Invoking IDCAMS from a RUV job step


You can perform the IDCAMS delete/define operations in separate steps from the RUV restore or recovery process, or you can have RUV invoke IDCAMS to perform the delete/define operations in the same job step with the restore or recovery process.

RUV honors the IDCAMS return code. RUV does not display the SYSPRINT output from IDCAMS if the return code from IDCAMS is zero. If the return code is greater than zero or you have selected the detail or full level of reporting, RUV includes all IDCAMS SYSPRINT output in the RUV job output.

Using the IDCAMS commands

To mark the beginning of a series of IDCAMS commands that you want RUV to pass to IDCAMS during the RUV job step, use the ENTER_IDCAMS command, as shown in the following example. RUV passes all statements from the semicolon after the ENTER_IDCAMS command to the last character before the EXIT_IDCAMS command.

Coding the ENTER_IDCAMS and EXIT_IDCAMS commands

To code an UPDATE VSAM_FILE statement, use the following syntax:

ENTER_IDCAMS;
    [ statements to pass to IDCAMS ]
EXIT_IDCAMS;

Use the ENTER_IDCAMS and EXIT_IDCAMS commands as shown in the following example:

* define of ESDS test file
 ENTER_IDCAMS;
 DELETE  (RUVRUV.TEST.EBASE) CLUSTER
 SET     MAXCC=0
 DEFINE  CL (NAME(RUVRUV.TEST.EBASE)    -
         NONINDEXED                     -
         RECSZ(512 8192)                -
         TRK (8 4)                      -
         VOLUME(DEV233)                 -
         SHAREOPTIONS(2,3)              -
         )
 EXIT_IDCAMS;


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*