Setting up AR/CTL with JCL changes
Depending on the type of application program and on the methods you choose to implement
AR/CTL
participation, perform these steps as applicable:
If the program uses Db2 and is attached to run under any other program or product (except AR/CTL), change the JCL to invoke the program directly.Many batch Db2 programs that use the TSO attach method execute program IKJEFT01 and provide the Db2 attach and execute commands with the SYSTSIN DD statement. The following example shows this method of executing a Db2 program without AR/CTL:
//S1 EXEC PGM=IKJEFT01
//SYSTSIN DD *
DSN SYSTEM (DB2P)
RUN PROGRAM (MYPROG)
END
/*
// ADDITIONAL DD CARDS......To use AR/CTL for a Db2 program that is set up to use TSO attach (or any product that performs the attach on behalf of the application program), you must modify the EXEC statement in the JCL to execute the Db2 program in place of IKJEFT01. You can provide the Db2 attach information in the program execution record or with the ARCSSMLB DD statement, as explained in Setting-up-Db2-connections.
Db2 programs that used AR/CTL Version 1 execute program ARCCTRL. You do not need to change this program name.
If you want to use the AES$ssid DD statement, insert the AES$ssid DD DUMMY statement into the step JCL, where ssid is the four-character subsystem ID of the BCSS to use during execution.For more information, see Using-AR-CTL-DD-statements.
- If you are using the AR/CTL Status Check utility (program AESUVBCS) to ensure that AR/CTL products, components, and functions are available, and if you want to execute this utility as a stand-alone program, insert the utility job step ahead of the application program execution job step.For more information, see Administering.
Related topic