Messages BMC115000 through BMC115099

BMC115002C

Error during function call to program name. Return code return code, reason code reason

Explanation: An internal error occurred during the indicated function call to the indicated program name. The job step terminates.

User response: Refer to the previous messages to determine the specific error, and contact BMC Customer Support.

BMC115003I

No space available for temporary work file

Explanation: The Area Copy function allocates multiple, 100-cylinder temporary data sets (SYS0nn) to store internal work files. This action can result in many 100-cylinder SYS0nn files. If no space is available for the next 100-cylinder increment, this message is issued. The job step terminates abnormally with a user abend 4094.

User response: Increase the free amount of work space.

BMC115004C

Dynamic Allocation error: text

Explanation: A dynamic allocation request failed. The job step terminates.

User response: Refer to the IBM publication that describes MVS dynamic allocation reason codes for an explanation of the reason code. Correct the error, and resubmit the job.

BMC115005C

The temporary data set allocated to DD ddname cannot be VIO.

Explanation: A temporary data set was allocated that is to be shared between address spaces. This data set cannot be virtual I/O (VIO). The job step terminates.

User response: Reassemble PC$SET0, specifying a different work unit or SMS specifications. Contact your DASD administrator and request SMS rules be modified to avoid VIO.

BMC115006C

Data set dsname not found.

Explanation: Dynamic allocation detected that the indicated data set was not found. Subsequent messages may be issued. Processing continues.

User response: If additional messages are issued, complete the actions indicated in the additional messages.

BMC115007C

Data set dsname in use.

Explanation: Another job is using the indicated data set. Processing continues. Additional messages might be issued.

User response: If additional messages are issued, complete the actions that are indicated in the additional messages.

BMC115008C

Task taskid ended prematurely|with bad RC completion code= return code

Explanation: A utility task ended prematurely. Processing continues. The task completion code is displayed.

User response: Contact BMC Customer Support.

BMC115009I

Listing of ddname control statements:

Explanation: A list of indicated ddname control statements follows this message. Processing continues.

User response: No action is required.

BMC115010C

Control card error. text

Explanation: One or more control statements are in error. The text explains the reason. The job step terminates abnormally.

User response: Ensure that the control statement data set contains valid commands, keywords, and values.

BMC115011C

Data set dsname text

Explanation: While the product was retrieving or updating data set information from the catalog, an error was detected. The following values are valid for text :

The job step terminates abnormally.

User response: Correct the problem indicated by the text. If the problem persists, contact BMC Customer Support.

BMC115012F

process failed, Return code return code Reason code reason code text

Explanation: The indicated internal process (such as GETMAIN or FREEMAIN) has failed. The return code and reason code are shown in hexadecimal format (X'xx') and decimal format (ddd). Explanatory text may also be displayed. The action taken depends on the error.

User response: If the text does not provide enough information for you to resolve the problem, check for a previous message that indicates a possible cause of the problem.

BMC115013I

dbd,*: ASID (addressspaceid) function started in procstepname.jobname STC

Explanation: An external address space has been started to perform a the indicated function. Processing continues.

User response: No action is required.

BMC115014I

dbd,*: ASID (addressspaceid) function ended, procstepname.jobname STC RC= returncode. Elapsed=elapsed time. CPU=CPU time. SRB=SRB time. EXCP=number of EXCPs

Explanation: The address space for the indicated procestepname.jobname ended. The message provides the elapsed, CPU, and supervisor request block (SRB) time. An EXCP count is also provided. Processing continues.

User response: No action required.

BMC115015I

DBRC Authorization for database database name is Exclusive|Update|Read|Read-only

Explanation: The job has acquired the specified access to the database. Processing continues.

User response: No action is required.

BMC115016C

DBRC Authorization failed for database dbdname. Return code returncode, reason code reasoncode

Explanation: The job could not obtain authorization for the indicated database. DBRC processing for the database terminates.

User response: Select one of the following responses:

• If you receive reason code $$, check the output for other messages from DATABASE INTEGRITY PLUS that indicate a label problem. Correct the problem.
• If you receive reason code 03, ensure that the DBI-CRF-LINK has been done and that the hook resides in the batch job, the control region, and the DBRC region. If you receive any other reason code, refer to message DFS047A in the IBM publication, IMS/ESA Messages and Codes reference manual for an explanation of the reason code.

