Previous Topic: Configure the Basic ARMNext Topic: To Disable or Enable the JES2 Exit6 Interface


Configure Extended ARM Support for JES2

If your installation uses JES2 instead of JES3, CA Vantage GMI supplies an exit program for JES2 Exit 6 which makes batch processing more efficient when the batch JCL references archived data sets. Instead of letting the job tie up an initiator while the needed data sets are restored one-by-one, the JES2 Exit 6 support holds the job, and routes all the needed restores to ARM at once. ARM can use multiple servers to restore the data sets, and do so more efficiently by grouping the restores so that all data sets on an archive volume are processed together, reducing the number of required tape mounts and associated wait time. ARM then releases the job when all restores are completed.

The supplied exit program is for JES2 Exit 6, and is implemented as a standard JES2 exit, allowing the scanning of internal text. Before installing the exit, see the IBM manual, System Programming Library: JES2 User Modifications and Macros, to read about JES2 exits and considerations for their use.

To configure the JES2 Exit

  1. Determine if you must tailor the supplied exit program KNGED009.

    Normally there is no need to tailor this program.

    However, KNGED009 uses user-field DTEUSER3 in the Converter DTE to store and retain information that is needed between calls to the Exit. If this field is already being used by other installation exits on your system, you must change the source code for KNGED009 to use one of the other user-fields (1-4). Contact your JES2 systems programmer to determine if user-field DTEUSER3 is already in use, and if it is, to select an alternate field to use.

    If an alternate field must be used, do the following:

    Find the source code for programs KNGJX006 and KNGED009 in the CCTUSRC library.

    Modify KNGED009 to use the alternate user-field that was selected.

  2. Assemble and link the JES2 Exit6 code.

    KNGJX006 is the small exit module loaded by JES2. KNGJX006 checks to see if CA Vantage GMI is active. If it is, KNGJX006 loads and calls KNGED009. KNGED009 is a larger module that performs the actual work.

    Verify that the SMP/E installation has assembled and linked the two exit programs without errors:

    If you have system parameter ARACALTR set to (Y), then review the description of this system parameter.

    Note: For a description of this system parameter, see the chapter "System Parameters" in the CA Vantage GMI SRM Configuration Guide. In addition, depending on how your security system is configured, modifications to the RACROUTE macro in KNGED009 may be required.

  3. Ensure that the CCTULINK library is in your system's linklist (the appropriate LNKLSTxx member in SYS1.PARMLIB). Be sure that the CCTULINK library is APF authorized.

    Note: In prior releases you may have moved KNGJX006 into the JES2 LOADLIB or another linklist data set. If so, it is recommended that you find and delete the old copy. Executing the exit from the CCTULINK linklist library makes future upgrades through SMP/E easy and reliable.

  4. Specify the new exit in the JES2 start‑up parameters

    The default JES2 start‑up parameters are in the data set pointed to by the //HASPPARM DD statement in the JES2 procedure in SYS1.PROCLIB.

    Add the following statements to your system's JES2 start‑up parameters:

    LOADMOD (KNGJX006)
    EXIT006 ROUTINE=(KNGJE006),ENABLE
    

    If your installation already has a JES2 Exit6 installed, for example USER06, you can add the CA Vantage GMI Exit6 to the list, as in the following example:

    LOADMOD(USER06)
    LOADMOD(KNGJX006)
    EXIT006 ROUTINE=(USER06,KNGJE006),ENABLE
    

    The CA Vantage GMI JES2 Exit6 should be called last so that it sees changes to the internal text made by prior exits.

  5. Activate the new JES2 Exit

    To do this, you must restart the JES2 system. Follow your installation procedures for restarting JES2.

    Observe the following:

  6. Provide filters in PARMLIB member ARJES2XT to improve efficiency.

    The JES2 exit must potentially find all data sets referenced in the JCL, and check the catalog to see which have been archived. You can eliminate some of this checking by specifying filter lists in member ARJES2XT in the CA Vantage GMI PARMLIB. Create ARJES2XT by copying it from the CCTUSAMP library.

    You can reduce the amount of checking in the following ways:

    In other words, you can customize the ARJES2XT PARMLIB member with include and exclude lists for JOBNAMES, PGMNAMES, and DSNAMES. The exit will check to see if a data set has been archived only if all three filter lists indicate it should be included for checking. That is, an exclude at any level; job, program, or data set name, results in the check being skipped.

    Find the JOBNAME PROCESSING LIST, PGMNAME PROCESSING LIST, and DSNAME PROCESSING LIST within PARMLIB member ARJES2XT, and supply appropriate patterns to be included and/or excluded. Each entry can specify an explicit (complete) name or a pattern name. Follow the instructions within the member itself.

    For a series of jobs that must run in sequence, it is usually best to ensure that all of the jobs are either included or excluded, but not mixed. If only some of the jobs in the series are included, the order may be affected.

    Observe the following:

  7. Activate your new or changed filters in ARJES2XT.

    When changes are necessary, update the member and issue the following operator command:

    F SAMS,ARM,REFRESH
    
  8. Jobs, Steps, and Data Sets Automatically Excluded (information only).

    The supplied JES2 EXIT6 code (programs KNGJX006 and KNGED009) automatically excludes certain jobs, job steps, and data sets from auto restore processing within the JES2 Exit. The following are descriptions for the automatic exclusions:

    Automatic Job Exclusions

    The exit does not process a job if:

    • TYPRUN=SCAN is used on the JOB statement
    • TYPRUN=COPY is used on the JOB statement
    • A ddname of ARNOJ2X6 is found within the job JCL
    Automatic Job Step Exclusions

    The exit does not process a job step if:

    • COND=ONLY is used on the EXEC statement. (Such data sets are not needed unless a previous job step abends.)
    • IEFBR14 is being executed with the COND keyword
    Automatic Data Set Exclusions

    The exit does not process a data set on a DD statement if:

    • DISP=NEW is specified (Only data sets with dispositions of OLD, SHR, or MOD are processed.)
    • DDNAME=, DYNAM, or SYSIN is specified
    • DUMMY is the first parameter
    • DSN=NULLFILE
    • DSN=* (A refer back. The data set name will have been checked already.)
    • VOL=SER is specified (Uncataloged data sets are not checked.)
    • DISP=(,CATLG) or (,PASS) was specified in a previous DD statement. (The data set was cataloged or passed from a prior job step DD statement.)

    Note: A data set referenced on a VOL=REF=dsname or DCB=dsname is not excluded from processing. These could reference archived data sets, so the catalog must be searched to determine whether they need to be restored.

    Automatic Exclusions Due to Errors

    The exit does not process any data set that is:

  9. Test the JES2 exit.

    To test the installation of the CA Vantage GMI JES2 Exit, start CA Vantage GMI, and then submit a job that refers to an archived data set. Make sure that the job name, program name, and data set name are not excluded by the processing list.

    The following should take place:

The extended ARM support for JES2 is active.