Messages BMCIPR5500 through BMCIPR5999

This group includes messages for the BMC system administration family of products for IMS.
Number Description
BMCIPR5501I

Energizer for IMS Connect ProductLevel:productLevel Date:date


Explanation: This message indicates the level and maintenance date of the Energizer for IMS product that is currently active in the IMS Connect address space.

User response: No action is required.

BMCIPR5502I

Energizer for IMS Connect Initialization In Progress


Explanation: The product is performing initialization processing in the IMS Connect address space.

User response: No action is required.

BMCIPR5503I

Energizer for IMS Connect Initialization Complete


Explanation: The product successfully completed the initialization process in the IMS Connect address space.

User response: No action is required.

BMCIPR5504I

Energizer for IMS Connect Termination In Progress


Explanation: The product has started termination processing in the IMS Connect address space.

User response: No action is required.

BMCIPR5505I

Energizer for IMS Connect Termination Acknowledged


Explanation: A shutdown request was received and termination processing in the IMS Connect address space will begin.

User response: No action is required.

BMCIPR5506I

Energizer for IMS Connect Termination Complete


Explanation: Termination processing completed within the IMS Connect address space.

User response: No action is required.

BMCIPR5507E

Energizer for IMS Connect productTask Task abended, RC=returnCode


Explanation: The indicated product task abended with the indicated abend code. IMS Connect abends.

User response: Contact BMC Customer Support.

BMCIPR5508I

Energizer for IMS Connect is inactive, IPROPTS DD statement missing


Explanation: The IPROPTS DD statement was not found in the IMS Connect address space. IMS Connect initializes without the product.

User response: Ensure that the product was properly installed.

BMCIPR5509E

Energizer for IMS Connect could not locate required HWSUINIT routine


Explanation: The product is not active in the IMS Connect address space and the required user exit, HWSUINIT could not be located in the STEPLIB concatenation. IMS Connect abends.

User response: HWSUINIT must be present in the STEPLIB concatenation when the product is not active.

BMCIPR5510I

Energizer for IMS Connect calling customer HWSUINIT routine for {INITIALIZATION | TERMINATION}


Explanation: The customer user initialization exit, HWSUINIT is being called for INITIALIZATION or TERMINATION processing.

User response: No action is required.

BMCIPR5511E

Customer HWSUINIT routine returned RC=returnCode, IMS Connect will terminate


Explanation: The customer user initialization exit, HWSUINIT was called for initialization and returned a return code of 8 or higher. This indicates that IMS Connect should terminate. Control is returned to IMS Connect and the system will terminate.

User response: Determine the reason for the error and correct the problem.

BMCIPR5512W

Unable to complete dubbing process. ISPF discovery may be unavailable


Explanation: The attempt to connect to the kernel for z/OS Unix System services (the dubbing process) failed. The system cannot determine the IP address of the IMS Connect for ISPF discovery function. Processing continues, but discovery might not occur in the ISPF interface.

User response: No action is required.

BMCIPR5513W

Unable to obtain host IP address at initialization. ISPF discovery may be unavailable


Explanation: The get host IP function failed. The system cannot determine the IP address of the IMS Connect system and, therefore, cannot load the discovery table. Processing continues, but discovery might not occur in the ISPF interface.

User response: No action is required.

BMCIPR5515E

HWSUINITProcessing Error, Energizer for IMS Connect is inactive


Explanation: An error occurred during the processing of the product HWSUINIT routine. IMS Connect initialization continues but the product will not be active.

User response: Review the error messages issued to the IMS Connect job log to determine what error occurred. Correct the problem and restart IMS Connect. Contact BMC Customer Support, if necessary.

BMCIPR5517E

Function functionName failed for functionTarget


Explanation: An internal error was encountered while processing the indicated function. The second operand indicates the target of the function. The system action depends on the processing that was taking place at the time of the error.

User response: Review any additional messages to determine what was taking place at the time of the error and contact BMC Customer Support.

BMCIPR5518E

Function functionName failed for functionTarget, RC=returnCode


Explanation: An internal error was encountered while processing the indicated function. The second operand indicates the target of the function. The function return code is also displayed. The system action depends on the processing that was taking place at the time of the error.

User response: Review any additional messages to determine what was taking place at the time of the error and contact BMC Customer Support.

BMCIPR5519E

STORAGE OBTAIN failed for target, RC=returnCode


Explanation: An internal error was encountered during a STORAGE OBTAIN macro call. The first operand specifies the target of the storage call. The function return code is also displayed. The system action depends on the processing that was taking place at the time of the error.

User response: Review any additional messages to determine what was taking place at the time of the error. You might need to increase the region size of the affected address space. Contact BMC Customer Support, if necessary.

BMCIPR5520I

productTask TCB Initialization Complete


Explanation: The indicated product task has completed the initialization process.

User response: No action is required.

BMCIPR5522I

productTask TCB Termination Complete


Explanation: The indicated product task has completed the termination process.

User response: No action is required.

BMCIPR5525E

Energizer for IMS Connect logic error in CSECT csect at label label


