Using AR/CTL DD statements

In addition to any DD statements that the application program already uses, the following DD statements are valid in the job step JCL of application programs that use AR/CTL:
AES$ssid DD

Optional if a program registration record applies to the execution; required if you want to use AR/CTL, if no program registration record applies, and if the program name is ARCCTRL or DFSRRC00; ignored if no program registration record applies and the program name is not ARCCTRL or DFSRRC00. Code the ddname as AES$ssid, where ssid is the four-character subsystem ID of the specific BCSS to use during execution. Code the statement as DUMMY. You might want to use the AES$ssid DD statement in the following situations:

  • If more than one REGISET contains a program registration record that applies to the program, you can use the AES$ssid DD statement to ensure that the execution uses a specific BCSS.

  • For a non IMS program that used AR/CTL Version 1 (the JCL was changed to execute program ARCCTRL), you can use the AES$ssid DD statement to implement AR/CTL Version 2 without creating a program registration record.

  • For IMS programs, you can use the AES$ssid DD statement instead of creating a program registration record.

If the program name is not ARCCTRL or DFSRRC00 and no program registration record applies to the execution, the AES$ssid DD statement is ignored; the execution continues without AR/CTL product participation. If the BCSS specified in the ddname of the AES$ssid DD statement is not active, execution continues without AR/CTL product participation. If more than one AES$ssid DD DUMMY statement is present, execution continues without AR/CTL product participation.

BMC Software recommends the use of program registration records instead of the AES$ssid DD statement.

For more information, see Administering.

ARC DD

Required if the application program uses specific program option members (ASBs), specific or default data set option members (also known as file characteristics blocks or FCBs), or both; can be allocated dynamically. Describes the library (or libraries) that contain these members. If the program uses the default ASB (AUTO$ASB) and AR/CTL internal default values for FBCs, this data set is not used.

Data set and program option members are load modules. The library that contains these members must have the following DCB parameters, which are typical of a load module library: DSORG=PO and RECFM=U.

AR/CTL can allocate this data set dynamically if you provide a dynamic allocation record to define it. If the JCL contains the ARC DD statement and the REGISET contains an ARC dynamic allocation record, the DD statement overrides the dynamic allocation record. For information about how to create dynamic allocation records, see Reference.

ARV DD

Optional. Use this statement to specify the data set name of the library that contains the CICS APPLID or CICS connection table that you want to work with.

AR/CTL can allocate this data set dynamically if you provide a dynamic allocation record to define it. If the JCL contains the ARV DD statement and the REGISET contains an ARV dynamic allocation record, the DD statement overrides the dynamic allocation record. For information about how to create dynamic allocation records, see Reference.

AR/CTL uses the following search order for locating the ARVRCON and ARVAPID modules. These steps occur independently for each module.

  1. If the ARV DD statement is included in the JCL, AR/CTL searches the JCL for the data set name. If the data set name is not present, AR/CTL allocates the data set dynamically if a skeleton is present.

  2. If the ARV DD statement is included in the JCL or is dynamically allocated, AR/CTL attempts to load the module from the library that is identified with ARV DD statement.

  3. If no ARV DD statement is present and AR/CTL cannot allocate it dynamically from a skeleton, it is loaded from the STEPLIB, JOBLIB, or LINKLST concatenation.

ARCSSMLB DD

Optional for non IMS DB2 application programs (can be allocated dynamically); not applicable for application programs that do not use DB2. Describes the AR/CTL procedure library containing the subsystem member that defines the DB2 subsystem connection information, as referenced by the ssm value of the PARM parameter. This data set must have the following DCB parameters: RECFM=F or FB, LRECL=80, BLKSIZE=n (where n is a multiple of 80). The name of the subsystem member that AR/CTL uses is the ARCID concatenated with the value of the ssm parameter of the EXEC statement.

The information provided with the subsystem member can be provided through the program registration record instead of the ARCSSMLB DD statement.

