IBM Support

C:D HP NonStop and RUN JOBs

Technical Blog Post


Abstract

C:D HP NonStop and RUN JOBs

Body

NonStop does actually support a RUN JOB, though it is not named as such.

If you submit a RUN TASK as 'nowait', the session manager launches it, reports success or failure of the startup of the task, and moves on to the next step. At that point the task is no longer associated with the C:D process.

Here is a simple example. A little test program called WAIT takes as an argument the number of seconds to wait after startup, then shuts down.  Here it is written as a run task, nowaited:

RUNJOB   PROCESS  SNODE=XXX

RUNJOB   RUN TASK PNODE PGM=WAIT -
                  SYSOPTS="/name $WAIT,nowait/ 30"


When the RUN TASK is executed,  the task will start as process $WAIT, the C:D process will complete and the $WAIT process will run on its own, execute for 30 seconds, then shut down.

 

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4PJT","label":"IBM Sterling Connect:Direct"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

UID

ibm11123503