Explanation: An unrecoverable logic error was detected by the indicated CSECT at the indicated label. This abend might be caused by recently applied maintenance. The affected address space abends.

User response: Review any maintenance documentation that you have received from BMC. Apply the fix or circumvention, or contact BMC Customer Support.

BMCIPR5530E

Open failed for DDname IPROPTS


Explanation: An attempt to open the data set allocated to the IPROPTS DDname failed. The process executing at the time of the error fails.

User response: Review any additional messages to determine what was taking place at the time of the error. Ensure that the data set is available.

BMCIPR5531E

Load failed for IMS Connect options member memberName, RC=returnCode


Explanation: A LOAD for the indicated IMS Connect options member failed with the indicated return code. The action being performed fails.

User response: Ensure that the specified member is located in IPROPTS data set.

BMCIPR5532E

IMS Connect options member memberName is invalid


Explanation: Verification for the indicated IMS Connect options member failed. Validation of internal fields failed. The options member is invalid and unusable. If the address space is initializing, it will abend.

User response: Ensure that the indicated options member was created by using the console.

BMCIPR5533E

Load failed for Global options member memberName, RC=returnCode


Explanation: An attempt to load the indicated Global options member failed with the indicated return code. The options member is invalid and unusable. If the address space is initializing it will abend.

User response: Ensure that the indicated options member is located in the load library allocated to the IPROPTS DD statement.

BMCIPR5534E

Global options member memberName is invalid


Explanation: The indicated Global options member is invalid. The options member is invalid and unusable. If the address space is initializing it will abend.

User response: Ensure that the indicated options member was created by using the console. Edit the options by using the console and ensure that they are valid.

BMCIPR5540E

Invalid message type encountered, request not supported


Explanation: An XCF message has been received but contains an invalid request type (request). This error is an internal error. The message is rejected and cannot be processed.

User response: Contact BMC Customer Support.

BMCIPR5541I

Member system has {JOINED | LEFT} the XCF group groupName


Explanation: The indicated member system has either JOINED or LEFT the indicated XCF group.

User response: No action is required.

BMCIPR5542E

XCF SEND to partner failed, RC=returnCode, User=user


Explanation: An attempt to send a message using XCF services to the indicated user failed with the indicated return code. The requested function fails.

User response: Contact BMC Customer Support.

BMCIPR5545E

EMCS console consoleName is in use and cannot be started


Explanation: The indicated EMCS console is in use and is unavailable to Energizer. If the name ends in asterisks, all matching numeric values are in use. The command is issued, but no responses can be returned.

User response: Ensure that the indicated console is available for use by the IMS Connect address space.

BMCIPR5546E

Console function macro function failed, RC=returnCode, reason code=reasonCode


Explanation: A console macro with the indicated function failed. The return code and reason code are displayed in hexadecimal. (An invalid console name will result in an MCSOPER error RC=0010, RS=0008). The command is issued, but no responses can be returned.

User response: Determine the reason for the macro failure. Contact BMC Customer Support, if necessary.

BMCIPR5547I

Console consoleName is {ACTIVE|INACTIVE}, wait time is number.number seconds, quiesce time number.number minutes


Explanation: The indicated console is ACTIVE or INACTIVE as an EMCS console. The wait time is the default used to capture command responses. The quiesce time is the default used to stop an inactive console.

User response: No action is required.

BMCIPR5550E

Invalid message received, segment segment not found


Explanation: An XCF message was received and is being processed. However, the message does not include one or more of the required segments. The variable segment indicates which segment is missing or in error. The message is rejected and cannot be processed.

User response: Ensure that the XCF group being used by the address space (specified in the address space processing options) is not being used for anything other than this product. Contact BMC Customer Support.

BMCIPR5551E

User blocks not found for userid userID


Explanation: A response message was received by the address space but the user blocks associated with the specified userid could not be located. The output cannot be returned to the user.

User response: If the problem persists, contact BMC Customer Support.

BMCIPR5552E

XCF member with token tokenName not found, message discarded


Explanation: An XCF message was received by this address space but a member with the specified XCF token could not be found in the list of XCF members. The following reasons are the most common reasons for this message:

  • The partner system terminated after the message was sent.

  • The XCF group being used by the product is not unique and is being used by other address spaces for other purposes.

The message is discarded.

User response: Ensure that the XCF group name specified for the product is unique. To display all of the members that are joined to the XCF group, issue the following command to the MVS console: /D XCF,GROUP,groupName,ALL where groupName is the XCF group name specified in the options. Ensure that all of the members joined to the group are associated with the product.

BMCIPR5553E

Signon error for user process error RC=returnCode


Explanation: An attempt to sign on a user has failed with the indicated return code. This error is probably an internal logic error. The user process identifier is shown. The command being entered is rejected.

User response: Re-input the command. Contact BMC Customer Support.

BMCIPR5554E

Signoff error for userid userID


Explanation: An attempt to sign off the specified user ID after successful command completion failed. This error is probably an internal logic error.

User response: Contact BMC Customer Support.

