Using program ARCCTRL
To implement
AR/CTL
for an application program, BMC Software recommends that you use a program registration record or an automatic registration record. However, if you do not want to use one of these records, you can change the job step JCL to execute program ARCCTRL instead of the application program.
The following figure shows the EXEC statement and the AES$ssid DD statement for executing program ARCCTRL.
Program ARCCTRL
// REGION=0M,
// PARM='progname,asbname,arcid,ssm,PN=planname/parms/parms'
//AES$ssid DD DUMMY
Code the following parameters on the EXEC statement:
progname | Required. Specify the name of the application program to be executed under AR/CTL. |
|---|---|
asbname | Required. Specify the name of the application specification block (ASB) to use for this application program. You can code AUTO$ASB to use the default ASB. |
arcid | (Optional) You can specify an override AR/CTL identifier. If you omit it, AR/CTL uses the value of the Default AR/CTL Identifier (ARCID) option as it is set in the global options module. Retain the comma if you omit this parameter. |
ssm | Required for Db2 applications. Specify a value to be appended to the ARCID to form the subsystem name member. The member name is loaded from the data set that is identified with the ARCSSMLB DD statement. The member contains information such as which Db2 to connect to and is similar to the information that is supplied with the DDITV02 DD statement for IMS jobs. |
planname | Required for Db2 applications if the Db2 plan name is different from the program name. Specify the Db2 plan name. |
/parms/parms | (Optional) You can specify application and run-time parameters. |
If the program that is being executed is ARCCTRL, the AES$ssid DD statement works in the same way as a program registration record. It ensures that the job runs only under the subsystem ID of the BCSS that corresponds to the ssid value in the AES$ssid ddname.