The DEMAND command forces a job to be scheduled immediately in the CA WA CA 7 Edition request queue. Jobs that have no definable processing cycles can be scheduled in this way. Demand scheduling can also be used to force jobs that have defined processing cycles to run early, or to schedule jobs for the first time before they are defined in the database.
The DEMANDH command indicates that the requested job is held in the request queue.
CC and RO are invalid for agent jobs.
You cannot specify the FROMNODE keyword.
JCLID, JCLLIB, MAINID, and RMS are invalid for internal cross-platform jobs.
Defines the name of the requested job. The requested jobs are placed in the request queue and given a unique CA 7 job number. JOB and JOBL are mutually exclusive.
(Optional) Defines the long name of the requested job. The requested jobs are placed in the request queue and given a unique CA 7 job number. JOB and JOBL are mutually exclusive.
Limits:1 to 64 alphanumeric characters
(Optional) Defines the ARF record name used for this execution of the job. If you specify **NONE**, no ARF processing is performed for this run of the job.
Limits:1 to 8 alphanumeric characters or **NONE**
(Optional) Uses RO (relational operator) to define the job-level condition codes used to determine whether a job runs successfully. If specified, this value overrides the RO defined for the job in the CA WA CA 7 Edition database. RO is required when CC is specified.
Standard:The COND-CODE value of the order definition field if the order is defined for CA WA CA 7 Edition; otherwise 0
Limits:1 to 4 numeric characters from 0 to 4095. Invalid for agent jobs.
(Optional) Defines the workload balancing class for resource checking.
Limits:1 alphanumeric character
(Optional) Defines the maximum number of repetitions of the job. COUNT is ignored if INTERVAL is not specified. If both COUNT and STOP are specified, the job will no longer be retried when COUNT reaches zero or the STOP time is reached, whichever comes first.
Standard:none. The job is repeated until the STOP time is reached.
Limits:1 to 4 digits from 0 to 1439. The leading zeros can be omitted.
(Optional) Defines due and submission dates.
Limits:If used, specify DOTM or TIME.
- +nn
Defines the number of days after the current date.
Limits:1 to 2 numeric characters from 1 to 99
- And
Defines the Julian date to run the job.
(Optional) Defines a single predecessor job that must be completed while the requested job is waiting.
Limits:1 to 8 alphanumeric characters
(Optional) Defines the due time for the job in hours (hh) and minutes (mm). If omitted, the current time (when the DEMAND was processed) plus the lead time is assumed.
If DOTM is specified in the DEMAND/DEMANDH command and the specified value is before the current time, the due date is assumed to be the following day.
If both DOTM and LEADTM are omitted, the deadline start time is assumed to be current time plus LEADTM.
Standard:Current time
Limits:hh= 1 to 2 numeric characters from 0 to 24
mm= 2 digits from 00 to 59
Necessary:No (unless DATE is used, if so, DOTM or TIME must be specified)
(Optional) Specifies whether to run the job (YES/NO). If NO (N) is used, the job will not run but will display a normal completion as if it had run. The value specified here overrides the value encoded in the EXEC field of the job definition.
Standard:The EXEC value of the order definition field if the order is defined for CA WA CA 7 Edition; otherwise YES.
(Optional) Specifies that the job should be repeated (run more than once) and defines the amount of time between each iteration. If INTERVAL is specified, the TIME and TYPE keywords are required. If both INTERVAL and COUNT are specified, the INTERVAL multiplied by the COUNT must be less than 24 hours. For information on how the deadline, due date, and submission times are calculated for recurring jobs, see the usage notes.
Standard:none. The job is not repeated.
Limits: hh=1 to 2 numeric characters from 0 to 23
mm=2 numeric characters from 00 to 59
(Optional) Defines the JCL file that contains the execution JCL to be submitted. If used, the value must be a numeric INDEX associated with the desired JCL file (in the JCL statement in the initialization file). If the job is defined in the database, the value must match the value in the DB.1 panel or the optional PARMLIB/Parmlib value in the DB.10 and DB.11 panels. (More information about the initialization file can be found in theSystem Programming Guide.) This field or the JCLLIB field is required if the job is not defined in the database. JCLID and JCLLIB are mutually exclusive.
Note:Attempts to run cross-platform jobs that are not defined for the database fail because they are treated as regular CPU jobs during processing.
Limits:1 to 3 numeric characters from 0 to 254 and from 256 to 999. 255 is reserved.
Necessary:No, unless the job is not defined in the database
(Optional) Defines the JCL file that contains the execution JCL to be submitted. If used, the value must be a symbolic INDEX associated with the desired JCL file (in the JCL statement in the initialization file). If the job is defined in the database, the value must match the value in the DB.1 panel or the optional PARMLIB/Parmlib value in the DB.10 and DB.11 panels. (More information about the initialization file can be found in theSystem Programming Guide.) This field or the JCLID field is required if the job is not defined in the database. JCLID and JCLLIB are mutually exclusive.
Note:Attempts to run cross-platform jobs that are not defined for the database fail because they are treated as regular CPU jobs during processing.
Limits:2 to 16 alphanumeric characters starting with the ampersand (&)
Necessary:No, unless the job is not defined in the database
Note:A dynamic allocation failure for a JCLIB-specified JCL file results in the job entering the request queue in the SKELETON state.
(Optional) Specifies whether notification occurs when the job is late. Specify YES (Y) to allow the job to be marked as LATE. If NO (N) is used, the job will never be marked LATE. The value specified here overrides the value encoded in the PROMPTS field of the job definition.
(Optional) Defines the elapsed time required to process the job. Displays in hours (hh) and minutes (mm) the elapsed time. The maximum value you can specify is 2400.
Standard:1 hour
Limits: hh= 1 to 2 numeric characters from 0 to 24
mm= 2 digits from 00 to 59
(Optional) Specifies the MAINID as defined in the CPU statement of the initialization file to which you want to redirect the job. The value specified here overrides the value encoded in the MAINID field of the job definition. Also, the SASSXX05 user exit does not override this value.
The name must be one of the following values:
- AT
Indicates that all CPUs are acceptable to run the job.
- SYN
Ndefines the CPU to which the job is redirected. The value ofNcan range from 1 to 7.
- /SYN
Ndefines a CPU to which the job is directedcan notbe submitted. The value ofNcan range from 1 to 7.
- -SYN
Ndefines a CPU to which the job is directedcan notbe submitted. The value ofNcan range from 1 to 7.
Limits:Invalid for internal cross-platform jobs.
(Optional) Defines the initial Workload Balancing priority.
Limits:1 to 3 numeric characters from 1 to 255
(Optional) Specifies whether CA WA CA 7 Edition inserts the CA 11 RMS step. Specify YES (Y) to insert the step with CA 11 processing code P. Enter NO (N) to indicate that the RMS step should not be inserted. The value specified here overrides the value encoded in the INSERT-RMS field of the job definition.
Standard:The INSERT RMS value of the job definition field if the job is defined for CA WA CA 7 Edition; otherwise NO.
Limits:Invalid for internal cross-platform jobs.
Note:For more information, seeInterface-Referenzhandbuch.
(Optional) Specifies the condition code (CC) comparison operator or whether to use the step-level #SCC statements in the job's JCL. If specified, this RO overrides the RO defined for the job in the CA WA CA 7 Edition database. The following values are valid:
- EQ
Same
- LT
Less than
- GT
greater than
- GE
Greater than or equal to
- THE
Equal to or less than
- NO
Not to be equated with
- #S
Step condition code tests to be performed based on the #SCC instruction.
Note:For more information, see the #SCC statement inDatabase Maintenance Guide.
- I G
There is no assessment of the work. CA WA CA 7 Edition always assumes that the job will complete successfully, regardless of condition codes, abort codes, or runtime JCL errors.
- 0
No condition code test is performed.
Standard:The job definition panel RO value if the job is defined for CA WA CA 7 Edition; otherwise 0
Limits:Invalid on agent jobs.
Defines the schedule ID within the job's overall schedule definition to use for this run. If omitted, SCHID=1 is assumed unless the job exists in the CA WA CA 7 Edition database and has an associated schedule. In this case, the first SCHID defined in the schedule member is assumed.
Standard:1
Limits:1 to 3 numeric characters from 1 to 255 (see note)
Note:If the SCHEDULE statement specifies SCHID=YES in the initialization file, this parameter is required.
(Optional) Specifies to skip the next scheduled cycle for the job (SKP), disable triggering (NTR), or bypass the database update after the job completes.
- BIP
Indicates that this run of the job will replace the next scheduled run. This value has the same effect as entering NXTCYC,SET=SKP. It is reflected in the output of LJOB and LLOCK commands as if NXTCYC,SET=SKP was used. This parameter is invalid if the job has no schedule. SET=SKP has no effect on recurring jobs already in the CA WA CA 7 Edition queues.
- NTR
Specifies that normal triggering is disabled only for this run of the job.
- NDB
Allows a job to bypass all load processing at job termination, but allows other processing to continue normally.
Note:Record triggering is still in effect.
(Optional) Defines the time after which the job will not be repeated. STOP is ignored if INTERVAL is not specified. If both COUNT and STOP are specified, the job will no longer be repeated when either COUNT reaches zero or the STOP time is reached, whichever comes first.
If the STOP time is less than the transmit time, the stop date is assumed to be the following day.
Standard:1439 minutes (24 hours minus 1 minute) after airtime
Limits: hh=1 to 2 numeric characters from 0 to 23
mm=2 numeric characters from 00 to 59
(Optional) Defines an airtime requirement for the job. When the format with a + is used, the delivery time is calculated from the current time, adding the specified number of hours and minutes. If the + is used, the DATE keyword must be omitted.
Limits:+ is optional
hh= 1 to 2 numeric characters from 0 to 23
mm= 2 digits from 00 to 59
Necessary:No (unless DATE is used, if so, specify DOTM or TIME (HmmmFormat). Also required if TYPE=CLOCK is specified.
(Optional) TYPE=RES specifies that the job is scheduled in restart/retry state.
TYPE=CLOCK, START or END controls how the airtime requirement is calculated for repetitive jobs.
With TYPE=RES, the job with a restart request is placed in the request queue. The job will not be submitted until the CA WA CA 7 Edition restart is complete. The output networks are scheduled, but the input requirements validation is bypassed.
TYPE=CLOCK, START or END is ignored if INTERVAL is not specified. With TYPE=CLOCK, the interval is added to the airtime request of the previous iteration to determine the new airtime request. With TYPE=START and END, the interval is added to the last (most recent) start or end time of the previous iteration to determine the new airtime request. TYPE is required if INTERVAL is specified.
Limits:RES, CLOCK, START or END
FAQs
What is not enough goods and services available to meet demand? ›
Scarcity is one of the key concepts of economics. It means that the demand for a good or service is greater than the availability of the good or service. Therefore, scarcity can limit the choices available to the consumers who ultimately make up the economy.
What are the three economic questions answered? ›An economic system is any system of allocating scarce resources. Economic systems answer three basic questions: what will be produced, how will it be produced, and how will the output society produces be distributed? There are two extremes of how these questions get answered.
What means not having enough resources to satisfy every need? ›Scarcity is not having enough resources to satisfy every need or want.
What are the three big questions in economics? ›Economists address these three questions: (1) What goods and services should be produced to meet consumer needs? (2) How should they be produced, and who should produce them? (3) Who should receive goods and services? The answers to these questions depend on a country's economic system.