BMCIPR5555I

Maximum user threshold reached


Explanation: The maximum number of users was reached. No new processes can be initiated until some of the active users are terminated. The process is rejected.

User response: Wait for some of the work that is in progress to complete and retry the operation. Contact BMC Customer Support if the problem persists.

BMCIPR5556E

Cleanup processing in progress for user user


Explanation: During the execution of a user request, the partner system terminated. Cleanup processing is being performed for the indicated user, which had a request in process waiting on the terminated system. The process is terminated.

User response: Determine the reason for the partner system failure.

BMCIPR5557E

Cleanup processing failed for user userID - controlBlock not found


Explanation: An error has occurred while attempting to clean up the internal control blocks associated with the indicated user ID. The message indicates the type of control block that is in error.

User response: Contact BMC Customer Support.

BMCIPR5558I

Command execution started for ddname member memberName


Explanation: Processing of a commands member started.

User response: No action is required.

BMCIPR5559I

count commands executed from ddname member memberName, RC=returnCode


Explanation: Processing of a commands member completed. The return code shown is the maximum return code from the commands executed.

User response: No action is required.

BMCIPR5560E

Command execution aborted for ddname member memberName due to errors


Explanation: Processing of a commands member terminated.

User response: Review previous messages to determine the cause of the error.

BMCIPR5600I

Reset of security profiles not performed, profiles are not cached


Explanation: An attempt to reset the incore security profiles associated with the message exit security feature could not be performed because the profiles are not currently being cached.

User response: No action is required.

BMCIPR5601I

type options reload processing complete


Explanation: Reload processing completed for the indicated options type. Changes specified in the new options were activated.

User response: No action is required.

BMCIPR5602E

type options reload processing failed


Explanation: Reload processing failed for the indicated options type. No changes to the specified options were made.

User response: Review any additional messages in the address space job log to determine what errors have occurred.

BMCIPR5603W

type options reload processing complete, some parameters were not updated


Explanation: Reload processing completed successfully for the indicated options type, but some fields that require a restart to change were not updated. Only those parameters that can be changed dynamically were updated. Other fields require that the address space be recycled.

User response: Review the documentation relating to the options to see which options cannot be changed by RELOAD.

BMCIPR5604I

Reset of security profiles complete


Explanation: Security profiles were successfully reset.

User response: No action is required.

BMCIPR5605E

Reset of security profiles failed


Explanation: Reset of security profiles failed. Caching of security profiles is inactive.

User response: Review any additional messages in the IMS Connect address space job log to determine what errors have occurred.

BMCIPR5701I

Exit exitName is defined as a VIRTUAL exit - the IMS Connect definition and the exit load module are not used


Explanation: The specified message exit is defined in the IMS Connect configuration member (HWSCFG=) but was defined in the Message Exit options as a VIRTUAL exit. The message exit is treated as a VIRTUAL exit. The load module containing the customer exit is not used.

User response: Change the Message Exit options to make the exit a CUSTOMER exit if you want to use the load module.

BMCIPR5702E

Message exit exitName is already defined


Explanation: The indicated message exit is a duplicate of a previously defined exit. The message exit definition is ignored.

User response: Ensure that the Message Exit options is correct.

BMCIPR5703E

Message id msgID (X'hexMsgID') for exit exitName is already defined for exit exitName and is ignored


Explanation: During Message Exit initialization or reload processing, a duplicate message identifier was encountered. The first operand displays the message ID in character format and the second operand displays the same string in hexadecimal format. The first exitName in the message is the one that contains the duplicate definition. The second exitName is the previously defined exit that contains the same string. At initialization, the Message Exit definition for the first exitName in the message is ignored. No exit will be created for that name. The second exitName in the message remains active and valid. If this error occurs during a reload, the first exitName in the message is deleted. The exit might continue to use a slot in the exit table, but will not be displayed and cannot be used.

User response: Ensure that the Message Exit options is correct.

BMCIPR5704E

Maximum number of message exits reached


Explanation: The maximum number of message exits has been reached. Based on the IMS Connect level that you are running, the maximum number of message exits that are allowed is 15 or 255. The message exit definition is ignored and the associated exit is inactive.

User response: Ensure that the Message Exit options are correct.

BMCIPR5705E

Message exit exitName is inactive - error security routine module


Explanation: An attempt to activate the security routine for the indicated message exit failed. The message exit is inactive.

User response: See the associated message for the error and reason codes that indicate the cause of the problem. Specify a valid security exit in the options for the message exit.

BMCIPR5706E

Message exit exitName is inactive - error loading translate table module


Explanation: An attempt to activate the translation table for the indicated message exit failed. The message exit is inactive.

User response: See the associated message for the error and reason codes that indicate the cause of the problem. Specify a valid translation table in the options for the message exit.

BMCIPR5707E

Router services unavailable for message exit exitName not defined in options


Explanation: The indicated message exit was defined in the HWSCFG= configuration but was not defined in the Message Exit options. Router services are not available for any exits not defined in the Message Exit options. Router services will not be invoked for messages processed by the indicated message exit.

