Version 14.0 › CA Datacom Tools Products › New Features and Enhancements › URT option EOJ_OK

URT option EOJ_OK

Under normal processing, a MUF is intended to be enabled 24x7 starting during the IPL process and ending just prior to the next IPL. If the EOJ is needed, then it was built to be orderly where all connections to the MUF have been closed and disconnected. Therefore, the EOJ naturally waits on all current jobs.

For many releases, there has been an exception where connections through CA SYSVIEW have been allowed to be forced ended during an EOJ request. This ability also exists for the Change Data Capture (CDC) facility.

With Version 14.0, these exceptions are formally changed to be a specific option, EOJ_OK. This parameter is set in the DBURSTR macro generating a User Requirements Table used to connect to a MUF. The requirement is considered to be rare and the feature is not intended to be commonly used. It has a number of restrictions and presents special considerations for the applications running with the option set.

The following are a few restrictions for the EOJ_OK parameter:

• Meant for single task applications.
• Is not allowed for applications such as CA Datacom CICS Services and CA Datacom Server that connect to MUF with multiple task areas.
• Is for read-only applications, but updating is allowed, subject to certain rules.
• Is not intended for applications that have multiple URTs, but is allowed with certain rules.

For more information, see the DBURSTR parameter EOJ_OK in the CA Datacom/DB Database and System Administration Guide.

An independent but related change is a similar, but different option for applications that have multiple URTs known as EOJ_OK_S. For Extended Options Programming, see that chapter in the CA Datacom/DB Database and System Administration Guide.