BIP9000-9999: Runtime components - z/OS
- BIP9001
- Memory allocation error in <insert_1> heap for element <insert_2>.
- Severity
- 30 : Severe error
- Explanation
- An error occurred during the allocation of memory out of heap <insert_1>. The memory was being allocated for element <insert_2>.
- 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_1>. rc= <insert_2>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_1>x, reasoncode= <insert_2>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.
- BIP9015
- The RRS EXIT_FAILED routine has been called: <insert_1>,<insert_2>,<insert_3>,<insert_4>,<insert_5>.
- Severity
- 20 : Error
- Explanation
- Resource Recovery Services (RRS) has called the EXIT_FAILED routine in BIPIMAIN.
- Response
- RRS will unset the exits registered by the Integration Server, and the Integration Server will shut down and restart. If the problem persists, contact your IBM support center.
- BIP9101
- Invalid start mode <insert_1>.
- Severity
- 10 : Warning
- Explanation
- The Control Process has been started with a start mode of <insert_1>. If defined, the start mode must be either AUTO or MAN. The parameter <insert_1> 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
- 40 : Stop 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
- 40 : Stop 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
- 40 : Stop 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
- 40 : Stop 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
- 40 : Stop 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
- 40 : Stop 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
- Integration node service value is <insert_1>.
- Severity
- 0 : Information
- Explanation
- The integration node 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 IBM Integration Bus service to OS/390 Automatic Restart Management failed.
- Severity
- 20 : Error
- Explanation
- Macro IXCARM returned an error while registering IBM Integration Bus 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 IBM Integration Bus service to OS/390 Automatic Restart Management failed.
- Severity
- 20 : Error
- Explanation
- Macro IXCARM returned an error while registering IBM Integration Bus 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 IBM Integration Bus service from OS/390 Automatic Restart Management failed.
- Severity
- 20 : Error
- Explanation
- Macro IXCARM returned an error while deregistering IBM Integration Bus 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_1>.
- Severity
- 30 : Severe error
- Explanation
- The integration server 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 integration node. 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_1>1
- Severity
- 30 : Severe error
- Explanation
- The integration server 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 integration node. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9133
- Unable to deregister as an RRS resource manager: return code=<insert_1>.
- Severity
- 10 : Warning
- Explanation
- The integration server was unable to deregister as an RRS resource manager because the CRGDRM call failed with the indicated return code.
- Response
- The integration server is automatically deregistered when the integration node has ended, or when 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 integration node. 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_1>.
- Severity
- 30 : Severe error
- Explanation
- The integration server 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 integration node. 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_1>.
- Severity
- 30 : Severe error
- Explanation
- The integration server 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 integration node. 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_1>.
- Severity
- 10 : Warning
- Explanation
- The integration server 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 integration node. 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_1>.
- Severity
- 0 : Information
- Explanation
- The integration server has successfully registered itself as a resource manager with RRS and its name, <insert_1> has been logged.
- Response
- No user action required.
- BIP9139
- Unable to set RRS environment: return code=<insert_1>.
- Severity
- 30 : Severe error
- Explanation
- The integration server 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 integration node. 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 IBM Integration Bus service while <insert_1>.
- Severity
- 20 : Error
- Explanation
- OS/390 Automatic Restart Management Interface returned an error.
- Response
- Check the trace for further information.
- BIP9141
- The integration node has started.
- Severity
- 0 : Information
- Response
- No user action required.
- BIP9142
- The integration node has stopped.
- Severity
- 0 : Information
- Response
- No user action required.
- BIP9143
- IBM Integration Bus service detected that <insert_1> is already running.
- Severity
- 10 : Warning
- Explanation
- The IBM Integration Bus service detected that an instance of <insert_1> is already running. No new instance was started.
- Response
- No user action required.
- BIP9147
- Beta program expired.
- Severity
- 20 : Error
- Explanation
- The time for beta testing has expired. The component stops.
- Response
- Contact your IBM support center.
- BIP9148
- The MQTT broker process could not be started. integration node name <insert_1>;
- Severity
- 20 : Error
- Explanation
- The integration node was unable to start an MQTT broker process.
- Response
- Ensure that the executable is available and that the integration node's service userid has permission to run the executable.
- BIP9149
- The integration node has detected that the MQTT broker (process ID <insert_1>), has shut down abnormally.
- Severity
- 20 : Error
- Explanation
- An MQTT broker process ended abnormally.
- Response
- Investigate the reasons for the problem.
- BIP9150
- Internal error in the Admin Agent: <insert_1>
- Severity
- 30 : Severe error
- Explanation
- An error has occurred during MQTT broker startup or shutdown.
- Response
- See other error messages for information on how this error happened.
- BIP9151
- The specified MQTT port is already in use: <insert_1>
- Severity
- 30 : Severe error
- Explanation
- An error has occurred during MQTT broker startup and the specified port is already in use by another application.
- Response
- Check which process is using the port. Either reconfigure the integration node MQTT port number to a different value, end the process which is currently using the port, or wait until the port becomes available.
- BIP9152
- Unable to connect to the MQTT broker owned by node: <insert_1>
- Severity
- 30 : Severe error
- Explanation
- An attempt was made to connect to the MQTT broker owned by node <insert_1>, but failed. Event publications that use this server might fail.
- Response
- Examine previous error messages for details about the cause of this problem.
- BIP9153
- The MQTT pub/sub broker has started successfully, configured to listen on port <insert_1>.
- Severity
- 0 : Information
- Explanation
- The MQTT pub/sub broker process has started, configured to listen on the integration node-specific TCPIP port. Additional messages might indicate if the port is already in use.
- Response
- No user action required.
- BIP9154
- The HTTP listener could not be started because it requires a queue manager to be specified on the integration node.
- Severity
- 20 : Error
- Explanation
- The stand-alone HTTP listener uses WebSphere MQ to communicate between the listener process and the server that runs a message flow that uses HTTP. The HTTP listener requires the queue manager that is specified on the integration node, and without it, the listener cannot run. Any message flow that requires the HTTP listener will fail to deploy, and any message flow that is already deployed will fail to start.
- Response
- Specify a queue manager on the integration node, or force the use of the server-embedded listener by using the command: mqsichangeproperties <integration node name> -b httplistener -o HTTPListener -n startListener -v false
- BIP9155
- The MQTT pub/sub broker, configured to listen on port <insert_1>, has stopped.
- Severity
- 0 : Information
- Explanation
- The MQTT pub/sub broker process has stopped.
- Response
- No user action is required.
- BIP9160
- <insert_1> 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_1> is an invalid integration node name.
- Severity
- 20 : Error
- Explanation
- The name for an integration node is invalid. The integration node must contain up to 64 characters and must not contain special characters.
- Response
- Change the name for the integration node.
- BIP9162
- <insert_1> already set, check the options and arguments.
- Severity
- 20 : Error
- BIP9163
- Wrong argument for option <insert_1> submitted.
- Severity
- 20 : Error
- Explanation
- Change the argument for option <insert_1>.
- BIP9164
- <insert_1> must be in range <insert_2>.
- Severity
- 20 : Error
- BIP9165
- Mandatory parameter <insert_1> is missing.
- Severity
- 20 : Error
- BIP9166
- <insert_1> 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_1> 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 IIB 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 IIB 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_1> 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_1>...
- Severity
- 0 : Information
- Explanation
- The named file is copied from the installation path to the component HFS.
- Response
- No user action required.
- BIP9170
- <insert_1> 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 IBM Integration Bus installation path.
- BIP9171
- Installation Path is : <insert_1>1
Component Name is : <insert_2>2
Component Path is : <insert_3>3
Queue Manager Name is : <insert_4>4
UNS Queue Manager Name is : <insert_5>5
Configuration Timeout is : <insert_6>6
Configuration Timeout Delay is : <insert_7>7
Statistics Major Interval is : <insert_8>8
Publish/Subscribe Access Control enabled : <insert_9>9
Refresh component specified : <insert_10>0
- Severity
- 0 : Information
- BIP9172
- Installation Path is : <insert_1>1
Component Path is : <insert_2>2
Queue Manager Name is : <insert_3>3
Refresh Interval is : <insert_4>4
Protocol Authorization source is : <insert_5>5
Use authorization services library : <insert_6>6
Refresh component specified : <insert_7>7
- Severity
- 0 : Information
- BIP9173
- Component <insert_1> created successfully.
- Severity
- 0 : Information
- Explanation
- mqsicreatebroker. or mqsicreateusernameserver. ended successfully.
- Response
- No user action required.
- BIP9174
- Component <insert_1> 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_1>1
- Severity
- 0 : Information
- BIP9178
- <insert_1> 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_1> 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. integrationNodeName -c ComponentDir [-q QueueManagerName] [ -s UserNameServerQueueManagerName [ -j ] ] [ -g ConfigurationTimeout ] [ -k ConfigurationTimeoutDelay ] [ -v StatisticsMajorInterval ]
Command Options
-c path to the directory where the integration node will be created.
Optional
-q queueManagerName the default WebSphere MQ queue manager that is used by the integration node. If -q is not specified, there is no default WebSphere MQ queue manager associated with the integration node.
-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_1> 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_1> 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_1>.
- 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_1> 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_1> 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 the mqsicustomize command, without options, to customize the component.
The following command options are available:
-R d to reset locks, log, files and errors directory.
-R e to reset ENVFILE and dsnaoini if the component is an integration node.
-R r to reset the registry.
These options can be combined, for example mqsicustomize -R der.
- BIP9195
- IBM Integration Bus 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
- IBM Integration Bus 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
- IBM Integration Bus 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
- IBM Integration Bus 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_0>/registry/<insert_1>.
- Severity
- 0 : Information
- Explanation
- The named directory is being created.
- Response
- No user action required.
- BIP9203
- Creating registry for component <insert_1>.
- 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_1> after end tag <insert_2> 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_1>.
- Severity
- 0 : Information
- Explanation
- This message shows the current processing step of mqsicustomize.
- BIP9206
- Length of at least one entry in <insert_1> exceeds <insert_2> 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_1> 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_1> 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_0> 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_1> 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_1> ended successfully.
- Severity
- 0 : Information
- Explanation
- Customization for an integration node or UserNameServer completed successfully.
- Response
- No user action required.
- BIP9218
- <insert_0> 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_1> ended unsuccessfully.
- Severity
- 30 : Severe error
- Explanation
- Customization for an integration node 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 integration node 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 integration node.
- BIP9240
- An internal error occurred starting a DataFlowEngine address space, returncode <insert_1>, reasoncode <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred processing a shared memory segment whilst starting a DataFlowEngine address space. <insert_1> and <insert_2> 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_1>, reasoncode <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred processing a semaphore whilst starting or stopping a DataFlowEngine address space. <insert_1> and <insert_2> 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_1>, reasoncode <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred whilst creating a DataFlowEngine address space. <insert_1> and <insert_2> 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 integration node'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 integration server label is <insert_1>, maximum is <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred whilst starting a DataFlowEngine address space. The length of an integration server label is limited to <insert_2> when passed to the DataFlowEngine address space. The length of the integration server label is <insert_1>.
- Response
- Reduce the length of the integration server label to less than <insert_2> 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_1>, reasoncode <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred whilst spawning an internal executable program. <insert_1> and <insert_2> 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 integration node'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_1>.
- Severity
- 0 : Information
- Explanation
- The internal process has ended, returning the value <insert_1>.
- 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_1>, reasoncode <insert_2>.
- Severity
- 20 : Error
- Explanation
- An internal error occurred whilst waiting for an internal process. <insert_1> and <insert_2> 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 integration node'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_1>.
- Severity
- 0 : Information
- Explanation
- IIB attempted to write a statistics record type 117, subtype <insert_1> to SMF. However, SMF is not collecting this record type/subtype.
- Response
- Change SMF to start collecting IIB statistics record type 117, subtype <insert_1>. A restart of IIB is not necessary.
- BIP9251
- An error occurred writing record type 117, subtype <insert_1> to SMF, errorcode <insert_2>, reasoncode <insert_3>.
- Severity
- 20 : Error
- Explanation
- An error occurred writing a IIB statistics record type 117, subtype <insert_1> 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_1> Reason Code <insert_2>2
- 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 was issued during deregistration from event notification (ENF), return code <insert_1> reason code <insert_2>.
- Severity
- 10 : Warning
- Explanation
- Event notification reason codes:
4 Failed to deregister from ENF.
8 Unable to release the anchor block.
12 Failed to remove the ENF exit.
- Response
- Investigate the reason code to determine the cause of the problem.
- BIP9254
- An Internal warning occurred while Posting for Event Notification, Return Code <insert_1> Reason Code <insert_2>2
- 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 to resolve the problem. 4 Check that there is storage available. 8 Check that the SBIPAUTH Dataset containing the BIPS7ENF exit exists.
- BIP9260
- Memory allocation failed in component <insert_1>.
- Severity
- 10 : Warning
- Explanation
- Memory allocation error. The requested memory could not be provided. The component stops.
- Response
- No user action required.
- BIP9261
- Integration server procedure <insert_1> specified in <insert_2> is greater than 8 characters
- Severity
- 10 : Warning
- Explanation
- The procedure <insert_1> specified in the <insert_2> environment variable exceeds the maximum 8 characters. The procedure name override is ignored.
- BIP9270
- The address space of integration server <insert_1>, which has a UUID of <insert_2>, has been set to be non-swappable.
- Severity
- 0 : Information
- Explanation
- A request to run the above integration server in a non-swappable address space has succeeded.
- Response
- No user action required.
- BIP9271
- Address space of integration server <insert_1> (UUID <insert_2>) has not been set to non-swappable. Errno: <insert_3> Call: <insert_4>, <insert_5>5
- Severity
- 10 : Warning
- Explanation
- A request to run the above integration server in a non-swappable address space, as per integration node configuration, has failed.
- Response
- See the above errno for possible cause. Your integration node started task ID may need access to the BPX.STOR.SWAP class facility.
- BIP9272
- The DataFlowEngine process has registered SMF 89 subtype 1 record collection. Return code <insert_1>,
- Severity
- 0 : Information
- Explanation
- The DataFlowEngine process made a request to the IFAUSAGE macro to register SMF 89 subtype 1 record collection. The IFAUSAGE macro returned <insert_1>.
- Response
- If the return code from IFAUSAGE is 0 then the DataFlowEngine process successfully registered SMF 89 subtype 1 record collection. Any other return code is described in the MVS System Management Facilities manual. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9273
- The DataFlowEngine process has deregistered SMF 89 subtype 1 record collection. Return code <insert_1>,
- Severity
- 0 : Information
- Explanation
- The DataFlowEngine process made a request to the IFAUSAGE macro to deregister SMF 89 subtype 1 record collection. The IFAUSAGE macro returned <insert_1>.
- Response
- If the return code from IFAUSAGE is 0 then the DataFlowEngine process successfully deregistered SMF 89 subtype 1 record collection. Any other return code is described in the MVS System Management Facilities manual. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9275
- Application <insert_1> on integration server <insert_2> is running. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> UUID <insert_8> Start mode: <insert_9> Java isolation: <insert_10> Long description: <insert_6> Keywords: <insert_7>7
- Severity
- 0 : Information
- BIP9276
- Application <insert_1> on integration server <insert_2> is stopped. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> UUID <insert_8> Start mode: <insert_9> Java isolation: <insert_10> Long description: <insert_6> Keywords: <insert_7>7
- Severity
- 0 : Information
- BIP9277
- Message flow <insert_1> on integration server <insert_2> is running. Application <insert_10>. Library <insert_11>. Additional thread instances: <insert_3> Deployed: <insert_4> in Bar file <insert_5> Last edited: <insert_6> UUID: <insert_12> Start mode: <insert_13> Long description: <insert_9> User-defined property names: <insert_7> Keywords: <insert_8>
- Severity
- 0 : Information
- BIP9278
- Message flow <insert_1> on integration server <insert_2> is stopped. Application <insert_10>. Library <insert_11>. Additional thread instances: <insert_3> Deployed: <insert_4> in Bar file <insert_5> Last edited: <insert_6> UUID: <insert_12> Start mode: <insert_13> Long description: <insert_9> User-defined property names: <insert_7> Keywords: <insert_8>
- Severity
- 0 : Information
- BIP9279
- Starting integration server <insert_1> using procedure <insert_2>
- Severity
- 0 : Information
- Explanation
- The procedure <insert_2> specified in either MQSI_STARTEDTASK_FIXED_<integrationServerName>, MQSI_STARTEDTASK_MULTI_<integrationServerName> or MQSI_STARTEDTASK_DEFAULT environment variables will be used to start the integration server <insert_1>.
- BIP9280
- Integration server procedure <insert_1> ignored as it does not match the first 4 characters of <insert_2>
- Severity
- 10 : Warning
- Explanation
- Integration server procedure <insert_1> specified in either MQSI_STARTEDTASK_FIXED_<integrationServerName>, MQSI_STARTEDTASK_MULTI_<integrationServerName> or MQSI_STARTEDTASK_DEFAULT environment variables must match the first 4 characters of the integration node procedure <insert_2>.
- BIP9281
- Failure retrieving the internal RRS Resource Manager Name: return code=<insert_1>.
- 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_1>.
- Severity
- 30 : Severe error
- Explanation
- The integration server 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 integration node. 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_1>: MQCC=<insert_2>; MQRC=<insert_3>.
- Severity
- 30 : Severe error
- Explanation
- The integration server was unable to set its context with MQ for the connection to queue manager <insert_1>.
- 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 integration node. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9284
- Integration node <insert_1> on queue manager <insert_2> is running. Integration node version: <insert_3> (build <insert_4>) Platform: <insert_5>, <insert_6>, <insert_7> Process ID: <insert_8> Administration URI: <insert_11> Short description: <insert_9> Long description: <insert_10>
- Severity
- 0 : Information
- BIP9285
- Integration node <insert_1> is running. Version: <insert_3> (build <insert_4>) Platform: <insert_5>, <insert_6>, <insert_7> Process ID: <insert_8> Short description: <insert_9> Long description: <insert_10>
- Severity
- 0 : Information
- BIP9286
- Integration server <insert_2> on integration node <insert_1> is running. Number of message flows that are enabled to run: <insert_3>. Number of applications that are enabled to run: <insert_8>. Process ID: <insert_4> UUID: <insert_5> Short description: <insert_6> Long description: <insert_7>
- Severity
- 0 : Information
- BIP9287
- Integration server <insert_2> on integration node <insert_1> is stopped. Number of message flows that will start with the integration server: <insert_3>. Number of applications that will start with the integration server: <insert_8>. UUID: <insert_5> Short description: <insert_6> Long description: <insert_7>
- Severity
- 0 : Information
- BIP9288
- Message flow <insert_1> on integration server <insert_2> is running. Additional thread instances: <insert_3> Deployed: <insert_4> in Bar file <insert_5> Last edited: <insert_6> UUID: <insert_10> Start mode: <insert_11> Long description: <insert_9> User-defined property names: <insert_7> Keywords: <insert_8>8
- Severity
- 0 : Information
- BIP9289
- Message flow <insert_1> on integration server <insert_2> is stopped. Additional thread instances: <insert_3> Deployed: <insert_4> in Bar file <insert_5> Last edited: <insert_6> UUID: <insert_10> Start mode: <insert_11> Long description: <insert_9> User-defined property names: <insert_7> Keywords: <insert_8>8
- Severity
- 0 : Information
- BIP9290
- File <insert_1> is deployed to integration server <insert_2>. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> Keywords: <insert_6>6
- Severity
- 0 : Information
- BIP9291
- Unable to enlist RRS resource in unit of work. Resource manager <insert_1> has not successfully completed startup and recovery processing.
- Severity
- 30 : Severe error
- Explanation
- RRS Resource manager <insert_1> cannot participate in a unit of work because it has not fully completed registration and recovery processing. This may be be due to an RRS processing error, or the resource not being available.
- Response
- Use the system log messages together with your resource recovery documentation to determine the source of the problem. Ensure the resource is available, and check the state of the resource in the RRS ISPF panels to ensure it is in the correct state.. Correct the problem and restart the integration node. Contact your IBM support center if you are unable to determine the cause of the problem.
- BIP9298
- File <insert_1> is deployed to integration server <insert_2>. Shared library <insert_7>. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> Keywords: <insert_6>6
- Severity
- 0 : Information
- BIP9299
- File <insert_1> is deployed to integration server <insert_2>. Application <insert_7>. Library <insert_8>. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> Keywords: <insert_6>6
- Severity
- 0 : Information
- BIP9300
- Permission denied error encountered while trying to access directory <insert_2> with user ID <insert_1>.
- Severity
- 20 : Error
- Explanation
- The component has encountered a permission denied error while trying to access a directory.
The typical cause of this failure is incorrect file permissions.
- Response
- Ensure that user ID <insert_1> has the correct permissions to access the directory <insert_2>.
If this problem persists, contact your IBM support center.
- BIP9301
- Invalid policy document <insert_1>.
- Severity
- 20 : Error
- Explanation
- The policy document contained invalid content. Reason: <insert_2>
- Response
- Record the full details provided with this message and contact your IBM Support Center.
- BIP9302
- Invalid policy document <insert_1>.
- Severity
- 20 : Error
- Explanation
- The policy document contained invalid content according to the XML schema: <insert_2>.
- Response
- Review the reason : <insert_3>. Try to correct the policy contents to match the schema. If the problem persists record the full details provided with this message and contact your IBM Support Center.
- BIP9303
- Invalid policy descriptor for the policy type <insert_1>.
- Severity
- 20 : Error
- Explanation
- Policy document can not be validated as the policy descriptor does not contain the required element <insert_2>.
- Response
- Record the full details provided with this message and contact your IBM Support Center.
- BIP9304
- Invalid policy document <insert_1>.
- Severity
- 20 : Error
- Explanation
- The value <insert_2> is not valid for field <insert_3>.
- Response
- The value is expected to be of type <insert_4>.
- BIP9305
- Invalid policy document <insert_1>.
- Severity
- 20 : Error
- Explanation
- The value <insert_2> is not valid for field <insert_3>.
- Response
- Valid values for the <insert_3> field are : <insert_4>.
- BIP9306
- The message flow was not deployed because there is no queue manager associated with the Integration node <insert_1>
- Severity
- 0 : Information
- BIP9307
- The message flow was not deployed because node <insert_1> requires WebSphere MQ Java libraries.
- Severity
- 0 : Information
- Explanation
- An attempt was made to locate the WebSphere MQ Java libraries but they could not be loaded.
- Response
- Check that a supported level of WebSphere MQ is installed and verify that the install path can be discovered by using the command mqsifindmqpath. If IBM Integration Bus cannot determine your installation location, run the setmqenv script.
- BIP9308
- Failed to update policy; it does not exist in the integration node registry <insert_1>.
- Severity
- 20 : Error
- Explanation
- None
- Response
- None
- BIP9309
- Failed to update service file; it does not exist in the integration node registry <insert_1>.
- Severity
- 20 : Error
- Explanation
- None
- Response
- None
- BIP9310
- The integration registry that is hosted by integration node <insert_1> does not require migration.
- Severity
- 0 : Information
- Response
- No user action required.
- BIP9311
- Starting migration of the integration registry that is hosted by integration node <insert_1>.
- Severity
- 0 : Information
- Response
- No user action required.
- BIP9312
- Policies and services from V9.0 installation migrated successfully for integration node <insert_1>.
- Severity
- 0 : Information
- Response
- No user action required.
- BIP9313
- Migration of policies and services from V9.0 installation did not complete successfully for integration node <insert_1>.
- Severity
- 20 : Error
- Explanation
- See previous messages for details
- Response
- No user action required.
- BIP9314
- The Accounting and Statistics CSV File Writer failed to write to the file <insert_1>.
- Severity
- 20 : Error
- Explanation
- The Accounting and Statistics CSV File Writer failed to write to the file <insert_1>. Please ensure that the parent directory exists and, the Integration Node's username has permission to access the file and that there is sufficient diskspace on the file system.
- Response
- Please ensure that the parent directory exists and, the Integration Node's username has permission to access the file and that there is sufficient diskspace on the file system.
- BIP9315
- The ESQL Performance Statistics File Writer failed to write to the file <insert_1>.
- Severity
- 20 : Error
- Explanation
- The ESQL Performance Statistics File Writer failed to write to the file <insert_1>. Please ensure that the parent directory exists, the Integration Node's username has permission to access the file, the value configured for 'performanceStatsOutputPath' property is a valid file path and that there is sufficient diskspace on the file system.
- Response
- Please ensure that the parent directory exists, the Integration Node's username has permission to access the file, the value configured for 'performanceStatsOutputPath' property is a valid file path and that there is sufficient diskspace on the file system.
- BIP9316
- The message flow was not deployed because node type <insert_1> requires the use of the shipped MQ java classes, which has been disabled.
- Severity
- 20 : Error
- Explanation
- The integration node received a configuration message that contains an instruction to create a message flow node of type <insert_1>. The node cannot be created because the node type requires use of the shipped MQ java classes, which has been disabled.
- Response
- Review the documentation and remove any nodes from your message flows that are not supported when use of the shipped MQ classes is disabled. Alternatively, unset the 'MQSI_DISABLE_SHIPPED_MQ' environment variable.
- BIP9317
- The deployed resource <insert_1>, <insert_2> of type <insert_3> cannot start as it contains configuration errors or has dependencies which can not be resolved.
- Severity
- 20 : Error
- Explanation
- The resource has configuration errors, or a dependancy upon which the resource is dependant upon could not be located. The resource cannot be started until the errors are fixed. Information on the error(s) are included in the associated error messages.
- Response
- Use the associated error messages to identify and resolve the configuration errors or missing dependancies.
- BIP9318
- Request to <insert_1> resource <insert_2>, <insert_3> of type <insert_4> failed.
- Severity
- 20 : Error
- Explanation
- The <insert_1> operation on the resource <insert_2>, <insert_3> of type <insert_4> failed. Further messages have been logged with details of the error.
- Response
- Use the previous error messages to identify the cause of the error and correct before retrying the operation.
- BIP9319
- The deployed resources contain errors.
- Severity
- 20 : Error
- Explanation
- The resources deployed contain configuration errors, or have dependencies which could not be resolved.
- Response
- Use the associated error messages to identify and resolve the configuration errors or missing dependencies.
- BIP9320
- Message Flow <insert_1>, <insert_2> encountered a failure and could not start.
- Severity
- 20 : Error
- Explanation
- A request was made to start message flow <insert_1> but the message flow encountered a failure and could not start.
- Response
- Use the associated error messages to identify and resolve the failures which prevented the message flow from starting.
- BIP9321
- Resource <insert_1> of type <insert_2> cannot be deployed at this time because it is already deployed.
- Severity
- 20 : Error
- Explanation
- A request was made to deploy the resource <insert_1> but the resource is already deployed and cannot be redeployed at this time.
- Response
- Delete the deployed resource before attempting to redeploy it.
- BIP9322
- The Java isolation setting for Application <insert_1> is set to disabled. This option is no longer supported such that no java classes will be shared with Application <insert_1>,
- Severity
- 10 : Warning
- Explanation
- Java is isolated for all applications and this can no longer be configured.
- Response
- Shared Libraries can be used to share Java between applications that reference them.
- BIP9323
- The request to <insert_1> the deployed resource <insert_2> of type <insert_3> was successful.
- Severity
- 0 : Information
- Explanation
- An integration server has completed an action successfully.
- Response
- No user action required.
- BIP9324
- The request to <insert_1> the deployed resource <insert_2> of type <insert_3> has failed.
- Severity
- 10 : Warning
- Explanation
- An integration server has completed an action but the operation did not complete successfully .
- Response
- No user action required.
- BIP9325
- The source <insert_1> could not be deployed as it contains errors. No changes have been made to the integration server.
- Severity
- 20 : Error
- Explanation
- The source <insert_1> could not be processed. Further error messages will contain detailed information on the cause of the errors.
- Response
- Use the associated messages to correct the errors before redeploying the source.
- BIP9326
- The source <insert_1> has been successfully deployed.
- Severity
- 0 : Information
- BIP9327
- The request to delete resource <insert_1> from application <insert_2> has failed with system error code <insert_3>.
- Severity
- 20 : Error
- Explanation
- The request to delete the resource definition from the file system at location <insert_4> has failed.
- Response
- In the case of a temporary failure re-issue the request to complete the operation.
- BIP9328
- The policy project <insert_1> cannot be redeployed as the non-dynamic policy <insert_2> differs or has been deleted from the policy project being deployed.
- Severity
- 20 : Error
- Explanation
- The changing or deletion of policies within a policy project is only supported for certain types of policy.
- Response
- In order to make changes to a policy of this type, it is necessary to delete all deployed resources from the integration server and then redeploy all the resources including the modified version of the policy project.
- BIP9329
- The project <insert_1> of type <insert_2> cannot be deployed as a project with the same name of type <insert_3> already exists on the integration server.
- Severity
- 20 : Error
- Explanation
- A project cannot be deployed if a project with the same name already exists on the integration server.
- Response
- Either delete the existing project from the integration server or change the name of the project being deployed.
- BIP9330
- The project <insert_1> of type <insert_2> has been marked as deleted but cannot be permanently removed as another process is accessing the disk location where the project is stored. The project will be deleted from disk when the Integration Server is restarted.
- Severity
- 10 : Warning
- Explanation
- The disk location for a project is open by another process which prevents the project from being permanently deleted. The project and its dependencies have been left in stopped state and will be deleted when the Integration Server is restarted.
- Response
- Close any processes which may be accessing the file-system location <insert_3> before reissuing the request.
- BIP9331
- The source <insert_1> has been successfully processed but contained no deployable resources.
- Severity
- 0 : Information
- Explanation
- A BAR file has been deployed which contained no deployable resources.
- BIP9332
- <insert_1> <insert_2> has been <insert_3> successfully.
- Severity
- 0 : Information
- Explanation
- The resource <insert_2> of type <insert_1> has been successfully <insert_3>.
- BIP9333
- <insert_1> <insert_2> has been <insert_3> but contains errors which has prevented some resources from starting.
- Severity
- 10 : Warning
- Explanation
- The resource <insert_2> of type <insert_1> has been <insert_3> but it contains errors or missing dependencies which has prevented some of the resources within the <insert_1> from starting.
- BIP9334
- Warning from XLXP&colon. <insert_1> <insert_2> <insert_3>
- Severity
- 10 : Warning
- Explanation
- A warning was generated processing an XML schema.
- BIP9335
- The policy(s) <insert_1> in the policy project <insert_2> match existing administrator defined policy(s). Any deployed resources using the policy(s) will not be affected by the redeploy of the policy project.
- Severity
- 10 : Warning
- Explanation
- The policy project <insert_2> contains policies which are configured as override or integration node level policies. The deployed values will not be used until the integration server is restarted. When the integration server next starts the deployed policy will be used if there is no matching override policy.
- BIP9336
- The policy <insert_1> in policy project <insert_2> cannot be deleted as it is in use.
- Severity
- 20 : Error
- Explanation
- The redeploy of policy project <insert_2> is attempting to delete the policy <insert_1> which is in use by other projects deployed to the server.
- Response
- Delete any projects using the policy before deleting the policy.
- BIP9337
- The project <insert_1> of type <insert_2> cannot be loaded as a previous instance of the project is pending deletion.
- Severity
- 20 : Error
- Explanation
- The project <insert_1> of type <insert_2> has been marked as deleted but could not be permanently removed as another process was accessing the disk location where the project was stored. The project will be deleted from disk when the Integration Server is restarted.
- Response
- Close any processes which may be accessing the file-system location before restarting the Integration Server.
- BIP9338
- The deployed policies within the policy project <insert_1> are being deleted. The policy project also contains administrator defined policy(s) <insert_2> which will not be deleted.
- Severity
- 10 : Warning
- Explanation
- The policy project contains policies which are configured as override or integration node level policies. To delete these policies the policyxml files must be deleted from the filesystem and the integration server restarted.
- BIP9339
- The values defined in the policy(s) <insert_1> in policy project <insert_2> match the values of the existing policy(s). Any deployed resources using the policy(s) will not be affected by the redeploy of the policy project.
- Severity
- 10 : Warning
- Explanation
- When a policy is redeployed with the same values as the existing policy no changes are made to any resources which are using the existing policy.
- BIP9340
- Integration server failed, because the specified directory <insert_1> is already in use.
- Severity
- 20 : Error
- Explanation
- Only one instance of the integration server can be run within a work directory, this instance cannot continue because it cannot acquire exclusive use of the file <insert_2>.
- Response
- Ensure that the integration server is being started with the correct work directory and that no other instances are using that work directory.
- BIP9341
- Created compiled 'DFDL' schema file <insert_1>.
- Severity
- 0 : Information
- Explanation
- The deployed schema resources for 'DFDL' have been compiled into their runtime format.
- Response
- The 'mqsibar' command can be used to compile schema resources for 'DFDL' into their runtime format prior to deployment.
- BIP9342
- Created compiled 'XMLNSC' schema file <insert_1>.
- Severity
- 0 : Information
- Explanation
- The deployed schema resources for 'XMLNSC' have been compiled into their runtime format.
- Response
- The 'mqsibar' command can be used to compile schema resources for 'XMLNSC' into their runtime format prior to deployment.
- BIP9343
- Failed to acquire lock for integration node <insert_1>.
- Severity
- 20 : Error
- Explanation
- Failure to acquire the integration node lock may indicate that an instance of the integration node is already running.
- Response
- Ensure that any previous instance of the integration node is stopped before attempting to restart the integration node.
- BIP9344
- The integration server is shutting down due to an unhandled exception.
- Severity
- 20 : Error
- Explanation
- A processing exception has occurred from which the integration server could not recover. Further messages will include information about the exception. The integration server process is shutting down. If the integration server is managed by an integration node it will be restarted.
- Response
- Use the information contained in the subsequent messages to correct any problem and restart the integration server.
- BIP9345
- The BAR file <insert_1> is empty.
- Severity
- 10 : Warning
- Explanation
- This is not an error, however if the deploying of a zero length BAR file was unintentional verify the correct BAR file is being deployed.
- BIP9350
- Push REST APIs to an &ibmapiconnect. system.
- Severity
- 0 : Information
- Explanation
- Syntax:
mqsipushapis connectionSpec -e integrationServerName --apic-host host --apic-port port --apic-version version [--apic-username user --apic-password password [--apic-realm realm --apic-client-id clientId --apic-client-secret clientSecret]] [--apic-api-key apiKey] --apic-org organization [--apic-catalog-title catalogTitle] --apic-product-title productTitle [--apic-product-name Integration Bus] [--apic-product-version productVersion] --rest-apis restApis [--http-proxy-host httpInboundProxyHost] [--https-proxy-host httpsInboundProxyHost] [-v traceFileName] [-w timeoutSecs]
Command Options:
'connectionSpec' is one of:
(a) 'integrationNodeName' : Name of a local integration node
(b) '--admin-host (-i) hostname --admin-port (-p) port' : hostname and port of an integration node or standalone integration server.
(c) '--integration-node-file (-n) fileName' : File containing integration node connection parameters (*.broker)
'--integration-server (-e) integrationServerName' The name of the integration server.
'--apic-host (-t) host' The host name of the &ibmapiconnect. system.
'--apic-port (-g) port' The port of the &ibmapiconnect. system.
'--apic-version version' The version of the &ibmapiconnect. system. One of 'v5', 'v5-on-ibm-cloud', 'v2018'.
'--apic-username (-u) user' The user name that is being used to connect to &ibmapiconnect.. Required for v5 and v2018.
'--apic-password (-a) password' The password that is being used to connect to &ibmapiconnect.. Required for v5 and v2018.
'--apic-api-key apiKey' The API key that is being used to connect to &ibmapiconnect.. Required for v5-on-ibm-cloud.
'--apic-realm realm' The realm that is being used to connect to &ibmapiconnect.. Required for v2018.
'--apic-client-id clientId' The client ID that is being used to connect to &ibmapiconnect.. Required for v2018.
'--apic-client-secret clientSecret' The client secret that is being used to connect to &ibmapiconnect.. Required for v2018.
'--apic-disable-certificate-verification' Ignore certificate validation errors when connecting to &ibmapiconnect.. This flag can be used when connecting to &ibmapiconnect. environments that present self-signed certificates.
'--apic-org (-o) organization' The name of the &ibmapiconnect. organization where the APIs will be pushed.
'--apic-catalog-title (-c) catalogTitle' The title of the &ibmapiconnect. catalog where the product will be staged. This is optional. If you do not specify this option, then the product will not be staged. This option must be provided if the -k | --rest-apis option is omitted, in which case the product will be staged without pushing APIs.
'--apic-product-title (-r) productTitle' The title of the &ibmapiconnect. product to create or update and then stage.
'--apic-product-name (-d) Integration Bus' The name of the &ibmapiconnect. product to create or update and then stage. This is optional. If you do not specify this option, the name of the product will be derived from the title.
'--apic-product-version (-s) productVersion' The version of the &ibmapiconnect. product to create or update and then stage. This is optional. A value of '1.0.0' will be used if no value is supplied.
'--rest-apis (-k) restApis' A list of API names, separated by colons (:), that will be pushed to &ibmapiconnect.. If you do not specify this option, you must specify the -c | --apic-catalog-title option.
'--http-proxy-host (-x) httpInboundProxyHost' The host name and port of the proxy that receives the inbound HTTP request for the REST API that is running on IBM Integration Bus. The host name and port are separated by a colon (:). If no value is specified, the host name and HTTP port of the integration server will be used. This is optional.
'--https-proxy-host (-y) httpsInboundProxyHost' The host name and port of the proxy that receives the inbound HTTPS request for the REST API that is running on IBM Integration Bus. The host name and port are separated by a colon (:). If no value is specified, the host name and HTTPS port of the integration server will be used. This is optional.
'--trace (-v) traceFileName' Send verbose internal trace to the specified file. This is optional.
'--timeout-seconds (-w) timeoutSecs' Maximum number of seconds to wait for the integration node or server to respond (default is 60).
- BIP9351
- The value specified for the &ibmapiconnect. port is not a number (<insert_1>).
- Severity
- 20 : Error
- Explanation
- The mqsipushapis command requires an integer value for the &ibmapiconnect. port parameter (apiConnectPort) supplied with the --apic-port (-g) flag, but it received <insert_1>.
- Response
- Retry the command specifying a valid port value. The port value must be a number between 0 and 65535.
- BIP9352
- The organization <insert_1> could not be found in &ibmapiconnect..
- Severity
- 20 : Error
- Explanation
- The organization <insert_1> that was specified for the operation could not be found in the &ibmapiconnect. system. The available organizations are <insert_2>.
- Response
- Retry the operation, specifying a valid organization.
- BIP9353
- An error occurred while connecting to &ibmapiconnect. using the mqsipushapis command.
- Severity
- 20 : Error
- Explanation
- Check that you have supplied the correct parameter values for connecting to &ibmapiconnect..
- Response
- Retry the mqsipushapis command specifying the correct parameter values.
- BIP9354
- The <insert_1> catalog could not be found in the <insert_2> organization in &ibmapiconnect..
- Severity
- 20 : Error
- Explanation
- The <insert_1> catalog for the <insert_2> organization must exist in &ibmapiconnect., but the <insert_1> catalog does not exist. The available catalogs are <insert_3>.
- Response
- Check that you have supplied the correct value for your organization and catalog and then retry the operation. If the problem persists, contact your &ibmapiconnect. Administrator and request the <insert_1> catalog to be created.
- BIP9355
- The product <insert_1> is already staged for the organization <insert_2> in &ibmapiconnect.. It will be replaced.
- Severity
- 0 : Information
- BIP9356
- Successfully created API <insert_1> in &ibmapiconnect..
- Severity
- 0 : Information
- BIP9357
- Successfully replaced API <insert_1> in &ibmapiconnect..
- Severity
- 0 : Information
- BIP9358
- Successfully created product <insert_1> and added API <insert_2> to it in &ibmapiconnect..
- Severity
- 0 : Information
- BIP9359
- Successfully added API <insert_2> to product <insert_1> in &ibmapiconnect..
- Severity
- 0 : Information
- BIP9360
- Successfully staged product <insert_1> to catalog <insert_3> for organization <insert_2> in &ibmapiconnect..
- Severity
- 0 : Information
- BIP9361
- The REST API <insert_1> is not deployed to the integration server <insert_2>.
- Severity
- 20 : Error
- Explanation
- The REST API must be deployed to the integration server before it can be pushed to &ibmapiconnect..
- Response
- Check that you have supplied the correct REST API name and integration server name and then retry the operation. If the problem persists, ensure that the REST API has been deployed to the integration server.
- BIP9362
- The product <insert_1> could not be staged in &ibmapiconnect. due to an earlier error.
- Severity
- 20 : Error
- Explanation
- An error occurred while running the mqsipushapis command, so the product <insert_1> could not be staged.
- Response
- Check why the mqsipushapis command failed, correct the error, and rerun the command.
- BIP9363
- The selected installation of &ibmapiconnect. is not supported. The minimum supported version of &ibmapiconnect. is version <insert_1>.
- Severity
- 20 : Error
- Explanation
- This operation cannot be used with this version of &ibmapiconnect..
- Response
- Select an &ibmapiconnect. installation that satisfies the minimum required version.
- BIP9364
- &ibmapiconnect. operation failed with error <insert_1>.
- Severity
- 20 : Error
- Explanation
- The &ibmapiconnect. operation failed.
- Response
- Use the details of the error contained within the message to correct the problem before retrying the operation.
- BIP9365
- A connection cannot be made to &ibmapiconnect. at <insert_1>. Error <insert_2>.
- Severity
- 20 : Error
- Explanation
- A connection could not be established to &ibmapiconnect. at <insert_1>.
- Response
- Verify that the connection details are correct before you retry the operation. If the cause of the error is that the &ibmapiconnect. certificate cannot be verified, you can select the option to disable certificate verification.
- BIP9366
- Product <insert_1> was not staged for organization <insert_2> in &ibmapiconnect. as staging was not requested.
- Severity
- 0 : Information
- BIP9367
- More than one <insert_1> catalog was found in the <insert_1> organization in &ibmapiconnect..
- Severity
- 20 : Error
- Explanation
- The <insert_1> catalog was specified for the <insert_2> organization, but multiple catalogs of the same name were found.
- Response
- Check that you have supplied the correct values for your organization and catalog and then retry the operation.
- BIP9368
- The <insert_1> catalog was found in the <insert_2> organization in &ibmapiconnect. but it was not of type 'Sandbox' so it cannot be used.
- Severity
- 20 : Error
- Explanation
- The <insert_1> catalog for the <insert_2> organization must exist in &ibmapiconnect. and it must be of type 'Sandbox'.
- Response
- Check that you have supplied the correct values for your organization and catalog and then retry the operation. If the problem persists, contact your &ibmapiconnect. Administrator and request the <insert_1> catalog to be created and to be of type 'Sandbox'.
- BIP9369
- The product <insert_1> with version <insert_2> was found in organization <insert_3> in &ibmapiconnect.; however, it has title <insert_4>, which is different from the title <insert_5> that was specified.
- Severity
- 20 : Error
- Explanation
- A product was found with the product name <insert_1> and version <insert_2>, but the title <insert_5> did not match the title in the product.
- Response
- Check that you have supplied the correct value for your product title and then retry the operation.
- BIP9370
- The mqsipushapis command could not complete due to earlier errors.
- Severity
- 20 : Error
- Explanation
- An error occurred while running the mqsipushapis command.
- Response
- Check the previous errors to find out why the mqsipushapis command failed, correct the error, and then rerun the command.
- BIP9371
- The user ID <insert_1> has role <insert_2>, but the role does not have 'read' permission on the integration server <insert_3>.
- Severity
- 20 : Error
- Explanation
- The user ID that is being used to connect to the integration server has role <insert_2>, but that role does not have the required permission to push the REST APIs to &ibmapiconnect.. The role must have 'read' permission on the integration server <insert_3>.
- Response
- Grant 'read' permission to the role <insert_2> for integration server <insert_3>, or associate user ID <insert_1> with a different role that has the required authorization.
- BIP9372
- Product <insert_1> was not staged for organization <insert_2>, because no REST APIs were successfully pushed to &ibmapiconnect..
- Severity
- 0 : Information
- BIP9373
- A negative response has been received.
- Severity
- 20 : Error
- Explanation
- This command failed because there is invalid data in the file 'C2CPolicy.xml' that is used to hold the integration node configuration information for the IBM Cloud Product Insights and IBM Cloud Log Analysis services. The command has detected an error in the format of the XML data.
- Response
- Check the system log for further information and ensure that the integration node registry is valid. It might be possible to modify the XML data that the command is parsing so that the error does not recur.
- BIP9374
- A negative response has been received.
- Severity
- 20 : Error
- Explanation
- This command cannot set IBM Cloud Product Insights, IBM Cloud Log Analysis, or both active because missing data in the configuration policy. The field <insert_1> requires a value.
- Response
- Reissue the command and ensure that you add the parameter to specify the missing configuration value.
- BIP9375
- The template <insert_1> has been copied into the workpath at <insert_2>.
- Severity
- 0 : Information
- Explanation
- The specified workpath at <insert_2> did not contain a <insert_1> file so the product supplied template was copied in.
- Response
- Review the <insert_1> and edit to change configuration values.
- BIP9376
- The template <insert_1> could not be copied into the workpath at <insert_2>.
- Severity
- 10 : Warning
- Explanation
- The specified workpath at <insert_3> did not contain a <insert_1> file, however the product supplied template could not be copied into it.
- Response
- Changes to default configuration for this IntegrationServer can only be supplied via command line arguments.
- BIP9377
- The Switch server exists, but it has not been started.
- Severity
- 0 : Information
- BIP9378
- The Switch server exists and is running.
- Severity
- 0 : Information
- BIP9379
- The Switch server is configured for secure connectivity and callable flows.
- Severity
- 0 : Information
- BIP9380
- The Switch server is configured as a secure connectivity agent for on-premises systems.
- Severity
- 0 : Information
- BIP9381
- The Switch server is configured as a secure connectivity agent for cloud systems.
- Severity
- 0 : Information
- BIP9382
- Generated the self-signed certificate file <insert_1>.
- Severity
- 0 : Information
- BIP9383
- Generated the switch configuration file <insert_1>.
- Severity
- 0 : Information
- BIP9384
- Generated the agentx configuration file <insert_1>.
- Severity
- 0 : Information
- BIP9385
- The specified output directory <insert_1> does not exist, is not a directory, or is not writeable.
- Severity
- 20 : Error
- BIP9386
- The version <insert_1> specified for the &ibmapiconnect. system is not supported.
- Severity
- 20 : Error
- Explanation
- The version <insert_1> that was specified for the operation is not a version of &ibmapiconnect. that is supported.
- Response
- Specify a valid version, then retry the operation. The version must be one of 'v5', 'v5-on-ibm-cloud', or 'v2018'.
- BIP9387
- Making IBM Integration Bus administrative REST API call <insert_1> <insert_2>.
- Severity
- 0 : Information
- BIP9388
- IBM Integration Bus administrative REST API call failed with status code <insert_1> and error <insert_2>.
- Severity
- 20 : Error
- Explanation
- A failure status code was returned by an administrative REST API call.
- Response
- Review the error, make any corrections to the parameters that you are using, and retry the operation.
- BIP9399
- The flag <insert_1> has been deprecated, so its value has been ignored. The command will continue to execute as if the flag was never specified. Refer to the Integration Bus documentation in the IBM Knowledge Center for further information.
- Severity
- 10 : Warning
- Explanation
- The flag <insert_1> has been deprecated. Refer to the Integration Bus documentation in the IBM Knowledge Center for further information.
- BIP9400
- Unable to retrieve the Swagger definition for REST API <insert_1> on integration server <insert_2>. <insert_2> is stopped.
- Severity
- 20 : Error
- Explanation
- To retrieve the Swagger definition, the integration server <insert_2> must be running.
- Response
- Ensure that the integration server is running, then retry the operation.
- BIP9401
- Unable to retrieve the Swagger definition for REST API <insert_1>. Integration server <insert_2> does not exist.
- Severity
- 20 : Error
- Explanation
- An attempt was made to retrieve the Swagger definition for a REST API from an integration server, but no server with name <insert_2> exists for the integration node.
- Response
- Ensure that the name of the integration server is specified correctly, then retry the operation.
- BIP9402
- Unable to complete administration REST API call <insert_1> <insert_2>. No session exists with &ibmapiconnect..
- Severity
- 20 : Error
- Explanation
- In order to interact with &ibmapiconnect., you must first create a session, then use the session cookie on all subsequent calls.
- Response
- Create a session with &ibmapiconnect. by using administration REST API call 'POST /apiv2/api-session'. In the response, find the 'set-cookie' header value that starts with 'ACE-Session-'. Use that as the value of the 'Cookie' header of REST API call <insert_1> <insert_2>, then retry the call.
- BIP9403
- Unable to complete the &ibmapiconnect. operation because of a missing or invalid property <insert_1>.
- Severity
- 20 : Error
- Explanation
- The body of the request for the &ibmapiconnect. operation either does not contain property <insert_1> or the property is not of the correct type.
- Response
- Ensure that the request has a body and that the body contains a valid value for property <insert_1>, then retry the operation.
- BIP9404
- Unable to retrieve the Swagger definition for REST API <insert_1>. The integration server returned error <insert_2>.
- Severity
- 20 : Error
- Explanation
- An attempt was made to retrieve the Swagger definition for a REST API from an integration server, but the server returned an error.
- Response
- Ensure that the name of the REST API is correct and retry the operation. If the problem persists, restart the integration server and retry the operation.
- BIP9843
- Property <insert_1> for policy <insert_2> cannot be deleted.
- Severity
- 10 : Warning
- Explanation
- You have tried to delete a policy property that cannot be removed. You can delete properties for UserDefined policies only.
- Response
- Run the mqsireportproperties command to check that the policy is defined as type UserDefined. Then modify and reissue the command.
- BIP9844
- WebSphere MQ service definitions for component <insert_1> cannot be migrated backwards, please update manually.
- Severity
- 10 : Warning
- Explanation
- When migrating backwards, MQ service definitions for component <insert_1> must be updated manually.
- Response
- None.
- BIP9845
- Failed to detach policy as it is already detached.
- Severity
- 20 : Error
- Explanation
- The resource does not have a policy attached so the detach command is ineffective.
- Response
- None.
- BIP9846
- Policy type of <insert_1> is invalid.
- Severity
- 20 : Error
- Explanation
- It is not valid to attach a policy of the given type to the resource.
- Response
- Ensure a supported policy type is being used (For example: WorkloadManagement).
- BIP9847
- The specified object name, <insert_1>, contains an invalid character or begins with a number.
- Severity
- 20 : Error
- Explanation
- The object name must contain only characters that are supported by the platform on which the command is being processed, and must not begin with a number.
- Response
- Specify a valid object name and then reissue the command.
- BIP9848
- The MQSI_WORKPATH environment variable has not been set, so the command cannot continue.
- Severity
- 20 : Error
- Explanation
- The command must be run from an environment that has the environment variable MQSI_WORKPATH set.
- Response
- Ensure that the correct environment has been set up to enable the command to run.
- BIP9849
- Failed to lock file <insert_1>. Reason <insert_2>.
- Severity
- 20 : Error
- Explanation
- A request was made to lock the file <insert_1>, but this request failed.
- Response
- Verify the location of the lock file exists and the current user has sufficient permissions to create the lock file.
- BIP9850
- Failed to access lock file <insert_1>.
- Severity
- 20 : Error
- Explanation
- A request was made to check the status of the lockfile <insert_1> but the file does not exist.
- Response
- Verify the location of the lock file exists and the current user has sufficient permissions to access the lock file.
- BIP9851
- The multi-instance or High Availability integration node <insert_1> on queue manager <insert_2> is active on another host.
- Severity
- 20 : Error
- Explanation
- This integration node is not running on this system but is running on another system; the command you issued cannot be processed when an integration node is active on another host system.
- Response
- The command should be issued on the active multi-instance integration node <insert_1>.
- BIP9852
- <insert_1> <insert_2> Active state=<insert_3>
- Severity
- 0 : Information
- BIP9853
- <insert_1> <insert_2> Configured state=<insert_3>
- Severity
- 0 : Information
- BIP9854
- The command 'mqsimigratecomponents' has been permanently removed, please refer to 'mqsiextractcomponents'.
- Severity
- 0 : Information
- BIP9855
- Cannot restore an Integration Node under a new name. Argument integrationNodeName, <insert_1>, needs to match the Integration Node name, <insert_2>, found in archive <insert_3>.
- Severity
- 0 : Information
- BIP9875
- Service <insert_1> on integration server <insert_2> is running. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> UUID <insert_8> Start mode: <insert_9> Java isolation: <insert_10> Long description: <insert_6> Keywords: <insert_7>7
- Severity
- 0 : Information
- BIP9876
- Service <insert_1> on integration server <insert_2> is stopped. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> UUID <insert_8> Start mode: <insert_9> Java isolation: <insert_10> Long description: <insert_6> Keywords: <insert_7>7
- Severity
- 0 : Information
- BIP9877
- REST API <insert_1> on integration server <insert_2> is running. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> UUID <insert_8> Start mode: <insert_9> Java isolation: <insert_10> Long description: <insert_6> Keywords: <insert_7>7
- Severity
- 0 : Information
- BIP9878
- REST API <insert_1> on integration server <insert_2> is stopped. Deployed: <insert_3> in Bar file <insert_4> Last edited: <insert_5> UUID <insert_8> Start mode: <insert_9> Java isolation: <insert_10> Long description: <insert_6> Keywords: <insert_7>7
- Severity
- 0 : Information