User response: If router services are desired for this exit, define the exit in the Message Exit options.

BMCIPR5708E

Router services unavailable for message exit exitName due to prior error


Explanation: Router services are not available for the indicated message exit due to a previous error. Router services will not be invoked for messages processed by the indicated message exit.

User response: Review messages to determine the associated error and correct the problem.

BMCIPR5709E

Load failed for module module (abend code code)


Explanation: The indicated module could not be loaded for the indicated reason. The system action depends on the process that was being performed at the time of the error. The associated exit might be made inactive.

User response: Review associated messages for the message exit, and correct the problem.

BMCIPR5710E

Message exit exitName cannot be found and is now inactive


Explanation: The indicated message exit could not be found. The message exit will not be loaded and will be inactive.

User response: Ensure that the specified member name of the message exit is correct and that the member exists in the module search path.

BMCIPR5711I

Message Exit options memberName from configurationDate in use


Explanation: The indicated Message Exit options member is being used and the configuration date is displayed .

User response: No action is required.

BMCIPR5712I

Message Exit options reload process initializing


Explanation: A request to reload the Message Exit options was received and is being processed. The Message Exit options will be reloaded and associated changes made to the processing options.

User response: No action is required.

BMCIPR5713I

Message Exit options reload process complete


Explanation: A request to reload the Message Exit options successfully completed.

User response: No action is required.

BMCIPR5714W

Message Exit options reload process completed with errors


Explanation: A request to reload the Message Exit options completed but some errors were encountered.

User response: Review the messages issued to determine what errors were encountered.

BMCIPR5715E

Message Exit options reload process failed


Explanation: A request to reload the Message Exit options failed.

User response: Review the messages issued to determine what errors were encountered.

BMCIPR5716E

msgIDNumber'msgIDValue' returned from message exit exitName does not match definition 'msgIDValue'


Explanation: The INIT subroutine was called for the indicated message exit and returned the first msgIDValue indicated in the message. The Energizer message exit options definition contained the second msgIDValue. This message might be issued when the INIT subroutine is called, and might also be issued when message exit options are reloaded, if the strings in the newly loaded options do not match those currently in use. msgIDNumber is either MSGID1 or MSGID2 depending on which msgid does not match. The msgIDValue will be displayed in EBCDIC if it contains only printable EBCDIC characters. It will be displayed in ASCII followed by -ASCII if it contains only ASCII characters with unambiguous EBCDIC translations. Otherwise, it will be displayed in hexadecimal. The indicated message exit is made inactive when this problem occurs after calling the INIT subroutine. The exit definition is ignored when this problem occurs while reloading message exit options.

User response: You have several options:

  • Change the definition so that the message IDs match and reload the message exit options.

  • Change the definition and deselect the Verify msgids option; the message IDs returned by the exit will be used. Then reload the message exit options.

  • Change the definition and select the Override msgids option; the message IDs in the definition will be used instead of those returned from the exit. Then reload the message exit options.

  • Change the message exit to return matching message IDs. Then reload the message exit.

BMCIPR5717E

CUSTOMER message exit exitName INITIALIZATION failed, exit returned RC=returnCode


Explanation: The indicated message exit was called for initialization processing and returned the indicated non-zero return code. The exit will be inactive.

User response: Correct the problem. Using Energizer, the exit may be changed and reloaded dynamically without restarting IMS Connect.

BMCIPR5718E

offset() offset specified is invalid


Explanation: The offset specified for the indicated parameter is invalid. The exit is marked in error and made inactive.

User response: Correct the problem and reissue the command.

BMCIPR5719I

msgIDNumber (msgIDValue) returned from message exit exitName overridden by msgid from options (msgIDValue)


Explanation: The INIT subroutine was called for the indicated message exit and returned the first msgIDValue indicated in the message. The Energizer message exit options definition contained the second msgIDValue. This message might be issued when the INIT subroutine is called, and might also be issued when message exit options are reloaded, if the message IDs in the newly loaded options do not match those currently in use. msgIDNumber is either MSGID1 or MSGID2 depending on which message ID does not match. Processing continues using the message ID from the exit definition.

User response: No action is required.

BMCIPR5720I

{CUSTOMER | VIRTUAL} messageExit {INITIALIZATION | TERMINATION} complete


Explanation: The indicated message exit completed INITIALIZATION or TERMINATION processing. The exit is either a CUSTOMER exit or a VIRTUAL exit.

User response: No action is required.

BMCIPR5721E

Message exit exitName inactive due to a prior error


Explanation: An attempt was made to change the indicated message exit but failed due to a prior error. The error might have occurred at initialization, which prevents the exit from being made active except with a restart of IMS Connect. The command is rejected.

User response: A restart is required to activate the exit.

BMCIPR5722I

Message exit exitName reloaded, assembly date assemblyDate


Explanation: The indicated message exit was successfully reloaded. The assembly date associated with the exit is also displayed.

User response: No action is required.

BMCIPR5723E

Message exit exitName reload failed, exit is now inactive