AR/CTL can allocate this data set dynamically if you provide a dynamic allocation record to define it. If the JCL contains the ARCSSMLB DD statement and the REGISET contains an ARCSSMLB dynamic allocation record, the DD statement overrides the dynamic allocation record. For information about how to create dynamic allocation records, see Reference.

ARCXRST DD

Required only for restart of non-unique job steps. If the job step is identified as non-unique and it requires restart, you must provide the data set name of the checkpoint data set that contains the necessary restart information. The presence of the restart data set in the job step JCL is the only indication that the job step needs to be restarted.

For more information, see Restarting a non-unique job step.

ARCPRINT DD

Optional; AR/CTL dynamically allocates the ARCPRINT data set if you omit the DD statement. You can include the ARCPRINT DD statement for use in reporting errors detected in the ARCSYSIN control statements. The statement defines a sequential data set. You can define it as SYSOUT=* to send the output to the same destination as the job messages, or you can define it as a DASD data set. On DASD, use the following DCB parameters: DSORG=PS, RECFM=FBA, LRECL=133, BLKSIZE=n (where n is a multiple of 133).

ARCSTATS DD

Optional. In addition to writing statistics to the history data set, AR/CTL can write them to the output data set defined by the ARCSTATS DD statement. If you provide the ARCSTATS data set, you can define it as SYSOUT=* to send the output to the same destination as the job messages, or you can define it as a DASD data set. On DASD, use the following DCB parameters: DSORG=PS, RECFM=FBA, LRECL=133, BLKSIZE=n (where n is a multiple of 133). If you omit the ARCSTATS DD statement, AR/CTL writes the statistical reports to the history data set only.

For information about the AR/CTL reports, see Reference. SYSUDUMP Optional. See Obtaining traces.

ASMTRACE

Optional; use this statement only if requested by BMC Software Product Support. See Obtaining traces.

RMTTRACE

Optional; use this statement only if requested by BMC Software Product Support. See Obtaining traces7.

VSMTRACE

Optional; use this statement only if requested by BMC Software Product Support. See Obtaining traces.

ARCDLTRC DD

Optional. AR/CTL writes enhanced call tracing records to this data set. You can include the ARCDLTRC DD statement in the job step JCL, or AR/CTL can allocate the trace data set dynamically.

For more information, see Using enhanced call tracing.

ARCSYSIN DD

Optional, but not recommended for use in production environments; however, it is useful for testing options. You can set AR/CTL processing options at the execution level with keywords in the ARCSYSIN data set. Typically, this data set is included in stream with the job step JCL, but it can be in a separate data set instead. If a separate data set, use the following DCB parameters: DSORG=PS, RECFM=F or RECFM=FB, LRECL=80, BLKSIZE=n (where n is a multiple of 80).

For more information, see Reference.

arvdblog DD

Required for local VSAM access services (can be allocated dynamically). Specify the data set name and disposition of the VSAM dynamic backout log. AR/CTL uses this log to provide dynamic backout support for batch VSAM application programs.

The VSAM Dynamic Backout Log DDname option defines the ddname to use for this DD statement. The default ddname (as distributed by BMC Software) is ARVDBLOG. If you use another ddname (except RCMDBLOG), you must change the value of this processing option to match the ddname you use. If you use RCMDBLOG, no change is necessary; AR/CTL supports the RCMDBLOG ddname for compatibility with previous levels of AR/CTL.

AR/CTL can allocate the VSAM dynamic backout log data set dynamically if you provide a dynamic allocation record to define it. If AR/CTL dynamically allocates this data set, the value of the VSAM Dynamic Backout Log DDname option must be ARVDBLOG or RCMDBLOG.

For more information, see Reference.

arvfctab DD

Required for remote VSAM access services; can be allocated dynamically. To perform remote VSAM access services, AR/CTL must access the VSAM file control table data set. You can provide a DD statement in the JCL to execute the batch application program, or you can allow AR/CTL to allocate the data set dynamically. If you provide the DD statement in the JCL, you can use any ddname; however, this ddname must be specified as the value of the VSAM File Control Table DDname processing option. The default ddname is ARVFCTAB.

For more information, see VSAM file control table data set - remote VSAM access services.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments