Installation Options › The ChekPlex Feature › Remote validation options

Remote validation options

ChekPlex uses the REMVAL DD to get data set references and options for remote validation.

The data set allocated to the REMVAL DD defines the following items:

• All the nodes that are participating in the validation process.
• The data sets to be validated.
• The procedure libraries to be allocated on the target server.
• The data sets to be shipped with the source JCL from the source server to the target server.

The options available with REMVAL are:

LOCAL

Defines the name of the local GTS server. This GTS server must be running with the ChekPlex subsystem running on it.

This is a required keyword.

Example:

LOCAL GTS1

SOURCE

Defines the name of the source GTS server. It provides source JCL and can also provide several procedures that you can use for procedure overrides. In most cases, this is the same server as the LOCAL node. This GTS server must be running and the ChekPlex subsystem running on it.

This is not a required keyword; however, if omitted the LOCAL node name is used.

Example:

SOURCE GTS1

TARGET

Defines the names of GTS servers where the validation is to be performed. The GTS servers must be running with the ChekPlex subsystem running on them. You can request validation on up to 64 servers.

This is a required keyword, it can appear multiple times.

Example:

TARGET GTS2
TARGET GTS3

SYSIN

Defines a JCL file to be validated, for example, a PDS member or a sequential data set. These data sets are retrieved from the source server and transferred to the target servers prior to JCL validation. You can define more than one data set or PDS member.

For library validation, one library name can be defined using this SYSIN and you need to use the PDS, LIB, or PAN option in the JCLCheck options. Options to limit member selection (for example, INCLUDE, EXCLUDE, and ONEMEM) can be used in Calling options or OPTIONS DD.

Note: The SYSIN keyword in the REMVAL file completely overrides the SYSIN DD statement defined in the execution JCL, and the input file used on the ISPF panels.

This is not a required keyword, it can appear multiple times.

Example:

SYSIN USERID.JCLCHECK.JCL(TESTJCL)

PROC

Defines procedure libraries that are used for resolving procedure and include references in JCL. These libraries need to exist on the target server, or validation on that server fails.

Note: The PROC keyword in the REMVAL file completely overrides the SYSPROC DD statement defined in execution JCL.

This is not required if using AUTOPROC; otherwise, it is a required keyword. More than one library can be defined.

Example:

PROC USERID.JCLCHECK.PROCLIB
PROC SYS1.PROCLIB

OPROC

Defines procedure libraries that are used for the OPROC option. These procedure libraries have to exist on the target servers or validation on that server fails.

Note: The OPROC keyword in the REMVAL file completely overrides the OPROC DD statement defined in execution JCL.

This is not a required keyword, it can appear multiple times.

Example:

OPROC USERID.JCLCHECK.PROCLIB

SSPROC

The SSPROC keyword defines a small number of procedures that are transferred with the source JCL from the source server to all target servers. This option must refer to library members in the form PDS(member). On the target server, these procedures are stored in a temporary PDS library which is used to locate a procedure before using the IBM standard search libraries.

Note: The SSPROC and OPROC keywords are mutually exclusive. If both keywords are specified, the SSPROC keyword overrides the OPROC specification.

The SSPROC keyword is processed whether the AUTOPROC option is specified or not.

This is not a required keyword; it can appear multiple times.

Example:

SSPROC USERID.PROCLIB(TESTPROC)