Explanation: An attempt to reload the specified message exit failed. The exit is marked inactive.

User response: Review other messages issued to determine the cause for the error. Correct the problem and then reissue the exit reload request.

BMCIPR5724W

Translate table module for message exit exitName was condition and cannot be reloaded


Explanation: The product could not reload the indicated translation table due to the indicated condition. The product cannot reload the following types of modules:

  • Modules in the link pack area (LPA) (unless you use dynamic LPA to make a new module available)

  • Modules in use within IMS Connect itself

  • Modules with an alias in use

  • Modules not previously loaded or not found

The reload does not occur, and the table's state remains unchanged.

User response: Ensure that the specified member name of the message exit is correct and that the member exists in the module search path. Also, ensure that the translate table is defined in the options correctly.

BMCIPR5725I

TCP/IP Client message exit {INITIALIZATION | TERMINATION} beginning


Explanation: Message exit initialization or termination is beginning for the TCP/IP type clients. Individual messages are issued as each exit is processed.

User response: No action is required.

BMCIPR5726I

LOCAL Client message exit {INITIALIZATION | TERMINATION} beginning


Explanation: Message exit initialization or termination is beginning for the Local type clients. Individual messages are issued as each exit is processed.

User response: No action is required.

BMCIPR5727E

Message exit exitName reload not allowed, exit is a Virtual exit


Explanation: An attempt was made to reload the indicated message exit but was not allowed because the exit is a virtual exit. The command is rejected.

User response: Changes associated with Virtual Exit processing must be done by making changes to the Message Exit options.

BMCIPR5728W

Security exit module for message exit exitName was condition and cannot be reloaded


Explanation: The product could not reload the indicated user exit due to the indicated condition. The product cannot reload the following types of modules:

  • Modules in the link pack area (LPA) (unless you use dynamic LPA to make a new module available)

  • Modules in use within IMS Connect itself

  • Modules with an alias in use

  • Modules not previously loaded or not found

The reload does not occur, and the user exit's state remains unchanged.

User response: Ensure that the specified member name is correct and exists in the module search path. Also, define the security exit in the options, or use the NEWNAME keyword on the command.

BMCIPR5729E

Virtual exit exitName is inactive due to error - type name cannot be reloaded


Explanation: The product attempted to reload the indicated exit or member that is associated with the specified VIRTUAL exit. However, the VIRTUAL exit is inactive due to a previous error. The command was rejected.

User response: A restart is required to activate the exit.

BMCIPR5730I

Security exit exitName for message exit exitName reloaded


Explanation: The indicated security exit associate with the indicated message exit has been reloaded.

User response: No action is required.

BMCIPR5731I

Message exit exitName deleted - exit now unavailable


Explanation: The indicated message exit was deleted. This might occur when reloading message exit options that do not contain the message exit. The message exit is made unavailable for future transactions. The indicated exit remains in the exit table but is marked as deleted so that it cannot be used.

User response: No action is required.

BMCIPR5732I

Message exit exitName is defined to IMS Connect and cannot be changed to a VIRTUAL exit


Explanation: The indicated message exit is defined in the IMS Connect configuration member (HWSCFG=). These exits cannot be treated as VIRTUAL exits. The message exit is treated as a CUSTOMER exit.

User response: Either remove the exit from the IMS Connect configuration member (if you want it to be a VIRTUAL exit) or change the Message Exit options to make the exit a CUSTOMER exit.

BMCIPR5733W

Message exit exitName reload failed, previous exit remains active


Explanation: An attempt to reload the indicated message exit has failed. The previous exit remains active with no change.

User response: Review other messages issued to determine the cause for the error and correct the problem, then reissue the exit reload request.

BMCIPR5734W

Message Exit options member not specified. Default is HWSJAVA0 only.


Explanation: The Message Exit options member was not specified in the IMS Connect options. By default, only the HWSJAVA0 exit is defined with routing inactive.

User response: Create a Message Exit options member to add other exits or use routing.

BMCIPR5735W

Energizer for IMS Connect routing bypassed for message exit exitName


Explanation: The IMSPLEX routing exits HWSCLSO0 and HWSCLSO1 will bypass Energizer routing.

User response: No action is required.

BMCIPR5736W

Duplicate exit name exitName in HWSCFG member ignored


Explanation: A duplicate exit name was found in the list of exits in the IMS Connect configuration member (HWSCFG=). The duplicate name is ignored.

User response: Correct the list of exits to avoid this message.

BMCIPR5737I

*PING RESPONSE* from exit exitName connect=connect system=system


Explanation: A virtual exit returned a message to the IMS Connect client in response to a PING command.

User response: No action is required.

BMCIPR5750W

Module module was condition and cannot be reloaded


Explanation: The product could not reload the indicated module due to the indicated condition. The product cannot reload the following types of modules:

  • Modules in the link pack area (LPA) (unless you use dynamic LPA to make a new module available)

  • Modules in use within IMS Connect itself

  • Modules with an alias in use

  • Modules not previously loaded or not found

The reload does not occur, and the module's state remains unchanged.

