BMC Software, Inc., Confidential and Proprietary Information
BMC74000–BMC74099 145
BMC74027E DYNAMIC CONCATENATION OF ddname RETURNED R15(return code),
S99ERROR(error), AND S99INFO(reason)
Explanation: Dynamic concatenation of ddnames for the specified ddname
failed. The message also displays the return code, the error reason code, and the
information reason code.
System Action: APPLICATION RESTART CONTROL (AR/CTL) abnormally
terminates the task with abend U1771 and reason code X’00074027’.
User Response: Refer to the Dynamic Allocation Parameter List report (found
under ddname ARCDYNPR). Using the return code and the error and information
reason codes from this message, see the IBM manual SPL: System Macros and
Facilities Volume 1 to determine the cause of the error and the corrective action to
take.
BMC74028E READ (RETRIEVE COPY OF) JOB FILE CONTROL BLOCK FOR
DDNAME ddname RETURNED CODE rc
Explanation: APPLICATION RESTART CONTROL (AR/CTL) attempted to
read (retrieve a copy of) the job file control block for the given ddname. The attempt
failed, and AR/CTL received return code rc.
System Action: AR/CTL abnormally terminates the task with abend U1771 and
reason code X’00074028’.
User Response: Save the SYSUDUMP data set and JES message log for this job,
and contact BMC Software Product Support.
BMC74029E THE RESTART DATA SET restart dsn CONTAINS INVALID HEADER
INFORMATION
Explanation: APPLICATION RESTART CONTROL (AR/CTL) detected
invalid header information in the restart data set (restart dsn) defined in the
ARCXRST DD statement or in the restart control record in the REGISET. This
condition implies that the data set is not a restart data set and does not contain valid
checkpoint records that can be used during restart processing.
System Action: AR/CTL abnormally terminates the task with abend U1771 and
reason code X’00074029’.
User Response: Provide a valid restart data set. If a valid restart data set does not
exist, perform the restart using the IMS system log data set (SLDS), if possible. If
not, perform the procedure for handling a damaged or destroyed restart data set as
described in the APPLICATION RESTART CONTROL User Guide.
