Messages BMC74200 through BMC74299

This group includes messages for the

BMC AMI Application Restart Control

and BATCH CONTROL FACILITY products.

Number

Description

BMC74200W

THE type CALL TRACE IS INACTIVE. TERMINATION CANNOT BE SCHEDULED ON BEHALF OF requestor.

Explanation: The SET TRACE OFF command was issued, but APPLICATION RESTART CONTROL (AR/CTL) enhanced call tracing is not active for the given type of subsystem. Therefore, termination of enhanced call tracing cannot be scheduled on behalf of the given requestor.

User response: No action is required.

BMC74201W

THE type CALL TRACE IS ACTIVE. COMMENCEMENT CANNOT BE SCHEDULED ON BEHALF OF requestor.

Explanation: The SET TRACE ON command was issued, but APPLICATION RESTART CONTROL (AR/CTL) enhanced call tracing is already active for the given type of subsystem. Therefore, start of enhanced call tracing cannot be scheduled on behalf of the given requestor.

User response: No action is required.

BMC74202I

COMMENCEMENT OF THE type CALL TRACE HAS BEEN SCHEDULED ON BEHALF OF requestor AFTER c-number FOR t-number CALLS.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) has scheduled enhanced call tracing to start on behalf of the given requestor. The trace of application program calls for the given type of subsystem will start after the given number (c-number) of application program calls and continue for the given number of application program calls (t-number).

User response: No action is required.

BMC74203E

DYNAMIC ALLOCATION OF THE SNAP DUMP FILE RETURNED CODE returnCode

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to dynamically allocate the snap dump data set, but the allocation failed. This message displays the return code that AR/CTL received. The accompanying message BMC74204E displays the error reason code and the information reason code returned from the dynamic allocation request. AR/CTL also issues message BMC74204E, then abnormally terminates the task with abend U1771 and reason code X'00074203'.

User response: Refer to the Dynamic Allocation Parameter List report (found under ddname ARCDYNPR). Using the return code from this message and the error reason code and information reason code from message BMC74204E, see the appropriate IBM manual to determine the cause of the error and the corrective action to take.

BMC74204E

DYNAMIC ALLOCATION RETURNED ERROR REASON CODE errorReasonCode AND INFORMATION REASON CODE informationReasonCode.

Explanation: This message, which accompanies message BMC74204E, displays the error reason code and the information reason code returned from the dynamic allocation request.

User response: For information, see the user response for message BMC74203E.

BMC74205E

SNAP DUMP OF VIRTUAL STORAGE nn ON BEHALF OF requestor RETURNED RETURN CODE returnCode.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to perform the given snap dump of virtual storage for the current task on behalf of the given requestor. AR/CTL received the indicated return code.

User response: No action is required.

BMC74206I

THE CURRENT REGION IS BEING TERMINATED AFTER CHECKPOINT chkpid ON BEHALF OF requestor.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) abnormally terminates the current task after the given checkpoint on behalf of the given requestor. The task terminates with abend U1771 and reason code X'00074206'.

User response: No action is required.

BMC74207I

THE CURRENT REGION IS BEING TERMINATED AFTER A type DL/I CALL ON BEHALF OF requestor.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) abnormally terminates the current task after the given type of application program DL/I call on behalf of the given requestor. The task terminates with abend U1771 and reason code X'00074207'.

User response: No action is required.

BMC74208I

TERMINATION OF THE DL/I CALL TRACE WAS COMPLETED ON BEHALF OF requestor.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) has completed termination of enhanced call tracing of the application program calls on behalf of the given requestor.

User response: No action is required.

BMC74209I

COMMENCEMENT OF THE DL/I CALL TRACE WAS COMPLETED ON BEHALF OF requestor.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) has started enhanced call tracing of the application program calls on behalf of the given requestor.

User response: No action is required.

BMC74210I

NORMAL TERMINATION PROCESSING WILL BE IGNORED AS REQUESTED BY THE APPLICATION RESTART CONTROL MERGED OPTIONS.

Explanation: As specified in the merged options in the APPLICATION RESTART CONTROL (AR/CTL) directory, AR/CTL will not perform normal termination processing. Normal termination processing includes deletion of active job step member and deletion of the checkpoint data set.

User response: No action is required.

BMC74211I

THE CURRENT REGION IS BEING TERMINATED AFTER A type DL/I CALL ON BEHALF OF exitName.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) is terminating the current task after the given type of application program DL/I call on behalf of the named checkpoint pacing user exit routine (exitName).

User response: No action is required.

BMC74212E

FUNCTION function IS NOT PERMITTED IN THE NATIVE ENVIRONMENT.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) does not allow the application program call to issue the given function code in IMS-compatible mode. The following function codes are valid in IMS-compatible mode:

CHKP
CLSE
GN
GU
ISRT
OPEN
ROLB
ROLD
ROLL
TERM
XRST

AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074212'.

User response: Correct the application program call to use a valid function code.

BMC74213E

BMP RESTART AND APPLICATION RESTART CONTROL CANNOT COEXIST IN THE SAME REGION.

