The DB.10 - XP Job Definition panel lets you enter or review data related to XPJOB jobs.
To display the panel, enter:
To exit the panel:
------------------------- CA-7 XP Job Definition -------------------------- Function: xxxxxxxx (Add, DD, Delete, DELPRRN, Format, List, Purge, Update) Job: xxxxxxxx System: xxxxxxxx JOBNET: xxxxxxxx Owner: xxxxxxxx UID: nnn XP Node: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx XP EXEC: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx XP PARM: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Optional PARMLIB: xxxxxxxxxxxxxxxx Member: xxxxxxxx Use-Ovrd-Lib: EXEC: x SUTYPE: x Cond-Code: xxxx RO: xx DRClass: xxxxxxxx Hold: x Verify: x Satisfaction Lead Time: nn ARFSET: xxxxxxxx Clock Time: nnnn WLBClass: x WLBPRTY: nnn Trace: x Don't Schedule Before: yyddd hhmm After: yyddd hhmm Retain: x LTERM: xxxxxxxx Prompt: x Rqmt List: x Rqmts Not Used: x PROGRAM: SM22 MSG-INDX: nn -- DB.10 -- yy.ddd / hh:mm:ss MESSAGE: ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE
This panel contains the following fields:
Specifies the function to perform. Value must be the name of some other panel or one of the following:
Adds a job to the database if the same-named job does not currently exist.
Deletes a job and its associated data from the database (documentation, schedules, and so forth).
Deletes a job and its associated data from the database (documentation, schedules, and so forth).
Deletes the parameter and associated data from the prior run queue for this job.
Clears the panel of all input data.
Lists a job and job-related information. In batch, a formatted panel is not listed; only a found or not found message is returned.
Same as delete, but also deletes job trigger definitions that trigger the job being deleted and job requirement definitions that require the job being deleted. This includes all virtual resources connected to the job.
Updates database information about a job.
Batch keyword: Positional parameter
Note: A default interpretation can be set for the DELETE function in the CA Workload Automation SE initialization file. For more information, see the OPTIONS statement in the chapter "Initialization" of the Systems Programming Guide.
Defines the job name on which to perform the indicated function.
Limits: 1 to 8 alphanumeric characters. The job name format of UCC7Rxxx (where xxx is any three characters) is reserved for use with Workload Balancing. This imposes a restriction that no other user-defined job can begin with UCC7R as the first five characters.
Batch keyword: Positional parameter
(Optional) Defines the user-defined application system name of which this job is a part. This field will be transmitted to the cross-system platform as the JOBSET name. If this field is not completed, the JOBSET field is the value of the CA Workload Automation SE XPS monitor name.
Limits: 1 to 8 alphanumeric characters. This field cannot contain a comma.
Batch keyword: SYSTEM
(Optional) Defines the name of a job network of which this job is a part.
Note: This field is not transmitted to the cross-system platform but may be used within CA Workload Automation SE internally.
Limits: 1 to 8 alphanumeric characters. This field cannot contain a comma.
Batch keyword: JOBNET
(Optional) Defines the ID identifying ownership of this job. This field can have multiple meanings, depending on the CA Workload Automation SE startup options specified on the XPDEF statement. This field can be used to identify the "User ID" resource record (entered through the XPSWD,OWNER= command) in which to find the user ID and password for the job being executed on the alternate platform. If the XPDEF definition permits this field to code the user ID, the user ID under which the job executes is obtained from here, and a password is not associated with the job on the alternate platform. If this field is left blank and the XPDEF definition allows USER, the security information must be specified in the parameter library. If PSWDLOC specifies NODE, the user ID and password are obtained from the Node Table information. If no user ID is found for the AJB, the job is submitted to the platform without any user information (the platform may reject the job execution if security is set that way).
Limits: 1 to 8 alphanumeric characters. Although this field supports up to 8 characters, some external security packages only accept up to 7 characters. This field must not exceed any such limit that exists.
Batch keyword: OWNER
(Optional) Defines the CA Workload Automation SE user security identification.
Default: 0 (No internal security identification)
Limits: 1 to 3 numeric characters from 0 to 255
Batch keyword: USERID
Defines the CAICCI node to which the execution of this job is targeted. This should state the primary node. If this node is unavailable and the node definition has alternate nodes defined, the execution of this job can be directed to an alternate node.
Limits: 1 to 44 alphanumeric characters, although current z/OS CAICCI restricts this name to eight characters.
Batch keyword: NODE
Defines the executable (file, command) to execute at the targeted cross-platform node. If the targeted platform is a mainframe scheduling system such as CA Workload Automation SE, this indicates the job name to be executed on that platform. If the targeted platform is CA Workload Automation AE system, this indicates a job defined in the CA Workload Automation AE system. If this field begins and ends in single quote (') marks, these are removed before being passed in the transmission data. Otherwise, the field is passed to the target system as-is and in its entirety. This includes any embedded blanks and quotation marks.
Limits: Three 64-byte lines and one 52-byte line, comprising 244 alphanumeric characters, and file delimiters of forward slash (/) and backward slash (\) signs.
Batch keyword: EX1, EX2, EX3, EX4
Note: Some EBCDIC characters do not translate to ASCII, and thus the file name must be carefully defined so that translation can occur correctly between EBCDIC and ASCII.
You must enclose the value of the batch parameter in parentheses if this field contains commas or trailing spaces and you are using the batch method to add or update the XP EXEC or XP PARM fields.
(Optional) Defines up to 128 bytes of parameter data to pass to the file or command being executed on the alternate platform. This data is supplied as PARM1 to the data being transmitted to the alternate platform. If this field begins and ends in single quote (') marks, these are removed before being passed in the transmission data. This value may be overridden if the PARMLIB/MEMBER field PARM1 is coded.
Limits: Two 64-byte lines, comprising up to 128 EBCDIC characters.
Batch keyword: XP1 and XP2
Note: Some EBCDIC characters do not translate to ASCII, and thus the file name must be carefully defined so that translation can occur correctly between EBCDIC and ASCII.
(Optional) Defines an additional, optional indexed or symbolic (PDS) library from where execution data to be associated with this job may be found. This information is normally PARM1 through PARM64 keywords but can vary based on CA Workload Automation SE system configuration options. If PARM1 field is found within this file, it overrides the data specified in the XP PARM field listed on the panel.
Limits: 1 to 16 alphanumeric characters. If this field starts with a numeric value, the value is treated as a JCL Index value (0 - 253), and the associated numbered JCL library, as defined in the initialization file JCL statement, is used. If the first character is not numeric, the field must start with an ampersand (&) and denote the library variable as defined using a /JCL command.
Batch keyword: PRMLIB
Note: Specifying data in the PARMLIB/MEMBER fields is in addition to anything specified in the XPPARM field. If XPPARM is coded, and if the PARMLIB/Member contains a PARM1 statement, the PARMLIB specification overrides the XP PARM field. Thus, if both XPPARM and PARMLIB PARM1 fields contain data, the data obtained from the PARMLIB/MEMBER is used in the data transmitted to the target node.
(Optional) Indicates the PDS member name of the preceding library where the parameters for this job reside.
Default: Same as the Job field
Limits: 1 to 8 alphanumeric characters, beginning with an alphabetic character
Batch keyword: MEMBER
(Optional) Specifies whether to retrieve the JCL from the JCL Override library (JCLID=254) for the next run only (Y or N). This field is automatically set back to N the next time the job comes into the request queue.
Default: N
Batch keyword: JOVRDLIB
(Optional) Indicates whether to execute this job.
Specifies to execute the job. This is the default.
Specifies that the job does not run but shows a normal completion as if it did run.
Note: Consider the following items:
Batch keyword: EXEC
(Optional) Specifies the type of "switch user" command to execute at the UNIX target node.
Executes an "SU -" causing the environment set up to include execution of the ".PROFILE" for the target user. This is the default.
Executes an "SU" command without the profile option.
Batch keyword: SUTYPE
(Optional) Used with RO (relational operator), defines the job-level condition codes used to determine whether a job executes successfully. All condition codes returned from an XPJOB job are treated as positive values. Any negative value returned is converted to an absolute (positive) value.
Default: 0
Limits: 1 to 4 numeric characters from 0 to 9999
Batch keyword: CONDCODE
(Optional) Specifies the relational operator of the condition code (COND-CODE).
The following are the possible values:
Performs no condition test. This is the default.
Specifies equal to.
Specifies less than.
Specifies greater than.
Specifies greater than or equal to.
Specifies less than or equal to.
Specifies not equal to.
Performs no evaluation of the job. CA Workload Automation SE always assumes the job completes successfully, regardless of condition codes, abend codes, or runtime JCL errors.
Batch keyword: RELOPR
The highest condition code that this job generates is tested by this pair of parameters. For example, if COND-CODE is set at 8 and RO is set at LT, the job is marked as completing abnormally if 8 is less than the job's condition code.
Note: This test is for internal use by CA Workload Automation SE only. It simply tells CA Workload Automation SE what action to take after the job completes.
(Optional) Defines the job's disaster recovery class. This field has no impact on processing during normal execution. When running in disaster recovery mode, the disaster recovery class is used to determine whether the job should execute.
Note: For more information about disaster recovery mode, see the Systems Programming Guide.
Limits: 1 to 8 alphanumeric characters. Values must start with a letter, #, or $ (not @) and can include letters, #, $, @, and numbers. Disaster recovery classes cannot contain embedded blanks.
Batch keyword: DRCLASS
(Optional) Specifies whether to put this job in a hold status when it enters the request queue.
Does not put this job in a hold status. This is the default.
Puts this job in a hold status.
Batch keyword: HOLD
(Optional) Specifies whether this job requires any presubmission manual verification.
Note: This function is similar to VERIFY command.
Specifies that this job does not require presubmission manual verification. This is the default.
Specifies that this job requires presubmission manual verification.
Batch keyword: VERIFY
(Optional) Defines the number of hours to consider when satisfying job dependent requirements.
The following are the possible values:
Indicates no lead time is to be considered when satisfying this job's requirements. This is the default.
Indicates that the requirement is never considered as already satisfied when the job enters the queues. Each predecessor job must complete normally while this job is in the request queue.
Indicates that each predecessor job must have run within the last nn hours since the last run of this job.
Limits: 1 - 98
Batch keyword: JOBLDTM
Note: For XPJOB jobs, JOB and DSN Satisfaction Lead Time are treated as one.
(Optional) Defines the collection of ARF definitions that apply to this job. Remember that ARF recovery is not invoked for nonexecutable jobs.
Limits: 1 to 8 alphanumeric characters. The specified ARFSET must be defined in the ARF database.
Batch keyword: ARFSET
(Optional) CA Workload Automation SE maintains certain feedback data in its database, including a weighted average elapsed execution time. If the database is updated with a clock time of 0000, then in addition to this clock time field the counters for the number of runs, number of times late, and number of restarts is also set to 0000. One use of this value is deadline prompting. If 2359 is specified, deadline prompt time is not adjusted. The deadline time remains due-out time minus lead time.
Note: Clock time average is not updated if the job is not successful in its execution. The weighted average is the value in the database times five, plus the value from the current execution, divided by six. This tends to keep the current run from possibly skewing the value.
Default: 0000
Limits: 4 numeric characters specified as hhmm, where hh can be 00 through 23, and mm can be 00 through 59
Batch keyword: ELAPTM
(Optional) Defines the CA Workload Automation SE WLB job class. If Workload Balancing is used, any job without a specified job class is automatically assigned to class A. Also, for workload balancing, any job that enters the queue as a result of a RUN(H) command is assigned to class 9.
Default: A
Limits: 1 alphanumeric character
Batch keyword: CLASS
(Optional) Defines the CA Workload Automation SE WLB job priority. A value of 255 indicates an express priority used to bypass WLB priority scheduling criteria. If using WLB, any job without a specified priority is automatically assigned a priority of 100 unless the default is changed.
Default: 100 if WLB is used or 0 is WLB is not used
Limits: 1 to 3 numeric characters from 0 to 255
Batch keyword: PRTY
(Optional) Indicates whether to trace the activity associated with this job as it moves through the CA Workload Automation SE queues. The possible values include:
Do not activate tracing for this job. This is the default.
Issue WTOs as the job enters into the submission process and retain up to 256 characters of the data sent for inclusion in a log record.
Batch keyword: XPTRACE
(Optional) Specifies that this job is not to be scheduled before this date and time. This keyword is especially helpful for timing the start of new jobs.
Panel input is:
BEFORE: yyddd hhmm
Batch input is:
BDATE=yyddd,BTIME=hhmm
Default: All zeros
Limits: Julian date specified as yyddd and time specified as hhmm
Batch keyword: BDATE and BTIME
(Optional) Specifies that this job is not to be scheduled after this date and time. This keyword is especially helpful for timing the permanent discontinuation of a job.
Panel input is:
AFTER: yyddd hhmm
Batch input is:
ADATE=yyddd,ATIME=hhmm
Default: 99999 0000
Limits: Julian date specified as yyddd and time specified as hhmm
Batch keyword: ADATE and ATIME
Note: If BDATE and BTIME values are equal to ADATE and ATIME, the job is not scheduled and does not appear on forecasts. If BDATE and BTIME values are greater than ADATE and ATIME, the job is not available for scheduling during the inclusive times only. Thus, if BDATE=09031 and BTIME=2359 and ADATE=09001 and ATIME=0000, the job does not schedule during the time from Jan. 1, 2009 through Jan. 31, 2009, but does schedule at all other times. CA Workload Automation SE uses current date and time for comparisons.
(Optional) Specifies whether to retain the job data sent to the target node in the trailer queue after a successful execution.
Do not send the job data. This is the default.
Send the job data.
Default: N
Batch keyword: RETJCL
(Optional) Defines a logical terminal name to receive messages about this job.
Default: MASTER
Limits: 1 to 8 alphanumeric characters
Batch keyword: LTERM
Note: Although a CPU job can specify LTERM either on the JOB (DB.1) Definition panel or in the initialization file JCL statement from which the JCL is pulled, for XPJOBs, the only place to define the terminal to which messages are sent is on the XPJOB (DB.10) panel.
(Optional) Specifies whether to issue prompt messages if this job is late.
Issue the prompt messages. This is the default.
Do not issue the prompt messages.
Batch keyword: PROMPT
Note: If LATEPROMPT=LATE is specified on the OPTIONS statement of the CA Workload Automation SE initialization file, setting this value to no (N) prevents the job from ever having a status of LATE on an LQ or LRLOG display. Jobs defined with a value of yes (Y) are processed the same regardless of the LATEPROMPT setting.
(Optional) Specifies whether to list the pre-execution requirements for this job when it enters the request queue.
List the requirements. This is the default.
Do not list the requirements.
Batch keyword: RQLST
(Optional) Specifies whether to issue error messages for job requirements not used.
Issue error messages. This is the default.
Do not issue error messages.
Batch keyword: RQMSG
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|