BMC115017C

process FAILED. RETURN CODE= rc text

Explanation: The indicated DBRC process has failed for the reason indicated by the text. The return code is shown in hexadecimal format. DBRC processing terminates.

User response: If the text does not provide enough information for you to resolve the problem, check the JES log for any DBRC-related messages that may provide more information about the cause of the problem. If the problem persists, contact BMC Customer Support.

BMC115018C

DATABASE dbdname IS NOT REGISTERED WITH DBRC

Explanation: The indicated dbdname is not registered in the RECON data set. DBRC processing for the database terminates.

User response: Ensure that the correct RECON data sets are being used. Use the INIT.DB and INIT.DBDS commands to define the database and its data sets to the RECON data sets, and resubmit the job.

BMC115019C

Database database name Area ddname is using data sets not registered with DBRC

Explanation: The indicated database data set is not registered in the RECON data set. DBRC processing for the database terminates.

User response: Ensure that the correct and complete RECON data set and database data sets are being used, and resubmit the job. Use the INIT.DB and INIT.DBDS commands to define the database and its data sets to the RECON data sets, and resubmit the job.

BMC115020C

DATABASE database DDNAME ddname IS USING DATA SETS NOT REGISTERED WITH DBRC

Explanation: The data set name that is defined in the RECON data set for the indicated dbdname does not match the name in the JCL. DBRC processing for the database terminates.

User response: Ensure that the correct RECON data set and database data sets are being used, and resubmit the job.

BMC115021C

UNABLE TO LOCATE CONTROL BLOCK block

Explanation: The program was unable to locate the indicated internal IMS or BMC control block. The job step terminates.

User response: Check for a previous message that indicates a possible cause of the problem. If the problem persists, contact BMC Customer Support.

BMC115022C

UNABLE TO LOCATE MODULE 'module'

Explanation: The product is unable to locate the indicated module. The job step terminates.

User response: Ensure that the correct libraries are included in the STEPLIB, JOBLIB, or LINKLIST concatenations, and resubmit the job.

BMC115023C

DBRC ABNORMALLY TERMINATED. text

Explanation: A DBRC function failed, causing DBRC to terminate. The text explains the problem. The job step terminates.

User response: If the text does not provide enough information for you to resolve the problem, check for a previous message that indicates a possible cause of the problem.

BMC115024C

DBRC REORG PROCESSING FAILED ON DATABASE dbdname, RETURN CODE= rc

Explanation: The product encountered an error while performing the DBRC NOTIFY.REORG function. The return code is shown in hexadecimal format. DBRC processing terminates.

User response: Refer to any DBRC-related error messages in the job to determine a possible cause of the problem.

BMC115025C

Error rewriting RECON record. RECON key= key

Explanation: The product encountered an error while attempting to rewrite a record to the RECON data set. DBRC processing for the database terminates.

User response: Refer to any DBRC-related error messages in the job to determine a possible cause of the problem.

BMC115026I

Stop text1(jobName) PSB(psbName) RGN(regionNumber) IMS(imsId) DBD(dbdName)

Explanation: This message appears when Fast Path Online Restructure/EP is about to start a brief outage before BMCPAU or DBR. Use the information in this message to issue the IMS command to stop a BMP, an IFP, or an MPR processing WFI-PWFI transactions. The Write to operator (WTO) macro appears on the console log and in the system messages. Processing continues and this message appears approximately every 4 minutes unless the dependent region (BMP, IFP, or MPR) is stopped. Fast Path Online Restructure/EP cannot progress unless the dependent region is stopped.

User response: Stop the dependent region (manually or automatically).

BMC115027I

Start text1(jobName) PSB(psbName) RGN(regionNumber) IMS(imsId)

Explanation: This message appears when a brief outage in Fast Path Online Restructure/EP is finished. Use the information in this message to issue the IMS command to start a BMP, an IFP, or an MPR processing WFI-PWFI transaction. The Write to operator (WTO) macro appears on the console log and in the system messages. Processing continues.

User response: Start the dependent region (manually or automatically).

BMC115028C

Invalid DBRC request option Y|N. DBRC usage forced by IMSGEN.

Explanation: The indicated DBRC processing option specified in the JCL parameters or in the PLUSIN control statement data set is not compatible with the value from the IMS generation. The job step terminates.