Explanation: BMP RESTART was detected in the same region in which APPLICATION RESTART CONTROL (AR/CTL) was executing. BMP RESTART and AR/CTL cannot co-exist in the same region. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074213'.

User response: Remove BMP RESTART from the region in which AR/CTL is installed.

BMC74214I

AR/CTL WILL ATTEMPT RESTART IN A NATIVE ENVIRONMENT FOR JOB jobName, STEP stepName, PSB OR ASB

Explanation: APPLICATION RESTART CONTROL (AR/CTL) will attempt to perform restart in the native environment for the indicated job and step. Accompanying message BMC74215I displays the program specification block (PSB) name or application specification block (ASB) name and checkpoint identifier for which restart is to be attempted.

User response: No action is required.

BMC74215I

NAME name, AND APPLICATION PROGRAM NAME program AT CHECKPOINT IDENTIFIER chkpID.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) will attempt to perform restart in the native environment for the job and step displayed in accompanying message BMC74214I. This message displays the program specification block (PSB) name or application specification block (ASB) name and checkpoint identifier for which restart is to be attempted.

User response: No action is required.

BMC74216E

AR/CTL NATIVE ENVIRONMENT SUPPORTS ONLY EXTENDED CHECKPOINTS.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) supports only extended checkpoints, not simple checkpoints. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074216'.

User response: Modify the application program to issue extended checkpoint calls only.

BMC74218E

CONNECTION WITH DB2 SUBSYSTEM ssid RETURNED CODE returnCode AND REASON CODE reasonCode.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted connection with the indicated DB2 subsystem. The attempt was not successful, and AR/CTL received the indicated return code and reason code. AR/CTL abnormally terminates the task with abend U1776 and reason code X'00074218'.

User response: For an explanation of the return code and reason code in this message, see the appropriate IBM manual. Review the JES message log and the data set containing unsolicited status messages for the DB2 Call Attach Facility (found under ddname DDOTV02). Take corrective action as indicated by the messages and codes.

BMC74219E

OPEN OF DB2 SUBSYSTEM ssid PLAN plan RETURNED CODE returnCode AND REASON CODE reasonCode.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to open the indicated plan in the given DB2 subsystem. The attempt was not successful, and AR/CTL received the indicated return code and reason code. You might receive this message when you use the Automatic Checkpoints and Trigger Cursor Name processing options to take checkpoints based on fetch counts of a cursor. This message is generated if the AR/CTL plan ARCTLP$3 (installation default), was not found on the DB2 system. You must run the install job $Q06BDGT on every system where AR/CTL will run and must use the same plan name in every DB2 system. AR/CTL abnormally terminates the task with abend U1785 and reason code X'00074219'.

User response: For an explanation of the return code and the reason code in this message, see the appropriate IBM manual. Review the JES message log and the data set containing unsolicited status messages for the DB2 Call Attach Facility (found under ddname DDOTV02). Take corrective action as indicated by the messages and codes.

BMC74220E

CLOSE OF DB2 SUBSYSTEM ssid PLAN plan RETURNED CODE returnCode AND REASON CODE reasonCode.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to close the indicated plan in the given DB2 subsystem. The attempt was not successful, and AR/CTL received the indicated return code and reason code. AR/CTL abnormally terminates the task with abend U1776 and reason code X'00074220'.

BMC74221E

DISCONNECTION WITH DB2 SUBSYSTEM ssid RETURNED CODE returnCode AND REASON CODE reasonCode.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted disconnection with the indicated DB2 subsystem. The attempt was not successful, and AR/CTL received the indicated return code and reason code. AR/CTL abnormally terminates the task with abend U1776 and reason code X'00074221'.

BMC74222E

CALL ATTACH FACILITY LANGUAGE INTERFACE interface FOR DB2 SUBSYSTEM ssid AND PLAN plan.

Explanation: The given language interface is invalid for the indicated DB2 subsystem and plan. The only valid language interfaces are SQL and IFC. APPLICATION RESTART CONTROL (AR/CTL) abnormally terminates the task with abend U1776 and reason code X'00074222'.

BMC74223E

OPEN OF DB2 DDITV02 INPUT DATA SET RETURNED CODE returnCode.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to open the DB2 DDITV02 input data set. The attempt was not successful, and AR/CTL received the indicated return code. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074223'.

User response: Review the JCL statements for a valid DDITV02 DD statement.

BMC74224E

OPEN OF DB2 DDITV02 INPUT DATA SET WAS NOT SUCCESSFUL.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to open the DB2 DDITV02 input data set, but was not successful. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074224'.

User response: Review the JCL statements for a valid DDITV02 DD statement.

BMC74225E

CLOSE OF DB2 DDITV02 INPUT DATA SET RETURNED CODE returnCode.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to close the DB2 DDITV02 input data set. The attempt was not successful, and AR/CTL received the indicated return code. This message indicates an internal processing error. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074225'.

User response: Save the SYSUDUMP data set and JES message log for this job, and contact BMC Customer Support.

