hi,
1>validate(run/bind)-default is validate at run.. it checks authorization for an object
2>sqlerror(continue/error)-- if an error occurs in sql it wont bother it continues to create a incorrect package almost this parameter error..if error it wont create a package...
3>ACQUIRE(USE)/RELEASE(COMMIT)...
WHEN EVER SQL THREAD IS IMPLEMENTED THAT TIME ONLY THE LOCKS WILL IMPOSED ON TABLE WHICH TABLE REFERED .AFTER COMIT IT WLL BE RELEASED AS PER THE RELEASE PREFERENCE
4>ISOLATION LEVEL(CS/UR/RR)--DEFAULT IS CS(CURSOR STABILITY) WHICH IS IMPLEMENTING ON TABLE / TABLE SPACE LEVEL ,,,IF THE CURRENT PAGE IS MOVING TO ANOTHER PAGE..(INCLUDING THE UPDATION TAKEN PLACE) ..THE LOCKS ON FIRST IS RELEASED...THIS IS CS//
RR--- TABLE/TABLESPACE LOCKING WLL BE TAKEN AND WHEN PLAN STARTS EXECUTION IT WLL BE LOCKED AND AFTER COMIT IT RELEASES LOCK...
UR--DIRTY READ./....N NUMBER TRANSACTION CAN ACCESS THE ROW IRRESPECT OF UPDATION WHICH TENDS TO UNCERTAINITY OF DATA..WHICH IS NOT A POLICY OF DB2..
4>QUALIFIERS-- IMPORTANT--WHEN U R MOVING PGM TO ONE REGION TO ANOTHER REGION AT BIND TIME WE CAN ADD QUALIFIER S TO OBJECT WITH OUT CHANGING THE CODE SIMPLY SPECIFYING THIS