User response: Ensure that the specified member name is correct and that the member exists in the module search path.

BMCIPR5751E

Security function functionName failed, RC=returnCode, RACF return code=RACFReturnCode, reason code=reasonCode


Explanation: A RACROUTE macro request for the specified function failed. The return code, RACF return code, and reason code are displayed. The requested function is not processed.

User response: Ensure that the Security Class name specified in the IMS Connect address space options is a valid RACF class name. Look up the return and reason codes for the RACROUTE macro. Contact BMC Customer Support, if necessary.

BMCIPR5752E

Security violation, error, USER=user, RC=returnCode, RACFRC/RS=RACFReturnCode and RACFReasonCode


Explanation: A call was made to the Message Exit security routine, IPRHUMXC and it encountered a security violation. The SAF return code, and RACF return and reason codes are listed along with a description of the error, which might be one of the following:

  • not authorized for IMS Connect

  • SAF error checking IMS Connect

  • not authorized for transaction

  • SAF error checking transaction

  • user profile not defined

  • password is invalid

  • password has expired

  • new password is invalid

  • userid not in group

  • userid has been revoked

  • userid access to group revoked

  • verification failed

The message is rejected with reason code 240.

User response: Ensure that the Security Class name specified in the IMS Connect address space options is a valid RACF class name. Look up the return and reason codes for the RACROUTE macro. Contact BMC Customer Support, if necessary.

BMCIPR5753E

Security processing error, userid not available


Explanation: A call was made to the Message Exit security routine, IPRHUMXC and it encountered a parameter error. The user ID was not specified. The message is rejected with reason code 240.

User response: Ensure that the customer user exit has correctly specified the parameter list to the security routine. Contact BMC Customer Support, if necessary.

BMCIPR5754E

VIRTUAL exit name disabled - user exit name INIT call returned RC=code


Explanation: The indicated user virtual exit was called for initialization processing and returned the indicated nonzero return code. The virtual exit will be inactive.

User response: Correct the problem in the user exit.

BMCIPR5755E

VIRTUAL message exit exitName is inactive - error loading user exit module


Explanation: An attempt to activate the user exit for indicated virtual exit routine failed. The message exit is inactive.

User response: See the associated message for the error and reason codes that indicate the cause of the problem. Ensure that a valid user exit is specified in the options for the virtual exit.

BMCIPR5756I

User exit name for VIRTUAL exit name reloaded


Explanation: The indicated user exit that is associated with the indicated virtual exit has been reloaded.

User response: No action is required.

BMCIPR5757W

User virtual exit module for VIRTUAL exit exitName was condition and cannot be reloaded


Explanation: The product could not reload the indicated user exit due to the indicated condition. The product cannot reload the following types of modules:

  • Modules in the link pack area (LPA) (unless you use dynamic LPA to make a new module available)

  • Modules in use within IMS Connect itself

  • Modules with an alias in use

  • Modules not previously loaded or not found

The reload does not occur, and the module's state remains unchanged.

User response: Ensure that the specified member name is correct and that the member exists in the module search path. Also, ensure that the virtual exit is defined in the options, or use the NEWNAME keyword in the command.

BMCIPR5758E

function failed for VIRTUAL exit name IP list member name,RC=code


Explanation: An attempt to open, find, or read the indicated IP list member failed with the indicated return code. If the request was attempting to open or find a member during a reload, the reload failed and the previous list remains active. For all other failures, the virtual exit will be disabled.

User response: Ensure that the IP list member is present in the IMS Connect PROCLIB library.

BMCIPR5759I

IP list name for VIRTUAL exit name loaded


Explanation: The indicated trusted IP list that is associated with the indicated virtual exit was loaded or reloaded.

User response: No action is required.

BMCIPR5760W

IP list member not defined for VIRTUAL exit name - list not reloaded


Explanation: The product attempted to reload the trusted IP list that is associated with the indicated virtual exit, but no IP list member is defined in the options. The command was rejected.

User response: Define the IP list member in the options, or use the NEWNAME keyword in the command.

BMCIPR5761W

IP list member name for VIRTUAL exit name has invalid verb on line lineNumber: verb


Explanation: In PROCLIB, the indicated IP list member contains a line with an invalid verb. The message indicates the relative line number and the verb. The line was ignored.

User response: Ensure that the first word on the line is a valid IP list verb. See the IPR$IPLS sample member for valid verbs.

BMCIPR5762W

IP list member name for VIRTUAL exit name has invalid IP address on line lineNumber starting address/hostName


Explanation: In PROCLIB, the indicated IP list member contains a line with an invalid or missing IP address or host name. The message indicates the relative line number. If the IP address is missing, the message indicates the verb. Otherwise, the message indicates the first part of the invalid IP address or host name. The line was ignored.

User response: Ensure that the first word on the line is a valid IP list verb. Ensure that the next word is an IP address in dotted decimal format (for example, 123.123.123.123) or a valid host name that is known to the default domain name server (DNS).

BMCIPR5763W

IP list member name for VIRTUAL exit name has duplicate IP address on lines lineNumber and lineNumber