BMC74226E

CLOSE OF DB2 DDITV02 INPUT DATA SET WAS NOT SUCCESSFUL.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to close the DB2 DDITV02 input data set, but was not successful. This message indicates an internal processing error. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074226'.

User response: Save the SYSUDUMP data set and JES message log for this job, and contact BMC Customer Support.

BMC74227I

ASAM INTERNAL LOGIC ERROR, REASON= reasonCode, DDN= ddname

Explanation: APPLICATION RESTART CONTROL (AR/CTL) detected an unexpected internal logic error for the given application sequential access method (ASAM) data set. The indicated reason code is for BMC internal use only. AR/CTL terminates the task abnormally with abend U1770.

User response: Save the SYSDUMP data set and the JES message log for this job, and contact BMC Customer Support.

BMC74228I

BLOCK COUNT REPOSITION USED, REASON= reasonCode, DDN= ddname

Explanation: During restart processing for the given application sequential access method (ASAM) data set, APPLICATION RESTART CONTROL (AR/CTL) determined that standard repositioning techniques cannot be used because they might result in a failure to correctly reposition the data set. Instead of using high speed reposition techniques, AR/CTL will read the data set block by block until the correct restart position is reached. The reason code indicates why normal reposition techniques could not be used:

01 indicates that the data set is not on the same volume as it was during the previous execution.

This condition normally occurs if the data set has been moved. The data set movement might have occurred because of Storage Management Subsystem (DFSSMS) migration, use of the ASAM Copy utility, or other reasons. DFSSMS and the ASAM Copy utility preserve the number and relative position of the blocks. The data set must not be moved using other techniques (such as IEBGENER) that can reblock the data set. If reblocking occurs, data set repositioning might not be successful. Processing continues, and the data set is repositioned for application restart.

User response: No action is required.

BMC74229I

UNABLE TO OPEN DATA SET, REASON= reasonCode, RC= returnCode, DDN= ddname

Explanation: APPLICATION RESTART CONTROL (AR/CTL) could not open the given data set. The reason code indicates why open processing could not be performed. The following reason codes are possible:

Reason code	Description
01	The job step JCL did not contain a DD statement for the data set.
02	A nonzero return code was returned by the RDJFCB macro.
03	A nonzero return code was returned by the OPEN macro.
04	The locate mode buffer is too small.
05	The block size was not a multiple of the logical record length for a fixed-format data set.
06	During OPEN processing, the AR/CTL action module has determined that the file with the specified ddname was already open.
07	The data set was allocated as a temporary data set.
08	The data set being opened for repositioning has a disposition of NEW (DISP=NEW). A data set with a disposition of NEW cannot be opened for repositioning.

The return code provides the return code from the MVS service that failed. Processing continues, and the file characteristics block (FCB) for the data set is marked with a permanent error. The application receives a status or return code indicating that the data set could not be opened.

User response: Correct the problem identified by the reason and return codes in the message. Have the job step listing available if you contact BMC Customer Support.

BMC74230I

ASAM SERVICE ROUTINE FAILURE, REASON= reasonCode, RC= returnCode, DDN= ddname

Explanation: While processing a request for the given application sequential access method (ASAM) data set, APPLICATION RESTART CONTROL (AR/CTL) received a bad return code from either an ASAM or MVS service request. The reason code identifies the service that failed. The following values are possible:

Reason code	Description
01	A bad return code was received from the MVS POINT macro.
02	A bad return code was received from the MVS SYNCDEV macro.
03	A bad return code was received from the MVS NOTE macro.

User response: Correct the problem identified by the reason and return codes in the message. Have the job step listing available if you contact BMC Customer Support.

BMC74231I

ASAM RESTART FAILED, REASON= reasonCode, RC= returnCode, DDN= ddname

Explanation: While APPLICATION RESTART CONTROL (AR/CTL) attempted restart processing for the given application sequential access method (ASAM) data set, an error occurred that made restart impossible. The reason code indicates why restart processing failed or cannot be continued. The following reason codes are possible:

Reason code	Description
01	A mismatch was found in the number of ASAM data sets at restart. Either a data set that was present in the previous execution was missing for the current execution, or a data set was present in the current execution that did not exist in the previous execution.
02	An invalid condition was detected for the ASAM data set that was being repositioned during restart. See the return code descriptions for additional information about the invalid condition that was detected.

The return code provides additional information about why restart failed. The following return codes are possible:

Return code	Description
01	A data set present in the previous execution was missing from this execution.
02	This execution contains a data set not present in the previous execution because a new file characteristics block (FCB) was added.
03	A data set present in this execution does not reside on the same device category (DASD, tape, SYSIN, SYSOUT, and so on) as the original data set.
04	The data set being repositioned does not have the same block size as the original data set.
05	The data set being repositioned does not have the same record format as the original data set.
06	The data set being repositioned requires a block count restart for correct repositioning, but the application issued a GU call during the previous execution. The use of the GU call prevents AR/CTL from doing a block count restart.
07	Since the job step abended, the number of concatenated data sets has been reduced to one, causing the subsequent restart to fail. After a job step abends, the number of concatenated data sets can increase before a restart occurs, but the number cannot decrease.
08	The number of data sets in the concatenation is less than in the previous execution.
09	The data set cannot be repositioned because it is empty or does not contain the number of records needed for repositioning.
0A	The data set cannot be repositioned because an I/O error was encountered while AR/CTL was trying to read the first or second block.