User response: Specify the correct DBRC option, and resubmit the job.

BMC115029I

DBRC Authorization released for database database name

Explanation: The job has released DBRC authorization for the indicated database. Processing continues.

User response: No action is required.

BMC115030C

ABEND issued by process. ABEND code abend code, Reason code reason

Explanation: The indicated entity issued an abend. The following values are valid for entity:

• DBRC REQUEST HANDLER
• DBRC SUBTASK
• SWAP PROCESSOR

The job step terminates abnormally.

User response: Refer to previous messages to determine the cause of the abend.

BMC115031I

NOTIFY.REORG DBD(dbdname) RUNTIME timestamp

Explanation: The NOTIFY.REORG command was issued for the indicated database. Processing continues.

User response: No action is required. For more information about the DBRC parameters listed in the message text, refer to the IBM publication IMS/ESA Utilities Reference: System.

BMC115032I

NOTIFY.ALLOC DBD(dbdname) DDN(ddname) ALLTIME allocation timestamp STARTTIME start timestamp

Explanation: The NOTIFY.ALLOC command was issued for the indicated database and ddname. Processing continues.

User response: No action is required. For more information about the DBRC parameters listed in the message text, refer to the IBM publication IMS/ESA Utilities Reference: System.

BMC115033I

NOTIFY.ALLOC DBD(dbdname) DDN(ddname) ALLTIME allocation timestamp DEALTIME deallocation timestamp

Explanation: The NOTIFY.ALLOC command was issued for the indicated database and ddname. Processing continues.

User response: No action is required. For more information about the DBRC parameters listed in the message text, refer to the IBM publication IMS/ESA Utilities Reference: System.

BMC115034I

NOTIFY.IC DBD(dbdname) DDN(ddname) ICDSN(image copy dsname) RUNTIME timestamp

Explanation: The NOTIFY.IC command was issued for the indicated database, ddname, and image copy data set name. Processing continues.

User response: No action is required. For more information about the DBRC parameters listed in the message text, refer to the IBM publication IMS/ESA Utilities Reference: System.

BMC115035I

dbd: NOTIFY.UIC DBD( dbdname ) AREA(ddname) RUNTIME timestamp

Explanation: The NOTIFY.UIC command was issued for the indicated database and ddname. Processing continues.

User response: No action is required. For more information about the DBRC parameters listed in the message text, refer to the IBM publication IMS/ESA Utilities Reference: System.

BMC115036I

function STARTIME timestamp DSN(DSN) ERROR|NORMAL

Explanation: The indicated DBRC command was issued for the indicated data set name and ended normally or with an error. Processing continues or terminates, depending on the message text.

User response: No action is required. For more information about the DBRC parameters listed in the message text, refer to the IBM publication IMS/ESA Utilities Reference: System.

BMC115037I

CHANGE.DB DBD(dbdname) DBRC value

Explanation: The CHANGE.DB command was issued for the indicated database. Processing continues.

User response: No action is required. For more information about the DBRC parameters listed in the message text, refer to the IBM publication IMS/ESA Utilities Reference: System.

BMC115038I

CHANGE.DBDS DBD(dbdname) AREA(DD) DBRC value

Explanation: The CHANGE.DBDS command was issued for the indicated database and ddname. Processing continues.

User response: No action is required. For more information about the DBRC parameters listed in the message text, refer to the IBM publication IMS/ESA Utilities Reference: System.

BMC115039I

NOTIFY.RECOV DBD(dbdname) DDN(ddname) RCVTIME timestamp CURRENT

Explanation: A NOTIFY.RECOV was issued for the indicated DBD (dbdname) and ddname. The recovery time stamp is provided. Processing continues.

User response: No action is required.

BMC115040C

RECOVERY NEEDED COUNT FOR DATABASE dbdname IS ZERO BUT DATA SET ddname HAS RECOVERY-NEEDED FLAG ON

Explanation: An illogical condition has been found in the RECON. The RECOVERY NEEDED count for the database is zero, but one of the data sets has the RECOVERY NEEDED flag on. The utility terminates.

User response: Determine how this condition occurred and correct the problem.

BMC115041I

dbd: NOTIFY.REORG DBD(dbdname) AREA(areaname) RUNTIME timestamp

