BIP9000-9999: Runtime components - z/OS and Derby
- BIP9001
- Memory allocation error in <insert_0> heap for element <insert_1>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred during the allocation of memory out of heap <insert_0>. The memory was being allocated for element <insert_1>.
- Response
- Try restarting the component. If the problem persists contact your IBM support center. Provide the message text and a debug trace for further analysis.
- BIP9002
- Maximum number of threads reached.
- Severity
- 30 : Severe error
- Explanation
- The maximum number of concurrent threads has been reached.
- Response
- Try restarting the component. If the problem persists contact your IBM support center. Provide the message text and a debug trace for further analysis.
- BIP9003
- Maximum number of processes per address space reached.
- Severity
- 30 : Severe error
- Explanation
- The maximum number of processes per address space has been reached.
- Response
- Try restarting the component. If the problem persists contact your IBM support center. Provide the message text and a debug trace for further analysis.
- BIP9004
- An internal error was detected.
- Severity
- 30 : Severe error
- Explanation
- An internal error has been detected.
- Response
- Try restarting the component. If the problem persists contact your IBM support center. Provide the message text and a debug trace for further analysis.
- BIP9011
- Program not authorized.
- Severity
- 10 : Warning
- Explanation
- BIPIMAIN is started without sufficient authorization.
- Response
- Check that the product is correctly installed. If the problem persists contact your IBM support center.
- BIP9012
- Failed to create named token: <insert_0>. rc= <insert_1>x
- Severity
- 10 : Warning
- Explanation
- BIPIMAIN cannot create an MVS named token.
- Response
- There may be system resources limits, or BIPIMAIN is not running with sufficient authority. Check that the product is correctly installed. If the problem persists contact your IBM support center.
- BIP9013
- WEMPS internal parameter error.
- Severity
- 10 : Warning
- Explanation
- BIPIMAIN cannot pass the correct parameters to the embedded messaging engine.
- Response
- Check that the product is correctly installed and configured. If the problem persists contact your IBM support center.
- BIP9014
- BPX1WAT retcode= <insert_0>x, reasoncode= <insert_1>x
- Severity
- 10 : Warning
- Explanation
- BIPIMAIN obtained system errors when waiting for a process to terminate.
- Response
- Check that the product is correctly installed and configured. If the problem persists contact your IBM support center.
- BIP9101
- Invalid start mode <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The Control Process has been started with a start mode of <insert_0>. If defined, the start mode must be either AUTO or MAN. The parameter <insert_0> is ignored and the Control Process continues to start with start mode AUTO.
- Response
- Stop the component and restart the component with a valid start mode of either AUTO or MAN.
- BIP9102
- The component key start parameter is too long.
- Severity
- 30 : Severe error
- Explanation
- The component is started with a component key defined at customization time. This key, provided to the Control Process as the first parameter, is too long to be a component key. The component stops.
- Response
- Use the customized started task procedure to start the component. If you are using the generated started task procedure, check your customization and define a valid component key.
- BIP9103
- The component name is not provided.
- Severity
- 30 : Severe error
- Explanation
- The component name is retrieved from the environment. The value of variable MQSI_COMPONENT_NAME is either not defined or is empty. The component stops.
- Response
- Use the customized started task procedure to start the component. If you are using the generated started task procedure, check your customization and define a valid component name.
- BIP9104
- The component name is too long.
- Severity
- 30 : Severe error
- Explanation
- The component name is retrieved from the environment. The value of variable MQSI_COMPONENT_NAME is too long for a component name. Correct the name of the component and restart the program. The component stops.
- Response
- Use the customized started task procedure to start the component. If you are using the generated started task procedure, check your customization and define a valid component name.
- BIP9105
- The component name is too long.
- Severity
- 30 : Severe error
- Explanation
- The component name is retrieved from the command line. The value is too long for a component name. The Component stops.
- Response
- Check your customization for the correct component name, correct the command and retry it.
- BIP9106
- Mandatory program parameter missing.
- Severity
- 30 : Severe error
- Explanation
- The component was started without any parameters when at least the component key is required. The component stops.
- Response
- Use the customized started task procedure to start the component.
- BIP9107
- Registry not found.
- Severity
- 30 : Severe error
- Explanation
- The program tried to find the path to its registry. To find the registry the environment variable MQSI_REGISTRY is evaluated. This variable does not exist, is empty, or is too long. The program stops.
- Response
- Use the customized started task procedure to start the component. If you are using the generated started task procedure, check your customization for valid definitions.
- BIP9108
- Broker service value is <insert_0>.
- Severity
- 0 : Information
- Explanation
- The broker service value is shown. This value may be used by IBM support to assist in the diagnosis of problems.
- Response
- No action required. You may be asked to supply this value to IBM support during problem determination.
- BIP9120
- Registration of WebSphere Message Brokers service to OS/390 Automatic Restart Management failed.
- Severity
- 20 : Error
- Explanation
- Macro IXCARM returned an error while registering WebSphere Message Brokers service to OS/390 Automatic Restart Management.
- Response
- Check the product trace for the return codes from macro IXCARM and resolve the problems indicated. (See OS/390 MVS Sysplex Services Reference).
- BIP9121
- Indicate readiness for WebSphere Message Brokers service to OS/390 Automatic Restart Management failed.
- Severity
- 20 : Error
- Explanation
- Macro IXCARM returned an error while registering WebSphere Message Brokers service to OS/390 Automatic Restart Management.
- Response
- Check the trace for return codes from macro IXCARM and resolve the problems indicated. (See OS/390 MVS Sysplex Services Reference)
- BIP9122
- Deregister of WebSphere Message Brokers service from OS/390 Automatic Restart Management failed.
- Severity
- 20 : Error
- Explanation
- Macro IXCARM returned an error while deregistering WebSphere Message Brokers service from OS/390 Automatic Restart Management.
- Response
- Check the trace for the return codes from macro IXCARM and resolve the problems indicated. (See OS/390 MVS Sysplex Services Reference).
- BIP9131
- Unable to register as a resource manager with RRS: return code=<insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Execution Group was unable to register as a resource manager with RRS because the CRGGRM call failed with the indicated return code.
- Response
- Investigate why the resource manager registration service has failed. Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9132
- Unable to set RRS exit information: return code=<insert_0>
- Severity
- 30 : Severe error
- Explanation
- The Execution Group was unable to set its RRS exit information because the CRGSEIF call failed with the indicated return code.
- Response
- Investigate why the exit information service has failed. Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9133
- Unable to unregister as an RRS resource manager: return code=<insert_0>.
- Severity
- 10 : Warning
- Explanation
- The Execution Group was unable to unregister as an RRS resource manager because the CRGDRM call failed with the indicated return code.
- Response
- The Execution Group will be automatically unregistered when the broker has ended or RRS has been stopped. Investigate why the service has failed. Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9134
- Unable to begin an RRS context: return code=<insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Execution Group was unable to begin an RRS context because the CTXBEGC call failed with the indicated return code.
- Response
- Investigate why the begin context service has failed. Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9135
- Unable to switch RRS context: return code <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Execution Group was unable to switch to an RRS context because the CTXSWCH call failed with the indicated return code.
- Response
- Investigate why the switch context service has failed. Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9136
- Unable to end an RRS context: return code=<insert_0>.
- Severity
- 10 : Warning
- Explanation
- The Execution Group was unable to switch to an RRS context because the CTXSWCH call failed with the indicated return code.
- Response
- The context will be automatically ended when the task has ended or RRS has been stopped. Investigate why the service has failed. Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9137
- Successful registration with RRS as resource manager <insert_0>.
- Severity
- 0 : Information
- Explanation
- The Execution Group has successfully registered itself as a resource manager with RRS and its name, <insert_0> has been logged.
- Response
- No user action required.
- BIP9139
- Unable to set RRS environment: return code=<insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Execution Group was unable to set its RRS environment because the CRGGRM call failed with the indicated return code.
- Response
- Investigate why the call to the set environment service has failed. Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9140
- OS/390 Automatic Restart Management Interface returned an error to the WebSphere Message Brokers service while <insert_0>.
- Severity
- 20 : Error
- Explanation
- OS/390 Automatic Restart Management Interface returned an error.
- Response
- Check the trace for further information.
- BIP9141
- The component was started.
- Severity
- 0 : Information
- Explanation
- WebSphere Message Brokers component (Broker, Configuration Manager or UserNameServer) service was started.
- Response
- No user action required.
- BIP9142
- The component has stopped.
- Severity
- 0 : Information
- Explanation
- WebSphere Message Brokers component (Broker, Configuration Manager or UserNameServer) service has stopped.
- Response
- No user action required.
- BIP9143
- WebSphere Message Brokers service detected that <insert_0> is already running.
- Severity
- 10 : Warning
- Explanation
- The WebSphere Message Brokers service detected that an instance of <insert_0> is already running. No new instance was started.
- Response
- No user action required.
- BIP9144
- WebSphere Message Brokers stopped abnormally.
- Severity
- 30 : Severe error
- Explanation
- WebSphere Message Brokers service detected a nonrecoverable error which caused an abnormal stop.
- Response
- No user action required.
- BIP9145
- A Mandatory parameter for starting the component is missing.
- Severity
- 30 : Severe error
- Explanation
- A start parameter for the Control Process was not provided. The first parameter is mandatory. The component stops.
- Response
- Use the customized procedure to restart the component. If you have already used the customized procedure check the customization log for any errors and correct them.
- BIP9146
- Invalid length of a mandatory start parameter.
- Severity
- 30 : Severe error
- Explanation
- The component is started with an invalid component name or component key. The length of one of these parameters is not valid. The component stops.
- Response
- Check your customization and correct the required parameter.
- BIP9147
- Beta program expired.
- Severity
- 20 : Error
- Explanation
- The time for beta testing has expired. The component stops.
- Response
- Contact your IBM support center.
- BIP9160
- <insert_0> does not exist.
- Severity
- 20 : Error
- Explanation
- The named directory (ComponentDir) does not exist.
- Response
- Supply a valid directory name for the ComponentDir.
- BIP9161
- <insert_0> is an invalid brokername.
- Severity
- 20 : Error
- Explanation
- The name for a broker is invalid. The broker must contain up to 64 characters and must not contain special characters.
- Response
- Change the name for the broker.
- BIP9162
- <insert_0> already set, check the options and arguments.
- Severity
- 20 : Error
- BIP9163
- Wrong argument for option <insert_0> submitted.
- Severity
- 20 : Error
- Explanation
- Change the argument for option <insert_0>.
- BIP9164
- <insert_0> must be in range <insert_1>.
- Severity
- 20 : Error
- BIP9165
- Mandatory parameter <insert_0> is missing.
- Severity
- 20 : Error
- BIP9166
- <insert_0> invalid or missing parameter.
- Severity
- 20 : Error
- Explanation
- Either invalid parameters have been entered or parameters are missing.
- Response
- Rerun the command with the -h option to get help about the syntax.
- BIP9167
- Environment variable <insert_0> already exists in ENVFILE.
- Severity
- 20 : Error
- Explanation
- The subject environment variable from the Environment Variable Section in mqsicompcif cannot be processed.
Possible causes:
1. The environment variable is internally used by WBIMB for z/OS.
2. The environment variable has been specified multiple times in mqsicompcif.
It is not allowed to replace environment variables internally used by WBIMB for z/OS or to specify the same environment variable multiple times.
The customization process is terminated.
- Response
- Remove the named environment variable from the Environment Variable Section in mqsicompcif.
Run mqsicustomize again.
- BIP9168
- <insert_0> is not empty, a component already exists.
- Severity
- 10 : Warning
- Explanation
- The component you are about to create already exists. Delete the component if you want to reuse the ComponentDir or specify a new ComponentDir.
- Response
- Specify a valid ComponentDir.
- BIP9169
- Copy <insert_0>...
- Severity
- 0 : Information
- Explanation
- The named file is copied from the installation path to the component HFS.
- Response
- No user action required.
- BIP9170
- <insert_0> could not be found.
- Severity
- 20 : Error
- Explanation
- The named file could not be found in the installation path.
- Response
- Check whether mqsicreatebroker or mqsicreateusernameserver have been invoked from the correct WebSphere Message Brokers installation path.
- BIP9171
- Installation Path is : <insert_0>
Component Name is : <insert_1>
Component Path is : <insert_2>
Queue Manager Name is : <insert_3>
UNS Queue Manager Name is : <insert_4>
Configuration Timeout is : <insert_5>
Configuration Timeout Delay is : <insert_6>
Statistics Major Interval is : <insert_7>
Publish/Subscribe Access Control enabled : <insert_8>
Refresh component specified : <insert_9>
- Severity
- 0 : Information
- BIP9172
- Installation Path is : <insert_0>
Component Path is : <insert_1>
Queue Manager Name is : <insert_2>
Refresh Interval is : <insert_3>
Protocol Authorization source is : <insert_4>
Use authorization services library : <insert_5>
Refresh component specified : <insert_6>
- Severity
- 0 : Information
- BIP9173
- Component <insert_0> created successfully.
- Severity
- 0 : Information
- Explanation
- mqsicreatebroker or mqsicreateusernameserver ended successfully.
- Response
- No user action required.
- BIP9174
- Component <insert_0> not created.
- Severity
- 20 : Error
- Explanation
- mqsicreatebroker or mqsicreateusernameserver ended with an error. See previous messages for further explanation.
- Response
- Examine previous error messages to find out the required actions.
- BIP9177
- About to attempt creation of Component <insert_0>
- Severity
- 0 : Information
- BIP9178
- <insert_0> cannot be deleted.
- Severity
- 20 : Error
- Explanation
- The named directory (ComponentDir) cannot be deleted because: 1. The directory does not exist. 2. You are not authorized to delete the directory.
- Response
- Make sure the directory to be deleted exists and you have the authorization to delete it.
- BIP9179
- <insert_0> deleted successfully.
- Severity
- 0 : Information
- Explanation
- The named directory (ComponentDir) has been deleted.
- Response
- No user action required.
- BIP9180
- mqsicreatebroker command help.
- Severity
- 0 : Information
- Explanation
- Syntax: mqsicreatebroker brokername -c ComponentDir -q QueueManagerName [ -s UserNameServerQueueManagerName [ -j ] ] [ -g ConfigurationTimeout ] [ -k ConfigurationTimeoutDelay ] [ -v StatisticsMajorInterval ]
Command Options
-c path to the directory where the broker will be created.
-q the WebSphere MQ Queue Manager that the broker should use.
Optional
-s the WebSphere MQ Queue Manager of the UserNameServer.
-j (when present indicates that Publish/Subscribe access control is to be enabled.)
-g Configuration Timeout in seconds.
-k Configuration Delay Timeout in seconds.
-v Statistics Major Interval in minutes .
- BIP9182
- All parameters correct? (Y|y) or (N|n)?
- Severity
- 0 : Information
- BIP9185
- Directory <insert_0> does not exist.
- Severity
- 20 : Error
- Explanation
- The validation routine mqsichecksetup failed because the named directory does not exist.
- Response
- Check whether mqsicreatebroker or mqsicreateusernameserver has been executed from the correct installation directory. Check whether the CIF entries are valid for your installation. Correct the error and run the customization again.
- BIP9186
- File <insert_0> does not exist.
- Severity
- 20 : Error
- Explanation
- The validation routine mqsichecksetup failed because the named file does not exist.
- Response
- Check whether mqsicreatebroker or mqsicreateusernameserver has been executed from the correct installation directory. Correct the error and run the customization again.
- BIP9187
- Customization step is incomplete or failed with message <insert_0>.
- Severity
- 10 : Warning
- Explanation
- The validation routine mqsichecksetup failed because the log file indicates that some of the installation steps did not complete successfully.
- Response
- Check the log file <ComponentDir>/output/Customizelog for further information. Correct the error and run the customization again.
- BIP9188
- The contents of the registry do not correspond to the information in the CIF.
- Severity
- 20 : Error
- Explanation
- The contents of the registry are determined by some CIF keys. The current layout of the registry does not match the information in the CIF.
- Response
- Check <ComponentDir>/output/cvpslog for further messages. Correct the error and run the customization again.
- BIP9189
- The contents of the ENVFILE do not correspond to the information in the CIF.
- Severity
- 20 : Error
- Explanation
- The contents of the ENVFILE are determined by some CIF keys. The current layout of the ENVFILE does not match the information in the CIF.
- Response
- Check <ComponentDir>/output/cvpslog for further messages. Correct the error and run the customization again.
- BIP9190
- The contents of file dsnaoini do not correspond to the information in the CIF.
- Severity
- 20 : Error
- Explanation
- The contents of file dsnaoini are determined by some CIF keys. The current layout of the dsnaoini file does not match the information in the CIF.
- Response
- Check <ComponentDir>/output/cvpslog for further messages. Correct the error and run the customization again.
- BIP9191
- The required fixed settings in the dsnaoini file are invalid.
- Severity
- 20 : Error
- Explanation
- Some settings in the dsnaoini file are preset and must not be changed. These settings appear to be invalid.
- Response
- Check <ComponentDir>/output/cvpslog for further messages. Correct the error and run the customization again.
- BIP9192
- Name of Started Task <insert_0> is invalid.
- Severity
- 10 : Warning
- Explanation
- Started Task Name must not be longer than 7 characters and must not start with BIP.
- Response
- Specify a valid name.
- BIP9193
- Duplicate or missing tag <insert_0> in mqsicompcif.
- Severity
- 20 : Error
- Explanation
- The subject tag is either missing or duplicate in mqsicompcif.
Possible cause:
1. The mqsicompcif in the component directory is corrupted.
The customization process is terminated.
- Response
- Correct the error or get a fresh copy of mqsicompcif from installation_directory/template/data.
Run mqsicustomize again.
- BIP9194
- mqsicustomize command help.
- Severity
- 0 : Information
- Explanation
- Syntax: mqsicustomize [ -R der ]
Use mqsicustomize without an option to customize or recustomize the component.
Command Options
-R d Reset locks, log, files and errors directory.
-R e Reset ENVFILE and dsnaoini if component is a broker.
-R r Reset the registry.
The options can be combined, for example mqsicustomize -R der
- BIP9195
- WebSphere Message Brokers Customization Verification of HFS resources started.
- Severity
- 0 : Information
- Explanation
- The customization verification of HFS resources started successfully. The layout and contents of the <ComponentDir> directory tree structure are being verified.
- Response
- No user action required.
- BIP9196
- WebSphere Message Brokers Customization Verification Setup check ended with errors.
- Severity
- 20 : Error
- Explanation
- The validation routine mqsichecksetup failed because an error has been detected in the customization of the component.
- Response
- Check <ComponentDir>/output/cvpslog for further messages. Correct the error and run the customization again.
- BIP9197
- WebSphere Message Brokers Customization Verification Setup check ended with warnings.
- Severity
- 10 : Warning
- Explanation
- The validation routine mqsichecksetup ended with warnings. The customization of the component might be incomplete.
- Response
- Check <ComponentDir>/output/cvpslog for further messages, additional actions might be necessary.
- BIP9198
- WebSphere Message Brokers Customization Verification Setup check was successful.
- Severity
- 0 : Information
- Explanation
- The Customization Verification Program did not report any problems with the current customization.
- Response
- No user action required.
- BIP9199
- Successful command completion.
- Severity
- 0 : Information
- Explanation
- The command ended successfully.
- Response
- No user action required.
- BIP9201
- Update to Java version 1.3 or higher.
- Severity
- 20 : Error
- BIP9202
- Creating directory <insert_-1>/registry/<insert_0>.
- Severity
- 0 : Information
- Explanation
- The named directory is being created.
- Response
- No user action required.
- BIP9203
- Creating registry for component <insert_0>.
- Severity
- 0 : Information
- Explanation
- The registry and its keys will be created for the named component.
- Response
- No user action required.
- BIP9204
- Found begin tag <insert_0> after end tag <insert_1> in mqsicompcif.
- Severity
- 20 : Error
- Explanation
- The subject tags show up in the wrong sequence in mqsicompcif.
Possible cause:
1. mqsicompcif in the component directory is corrupted.
The customization process is terminated.
- Response
- Correct the error or get a fresh copy of mqsicompcif from installation_directory/template/data.
Run mqsicustomize again.
- BIP9205
- Processing <insert_0>.
- Severity
- 0 : Information
- Explanation
- This message shows the current processing step of mqsicustomize.
- BIP9206
- Length of at least one entry in <insert_0> exceeds <insert_1> characters.
- Severity
- 20 : Error
- Explanation
- Possible cause:
1. mqsicompcif in the component directory is corrupted.
The customization process is terminated.
- Response
- Correct the error or get a fresh copy of mqsicompcif from installation_directory/template/data.
Run mqsicustomize again.
- BIP9207
- <insert_0> in mqsicompcif is empty.
- Severity
- 20 : Error
- Explanation
- No entries were found in the subject section. This section must contain at least one entry.
Possible cause:
1. mqsicompcif in the component directory is corrupted.
The customization process is terminated.
- Response
- Correct the error or get a fresh copy of mqsicompcif from installation_directory/template/data.
Run mqsicustomize again.
- BIP9208
- //BIPXXXXX JOB not found in first line of Job Card Section.
- Severity
- 20 : Error
- Explanation
- The first entry in the Job Card Section must contain //BIPXXXXX JOB at the beginning.
Possible cause:
1. mqsicompcif in the component directory is corrupted.
The customization process is terminated.
- Response
- Correct the error or get a fresh copy of mqsicompcif from installation_directory/template/data.
Run mqsicustomize again.
- BIP9209
- Registry for component <insert_0> created successfully.
- Severity
- 0 : Information
- Explanation
- The registry and its keys have been created for the named component.
- Response
- No user action required.
- BIP9210
- Creating DB2/MQ job for test systems.
- Severity
- 0 : Information
- Explanation
- The job for setting up DB2 and MQ for test systems is being created.
- Response
- No user action required.
- BIP9211
- Component Anchor directory <insert_-1> deleted.
- Severity
- 0 : Information
- Explanation
- The named directory has been deleted by a customization step.
- Response
- No user action required.
- BIP9213
- There are no files to copy, please execute mqsicustomize first.
- Severity
- 0 : Information
- Explanation
- The files to be copied by this step do not exist. This indicates that the mqsicustomize step has been omitted.
- Response
- Execute mqsicustomize, then run this step again.
- BIP9216
- <insert_0> could not be found.
- Severity
- 20 : Error
- Explanation
- The named file could not be found in the <INSTPATH>/template/cntl directory.
- Response
- Check if the correct file name has been specified.
- BIP9217
- mqsicustomize for component <insert_0> ended successfully.
- Severity
- 0 : Information
- Explanation
- Customization for a broker or UserNameServer completed successfully.
- Response
- No user action required.
- BIP9218
- <insert_-1> job exists. Copy process stopped.
- Severity
- 0 : Information
- Explanation
- The named job already exists. It will not be replaced.
- Response
- Delete the already existing job.
- BIP9219
- mqsicustomize for component <insert_0> ended unsuccessfully.
- Severity
- 30 : Severe error
- Explanation
- Customization for a broker or UserNameServer completed unsuccessfully.
- Response
- Check customization log for further information.
- BIP9220
- An error occurred while retrieving time zone information.
- Severity
- 30 : Severe error
- Explanation
- The broker was unable to retrieve the current time zone.
- Response
- Check that the 'TZ' CIF key has been set correctly for your time zone and rerun the customization for this broker.
- BIP9240
- An internal error occurred starting a DataFlowEngine address space, returncode <insert_0>, reasoncode <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred processing a shared memory segment whilst starting a DataFlowEngine address space. <insert_0> and <insert_1> are returned from a shared memory segment function call.
- Response
- Investigate the return and reason code as to the cause of the problem. See z/OS UNIX System Services Programming Assembler Callable Services Reference and z/OS UNIX System Services Messages and Codes. In some cases, errors can occur because the shared memory segment system values IPCSHMNIDS, IPCSHMSPAGES, IPCSHMMPAGES, IPCSHMNSEGS and MAXSHAREPAGES are incorrectly set. The command DISPLAY OMVS,L displays these system values, and they can be changed dynamically using SETOMVS. See z/OS UNIX System Services Planning for further information. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9241
- An internal error occurred with a DataFlowEngine address space, returncode <insert_0>, reasoncode <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred processing a semaphore whilst starting or stopping a DataFlowEngine address space. <insert_0> and <insert_1> are returned from a semaphore function call.
- Response
- Investigate the return and reason code as to the cause of the problem. See z/OS UNIX System Services Programming Assembler Callable Services Reference and z/OS UNIX System Services Messages and Codes. In some cases, errors can occur because the semaphore system values IPCSEMNIDS, IPCSEMNOPS and IPCSEMNSEMS are incorrectly set. The command DISPLAY OMVS,L displays these system values, and they can be changed dynamically using SETOMVS. See z/OS UNIX System Services Planning for further information. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9242
- An internal error occurred whilst creating a DataFlowEngine address space, returncode <insert_0>, reasoncode <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred whilst creating a DataFlowEngine address space. <insert_0> and <insert_1> are returned from the ASCRE MVS macro call.
- Response
- Investigate the return and reason code as to the cause of the problem. See z/OS MVS Programming Authorized Assembler Services Reference , Volume 1. Check the broker's started task JCL for correctness, as this JCL is also required to start DataFlowEngine address spaces. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9243
- An internal error occurred whilst starting a DataFlowEngine address space, length of execution group label is <insert_0>, maximum is <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred whilst starting a DataFlowEngine address space. The length of an execution group label is limited to <insert_1> when passed to the DataFlowEngine address space. The length of the execution group label is <insert_0>.
- Response
- Reduce the length of the execution group label to less than <insert_1> and redeploy. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9244
- An internal error occurred whilst spawning process DataFlowEngine or bipservice, returncode <insert_0>, reasoncode <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred whilst spawning an internal executable program. <insert_0> and <insert_1> were returned from the BPX1SPN USS macro call.
- Response
- Investigate the return and reason code as to the cause of the problem. See z/OS USS Programming Assembler Callable Services Reference. Check the broker's started task JCL for correctness, as this JCL determines the path for the programs to be spawned. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9245
- Process DataFlowEngine or bipservice returned: returncode <insert_0>.
- Severity
- 0 : Information
- Explanation
- The internal process has ended, returning the value <insert_0>.
- Response
- If the return code is 0 the process has ended normally. Any other return code may indicate a POSIX signal, or a 'fail' return. Contact your IBM support center if there is an undetermined problem.
- BIP9246
- An internal error occurred whilst waiting on process DataFlowEngine or bipservice, returncode <insert_0>, reasoncode <insert_1>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred whilst waiting for an internal process. <insert_0> and <insert_1> were returned from the BPX1WAT USS macro call.
- Response
- Investigate the return and reason code as to the cause of the problem: see z/OS USS Programming Assembler Callable Services Reference. Check the broker's started task JCL for correctness. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9250
- SMF is not collecting record type 117, subtype <insert_0>.
- Severity
- 0 : Information
- Explanation
- WBIMB attempted to write a statistics record type 117, subtype <insert_0> to SMF. However, SMF is not collecting this record type/subtype.
- Response
- Change SMF to start collecting WBIMB statistics record type 117, subtype <insert_0>. A restart of WBIMB is not necessary.
- BIP9251
- An error occurred writing record type 117, subtype <insert_0> to SMF, errorcode <insert_1>, reasoncode <insert_2>.
- Severity
- 20 : Error
- Explanation
- An error occurred writing a WBIMB statistics record type 117, subtype <insert_0> to SMF.
- Response
- Investigate the error and reason code as to the cause of the problem. See z/OS C/C++ Run-Time Library Reference for possible errors from the _smf_record() function. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9252
- An Internal warning occurred while Registering for Event Notification, Return Code <insert_0> Reason Code <insert_1>
- Severity
- 10 : Warning
- Explanation
- Event Notification reason codes 4 Unable to obtain storage from CSA. 8 Unable to load the ENF exit into the system. 12 Failed to Register with ENF. 16 Unable to find Global anchor block when Registering for ENF.
- Response
- Investigate the reason code as to the cause of the problem. 4 Check there is storage available. 8 Check the Dataset containing the exit BIPS7ENF can be found.
- BIP9253
- An Internal warning occurred while DeRegistering for Event Notification, Return Code <insert_0> Reason Code <insert_1>
- Severity
- 10 : Warning
- Explanation
- Event Notification reason codes 4 Failed to De-Register from ENF. 8 Unable to release anchor block. 12 Failed to remove ENF exit.
- Response
- Investigate the reason code as to the cause of the problem.
- BIP9260
- Memory allocation failed in component <insert_0>.
- Severity
- 10 : Warning
- Explanation
- Memory allocation error. The requested memory could not be provided. The component stops.
- Response
- No user action required.
- BIP9270
- Address space of execution group <insert_0> (UUID <insert_1>) has been set to non-swappable.
- Severity
- 0 : Information
- Explanation
- A request to run the above execution group in a non-swappable address space, as per broker configuration, has suceeded.
- Response
- No user action required.
- BIP9271
- Address space of execution group <insert_0> (UUID <insert_1>) has not been set to non-swappable. Errno: <insert_2> Call: <insert_3>, <insert_4>
- Severity
- 10 : Warning
- Explanation
- A request to run the above execution group in a non-swappable address space, as per broker configuration, has failed.
- Response
- See the above errno for possible cause. Your broker started task ID may need access to the BPX.STOR.SWAP class facility.
- BIP9281
- Failure retrieving the internal RRS Resource Manager Name: return code=<insert_0>.
- Severity
- 30 : Severe error
- Explanation
- This is an internal error.
- Response
- Contact your IBM support center.
- BIP9282
- Unable to retrieve the current RRS context token: return code=<insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The Execution Group was unable to retrieve the current RRS context token because the CTXRCC call failed with the indicated return code.
- Response
- Investigate why the call to the retrieve current context service has failed. Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9283
- Unable to set context with MQ on queue manager <insert_0>: MQCC=<insert_1>; MQRC=<insert_2>.
- Severity
- 30 : Severe error
- Explanation
- The Execution Group was unable to set its context with MQ for the connection to queue manager <insert_0>.
- Response
- Use the system log messages together with your resource recovery documentation to determine the source of the problem. Correct the problem and restart the broker. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9801
- No supported database product found.
- Severity
- 0 : Information
- Explanation
- The requested database was not created becuase a support database product could not be found.
- Response
- Please check your database product installion.
- BIP9802
- A database of name <insert_0> already exist.
- Severity
- 10 : Warning
- Explanation
- No action taken.
- Response
- Use a unique name for the database you are creating.
- BIP9803
- The requested database engine <insert_0> could not be found.
- Severity
- 10 : Warning
- Explanation
- The database engine specified can not be used.
- Response
- Please specified a different database engine.
- BIP9804
- No database of name <insert_0> found, no action taken.
- Severity
- 10 : Warning
- Explanation
- The database name specified could not be found. The requested command action was aborted.
- Response
- Please check the database name supplied.
- BIP9805
- A Cloudscape Network Server is already running on port number <insert_0>
- Severity
- 10 : Warning
- Explanation
- The Cloudscape Network Server can only accept database connections on a single TCP/IP Port.
- Response
- Please use the existing Cloudscape Network Server running on port number <insert_0>. Or delete all the existing Derby databases, then re-run this command to create a new Cloudscape Network Server running on the port number <insert_1>.
- BIP9806
- The IBM Cloudscape Network Server on Port number <insert_0>, has started.
- Severity
- 0 : Information
- BIP9807
- The IBM Cloudscape Network Server on Port number <insert_0>, has been shutdown.
- Severity
- 0 : Information
- BIP9808
- The <insert_0> database files could not be deleted.
- Severity
- 10 : Warning
- Explanation
- The folder and the files created by the Apache Deraby database, could not be removed.
- Response
- Once the DatabaseInstanceMgr has been stopped, the folder and files for the <insert_0> database can be manually removed from: <insert_1>
- BIP9809
- Creating <insert_1> Database <insert_0>, this may take a while.
- Severity
- 0 : Information
- BIP9810
- The DatabaseInstanceMgr service could not be found.
- Severity
- 20 : Error
- Explanation
- The Windows service with the name <insert_0> could not be <insert_1>
- Response
- Please check the event log for any addition error messages.
- BIP9811
- The DatabaseInstanceMgr service already exists.
- Severity
- 10 : Warning
- Explanation
- The Windows service with the name <insert_0> already exists.
- BIP9812
- The IBM Cloudscape Network Server failed to start
- Severity
- 20 : Error
- Explanation
- The CNS running on port number <insert_0> could not be started.
- Response
- Please check that no other program is using the port number <insert_0>. Also check that the user id associated with the DatabaseInstanceMgr service has the correct permissions.
- BIP9813
- The DatabaseInstanceMgr timed out when running an external command.
- Severity
- 20 : Error
- Explanation
- The DatabaseInstanceMgr executed an external command to modify a database system. This was unsuccessful due to the command taking too long to finish.
- Response
- Check that the database system which the command is trying to invoke is working correctly.
- BIP9814
- <insert_0> - <insert_1> - <insert_2>
- Severity
- 0 : Information
- BIP9815
- The supplied database name <insert_0> is too many characters in length.
- Severity
- 10 : Warning
- Explanation
- The maximum length of a database name is <insert_1> characters. The supplied name is <insert_2> characters long.
- Response
- Re-issue this command with a database name which is less then or equal to <insert_1> character long.
- BIP9816
- Multiple Database types detected, defaulting to <insert_0>.
- Severity
- 0 : Information
- BIP9817
- The DB2 database engine was used to create the <insert_0> database.
- Severity
- 0 : Information
- BIP9818
- IBM Cloudscape/Apache Derby was used to create the <insert_0> database.
- Severity
- 0 : Information
- BIP9819
- Creates a database for use with a Broker
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsicreatedb databaseName [-i serviceUserID] [-a servicePassword] [-w workpath] [-p portNumber] [-e dbType] [-u dbUserID]]
- Response
- Command Options:
'databaseName' is the name of the database to be created
Optional:
'-i serviceUserID' the userid that the DatabaseInstanceMgr should run under.
'-a servicePassword' the password for the DatabaseInstanceMgr userid.
'-p portNumber' the port number the DatabaseInstanceMgr should use (default=1527)
'-e dbType' the Database type to use, currently supported: 'DB2' or 'Derby'
'-u dbUserID' (DB2 only) grant database access to this userID.
- BIP9820
- Deletes a database created by mqsicreatedb.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsideletedb [databaseName] [-d DeleteAllDatabases]
- Response
- Command Options:
'databaseName' is the name of the database to be deleted
'-d DeleteAllDatabases' will delete ALL the existing databases that were created with mqsicreatedb
- BIP9821
- Changes a Database Instance Manager's configuration.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsichangedbimgr -a ServicePassword < -i ServiceUserId >
- Response
- Command Options:
'i' the userid that the Database Instance Manager should run under.
'a' the password for the Database Instance Manager userid.
- BIP9822
- This msg is not in use.
- Severity
- 0 : Information
- Explanation
- A longer explanation of the basic message text And do not forget to update the severity field on line 3 above. Valid values are 0=info, 10=warn, 20=recoverableError, 30=unrecoverableError
- Response
- Document here what the user should do when the message is received
- BIP9823
- Rolling back creating Database <insert_0>.
- Severity
- 0 : Information
- BIP9824
- Creating the DatabaseInstanceMgr Service Component.
- Severity
- 0 : Information
- BIP9825
- Creating the ODBC Data Source name <insert_0>.
- Severity
- 0 : Information
- BIP9826
- Removing the DatabaseInstanceMgr Service Component.
- Severity
- 0 : Information
- BIP9827
- Removing the ODBC Data Source name <insert_0>.
- Severity
- 0 : Information
- BIP9828
- Connecting to the Cloudscape Network Server on port <insert_0>.
- Severity
- 0 : Information
- BIP9829
- Cataloging the <insert_1> Database <insert_0>.
- Severity
- 0 : Information
- BIP9830
- Deleting the <insert_1> Database <insert_0>.
- Severity
- 0 : Information
- BIP9831
- Uncataloging the Cloudscape Network Server.
- Severity
- 0 : Information
- BIP9832
- Starting the DatabaseInstanceMgr Service Component.
- Severity
- 0 : Information
- BIP9833
- Stopping the DatabaseInstanceMgr Service Component.
- Severity
- 0 : Information
- BIP9834
- Can not create the DatabaseInstanceMgr service, a serviceUserID is required.
- Severity
- 10 : Warning
- Explanation
- The DatabaseInstanceMgr service could not be created because a serviceUserID was not provided. The requested command action was aborted.
- Response
- Please supply a valid serviceUserID and servicePassword, via the -i and -a parameters.
- BIP9835
- The DB2 batch command failed with the error code SQLSTATE=<insert_1>.
- Severity
- 20 : Error
- Explanation
- The database <insert_0> could not be created/deleted. The error code SQLSTATE=<insert_1> was returned from the DB2 batch command. All preceding steps have been rolled back.
- Response
- Fix the problem indicated by the SQLSTATE code and reissue the command.
- BIP9836
- The DB2 batch command has failed when creating the database <insert_0>.
- Severity
- 30 : Severe error
- Explanation
- The output file from the DB2 batch command does not exist. All preceding steps have been rolled back.
- Response
- Please check that DB2/DB2 RunTime Client has been installed correctly.
- BIP9837
- Shutting down the <insert_1> Database <insert_0>.
- Severity
- 0 : Information
- BIP9838
- Granting access to the <insert_1> Database <insert_0> for userid <insert_2>.
- Severity
- 0 : Information
- BIP9839
- Failed to grant access to the <insert_1> Database <insert_0> for userid <insert_2>.
- Severity
- 10 : Warning
- BIP9840
- The DatabaseInstanceMgr failed to execute an external command.
- Severity
- 20 : Error
- Explanation
- The DatabaseInstanceMgr executed an external command to modify a database system. This was unsuccessful due to an unknown error in the database system being used.
- Response
- Check that the database system which the command is trying to invoke is working correctly.