Previous Topic: How You Change a CPU JobNext Topic: Example: Batch Input


DB.10 - XP Job Definition Panel

The DB.10 - XP Job Definition panel lets you enter or review data that is 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 JobL: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 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:

FUNCTION

Specifies the function to perform. Value must be the name of some other panel or one of the following:

Add

Adds a job to the database when the same-named job does not currently exist.

DD

Deletes a job and its associated data from the database (documentation, schedules, and so forth).

Delete

Deletes a job and its associated data from the database (documentation, schedules, and so forth).

DELPRRN

Deletes the parameter and associated data from the prior run queue for this job.

Format

Clears the panel of all input data.

List

Lists a job and job-related information. In batch, a formatted panel is not listed; only a found or not found message is returned.

Purge

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 group includes all virtual resources that are connected to the job.

Update

Updates database information about a job.

Batch keyword: Positional parameter

Note: A default interpretation can be set for the DELETE function in the CA WA CA 7 Edition initialization file. For more information, see the OPTIONS statement in the chapter "Initialization File" of the Systems Programming Guide.

Job

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

JobL

(Optional) Defines the long job name on which to perform the indicated function.

Note: For more information, see Long Job Name Rules.

Limits: 1 to 64 alphanumeric characters, case sensitive

Batch keyword: JOBL

System

(Optional) Defines the user-defined application system name of which this job is a part. This field is 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 WA CA 7 Edition XPS monitor name.

Limits: 1 to 8 alphanumeric characters. This field cannot contain a comma.

Batch keyword: SYSTEM

JOBNET

(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 can be used within CA WA CA 7 Edition internally.

Limits: 1 to 8 alphanumeric characters. This field cannot contain a comma.

Batch keyword: JOBNET

Owner

(Optional) Defines the ID identifying ownership of this job. This field can have multiple meanings, depending on the CA WA CA 7 Edition 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

UID

(Optional) Defines the CA WA CA 7 Edition user security identification.

Default: 0 (No internal security identification)

Limits: 1 to 3 numeric characters from 0 through 999

Batch keyword: USERID

XP Node

Defines the CAICCI node to which the execution of this job is targeted. This field 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

XP EXEC

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 WA CA 7 Edition, this value indicates the job name to execute on that platform. If the targeted platform is CA Workload Automation AE system, this value indicates a job that is defined in the CA Workload Automation AE system. If this field begins and ends in single quote (') marks, these marks 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 value 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. Thus, define the file name carefully so that translation can occur correctly between EBCDIC and ASCII.

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.

XP PARM

(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 marks 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 PARMLIB

(Optional) Defines extra, optional indexed, or symbolic (PDS) library from where execution data to be associated with this job may be found. This information is typically PARM1 through PARM64 keywords but can vary based on CA WA CA 7 Edition system configuration options. If the 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 or 256 - 999), 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 must 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.

Member

(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

Use-Ovrd-Lib

(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

EXEC

(Optional) Indicates whether to execute this job.

Y

Specifies to execute the job. This is the default.

N

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

SUTYPE

(Optional) Specifies the type of "switch user" command to execute at the UNIX target node.

Y

Executes an "SU -" causing the environment set up to include execution of the ".PROFILE" for the target user. This is the default.

N

Executes an "SU" command without the profile option.

Batch keyword: SUTYPE

Cond-Code

(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

RO

(Optional) Specifies the relational operator of the condition code (COND-CODE).

The following are the possible values:

0

Performs no condition test. This value is the default.

EQ

Specifies equal to.

LT

Specifies less than.

GT

Specifies greater than.

GE

Specifies greater than or equal to.

LE

Specifies less than or equal to.

NE

Specifies not equal to.

IG

Performs no evaluation of the job. CA WA CA 7 Edition always assumes that 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 WA CA 7 Edition only. It simply tells CA WA CA 7 Edition what action to take after the job completes.

DRClass

(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

Hold

(Optional) Specifies whether to put this job in a hold status when it enters the request queue.

N

Does not put this job in a hold status. This is the default.

Y

Puts this job in a hold status.

Batch keyword: HOLD

Verify

(Optional) Specifies whether this job requires any presubmission manual verification.

Note: This function is similar to VERIFY command.

N

Specifies that this job does not require presubmission manual verification. N is the default.

Y

Specifies that this job requires presubmission manual verification.

Batch keyword: VERIFY

Satisfaction Lead Time

(Optional) Defines the number of hours to consider when satisfying job-dependent requirements.

The following values are possible:

0

Indicates no lead time is considered when satisfying this job's requirements. This value is the default.

99

Indicates that the requirement is never considered as already satisfied when the job enters the queues. Each predecessor job must complete typically while this job is in the request queue.

nn

Indicates that each predecessor job must have run within the last nn hours after 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.

ARFSET

(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

Clock Time

(Optional) CA WA CA 7 Edition 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: The 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

WLBClass

(Optional) Specifies the CA WA CA 7 Edition WLB job class. If CLASS is not specified, a WLB class of A is automatically assigned. This value does not have to match the JOB statement CLASS value.

The CLASS specified here does not apply when the job enters the queue as a result of a RUN(H) command. Class 9 is assigned by default. To override class 9, use the RUNCLASS keyword on the OPTIONS statement in the initialization file.

The CLASS specified here does not apply when the job enters the queue as a result of a LOAD(H) command. Class 8 is assigned by default. To override class 8, use the LOADCLASS keyword on the OPTIONS statement in the initialization file.

Default: A

Limits: 1 alphanumeric character

Batch keyword: CLASS

WLBPRTY

(Optional) Defines the CA WA CA 7 Edition 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 if WLB is not used

Limits: 1 to 3 numeric characters from 0 to 255

Batch keyword: PRTY

Trace

(Optional) Indicates whether to trace the activity associated with this job as it moves through the CA WA CA 7 Edition queues. The possible values include:

N

Do not activate tracing for this job. N is the default.

Y

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

Don't Schedule Before

(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

After

(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 WA CA 7 Edition uses current date and time for comparisons.

Retain

(Optional) Specifies whether to retain the job data sent to the target node in the trailer queue after a successful execution.

N

Do not send the job data. N is the default.

Y

Send the job data.

Default: N

Batch keyword: RETJCL

LTERM

(Optional) Defines a logical terminal name to receive messages about this job.

Note: If the logical terminal name is defined as a virtual terminal, a CAICCI terminal, or CONSOLE, the messages are dynamically rerouted to the MASTER terminal. Messages that are routed to the MASTER terminal are written to the BROWSE DD file.

Default: MASTER

Limits: 1 to 8 alphanumeric characters

Batch keyword: LTERM

Note: For a CPU job, you can specify LTERM 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 where messages are sent is on the XPJOB (DB.10) panel.

Prompt

(Optional) Specifies whether to issue prompt messages when this job is late.

Y

Issue the prompt messages. Y is the default.

N

Do not issue the prompt messages.

Batch keyword: PROMPT

Note: If LATEPROMPT=LATE is specified on the OPTIONS statement of the 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 that are defined with a value of yes (Y) are processed the same regardless of the LATEPROMPT setting.

Rqmt list

(Optional) Specifies whether to list the preexecution requirements for this job when it enters the request queue.

Y

List the requirements. Y is the default.

N

Do not list the requirements.

Batch keyword: RQLST

Rqmts Not Used

(Optional) Specifies whether to issue error messages for job requirements not used.

Y

Issue error messages. Y is the default.

N

Do not issue error messages.

Batch keyword: RQMSG

More information:

Usage Notes for DB.1, DB.10, and DB.11