Explanation: The NOTIFY.REORG command was issued for the indicated database and area. Processing continues.

User response: No action is required. For more information about the DBRC parameters that are listed in the message text, refer to the IBM publication IMS DBRC Guide and Reference.

BMC115042C

DBRC processing terminated due to unavailable RECON data sets

Explanation: DBRC was unable to open the RECON data sets because they were not specified in the JCL and the MDA members were not found in the STEPLIB libraries. The job step terminates.

User response: Add the MDA library that contains the RECON MDAs to the STEPLIB concatenation, and resubmit the job.

BMC115050I

text BMP jobname subsystem subsystem id

Explanation: The Online Restructure function has detected BMPs running on the indicated subsystem. If the indicated BMP is preventing a successful /DBR, this message might be issued with BMC115051R, BMC115052R, or both. The following values are valid for text:

• Stop
• Restart
• AR/CTL stop request for
• AR/CTL restart request for
• AR/CTL stop request failed for

No action is required.User response: Stop or restart the indicated BMPs. If the BMC APPLICATION RESTART CONTROL (AR/CTL) product is controlling the BMPs, AR/CTL takes the appropriate action. If AR/CTL is not controlling the BMPs, stop or restart the BMPs as indicated.

BMC115051I

/DBR not successful on Subsystem imsid for database dbdname

Explanation: This WTO message informs you that the /DBR command was not able to stop the indicated database on the indicated subsystem name. Refer to message BMC115052R.

User response: Refer to message BMC115052R.

BMC115052R

Reply 'R' for retry or 'C' for cancel. Current job name is jobName

Explanation: A condition has occurred that requires you to respond. The product waits for your response.

User response: Your response depends on the message preceding this message. Determine the reason for this message. Then enter C to cancel the job or R to retry the job.

BMC115053W

Job jobname has not received a reply to 'IMS command ' sent to IMS subsystem on date at time

Explanation: This message is displayed when a job has waited for a period of time but has not received a reply from the IMS control region. This action is usually caused by a lost XCF message. Search the console log for messages prefixed with IXC. Use this message to determine the appropriate response by using the Automated Operator interface. The utility continues.

User response: No action is required.

BMC115054I

Reply to message number was reply

Explanation: An operator replied to the indicated message with the indicated reply. Processing continues.

User response: No action is required.

BMC115055W

IMS command (IMS command) failed. See IMS Log.

Explanation: An IMS command sent to the IMS control region has not completed successfully. Processing continues.

User response: Check the IMS control region log to determine the reason for the failure.

BMC115056I

IMS Subsystem subsystem id Added|Removed.

Explanation: The indicated IMSID was connected or disconnected. This message is issued during start-up, termination, or reorganization. If the message is issued during reorganization, it indicates that an IMS subsystem was started or stopped. Processing continues.

User response: No action is required.

BMC115057I

dbd: Command sent to IMS (imsid): command

Explanation: The command was sent to the IMS subsystems from where the original connection was made. (Refer to message BMC115056I.) Processing continues.

User response: No action is required.

BMC115058C

BMC Region Controller must precede the IBM version in the STEPLIB concatenation

Explanation: The BMC version of the region controller (DFSRRC00) must be first in the STEPLIB DD concatenation. Processing terminates.

User response: Place the library containing the BMC version of DFSRRC00 in front of any other libraries containing this module.

BMC115059I

dbd: CHANGE.ADS DBD(dbdname) AREA(areaname) ADDN (areaname) available|unavailable|failed Return code nnnn

Explanation: The CHANGE.ADS command was issued for the indicated database, area, and area DD statement. Processing continues.

User response: No action is required. For more information about the DBRC parameters that are listed in the message text, refer to the IBM publication IMS DBRC Guide and Reference.

BMC115060C

ASID (addressspaceid) failed to start in procname.jobname. Check console messages.

Explanation: The product attempted to start the indicated address space, but the address space failed to execute. Processing terminates.

User response: Review the console log messages to determine a possible cause of the problem. Possible causes could be that an invalid procedure was specified on the IFP_PROCNAME keyword, an invalid job name was specified on the IFP_JOBNAME keyword, or security rules restrict the creation of started tasks.

BMC115064E