Processing terminates abnormally.

User response: Correct the problem identified by the reason and return codes in the message. Have the job step listing available if you contact BMC Customer Support.

BMC74232I

UNABLE TO OBTAIN DATA SPACE, REASON= reasonCode, RC= returnCode, DDN= ddname

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to obtain a data space for the given application sequential access method (ASAM) data set that was specified as using output staging. The following reason codes indicate why the data space could not be obtained:

Reason code	Description
01	The system is not MVS/ESA and does not support data spaces.
02	A bad return code was received from the MVS DSPSERV macro.
03	A bad return code was received from the MVS ALESERV macro.
04	The number of blocks requested for the data space was zero.

The return code provides the return code from the MVS service that failed. Processing continues, and the file control block (FCB) is marked as not using output staging.

User response: Correct the problem identified by the reason and return codes in the message. Have the job step listing available if you contact BMC Customer Support.

BMC74233I

UNABLE TO FREE DATA SPACE, REASON= reasonCode, RC= returnCode, DDN= ddname

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to free a data space for the given application sequential access method (ASAM) data set that was specified as using output staging. The following reason codes indicate why the data space could not be freed:

Reason code	Description
01	A bad return code was received from the MVS DSPSERV macro.
02	A bad return code was received from the MVS ALESERV macro.

The return code provides the return code from the MVS service that failed. Processing continues, but the data space is not freed.

User response: Correct the problem identified by the reason and return codes in the message. Have the job step listing available if you contact BMC Customer Support.

BMC74234I

CLOSE FAILED FOR DATA SET, TYPE= type, RC= returnCode, DDN= ddname

Explanation: While attempting to close an application sequential access method (ASAM) data set, APPLICATION RESTART CONTROL (AR/CTL) received a bad return code from the close macro. The message also indicates the type of close request that was being processed. The following close requests are possible:

Type of close request	Description
01	Normal close operation
02	Temporary close operation

The file is marked in error. For IMS or IMS-compatible modes, the application receives an AI status code. When AR/CTL provides sequential support through call interception, the SYNAD routine for the data control block (DCB) is entered if present. The task abnormally terminates if no SYNAD routine is present.

User response: Correct the problem identified by the return code in the message. Have the job step listing available if you contact BMC Customer Support.

BMC74235I

ASAM/VSAM FILE INTERCEPT ERROR, RE= reasonCode, DDN= ddname

Explanation: While intercepting application read or write requests for the given application sequential access method (ASAM) or VSAM data set, APPLICATION RESTART CONTROL (AR/CTL) encountered an unrecoverable error. The following reason codes indicate the error that was detected:

Reason code	Description
01	The ASAM controller encountered an I/O error on an ASAM data set and could not recover from the error.
02	The ASAM controller found that an ASAM data set had been opened before the restart call.
03	The VSAM controller found that a VSAM file had been opened before the restart call.

Processing terminates abnormally.

User response: Correct the problem identified by the reason code in the message. Have the job step listing available if you contact BMC Customer Support.

BMC74236I

OUTPUT STAGING AREA ERROR, RE= reasonCode, DDN= ddname

Explanation: The output staging area for the given application sequential access method (ASAM) data set has become full, and the stage error option (STGERR) was specified as ABEND in the file characteristics block (FCB) generation. The following reason codes indicate why the error occurred:

Reason code	Description
01	A data space of the required size could not be obtained.
02	The data space has become full.

Processing terminates abnormally.

User response: For reason code 01, ensure that your installation allows unauthorized batch job steps to obtain a data space of the size needed. For reason code 02, increase the size of the output staging area specified in the FCB, or decrease the amount of data added to the file between application checkpoints. One way to do this is to reduce the time between application checkpoints.

BMC74237I

ASAM PARALLEL REPOSITIONING ENVIRONMENT ESTABLISHED.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attached one or more subtasks to perform restart repositioning for one or more application sequential access method (ASAM) data sets.

User response: No action is required.

BMC74238I

DATA SET CONCATENATION NOT SUPPORTED FOR VSAM.

Explanation: While processing an application sequential access method (ASAM) data set, APPLICATION RESTART CONTROL (AR/CTL) detected a concatenated VSAM data set. AR/CTL does not support concatenated VSAM data sets for ASAM. Processing terminates abnormally.

User response: Eliminate the VSAM concatenation.

BMC74239I

ASAM RESTART SUBTASK COMPLETE, FOR DDN= ddname, RC= returnCode

Explanation: APPLICATION RESTART CONTROL (AR/CTL) completed the repositioning of the given application sequential access method (ASAM) data set. The message includes the return code from the subtask.

