Explanation | The server has received a stop command. The server will begin shutting down. |
Action | No action is required. |
Explanation | The server has completed processing the indicated command. If the command did not complete successfully, previous messages will indicate the reason. |
Action | No action is required. |
Explanation | The server called to native code for a command processing related service. The native code encountered the problem identified by the displayed error code. |
Action | Examine the server logs to determine the reason for the native code failure. |
Explanation | The server received a modify command to process. This is the command response message from the command handler. Message CWWKB0005I identifies the command handler. |
Action | No action is required. |
Explanation | The server received a modify command to process. This message indicates that the command handler has finished processing the command. |
Action | No action is required. |
Explanation | The server has completed processing the indicated command. No active command handler reported processing the command. |
Action | Check the syntax of the command to ensure it is correct then re-issue the command. |
Explanation | The server received a modify command to process. This message indicates that the command handler has encountered an error while processing the command. |
Action | Examine the server logs to determine the reason for the Command Handler error. |
Explanation | The server attempted to issue a command response message. It was unable to resolve the message with its message bundle. |
Action | Examine the server logs to determine the reason for a related Command Handler error. |
Explanation | The server attempted to issue a command response message. It was unable to translate the message response to the native encoding ("Cp1047"). |
Action | Examine the server logs to determine the reason for the error. |
Explanation | The server received a modify command. It was unable to translate the command text from the native encoding ("Cp1047"). |
Action | Examine the server logs to determine the reason for the error. |
Explanation | This message represents the start of help information from the indicated command handler. |
Action | No action is required. |
Explanation | Help information from the indicated command handler is displayed. |
Action | No action is required. |
Explanation | This message represents the end of help information from the indicated command handler. |
Action | No action is required. |
Explanation | The server attempted to delete the pid file during server stop. It was unable to delete the pid file specified by {0}. |
Action | Examine the server logs if server stopped properly. |
Explanation | The angel cannot be stopped because there are currently servers connected to it. |
Action | Message CWWKB0052I will contain the ASID for each server that is currently active. Stop the active servers and then try stopping the angel again. |
Explanation | This server is currently connected to the angel process. |
Action | No action is necessary. |
Explanation | The version of the angel processes dynamic replaceable module is displayed, in response to a MODIFY PROCESS,VERSION command. |
Action | No action is necessary. |
Explanation | The modify command being processed by the angel contains unrecognized keywords. |
Action | Re-issue the command with the correct syntax. |
Explanation | An angel process is starting. |
Action | No action is necessary. |
Explanation | An angel process has completed initialization. |
Action | No action is necessary. |
Explanation | An angel process is ending. |
Action | No action is necessary. |
Explanation | An angel process has ended abnormally. |
Action | For more information, see previous messages in the job log or system log. The message text includes an internal reason code to be used by product support. |
Explanation | An unrecognized parameter was passed on the angel start command. The unrecognized parameter is printed in the message. |
Action | Refer to the product documentation for the supported start command parameters. |
Explanation | A recognized parameter key was passed on the angel start command, but its value was unrecognized. The key and the value are printed in the message. |
Action | Refer to the product documentation for the supported start command parameter keys, and supported values. |
Explanation | A command response message from a command handler or a message being written to the operator or hard copy log needs to be issued by multiple multiline WTOs. This is a continuation of the message. Use the message identifier to group related CWWKB0061I messages. |
Action | No action is necessary. |
Explanation | An angel process is already running on this system. The ASID and JOBNAME of the active angel process are printed in message CWWKB0063I. The second angel process will stop. |
Action | No action is necessary. |
Explanation | This angel process is active. |
Action | No action is necessary. |
Explanation | This message is printed in response to a MODIFY BBGZANGL,HELP command. The RELOAD option causes the load modules for the angel process to be reloaded from the file system. A reload may be required after a PTF is installed if the angel process is not restarted. |
Action | No action is necessary. |
Explanation | This message is printed in response to a MODIFY BBGZANGL,HELP command. The VERSION option displays the version of the angel process dynamically replaceable load module. This information may be requested by IBM service and support. |
Action | No action is necessary. |
Explanation | This message is printed in response to a MODIFY BBGZANGL,HELP command. The TRACE option controls trace messages in the angel process. Modifying TRACE=Y displays diagnostic traces to the SYSOUT DD. Modifying TRACE=N disables the diagnostic traces. This information may be requested by IBM service and support. |
Action | No action is necessary. |
Explanation | This message is printed in response to a MODIFY BBGZANGL,SERVERS command. This message will be followed by one instance of message CWWKB0052I for each server which is connected to the angel process. |
Action | No action is necessary. |
Explanation | This message is printed in response to a MODIFY BBGZANGL,HELP command. The SERVERS option displays active servers. |
Action | No action is necessary. |
Explanation | An angel process has completed initialization. The angel name is displayed in the message. |
Action | No action is required. |
Explanation | The NAME parameter specifies the name of the angel process. The parameter is specified on the BBGZANGL PROC and must be 54 characters or less. |
Action | Specify a value of 54 characters or less for the NAME parameter, and start the angel process using the BBGZANGL PROC again. |
Explanation | The NAME parameter specifies the name of the angel process. The parameter is specified on the BBGZANGL PROC and can only contain characters from the following character set: A-Z 0-9 ! # $ + - / : < > = ? @ [ ] ^ _ ` { } | ~ |
Action | Specify a value using the supported character set for the NAME parameter, and start the angel process using the BBGZANGL PROC again. |
Explanation | An angel process cannot be stopped because servers are currently connected to it. The angel name is displayed in the message. |
Action | Message CWWKB0052I contains the ASID for each server that is currently active and associated with the named angel. Stop the active servers and then stop the angel named in the message. |
Explanation | An angel process is ending. The angel name is displayed in the message. |
Action | No action is required. |
Explanation | An angel process ended abnormally. The angel name is displayed in the message. |
Action | The message text includes a reason code that describes the specific error, and the name of the angel process that ended. See previous messages in the job log or system log for more information. |
Explanation | An angel process with the name displayed in the message is already running on this system. The ASID and JOBNAME of the active angel process are printed in the CWWKB0063I message. The second angel process will stop. |
Action | No action is required because the duplicate angel process will stop. To prevent this message, do not start a named angel process when an angel process with the same name is already running. |
Explanation | This message is printed in response to a MODIFY BBGZANGL,ANGELS command. This message is followed by one instance of the CWWKB0077I message and one instance of the CWWKB0078I message for each angel process that is active on the system. |
Action | No action is required. |
Explanation | The message text specifies the details of an active angel process. This message is preceded by the CWWKB0076I message and precedes the CWWKB0078I message. |
Action | No action is required. |
Explanation | The message text specifies the name of an active angel process. This message is preceded by the CWWKB0076I message and the CWWKB0077I message. |
Action | No action is required. |
Explanation | The message text specifies the build level and the beta build level of the angel process. The build level after the / is the beta build level. |
Action | No action is required. |
Explanation | This server is currently connected to the angel process. |
Action | No action is necessary. |
Explanation | This message is printed in response to a MODIFY BBGZANGL,HELP command. The SERVER,PID option displays active servers and their PIDS. |
Action | No action is necessary. |
Explanation | The ARMEL parameter specifies the arm element name to register. The parameter is specified on the BBGZANGL PROC and must be 16 characters or less. |
Action | Specify a value of 16 characters or less for the ARMEL parameter, and start the angel process using the BBGZANGL PROC again. |
Explanation | The ARMEL parameter specifies the element name for automatic restart manager. The parameter is specified on the BBGZANGL PROC and can only contain characters from the following character set: A-Z 0-9 $ # @ _ |
Action | Specify a value using the supported character set for the ARMEL parameter, and start the angel process using the BBGZANGL PROC again. |
Explanation | This angel has successfully registered with the automatic restart manager (ARM). |
Action | No action is necessary. |
Explanation | The angel has been successfully registered with the automatic restart manager on restart and any abrupt shutdown will automatically bring up this angel. |
Action | No action is necessary. |
Explanation | The provided element name was not valid when trying to register with automatic restart manager. |
Action | Verify that the element name was correct and does not exceed 16 characters. The element name must adhere to the rules listed under the description of the IXCARM ELEMENT parameter. For more information, see the IXCARM docs. |
Explanation | The angel was neither a started task nor a batch job, but specified a bind to the current batch job or started task. |
Action | Verify the caller was started before invoking the register to the automatic register service. For more information, see the IXCARM docs. |
Explanation | The angel used an element name that is already been registered with the automatic restart manager. Element names must be unique across a sysplex. |
Action | Check the list of element name that are already in use by issuing the IXCQUERY macro and request ARMSTATUS commands. For more information, see the IXCARM docs. |
Explanation | The angel tried to register in an address space that is used for another element. ARM rejects the registration because as part of restarting the related job or started task address space, ARM propagates resources related to the member from the previous instance of the member. |
Action | Ensure to register with ARM as soon as possible so the condition can be identified and check if the element name is not used anywhere in the sysplex. For more information, see the IXCARM docs. |
Explanation | The IXCARM service used for automatic restart manager failed. Please refer to the IXCARM docs for the return and reason codes explanation. |
Action | For more information, see the IXCARM docs. |
Explanation | The server could not register with the angel service because it was not a valid angel service. |
Action | Check the services defined in the com.ibm.ws.zos.core.angelRequiredServices for errors and make sure that the angel supports the service specified. |
Explanation | Reduce the number of angel required services specified in com.ibm.ws.zos.core.angelRequiredServices in bootstrap.properties. |
Action | Correct the server configuration in bootstrap.properties. |
Explanation | Either no angel process exists or one exists but the server could not connect to the angel process due to an error. |
Action | If the server does not require authorized services, then no action is required. If the server requires authorized services, start an angel process on this system so that this server can load its authorized code, and make the authorized services available. The message text includes an internal reason code to be used by product support. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The user ID which started this server does not have access to the BBG.ANGEL profile of the SAF server class. Read access to this profile is required to connect to the angel process. |
Action | If no authorized services are required by this server, then no action is required. If the server requires authorized services, give the user ID that starts the server read access to the BBG.ANGEL profile of the SAF server class. |
Explanation | The authorized service group named in the message has been loaded successfully. |
Action | No action is required. |
Explanation | The user ID that started this server does not have access to the appropriate profile in the SAF server class. The profile name is BBG.BBGZSAFM.<name> where <name> is the service group name in this message. |
Action | If this authorized service group is not required by this server, then no action is required. If the server requires services that are provided by this authorized service group, give the user ID that starts the server read access to the appropriate profiles in the SAF server class. |
Explanation | A portion of the z/OS native libraries for the application server could not be loaded. Unix system service BPX4LOD failed while trying to load the library indicated in the message. The return value, return code, and reason code returned by BPX4LOD are also indicated in the message. The return and reason codes are printed as hexadecimal integers. |
Action | Confirm that all installation steps were completed when installing the application server on this system. The return value, return code, and reason code can be looked up in "z/OS UNIX System Services Messages and Codes", publication number SA22-7807-xx. If the problem persists, contact your next level of support. |
Explanation | A z/OS native code library was not found in the file system. The library name is indicated in the message. |
Action | Confirm that all installation steps were completed when installing the application server on this system. If the problem persists, contact your next level of support. |
Explanation | One of the product identification strings could not be translated into EBCDIC to pass to the IFAUSAGE service. |
Action | Contact the owner of the product to get the identifying string(s) corrected. |
Explanation | The named product was registered with z/OS using the IFAUSAGE service. |
Action | No action is required. |
Explanation | The named product failed to register with z/OS using the IFAUSAGE service. Return codes greater than zero come from the IFAUSAGE service itself. Negative return codes indicate an internal problem processing the registration request. |
Action | A return code of eight (8) might indicate that the server is trying to register for too many products. To avoid this error, create and enable the server profile to access authorized services under the PRODMGR group, and start the angel process. The angel process must be started before the server is started. |
Explanation | Module bbgzsafm is not APF authorized. bbgzsafm must be APF authorized to enable access to authorized services. |
Action | If no authorized services are required by this server, then no action is required. If the server requires authorized services, APF authorize module bbgzsafm. See the extattr command in the "z/OS UNIX System Services Command Reference", publication number SA22-7802-xx. |
Explanation | The named product was deregistered from z/OS using the IFAUSAGE service. |
Action | No action is required. |
Explanation | The server will attempt to explicitly deregister all successfully registered products from z/OS during server shutdown. The z/OS service used to deregister products is IFAUSAGE. |
Action | No action is required. |
Explanation | All successfully registered products will be deregistered from z/OS when the address space terminates. If explicit product deregistration during server shutdown is needed, create and enable the server profile to access authorized services under group PRODMGR, and start the angel process. The angel process must be started before the server is started. |
Action | No action is required. |
Explanation | The named product failed to deregister from z/OS using the IFAUSAGE service. Return codes greater than zero come from the IFAUSAGE service itself. Negative return codes indicate an internal problem processing the deregistration request. |
Action | A return code of eight (8) indicates that the product was never registered first. |
Explanation | The user ID which that started this server does not have access to the BBG.AUTHMOD.BBGZSAFM profile of the SAF server class. Read access to this profile is required to connect to the angel process and load authorized services. |
Action | If no authorized services are required by this server, then no action is required. If the server requires authorized services, give the user ID that starts the server read access to the BBG.AUTHMOD.BBGZSAFM profile of the SAF server class. |
Explanation | The server is configured to abort startup when it is not registered with an angel process. The server is not registered with an angel process and is stopping. |
Action | Make sure that the angel process is started and that the server is able to connect to and register with it. Alternatively, change the configuration to allow the server to start without registering with an angel process. |
Explanation | Either no angel process with the name displayed in the message exists or one exists but the server could not connect to it due to an error. |
Action | If the server requires authorized services, start an angel process on this system so that this server can load its authorized code and make the authorized services available. The message text includes an internal reason code to be used by product support. If the problem persists, see the problem determination information on the following WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. If no authorized services are required by this server, then no action is required. To prevent this message from appearing, remove the com.ibm.ws.zos.core.angelName property from the bootstrap.properties file. |
Explanation | The user ID that started this server does not have access to the System Authorization Facility (SAF) profile for the angel process named in the message. Read access to that profile is required to connect to this angel process. |
Action | If the server requires authorized services, consult the documentation on how to set up a named angel. If no authorized services are required by this server, then no action is required. To prevent this message from appearing, remove the com.ibm.ws.zos.core.angelName property from the bootstrap.properties file. |
Explanation | The com.ibm.ws.zos.core.angelName property specifies the name of the angel process that this server should connect to. The property is specified in bootstrap.properties and must be 54 characters or less. |
Action | This server will not connect to an angel process. To connect to an angel process, specify a value of 54 characters or less for the com.ibm.ws.zos.core.angelName property, and restart the server. |
Explanation | The com.ibm.ws.zos.core.angelName property specifies the name of the angel process that this server should connect to. The property is specified in boostrap.properties, and can only contain characters from the following character set: A-Z 0-9 ! # $ + - / : < > = ? @ [ ] ^ _ ` { } | ~ |
Action | This server will not connect to an angel process. To connect to an angel process, specify a value using the supported character set for the com.ibm.ws.zos.core.angelName property, and restart the server. |
Explanation | The server process UMASK value. By default the UMASK value is inherited from the process that started the liberty server, but is then further modified to disallow any read, write, or execute access to OTHER users. Setting the WLP_SKIP_UMASK environment variable to true prevents the server from modifying the UMASK in this way. When a Liberty server is started using a z/OS procedure, you can customize the UMASK used by the server process by defining the WLP_SKIP_UMASK and the _BPX_BATCH_UMASK environment variables. WLP_SKIP_UMASK can be specified either in the server.env file or, if the server is started using a z/OS procedure, it can be specified using the STDENDV DD entry. In contrast, _BPX_BATCH_UMASK cannot be specified in the server.env file. It must only be specified using the STDENV DD entry in the z/OS procedure. |
Action | No action is required. |
Explanation | This server is connected to the configured angel process. |
Action | No action is required. |
Explanation | The server has the wrong configuration for angel's startup waiting time. The allowable range is from 0 to 300 seconds. |
Action | This server will use the default waiting time 0(s) to connect to the required Angel. To configure the valid startup waiting time, specify an integer value between 0 and 300 in the com.ibm.ws.zos.core.angelWaitTimeSeconds property, and restart the server. |
Explanation | This server requires the Angel to start, also has specified a maximum startup wait time until shutdown if it fails to register with the required Angel. |
Action | No action is required. |
Explanation | This message displays various values from the Local Data Area (LDA) control block, which can be useful for debugging an out-of-storage condition. The region size is the storage region that is allocated to the address space, indicated in kilobytes. The below and above the line limits are given in megabytes. The "LINE" is the boundary between 24-bit and 31-bit storage addresses. The limits indicate the actual storage limits for addresses that are below the line (24-bit addresses) and addresses that are above the line (31-bit addresses). |
Action | No action is required. |
Explanation | Displays the configured MEMLIMIT value for the address space in hexadecimal, and the MEMLIMIT configuration source. The MEMLIMIT CONFIGURATION SOURCE is one of the following values. "SMF" is either set by SMF in SMFPRMxx or set to 0 by default. "JCL" is set by the JCL. "REG0" indicates an unlimited size based on the REGION=0 specification. "USI" is configured by the IEFSMFIE field and set by using the IEFUSI exit. "OMVS" is set by the UNIX OMVS segment. "SETR" is set by the UNIX setrlimit. "SPW" is set by UNIX spawn. "SETO" is set by the UNIX SETOMVS command. "AUTH" is set by the authorized application modification."URG" is set in IEFSMFIE by the IEFUSI exit. "UNKNOWN" is set by unknown source. "BAD" indicates MEMLIMIT was not set due to an error. |
Action | No action is required. |
Explanation | The server has an expected value for the version of the angel process. The current version is earlier than the expected version. If a Liberty server instance connects to an angel that is running at an earlier service level, some features of the server might not be available. |
Action | To ensure that all features of the server are available to the angel process, update the angel to the latest version. |
Explanation | Displays the invalid angel service names that are passed as the value of the com.ibm.ws.zos.core.angelRequiredServices property from bootstrap.properties. |
Action | Correct the invalid values of the com.ibm.ws.zos.core.angelRequiredServices property. |
Explanation | The server will be registered to the angel with only the specified services passed in the com.ibm.ws.zos.core.angelRequiredServices property in the server bootstrap.properties file. |
Action | No action is required. |
Explanation | The server was configured with the property com.ibm.ws.zos.core.angelRequired=false and the property com.ibm.ws.zos.core.angelRequiredServices set to a valid list of angel services. The com.ibm.ws.zos.core.angelRequired property must be true to configure the server with a list of angel required services. |
Action | Change the server configuration to include the property com.ibm.ws.zos.core.angelRequired=true or remove the com.ibm.ws.zos.core.angelRequiredServices property. |
Explanation | A service specified in com.ibm.ws.zos.core.angelRequiredServices was not found in the list of services defined for the angel. |
Action | Correct the server configuration in bootstrap.properties. |
Explanation | Reduce the number of angel required services specified in com.ibm.ws.zos.core.angelRequiredServices in bootstrap.properties. |
Action | Correct the server configuration in bootstrap.properties. |
Explanation | While registering the server to the angel, the listed services were not authorized for use. |
Action | If this authorized service group is not required by this server, then no action is required. If the server requires services that are provided by this authorized service group, give the user ID that starts the server read access to the appropriate profiles in the SAF server class. |
Explanation | The server has driven a native method that encountered an out of memory condition. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | The server has driven a native method that called the referenced WLM service. The reason code from the WLM service indicates the reason for the failure. |
Action | Use the WLM reason code to determine the reason for the failure. |
Explanation | The server has driven a native method that called the referenced WLM service. The errno from the WLM service indicates the reason of the failure. |
Action | Use the errno value to determine the reason for the failure. |
Explanation | The server has driven a native method that failed. The target WebSphere Application Server service and return code are provided. The target WLM service with return and reason codes are also provided. |
Action | Use the return and reason codes to determine the reason for the failure. |
Explanation | The server has driven a native method to perform an authorized service call. It received a non-zero return code from the authorized Program Call (PC). |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | The server has driven a native method to perform an authorized service call. It successfully completed the native WLM service invocation, but failed to register the WLM Enclave in the native registry. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | The supplied token representing a WLM Enclave failed validation in the native registry. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | A native service needed to process the service call was not found. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | An attempt to drive a service call using the native service BPX4IPT failed. |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | The value supplied for collectionName attribute has exceeded the maximum of eighteen characters. The first eighteen characters will be used. |
Action | Update the server configuration to specify a correct value for the collectionName attribute. |
Explanation | The value supplied for collectionName attribute is either null or empty. |
Action | Update the server configuration to specify a value for the collectionName attribute. |
Explanation | A classification rule was specified containing a transaction class of greater than 8 characters. It has been truncated to be only 8 characters. |
Action | Update the associated classification rule to specify a correct value for the transactionClass attribute. |
Explanation | A classification rule was specified containing a resource string that uses too many consecutive wildcard characters. The specified resource string contains too many consecutive wildcard characters. (Up to two may be used consecutively) |
Action | Update the associated classification rule to specify a valid resource string by correcting the use of wildcarding. |
Explanation | A classification rule was specified containing a resource string that uses double wildcards. |
Action | Update the associated classification rule to specify a valid resource string by eliminating the use of double wildcards. |
Explanation | This message indicates that a new health factor is supplied to WLM for this server by using the IWM4HLTH API. |
Action | No action is required. |
Explanation | Failure to open the specified library. |
Action | =The message text includes a reason code which describes the specific error. See previous messages in the job log or system log for more information. |
Explanation | Method registration function failed. |
Action | =The message text includes a reason code which describes the specific error. See previous messages in the job log or system log for more information. |
Explanation | The registration of a native method failed. |
Action | =The message text includes a reason code which describes the specific error. See previous messages in the job log or system log for more information. |
Explanation | The de-registration of a native method failed. |
Action | =The message text includes a reason code which describes the specific error. See previous messages in the job log or system log for more information. |
Explanation | The specified dynamic link library failed to close. |
Action | =The message text includes a reason code which describes the specific error. See previous messages in the job log or system log for more information. |
Explanation | Unable to determine WLP_INSTALL_DIR. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to prepend NLS path to NLSPATH. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Unable to determine WLP_USER_DIR. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Unable to determine SERVER_CONFIG_DIR. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to resolve JAVA_HOME. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to prepend JVM library path to LIBPATH. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to prepend WebSphere library path to LIBPATH. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Unable to determine output directory. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to change working directory. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to open a file. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to resolve JNI_CreateJavaVM. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to create JavaVM. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Failed to invoke main class. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Path to user directory could not be extracted from the DD. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Real path of user directory could not be resolved from JCL. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Real path of user directory could be resolved from environment. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Server configuration directory does not exist. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Unable to stat() the server configuration directory. |
Action | See previous messages in the job log or system log for more information. |
Explanation | Server configuration does not exist. |
Action | See previous messages in the job log or system log for more information |
Explanation | Failed to stat . |
Action | See previous messages in the job log or system log for more information |
Explanation | The output directory could not be resolved or created. |
Action | See previous messages in the job log or system log for more information |
Explanation | The server output directory could not be resolved or created under WLP_OUTPUT_DIR. |
Action | See previous messages in the job log or system log for more information |
Explanation | Error reading from the indicated file. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to get environment file position. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to restore environment file position. |
Action | See previous messages in the job log or system log for more information |
Explanation | Failed to set environment from indicated property. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unsuccessful fgetpos. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unsuccessful fsetpos. |
Action | See previous messages in the job log or system log for more information |
Explanation | The JAVA_HOME location indicated does not exist. |
Action | See previous messages in the job log or system log for more information |
Explanation | Error reading java options from indicated file. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to set default IBM Java options. |
Action | See previous messages in the job log or system log for more information |
Explanation | Failed to load main class. |
Action | See previous messages in the job log or system log for more information |
Explanation | Failed to locate main method. |
Action | See previous messages in the job log or system log for more information |
Explanation | Failed to load java.lang.String class. |
Action | See previous messages in the job log or system log for more information |
Explanation | Failed to create main method's parameter list. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to set _BPXK_WLM_PROPAGATE=NO. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to set JAVA_THREAD_MODEL=HEAVY. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to set JAVA_PROPAGATE=NO. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to set default value for _EDC_PTHREAD_YIELD. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to set working directory. |
Action | See previous messages in the job log or system log for more information |
Explanation | Usage: bbgzsrv [liberty arguments] serverName. |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to redirect stdout to LOG_DIR |
Action | See previous messages in the job log or system log for more information |
Explanation | Unable to redirect stderr to LOG_DIR |
Action | See previous messages in the job log or system log for more information |
Explanation | Failed to set the server PID directory or PID file |
Action | See previous messages in the job log or system log for more information |
Explanation | When processing JVM_ARGS an unexpected EOF was encountered while processing `"' |
Action | See previous messages in the job log or system log for more information |
Explanation | The server is entering its final stage of shutdown processing. |
Action | No user action is required. For system automation, you can use this message as a trigger to indicate that the server is stopped. After this message, no further messages will be routed to the WTO (Write to operator) macro. |
Explanation | The DDName must be between 1 and 8 characters long. If the given name is not allowed, the default name of MSGLOG will be used. |
Action | Provide a message log DD name of a length that is between 1 and 8 characters. |
Explanation | The server has driven a native method that called the referenced Local Communication service. The reason code from the Local Communication service indicates the reason for the failure. |
Action | Use the Local Communication reason code to determine the reason for the failure. |
Explanation | The server has driven a native method that failed. The target WebSphere Application Server service and return code are provided. The target Local Communication service with return and reason codes are also provided. |
Action | Use the return and reason codes to determine the reason for the failure. |
Explanation | The server has driven a native method to perform an authorized service call. It received a non-zero return code from the authorized Program Call (PC). |
Action | Examine the server logs and runtime environment to determine the reason for the native code failure. |
Explanation | A local communication request was received with an unknown request type. The request will be ignored. |
Action | Enable native tracing to determine the cause for the unknown request type. |
Explanation | The local communication service is used to communicate with clients running on the same system as this server instance. The angel process must run at a minimum required level for the local communication service. The minimum required level is displayed in the message. |
Action | Examine the JCL that you used to start the angel process to see which directory it is being loaded from. The version of the product at that directory must be at the same PTF level, or higher, than the PTF level of this server instance. |
Explanation | First line response to a detailed registration listing command. |
Action | None |
Explanation | Second line response to a detailed registration listing command. |
Action | None |
Explanation | Third line response to a detailed registration listing command. |
Action | None |
Explanation | Header response for a tabulated registration listing command. |
Action | None |
Explanation | RGE row response for the tabulated command: MODIFY,DISPLAY,ADAPTER,RGE,* |
Action | None |
Explanation | Response to the command: MODIFY DISPLAY,ADAPTER,STATUS |
Action | None |
Explanation | Response to the command: MODIFY DISPLAY,ADAPTER,REGISTRATIONS |
Action | None |
Explanation | Response to the command: MODIFY DISPLAY,ADAPTER,GROUPRGES |
Action | None |
Explanation | Response to an unknown ADAPTER command or HELP command |
Action | None |
Explanation | Displays a command or search option and its description |
Action | None |
Explanation | Displays an error message for an invalid option or token |
Action | None |
Explanation | Displays an error for an invalid boolean value |
Action | None |
Explanation | Displays an error for an invalid numeric value |
Action | None |
Explanation | Displays an error for an invalid attribute name when searching |
Action | None |
Explanation | Displays an error for a search option with more than 1 = sign |
Action | None |
Explanation | Displays a header for list of valid search options and their types |
Action | None |
Explanation | Displays a search option and its type |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | A description for the STATUS command |
Action | None |
Explanation | An error message for the DISPLAY,ADAPTER,REGISTRATIONS,servername command |
Action | None |
Explanation | A message that is displayed for a detailed RGE view without any connection handle |
Action | None |
Explanation | A header for the tabular display of connection handles |
Action | None |
Explanation | A row of display of connection handles for a registration |
Action | None |
Explanation | A description for the DETAILS command |
Action | None |
Explanation | An updated RAR file for the Optimized Local Adapters (OLA) feature of WebSphere Application Server for z/OS has been supplied with this service pack. The version which is currently installed may not be compatible with this service pack. |
Action | Replace the Optimized Local Adapters (OLA) RAR file installed in this server instance with the one supplied by the currently installed service level of WebSphere Application Server for z/OS. Installation instructions can be found in the WebSphere Applicatin Server for z/OS Information Center. |
Explanation | WebSphere Application Server for z/OS is requesting transaction resynchronization with the Optimized Local Adapters registration name identified in the message. The resynchronization process did not complete due to an exception. |
Action | When resynchronizing with CICS, be sure that the Optimized Local Adapter link server corresponding to the registration name is started. Look in the WebSphere Application Server for z/OS logs and FFDC for an exception associated with this resynchronization operation. If the problem persists, contact your next level of support. |
Explanation | WebSphere Application Server for z/OS attempted to complete a two phase commit transaction, and encountered an error when communicating with an Optimized Local Adapters registration. This message may be supressed if repeated errors occur to the same registration. |
Action | Be sure that the Optimized Local Adapters registration named in the message is started. During resynchronization at server startup, this message does not necessarily indicate that a failure has occurred, due to the nature of the two phase commit and presume abort protocols. Check the WebSphere Application Server for z/OS logs and FFDC for details pertaining to the exception which caused this mesasge to be issued. The exception may contain the transaction XID identifying the specific transaction and operation which failed. If the problem persists, contact your next level of support. |
Explanation | Displays the XCF group ID and XCF server name used by OTMA for an IMS system which WebSphere Application Server for z/OS is connected to. Individual client names will follow using message CWWKB0383I. |
Action | None |
Explanation | Displays the WebSphere Application Server for z/OS server name and the OTMA client name that are used to connect to the IMS system identified by the preceeding CWWKB0382I message. |
Action | None |
Explanation | The OTMA name pool for this system has not been created yet and cannot be displayed by the display command. |
Action | None |
Explanation | A description for the OTMANAMES command. |
Action | None |
Explanation | Displays the maximum number of OTMA client name that WebSphere Application Server for z/OS can use to connect to each IMS system. |
Action | None |
Explanation | Displays the WebSphere Application Server for z/OS daemon group name that set the maximum number of OTMA client names. The OTMA client names can be used to see which IMS systems a WebSphere Application Server for z/OS instance is connected to. The time that the maximum number of OTMA client names was set, in STCK format, is also displayed. The maximum number of OTMA client names was displayed using message CWWKB0386I. |
Action | None |
Explanation | When the Optimized Local Adapters RAR is installed on a platform other than z/OS, it operates in proxy mode, communicating with a WebSphere Application Server for z/OS server which has the proxy EJB installed. When running in this mode, transactions are not supported. The resource adapter will ignore any transaction protocol messages it receives. |
Action | None. This message is issued the first time the resource adapter attemps to enlist in a transaction while in proxy mode. |
Explanation | An error was encountered while attempting to process a WebSphere Optimized Local Adapter (WOLA) remote work request on the remote Enterprise Java Bean target. |
Action | Verify that the Java Naming and Directory Interface (JNDI) name provided is correct. Verify that the Enterprise Java Bean target is within the scope that the caller can see and reach. Look in the WebSphere Application Server for z/OS logs and First Failure Data Capture (FFDC) for an exception associated with the remote Enterprise Java Bean call. |
Explanation | WebSphere Application Server for z/OS reported a failed WebSphere Optimized Local Adapters (WOLA) transaction resolution request in the CWWKB0381E message. This message contains the transactional identifier for the request that failed. |
Action | No action is required. The information in this message may be useful in resolving the failure reported in the CWWKB0381E message. |
Explanation | The requested registration name could not be found by the resource adapter. |
Action | Be sure the registration name was entered correctly, either in the ConnectionFactory properties, or in the ConnectionSpecImpl supplied on the getConnection request. |
Explanation | The OTMA Client name must be specified in the ConnectionSpec, or in the server.xml |
Action | Ensure that an OTMA Client name is set in the ConnectionSpec through ConnectionSpecImpl.setOTMAClientName(), or in the server.xml. |
Explanation | The OTMA Client name length must be between 1 and the length indicated in the message, and the Client name must be composed only of the characters A-Z, 0-9, @, #, or $ |
Action | Provide an OTMA Client name of a length that is within the limit and that uses only the permitted characters. |
Explanation | The OTMA Client name specified is the OTMA Client name that will be used. This could have come from the server.xml, the ConnectionSpec, or it could be the default value. |
Action | No action is required. |
Explanation | The indicated OTMA name length must be between 1 and the length specified in the message, and the name must be composed only of the characters A-Z, 0-9, @, #, or $ |
Action | Provide an OTMA name of a length that is within the limit and that uses only the permitted characters. |
Explanation | No value has been specified for either the OTMA Group name or, the OTMA Server name, or both. |
Action | Ensure that the OTMA Group name and OTMA Server name are specified on the ConnectionFactory, or in the ConnectionSpec. |
Explanation | The maximum receive message size configured is greater than the size of the message that can be handled by the max number of segments configured. Each segment can only carry 32k of data. |
Action | Review the configuration and make sure the maximum message length and the maximum number of segments are configured correctly. |
Explanation | The mentioned service is not registered with the OSGI framework. |
Action | Review the server logs for errors. |
Explanation | The specified service is not available to process work. |
Action | Review the server logs and configuration files for possible errors. |
Explanation | An attempt was made to process a service request. The service was not available. |
Action | Verify that the specified service was configured and that the service configuration contains all required attributes. Verify that the service name specified in the request URL matches the configured service name. Verify that the status of the service is STARTED. |
Explanation | The mentioned service encountered an error while processing a request. |
Action | Review service logs and HTTP response body for possible errors. |
Explanation | The asynchronous service request has timed out after the specified milliseconds. |
Action | Verify that the system is able to handle further requests and that the timeout is appropriate for the work being executed. |
Explanation | The named interceptor encountered an error. |
Action | Review service logs and the HTTP response body for possible errors. |
Explanation | The entity containing the user name associated with this request was not found. |
Action | Verify that security authentication was enabled on the system. |
Explanation | The user name associated with the request was not found. |
Action | Review service logs or security configuration for possible errors. |
Explanation | The named user is not authorized to perform the request. |
Action | Verify that the user is authorized to perform requests. |
Explanation | The specified schema could not be located. |
Action | Verify that the specified schema is present and the data transformation configuration is correct. |
Explanation | An error occurred while loading the specified data transformation file. |
Action | Verify that the transformation configuration files are valid and in the specified location. |
Explanation | The data transformation operation encountered an error. |
Action | Verify that the bind file is valid and the data transformation configuration is correct. |
Explanation | The user registry for the currently active realm was not found. |
Action | Verify that a user registry is configured and security is enabled. |
Explanation | A data transformer is not present to process data conversion. |
Action | Verify that a data transformer was configured and that an operation requiring transformation is not being called in error. |
Explanation | A response payload was previously set. Subsequent attempts to set the response are rejected. |
Action | Verify that the operation that sets the payload was not called in error more than once. |
Explanation | An unsupported action parameter value was specified. |
Action | Verify that a supported action is entered in the request URL. |
Explanation | The request payload is not in the expected JSON format. |
Action | Verify that a request payload is of the appropriate format. Review the service logs for more detailed error information. |
Explanation | An unsupported media type was specified. An media type of application/json is required. |
Action | Verify that a correct media type was set in the request. |
Explanation | A timeout or an error occurred that caused the complete method to be driven on the request's AsyncContext. |
Action | Verify that the timeout is appropriate for the work being executed. Review the service logs for more detailed error information. |
Explanation | The configured invokeURI attribute definition value does not contain a valid list of request URI strings. |
Action | Verify that the configured value contains valid request URI strings. If multiple URI entries are specified, they must be comma separated. |
Explanation | The specified entry under the invokeURI attribute definition is not a valid request URI String. |
Action | Verify that the configured entry represents valid request URI string. For instance, spaces representing a request URI or empty request URIs are not allowed. |
Explanation | The configured invokeURI attribute entry for the mentioned service does not conform with the supported usage of the wildcard character. |
Action | Verify that the configured entry conforms with the documented usage of the wildcard character. |
Explanation | The specified entry is already assigned to another service. |
Action | Verify that invokeURI entries representing valid request URI strings are unique for this installation. |
Explanation | The properties supplied with the service registration do not contain a valid name for the service. |
Action | Verify that the code used to register the service includes a service name as part of the registration call. Empty service names are not allowed. |
Explanation | The name specified as part of the service registration is already associated with an existing service. |
Action | Use a unique name for the service being registered. All services registered with the z/OS Connect framework must have a unique service name. |
Explanation | The configured response schema file location was not specified. The response schema file location is set to match the configured request schema location. |
Action | Verify that a response schema file location was specified and has a valid value. |
Explanation | The SSL port could not be determined, which prevented the incoming HTTP request from being redirected to the HTTPS port. This could happen if there is a configuration error in the keyStore element or if the SSL feature is missing. |
Action | Verify that you have the correct SSL information in server.xml file. |
Explanation | The servlet request URL is malformed, which prevented the incoming HTTP request from being redirected to the HTTPS port. |
Action | Verify that the servlet request URL is correct. |
Explanation | The z/OS Connect bundle context could not be found. |
Action | Verify that the Liberty server is not in the process of shutting down. |
Explanation | A service stop request was previously issued. Any subsequent work requests are rejected. |
Action | Issue a service start request to restart the service. |
Explanation | An error was detected during the processing a WOLA service request. The request may have completed. |
Action | Review service logs and the HTTP response body for more information. |
Explanation | An error occurred after the WOLA service request completed. |
Action | Review service logs and the HTTP response body for more information. Verify that service request actions that took place are in a consistent state. |
Explanation | The execution of the mentioned WOLA target service did not complete successfully. |
Action | Review service logs and the HTTP response body for more information. |
Explanation | The Liberty profile server registered the WebSphere Optimized Local Adapter. Calls can now be made between native-language applications and the local Liberty profile server environment. |
Action | No action is required. |
Explanation | The z/OS security subsystem converts lowercase characters to upper case, which can cause a mismatch with your configuration. |
Action | Do not use lowercase characters in the values for wolaGroup, wolaName2, and wolaName3 in the zosLocalAdapters configuration. For more information about naming conventions, see the System Authorization Facility (SAF) documentation. |
Explanation | The Liberty server was unable to use the name specified in the zosLocalAdapters configuration for registering WebSphere optimized local adapters. This name might be in use by another Liberty server. |
Action | Check your environment to make sure that no other Liberty servers are using the same zosLocalAdapters configuration as the one on this server. |
Explanation | An error occurred while parsing an OTMA Response Message that is received from IMS. The size indicated in the header does not match the actual size of the message data. |
Action | Check the application and ensure it is generating valid OTMA format messages. |
Explanation | An error occurred while parsing and OTMA response message received from IMS. The size indicated in the header does not match the actual size of the message data. |
Action | Check the application and ensure the message segment header lengths that are specified match the length of the message data. |
Explanation | An error occurred while parsing an OTMA Request Message. Either the message length that is specified in the message segment header is greater than 32768 or it is less than the minimum length. |
Action | Check the application and ensure the message header lengths that are specified are valid. Also make sure the OTMA response message length equals the total number of bytes that is specified in the header lengths |
Explanation | An error occurred while parsing an OTMA Request Message. The length specified in the segment header is greater than the number of bytes that are left in the data buffer. |
Action | Check the application and ensure the message header lengths that are specified are valid. Also make sure the OTMA response message length equals the total number of bytes specified in the header lengths |
Explanation | The header specified for the response segment is larger than the number of bytes left in the message buffer. |
Action | Check the application to ensure the header message lengths match the buffer size. |
Explanation | The header specified for the response segment is larger than the number of bytes left in the message buffer. |
Action | Check the application to ensure the header message lengths match the buffer size. |
Explanation | The number of request segments is larger than the currently configured maximum allowed number of segments. |
Action | Check the configuration of the connection specification and ensure the maximum number of segments is set correctly. |
Explanation | The number of response segments is larger than the currently configured maximum allowed number of segments. IMS sends back the maximum number of segments and concatenates in the final segment those response segments that exceed the maximum allowed. |
Action | Check the configuration of the connection specification and ensure the maximum number of segments is set correctly. |
Explanation | There are more than 500 registrations in the WOLA group. The number of registrations is displayed in the message. |
Action | No action is required. |
Explanation | The configured password is invalid. If the specified configuration value is an encoded string, the encoding does not comply with the WebSphere Liberty profile supported encoding standards. |
Action | Verify that the configured password is valid. If the password needs encoding use the securityUtility shipped with WebSphere Liberty profile. |
Explanation | Unable to determine the path where the logs will be written because the logPath attribute was not configured and the environment property ${server.output.dir} was not set. |
Action | Configure a valid log path name in the server.xml file or set environment variable ${server.output.dir}. |
Explanation | The context propagation service for asynchronous servlets is shutting down because the WLM feature, the servlet feature, or both features are not available. |
Action | Verify that the WLM feature, the servlet feature, or both features were not removed from the configuration file while work was still in progress. |
Explanation | The value of the mentioned configured transactionClass attribute under configuration element mdbClassification was truncated to be the maximum allowed length of characters. Note that if the shown activation specification is a wildcard, it was either specified as such or it was not specified and the default value is being used. |
Action | Verify that the transactionClass attribute under the mdbClassification configuration element contains a value that does not exceed the maximum length. |
Explanation | The value of the mentioned configured jmsActivationSpec attribute under configuration element mdbClassification cannot be an empty string or a sequence of spaces. Note that if the shown transaction class is an empty string, it was either specified as such or it was not specified and the default value is being used. |
Action | Verify that the jmsActivationSpec attribute under the mdbClassification configuration element contains a valid value. |
Explanation | Automatic restart manager cannot be dynamically enabled after the server has started. |
Action | To register the server, enable the zosAutomaticRestartManager-1.0 feature and restart the server. |
Explanation | The server is registered with the automatic restart manager. Any abrupt shutdown automatically restarts this server. |
Action | None. |
Explanation | The server successfully registered with the automatic restart manager on restart. Any abrupt shutdown automatically restarts this server. |
Action | None. |
Explanation | The provided element name is not valid according to the rules for the 'element' parameter of the automatic restart manager. |
Action | Verify that the element name is correct and does not exceed 16 characters. The element name must adhere to the rules that are listed under the description of the 'element' parameter. |
Explanation | The server was not recognized as a started task but specified a bind to the current started task. |
Action | Verify that the server was started before invoking the register to the automatic register manager. |
Explanation | The issuer of the IXCARM macro does not have the required SAF authorization. The SAF authorization is required to for the IXCARM profile to invoke the automatic restart manager services. |
Action | Verify that the server has the correct authorization for the IXCARM profile in SAF FACILITY class. For more information, see the IXCARM documentation. |
Explanation | The server specified an element name that is already registered with the automatic restart manager. Element names must be unique across a sysplex. |
Action | Check the list of element names that are already in use by issuing the IXCQUERY macro and request ARMSTATUS commands. Specify an element name that is not already in use. |
Explanation | The server tried to register in an address space that is used for another element. ARM rejects the registration because the necessary resources are already propagated to another element. |
Action | Ensure that the element that is used to register with ARM is not used anywhere else in the sysplex. |
Explanation | The SAF entity was not defined during an attempt to register with the auto restart manger. Problem state and problem key users must have a security profile to use IXCARM. |
Action | Ensure that the IXCARM.elemtype.elemname SAF entity for the unauthorized application is defined correctly. |
Explanation | The IXCARM service that was used for automatic restart manager failed. See the IXCARM docs for explanations of the return and reason codes. |
Action | For more information, see the IXCARM docs. |
Explanation | The z/OS AES encryption key must come only from an RACF keystore. |
Action | Make sure that the keystore that is specified is an RACF keystore type. |
Explanation | The certificate does not exist in the keystore. Specify a certificate with a key entry for AES password encryption. |
Action | Make sure that the certificate that is specified exists in the keystore. |
Explanation | The certificate specified is not a key entry. The certificate must be a key entry to be used as an AES password encryption key. |
Action | Make sure the certificate specified is a key entry. |
Explanation | The certificate that is specified is expired. The key that is associated with the certificate cannot be used as an AES password encryption key. |
Action | Make sure that the certificate that is specified is valid and a key entry. |
Explanation | The keystore that is specified does not exist. No key entry can be retrieved to use as the AES password encryption key. |
Action | Make sure that the keystore and key entry exist. |
Explanation | The SAF key ring cannot be loaded. Check whether you have the correct permissions to access the key ring and that the correct key ring type is being used. |
Action | Make sure that the key ring exists and the correct key ring type is specified. |
Explanation | The private key from the SAF key ring cannot be retrieved. Check whether you have the correct permissions to access the private key. |
Action | Make sure that the SAF key ring exists and the correct SAF key ring type is specified. |
Explanation | Information for users about the key to use as the AES password encryption key. |
Action | No user action. |
Explanation | Failed to prepend JVM JAVA_HOME/lib/j9vm library path to LIBPATH. |
Action | For more information, see messages in the job log or system log. |
Explanation | Failed to prepend JVM JAVA_HOME/lib library path to LIBPATH. |
Action | For more information, see messages in the job log or system log. |
Explanation | Tracing provides information that is useful when debugging a problem. Tracing was requested when this registration or link server was started. |
Action | No user action is required. |
Explanation | Tracing provides information that is useful when debugging a problem. Tracing was requested when this registration or link server was started. |
Action | No user action is required. |
Explanation | Tracing provides information that is useful when debugging a problem. Tracing was requested when this registration or link server was started. |
Action | No user action is required. |
Explanation | The EXEC CICS START TRUE command for the BBOATRUE program did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information about why TRUE could not be enabled. Verify that program BBOATRUE is found in a dataset in the CICS DFHRPL. |
Explanation | The EXEC CICS EXTRACT TRUE command for the BBOATRUE program did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information about why information about TRUE could not be extracted. |
Explanation | The EXEC CICS DISABLE TRUE command for the BBOATRUE program did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information about why TRUE could not be disabled. |
Explanation | The control transaction (BBOC) request cannot be processed because the BBOATRUE is not active.The BBOC request cannot be processed since the BBOATRUE is not active. |
Action | Start BBOATRUE by running the BBOC START_TRUE command, and issue the control transaction (BBOC) request again. |
Explanation | A WOLA group name must be 8 character or less. The control transaction (BBOC) request cannot be processed using the input WOLA group name. |
Action | Shorten the WOLA group name, and issue the control transaction (BBOC) request again. |
Explanation | The second part of the WOLA name must be 8 character or less. The control transaction (BBOC) request cannot be processed using the input WOLA name. |
Action | Shorten the second part of the WOLA name, and issue the control transaction (BBOC) request again. |
Explanation | The third part of the WOLA name must be 8 character or less. The control transaction (BBOC) request cannot be processed using the input WOLA name. |
Action | Shorten the third part of the WOLA name, and issue the control transaction (BBOC) request again. |
Explanation | The minimum connections value, which is specified on the BBOC MNC parameter, must be 9999 or less. |
Action | Specify a value of 9999 or less for the BBOC MNC parameter, and issue the control transaction (BBOC) request again. |
Explanation | The maximum connections value, which is specified on the BBOC MXC parameter, must be 9999 or less. |
Action | Specify a value of 9999 or less for the BBOC MXC parameter, and issue the control transaction (BBOC) request again. |
Explanation | The parameter that specifies the behavior of the control transaction, BBOC TXN, was not set to a valid value. |
Action | Set the value of the BBOC TXN parameter to Y or N, and issue the control transaction (BBOC) request again. For more information about specifying the TXN parameter, see the documentation about the BBOC transaction. |
Explanation | The BBOC UNREGISTER command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The parameter that specifies the security propagation, BBOC SEC, was not set to a valid value. |
Action | Set the value of the BBOC SEC parameter to Y or N, and issue the control transaction (BBOC) request again. For more information about specifying the SEC parameter, see the documentation about the BBOC transaction. |
Explanation | The Liberty profile server modules under CICS are routed to the BBOQ extra partition transient data queue (TDQ). This queue can be renamed, and the name is reflected in the message. |
Action | Ensure that the BBOQ TDQ is defined to CICS. For more information, see the BBOACSD definition sample file for BBOQ and the CICS documentation. |
Explanation | The BBOC REGISTER command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The default link server that connects the Liberty profile server with the CICS region was not registered. |
Action | Verify that the target Liberty profile server is available. See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The register name must be 12 characters or less. |
Action | Shorten the register name, and issue the control transaction (BBOC) request again. |
Explanation | The service name must be 8 characters or less. |
Action | Shorten the service name, and issue the control transaction (BBOC) request again. |
Explanation | The link server was not started because BBOC START_SRVR did not successfully call the Register API. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBOC REGISTER command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The name of the server task transaction, which is specified on the STX parameter, must be 4 characters or less. |
Action | Shorten the name of the server task transaction, and issue the control transaction (BBOC) request again. |
Explanation | The name of the link task transaction, which is specified on the LTX parameter, must be 4 characters or less. |
Action | Shorten the name of the link task transaction, and issue the control transaction (BBOC) request again. |
Explanation | The BBOC START_SRVR command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The link server was not stopped because BBOC STOP_SRVR did not successfully call the Unregister API. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The name of the transient data queue, which is specified on the TDQ parameter, must be 4 characters or less. |
Action | Shorten the name of the transient data queue, and issue the control transaction (BBOC) request again. |
Explanation | The TRC parameter specifies the level of tracing for BBOC commands, and it was not set to a valid value. |
Action | Specify a valid value for the TRC parameter, and issue the control transaction (BBOC) request again. For information about supported values, see the documentation about the BBOC transaction. |
Explanation | The LSYNC parameter specifies whether the link server synchronizes with CICS when the server links with a CICS program. Supported values are Y to synchronize or N to not synchronize. |
Action | Specify Y or N for the LSYNC parameter, and issue the control transaction (BBOC) request again. |
Explanation | The LSYNC and TXN parameters both control how CICS synchronizes updates when the target program returns. Setting LSYNC=Y causes an EXEC CICS SYNCPOINT operation when the target program returns. Setting TXN=Y delays the EXEC CICS SYNCPOINT until a commit signal is received from the Liberty server instance. Setting both of these values to Y causes a conflict when EXEC CICS SYNCPOINT is issued. |
Action | Change the value of LSYNC or TXN, and issue the control transaction (BBOC) request again. |
Explanation | The register name, which is specified on the RGN parameter, must be 12 characters or less. |
Action | Shorten the register name, and issue the control transaction (BBOC) request again. |
Explanation | The BBOC command contained an operation name that is not supported. |
Action | Change the operation name to a supported value, and issue the control transaction (BBOC) request again. For a list of supported operation names, see the documentation about the BBOC transaction. |
Explanation | The BBOC START_TRUE command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBOC STOP_TRUE command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBOC START_SRVR command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBOC REGISTER command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBOC UNREGISTER command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The XTR parameter specifies whether system-level tracing is enabled for BBOC commands. Supported values are Y to enable tracing and N to disable tracing. |
Action | Specify a valid value for the XTR parameter, and issue the control transaction (BBOC) request again. |
Explanation | The EXEC CICS START command for the specified link server transaction was not issued successfully. |
Action | See the CICS documentation for the meanings of EIBRESP and EIBRESP2 values for CICS START transactions. |
Explanation | The parameter must be specified when you issue the control transaction (BBOC) request. |
Action | Specify the parameter, and issue the control transaction (BBOC) request again. |
Explanation | The reuse length, which is specified on the REUC parameter, must be 4 characters or less. |
Action | Shorten the reuse length, and issue the control transaction (BBOC) request again. |
Explanation | Storage was not available to create the control blocks necessary to start the requested link server. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. Issue the control transaction (BBOC) request again. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The REU parameter specifies whether the link server reuses the program link invocation tasks (BBO# transactions). Supported values are Y to enable reuse and N to disable reuse. |
Action | Specify a valid value for the REU parameter, and issue the control transaction (BBOC) request again. |
Explanation | The REUC parameter specifies the number of requests for which CICS link invocation task (BBO#) remains active and is reused. The parameter must be 8 digits or less. |
Action | Specify a numeric value of 8 digits or less for the REUC parameter, and issue the control transaction (BBOC) request again. |
Explanation | The REUT parameter specifies the number of seconds for which CICS link invocation task (BBO#) remains active and is reused. The parameter must be 8 digits or less. |
Action | Specify a numeric value of 8 digits or less for the REUT parameter, and issue the control transaction (BBOC) request again. |
Explanation | The link server issued the EXEC CICS INQUIRE TDQUEUE() API to determine the default record size of the BBOQ queue. However, an error occurred and produced the response codes that were received for the specified queue name. |
Action | Verify that the named queue exists and that the user ID that started the link server has the authority to invoke the EXEC CICS INQUIRE TDQUEUE() API. Messages will continue to be written to this queue using the default queue record length. If your queue record length is larger than the default, some messages might be truncated at the default length. |
Explanation | The start server command completed with warnings. |
Action | See the BBOOUT DD in the CICS log file for warning messages that indicate conflicting parameters in the start server command. |
Explanation | The specified parameter was not passed and is set to the default value. |
Action | The processing of the parameter continues. |
Explanation | The BBOC START_SRVR transaction was requested with the SEC(Y) and REU(Y) parameters. |
Action | The reuse option, REU(Y), is not supported when the security parameter, SEC(Y) is specified. The REU parameter is set to no and processing continues. |
Explanation | When a BBOC STOP_SRVR command is processed, the BBO$ transaction ends. |
Action | No user action is required. |
Explanation | When a BBOC STOP_SRVR command is processed, the BBO$ transaction and all related BBO# transactions are stopped. |
Action | No user action is required. |
Explanation | The communication with the Liberty profile server instance that is indicated in the message has been lost. |
Action | Ensure that the Liberty profile server instance is running. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | Communication with the Liberty profile server instance is re-established. |
Action | No user action is required. |
Explanation | An error was encountered while receiving a request from the Liberty profile server. |
Action | See the product documentation to find the specified return code and reason code for the BBOA1RCA API, and take the recommended action. |
Explanation | The BBOA1RCA API receive request message is returned with non-zero return and reason code. |
Action | See the product documentation to find the specified return code and reason code for the BBOA1RCA API, and take the recommended action. See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information about this error. |
Explanation | An exception occurred while the optimized local adapters link server was running. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information about why the link server might have stopped. |
Explanation | The BBOA1GET Get Message Data API request was returned with a non-zero return and reason code. |
Action | See the product documentation to find the specified return code and reason code for the BBOA1GET API, and take the recommended action. See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The system could not retrieve the message context data. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBOA1SRX send exception response request was returned with non-zero return and reason code. |
Action | See the product documentation to find the specified return code and reason code for the BBOA1SRX API, and take the recommended action. See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBOA1CNR release connection request was returned with a non-zero return and reason code. |
Action | See the product documentation to find the specified return code and reason code for the BBOA1CNR API, and take the recommended action. See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The system is unable to start the EXEC CICS START checking for specified link transaction identifier. |
Action | See the product documentation for CICS to find the specified EIBRESP and EIBRESP2 values for the EXEC CICS START TRANSACTION command, and take the recommended action. |
Explanation | The propagation of a link transaction ID into CICS from a Liberty profile server is not supported while running the link server with the REU=Y option. This error is written to the BBOQ log and sent as an exception back to the caller in the Liberty profile server. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBO# transaction terminates when the BBOC STOP_SRVR command is issued. |
Action | No user action is required. |
Explanation | When a BBOC STOP_SRVR command is processed, the BBO# transaction ends. |
Action | No user action is required. |
Explanation | The link server received a request that includes a transaction context. This version of CICS does not support transaction propagation over optimized local adapters. |
Action | To propagate transactions to CICS Transaction Server using optimized local adapters, use version 4.1 or higher of CICS Transaction Server for z/OS. |
Explanation | The link server cannot determine the version of CICS Transaction Server for z/OS. |
Action | Verify that you are using a supported version of CICS Transaction Server for z/OS. |
Explanation | The link server unsuccessfully attempted to invoke the EXEC CICS INQURE SYSTEM CICSTSLEVEL API. |
Action | Verify that the user running the link server has the authority to invoke the INQUIRE SYSTEM CICSTSLEVEL API. |
Explanation | The link server unsuccessfully attempted to invoke the EXEC CICS INQUIRE UOWLINK START command. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | After resolving an in-doubt UOW failure, the link server attempted to delete the UOWLINK that it created to record its interest in the UOW. The UOWLINK was not found because it has already been deleted. |
Action | No user action is required. |
Explanation | After resolving an in-doubt UOW failure, the link server attempted to delete the UOWLINK that it created to record its interest in the UOW. The error occurred when the EXEC CICS SET UOWLINK() DELETE API was invoked. |
Action | Make sure that the user running the link server has the authority to invoke the EXEC CICS SET UOWLINK() DELETE API. Verify that the UOWLINK specified in the message has been deleted. |
Explanation | After resolving an in-doubt UOW failure, the link server attempted to find the UOWLINK that it created to record its interest in the UOW. The error occurred when the EXEC CICS INQUIRE UOWLINK() NEXT API was invoked. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The link server was attempting to resolve an in-doubt UOW that corresponds to an XID that was received from the Liberty profile server. An error was encountered while iterating the UOWs using the EXEC CICS INQUIRE UOW() NEXT API. |
Action | The operation will be retried. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The system attempted to resolve an in-doubt UOW that is in the wrong state. |
Action | The operation will be retried. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An attempt was made to commit or back out an in-doubt UOW using the EXEC CICS SET UOW() API, but an error code was received. |
Action | The operation will be retried. Make sure that the user running the link server has the authority to invoke the EXEC CICS SET UOW() API. |
Explanation | The Liberty profile server instance requested a list of in-doubt XIDs from CICS Transaction Server for z/OS. The link server tried to obtain storage to hold the XIDs, but an error occurred when the EXEC CICS GETMAIN API was invoked. |
Action | The number of XIDs to be returned is listed in the message. The amount of storage to return a single XID is about 140 bytes. Calculate the amount of storage required and ensure that much storage is available in the CICS Transaction Server address space, and available to the link server transaction. |
Explanation | The Liberty profile server instance requested a list of in-doubt XIDs from CICS Transaction Server from z/OS. An error code was received when the EXEC CICS INQUIRE UOWLINK NEXT API was used to iterate unit of work link (UOWLINK) objects. |
Action | The operation will be retried. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The Liberty profile server instance requested a list of in-doubt XIDs from CICS Transaction Server for z/OS. An error code was received when the EXEC CICS INQUIRE UOW() API inquired to get information about a UOW. |
Action | The operation will be retried. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The Liberty profile server instance requested a list of in-doubt XIDs from CICS Transaction Server for z/OS. An error code was receive when the EXEC CICS GETMAIN API attempted to build the list of XIDs. |
Action | The operation will be retried. The amount of storage required by this call is about 144 bytes. Make sure that this much storage is available to the link server. |
Explanation | The version of the link server and link tasks are different. |
Action | Be sure that the link task (BBOACLNK) and link server (BBOACSRV) were both obtained from the same version of the Liberty profile server. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | A request was read by the link task which contains a transaction XID. The TID within the XID is longer than the maximum length allowable by CICS Transaction Server for z/OS. The length (in bytes) of the TID is displayed in the message. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | A communication error occurred while communicating with the Liberty profile server instance. The link server task will end. |
Action | Ensure that the Liberty profile server instance used by this link task is running. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | A request to commit a UOW was received from the Liberty profile server. When directing CICS to perform the commit operation, the operation failed. The UOW will be backed out. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS received a request from the Liberty profile server to prepare a unit of work (UOW). When the Liberty profile server directed CICS to perform the prepare operation, a return and reason code was received. The link task will abend, and the UOW will be backed out. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The transaction received new work for a unit of work (UOW) after the UOW was prepared, so the work could not be added to the transaction. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS received a request from the Liberty profile server to prepare a unit of work (UOW). When the Liberty profile server directed CICS to perform the prepare operation, a return code reported a heuristic commit or backout. The most likely cause of this error is that one of the resource managers involved in the UOW committed or backed out its resources before it received the prepare message. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS received a request from the Liberty profile server to prepare a unit of work (UOW). When the Liberty profile server directed CICS to perform the prepare operation, a return code indicated that CICS backed out the UOW. The most likely cause of this error is that one of the resource managers could not perform its updates and backed out. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS received a request from the Liberty profile server to back out a unit of work (UOW). The unit of work was not successfully backed out because of the cause stated in the return and reason codes. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS received a request from the Liberty profile server to commit a unit of work (UOW), but the UOW could not be committed. The most likely cause of this problem is that one of the resource managers that is participating in the UOW was not able to commit its updates. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The link server task (BBO#) was processing a unit of work (UOW) in a global transaction, but the task received a request that was not part of that global transaction. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS did not successfully add data to the specified container in the IBM-WAS-ADAPTER channel. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the CICS documentation for the meanings of EIBRESP and EIBRESP2 values. |
Explanation | CICS did not retrieve the length of the data in the specified container in the IBM-WAS-ADAPTER channel. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the CICS documentation for the meanings of EIBRESP and EIBRESP2 values. |
Explanation | CICS did not allocate storage for a response buffer of the specified size. |
Action | Verify that the CICS EDSALIM parameter is larger than the specified response buffer size. The EDSALIM parameter specifies the maximum amount of storage in which CICS allocates the extended dynamic storage areas (EDSAs). See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | CICS did not free storage for a response buffer of the specified size. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | CICS did not free storage for a response buffer of the specified size at the specified address. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the CICS documentation for the meanings of EIBRESP and EIBRESP2 values. |
Explanation | CICS did not free storage for the reasons specified by the EIBRESP and EIBRESP2 response codes. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the CICS documentation for the meanings of EIBRESP and EIBRESP2 values. |
Explanation | CICS received a request from the Liberty profile server to commit or back out a unit of work (UOW), but the operation was not processed because the UOW was not in the correct state to process the request. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The link task (BBO#) was processing requests for a unit of work (UOW) that is participating in a global transaction. The UOW received a request that was participating in a different global transaction, so the link task cannot process the request. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The link task attempted to retrieve a list of containers that are contained in the channel that was used to process the target service name. During this attempt, the EXEC CICS STARTBROWSE CONTAINER command did not run successfully for the reasons specified by the EIBRESP and EIBRESP2 response codes. |
Action | Verify that the target service uses the correct channel name to store its output. See the CICS documentation for the meanings of EIBRESP and EIBRESP2 values. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS did not allocate storage for the reasons specified by the EIBRESP and EIBRESP2 response codes. |
Action | See the CICS documentation for the meanings of EIBRESP and EIBRESP2 values. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS did not allocate storage for a request buffer of the specified size. |
Action | Verify that the CICS EDSALIM parameter is larger than the specified request buffer size. The EDSALIM parameter specifies the maximum amount of storage in which CICS allocates the extended dynamic storage areas (EDSAs). See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | CICS did not return the container names on the channel used to store the output of the target service for the reasons specified by the EIBRESP and EIBRESP2 response codes. |
Action | Verify that the target service is using the correct channel name to store its output. See the CICS documentation for the meanings of EIBRESP and EIBRESP2 values. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The link task (BBO#) received the next request in the global transaction that is currently running, but it did not get the context data associated with the request. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The link task (BBO#) received a request that requires a global transaction, but CICS could not import the global transaction for the reasons specified by the EIBRESP and EIBRESP2 response codes. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The Send Response Exception API, BBOA1SRX, was unable to send an error response to the Liberty profile server for the reasons specified by the return and reason codes. |
Action | Verify that the Liberty profile server is available. See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the optimized local adapters API documentation for the meanings of BBOA1SRX return and reason codes. |
Explanation | The Get Data Request API, BBOA1GET, was unable to copy the message data for the reasons specified by the return and reason codes. |
Action | Verify that the Liberty profile server is available. See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the optimized local adapters API documentation for the meanings of BBOA1GET return and reason codes. |
Explanation | CICS did not successfully write data to the specified temporary storage queue that is in main storage. |
Action | See the CICS documentation for the meanings of the EIBRESP and EIBRESP2 values. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS did not successfully link from the link server program in the CICS region to the program that the client requested. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the CICS documentation for the meanings of the EIBRESP and EIBRESP2 values. |
Explanation | The Connection Release API, BBOA1CNR, was unable request that the connection be returned for the reasons specified by the return and reason codes. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the optimized local adapters API documentation for the meanings of BBOA1CNR return and reason codes. |
Explanation | The optimized local adapters link server encountered a problem when it was running that caused it to stop. The Liberty profile server will not be able to send requests using this registration name until the link server is restarted. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. The link server can be restarted using the BBOC transaction. |
Explanation | The Receive Request Specific API, BBOA1RCS, was unable to receive a request from the Liberty profile server for the reasons specified by the return and reason codes. The link count is the number of programs that the link task ran since it started. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the optimized local adapters API documentation for the meanings of BBOA1RCS return and reason codes. |
Explanation | This message provides the CICS unit of work (UOW) ID for the transaction reported in message CWWKB8072. |
Action | No user action is required. |
Explanation | This message provides the global transaction identifier (GTRID) portion of the transaction ID (XID) for the transaction reported in message CWWKB8072. The XID is used to retrieve transaction information from the Liberty profile server and CICS. This message might be repeated multiple times if the value is too large to print on one line. |
Action | No user action is required. |
Explanation | CICS did not retrieve data from the specified container in the IBM-WAS-ADAPTER channel for the reasons specified by the EIBRESP and EIBRESP2 codes. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the CICS documentation for the meanings of the EIBRESP and EIBRESP2 values. |
Explanation | CICS did not delete the specified container in the IBM-WAS-ADAPTER channel for the reasons specified by the EIBRESP and EIBRESP2 codes. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the CICS documentation for the meanings of the EIBRESP and EIBRESP2 values. |
Explanation | The length of the value that the link server generated for the UOW parameter is not supported. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS did not run the RESYNC command successfully because the link server did not generate a value for the UOW parameter. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The UOW parameter must contain a hexidecimal string. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CICS did not determine whether the units of work that are in doubt were committed or backed out. |
Action | See the CICS documentation for the meaning of the response code. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The register name, which is specified on the REG parameter, was not specified in the control transaction (BBOC). The default registration name was used to register the connection. The default registration name is the CICS APPLID, which is printed in the message text. |
Action | If the REG parameter was omitted by mistake, re-issue the BBOC transaction with the REG parameter specified. You will need to manually unregister the registration that was made under the default register name. |
Explanation | The link server invoked the EXEC CICS INQUIRE SYSTEM JOBNAME API to determine the job name for the CICS region where the link server is running, but the command did not run successfully. |
Action | Verify that the user ID that started the link server has the authority to invoke the EXEC CICS INQUIRE SYSTEM API. See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. See the CICS documentation for the meanings of the EIBRESP value. |
Explanation | The BBOC control transaction received a LIST_SRVR command. The link servers for the specified job name will be logged in the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region. |
Action | No user action is required. |
Explanation | The BBOC control transaction received a LIST_SRVR command for the specified job name. No link servers are currently running in the specified job name. |
Action | If you expected to see a link server listed at the time the BBOC LIST_SRVR command was issued, see the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for messages indicating why a link server might have stopped. |
Explanation | The Get Connection Pool Information function did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The BBOC control transaction received a LIST_SRVR command for the specified job name and registration name. No link servers with the specified registration name are currently running in the specified job name. |
Action | If you expected to see a link server listed at the time the BBOC LIST_SRVR command was issued, see the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for messages indicating why a link server may have stopped. |
Explanation | The task-related user exit (TRUE) detected that a transaction was incomplete and required resolution. The BBOACNTL program was scheduled to resolve the transaction, but it did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for messages indicating why the transaction could not be resolved. If the problem persists, see the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The LTSQ parameter specifies the name of the temporary storage queue where the BBOC LIST_SRVR command writes its output. The parameter must be 8 characters or less. |
Action | Shorten the length of the LTSQ parameter, and issue the control transaction (BBOC) request again. |
Explanation | The BBOC LIST_SRVR command did not run successfully. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The specified CICS EXEC function did not complete successfully. |
Action | Refer to the CICS error codes in the CICS documentation to determine the corrective action. |
Explanation | The BBOC RTXP parameter must be Yes (Y) or No (N). |
Action | Re-submit the request with a valid RTXP option. |
Explanation | The BBOC RTX parameter must specify a valid CICS transaction ID. |
Action | Re-submit the request with a valid RTX parameter. |
Explanation | The BBOC RTXSYS parameter must specify a valid CICS remote SYSID. |
Action | Re-submit the request with a valid RTXSYS parameter. |
Explanation | The BBOC RETRY parameter must be Yes (Y) or No (N). |
Action | Re-submit the request with a valid RETRY option. |
Explanation | The BBOC RETINT parameter must be in the range of 0 to 359999. |
Action | Re-submit the request with a valid RETINT parameter. |
Explanation | The BBOC RETCNT parameter must be in the range of 0 to 99999999. |
Action | Re-submit the request with a valid RETCNT parameter. |
Explanation | The BBOC RETRY option was selected and the optimized local adapters registration will now be retried. |
Action | No user action is required. |
Explanation | The BBOC RETRY option was selected and the optimized local adapters registration will no longer be retried. |
Action | No user action is required. |
Explanation | The BBOC RETRY option was processed and an EXEC CICS START TRANSID was issued to queue the command under a new instance of BBOC in retry mode. |
Action | No user action is required. |
Explanation | The BBOC command exceeded the maximum supported 500 characters. |
Action | Re-submit the request with a command that is a valid length. |
Explanation | The specified CICS EXEC function did not complete successfully. |
Action | Refer to the CICS error codes in the CICS documentation to determine the corrective action. |
Explanation | The BBOC DOC NAME parameter must specify a valid CICS document template name no more than 48 characters. |
Action | Re-submit the request with a valid NAME parameter. |
Explanation | The specified CICS EXEC function did not complete successfully. |
Action | Refer to the CICS error codes in the CICS documentation to determine the corrective action. |
Explanation | The specified CICS EXEC function did not complete successfully. |
Action | Refer to the CICS error codes in the CICS documentation to determine the corrective action. |
Explanation | A BBOC DOC request cannot be used as a command inside a document template. |
Action | Remove the BBOC DOC command from the referenced document template. |
Explanation | An error occurred while creating the CICS request ID for the EXEC CICS START TRANSID for the WOLA Link invocation task. |
Action | See the BBOQ extra partition transient data queue (TDQ) that is allocated under DD BBOOUT in the CICS region for further information. |
Explanation | The Link server module (BBOACSRV) level is not compatible with the control transaction module (BBOACNTL). |
Action | Ensure the WOLA load modules used in the CICS region are at the same service level. |
Explanation | During Link server processing an attempt was made to complete an EXEC CICS GETMAIN that failed |
Action | Review the return code and take the appropriate action. |
Explanation | The specified CTID parameter exceeds the maximum character length of four. |
Action | Set the parameter to a value with four or fewer characters and retry. |
Explanation | A CICS transaction identifier with the CPLT value was encountered when the TRUE was established. If the TRUE uses the CPLT value for transaction recovery, CICS issues an error. To avoid the error, the TRUE uses BBOC for transaction recovery. |
Action | If you do not want BBOC used as the transaction identifier, use the CTID= parameter in the CICS PLT initialization program to specify a different transaction identifier. A sample of a CICS PLT initialization program is in the http://github.com/WASdev/sample.wola/blob/master/bboacplt.jclsamp file. |