The COMM EOJ option informs the MUF that processing is to end. After receiving an EOJ request, it is acknowledged with message DB00247I - EOJ REQUESTED, NO NEW CONNECTIONS, EOJOFF AVAILABLE, and the MUF does not allow any new jobs to start processing. MUF allows jobs in progress to continue. The MUF goes to EOJ when the last job completes. A job is considered complete when all open User Requirements Tables have been closed.
There are exceptions to the closing of User Requirements Tables (URT) to support special situations. There is a URT option on the DBURSTR Macro named EOJ_OK that can be set to YES for a Job connected to MUF having a single task area. The details of the keyword are documented with the URT description. If the requirements are met, as part of EOJ detection the Job can be set as missing and the task area be set to close its URT, thereby moving the EOJ to closer execution. A second ability exists for Job connections that use multiple task areas known as EOJ_OK_S, (see the information about Extended Options Entry Processing in the CA Datacom/DB Database and System Administration Guide).
It is at the point of the URT closings that the EOJ is committed, noted with message: DB00243I - EOJ COMMITTED, EOJOFF DISABLED.
When the MUF is terminated an EOJ report is written to the .when 'CS7' insert SYSPRINT file. The report contains information about the following:
No other COMM function, except the COMM EOJOFF console command, is accepted by the MUF after this option is initiated. Once an EOJ request is accepted by the MUF, the request can only be canceled with the COMM EOJOFF command. Unless EOJOFF is used, the MUF must be allowed to complete termination processing. See the CA Datacom/DB Database and System Administration Guide for details about using EOJOFF. After the MUF is started again, new jobs can be executed.
Online systems must initiate a close request for each User Requirements Table opened.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|