User response: No action is required.

BMC74240I

ASAM CLOSE SUBTASK COMPLETE, FOR DDN= ddname, RC= returnCode

Explanation: APPLICATION RESTART CONTROL (AR/CTL) closed the given application sequential access method (ASAM) data set. The message includes the return code from the subtask.

User response: No action is required.

BMC74241I

ASAM RESTART SUBTASK ABENDED, FOR DDN= ddname, RC= returnCode

Explanation: APPLICATION RESTART CONTROL (AR/CTL) encountered an unrecoverable error while attempting to reposition the given application sequential access method (ASAM) data set. The message includes the return code from the subtask. Processing terminates abnormally.

User response: Correct the problem identified by the return codes in the message. Have the job step listing available, and contact BMC Customer Support.

BMC74242I

ASAM CLOSE SUBTASK ABENDED, FOR DDN= ddname, RC= returnCode

Explanation: APPLICATION RESTART CONTROL (AR/CTL) encountered an unrecoverable error while attempting to close the given application sequential access method (ASAM) data set. The message includes the return code from the subtask. Processing terminates abnormally.

User response: Correct the problem identified by the return codes in the message. Have the job step listing available, and contact BMC Customer Support.

BMC74243E

accessMethod INTERCEPT FAILED FOR DDN= ddname

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) interception routines did not intercept the open of the given application sequential access method (ASAM) or VSAM data set. AR/CTL abnormally terminates the task with abend U1775 and reason code X'00074243'.

User response: Ensure that the specified data set is not opened before the restart request is made in the application program. Ensure that open interception is enabled for the appropriate AR/CTL component in the BMC Consolidated Subsystem (BCSS).

BMC74244I

DATA SET REPOSITION BYPASSED FOR DDN= ddname, AS PER REQUEST

Explanation: The application sequential access method (ASAM) restart subtask bypassed the repositioning process for the indicated ddname, as requested by the user during file control block (FCB) generation.

User response: No action is required.

BMC74245I

REPOSITION BY RECORD NEEDED FOR DDN= ddname, BUT REPOSITION BY RECORD NOT ALLOWED

Explanation: The data set with the indicated ddname requires repositioning with the record-level technique, but the file characteristics block (FCB) indicates that this technique is not allowed. Processing terminates.

User response: Modify the FCB to allow repositioning by record, or copy the ASAM data set to a new location using the ASAM Copy utility.

BMC74246I

RECORD COUNT REPOSITION USED FOR DDN= ddname

Explanation: During restart processing for an application sequential access method (ASAM) data set, APPLICATION RESTART CONTROL (AR/CTL) determined that standard repositioning techniques could not be used because the data set had been moved to a different device or had been reblocked. Instead of using high-speed repositioning techniques, AR/CTL will read the data set records sequentially until it reaches the correct restart position. Processing continues, and the data set is repositioned for application restart. This condition normally occurs if the data set has been moved. The data set movement might have occurred because of Storage Management Subsystem (DFSMS) migration, use of the ASAM Copy utility, or other reasons. Such movements can cause changes to the number or relative position of the blocks within a data set.

User response: No action is required.

BMC74247I

TERMINATION OF THE DB2 CALL TRACE WAS COMPLETED ON BEHALF OF requestor.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) terminated enhanced call tracing of the application program calls to the DB2 subsystem on behalf of the indicated requestor.

User response: No action is required.

BMC74248I

COMMENCEMENT OF THE DB2 CALL TRACE WAS COMPLETED ON BEHALF OF requestor.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) started enhanced call tracing of the application program calls to the DB2 subsystem on behalf of the indicated requestor.

User response: No action is required.

BMC74249E

OPEN OF DB2 CALL TRACE DATA SET RETURNED CODE returnCode. DATA SET STATUS IS status.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to open the DB2 call trace data set. The attempt was not successful, and AR/CTL received the indicated return code. The DB2 call trace data set has the indicated status. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074249'. The most likely reason for this message is that the dynamic allocation skeleton contains an error.

User response: Review the JES message log, and review the Dynamic Allocation Parameter List report (found under ddname ARCDYNPR). Take corrective action as indicated by the messages and the Dynamic Allocation Parameter List report.

BMC74250E

OPEN OF DB2 CALL TRACE DATA SET WAS NOT SUCCESSFUL. DATA SET STATUS IS status.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to open the DB2 call trace data set. The attempt was not successful. The DB2 call trace data set has the given status. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074250'. The most likely reason for this message is that the dynamic allocation skeleton contains an error.

BMC74251E

CLOSE OF DB2 CALL TRACE DATA SET RETURNED CODE returnCode. DATA SET STATUS IS status.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to close the DB2 call trace data set. The attempt was not successful, and AR/CTL received the indicated return code. The DB2 call trace data set has the given status. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074251'. The most likely reason for this message is that the dynamic allocation skeleton contains an error.

BMC74252E