NOTIFY.IC DBD (dbdname) AREA (areaname) ICDSN (imagecopy DSN) RUNTIME timestamp has failed. Return code=returncode Reason=reason

Explanation: The NOTIFY.IC command issued for the database, area, and image copy data set name failed because the image copy is not registered in the RECON. Processing continues. The area cannot be started until a valid image copy is registered.

User response: Take an image copy of the area, and then start the area manually.

BMC115065F

NOTIFY.IC DBD (dbdName) AREA (areaName) ICDSN (imagecopy DSN) RUNTIME timestamp has failed. The image copy was recorded in the RECON, but it could not be updated to indicate it is a Snapshot image copy. Return code=returnCode Reason=reason

Explanation: The NOTIFY.IC command was issued for the indicated database, area, and image copy data set name. However, the image copy entry in the RECON could not be updated to indicate it is a Snapshot image copy. Processing terminates.

User response: The image copy entry in the RECON is not usable for standard recovery processing. However, the image copy data set name (ICDSN) is a valid copy of the area after the restructure. BMC recommends that you create an image copy of the area manually, before issuing a start of the area. This action ensures that any required recovery of the area is successful.

BMC115068W

OM not active. Falling back to TYPE1 commands

Explanation: Operations Manager is inactive in IMSPLEX, so the RESTRUCTURE function will continue to issue TYPE1 commands. Processing continues. The job ends with return code RC=4.

User response: Activate the Operations Manager so that the RESTRUCTURE function can issue TYPE2 commands for future runs.

BMC115069I

OMA join successful for plexName - RESTRUCTURE will issue TYPE2 commands

Explanation: OMA has successfully joined the specified IMSPLEX on the OPTIONS command. The RESTRUCTURE function will start issuing TYPE2 commands. Processing continues.

User response: No action is required.

BMC115070W

OMA join failed for plex plexName Return code returnCode Reason code reasonCode falling back to TYPE1 commands

Explanation: OMA has not been able to join the specified IMSPLEX on the OPTIONS command. The RESTRUCTURE function continues to issue TYPE1 commands. Processing continues with return code RC=4.

User response: Contact BMC Support.

BMC115071I

OMA leave successful for plex plexName

Explanation: OMA has successfully left the specified IMSPLEX. Processing continues.

User response: No action is required.

BMC115072I

OMA leave failed for plex plexName - Return code returnCode Reason code reasonCode

Explanation: OMA termination has failed. The job continues to run successfully.

User response: Contact BMC Support.

BMC115073I

dbdName;areaName: TYPE2 command sent to IMS(IMSID) : TYPE2 command text

Explanation: The TYPE2 commands have been sent to the specified IMS subsystem. Processing continues.

User response: No action is required.

BMC115075I

dbdName:areaName Command executed successfully - Return code returnCode Reason code reasonCode

Explanation: The TYPE2 command has executed successfully. Processing continues.

User response: No action is required.

BMC115076W

dbdName:areaName Command failed - Return code returnCode Reason code reasonCode - falling back to TYPE1 commands

Explanation: The TYPE2 command has failed. The RESTRUCTURE function will continue to run the job and issue the TYPE1 commands. Processing continues.

User response: Contact BMC Support.

BMC115080I

ASID (addressspaceid) dbd, *: Area Scan started task name changed from <procname>.<jobname> to <procname>.<jobname>

Explanation: The started task name for Area Scan has been changed because the job name started with @, #, or $. The first character of the job name has been changed to ‘P’ in the started task name only. The job name, which is used as an identifier in the started task name, and should start with an alphabet as per the started task naming conventions.

User response: No action is required.

BMC115081I

A program is preloaded by the DFSMPLXX PROCLIB member, the UPDATE PGM REFRESH CMD is ignored

Explanation: If a program is preloaded by the DFSMPLXX PROCLIB member, the UPDATE PGM REFRESH CMD is ignored.

User response: No action is required.

BMC115090I

ASID (addressspaceid)  dbd, *: Area Copy started task name changed from <procname>.<jobname> to <procname>.<jobname>

Explanation: The started task name for Area Copy has been changed because the job name started with @, #, or $. The first character of the job name has been changed to ‘P’ in the started task name only. The job name, which is used as an identifier in the started task name, and should start with an alphabet as per the started task naming conventions.

User response: No action is required.