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)
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 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.
Note: 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 gets the TYPE and LEVEL from JES itself. In this case, we do not recommend entering TYPE and LEVEL.
Indicates the level of JES operating in your system. Because this operand is specified with spaces, a command to modify the JES version must be enclosed in single quotes. An operator command or parameter file entry must not use single quotes.
Note: 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 gets the TYPE and LEVEL from JES itself. In this case, we do not recommend entering TYPE and LEVEL.
Specifies the operating system.
Specifies the JES release number. This number may not correspond with the 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
Limits: This operand can be a maximum of 8 characters. If you are running z/OS 1.10 and higher, do not include a space in the LEVEL= operand.
Examples
These examples show only eight characters used:
LEVEL=z/OS1.10
LEVEL=z/OS1.11
This example shows a TSS command with single quotes:
TSS MODIFY('JES(SSID=JES2,TYPE=2,RELEASE=OS 2.8)')
This example shows an operator command without single quotes:
F TSS,JES(SSID=JES2,TYPE=2,RELEASE=OS 2.8)
This example shows a parameter file entry without single quotes:
JES(SSID=JES2,TYPE=2,RELEASE=OS 2.8)
(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: Other Interfaces Guide.
Indicates CA Top Secret will insert USER and PASSWORD information explicitly into the JOB JCL processing if it is not already present. We recommend that you do not include explicit USER and PASSWORD information, 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.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|