CLOSE OF DB2 CALL TRACE DATA SET WAS NOT SUCCESSFUL. DATA SET STATUS IS status.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to close the DB2 call trace data set. The attempt was not successful. The DB2 call trace data set has the given status. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074252'. The most likely reason for this message is that the dynamic allocation skeleton contains an error.

BMC74253E

AN INPUT/OUTPUT ERROR OCCURRED ON THE DB2 CALL TRACE DATA SET. THE DB2 CALL TRACE IS DISABLED.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) intercepted an I/O error on the application program DB2 call trace data set. Processing continues, but the DB2 call trace will be disabled for the remainder of the execution of the current task. The most likely reason for this message is that the dynamic allocation skeleton contains an error.

BMC74254E

TEMPORARY CLOSE OF DB2 CALL TRACE DATA SET RETURNED CODE returnCode. DATA SET STATUS IS status.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to temporarily close the DB2 call trace data set. The attempt failed, and AR/CTL received the indicated return code. The trace data set has the given status. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074254'. The most likely reason for this message is that the dynamic allocation skeleton contains an error.

User response: Review the JES message log, and review the Dynamic Allocation Parameter List report (found under ddname ARCDYNPR). Take corrective action as indicated by messages and the Dynamic Allocation Parameter List report.

BMC74255E

TEMPORARY CLOSE OF DB2 CALL TRACE DATA SET WAS NOT SUCCESSFUL. DATA SET STATUS IS status.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to temporarily close the DB2 call trace data set. The trace data set has the given status. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074255'. The most likely reason for this message is that the dynamic allocation skeleton contains an error.

BMC74256E

ARC initialization error; invalid region type - TM BATCH not valid

Explanation: The Application Restart Control for IMS (AR/CTL) product does not support the TM BATCH environment. ARC initialization fails because of an invalid region type.

User response: ARC supports only the DLI, DBB, and ULU region types. Rerun the job with a supported region type.

BMC74257I

APPLICATION RESTART CONTROL type CALL TRACE IS PENDING ACTIVE AFTER c-number CALLS AND FOR t-number CALLS.

Explanation: In response to the DISPLAY TRACE command, APPLICATION RESTART CONTROL (AR/CTL) issues this message to report that enhanced call tracing for the given type of subsystem will be activated after the given number (c-number) of application program calls is completed and will continue to be active for the given number (t-number) of application program calls.

User response: No action is required.

BMC74258I

APPLICATION RESTART CONTROL type CALL TRACE IS PENDING INACTIVE AFTER c-number CALLS AND FOR t-number CALLS.

Explanation: In response to the DISPLAY TRACE command, APPLICATION RESTART CONTROL (AR/CTL) issues this message to report that enhanced call tracing for the given type of subsystem is pending inactive. Tracing will be deactivated after the given number (c-number) of application calls have completed and the given number (t-number) of application calls have been traced. After this number of calls completes, tracing will be inactive.

User response: No action is required.

BMC74259W

PARSED COMMAND number LENGTH length TOKEN token LENGTH length TOKEN token

Explanation: APPLICATION RESTART CONTROL (AR/CTL) issues this message to accompany message BMC74176W or BMC74177W, which report that AR/CTL found an error in a command. This message displays the parsed command, including the number of the command and the length and token of each part of the command. AR/CTL also issues message BMC74176W or message BMC74177W, whichever is appropriate. Processing continues.

User response: For the appropriate action, see the response for the accompanying message.

BMC74260E

RESTART DATA SET (restartDataSetName) IDCAMS LISTCAT COMMAND RETURNED CODE (returnCode)

Explanation: APPLICATION RESTART CONTROL (AR/CTL) issued the IDCAMS LISTCAT command to list the catalog entry for the indicated restart data set. The command failed, and AR/CTL received the indicated return code.

User response: To determine the corrective action to take, examine the alternate SYSPRINT data set (found under the ddname ARCDIVPR) for the IDCAMS LISTCAT command. Analyze the listing of the restart data set catalog entry to determine whether to modify the dynamic allocation skeleton for the restart data set.

BMC74261E

UNABLE TO LOCATE {PSB psbName| ASB ASBname}

Explanation: APPLICATION RESTART CONTROL (AR/CTL) could not locate the indicated PSB in the IMS DD statement concatenation, or could not locate the given ASB in the ARC DD statement concatenation. The job step terminates abnormally with abend U1553.

User response: Ensure that the correct PSB or ASB library is specified and that it is spelled correctly.

BMC74262E

UNABLE TO LOCATE {DBD DBDname| FCB FCBname}

Explanation: APPLICATION RESTART CONTROL (AR/CTL) could not locate the indicated DBD in the IMS DD statement concatenation, or could not locate the indicated FCB in the ARC DD statement concatenation. The job step terminates abnormally with abend U1553.

User response: Ensure that the correct DBD or FCB library is specified and that it is spelled correctly.

BMC74263E

type modName IS INVALID

Explanation: The control block of indicated type (PSB, ASB, DBD, or FCB) named modname was invalid. It might have been generated incorrectly, or the PSB or ASB name might be misspelled in the parameters. The job step might terminate abnormally with abend U1553. If the module is an ASB or on FCB, the job step continues but a return code is issued.

