Messages BMC44200 through BMC44299
This group includes messages for the APPLICATION RESTART CONTROL and BATCH CONTROL FACILITY products.
Number | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
BMC44200I | {BCF PHYSICAL LOGGER | BCF NONLOGGING ENVIRONMENT} INITIALIZED Explanation: One of the following situations occurred:
User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44201E | DATA SET NOT OPENED, DD = ddname, MISSING Explanation: The log open routine could not open a data set because the ddname was missing from the job step JCL. If dual logging was requested and the failure occurs for the secondary log, execution continues using single logging. If a single logging environment was requested, the job step abnormally terminates. User response: The ddname must be available at execution of the job step. If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44202E | DATA SET NOT OPENED, READ JFCB FAILED FOR DDNAME=ddname, RC=returnCode Explanation: The log open routine could not open a needed data set (ddname) because a bad return code was received from the RDJFCB macro issued for the data set. A possible system error has occurred. If dual logging was requested and the failure occurs for the secondary log, execution continues using single logging. If a single logging environment was requested, the job step abnormally terminates. User response: If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44203E | LOG OPEN FAILED, TYPE=type, DDNAME=ddname, RC=returnCode Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger could not open a needed data set because a bad return code was received from the OPEN macro issued for the indicated ddname. A possible system error has occurred. The following type values are possible:
If dual logging was requested and the failure occurs for the secondary log, execution continues using single logging. If a single logging environment was requested, the job step abnormally terminates. User response: If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44204I | SECONDARY LOG DATA SET NOT OPENED, SINGLE LOGGING IN EFFECT Explanation: Dual logging was requested, but the secondary log data set could not be opened because of an error identified in a previous message. The job step continues to execute using single logging. User response: No action is required. For additional information, see the accompanying message that contains the actual error. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44205I | BCF LOGGER NOT INITIALIZED, REASON = reasonCode Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger could not initialize. The message contains a reason code that identifies the reason that initialization was not successful. The following reason codes are possible:
User response: Respond to this message based on the indicated reason code:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44206I | IMS LOG TERMINATED Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger has closed the IMS log. This message replaces the IMS DFS092I message. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44207I | LOGGING STATISTICS - BLOCKS = count, FORCED = count, PERF % = percent% Explanation: This message displays the logging statistics that aid in understanding the performance characteristics of the IMS log integrity function of the APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger. This message is provided only when the log devices use AR/CTL BCF component buffered device support. The following statistics are displayed:
User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44208E | NO LOG DATA SETS USABLE FOR READ Explanation: None of the log data sets can satisfy a read request from dynamic backout. Processing continues, but IMS dynamic backout processing fails. If the Automatic Backout option is specified as YES, the execution controller will perform batch backout processing. User response: If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44209I | PERF % EXCEEDED jobName stepName psbName date time Explanation: Alert! This is an Alert category message. The value reported as the PERF% has exceeded the threshold specified for the given job step. User response: No action is required. You might want to tune the database buffer pools, tune the logging environment, or change the application program to improve the logging performance. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44210I | RETURNING CONTROL TO IMS PHYSICAL LOGGER Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger could not initialize. The AR/CTL BCF component attempts to return control to the IMS Physical Logger. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44211I | DB = databaseName DDN = ddname UNREGISTERED CPY Explanation: Alert! This is an Alert category message. The indicated database is registered with DBRC. However, the name of the data set being used by this execution is not the name registered with DBRC. (This message is issued only if IBM’s IMS APAR PL63425 is installed.) User response: No action is required. This message provides notification of the potential loss of recovery information. Verify that the use of the unregistered database was intentional. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44212I | LOG DS USING TWI, DD = ddname Explanation: Alert! This is an Alert category message. The message indicates that the options selected for this job step specified that tape write immediate mode should be used for the log data sets if they are being written to a buffered device. Tape write immediate mode might result in significant performance degradation. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44213I | BCF LOGGER DBRC ERROR, FUNC = function, RC = returnCode Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger received a nonzero return code from DBRC while attempting to notify DBRC of a change in the status of a log data set volume. The function in error and the DBRC return code appear in the message. The following table describes the displayed function:
The action taken depends on the routine that detects the error. If the routine is log data set notification, the job step terminates. If the routine is discard logging database processing, processing continues. User response: If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44214I | RGX ERROR, EXECUTION MUST TERMINATE, RC = returnCode Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger detected a critical error with the REGISET. Job step termination is necessary to prevent possible database integrity exposures. The job log might contain additional information about the REGISET error. The return code in the message provides additional information concerning the reason for termination. If the indicated return code is 4, the execution control record could not be written to the REGISET. When the execution control record cannot be written, job step restart might be possible without execution of the IMS Batch Backout utility. Since DBRC is not active for execution, the job step abnormally terminates before database updates can be done. The job step terminates abnormally. User response: Obtain the error messages from the job log concerning the REGISET error encountered. Correct the condition that caused the error. Resubmit the job step only after the condition that caused the error is corrected. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44215E | CLOSE FAILED, DDNAME = ddname, RC = returnCode Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger could not close the data set that is associated with the indicated ddname. User response: If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44216E | type ERROR HAS OCCURRED, DDNAME = ddname Explanation: The indicated data set being written by the APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger encountered an error of the indicated type. A possible system or physical device error has occurred. Review the job log data set for any MVS messages. The message displays one of the following types:
The log data set is marked in error and DBRC is notified. If dual logging is active and a valid log data set exists, processing continues with the remaining log data set. If dual logging is not active or if both logs are invalid, the job step terminates. If no valid output devices are available for logging, the job terminates abnormally with a U616 abend. User response: If the job log data set contains MVS messages, review those messages for more error information. If the job log data set does not contain MVS messages, obtain a SYSUDUMP data set and contact BMC Customer Support for assistance. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44217I | DATASET NOT CLOSED, WRITE ERROR, DDNAME = ddname, LSN = lsn Explanation: The indicated data set being written by the APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component Physical Logger was not closed because it encountered a WRITE error. A possible system or physical device error has occurred. The LSN value is the sequence number of the last log record in the last valid block that was written to the log data set. This number might be needed when using the IMS Log Recovery utility. User response: No action is required. The message provides information that you might need to close the log data set if the execution controller cannot recover the job log data set. If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44218I | DYNAMIC LOG DATA SET CREATED, BLOCKS = number Explanation: A dynamic log data set was specified, and the environment supported dynamic backout. The dynamic log was created to provide dynamic backout if needed. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44219I | DYNAMIC BACKOUT (BKO=Y) ACTIVATED Explanation: An execution option requested IMS dynamic backout for the job step, but the IMS execution parameters did not specify BKO=Y. The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) changed the environment to include IMS backout processing for the job step execution. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44220I | READ REQUEST FAILED, DYNAMIC LOG WAS SUSPENDED Explanation: The job step was using a dynamic log to provide read services for the IMS dynamic backout process. A READ request could not be satisfied because the block was not contained in the dynamic log and the use of the dynamic log was suspended when it became full. The IMS dynamic backout process fails because of the read error on the dynamic log. The execution controller might attempt database backout by using the IMS Batch Backout utility. User response: Increase the size of the dynamic log, or issue the DL/I application checkpoints more frequently. Increasing the size of the dynamic log is usually preferable. The number of blocks specified for the dynamic log must be large enough to contain all blocks written to the IMS log data set between checkpoints. The Application Checkpoint Detail report (provided when the BCFSTATS DD statement is present) can help determine the number of blocks necessary to prevent suspension of the dynamic log. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44222E | RGX WRITE ERROR; REC TYPE = type Explanation: An attempt to write to the REGISET failed when the BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) attempted to write job information to the REGISET. The following type values indicate the type of record being written to the REGISET:
The actions taken by the AR/CTL BCF component depend both on the function that detects the error and on how the execution options are specified. User response: Correct the problem that caused the error and resubmit the job. For a discussion of the actions taken, see the section on the REGISET in the APPLICATION RESTART CONTROL Installation Guide. If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44223E | RGX READ ERROR; REC TYPE = type Explanation: An attempt to read the REGISET failed when the BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) attempted to read job information from the REGISET. The following type value indicate the type of record being written to the REGISET:
The actions taken by the AR/CTL BCF component depend both on the function that detects the error and on how the execution options are specified. User response: Correct the problem that caused the error and resubmit the job. For a discussion of the actions taken, see the section on the REGISET in the APPLICATION RESTART CONTROL Installation Guide. If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44228I | STORAGE REQUEST FAILED, FUNCTION = function, REASON = reasonCode Explanation: A conditional request for virtual storage failed. The message displays one of the following function codes:
Register 15 contains the reason code passed by GETMAIN. If possible, processing continues with reduced functions. User response: For function code 2, verify that your installation allows batch jobs to obtain MVS/ESA data spaces of the size required. If the dynamic log is requested in extended private memory, verify that your installation allows a batch job to obtain the amount of storage requested from extended private memory. Determine the amount of storage needed for the dynamic log using the following formula: (log blksize x #blks for dynamic log) = dynamic log size This value represents the amount of extended private memory or data space memory requested. For the other function codes, you might need to increase the region size requested for the job step. If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44229I | BATCH CONTROL FACILITY LEVEL IS V version R release M maintenanceLevel Explanation: This message displays the release level of the APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44230I | INCONSISTENT EXECUTION OPTIONS Explanation: The values specified for the Use Execution Control option and the Use Physical Logger option are inconsistent. The Use Physical Logger option must be specified as Y if the Use Execution Control option is specified as Y. Processing continues without the use of the BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL). User response: Correct the inconsistent options and resubmit the job. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44232I | RETRY MANUAL INTERVENTION PROCESSING ACTIVE Explanation: The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) is attempting to restart a job step that failed to complete log recovery or batch backout in a previous execution. The operator updated the execution control record to request retry of a condition that resulted in manual intervention for the job step. Processing continues. The previously failed recovery action is retried. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44233I | APPLICATION RESTART DEFERRED BY OPERATOR REQUEST Explanation: The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) completed restart recovery processing for a job step that previously failed a recovery process. The operator or the Automatic Restart Preparation utility updated the execution control record to request recovery of the environment only. All of the processing necessary to recover the environment to a point ready for application execution has completed. The user’s application was not executed due to the request to defer application execution. The job step abnormally terminates to prevent execution of any additional steps. The AR/CTL BCF component prevents any COND=ONLY batch backout steps from executing. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44234E | INITIALIZATION ERROR; INVALID BCF ENVIRONMENT, RC = returnCode Explanation: During initialization, the BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) detected an error with the user-defined defaults for job step execution. The return code provides additional information about the error. The message displays one of the following return codes:
Initialization terminates. If the global options record is at an incorrect level, the job step terminates abnormally. The global options record must be present in the REGISET and must match the executing version of the AR/CTL BCF component before job step execution is allowed. If the REGISET does not contain any records, the execution controller performs abort processing. User response: Respond to the message based on the indicated return code:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44235E | INITIALIZATION ERROR; INVALID IMS REGION TYPE Explanation: The region type was not an IMS batch region (DLI, DBB, or ULU). If the IMS version of DFSRRC00 can be found and loaded successfully, control returns to IMS and the job continues processing. If the IMS version cannot be loaded, the job step terminates abnormally. User response: If the region type was correctly specified and the job does not continue processing due to this error, either remove the AR/CTL BCF component library from the job step’s JOBLIB or STEPLIB specification to prevent the BCF component from attempting initialization or include the IMS version of DFSRRC00 in the job’s JOBLIB or STEPLIB concatenation. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44236I | IMS DYNAMIC BACKOUT NOT PERFORMED Explanation: The application terminated abnormally after database updates had occurred. IMS did not attempt to perform the IMS dynamic backout process after the abnormal termination of the application. This message is not present unless FULL was specified for the JOBLOG Messages option. User response: No action is required. The IMS dynamic backout process might have been effective, but it was not invoked. This message indicates that no form of the IMS dynamic backout process was requested for job step execution. For more information about the use of the IMS dynamic backout process, see the APPLICATION RESTART CONTROL Reference Manual: BATCH CONTROL FACILITY. This message does not imply that the IMS dynamic backout process would have been invoked; it only states that it was not. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44237I | IMS DYNAMIC BACKOUT FAILED Explanation: The application terminated abnormally after database updates had occurred. IMS attempted to perform dynamic backout, but the dynamic backout process did not complete successfully. The AR/CTL BCF component might attempt IMS batch backout for the failed job step. User response: No action is required. The IMS dynamic backout process was invoked, but it did not complete successfully. The job log data set for the job step execution might contain more information regarding the reason for dynamic backout failure. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44238I | text Explanation: The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) issued this message to report information that is related to database updates. The message text can take either of the following forms:
User response: If the application was exectuing in a BCF logging environment, no action is required. The execution of the application was not successful. The job log data set for the job step execution might contain more information about the program failure. If the application was exectuing in a nonlogging environment, ensure that the updated databases are restored to a point of consistency. Because logging was not invoked, batch backout cannot be performed. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44240I | MVS SVC99 errorInformation Explanation: This message contains information about a specific allocation or unallocation error detected by the APPLICATION RESTART CONTROL (AR/CTL) application supervisor. If this is a dynamic allocation error that can be retried, message BMC44240A will follow. For more information about the use of dynamic allocation services (SVC99), see the appropriate IBM manual. The action taken depends on the routine that detected the error. If this error is listed in BCFDALIN (a table of correctable AR/CTL BATCH CONTROL FACILITY (BCF) component dynamic allocation errors), message BMC44240A will follow. User response: If this message indicates a correctable dynamic allocation error, reply to message BMC44240A when displayed. If a BCFPRINT DD statement is present, the text units for allocation are provided. Have the information from this message available if you need to contact BMC Customer Support for assistance. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44240A | REPLY “R” TO RETRY, “W” TO WAIT, “C” TO CANCEL Explanation: A dynamic allocation error has occurred that can be retried. This message is sent to the operator, indicating that action needs to taken. User response: Reply to the message by issuing one of the following commands:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44241I | UNALLOCATION SUCCESSFUL, DDN = ddname Explanation: The execution controller successfully unallocated the current IMS log data set identified by ddname. This message is issued only when the JOBLOG Messages option is specified as FULL. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44242I | MANUAL INTERVENTION REQUIRED PROCESS = process, REASON = reasonCode Explanation: An error occurred from which the execution controller cannot recover. Manual intervention is required before the job step can be restarted. The message displays one of the following processes:
The message displays one of the following reason codes:
The job step terminates abnormally. User response: The error indicated by this message requires manual intervention to create a restartable environment. For more information, see the section about manual intervention in the APPLICATION RESTART CONTROL Reference Manual: BATCH CONTROL FACILITY. After intervening manually, update the REGISET. If you are using DBRC, the presence of a subsystem record and database allocation records might indicate the need for execution of the IMS Batch Backout utility. The job log data set for the job step execution contains additional messages about the failure. These messages might indicate additional actions that you need to take. Have the job log data set available if you need to contact BMC Customer Support for assistance. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44243I | ALLOCATION ERROR; TYPE = type, DDNAME = ddname, DSN = dataSetName Explanation: An error occurred while attempting allocation for a function needed by the execution controller. The message contains the allocation type being attempted, the ddname, and the data set name associated with the allocation attempt. The message displays one of the following types:
Message BMC44240I is issued with this message; it contains the details of the MVS SVC99 error that occurred. User response: If the allocation is for a new data set, the allocation characteristics are determined by the most qualified dynamic allocation record found in the REGISET. Verify that the allocation options are correct for the device type requested. If the allocation is for a data set created during job step execution, contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44244E | IEFRDER DD STATEMENT MISSING Explanation: The job step JCL does not contain a DD statement for the IMS log data set, which is required by IMS for job step execution. The situation is treated as an initialization error, and processing continues based on the value of the Initialization Error option (set at the APPLICATION RESTART CONTROL (AR/CTL) global level). User response: Correct the job step JCL and resubmit the job step. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44245E | BCF INTERNAL LOGIC ERROR, REASON = reasonCode Explanation: The execution controller detected an internal logic error. The job step terminates abnormally. User response: Contact BMC Customer Support and provide the reason code from this message. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44246I | DYNAMIC ALLOCATION SKELETON MISSING, DDN = ddname Explanation: When attempting to allocate a data set, the execution controller could not locate the dynamic allocation skeleton for the indicated ddname. If the allocation is necessary to provide a restartable environment, message BMC44242I is also issued, requesting manual intervention. User response: Create the dynamic allocation record and restart the job step. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44247E | BCFHIST DUMMY OR NULLFILE: NO STATS WILL BE RECORDED FOR THIS JOBSTEP Explanation: A BCFHIST DD statement was included in the batch execution JCL, but the statement was coded as DUMMY or NULLFILE. Processing continues. The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component will not write any statistics for this job step execution. Message BMC48083E is displayed at the end of the job step. User response: Complete one of the following actions:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44248I | UNALLOCATION ERROR; TYPE = type, DDNAME = ddname Explanation: An error occurred while attempting unallocation for a function needed by the execution controller. The message contains the unallocation type being attempted and the ddname that is associated with the unallocation attempt. The message displays one of the following types:
Message BMC44240I is also issued and provides details of the MVS SVC99 error. User response: If the error is not the result of inconsistent allocation specifications, contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44249W | BCF INITIALIZATION WARNING RC = returnCode, RESOURCE = resource Explanation: The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) encountered an exception condition during initialization. The error was not considered severe enough to cause an initialization error. The message contains a return code that identifies the exception condition and an optional resource name. When the resource name is included in the message, it identifies the resource that contains the inconsistent or exception specification. The message displays one of the following return codes:
When present, the resource name identifies the resource associated with the exception condition. The message displays one of the following resources:
Processing continues after error handling has been completed. User response: Correct the record before the next execution of the job step. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44250E | BCFSYSIN CONTROL CARD ERROR Explanation: The execution controller detected a control statement error while processing the BCFSYSIN data set. The execution controller uses a print data set from the SYSOUT class. The ddname used for the allocation is BCFPRINT. Processing of the BCFSYSIN data set terminates. The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) attempts execution by using the job step options that were specified before it encountered the error in the BCFSYSIN data set. User response: Correct the control statement error and resubmit the job. Diagnostic information about the error is provided when a BCFPRINT DD statement is included in the job step JCL. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44251I | BATCH BACKOUT MAY BE REQUIRED, REASON = reasonCode Explanation: The application program terminated abnormally, and the execution controller cannot determine whether the IMS Batch Backout utility is necessary for the abending task. The message displays one of the following reason codes:
If the error is the result of Physical Logger initialization failure, additional messages might be present in the job log data set. If DBRC is active for the job step, DBRC might prevent another execution of the job step if the IMS Batch Backout utility has not been executed. If DBRC is not active for the job step, the potential for another execution of the job step is possible, and database integrity might be compromised. For more information, see the section about job step restart considerations in the APPLICATION RESTART CONTROL Reference Manual: BATCH CONTROL FACILITY. User response: No action is required. The message might be intercepted by an automated console facility to assist in controlling the execution environment. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44252E | RESULTING DATA SET NAME INVALID, REASON = reasonCode Explanation: The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) attempted to construct the data set name for allocation of a new IEFRDER or IEFRDER2 data set. Processing of the data set name skeleton might have produced an invalid data set name. The message displays one of the following reason codes:
Dynamic allocation is attempted using the constructed data set name. User response: Correct the data set name skeleton so that a valid data set name is constructed and resubmit the job. When an invalid data set name is used with dynamic allocation, the job log data set might contain several messages. Use the information from these messages to correct the data set name skeletons. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44254I | DISCARD LOGGING INITIALIZED, DBRC IS status Explanation: Discard logging was activated for the job step. The status of DBRC usage for the job step execution is indicated. If DBRC is active, special processing is provided for databases that are updated by the job step. For more information about this process, see the APPLICATION RESTART CONTROL Reference Manual: BATCH CONTROL FACILITY. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44255I | UNABLE TO DELETE EXECUTION CONTROL RECORD Explanation: An error occurred while attempting to delete the current execution control record from the REGISET. Message BMC44242I, with return code 13, accompanies this message. Processing terminates. User response: The job log might contain additional error messages relating to the REGISET errors that were encountered. Have the job log data set available if you need to contact BMC Customer Support for assistance. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44256I | BCF EXECUTION CONTROLLER NOT INITIALIZED, REASON = reasonCode Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component execution controller could not be initialized for the given reason. If the message displays reason code 1, the AR/CTL BCF component execution controller was deactivated via a previously selected option. The Use Execution Control option specified was NO. The execution controller completed very limited processing. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44257W | BCF IS EXECUTING WITH AN UNSUPPORTED RELEASE OF IMS; PROCESSING CONTINUES Explanation: The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) detected an unsupported release of IMS. Processing continues; however, other error messages might be issued. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44270I | BATCH CONTROL FACILITY INITIALIZED Explanation: The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) has initialized the execution controller environment. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44271I | BATCH CONTROL FACILITY NOT INITIALIZED, REASON = reasonCode Explanation: The APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component initialization could not be performed for the reason indicated by one of the following reason codes. This message is issued only when the JOBLOG Messages option is specified as FULL.
The AR/CTL BCF component Active option was specified as N, or the product is executing on an unauthorized processor. The AR/CTL BCF component completed very limited processing. User response: Verify that the AR/CTL BCF component is authorized to execute on the processor. If you are using a trial copy, verify that the expiration date has not passed. The job log might contain additional messages that explain the failure. Respond to the message based on the indicated reason code:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44272I | ATTACHING PROCESS, FUNCTION = function Explanation: The execution controller attached a process function. This message is only issued when the JOBLOG Messages option is specified as FULL. The message displays one of the following functions:
User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44273I | PROCESS ENDED, FUNCTION = function, RC = returnCode, ABEND = code Explanation: The indicated function completed execution with the indicated process return code. If an abend occurred, the abend code is also included. This message is issued only when the JOBLOG Messages option is specified as FULL. The message displays one of the following functions:
User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44275I | ALLOCATION FUNCTION COMPLETE, FUNCTION = function Explanation: Dynamic allocation completed for a specific batch control function. This message is issued only when the JOBLOG Messages option is specified as FULL. The messge displays one of the following functions:
User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44276I | BATCH CONTROL FACILITY TERMINATION COMPLETE Explanation: All processing for the job step completed. The execution controller has terminated. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44277I | BATCH CONTROL FACILITY ABORTING Explanation: The execution controller encountered an error condition that prohibits continued processing. The job log contains additional messages that indicate the failure encountered. The job step terminates abnormally when the execution controller is active and the Initialization Error option (set at the APPLICATION RESTART CONTROL (AR/CTL) global level) has been set to ABEND. If the Initialization Error option has been set to IMS, the job step returns control to IMS and continues processing without the BATCH CONTROL FACILITY (BCF) component of AR/CTL. User response: The job log data set should contain additional information about the reason for aborting. If the job step abends, correct the problem identified in these messages before resubmitting the job step. Have the job log data set available if you need to contact BMC Customer Support for assistance. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44278I | UNABLE TO CLOSE PRIOR LOG DATA SETS Explanation: The IMS logs from the previous execution of the step were not closed. An unsuccessful attempt was made to close the logs with the IMS Log Close utility. If dual logging was being used in the previous step execution, the close failed for both logs. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44279I | UNABLE TO BACKOUT PRIOR EXECUTION Explanation: Backout of the previous execution of the step was not possible. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44280I | ACTIVE ENTRY = jobName.stepName.psbName.date.time Explanation: During initialization, the execution controller found an execution control record in the REGISET for the indicated job name, step name, PSB, date, and time. If the Qualify With Program option was selected, the value for the PSB is the program name for the job step. Execution continues to recover the job step to a point of restartability for your program execution. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44281I | BATCH CONTROL FACILITY RETURNING CONTROL TO IMS Explanation: The execution controller was not able to initialize and is aborting. The Initialization Error option (set at the APPLICATION RESTART CONTROL (AR/CTL) global level) was set to IMS. An attempt will be made to return to the standard IMS execution environment. This message is also issued when execution is attempted in an invalid IMS region type. In this case, message BMC44235E is also issued. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44282E | LOAD FAILED FOR MODULE = loadModule Explanation: The execution controller detected an error while attempting to load the indicated module. The action taken depends on the module being loaded. Additional messages are issued to provide more information about the error. User response: Ensure that the modules necessary for APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component execution are available. If you are unable to correct the problem, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44284I | logType LOG CLOSED OLD VOLUME = oldVolser, NEW = newVolser Explanation: The execution controller closed the previous log data set (oldVolser) by attaching the IMS Log Recovery utility, and identified a new log data set (newVolser). User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44285I | ALLOCATION SUCCESSFUL, DDNAME = ddname, DSN = dataSetName Explanation: Dynamic allocation is successful for the given ddname and data set name. This message is issued only when the JOBLOG Messages option is specified as FULL. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44286I | UNABLE TO LOCATE EXECUTION OPTIONS Explanation: The execution controller was not able to locate execution options at any level. Execution continues using the standard defaults. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44287I | OPEN FAILED FOR DDNAME = ddname, RC = returnCode Explanation: The execution controller cannot open a data set necessary for execution. The ddname and return code from the OPEN process appear in the message text. Processing generally continues based on the setting of the Initialization Error option (set at the APPLICATION RESTART CONTROL (AR/CTL) global level). Additional messages explain the function that failed. If the function was log recovery, a U624 or U1570 abend or a U625 or U1571 abend will occur. The abend code displayed depends on the value specified for the Use Abend Code Series (ABN) option. For more information, see the Use Abend Code Series option in the APPLICATION RESTART CONTROL Reference Manual: BATCH CONTROL FACILITY. User response: The response depends on the ddname that is indicated in the message:
If the message references any other ddname, ensure that the job log data set is available and contact BMC Customer Support. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44288I | IMAGE COPY NEEDED, ACTION = action Explanation: The Discard Logging Active option was specified as YES, and the application terminated normally. The database referenced in the job should be image copied. If DBRC is active and the database is registered with DBRC, the database has been marked as Image Copy Needed and a reorganization record was added to the RECON data set for the database. If DBRC is not being used or the database is not registered, protection of the database is your responsibility. The database has been updated without an IMS log data set being created and can be recovered only if the necessary steps are taken to ensure recoverability. The ACTION portion of the message displays additional information about the processing actions taken by the Physical Logger:
User response: No action is required. This message might be used by automated operations to submit the image copy job. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44289I | IMS DYNAMIC BACKOUT DETECTED FOR CUSTOMER PROGRAM Explanation: IMS completed dynamic backout for the application. You can verify this status by the presence of IMS message DFS022I in the job log. The application terminated abnormally and required database backout. Backout had already been performed by IMS dynamic backout, so the BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) did not invoke the IMS Batch Backout utility, unless updates were made after the IMS dynamic backout was performed. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44291I | UNEXPECTED RETURN CODE, ROUTINE = routine, RC = returnCode Explanation: The execution controller received an unexpected return code from a service routine. Additional messages provide information about the actions taken by the BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL). User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44292I | BATCH BACKOUT COMPLETED Explanation: The execution controller invoked the IMS Batch Backout utility to back out the failed application. The IMS Batch Backout utility completed normally, and the job step is ready for application execution or step restart. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44293I | RECOVERY NEEDED, ACTION = action Explanation: The Discard Logging Active option of the APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component was specified as Y, and the job step terminated abnormally. The database referenced in the job should be recovered. If DBRC is active and the database is registered with DBRC, the database was marked as Backout Needed. If DBRC is not being used or if the database is not registered, protection and recovery of the database is your responsibility. The database has been updated without an IMS log data set being created and cannot be backed out using the IMS Batch Backout utility. This is an informational message to indicate that the specific database needs additional processing to ensure database integrity and recoverability. The ACTION portion of the message displays additional information about the processing actions taken by the AR/CTL BCF component Physical Logger:
User response: No action is required. The message might be used by automated operations to initiate the recovery process. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44294I | DISCARD LOGGING NOT SUPPORTED AT THIS LEVEL, REASON = reasonCode Explanation: The Discard Logging Active option was specified as Y, but discard logging is not supported in the execution environment detected. The message displays one of the following reason codes:
User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44295I | DISCARD LOGGING; IGNORE MESSAGE DFS036 IF PRESENT Explanation: The Discard Logging Active option was specified as Y. The special processing necessary to provide discard logging when DBRC is active might cause IMS to issue message DFS036, when databases have been updated and must be recovered or restored. Messages BMC44288I or BMC44293I accompany this message, providing the actual recovery or integrity processing required for the databases that were updated during job step execution. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44296I | DYNAMIC LOG NOT INITIALIZED, REASON = reasonCode Explanation: The execution options present for the job indicated that a dynamic log should be built and used. The dynamic log was not built because of conflicting execution options that prohibit usage of a dynamic log or reduce its benefit. The following reason code values provide additional information about why the dynamic log was not built:
User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44297I | NOTIFY OPTION IN EFFECT, REASON=reasonCode Explanation: The Notify DBRC option of the APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component is in effect for the indicated reason:
User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44298I | NOTIFY=NONE NOT ALLOWED IF PCB PROCOPT NOT L OR LS; CHANGED TO BACKOUT Explanation: The value of the Notify DBRC option of the APPLICATION RESTART CONTROL (AR/CTL) BATCH CONTROL FACILITY (BCF) component was changed from NONE to BACKOUT because the processing option (PROCOPT) in the program specification block (PSB) is not L or LS. User response: No action is required. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
BMC44299E | BCF INITIALIZATION ERROR; INVALID REGION TYPE - TMBATCH NOT VALID Explanation: The BATCH CONTROL FACILITY (BCF) component of APPLICATION RESTART CONTROL (AR/CTL) does not support the TMBATCH Environment. BCF initialization fails for an invalid Region type. User Response: BCF supports only DLI, DBB, and ULU region types. Rerun the job with a supported region type. |