Bypassing specific processing

When Advanced Allocation Management does not operate as expected for a particular job or started task, and the process is critical to production processing, you can force Advanced Allocation Management to bypass the area of processing in question without shutting down the product entirely for all other processing.

To force Advanced Allocation Management to bypass processing for all of the data sets that are accessed by the step, add a bypass ddname to any job step JCL. The ddname is AOBYPASS and the format of the DD statement is:

//AOBYPASS DD DUMMY

Add the statement anywhere after the EXEC statement of a step and before the EXEC statement of the next step or the end of job indicator (//). For example:

//PDUSER#2 JOB (ACCT#),'PDUSER',                           
//         MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID              
//*
//JOBLIB  DD  DISP=SHR,                                   
//            DSN=DSN.V710.SDSNLOAD                       
//*                                                       
//DSNTEP2 EXEC PGM=IKJEFT01,DYNAMNBR=20                   
//AOBYPASS DD DUMMY
//SYSTSPRT DD  SYSOUT=*                                   
.
 -- PROCESSING TO BYPASS -----
.
//DSNTEP3 EXEC PGM=IKJEFT01,DYNAMNBR=20

By using the bypass ddname, you can avoid the processing in question without having to perform extensive time-consuming modifications to the rule definitions. You can also use the bypass ddname to systematically isolate specific areas of processing to locate the cause of a particular problem.

Note: Because DB2® performs space management for its own data sets, Advanced Allocation Management automatically bypasses processing for DB2 allocated data sets. This eliminates the creation of unnecessary control blocks and thus, the CPU time that is associated with managing those allocations.