Reason:
Run unit nnnnn of job jjjjjjjj successfully completed CA Datacom/DB processing. The displayed job name is derived from the job card. The run unit number is assigned by CA Datacom/DB. (A run unit ends when a task, which has only one User Requirements Table open, closes that User Requirements Table. A new run unit starts if the task reopens the same or a different User Requirements Table.)
Note: If the connection by the application to the CA Datacom/DB MUF is not successful, it is possible to see this message with a value of 0 for NUMBER representing the run unit.
In z/OS, if the specified job was an application that used XCF to communicate with MUF, ttt will be XCF, and ssssssss is the name of the originating z/OS system. If the specified job was an application that used CAICCI to communicate with MUF, ttt will be CAICCI, and ssssssss is the CAICCI name of the originating z/OS system.
The message occurs in the Multi-User Facility region for jobs which have done maintenance logged to the Log Area (LXX). The message may be useful in case backward recovery is required. For Multi-User Facility jobs that do not do maintenance to the Log Area, the message does not occur unless so specified in the MUF MUF startup option. The message does not occur during Single User, including DBUTLTY functions that run as Single User.
Action:
None. This message is for information only.
|
Copyright © 2014 CA.
All rights reserved.
|
|