User response: Ensure that the control block name is spelled correctly and the control blocks are generated correctly. Ensure that the correct library is specified in the ARC DD statement.

BMC74265E

DDNAME ''ddname'' NOT PRESENT, ARC TRACE UTILITY UNABLE TO CONTINUE

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility could not find the indicated ddname in the execution JCL. Processing terminates abnormally.

User response: Correct the execution JCL and resubmit the job.

BMC74266E

OPEN FAILED FOR DATASET, DDNAME ''ddname'', ARC TRACE UTILITY UNABLE TO CONTINUE

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected an unrecoverable error while trying to open the data set with the indicated ddname. Processing terminates abnormally.

User response: Check the data control block (DCB) information for the data set and check the JES log for MVS messages. Have the job step listing available if you contact BMC Customer Support.

BMC74267I

ERRORS FOUND IN INPUT COMMAND -- CORRECT AND RERUN

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected errors in the input commands. Processing terminates abnormally.

User response: Correct the input command and resubmit the job.

BMC74268I

ERROR PROCESSING LAST COMMAND

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected an undetermined error while processing the last command in the input command file. AR/CTL ignores the last command, and processing continues.

User response: Correct the input command and resubmit the job.

BMC74269I

CARD FLUSHED AFTER INVALID KEYWORD: keyword

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected the indicated invalid keyword in the input command file. AR/CTL ignores the input until the next valid command, and processing continues.

User response: Correct the input command and resubmit the job.

BMC74272I

REQUIRED OPERAND MISSING, COMMAND FLUSHED

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected an input command without a command value. AR/CTL ignores the command, and processing continues.

User response: Correct the input command and resubmit the job.

BMC74273I

END OF FILE ON SYSIN WITHIN A COMMAND

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected an expected continuation, but an end-of-file (EOF) condition on the SYSIN data set occurred before the command was complete. AR/CTL ignores the command, and processing continues.

User response: Correct the input command and resubmit the job.

BMC74274I

FUNCTION NOT CURRENTLY SUPPORTED

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected an unsupported command. AR/CTL ignores the command, and processing continues.

User response: Correct the input command and resubmit the job.

BMC74275I

command COMMAND VALUE HAS MORE CHARACTERS THAN ALLOWED, VALUE TRUNCATE

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected a value that is longer than expected for the indicated command. AR/CTL truncates the invalid value, and processing continues.

User response: Correct the input command and resubmit the job.

BMC74276I

value IS INVALID FOR COMMAND: command. DEFAULT VALUE USED

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected that the indicated value is invalid for the given command. AR/CTL replaces the invalid value with the default value, and processing continues.

User response: If appropriate, correct the input command and resubmit the job.

BMC74277I

FIRST RECORD IN TRACE FILE IS A TRAILER RECORD. TRACE UTILITY EXECUTION TERMINATED.

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility encountered a record other than a header record as the first record in the input trace data set. Processing terminates abnormally.

User response: Check the input trace data set to ensure that it is the correct input. Correct the problem, and resubmit the job.

BMC74278I

RECFM NOT SUPPORTED BY ASAM COPY UTILITY

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) ASAM Copy utility detected a record format (RECFM) other than fixed, variable, or undefined in the input file. Processing terminates abnormally.

User response: Check the input trace data set to ensure that the correct data control block (DCB) information is supplied. Correct the problem, and resubmit the job.

BMC74279E

AN INPUT/OUTPUT ERROR OCCURRED ON ddname DATA SET.

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) ASAM Copy utility encountered an unrecoverable I/O error on the given data set. Processing terminates abnormally.

User response: Check the data control block (DCB) information for the data set. Check the JES log for any MVS messages that might indicate some type of I/O error.

BMC74283E

THERE IS A MISMATCH BETWEEN THE type RECORD MAP AND THE TRACE RECORD

Explanation: The APPLICATION RESTART CONTROL (AR/CTL) Trace Format utility detected a mismatch between the given type of trace record map and the actual trace record in the trace file being processed. Processing terminates abnormally.

User response: Check to ensure that the job is using the correct input trace data set. Correct the problem, and resubmit the job.

BMC74284E

DBD DBDname IS NOT A GSAM DBD

Explanation: The indicated DBD is not a GSAM DBD. The job step terminates abnormally with abend U1553.

User response: Ensure that the correct DBD library is specified and that it is spelled correctly.

BMC74285E

DL/I BATCH REGION PROGRAM SPECIFICATION BLOCK WAS NOT GENERATED WITH CMPAT=YES OPTION.

Explanation: While executing in a DL/I batch region, APPLICATION RESTART CONTROL (AR/CTL) detected that the program specification block (PSB) was not generated with the CMPAT=YES keyword. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074285'.

User response: Regenerate the PSB with the CMPAT=YES keyword.

BMC74286E