Explanation: In PROCLIB, the indicated IP list member contains lines with the same IP address, or contains host names that translate to the same IP address. The message indicates relative line numbers and the IP address. The second line was ignored.

User response: Ensure that the first word on the line is a valid IP list verb. Ensure that the next word is an IP address in dotted decimal format (for example, 123.123.123.123) or a valid host name that is known to the default domain name server (DNS). Ensure that each IP address is unique, and that host names translate to unique IP addresses.

BMCIPR5764E

IP list member name for VIRTUAL exit name contains no valid IP addresses or host names


Explanation: The indicated IP list member in PROCLIB contains no lines with a valid IP address or host name. The virtual exit will be inactive.

User response: Correct the problem (or problems) in the IP list member.

BMCIPR5765E

IP list member name for VIRTUAL exit name has rejected a message from IP address IPAddress


Explanation: The indicated IP list member requested 'rejection with a message' for an input message that was received from a specified IP address. The message was rejected as a security violation.

User response: No action is required.

BMCIPR5766E

Reload not allowed for CUSTOMER exit name


Explanation: You attempted to reload a virtual exit component, but the indicated exit is a CUSTOMER exit. Changes that are associated with virtual exit processing must specify the name of a virtual exit. The command was rejected.

User response: Replace the CUSTOMER exit name with the name of a virtual exit.

BMCIPR5799E

Security processing error, unable to locate internalControlBlock


Explanation: A call was made to the Message Exit security routine, IPRHUMXC and it encountered an error. The routine could not locate the internal control block indicated. This error is probably an internal error. The message is rejected with reason code 240.

User response: Contact BMC Customer Support.

BMCIPR5800E

Load failed for Router options member memberName, RC=returnCode


Explanation: An attempt to load the indicated Router options member failed with the indicated return code. The options member is invalid and unusable. If the address space is initializing it will abend.

User response: Ensure that the indicated options member is located in the load library allocated to the IPROPTS DD statement.

BMCIPR5801E

BLDL failed for Router options member memberName, RC=returnCode


Explanation: The indicated Router options member could not be located in the data set allocated to the IPROPTS ddname. The return code is also returned. The options member is invalid and unusable. If the address space is initializing it will abend.

User response: Ensure that the indicated options member is located in the load library allocated to the IPROPTS DD statement.

BMCIPR5802E

Router options member memberName is invalid


Explanation: Verification for the indicated Router options member failed. Validation of internal fields failed. The options member is invalid and unusable. If the address space is initializing it will abend.

User response: Ensure that the indicated options member was created by using the console.

BMCIPR5803I

Router options member memberName from configurationDate in use


Explanation: The indicated Router options member being used and the configuration date is displayed.

User response: No action is required.

BMCIPR5804I

Router {WLM | Statistical} support is now active, cycle time=cycleTime


Explanation: The Router feature determined that either WLM services or Statistical Routing was been chosen and has been initialized.

User response: No action is required.

BMCIPR5805E

Router WLM error service failure, RC=returnCode, RSN=reasonCode


Explanation: An error occurred during processing of the specified Router WLM service. The return and reason codes are displayed. The process being executed fails.

User response: Contact BMC Customer Support.

BMCIPR5806W

Router defined datastore datastoreName must be defined to IMS Connect


Explanation: The indicated datastore was specified in the Router options was not specified in the IMS Connect configuration member (HWSCFG=). No messages are routed to the indicated datastore.

User response: If the indicated datastore is valid, specify it in the HWSCFG= PROCLIB member.

BMCIPR5807W

IMS Connect defined datastore datastoreName is not defined in Router options


Explanation: The indicated datastore was specified in the IMS Connect configuration member (HWSCFG=) but was not defined in the Router options. No messages are routed to the indicated datastore.

User response: Specify the datastore in the Router options.

BMCIPR5808I

Router type support is now inactive


Explanation: Router WLM or statistical load balancing support was inactivated due to system termination or during RELOAD of router options.

User response: No action is required.

BMCIPR5809W

Router options member not specified. Routing is inactive


Explanation: The Router options member was not specified in the IMS Connect options. Routing is inactive.

User response: Create a router options member and update the IMS Connect options to activate routing.

BMCIPR5810I

Router options reload process initializing


Explanation: A request to reload the Router options was received and is being processed. The Router options will be reloaded and associated changes made to the processing options.

User response: No action is required.

BMCIPR5811I

Router options reload process complete


Explanation: A request to reload the Router options successfully completed.

User response: No action is required.

BMCIPR5812W

IMS Connect defined IMSPLEX name is defined in Router


Explanation: Energizer cannot route to IMSPLEX definitions. Any definitions found in the Router options will be ignored.

User response: No action is required.

BMCIPR5813I

Router defined datastore datastoreName is now in use


Explanation: The state of the router-defined datastore has changed as a result of a create datastore type-2 command and this datastore is now in use.

User response: No action is required.

BMCIPR5830E

Load failed for ODBM options member name, RC=returnCode


