Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Restarting after an abnormal application termination

openUTM offers the option of an automatic restart after an abnormal application termination.

The product JV “Job Variables” is a prerequisite for the procedure outlined below.

If a job variable is cataloged with the base name of the KDCFILE (KDCA, including catid and userid), this job variable is used by openUTM.

The first position of the job variable can have the value R or T:

R:

UTM application is running

T:

UTM application is terminated

The second position of the job variable can have the value N or A:

N:

Normal termination

A:

Abnormal termination

These job variables can be used to monitor the execution of a UTM application using an ENTER job which restarts the application if the application terminates abnormally. If the first column of the job variable contains the value “T”, the value of the second job variable column determines whether this ENTER job is terminated (with ‘N’) or the UTM application is restarted (with ‘A’).

The ENTER job can be structured as follows:

/SET-LOGON-PARAMETERS 
/.WAIT1 REMARK
/WAIT-EVENT UNTIL=*JV(CONDITION=((jobvariable-name,1,1)='T'), -
/           TIME-LIMIT=32767,TIMEOUT-LABEL=WAIT1) 
/SKIP-COMMANDS TO-LABEL=END,IF=*JV(CONDITION=((jobvariable-name,2,1)='N')) 
/ENTER-JOB enterfile,CPU-LIMIT=ttt,JOB-CLASS=job-class 
/WAIT-EVENT UNTIL=*JV(CONDITION=((jobvariable-name,1,1)='R'))
/WAIT-EVENT UNTIL=*JV(CONDITION=*NONE,TIME-LIMIT=600,TIMEOUT-LABEL=WAIT2)
/.WAIT2 REMARK
/SKIP-COMMANDS TO-LABEL=END,IF=*JV(CONDITION=((jobvariable-name,1,2)='TA')) 
/SKIP-COMMANDS TO-LABEL=WAIT1
/.END REMARK
/EXIT-JOB 

Description of the ENTER job

  • The first WAIT-EVENT command instructs the job to wait until the UTM application has terminated (‘T’ in the first field of the job variable). If the application terminated abnormally (‘A’ in the second field of the job variable), the ENTER job is initiated to restart the UTM application; with a normal termination, the monitoring job is also terminated.

  • With the second WAIT-EVENT command, the job waits until the UTM application is running again.

  • With the third WAIT-EVENT command, the job waits for ten minutes (600 sec) until a query is issued as to whether the UTM application has terminated abnormally again. If so, the monitoring job is terminated and the UTM application is not restarted. If not, the system branches to the first WAIT-EVENT and the monitoring job lies in wait again. This prevents the UTM application from continuously terminating and restarting in the event of a permanent error.