Indicates the identity of the system in which the job must be initiated and executed (in JES2).
NOTE: This field is relevant only for z/OS jobs.
Additional information |
Description |
---|---|
Usage |
Optional |
Length |
1-5 alpha-numeric characters The alpha-numeric characters can be proceeded by a "/". "/" as a first character indicates NOT in JES3. |
Case Sensitive |
No |
Invalid Characters |
Non-English characters |
Variable Name |
None |
Alternate names |
|
Indicates the identity of the processor on which the job must execute (in JES3).
The System Affinity parameter has different effects, depending on which release of JES is in use.
NOTE: If a value is specified for the System Affinity parameter, it does not override any system identity specified in the job statement unless the OVERJCLM parameter in the CTMPARM library is set to Y.
Under JES2
If Control-M is running under JES2, the System Affinity parameter is used to specify the JES2 system on which the job is to be initiated and executed. If a value is specified for the System Affinity parameter, the following JCL statement is generated:
/*JOBPARM SYSAFF=sys_id
Under JES3
If Control-M is running under JES3, the System Affinity parameter is used to specify the JES3 processor that is to execute the job. If a value is specified for the System Affinity parameter, the following JCL statement is generated:
//*MAIN SYSTEM=processor_id
EXAMPLE: Under JES2
The following values are entered to the job processing definition:
The following statement is added to the JCL of the job:
/*JOBPARM SYSAFF=SYS3
The job is executed on the JES2 system SYS3.
Under JES3
The following values are entered to the job processing definition:
The following statement is added to the JCL of the job:
//*MAIN SYSTEM=PRC3
The job is executed on processor PRC3.
Parent Topic |