Explanation: Energizer for IMS Connect attempted to load the Open Database Manager (ODBM) options member that has the indicated name. The attempt failed with the indicated return code. The options member is invalid and unusable. If the address space was initializing, it terminated abnormally.

User response: Ensure that the specified options member is located in the load library that the IPROPTS DD statement allocates.

BMCIPR5831E

BLDL failed for ODBM options member name, RC=returnCode


Explanation: Energizer for IMS Connect attempted to locate the Open Database Manager (ODBM) options member that has the indicated name in the data set that the IPROPTS DD statement allocates. The attempt failed with the indicated return code. The options member is invalid and unusable. If the address space was initializing, it terminated abnormally.

User response: Ensure that the specified options member is located in the load library that the IPROPTS DD statement allocates.

BMCIPR5832E

ODBM options member name is invalid


Explanation: Energizer for IMS Connect attempted to verify the Open Database Manager (ODBM) options member that has the indicated name and found that internal fields are invalid. The options member is invalid and unusable. If the address space was initializing, it terminated abnormally.

User response: Make sure that the indicated options member was created by using the Data Management Console, also known as the graphical user interface (GUI).

BMCIPR5833I

ODBM options member name from configurationDate in use


Explanation: Energizer for IMS Connect used the Open Database Manager (ODBM) options member that has the indicated name and the indicated date of configuration. Processing continued.

User response: No action is required.

BMCIPR5834I

ODBM supportType support is now active, cycle time = value


Explanation: Energizer for IMS Connect successfully initialized the indicated type of Open Database Manager (ODBM) support for statistical routing. The indicated value was specified for the Cycle Time option to control the length of a cycle (in milliseconds). Processing continued.

User response: No action is required.

BMCIPR5838I

ODBM supportType support is now inactive


Explanation: Energizer for IMS Connect successfully inactivated the indicated type of Open Database Manager (ODBM) support for statistical routing. Processing continued.

User response: No action is required.

BMCIPR5839W

ODBM options member not specified. ODBM Routing is inactive


Explanation: Energizer for IMS Connect detected that the Open Database Manager (ODBM) options member was not specified in the IMS Connect options. ODBM routing was inactive.

User response: To activate ODBM routing, create an ODBM options member and update the IMS Connect options.

BMCIPR5840I

ODBM options reload process initializing


Explanation: Energizer for IMS Connect received a request to reload the Open Database Manager (ODBM) options member so that associated changes to the processing options could be implemented.

User response: No action is required.

BMCIPR5841I

ODBM options reload process complete


Explanation: Energizer for IMS Connect received a request to reload the Open Database Manager (ODBM) options member. The request was successful, and associated changes to the processing options were implemented.

User response: No action is required.

BMCIPR5843W

A target ODBM/ALIAS found in ODBM options is not active in IMS Connect or the IMSPLEX


Explanation: If a request is routed to the target alias default, routing will occur; requests will be round-robined to active ODBMs that are associated with the input alias name or to all ODBMs.

User response: Make sure that the specified resource is defined in the HWSCFG= configuration members, that the ODBM regions have been started and successfully initialized as a member of the correct IMSPLEX, and that the resource is active in IMS connect or the target ODBM.

BMCIPR5844I

The target ODBM/ALIAS was found to be inactive in IMS Connect, the IMSPLEX, or in ODBM but is now active


Explanation: Default routing is no longer enabled for the target ODBM/ALIAS, and normal routing will take place.

User response: This message is informational only. No action is required.

BMCIPR5850I

Datastore datastoreName state changed to {AVAIL | WARN | SEVERE}


Explanation: The indicated datastore state was changed to the indicated value of AVAIL, WARN, or SEVERE. Routing might be affected by the datastore state, resulting in fewer messages being routed to datastores in WARN and SEVERE states.

User response: No action is required.

BMCIPR5851I

Governor support is now {ACTIVE | INACTIVE}


Explanation: The Governor feature is now active or inactive. This message might be issued at IMS Connect initialization, termination, or when the Governor options are modified.

User response: No action is required.

BMCIPR5852W

Input transaction rate is now percentage of governor limit of number transactions/second!


Explanation: The governor determined that the input message rate exceeded the specified warning threshold specified in the IMS Connect address space options.

User response: Use the available displays to determine what the input message rate is and determine whether action needs to be taken to prevent exceeding the allowable threshold.

BMCIPR5853E

Governor limit of number transactions/second exceeded - rejecting arriving input!!!


Explanation: The governor determined that the input message rate exceeded the specified allowable threshold specified in the IMS Connect address space options. Input messages are rejected until the input rate drops below the allowable threshold.

User response: Use the available displays to determine what the input message rate is and determine whether action needs to be taken to reduce the rate.

BMCIPR5854W

Input message rate of number messages/second is less than Governor lower limit!


Explanation: The governor determined that the input message rate is lower than the allowable lower threshold specified in the IMS Connect address space options.

User response: Use the available displays to determine what the input message rate is and determine whether action needs to be taken.

Was this page helpful? Yes No Submitting... Thank you

Comments