Previous Topic: JCT—JES2 JCT OffsetsNext Topic: JESNODE—JES Local Node Name


JES—JES Subsystem Information

Valid on z/OS.

Use the JES control option to provide CA Top Secret with JES subsystem information and to indicate whether CA Top Secret needs to provide support for the Early Verify feature.

All entry methods are accepted.

This control option has the following format:

JES(SSID=cccc)
JES(TYPE=JES2 | JES3)
JES(LEVEL RELEASE n.n)
JES(VERIFY|NOVERIFY)
SSID=cccc

Specifies the name of the primary JES subsystem if it is other than JES2 or JES3. SSID only applies to the primary JES subsystem.

TYPE

TYPE must be entered if SSID is coded, and indicates the type of | primary JES system which is or will be active. TYPE can be abbreviated as 2, for JES2, and as 3, for JES3.

LEVEL|RELEASE|VERSION=xx r.ss.tt

Indicates the level of JES operating in your system. Specify this value only if starting CA Top Secret before JES. For example:

xx=SP|OS|z/OS
r.ss.tt=JES release number (may not correspond with operating system)

To obtain a valid value for the JES release, see the JES3 initialization message:

IAT31 JES3 xx r.ss.tt SYSTEM LOCAL START on yyy.ddd AS main

Or the JES2 message:

$HASP426 SPECIFY OPTIONS — JES2 xx r.ss.tt

Because this operand is specified with spaces, a command to modify the JES version must enclosed in single quotes. For example:

TSS MODIFY('JES(SSID=JES2,TYPE=2,RELEASE=OS 2.8)')

For an operator command or parameter file entry, single quotes must not be used. For example:

F TSS,JES(SSID=JES2,TYPE=2,RELEASE=0S 2.8)

If CA Top Secret is started before JES, both TYPE and LEVEL must be specified. If CA Top Secret is started after JES, CA Top Secret will pick up the TYPE and LEVEL from JES itself. In this case, entering TYPE and LEVEL is not recommended.

If you are specifying z/OS, the “z” must be in lower case unless fix Q042768 is applied.

VERIFY

(Default) Indicates CA Top Secret verifies USER and PASSWORD parameters implicitly without inserting these parameters into the JOB JCL statement. This is the default for JES2 and JES3. If a USER is present in the JOB statement, then the USER is checked to see that the submitter is cross‑authorized. If submission is allowed, no password processing will take place unless the password is explicitly coded. For information, see the Implementation:: Batch TSO and APPC Guide.

NOVERIFY

Indicates CA Top Secret will insert USER and PASSWORD information explicitly into the JOB JCL processing if it is not already present. Inclusion of explicit USER and PASSWORD information is not recommended, as this can be intercepted from spool.

The JES control option is required if the CA Top Secret main task is started before JES completes initialization. In this case, the control option indicates JES subsystem and release level, as well as whether the JES Early Verify feature is desired.

When JES is initialized before starting the CA Top Secret main task, the release and subsystem information is available to CA Top Secret, and need not be explicitly specified. CA Top Secret locates the first subsystem with type JES and interprets the information provided there.

Note: If the JES2 control option is supplied incorrectly by the user, the following message can be released during job submission:

TSS9401E TSS CONTROL OPTION 'JCT'IS INCORRECTLY SET

It is actually unlikely that the JCT control option is set incorrectly. Unless your site makes modifications to JES control blocks, the JCT option should be allowed to default.

Before attempting to adjust the JCT option, assure that the JES RELEASE has been correctly specified.