The following messages are issued by the batch request utility:
The CBKPRINT DDNAME is missing from the batch request utility JCL. The batch request utility cannot run without the CBKPRINT data set.
The batch request utility terminates.
Add the CBKPRINT DD statement to the batch request utility job step and resubmit the job.
Message log
The batch request utility has failed to open the CBKPRINT DDNAME data set, which is required for the batch request utility to run.
The batch request utility terminates.
Check the job log for additional MVS™ messages relating to this error, take the corrective action recommended by those messages, and resubmit the job.
Message log
The CBKIN DDNAME is missing from the batch request utility job step. The batch request utility cannot run without the CBKIN data set.
The batch request utility terminates.
Add the CBKIN DD statement to the batch request utility job step and then resubmit the job.
Message log.
The batch request utility has failed to open the CBKIN data set, which is required in order for the batch request utility to run.
The batch request utility terminates.
Check the job log for additional MVS messages relating to the error, take the corrective action recommended by those messages, and resubmit the job.
Message log
The batch request utility is unable to obtain the virtual storage needed to process its input requests.
The batch request utility terminates.
Check the REGION parameter for the batch request utility job step. The REGION parameter specifies how much virtual storage is allocated for the batch request utility. If possible, increase the value to make additional virtual storage available to the batch request utility. If it is not possible to increase this value, examine the input statements to the batch request utility to determine the best way to break the current job step into multiple job steps.
Message log
At least one input statement has an error that prevents the statement from being executed. When this condition occurs, the batch request utility does not execute any of the statements.
The batch request utility terminates without executing any of the input statements.
Examine the Message log to determine which statements have errors. Correct those errors and resubmit the JCL.
Message log.
An error has occurred while processing the request. This error prevents the request from completing successfully. The object and objecttype fields indicate the object and object type on which the error occurred. The errortext field, if any, provides additional information regarding the nature of the error. If the error occurs while accessing the CICS® region control file, the vsamcode field is non-zero. If the error occurs while processing a CICS API command, resp1 and resp2 contain the CICS EIB response codes for the command.
The current request is not successfully completed. All subsequent requests are skipped and the batch request utility terminates.
Contact technical support.
Message log
This command is not executed due to an error in one or more previous statements.
The current command is not executed.
Examine the message log for any errors prior to the current command. Correct those errors and resubmit the job step.
Message log
The batch request utility has executed the current statement without any errors. If the request was passed to a target CICS region for execution, it means also that the CICS BAC request server has executed the command successfully.
The batch request utility proceeds on to the next input statement.
None.
Message log
The DEFAULT statement has been successfully processed. The DEFAULT values for subsequent statements have been updated.
The batch request utility proceeds on to the next input statement using the applicable parameter values from this DEFAULT statement.
None.
Message log
A LINK PROGRAM or RUNCEMT command has been successfully completed and the data returned from that request is formatted in a standard dump format. Note that the returned data is dependent upon the program or CEMT command being executed. If more than 256 bytes of data are returned, only the first 256 bytes are dumped to the message log.
The returned data from that request is formatted in a standard dump format and written to CBKPRINT.
None.
Message log
The batch request utility is about to display the parameter definitions for the current command. The utility displays each parameter in a separate CBKxx5013I message, showing the values in effect for the command. If the command contains no parameters, the utility does not display any CBKxx5013 messages.
None.
None.
Message log
The batch utility displays a parameter and value pair, keyword (value) of the current command it is processing.
None.
Ensure that the parameter and its value are correct for the current statement. Note that the source of the parameter might be the current statement itself or the most recent DEFAULT statement.
Message log
A problem has occurred while processing the request that might have prevented the execution of the command from having the required results. The object and objecttype fields indicate the object and object type on which the problem occurred. The errortext field, if any, provides additional information regarding the nature of the problem. If the problem has occurred while accessing the CICS region control file, then the vsamcode field is non-zero. If the problem has occurred while processing a CICS API command, resp1 and resp2 contains the CICS EIB response codes for the command.
The current request might not have completed successfully. The batch request utility continues on to the next request.
Contact technical support.
Message log
The batch request utility has to directly update a CICS region control file because CICS BAC is not active in the CICS region. However, the batch request utility doesn't know the name of the control file data set because it cannot locate a control file table, or the control file table it located is empty.
The batch request utility job step abends with abend code U1503.
The batch request utility requires a control file table containing an entry for the target CICS region to find the data set name for the target region control file. For more information about the control file table, see The control file table. Ensure that a control file table that contains an entry for the target CICS region is available to the batch request utility job step, and retry the job step.
Job log
The batch request utility is unable to allocate dynamically the CICS BAC audit log. This message can be preceded by one or more messages that provide additional information relating to the dynamic allocation failure.
The batch request utility job step terminates with condition code 12.
If you cannot determine and correct the cause of the dynamic allocation failure, contact technical support.
Job log
The batch request utility is unable to open the CICS BAC audit log. This message can be preceded by one or more messages that provide additional information relating to the open failure.
The batch request utility job step terminates with condition code 12.
If you cannot determine and correct the cause of the open failure, contact technical support.
Job log
The batch request utility needs to log requests, but there is no CBKLOG data set DD statement in the job step JCL, and the options that enable the batch request utility to allocate dynamically the audit log are not specified.
The batch request utility job step terminates with condition code 12
Define an audit log data set in the batch request utility job step JCL or change the appropriate CICS region properties record to enable the audit log to be allocated dynamically.
Job log
The batch request utility needs to update the target CICS region control file directly because CICS BAC is not active in the region. However, the batch request utility detected an invalid control file during its control file validation processing. Messages providing additional information about the problem with the control file can precede this message.
The batch request utility job step abends with abend code U1502.
If you cannot determine and correct the cause of the problem, contact technical support.
Job log
During batch request utility initialization, CICS BAC has attempted to load the CICS EXCI module DFHXCPRX to check that the CICS SDFHEXCI load library is available. The load request has failed with the errors indicated by retcode and rsncode, which contain the return code and reason code from the failed load attempt.
The batch request utility job step terminates with condition code 12.
Ensure that the CICS SDFHEXCI load library is available to the batch request utility by adding it to the MVS linklist, or to the JOBLIB or STEPLIB concatenation in the batch request utility JCL.
Job log
The batch request utility has received confirmation that the commands it passed to the CICS BAC request server for CICS region applid have been processed. The commands are listed in the message log immediately following the CBKxx5021I message.
The batch request utility lists the commands that have been processed by the request server.
None.
Message log
The batch request utility is unable to send commands to CICS region applid, because the region is not active, or because CICS BAC is not active in the region. The batch request utility has serviced the listed commands directly itself. The commands are listed in the message log immediately following the CBKxx5022I message.
The batch request utility lists the commands that it has serviced.
None.
Message log
The batch request utility has detected that CICS BAC is not active in CICS region applid (or the CICS region is not available), and that CICS BAC did not go through its normal termination the last time it was active in the region. The region properties for CICS region applid specify that the batch request utility should wait for an operator reply to determine how to proceed.
The batch request utility issues message CBKxx5024R to prompt for a reply to this message.
See message CBKxx5024R.
Console
The batch request utility has issued message CBKxx5023W and now prompts for a answer on how to proceed.
The batch request utility waits for a GO or ABEND reply.
See message CBKxx5023W for a an explanation and reply accordingly
Console
The batch request utility has received a GO reply to message CBKxx5024R.
The batch request utility job step continues.
None.
Console
The batch request utility has received an ABEND reply to message CBKxx5024R.
The batch request utility job step abends with user abend code abend-code. No additional commands are processed.
Depending on the situation, you might need to restart CICS BAC in the CICS region and then shut it down to reset the shutdown flag.
Console
CICS BAC did not go through normal shutdown processing the last time it was active in CICS region applid. The region properties for the target region specify that a batch request utility job step should be abended when this condition occurs.
The batch request utility job step abends with the abend code specified in the target CICS region properties record.
Depending on the situation, you might need to restart CICS BAC in the CICS region and then shut it down to reset the shutdown flag.
Message log
CICS BAC did not go through normal shutdown processing the last time it was active in CICS region applid. The region properties for the target region specify that a batch request utility job step should be terminated when this condition occurs.
The batch request utility job step terminates with the condition code specified in the target CICS region properties record.
Depending on the situation, you might need to restart CICS BAC in the CICS region and then shut it down to reset the shutdown flag.
Message log
The batch request utility is unable to issue a command because the current user ID is not authorized. See the z/OS Security Server RACROUTE Macro Reference manual, SA22-7692, for an explanation of the return and reason codes.
The current request has not successfully completed. All subsequent requests are skipped and the batch request utility terminates.
Contact your RACF administrator if you believe the batch request utility user ID should be authorized to issue the command.
CBKPRINT file.