NATIVE ENVIRONMENT RESTART RECORD RETRIEVAL SERVICE ROUTINE RETURNED CODE returnCode.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to retrieve the native environment restart record. The attempt failed, and AR/CTL received the indicated return code. This is an internal processing error. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074286'.

User response: Save the SYSUDUMP data set and JES message log for this job, and contact BMC Customer Support.

BMC74287E

LENGTH OF THE USER AREAS SPECIFIED ON THE XRST CALL EXCEEDS LENGTH OF THE USER AREAS SPECIFIED ON THE CHKP CALL.

Explanation: The length of the user areas specified on the XRST call exceeded the length of the user areas specified on the CHKP call. The lengths must be equal for a successful restart. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074287'.

User response: Review the application program, and determine the correct length of the user areas. Correct the length of the user areas in the XRST call to match the length of the user areas in the CHKP call.

BMC74288E

LENGTH OF THE USER AREAS SPECIFIED ON THE CHKP CALL EXCEEDS LENGTH OF THE USER AREAS SPECIFIED ON THE XRST CALL.

Explanation: The length of the user areas specified on the CHKP call exceeded the length of the user areas specified on the XRST call. The lengths must be equal for a successful restart. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074288'.

BMC74289E

type PROGRAM COMMUNICATION BLOCK TYPE IS NOT SUPPORTED IN THE NATIVE ENVIRONMENT FOR call CALL.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) does not support the indicated type of program communication block (PCB) in the non-IMS environment for the indicated type of call. Only the I/O PCB and generalized sequential access method (GSAM) PCBs can be used in the non-IMS environment. Other types of PCBs can be present in the program specification block (PSB), but they cannot be used by a call. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074289'.

User response: Review the application program. Remove all application program calls that use a PCB that is not an I/O PCB or a GSAM PCB.

BMC74290E

GDG GENERATIONS DCB ATTRIBUTES ARE NOT IDENTICAL FOR GDG-ALL REQUEST, REASON=reasonCode, DDN=ddName

Explanation: You have requested GDG ALL but the data control block (DCB) attributes of the GDG generations are not identical. The job terminates abnormally with abend U1770. The following reason codes explain the reason for termination:

Reason code	Description
01 or 03	Logical record lengths (LRECL) of the GDG generations are not identical
02 or 04	Block sizes (BLKSIZE) of the GDG generations are not identical

User response: Specify correct GDG generations in the JCL, delete the generations with different DCB attributes, and rerun the job.

BMC74294E

ARCSYSIN CONTROL CARD ERROR

Explanation: APPLICATION RESTART CONTROL (AR/CTL) detected a control statement error while processing the ARCSYSIN data set. AR/CTL writes messages about the exact nature of the error to the ARCPRINT data set. AR/CTL abnormally terminates with abend U1551.

User response: Correct the control statement error and resubmit the job.

BMC74296W

A PROGRAM COMMUNICATION BLOCK NAMED pcbName CANNOT BE FOUND FOR THE APPLICATION INTERFACE BLOCK AT address.

Explanation: APPLICATION RESTART CONTROL (AR/CTL) searched the program specification block (PSB) list, but could not find a program communication block (PCB) with the indicated name that was specified in the application interface block (AIB) at the indicated address. This condition can occur if the PSB does not contain an I/O PCB or if the PSB contains an I/O PCB but no database PCBs. AR/CTL might abnormally terminate the task with abend U1771 and reason code X'00074296'. In some cases, AR/CTL continues processing after issuing this message.

User response: Review the AIB to verify that a PCB exists with the name given in this message. Review the application program to verify that the PCB name in the AIB is always initialized to the name of the PCB in the current application specification block (ASB) or PSB. Ensure that the PSB contains an I/O PCB and that, if no database PCBs are in the PSB, the I/O PCB is specified by name.

BMC74297I

A ROLL CALL WAS ISSUED BY THE APPLICATION PROGRAM. THE CURRENT TASK WILL TERMINATE WITH USER 778 COMPLETION CODE.

Explanation: The application program issued a ROLL call. AR/CTL abnormally terminates the task with abend U778 and reason code X'00074297'.

User response: Contact the application programmer to determine why the application issued the ROLL call.

BMC74298E

ASB ASBname IS INVALID

Explanation: The indicated application specification block (ASB) is invalid. ASBname might also refer to a program specification block (PSB) if the application is executing in IMS or IMS-compatible mode. The job step terminates abnormally with abend U1553.

User response: Ensure that the ASB name is spelled correctly and is the right one for this job. Ensure that the correct ASB or PSB library is being used. If these elements are correct, contact BMC Customer Support.

BMC74299E

ONE OR MORE RESTART CHECKPOINTS CONFLICT WITH THE FORCE COLD START OPTION.

Explanation: One or more restart checkpoints were specified and conflict with the Always Cold Start option. AR/CTL abnormally terminates the task with abend U1771 and reason code X'00074299'.

User response: Determine the source of the conflicting checkpoints. Supply the correct checkpoint.

Messages BMC74200 through BMC74299

Messages library

On this page