Friday 15 June 2012

Difference Between Demand And Run


Difference Between Demand And Run:

The main Deference is if we use demand the whole batch moving in to request Queue.
But if we use Run Then only that job will move to  request Queue.

There are two commands available which manually bring jobs into the Request Queue.
They are ‘DEMAND’ and ‘RUN’.

The ‘DEMAND’ command is used to schedule on-request work (recoveries, restores, user requested jobs, etc.). When used , any requirements defined for the job will be honored, and when the job terminates successfully, any triggers defined in the data base will be performed and requirements will be satisfied for other jobs.

The format of the ‘DEMAND’ command is:
DEMANDH, JOB=jobname
The ‘H’ on the end of the command instructs CA-7 to put the job on hold in the Request Queue. The ‘H’ is optional. However, if you demand in a job that does not have any requirements, the job will immediately submit to JES.
If you do not want the trigger processing to take place, ‘SET=NTR’ must be added to the command.

The ‘RUN’ command is used to schedule additional runs of a job and reruns (jobs that have completed successfully and are no longer in a CA-7 queue). The ‘RUN’ command will not do what the ‘DEMAND’ command does. No requirements are honored, triggers will not be performed and requirements will not be satisfied for other jobs.

The format of the ‘RUN’ command is:
RUNH, JOB=jobname, SCHID=nnn
The ‘H’ on the end of the command instructs  CA-7 to put the job on hold in the Request Queue. The ‘H’ is optional. However, if you demand in a job that does not have any requirements, the job will immediately submit to JES.

1 comment:

  1. Running a job will not show it's log file, but demanding a job will do.

    We can check the logs by LRLOG,JOB=JOBNAME. Is it correct ??

    ReplyDelete