CICS TG and CICS UC Version 7.1 |
Operating systems: z/OS, UNIX, Linux, Windows |
An invalid command option was specified on the command line.
The command line application terminates.
Retype the command using the correct options.
A command line application was run with no value supplied for the named required option.
The command line application terminates.
Retype the command using the correct options.
The named option was used more than once on the command line. This is invalid.
The command line application terminates.
Retype the command using the correct options.
The two named options, used on the command line, were incompatible.
The command line application terminates.
Retype the command using the correct options.
The command line did not include one of the named required options.
The command line application terminates.
Retype the command using the correct options.
option1 was specified on the command line, but option2 was not also specified. This is invalid.
The command line application terminates.
Retype the command using the correct options.
An invalid command option was specified on the command line.
The command line application terminates.
Retype the command using the correct options.
A command line application was run with no value supplied for the named required option.
The command line application terminates.
Retype the command using the correct options.
The named option was used more than once on the command line. This is invalid.
The command line application terminates.
Retype the command using the correct options.
The two named options, used on the command line, were incompatible.
The command line application terminates.
Retype the command using the correct options.
The command line did not include one of the named required options.
The command line application terminates.
Retype the command using the correct options.
option1 was specified on the command line, but option2 was not specified. This is invalid.
The command line application terminates.
Retype the command using the correct options.
The memory trace option 'B' was specified, without specifying that trace is to be switched on with 'D'.
Tracing is not activated, and this error is returned to the user.
Retype the command, specifying 'D' in addition to 'B'.
CTGBATCH has encountered an error errno while attempting to write to logging destination dest-number (1=STDOUT 2=STDERR).
CTGBATCH will attempt to re-direct subsequent logging data to the default JES log destination.
Investigate why the desired logging destination has become unavailable and correct the problem. It is possible that there is no space left on the chosen file system.
CTGBATCH has encountered error errno while creating pipes to communicate with the target program. Without the ability to create and use inter-process pipes, logging will be unavailable.
CTGBATCH will terminate with JES return code 16, after writing diagnostic information to the STDERR log destination.
The z/OS C/C++ Run-Time Library Reference (SC28-1663) documents the possible errno values and likely reason for the failure. In this case, the failing function call is pipe(). If problems persist, contact your service organization and supply the diagnostic log data together with the JCL being used to start the Gateway daemon.
CTGBATCH has encountered error errno while starting the target program HFS_executable . Possible reasons could be that the user does have the correct authority to execute the target program, the program is not an USS executable or valid shell script.
CTGBATCH will terminate with JES return code 8, after writing diagnostic information to the STDERR log destination.
The z/OS C/C++ Run-Time Library Reference (SC28-1663) documents the possible errno values and likely reason for the failure. In this case, the failing function call is spawnp(). If problems persist, contact your service organization and supply the diagnostic log data together with the JCL being used to start the Gateway daemon.
CTGBATCH has encountered an unexpected internal error when processing log data.
CTGBATCH attempts to continue.
Contact your service organization and supply the diagnostic log data together with the JCL being used to start the Gateway daemon.
CTGBATCH has encountered an error while attempting to read log data from the target program. It is possible that the target program has ended abnormally, before CTGBATCH had a chance to process the latest log data.
CTGBATCH will close the resources associated with this log before continuing.
If the problem is believed to be in the target program, then check for any diagnostic information specific to the target program that may have logged before it ended abnormally. If this is not the case, contact your service organization and supply the diagnostic log data together with the JCL being used to start the Gateway daemon.
CTGBATCH has encountered an unexpected condition.
CTGBATCH will write internal state data to the error log.
Check the diagnostic messages immediately prior to this state information dump for an indication of the specific problem.
CTGBATCH was unable to use the supplied STDOUT DD statement, or the STDOUT DD statement was not defined.
CTGBATCH continues. A JES log will be dynamically defined for stdout log messages. The log name will likely be 'SYS00001'. When CTGBATCH completes, the JES return code will be at least 4.
If the JCL for CTGBATCH did contain a STDOUT DD statement, verify that the definition is correct.
CTGBATCH was unable to use the supplied STDERR DD statement, or the STDERR DD statement was not defined.
CTGBATCH continues. A JES log will be dynamically defined for stdout log messages. The log name will likely be 'SYSOUT', although this can be overridden by the LE runtime option "MSGFILE". When CTGBATCH completes, the JES return code will be at least 4.
If the JCL for CTGBATCH did contain a STDERR DD statement, verify that the definition is correct.
CTGBATCH was unable to use the supplied STDENV DD statement, or the STDENV DD statement was not defined.
CTGBATCH continues. If the target program is a USS executable (e.g. ctgmsgs) then a STDENV may not be required.
If the JCL for CTGBATCH did contain a STDENV DD statement, verify that the definition is correct.
CTGBATCH diagnostic checks have found that a significant environment variable has not been set.
CTGBATCH continues.
Check whether or not the listed variable should be set in the STDENV data. It will be one of the following: - PATH should at least include "/bin" for base USS system commands and "<Java path>/bin" for the JVM startup script "java". - CICSCLI should specify the path to the "ctg.ini" file to be used by this Gateway daemon. If omitted, the Gateway daemon will attempt to find "ctg.ini" in the product "bin" directory. - TMPDIR should typically be set to "/tmp"; however, if /tmp is prone to becoming full - then it is advisable to specify a writable path which is dedicated to Gateway daemon usage. The ctgstart script utilizes fundamental USS commands which depend on the TMPDIR path having free space and being writable. - _BPX_SHAREAS should be set to YES when CTGBATCH is being used to launch either the Gateway daemon or ctgmaster. This will ensure mean that the target executable and CTGBATCH will run in the same address space if at all possible. - TZ should be set to reflect the local timezone and daylight savings time. The setting should usually reflect the setting of TZ in /etc/profile. The full format is : TZ= standardHH[:MM[:SS]] [daylight[HH[:MM[:SS:]]] [,startdate[/starttime],enddate[/endtime]] ] An example for UK could be TZ=GMT0BST,M3.5.0,M10.4.0 or for US Eastern could be TZ=EST5EDT For a further information please refer to z/OS UNIX System Services Command Reference (SA22-7802).
CTGBATCH diagnostics have failed to obtain the Region size data.
CTGBATCH continues.
This is a soft failure within CTGBATCH diagnostics, likely related to the problem for which diagnostics were enabled.
CTGBATCH diagnostics have failed to obtain the current working directory data.
CTGBATCH continues.
This is a soft failure within CTGBATCH diagnostics, likely related to the problem for which diagnostics were enabled.
CTGBATCH diagnostics have failed to obtain specific data relating to the current Runtime user.
CTGBATCH continues.
This is a soft failure within CTGBATCH diagnostics, likely related to the problem for which diagnostics were enabled.
CTGBATCH has encountered an unexpected internal error when generating a local message text.
CTGBATCH attempts to continue.
Contact your service organization and supply the diagnostic log data together with the JCL being used to start the Gateway daemon.
CTGBATCH has encountered an unexpected internal error when generating a local message text.
CTGBATCH attempts to continue.
Contact your service organization and supply the diagnostic log data together with the JCL being used to start the Gateway daemon.
The target program completed with a non-zero return code.
CTGBATCH will end normally.
Investigate the target program log data to determine why it may have completed with a non-zero return code.
The target executable target-program could not be found.
CTGBATCH will terminate with JES return code 8.
Check that target-program is correct. Ensure that the PARM string specified for the EXEC PGM=CTGBATCH JCL statement is correct. Up to and including the first forward slash (/) character of the PARM string is taken to be a LE runtime option. Therefore, ensure that the HFS path component of the PARM string includes its own leading / character. See the Administration book for more details.
CTGBATCH diagnostics have failed to obtain general data relating to the current Runtime user.
CTGBATCH continues.
This is a soft failure within CTGBATCH diagnostics, likely related to the problem for which diagnostics were enabled.
CTGBATCH diagnostics have failed to obtain Locale data.
CTGBATCH continues.
This is a soft failure within CTGBATCH diagnostics, likely related to the problem for which diagnostics were enabled.
CTGBATCH has encountered error errno while attempting to set an environment variable from the STDENV data.
CTGBATCH continues.
The z/OS C/C++ Run-Time Library Reference (SC28-1663) documents the possible errno values and likely reason for the failure. In this case, the failing function call is setenv(). If problems persist, contact your service organization and supply the diagnostic log data together with the JCL being used to start the Gateway daemon.
CTGBATCH detected that more than one of CTGMSGEN, CTGMSGJA or CTGMSGZH DD statements have been defined.
CTGBATCH will terminate with JES return code 20.
Check the JCL used to start CTGBATCH and ensure that at most one of CTGMSGEN, CTGMSGJA or CTGMSGZH dummy DD statements are defined.
The binary trace formatter is unable to write any further information to the Client trace file during conversion of the binary trace.
The binary trace formatter terminates.
Determine the cause of the error. It may be that the disk which the binary trace formatter is writing to is full, or the disk might be write-protected.
The binary trace formatter tried to format the binary trace file, but could not read the whole file. offset is the number of bytes between the start of the trace file and the error.
The binary trace formatter terminates.
Check that the binary trace file has not been deleted or truncated during conversion, and that it is not read-protected.
The binary trace formatter is unable to open the specified file for reading or writing as required.
The binary trace formatter terminates.
If the file that is being opened is the binary trace file, check that the file exists and that it is not read-protected. If the file that is being opened is the output text file, make sure that the disk on to which the file is being written is not write-protected.
The binary trace formatter cannot process the binary trace file filename ,because the file contains some incorrect data structures. offset is the number of bytes between the start of the trace file and the error.
The binary trace formatter terminates.
Make sure that the file being read is a valid binary trace file, and that it was created with the version of the Client daemon currently installed on your system. If the trace file was transferred from another computer, check that it was not damaged in transit. If you still get the same error, delete the binary trace file and run the trace again.
The binary trace formatter has run out of free memory whilst processing the binary trace.
The binary trace formatter terminates.
Increase the amount of available memory in the system by shutting down applications that are not needed, and then re-run the binary trace formatter. You can reduce the amount of memory that the binary trace formatter needs by specifying on the command line the maximum amount of data to convert at any one time (refer to the documentation for further information on how to do this).
The binary trace formatter detected an invalid version number in the binary trace file.
The binary trace formatter terminates without performing any further processing.
Make sure that the file you are trying to convert is a valid binary trace file and that you are using the most recent version of the binary trace formatter that is available on your system.
The binary trace formatter cannot access the section of the binary trace file which is referred to by filename . offset represents the offset in bytes, from the start of the trace file, where the error occurred.
The binary trace formatter terminates.
Check that the user has access to the binary trace file. Check that the binary trace file has not been truncated.
The trace file that has been specified does not contain any trace data. This can occur if memory mapped trace wrapping is being used, and the trace was not on for long enough for all of the trace files to be used.
The binary trace formatter will terminate. An empty text output file will be produced.
Either format the entire wrapping trace using the 'w' option, or choose another wrapping file to format.
Memory mapped wrapping trace is being used. None of the trace files in the sequence contain any data.
The binary trace formatter will terminate. An empty text output file will be produced.
If the problem persists contact your service organization.
A memory mapped trace is being formatted. File filename is not in the correct point in the sequence.
The binary trace formatter will terminate. No formatted output will be produced.
If the files have been renamed, verify that they have been given the correct sequence number in the file type suffix. If files have been transferred from another machine, verify that they have not been corrupted.
A system or internal product function failed.
The message is written to the error log. The function name and error code are logged.
If the problem persists, contact your service organization.
An internal EPI error has occurred.
The message is written to the error log. The function name and error code are logged, together with the TermId.
If the problem persists, contact your service organization.
An system or internal Client function failed.
The message is written to the error log. The function name and error code are logged.
If the problem persists, contact your service organization.
You have specified a list of components on the command line, but one or more of the components in the list is invalid.
The request that required a list of components to be specified is ignored.
Refer to the Administration book for a list of valid components and retype the request.
The system has thrown a signal that has been caught by the Client daemon and has entered the DaemonAbend function for processing.
The message is written to the error log. The signal code is logged.
Investigate what caused the system to generate the signal. If the problem persists, contact your service organization.
The system has thrown a signal that has been caught by the Client daemon and has entered the DaemonExit function for processing.
The message is written to the error log. The signal code is logged.
Investigate what caused the system to generate the signal. If the problem persists, contact your service organization.
The Client cannot open the binary trace file for writing.
The Client continues, but tracing is disabled.
Check that the directory into which the binary trace file is being written is not write protected.
The binary trace file opened successfully, but an error occurred while a trace point was being written.
The Client continues, but tracing is disabled.
Check that the permissions of the trace file have not changed.
There is not enough available memory for tracing to continue.
The Client continues, but tracing is disabled.
Make more memory available to the Client and then try again.
An internal error has occurred. The Client is unable to buffer its writes to the trace file.
The Client continues, but tracing is disabled.
If the problem persists, contact your service organization.
An internal system function has returned an error while tracing was turned on.
The Client continues, but tracing is disabled.
If the problem persists, contact your service organization.
An internal function has returned an error whilst tracing was turned on.
The Client continues, but tracing is disabled.
If the problem persists, contact your service organization.
This message will appear in the log file on UNIX and Linux if the owner of the trace file changes. For security reasons, you may not change the owner of the trace file whilst trace is running.
The Client continues, but tracing is disabled.
Restart trace and make sure that the owner of the trace file does not change.
An internal error prevented tracing from being turned on.
The Client continues, but tracing is disabled.
If the problem persists, contact your service organization.
The trace file was deleted whilst tracing was active.
This message is written to the error log. Tracing continues.
Deleting the trace file while tracing is active is not recommended. To limit the size of the trace file, set the maximum Client wrap size. See the Administration guide for more details.
The specified trace component is not valid.
Tracing continues, but the specified component is ignored.
Remove the reference to the invalid component.
A previously caught system signal has caused the trace lock semaphore to become unobtainable.
Tracing is terminated to prevent the possibility of further error messages.
Investigate what caused the system to generate the initial signal.
The CICSCLI -B option has been used to specify memory mapping trace, but MAXWRAPSIZE is 0, or is not set in the configuration file ctg.ini. Memory mapped trace can be used only if trace wrapping is enabled.
Tracing will be written using standard file I/O instead of memory mapped trace.
Specify a maximum Client wrap size, restart the Client and invoke memory mapped trace again.
A thread ended unexpected, leaving a partially written trace point in the internal trace buffer. Before the thread ended, it recorded the process id pid , thread id tid and trace point number trace pt in the trace buffer.
This message is logged, and Client trace continues. The individual trace point being written is lost.
If the problem persists, contact your service organization.
A thread ended unexpectedly, leaving a partially written trace point in the internal trace buffer. The buffer contains too little information to determine which trace point was being written when the thread ended.
This message is logged, and Client trace continues. The individual trace point being written is lost.
If the problem persists, contact your service organization.
The MAXWRAPSIZE parameter in the configuration file ctg.ini controls the maximum wrapping size of memory mapped trace. This is set to a value which is larger than the available space in the filesystem that trace is written to.
This message is logged. Client tracing is not activated.
Either increase the file system so that it can contain the full trace file, or reduce the value of MAXWRAPSIZE.
The exception named, one of the Ccl::ExCode enumeration values, was raised during the execution of the class ::method method during the server request indicated by the 'call' value. An exception object encapsulating details of the exception is passed to CclECI::handleException or CclEPI::handleException and/or thrown via the C++ exception mechanism.
The message is written to the trace file if tracing is enabled.
None.
ctgd was unable to change the effective user ID of the running process to the specified user. This is due to either the current user having insufficient privilege, or the specified user ID being invalid.
The Gateway daemon does not start.
Check that the current user has sufficient privilege to change user ID and that the user ID specified in ctgd.conf is valid.
ctgd was unable to change the effective group of the running process to the specified group. This is due to either the current user having insufficient privilege, or the specified group being invalid.
The Gateway daemon does not start.
Check that the current user has sufficient privilege to change group and that the group specified in ctgd.conf is valid.
ctgd was unable to start the specified program. The specific error code can be referenced in the documentation for your operating system.
The program in question, typically the Gateway daemon, does not start.
Ensure that the path is absolute and the user specified in ctgd.conf has permission to execute it.
The Client daemon received a request for a server, but the server is not defined in the configuration file.
The request fails but the Client daemon continues.
Ensure the server name specified by the ECI or EPI application, or by the 3270 Emulator is correct. If required, add the server name to the configuration file, then stop and restart the product to activate the changes.
An error was detected.
The Client daemon terminates.
Examine any other messages and the Client error log to determine the cause of the error.
The Client daemon ran out of memory while processing a request.
The request fails and the Client daemon attempts to continue processing.
Try altering the values in the configuration file to provide a larger free memory pool or to reduce the overall memory requirements.
The Client daemon detected an unexpected internal error.
Error information is written to the Client error log.
If the problem persists, contact your service organization.
The Client daemon detected an unexpected error.
Error information is written to the Client error log.
If the problem persists, contact your service organization.
An internal Client function failed.
The message is written to the error log and the Client terminates. The function name and error code are logged.
If the problem persists, contact your service organization.
The Client was unable to allocate enough memory to create an internal control structure for a new server conversation.
The message is written to the error log and processing continues. The conversation is not created.
Try altering the values in the configuration file ctg.ini to provide the Client with a larger free memory pool or to reduce the overall memory requirements.
The Client was unable to locate an internal control structure for an existing server conversation.
The message is written to the error log and processing continues. The conversation is ended.
If the problem persists, contact your service organization.
The Client was unable to allocate enough memory to create an internal control structure associated with an emulator or EPI terminal.
The message is written to the error log and processing continues. The control structure is not created.
Try altering the values in the configuration file ctg.ini to provide the Client with a larger free memory pool or to reduce the overall memory requirements.
The Client was unable to locate an internal control structure associated with a terminal or EPI program. This may occur if an ATI request is received for a terminal that no longer exists because either the Client or the terminal was shut while the ATI was in transit.
The message is written to the error log and Client processing continues but the emulator may be unable to continue.
If the problem persists, contact your service organization.
The Client received an event associated with an unconnected server.
The message is written to the error log and processing continues. The event is ignored.
If the problem persists, contact your service organization.
The Client received an unknown event from one of the communications protocol drivers.
The message is written to the error log and processing continues. The event is ignored.
If the problem persists, contact your service organization.
The default userid has been set to a value which contains only spaces.
The message is logged, and processing continues.
When using connection security, blank userids and passwords are valid only if 'Usedfltuser' is set to YES in the CICS connection definition.
An internal function failed.
The message is written to the error log and processing continues. The function name and error code are logged.
If the problem persists, contact your service organization.
The Client tried to send a response to an unknown application. Often this occurs if the application has ended before its response was received. The session value identifies the application.
The message is written to the trace file if tracing is enabled.
None.
The Client was unable to allocate enough memory to create an internal control structure.
The message is written to the error log and processing continues if possible.
Try altering the values in the configuration file ctg.ini to provide the Client with a larger free memory pool or to reduce the overall memory requirements.
The specified Client system transaction tran failed to run on the specified server. If connecting to a CICS TS for iSeries server, a failure of transaction CCIN indicates that the server is not available.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The Client daemon could not open or write to the specified error log file.
Log messages are lost.
Check that the name specified in the LogFile parameter in the configuration file is correct and accessible.
The Client received data from a server that exceeded the MaxBufferSize limit. The size value indicates the current MaxBufferSize setting and the length value indicates the length of the incoming data.
The message is written to the error log and processing continues.
Try altering the value of MaxBufferSize in the configuration file ctg.ini to at least the size of the incoming data.
The Client has attempted to put a transport message to a window owned by the Client application. This has failed, the most likely reason for this is that the message queue associated with the windows Client application is full.
The message is written to the trace file if tracing is enabled. The Client allows windows to process messages in the queue and then tries posting the transport message again, a number of times.
Try using SetMessageQueue to increase the size of the message queue.
An internal element of work took more than 30s to complete.
This message is output.
Check if any requests have failed to respond. If this problem continues contact your service organisation.
An error occurred during communications with the Windows Service Control Manager. The Windows OpenSCManager function returned the specified error.
The message is logged, and processing continues. The requested action does not succeed.
Check the Windows Event Log for further information on the error. If the problem persists, contact your service organization.
An error occurred during communications with the IBM CICS Universal Client service. The Windows OpenService function returned the specified error.
The message is logged, and processing continues. The requested action does not succeed.
Check the Windows Event Log for further information on the error. If the problem persists, contact your service organization.
An error occurred while the IBM CICS Universal Client service was starting. The Windows Service Control Manager returned the specified error.
The message is logged. Neither the Client daemon nor the IBM CICS Universal Client service start.
Check the Windows Event Log for further information on the error. If the problem persists, contact your service organization.
An error occurred while the IBM CICS Universal Client service was stopping. The Windows Service Control Manager returned the specified error.
The message is logged. The Client daemon shuts down. The IBM CICS Universal Client service might not be marked as terminated.
Check the Windows Event Log for further information on the error. If the problem persists, contact your service organization.
An error occurred while an internal message was being sent to the IBM CICS Universal Client service.
The message is logged, and processing continues. The requested action does not succeed.
Check the Windows Event Log for further information on the error. If the problem persists, contact your service organization.
The current user has insufficient authority for the administration of Windows Services.
The message is logged, and processing continues. The requested action does not succeed.
Check the Windows Event Log for further information on the error. Ensure the current user has the required level of authority.
The configuration file contains an entry for a separate information log, but the file specified could not be opened for writing.
Informational messages will be output to the error log instead.
Correct the entry in the configuration file to avoid seeing this message in future.
Errors were detected at or before the specified line in the configuration file.The following message will highlight the error and its severity.
The Client daemon may terminate.
See following message for details and correct the configuration file and restartthe product.
The specified configuration file could not be found.
The Client daemon terminates.
Ensure that the required configuration file exists and is correctly specified.
An = sign was expected after a parameter in the configuration file.
The Client daemon terminates.
Correct the configuration file error and restart the product.
An unknown parameter starting with specified text was encountered in the configuration file.
The Client daemon terminates.
Correct the configuration file error and restart the product.
A valid parameter was encountered in the wrong position in the configuration file.
The Client daemon terminates.
Correct the configuration file error and restart the product.
A valid parameter had an incorrect value specified in the configuration file.
The Client daemon terminates.
Correct the configuration file error and restart the product.
The values of certain parameters specified in the configuration file have dependencies on each other. The values for the two specified parameters are inconsistent.
The Client daemon terminates.
Correct the configuration file error and restart the product.
The specified parameter is missing from the configuration file and must be provided.
The Client daemon terminates.
Correct the configuration file error and restart the product.
There was not enough free memory to process the configuration file.
The Client daemon terminates.
Try altering the values in the configuration file to provide a larger free memory pool or to reduce the overall memory requirements.
The value of the protocol parameter in a Server section of the configuration file must match with the name of a Driver section. No matching driver definition was found for the named protocol.
The Client daemon terminates.
Correct the configuration file error and restart the product.
Errors were encountered while reading the configuration file.
The Client daemon terminates.
Correct the configuration file error and restart the product.
A Client, Server, or Driver section in the configuration file has the same name as a previously specified section.
The Client daemon terminates.
Correct the configuration file error and restart the product.
Errors were encountered while accessing file file name .
The Client daemon terminates.
Change the file permissions and restart the product.
MAXREQUESTS has been set to a value higher than the maximum allowed.
The Client daemon sets MAXREQUESTS to the maximum allowed (max ) and continues.
To avoid this message being logged at startup, correct the configuration file. The CICS Universal Client is intended for single user use only; the CICS Transaction Gateway can be configured to handle a higher number of concurrent requests.
The default directory contains both uppercase and lowercase versions of the configuration file.
The Gateway daemon will use the default file 'ctg.ini' as no configuration filename has been specified. The contents of file 'CTG.INI' will be ignored.
To avoid this warning being issued, explicitly specify a configuration file or delete file 'CTG.INI' from the default directory. For details of how to specify a configuration file see the Configuration chapter of the Administration Guide.
Parameters in either one or both of the server and driver sections of the configuration file have been configured to use TCP62. This product does not support TCP62.
This message is logged and the client daemon will fail to start.
The Information Center for the CICS TG and CICS UC provides details, and examples, of how to configure the Client daemon to use a range of supported network protocols to connect to CICS.
The "Application ID" parameter specified on SECTION CLIENT is deprecated, it is replaced by a new APPLID parameter.
The Application ID specified on SECTION CLIENT will be used when communicating with CICS servers.
Refer to the product information center for details of the new APPLID parameter.
The "Application ID" parameter specified on SECTION CLIENT is deprecated and is overidden by the new APPLID parameter.
The APPLID value specified in SECTION PRODUCT will be used when communicating with CICS servers.
Set the APPLID parameter to the value required and set "SECTION CLIENT = *".
The LUALIASNAMES parameter specified in the SECTION SERVER is deprecated. On a Windows platform LUALIASNAMES is replaced by parameters LOCALLUALIAS and PARTNERLUALIAS, on a UNIX or Linux platform LUALIASNAMES is replaced by PARTNERLUALIAS.
On a Windows platform the value of parameters LOCALLUALIAS and PARTNERLUALIAS is set to the same value specified for LUALIASNAMES, on a UNIX or Linux platform PARTNERLUALIAS defaults to Y.
Refer to the product information center for details of the parameters LOCALLUALIAS and PARTNERLUALIAS.
The LUALIASNAMES parameter specified in the SECTION SERVER is deprecated and is overidden. On a Windows platform LUALIASNAMES is replaced by parameters LOCALLUALIAS and PARTNERLUALIAS, on a UNIX or Linux platform LUALIASNAMES is replaced by PARTNERLUALIAS.
When LOCALLUALIAS and, or PARTNERLUALIAS is specified the value of LUALIASNAMES is ignored.
Set the parameters LOCALLUALIAS and PARTNERLUALIAS to the required values.
The Client received invalid data from a server. The data does not have a valid CICS data stream header. The gds value should be either 0x12F2 or 0x12FF, the length value gives the expected data length, and size gives the true received length.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The Client received invalid data from a server. The data was not part of a valid SYNC or ROLLBACK flow. The length values gives the length of the received data and data contains the first four bytes.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The Client received invalid data from a server. The data was not a valid CICS FMH43 header. The length values gives the length of the received data.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The Client received invalid data from a server. The data was not a valid CICS data stream. The type value indicates which part of the data contained errors, value1 and value2 further identify the error. This message may be received if the server does not support signon capable terminals.
The message is written to the error log and processing continues.
Use the option to request a non-signon capable terminal. If the problem persists, contact your service organization.
The Client was unable to allocate enough memory to save data from a server. Normally such data is a COMMAREA associated with an emulator terminal.
The message is written to the error log and processing continues.
Try altering the values in the configuration file ctg.ini, to provide the Client with a larger free memory pool or to reduce the overall memory requirements.
The Client received an invalid transaction attach request from a server. The only valid transaction name is CRSR, used to start ATI requests to a terminal. The data value indicates the requested transaction name.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The Client received invalid data from a server. The data was not a valid CICS FHM5 header. The length value gives the length of the received data.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The client name specified in the Client section of the configuration file was already installed on the specified server.
The server rejects the Client daemon's installation request.
Ensure all Client names are unique within the network or specify the name as "*" to enable a suitable unique name to be generated automatically.
The specified server was busy and could not process the Client daemon installation request.
The server rejects the Client daemon's installation request.
Retry the request sometime later when the server is not so busy. If the problem persists contact your server administrator.
The specified server could not process the Client installation request.
The server rejects the Client daemon's installation request, server continues processing.
Examine the Client error log and, if possible, trace information on both the Client and server to determine the cause of the error.
A user exit running on the specified server rejected the request to install the Client definition.
The server rejects the Client's installation request, the Client daemon continues processing.
Check with the server system administrator to determine why the Client installation request was rejected.
The Client received the password expiry management (PEM) transaction response from a server. The data contained in the corresponding PEM request contained a data formatting error.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The codepage value sent to the server was rejected.
The server rejects the Client's installation request, the Client daemon continues processing.
If the CCSID parameter has been specified in ctg.ini, check that the value specified is valid. Otherwise, check with the server system administrator to determine why the codepage value was rejected.
The Client tried to communicate with a server whose connection is currently unavailable.
The message is written to the error log and processing continues. The server is ignored.
If the problem persists, contact your service organization.
The Client was unable to locate an internal control structure associated with a connection to a server.
The message is written to the error log and processing continues. The server is ignored.
If the problem persists, contact your service organization.
The Client was unable to locate an internal control structure associated with a server conversation.
The message is written to the error log and processing continues. The conversation is ignored.
If the problem persists, contact your service organization.
The Client received an invalid internal event from a communications protocol driver.
The message is written to the error log and processing continues. The event is ignored.
If the problem persists, contact your service organization.
The Client detected a conversation to a server in an incorrect state.
The message is written to the error log and processing continues. The request is ignored.
If the problem persists, contact your service organization.
The Client was unable to locate an internal control structure associated with a communications protocol driver.
The message is written to the error log and processing continues. The driver is ignored.
If the problem persists, contact your service organization.
The specified communications protocol driver module could not be found or loaded.
No communication can take place using the protocol, the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The Client was unable to allocate enough memory to create an internal control structure associated with communications.
The message is written to the error log and processing continues.
Try altering the values in the configuration file ctg.ini, to provide the Client with a larger free memory pool or to reduce the overall memory requirements.
The Client was unable to load a communications protocol driver DLL.
The message is written to the error log and processing continues. The name of the failing DLL and the loading function and error codes are logged.
Ensure the DLL is available and correctly named. If the problem persists, contact your service organization.
The Client application cannot communicate with the Client daemon.
This message is written to the log file. The EPI request returns CICS_EPI_ERR_FAILED.
This is expected behavior if the Client daemon has been stopped or restarted while an EPI session is active. First shut down the Gateway daemon if it is running, then shut down the Client daemon, and finally restart the Gateway daemon. If you are running a local mode Java application, shut it down and then restart it. Code any user applications that receive this error to restart the EPI by issuing a CICS_EpiTerminate call, followed by CICS_EpiInitialize to reinitialize the EPI; subsequent requests should complete successfully. Alternatively program applications to end if they receive this error. If the Client daemon had not been stopped or restarted, and the problem persists, contact your service organization.
The Client application cannot communicate with the Client daemon.
This message is written to the log file. The ECI request returns ECI_ERR_SYSTEM_ERROR.
This is expected behavior if the Client daemon has been stopped while an application, or the Gateway daemon is active. First shut down the Gateway daemon if it is running, then shut down the Client daemon, and finally restart the Gateway daemon. If you are running a local mode Java application shut it down and then restart it.
The specified communications protocol driver module reported errors during startup.
No communications can take place using the protocol, the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The specified communications protocol driver module reported errors while it was closing down.
The error is ignored and the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The specified communications protocol driver module reported errors while it was trying to connect to a server.
The Client daemon cannot communicate with the server, the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The specified communications protocol driver module reported errors while it was closing a connection with a server.
The error is ignored and Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The specified communications protocol driver module reported errors while it was starting a new conversation with a connected server.
The request to start the conversation fails and the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The specified communications protocol driver module reported errors while it was closing a conversation with a connected server.
The request to close the conversation fails and the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The specified communications protocol driver module reported errors while it was sending data over a conversation with a connected server.
The request that sent the data fails and the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The specified communications protocol driver module reported errors while it was receiving data from a conversation with a connected server.
The request that required the data fails and the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
The specified communications protocol driver module reported errors while it was communicating or trying to communicate with a server.
The request that initiated the communications fails and the Client daemon continues processing.
Examine the Client error log and, if possible, trace information to determine the cause of the error.
An internal Client communications function failed.
The message is written to the error log and the Client terminates. The function name and error code are logged.
If the problem persists, contact your service organization.
An network communications error occurred.
The message is written to the error log and the Client continues. The internal return codes provide information for use by IBM service groups.
If the problem persists, contact your service organization.
The TCP/IP protocol driver cannot issue TCP/IP calls on this system. TCP/IP may not be installed or may not be active on the system.
The message is written to the error log and processing continues.
Alter the system configuration to try to activate or install TCP/IP. If the problem persists, contact your service personnel.
The TCP/IP protocol driver could not allocate enough memory to create the internal data buffers.
The message is written to the error log and processing continues.
Try altering the values in the configuration file ctg.ini, to provide the Client with a larger free memory pool or to reduce the overall memory requirements.
The TCP/IP protocol driver could not create a TCP/IP socket. The server value identifies the server. The error value identifies the TCP/IP error code. The errordesc value provides a description of the error.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The TCP/IP protocol driver could not resolve a server host IP name. The netname value identifies the IP name and server identifies the server. The error value gives the TCP/IP error code. The errordesc value provides a description of the error.
The message is written to the error log and processing continues.
Ensure the server IP name or address is correct and can be resolved by the local name server. If the problem persists contact your service organization.
The TCP/IP protocol driver could not allocate enough memory to create the internal control structures; server identifies the server.
The message is written to the error log and processing continues.
Try altering the values in the configuration file ctg.ini, to provide the Client with a larger free memory pool or to reduce the overall memory requirements.
The TCP/IP protocol driver could not send data to a server. The server value identifies the server. The error value gives the TCP/IP error code. The errordesc value shows the description of the error.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The TCP/IP protocol driver could not connect to a server. The server value identifies the server. The error value gives the TCP/IP error code. The errordesc value shows the description of the error.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The TCP/IP protocol driver could not receive data from a server. The server value identifies the server. The error value gives the TCP/IP error code. The errordesc value shows the description of the error.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The TCP/IP protocol driver could not start an internal listener function; server identifies the server.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The TCP/IP protocol driver for Windows requires a WINSOCK DLL of at least version required , however version found was found to be installed. The required and found values indicate the version of WINSOCK required and found respectively.
The message is written to the error log and processing continues.
Ensure your TCP/IP product provides a suitable level of the WINSOCK DLL and the system is correctly configured. If the problem persists contact your service organization.
The TCP/IP link failed. The server value identifies the server and the error value gives the TCP/IP error code.
The message is written to the trace file if tracing is enabled.
If the problem persists, contact your service organization.
The transaction failed. The server value identifies the server and the sense code value gives the FMH7 sense data.
The message is written to the trace file if tracing is enabled.
If the problem persists, contact your service organization.
During TCP/IP processing a memory allocation failed.
The message is written to the trace file if tracing is enabled.
None.
An error occurred when attempting to send a good ping response.
The message is written to the trace file if tracing is enabled.
None.
Received a flow that looks like a ping but cannot be interpreted by the existing criteria.
The message is written to the trace file if tracing is enabled.
None.
This is the end of the processing loop. For the receive thread to be restarted, INSERT-0 needs to be zero and INSERT-1 needs to be zero or positive. If the recv thread is not started, tcp receives will not occur.
The message is written to the trace file if tracing is enabled.
None.
The TCP/IP send got a bad return code.
The message is written to the trace file if tracing is enabled.
None.
The protocol driver was unable to allocate memory when starting a conversation.
The conversation will not be allocated, this message is logged and the Client daemon continues.
Free up some memory and retry.
The TCP/IP socket select call completed with an error. The error value gives the TCP/IP error code. The error description value shows the description of the error.
The message is written to the error log and processing continues.
Check the configuration for the given server server , specifically check the addressof the server machine and the port that the CICS server is using. Check the basic connectivity to the server using the "ping" command to check the address of the server machine is accessible on the network. Check that the CICS server is up and listening on the expected port. If the problem persists, contact your service organization.
The TCP/IP socket select call timed out.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
A TCP/IP socket select call could not complete as the file descriptor had not been set.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The TCP/IP socket being used is closed.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
The host specified is unreachable.
The message is written to the trace file and processing continues
If the problem persists, contact your service organization.
The Client daemon could not send to the CICS region. The send was retried until the retry count was exceeded. This error can be caused by a full local send buffer or a full remote receive buffer.
The link to the server is marked as unavailable and will need to be reconnected before it can be used again.
Re-establish the connection and try increasing the size of the TCP/IP send and receive buffers.
The TCP/IP socket send call did not complete within 5 seconds. The errordesc value gives the TCP/IP error code.
The message is written to the error log and processing continues. The send call is expected to complete within5 seconds and not doing so may indicate an underlying problem in the OS or network hardware.
If the problem persists, contact your service organization.
The data to send over the TCP/IP socket was too long
The data is truncated to the maximum size and sent.
This is an internal error. Contact your service organization.
The TCP/IP protocol driver received more data than its buffer space could hold. The server value identifies the server, the data is discarded.
The message is written to the error log and processing continues.
If the problem persists, contact your service organization.
There was insufficient free memory for the Client SNA protocol driver to retrieve LU 6.2 information from the APPC provider.
The SNA protocol driver is not initialized.
Free up some memory and retry.
There was insufficient free memory for the Client SNA protocol driver to receive data from any servers.
The SNA protocol driver is not initialized.
Free up some memory and retry.
There was insufficient free memory for the Client SNA protocol driver to send data to any servers.
The SNA protocol driver is not initialized.
Free up some memory and retry.
Creation of thread, to handle inbound allocate requests from ATI to Client terminals, failed.
The SNA protocol driver is not initialized.
If the problem persists, contact your service organization.
The specified partner LU name in the 'NETNAME' parameter in your configuration file has an invalid length for this SNA protocol driver and 'PARTNERLUALIAS' parameter setting. The maximum length of an alias name is 8 characters, the minimum length is 1.
The connection to the partner LU is not started.
Refer to the Administration book to determine whether or not this SNA protocol driver requires the use of alias names. Correct the 'NETNAME' and/or 'PARTNERLUALIAS' parameters in the configuration file and retry.
The specified partner LU name in the 'NETNAME' parameter in your configuration file has an invalid length for this SNA protocol driver and 'PARTNERLUALIAS' parameter setting. The maximum length of a fully qualified name is 17 characters (********.********). The minimum length is 1.
The connection to the partner LU is not started.
Refer to the Administration book to determine whether or not this SNA protocol driver supports fully qualified names. Correct the 'NETNAME' and/or 'PARTNERLUALIAS' parameters in the configuration file and retry.
There was insufficient free memory for the Client SNA protocol driver to open a link to the specified server.
The Client continues.
Free up some memory and retry.
The Client SNA protocol driver was unable to open a link to the specified server because retrieval of LU6.2 information from the APPC provider failed. The APPC DISPLAY verb failed with the specified return code.
The Client continues.
If the problem persists, contact your service organization.
The Client SNA protocol driver was unable to open a link to the specified server because not all of the LU6.2 information could be obtained from the APPC provider.
The Client continues.
If the problem persists, contact your service organization.
The Client SNA protocol driver was unable to open any link using this LU because it is not defined to IBM Communications Manager/2.
The Client continues.
Define the LU to the Communications SNA Server or correct the 'LocalLUName' parameter in your configuration file ctg.ini and retry.
The Client SNA protocol driver was unable to open any link using this partner LU because it is not defined to IBM Communications Manager/2.
The Client continues.
Define the partner LU to IBM Communications Manager/2 or correct the 'NetName' parameter in your configuration file ctg.ini and retry.
APPC could not execute the verb because Communications Manager had not started APPC. Either Communications Manager has not been started or it has not been configured correctly for the application.
The Client continues.
Start Communications Manager if it is not active. If the necessary APPC profiles are not configured, configure them and restart Communications Manager.
The APPC verb TP_STARTED failed with the specified return code. The connection to the specified server has not been started.
The Client continues.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The APPC verb TP_ENDED failed with the specified return code.
The Client connection to the specified server is closed.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
There was insufficient free memory for the Client SNA protocol driver to start a conversation with the specified server.
The Client continues.
Free up some memory and retry.
APPC could not allocate a conversation because no free sessions were available.
The Client continues.
Wait until one or more existing conversations have finished and retry.
An attempt was made to allocate a Client conversation in SNASVCMG or CPSVCMG sessions mode. These are not valid modes.
The Client continues.
Change the 'Modename' parameter in the configuration file ctg.ini and retry.
The specified mode has not been defined.
The Client continues.
Check whether the mode has been configured, and the spelling of the 'ModeName' parameter in the configuration file ctg.ini.
The APPC verb ALLOCATE failed with the specified return code. A conversation with the specified server has not been started.
The Client continues.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The APPC verb DEALLOCATE failed with the specified return code.
The Client continues.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
A Client thread could not be created to process the queue holding inbound attach requests; _beginthread failed.
The SNA protocol driver is not initialized.
Contact your system administrator.
A Client thread could not be created to receive data from the server for the current conversation; _beginthread failed.
The conversation is deallocated.
Contact your system administrator.
An attempt to allocate resources for inbound allocate requests from ATI to Client terminals has failed.
The Client continues but all inbound request processing is terminated.
Check SNA configuration for ATI Side Information Profile entry.
An error occurred during an inbound ATI request.
The Client continues but all inbound request processing is terminated.
Contact your system administrator.
The Client received an inbound ATI attach request but the receive allocate failed because the attach manager was stopped.
The inbound allocate request is rejected.
Start the attach manager.
The APPC verb SET_TP_PROPERTIES failed with the specified return code.
The property change request is ignored. The client daemon attempts to continue. The SNA Logical Unit of Work (LUW) id for this conversation may not be unique.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The APPC verb RECEIVE_ALLOCATE failed with the specified return code.
The inbound allocate request is rejected.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The APPC verb SEND_DATA failed with the specified return code.
The Client sends a deallocate abend to the server to terminate the conversation.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The APPC verb RECEIVE_AND_POST failed with the specified return code.
The Client sends a deallocate abend to the server to terminate the conversation.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
An APPC RECEIVE returned an unexpected data_received or conversation status_received indicator.
The Client sends a deallocate abend to the server to terminate the conversation.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
There was insufficient free memory for the Client SNA protocol driver to receive data on the current conversation.
The Client sends a deallocate abend to the server to terminate the conversation.
Free up some memory and retry the transaction.
An attempt to set post semaphore for receiving conversation data failed.
The Client sends a deallocate abend to the server to terminate the conversation.
Contact your system administrator.
The server rejected the incoming attach because the Client or Client application specified a TP name that the server did not recognize.
The Client continues.
Ensure that the specified TP is installed on the server.
APPC could not allocate a conversation but retrying without intervention may succeed. APPC was probably unable to activate a link or a session.
The Client continues.
Retry the operation. If retrying does not succeed, see your APPC Programming Reference information for further information or contact your system administrator.
APPC could not allocate a conversation and intervention is required to correct the problem.
The Client continues.
Refer to your APPC Programming Reference information for further information or contact your system administrator.
The APPC verb PREPARE_TO_RECEIVE failed with the specified return code.
The Client sends a deallocate abend to the server to terminate the conversation.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The APPC verb RECEIVE_IMMEDIATE failed with the specified return code.
The Client sends a deallocate abend to the server to terminate the conversation.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
An APPC RECEIVE returned an unexpected data_received or conversation status_received indicator.
The Client sends a deallocate abend to the server to terminate the conversation.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The APPC verb SEND_DATA with DEALLOCATE type failed with the specified return code.
The Client sends a deallocate abend to the server to terminate the conversation.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The TP program was invoked because of an inbound allocate request but the IBM Communications Manager definition for the TP program has an invalid number of parameters defined.
The inbound allocate request is rejected.
Refer to the Administration book, correct the TP definition, and retry.
The TP program was invoked because of an inbound allocate request but the IBM Communications Manager definition for the TP program has an invalid TP name parameter defined.
The inbound allocate request is rejected.
Refer to the Administration book, correct the TP definition, and retry.
The APPC verb RECEIVE_IMMEDIATE failed with the specified return code after some data had already been received.
The Client sends a deallocate abend to the server to terminate the conversation.
Try altering the 'SnaRetryCount' parameter in the configuration file ctg.ini and retry. Refer to the Administration book.
The APPC verb POST_ON_RECEIPT failed with the specified return code.
The Client sends a deallocate abend to the server to terminate the conversation.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The partner LU name specified in the 'NETNAME' parameter in your configuration file was not qualified by the SNA network name (NETID). The format is NETID.LU_NAME.
The connection to the partner LU is not started.
If using real LU names, correct the 'NETNAME' parameter and retry. If using alias LU names, set the 'PARTNERLUALIAS' parameter to 'Y' and retry.
The attempt to allocate a session to the specified server was unsuccessful after the number of retries specified in your configuration file ctg.ini.
The Client continues.
Contact your system administrator.
A temporary failure prematurely ended the conversation.
The Client continues.
Retry the operation. If retrying does not succeed, see your APPC Programming Reference information for further information, or contact your system administrator.
A permanent failure prematurely ended the conversation. The link to the server has probably failed.
The Client continues.
Refer to your APPC Programming Reference information for further information or contact your system administrator.
The APPC verb CNOS failed with the specified return code. The connection to the specified server has not been started.
The Client continues.
Refer to your APPC Programming Reference information for further information, or contact your system administrator.
The APPC verb CNOS failed because the local maximum session limit of the partner LU is 0. The connection to the specified server has not been started.
The Client continues.
Refer to your APPC Programming Reference information for further the particular error, or contact your system administrator.
The APPC verb CNOS failed as the partner LU does not recognize the specified mode name. The connection to the specified server has not been started.
The Client continues.
Refer to your APPC Programming Reference information for further the particular error, or contact your system administrator.
The Client SNA protocol driver was unable to open a link to the specified server because SNA server has no active services.
The Client continues.
Activate the relevant service via SNA Server Administration or contact your system administrator.
The Client SNA protocol driver was unable to open a link to the specified server because it failed to register itself with the currently installed Windows APPC implementation.
The Client continues.
Contact your system administrator.
The Client SNA protocol driver was unable to open any link using this LU because it is not defined on an active SNA service/node.
The Client continues.
Activate the relevant service SNA service or define the LU to an active SNA service/node or correct the 'LocalLUName' parameter in your configuration file ctg.ini and retry.
The Client SNA protocol driver was unable to open any link using this partner LU because it is not defined in a connection with the specified local LU on an active SNA service/node.
The Client continues.
Define a connection between the specified local and partner LUs on an active SNA service/node or correct the 'NetName' parameter in your configuration file ctg.ini and retry.
APPC could not execute the verb because a component of the product providing the SNA transport could not be loaded or terminated whilst processing the verb.
The Client continues.
Contact your system administrator.
LoadLibrary failed, the Client could not load the specified dynamic link library.
The Client SNA protocol driver is not loaded.
Install and configure one of the supported products for SNA transport, if this has not already been done, and ensure that the DLL is in the LoadLibrary search path; then retry. Or contact your system administrator.
APPC could not start a remote TP program retrying without intervention may succeed.
The Client continues.
Retry the operation. If retrying does not succeed, see your APPC Programming Reference information for further information or contact your system administrator.
APPC could not start a remote TP program and intervention is required to correct the problem. The remote server is probably not available.
The Client continues.
Ensure the remote server is available and if the problem persists see your APPC Programming Reference information for further information or contact your system administrator.
The APPC verb RECEIVE_ALLOCATE failed as SNA Server has not been correctly configured to receive inbound ATI requests.
The Client continues.
If inbound ATI request processing is required, refer to the Administration book on how to configure SNA Server.
The SNA node has not been started.
The Client continues.
Start the SNA node and retry the operation.
Local LU names must be specified as alias names in the configuration file ctg.ini.
The connection to the SNA server is not started.
Specify the local LU name in the configuration file ctg.ini as an alias name, set the parameter 'LOCALLUALIAS' to 'Y' and retry.
Either the APPC provider has abended or has not been configured properly on the Client machine.
The connection to the server is not started.
Check the configuration of the APPC provider on the CICS Client machine. If using NWSAA v2.2, check that the NDS configuration for the NWSAA Client is correct.
The specified LU alias is not defined in the APPC provider.
The connection to the server is not started.
If using alias LU names, define the LU alias and retry. If using real LU names, set the 'LOCALLUALIAS' parameter to 'N' in the configuration file and retry.
If using real LU names, the specified mode is not defined. If using alias LU names, either the partner LU alias supplied in the 'Netname' parameter in the configuration file ctg.ini is not defined, or the mode is not defined, in the APPC provider.
The connection to the server is not started.
Check that the parameters in the configuration file ctg.ini match the definitions in the APPC provider.
There has been a failure to allocate a conversation or to receive data from the specified server. The link to the server has probably failed.
The Client continues.
Refer to your APPC Programming Reference information for further information or contact your system administrator.
The specified TP program abended on the given server. If the TP program is CTIN, then this may be because the server has been recycled since running CCIN.
The Client continues. If the TP program is CTIN, the Client will attempt to reconnect to the server and retry the request.
Contact your system administrator.
An attempt to wait on a semaphore for conversation data, after successful completion of the receive verb, failed.
The Client sends a deallocate abend to the server to terminate the conversation.
Contact your system administrator.
The protocol driver's attempt to notify the Client of a data event failed.
The protocol driver sends a deallocate abend to the server to terminate the conversation.
Contact your system administrator.
The protocol driver's callback function was called for the specified conversation, but it was not in the list of conversations for which a RECEIVE_AND_POST call had been made.
The event is ignored.
Contact your system administrator.
The protocol driver requires the named environment variable to be defined.
The Client SNA protocol driver is not loaded. Error messages are written to the SNA error log.
Refer to the configuration documentation for the SNA transport product. A number of environment variables must be correctly defined for the correct operation of SNA protocol driver. Stop the Client, make sure the named variable is correctly defined in the environment where the Client will run; and then retry.
Environment variable name caused an error in the Client daemon.
The Client daemon continues, if possible.
Check that the value of the name environment variable is correct.
In the configuration file in the SERVER SECTION for server name , the combination of values for the specified parameters is not supported by the SNA protocol driver.
The server name fails to start.
Correct the errors by running the configuration tool.
A call to the UNIX System Services API __smf_record failed with ENOMEM, which indicates that it did not have enough memory available.
This message is logged. All data in the SMF record is lost.
See the CICS Transaction Gateway Information Centre for details on dealing with out of memory errors.
The Gateway daemon attempted to write a record to SMF. The Unix System Services call __smf_record failed with reason code JRSMFNotAccepting, indicating that SMF is not accepting records.
This message is logged. All data in the current SMF record is lost.
Contact the systems administrator responsible for SMF. For further details on the error code see the C/C++ Run-Time Library Reference book, and refer to the section describing the __smf_record() call.
A call to retrieve information regarding the storage characteristics of the current address space has failed. The return code and reason code is included in the message text as encoded as a hexadecimal string. The most significant half-word represents the return code (0 = OK, 4 = WARNING, 8 = ERROR). The least significant half-word represents the reason code.
This message is logged. The SE resource group statistics which are specific to the z/OS platform will not be updated.
If the return and reason data is 0x00085008, then there has been a failure to allocate the memory required to store the data. See the CICS Transaction Gateway Information Centre for details on dealing with out of memory errors. If the messagereports any other non-zero return and reason code, contact your service organization.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) has an internal error reading the passed parameters.
The utility fails to run.
Contact your service organization.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) takes either 1,2 or 3 parameters. See other messages for the command format.
The parameters were incorrect, and the utility fails to run.
Check the format of the command used and retry.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) takes either 1,2 or 3 parameters. See other messages for the command format.
The parameters were incorrect, and the utility fails to run.
Check the format of the command used and retry.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) takes either 1,2 or 3 parameters. See other messages for the command format.
The parameters were incorrect, and the utility fails to run.
Check the format of the command used and retry.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) takes either 'R' or 'D' as its first parameter. See other messages for the command format.
The parameters were incorrect, and the utility fails to run.
Check the format of the command used and retry.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Ready' function of Automatic Restart Manager (ARM) as one of the last phases of registering with ARM. ARM rejected the call.
The utility will terminate.
An explanation of the reason code returned by the 'Ready' request to ARM can be found in the 'z/OS MVS Programming: Sysplex Services Reference' manual.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Registration' function of Automatic Restart Manager (ARM) as the first phase of registering with ARM. ARM rejected the call.
The utility will terminate.
An explanation of the reason code returned by the 'Registration' request to ARM can be found in the 'z/OS MVS Programming: Sysplex Services Reference' manual.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Wait' function of Automatic Restart Manager (ARM) as the 'Register' request to ARM indicated that this was a restart. ARM rejected the call.
The utility will terminate.
An explanation of the reason code returned by the 'Wait' request to ARM can be found in the 'z/OS MVS Programming: Sysplex Services Reference' manual.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Deregistration' function of Automatic Restart Manager (ARM) to deregister with ARM. ARM rejected the call. This is a non-fatal error.
The utility will terminate.
An explanation of the reason code returned by the 'Deregister' request to ARM can be found in the 'z/OS MVS Programming: Sysplex Services Reference' manual.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Deregistration' function of Automatic Restart Manager (ARM) to deregister with ARM. ARM rejected the call because this job was not registered with ARM.
The utility will terminate.
No further action is required.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Registration' function of Automatic Restart Manager (ARM) as the first phase of registering with ARM. ARM rejected the call because the ARM_ID was not unique in the sysplex.
The utility will terminate.
Choose a sysplex unique id and re-run the utility.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Registration' function of Automatic Restart Manager (ARM) as the first phase of registering with ARM. ARM rejected the call because the ARM_ID did not conform to the character restrictions.
The utility will terminate.
Check the value in the ARM_ID parameter against the restrictions given by other messages.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Registration' function of Automatic Restart Manager (ARM) as the first phase of registering with ARM. The call to ARM failed because ARM was not active on the sysplex.
The utility will terminate.
Investigate why ARM is not running.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Registration' function of Automatic Restart Manager (ARM) as the first phase of registering with ARM. ARM rejected the call because only started jobs can register.
The utility will terminate.
The utility may have been called from the USS command line or as part of a USS script. The utility can run successfully only when called from BPXBATCH with a PGM= parameter. Refer to the CTG Administration book for JCL examples.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) called the 'Registration' function of Automatic Restart Manager (ARM) as the first phase of registering with ARM. ARM rejected the call because the ARM_TYPE did not conform to the character restrictions.
The utility will terminate.
Check the value in the ARM_TYPE parameter against the restrictions given by messages.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) Registration command takes a required parameter (ARM_ID) that is up to 16 characters long. See other messages for the command format.
The parameter is incorrect, and the utility fails to run.
Check the format of the command used and retry.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) Registration command takes an optional parameter (ARM_TYPE) that is up to 8 characters long. See other messages for the command format.
The parameter is incorrect, and the utility fails to run.
Check the format of the command used and retry.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) has an internal error calling the CSVQUERY macro.
The utility terminates.
Contact your service organization.
CICS Transaction Gateway Automatic Restart Manager Batch Utility (ctgarm) must be APF authorized in order to register with ARM. This should happen during installation.
The utility terminates.
See the installation instructions in the CTG Administration book for details of how to APF authorize ctgarm.
The install requires the use of the command: command name , but this is not in the current PATH.
The install will terminate.
Identify where this command is on your system. Add its location to your PATH and retry the install. See the Problem Determination section in the Administration book for your platform for further information.
CICS Transaction Gateway supports a number of language and code set combinations, but the specified language code is not supported on this platform.
The message language will not be changed.
Run the 'ctgmsgs' command with the '-?' parameter to get a list of supported language and code set combinations. Choose the combination that best meets your requirements and retry with that combination.
CICS Transaction Gateway supports a number of language and code set combinations, but the specified code set is not supported on this platform.
The message language will not be changed.
Run the 'ctgmsgs' command with the '-?' parameter to get a list of supported language and code set combinations. Choose the combination that best meets your requirements and retry with that combination.
The Java applications supplied with CICS Transaction Gateway require a minimum level of JVM.
The application will not start.
See the Administration book for details of the versions of Java supported. Install the correct level of Java and add access to it from the PATH.
CICS Transaction Gateway on z/OS uses the 'ctgenvvar' script to initialize environment variables before executing its Java component. If the CTGENVVAR environment variable is set, then the ctgstart script will attempt to run that script. Note that the CTGENVVAR variable is intended for use only when the Gateway daemon is started under a Unix System Service shell (as opposed to batch).
The CICS Transaction Gateway will not start.
Verify that the file HFS path is correct. If this value is as expected, then verify that the file is place. Note that the value of CTGENVVAR is a HFS path, and therefore case-sensitive.
ctgmsgs4local was called to convert the CICS Transaction Gateway to the local code page, but it is already installed for that code page.
The script terminates.
No further action as CICS Transaction Gateway is in the local code page as requested.
The script that is running is incomplete. This indicates that there was an error during packaging.
The script terminates.
Contact your service organization.
The script that is running is unable to identify a supported operating system using the text output from the 'uname' command. Either the product is being run on an unsupported platform, or an update to the operating system version has changed this text in an unexpected way.
The script terminates.
Contact your service organization.
CICS Transaction Gateway is packaged for a number of different operating systems. This package is for the operating system identified by the string target . An operating system version check (uname) shows the operating system you are running to be actual and so the installation cannot continue.
The script terminates.
Remove the current installation and install the correct package for your operating system. If you believe that you have installed the correct package, contact your service organization.
CICS Transaction Gateway for z/OS can only communicate with CICS in a local region (EXCI is the only protocol provided). As CICS will not run under z/OS.e, there cannot be a local CICS region to communicate with. For this reason CICS Transaction Gateway is not supported on the z/os.e operating system.
The script terminates.
Remove the current installation and install it on a system running a full version of z/OS.
The script is unable to identify the runtime operating system as a command substitution using 'uname' has returned an empty string. This can be due to the temporary file system being inaccessible for write by the executing userid, or simply being full. The temporary file system is located at /tmp by default, but can be overridden by the TMPDIR environment variable.
The script terminates.
Ensure that the userid executing the script has write access to the tmp filesystem, and that the tmp filesystem is not full. If both of these requirements are satisfied and the problem persists, then contact your service organization.
When trying to run a Java application, the Java runtime classes could not be found.
The command line application terminates.
Install the Java Virtual Machine (JVM) correctly.
The CICS Transaction Gateway could not execute the command. Either the CICS TG is not correctly installed, or the environment is not setup correctly.
The application terminates.
Check for exceptions that indicate a problem with the environment. If there are no obvious problems, reinstall the CICS TG.
The Operating System you are running, as detected by the JVM, is unsupported.
The application terminates.
Ensure that you are running a supported Operating System.
The migration tool ctgconvenv cannot find the specified file, or the file does not have execute permission for this user. The syntax of the command is: ctgconvenv ['wrap width'] ['source file name'] where: ['wrap width'] is the width of the generated output and is a value in the range 40 to 120. The default is the terminal screen width. ['source file name'] is the ctgenvvar script to be converted. If the source file name is not fully qualified, the default directory is the <install_path>/bin directory. If the source file name is not specified, a filename of ctgenvvar is assumed. Output is written to stdout. This can be redirected to a file by standard operating system facilities.
The ctgconvenv application terminates.
If the specified file exists but is not executable, correct the file permissions and retry. If the displayed file name is not correct, retry the command using the full HFS file name.
An attempt was made to start the Gateway daemon in the background, but a valid configuration file could not be found at the specified location.
The Gateway daemon does not start.
Check that a valid file exists. Refer to the Administration book for details on the format and location of ctgd.conf.
A running instance of the CICS Transaction Gateway could not be found by ctgd.
The Gateway daemon, if running, does not stop.
Ensure the administration port specified in ctgd.conf matches that of the running Gateway daemon, or manually kill the processes if the Gateway daemon is still running.
The Gateway daemon will attempt to use the default configuration file 'ctg.ini' or 'CTG.INI' in the product bin directory. This is a compatibility feature and not the recommended configuration style.
The ctgstart script continues. If a Gateway daemon configuration file does not exist in the product bin directory, then the initialization will fail.
Verify the intended location of the Gateway daemon configuration file and set the CICSCLI environment variable if required.
The ctgstart script has determined that the environment variable '_BPX_SHAREAS' has not been defined.
The ctgstart script continues.
If the environment variable _BPX_SHAREAS is not set, then whether or not the Gateway daemon runs in a single address space will be subject to the system default. Verify your preferred setting for _BPX_SHAREAS and add the appropriate definition to the environment variable configuration. The recommended setting is _BPX_SHAREAS=YES.
The ctgstart script has determined that the environment variable 'CTG_SWAPPABLE' has been defined as 'YES'.
The ctgstart script continues.
Setting CTG_SWAPPABLE to 'YES' allows the Gateway daemon address space to be swapped out by z/OS. This is not a recommended configuration for the Gateway daemon. Consider either removing CTG_SWAPPABLE from the environment variable configuration (allowing it to default to NO), or explicitly define it with the value 'NO'.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has an internal error and can not read the parameters passed to it.
The utility fails to run.
Contact your service organization.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has an internal error calling the ASCRE macro.
The utility fails to run.
Contact your service organization.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has not been installed correctly as it must be APF Authorized to execute.
The utility fails to run.
Refer to the SMP/E Program Directory.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has an internal error calling CSVQUERY macro.
The utility fails to run.
Contact your service organization.
The user ID used to run the CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has insufficient authority to the 'CTG.RRM.SERVICES' entity of the 'FACILITY' class.
The utility fails to run.
Check that the user ID has been granted the correct level of access. See the CICS TG Administration book for details.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) cannot shutdown the CTGRRMS services because they are not running.
The utility ends.
To start the CTGRRMS services, use the ctgasi command without the refresh or shutdown options.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has an internal error creating a name token pair used by the CTGRRMS services.
The utility fails to run.
Contact your service organization.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has an internal error deleting a name token pair used by the CTGRRMS services.
The utility fails to run.
Contact your service organization.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has an internal error accessing the event control blocks (ECBs) used to communicate between address spaces as part of the initialization of the CTGRRMS services.
The utility fails to run.
Contact your service organization.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) was called with an incorrect parameter parameter .
The utility fails to run.
See messages (CTG6221I onwards) for the command format.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has been called to do a refresh but there are still number users registered as using the CTGRRMS services. This can be caused by failing programs not deregistering from the CTGRRMS services.
The utility ends.
Do not refresh the CTGRRMS services while there are active users. If the count of users is incorrect, a refresh can be forced by using the '-f' option to override this check.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has an internal error after calling ASCRE to initialize the CTGRRMS services. CTGINIT has posted the return code return code .
The utility fails to run.
Contact your service organization.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) was called to dump the internal trace table for CTGINIT. There is no trace table to dump out, because the CTGRRMS services have not been started.
The utility fails to run.
To start the CTGRRMS services, use the ctgasi command without the dump option.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has been called to do a refresh but there is an internal error with the CTGRRMS services. The CTGRRMS services cannot be used to determine the number of active users.
The utility ends.
You should not refresh the CTGRRMS services while there are active users, but because the services seem to be severely corrupted, a refresh can be forced by using the '-f' option to override this check.
The CICS Transaction Gateway Address Space Initiator Utility (ctgasi) has been called to do a refresh but there is an internal error with the CTGRRMS services. The CTGRRMS services cannot be used to determine the number of active users.
The utility ends.
You should not refresh the CTGRRMS services while there are active users, but because the services seem to be severely corrupted, a refresh can be forced by using the '-f' option to override this check.
The CICS Transaction Gateway Resource Recovery Management Service services (CTGRRMS) have failed due to an internal error.
The services have failed.
Contact your service organization.
The CICS Transaction Gateway Resource Recovery Management Service services (CTGRRMS) have failed due to an internal error.
The services have failed.
Contact your service organization.
The CICS Transaction Gateway Resource Recovery Management Service services (CTGRRMS) have failed due to an internal error.
The services have failed.
Contact your service organization.
The CICS Transaction Gateway Resource Recovery Management Service services (CTGRRMS) have failed because the version of CICS Transaction Gateway trying to initialize the services (ctgasi) is more recent than can be supported by the back level code (CTGINIT) in the LNKLST.
The services have failed.
Ensure that the most recent version of CTGRRMS services (CTGINIT) is in the LNKLST. See the CTG Administration book for details.
An internal error prevented statistic statistic from being registered with the CICS TG.
The statistic is not available through ctgadmin, SDSF or the statistics API.
Contact your service organization.
An internal error prevented statistic statistic from being updated.
The statistic is not available through ctgadmin, SDSF or the statistics API.
Contact your service organization.
An internal error prevented statistic group statistic group from being created.
No statistics for the statistic group will be available through ctgadmin, SDSF or the statistics API.
Contact your service organization.
The configuration file contains an entry sotimeout. This setting (Handler wakeup timeout field in the Configuration Tool) used to define the time that might have to elapse before the Gateway daemon could shut down. It became redundant when Version 6 of the CICS TG introduced shutdown commands, and from Version 7 is no longer supported.
The Gateway daemon continues its initialization process.
To suppress this message in future, remove any reference to sotimeout from the configuration file. Open the configuration file in the Configuration Tool and then save it.
The Gateway daemon terminated abnormally.
This message is ouptut and the Gateway daemon ends.
Consult the log for the causes of this problem, correct the problem, and restart the Gateway daemon.
The maximum number of Worker threads was previously configured as unlimited, or to a valuewhich exceeded the number of EXCI pipes available to the CICS TG.Requests fail if the number of Worker threads exceeds the EXCI pipe limit.The maximum number of Worker threads has been reduced.
The maximum number of Worker threads has been set to equal the maximum number of EXCI pipes available.
To prevent a warning message for this error choose one of the following options:configure the maximum Worker threads to less than or equal to the EXCI pipes logon limitor, increase the EXCI logon limit to greater than, or equal to, the number of Worker threads.
The statistics interval length (statint) value could not be parsed
The statistics interval length value is set to the default
The statistics interval length (statint) value should be in the format HHMMSS, where HH is the number of hours in the range 00-24, MM is the number of minutes in the range 00-59 and SS is the number of seconds in the range 00-59
The statistics interval length (statint) value, specified in the configuration file, is not valid. The interval length must be between 1 minute (000001) and 24 hours (240000)
The statistics interval length value is set to the default
The statistics interval length (statint) value should be in the format HHMMSS, where HH is the number of hours in the range 00-24, MM is the number of minutes in the range 00-59 and SS is the number of seconds in the range 00-59.
The statistics end of day (stateod) value could not be parsed
The statistics end of day value is set to the default
The statistics end of day (stateod) value should be in the format HHMMSS, where HH is the number of hours in the range 00-23, MM is the number of minutes in the range 00-59 and SS is the number of seconds in the range 00-59
The statistics end of day (stateod) value, specified in the configuration file, is not valid. The end of day value must be between midnight (000000) and one second before midnight (235959)
The statistics end of day value is set to the default
The statistics end of day (stateod) value should be in the format HHMMSS, where HH is the number of hours in the range 00-23, MM is the number of minutes in the range 00-59 and SS is the number of seconds in the range 00-59
An internal error prevented statistic group statistic group from being added to the current interval statistics.
The statistic group will be not be included in the interval statistics.
Contact your service organization.
Communications problems between the Gateway daemon and CICS have been reported to the workload manager. No new work will be sent to the Gateway daemon until the problems are resolved and the health value is reset.
The Gateway daemon continues.
1. Check the logs to determine the cause of the communications problems and take corrective action. 2. Reset the health value; see the information center for details.
The configuration file contains the setting healthreporting=ON, indicating that the state of communications between the Gateway daemon and CICS should be reported to the TCP/IP workload manager. An error with return code $1 prevents health reporting from being enabled.
The Gateway daemon continues.
Investigate the cause of the problem. If health reporting cannot be enabled on your system, for example because the version of z/OS does not support it, remove the entry from the configuration file.
The keyringpw parameter has been supplied without a user keyring also being specified.
CICS Transaction Gateway ignores the keyringpw parameter and continues the startup process.
In order to use the keyringpw parameter, a keyring must be specified.
A request has been flowed to the CICS Transaction Gateway. This is not allowed while the Gateway daemon is shutting down.
The Gateway daemon continues processing outstanding work during the shutdown process.
Check with your System Administrator as to when the CICS Transaction Gateway will be available again.
The configuration file contains the deprecated parameter 128bitonly as well as explicitly listed cipher suites. When selecting cipher suites for the SSL protocol handler to use, you must explicitly list each cipher suite in the configuration file.
The handler continues to start using the cipher suites that are explicitly listed. The cipher suites referenced by the 128bitonly parameter are not enabled unless they are explicitly listed in the configuration file.
Remove the 128bitonly parameter from the configuration file and restart the Gateway daemon to remove this warning message.
None of the cipher suites specified in the configuration file are available for use by the CICS Transaction Gateway.
The SSL protocol handler fails to start.
Ensure that the configuration file specifies only cipher suites that are available to the level of Java used by the CICS Transaction Gateway.
Requesting that only 128 bit cipher suites are used through the use of 'ciphersuites=128bitonly' has been deprecated and might be removed at a later date.
The SSL protocol handler is started and configured to only use the 128bit cipher suites that are documented in the Administration book.
Use the Configuration Tool to explicitly list the cipher suites you want the SSL protocol handler to use.
The specified cipher suite cipher cannot be used by the CICS Transaction Gateway for SSL connections.
The handler continues to start using the cipher suites that are supported.
Correct the cipher suites in the configuration file and restart the Gateway daemon to remove this warning message.
A password has been specified using the keyringpw parameter in the configuration file ctg.ini, at the same time as the esmkeyring parameter.
The protocol handler is started but the password provided is not used to try and read the key ring from the ESM provider.
Remove the keyringpw parameter if the key ring is stored in an ESM implementation, or the esmkeyring parameter if the key ring file is stored in the HFS.
A protocol string for either SystemSSL or SystemHTTPS is in the configuration file ctg.ini.
The Gateway daemon continues but does not start the specified protocol handler.
Migrate to JSSE-based SSL and HTTPS handlers and then remove the protocol strings from the configuration file, either manually or by loading the file into the Configuration Tool and saving it.
The CICS Transaction Gateway could not start.
The Gateway daemon process ends with a non-zero return code.
Check the logs for error messages and correct any reported problems.
A client has disconnected from ConnectionManager ConnectionManager , but count work requests are still in progress.
A ConnectionManager will not become available to handle another connection until the work has been finished.
Wait for requests to finish.
A client has disconnected from ConnectionManager name , but count requests which require completion are still outstanding.
The ConnectionManager will attempt to clean up the allocated resources.
For information only.
Where protocol specifies the protocol type, and RC specifies the cause of the error. The most likely cause is that the protocol handler is attempting to listen on a TCP/IP port that is already in use.
The Gateway daemon is forced to stop because of protocol protocol handler error.
Check the configuration settings of the protocol handler.
A client has disconnected from ConnectionManager name , with work requests in progress. count requests have failed to finish within a reasonable time.
The ConnectionManager marks itself as available again.
For information only.
The Gateway worker thread name was unable to send the reply to the client. This could be because the client was disconnected.
System action is not required.
Check if client is still running.
The client at client has been idle for too long, but there are still work requests in progress on its behalf.
ConnectionManager did not disconnect the client.
For information only.
Where reason specifies the reason for the failure.
The Gateway stops; it will not run without a configuration file.
Check that ctg.ini exists in the bin directory, or that the configuration file specified through the CICSCLI environment variable exists. Run the configuration tool if necessary to create a configuration file.
Configuration file ctg.ini contains entries for the TCPAdmin protocol, which is no longer supported.
The Gateway daemon continues its initialization process.
To prevent this message occuring in future, use the Configuration tool to open and then save your configuration file. This removes the invalid entries.
The specified command line parameter has an invalid value.
The CICS Transaction Gateway fails to start.
Ensure that the value is valid for the given parameter. Refer to the Administration book for details.
The display of symbolic hostnames might affect system performance.
The Gateway daemon continues processing.
Deselect the option to display TCP/IP hostnames using the configuration tool, or edit the configuration file and set NONAMES=ON, to avoid this. Refer to the CICS Transaction Gateway Administration book for further details.
Gateway is unable to recognize port number.
System action is not required.
Check valid port number, protocol and server name.
Usually this means that the system is running low on resources.
System action is not required.
Reduce the number of ConnectionManager and Worker threads initially created.
A connection was accepted from server , but a problem of type error occurred.
Unable to connect.
Check error code.
Where ConnectionManager specifies the ConnectionManager thread.
Unable to execute request.
Check if connection is still available.
Where worker thread specifies the Worker thread.
System action is not required.
For information only.
Where worker thread specifies the Worker thread.
Unable to write reply.
Check if connection is still available.
A problem has occurred in the CICS Transaction Gateway local mode support.
The CICS Transaction Gateway is unable to process the request.
Check the Gateway protocol settings.
An error occurred while processing request with name [name ]
System action is not required.
Check that request is valid.
Gateway cannot access any protocol handlers.
If no protocol handlers can be started, the Gateway will exit.
Check the CTG initialization file for protocol handlers; uncomment the protocol handle you want.
An exception of type [type ] occurred.
System action is not required.
For information only.
ConnectionManager name has received a request type but failed to load the required class file to execute the request.
Gateway exits and displays error message.
Make sure that the type class is in the CLASSPATH of the Gateway process.
The class class could not be successfully loaded to provide security to the connection from name .
The connection will be closed.
Make sure that the class class is in the CLASSPATH of the Gateway process.
A connection was accepted from name , but a ConnectionManager did not become available in time.
The connection was rejected.
Increase the maximum number of ConnectionManagers.
The name protocol handler exited due to problem description .
Gateway exits and displays error message.
Check error code.
The protocol protocol handler has been stopped because of errors on 50 consecutive socket accept calls. This can happen if the TCP/IP stack is stopped while the Gateway daemon is running. Exceptions from the failed accept attempts have been logged; the exception messages give additional information on the nature of the error.
The Gateway daemon continues without this protocol handler. An attempt to restart the protocol handler will be made within 30 seconds. If this fails further restarts will be attempted every 30 seconds.
Check the logged exceptions and correct the cause of the socket errors.
File with name filename could not be opened.
System action is not required.
Check that file is not in use or read-only.
An unknown parameter starting with the specified text was encountered in the configuration file ctg.ini.
The Gateway daemon terminates.
Correct the configuration file error and restart the Gateway daemon. The configuration tool can be used to correct a badly-formed configuration file.
An error was detected.
The Gateway daemon terminates.
Examine any other messages and the Gateway error log to determine the cause of the error.
An unknown option starting with specified text was encountered on the command line.
The Gateway daemon terminates.
Restart CICS Transaction Gateway with a correct command line option. Use 'ctgstart -?' to obtain a list of supported options, or refer to the Administration book.
The configuration file ctg.ini contains the adminport parameter, or the Gateway daemon was started and the -adminport command line parameter was specified. The Gateway daemon on z/OS does not support this parameter, which was ignored.
The Gateway daemon continues its initialization process.
To prevent this message occuring in future, remove the adminport parameter from configuration file ctg.ini. Edit the file manually, or use the Configuration tool to open and then save the file. This removes the parameter, providing you run the Configuration tool on z/OS, or specify the -plat z/OS or -plat 390 option if running it on a different platform.
The default directory contains both uppercase and lowercase versions of the configuration file.
The Gateway daemon will use the default file 'ctg.ini' as no configuration filename has been specified. The contents of file 'CTG.INI' will be ignored.
To avoid this warning being issued, explicitly specify a configuration file or delete file 'CTG.INI' from the default directory. For details of how to specify a configuration file see the Configuration chapter of the Administration book.
Java Client application unable to connect to Gateway daemon.
Java Client application is not started.
If running the Gateway daemon, check whether the Java Client application has specified the correct parameters to connect to the Gateway daemon.
Where IP address specifies the Gateway daemon TCP/IP address, port specifies the TCP/IP port and error specifies the cause of the error.
Java Client application is not started.
If running the Gateway daemon, check whether the Java Client application has specified the correct parameters to connect to the Gateway daemon.
Java Client application could not start the Gateway daemon listener.
Java Client application is not started.
Close this JavaGateway instance and check that Gateway daemon is correctly configured.
The Gateway daemon is unreachable.
Close this JavaGateway instance.
Check if the connections to the Gateway daemon still exist.
Where error specifies the cause of the error.
Close the Gateway daemon.
Check error code.
Where error specifies the cause of the error.
Unable to read the reply.
Check error code.
Network connection did not contain the correct identifier.
Connection closed.
For information only.
The Gateway daemon URL was incorrectly specified.
Unable to connect to Gateway daemon at this address.
Check Gateway daemon is running and address is right.
Attempts have been made to use the local mode support after the LocalJavaGateway.terminate method has been called.
Unable to make further local mode requests.
For information only.
The LocalJavaGateway.terminate method has been called while local mode applications are still in use.
Wait for requests to finish.
For information only.
Where error specifies the cause of the error.
Unable to copy reply.
Check error code.
A call to a JavaGateway.set method has been made, after the JavaGateway has been opened.
System action is not required.
Close JavaGateway instance.
This JavaGateway instance is already open in the Java Client application.
System action is not required.
Close this JavaGateway instance.
No protocol classes have been requested by the Java Client application.
Unable to make further requests to this instance.
Check that the Java Client application specifies a valid protocol parameter.
The JavaGateway URL specified an unsupported protocol.
The JavaGateway object is not initialized.
Ensure the Gateway URL is of the form 'protocol://host', where protocol is a supported protocol name. Refer to the Administration book for details of supported protocols.
The JavaGateway instance was closed by the Java Client application.
Unable to make a further request to this instance.
Start new JavaGateway instance.
Where error specifies the cause of the error.
Unable to make further request to this instance.
Check error code.
Where error specifies the cause of the error.
Unable to write further requests to this instance.
Check error code.
Caused by error
Unable to make initial handshake; hence unable to make requests.
Check error code.
Th server application needs security.
Unable to make requests because of lack of security.
Specify both client and server side security classes.
Where error specifies the cause of the error.
System action is not required.
Check error code.
The Java Client application has not opened a new JavaGateway instance yet.
System action is not required.
Open JavaGateway instance before making requests.
The Java Client application must specify both the SSL_PROP_KEYRING_CLASS and SSL_PROP_KEYRING_PW properties when attempting to establish an SSL connection to the CICS Transaction Gateway. The connection is not created.
System action is not required.
Change the application to specify both required properties and then retry.
An attempt has been made to set socket connection timeout with a negative value. The existing value has not been updated.
System action is not required.
Ensure the socket connect timeout is only either a positive value or zero.
The ctgjni library could not be initialized. The associated error gives more information about the cause.
The CICS Transaction Gateway fails to start.
If the associated error indicates a problem locating the JNI library, ensure that it is available on the path shown by the error. If the associated error indicates a security exception ensure that the library has the correct access privileges. If the associated error indicates that the EXCI is unavailable, check the JNI log for further details. After the error has been resolved start the CICS Transaction Gateway.
Unable to import key ring.
System action is not required.
Ensure correct key ring and password has been provided.
Where error specifies the Java error.
Unable to load native library.
If running on z/OS.e, this message indicates that you have specified the local: protocol. Specify a remote protocol; the local: protocol is not supported on z/OS.e. On operating systems other than z/OS.e, check that the specified native library is available.Also check that the CICS TG application classes on the CLASSPATH are the same version as the native library specified.
The exit key parameter indicated was not a valid AID value. Valid AID keys are enter, clear, PF1 - 24, and PA1 - 3.
Unable to execute command.
Check if AID key is valid.
CICS Server return code return code is not valid.
System action is not required.
Check if Cics_Rc is valid.
Where error specifies the Java error.
CICS Request revolted.
Check the Java error.
The codepage specified for the conversion was code page .
A CICS Request attempted to convert between a C byte array and a Java String. The codepage being used for the conversion was code page .
Check user codepage.
Where error specifies the error.
CICS Request revolted.
Check error.
An attempt was made to obtain the Java default character encoding. error specifies the Java error.
System action is not required.
Check the return Java error.
Either Call_Type ECI_GET_REPLY or Call_Type ECI_GET_REPLY_WAIT have been used. These types of call should be used with caution since they will return the next reply, which may be intended for another Java client.
System action is not required.
Use ECI_GET_REPLY and ECI_GET_REPLY_WAIT call types with caution.
The amount of data sent from the Java client to the CICS Transaction Gateway, is greater than the size of the Commarea given to CICS.
System action is not required.
Specify Larger Commarea.
The amount of data sent to the Java client from the CICS Transaction Gateway, is greater than the size of the Commarea given to CICS.
System action is not required.
Specify larger Commarea.
An invalid message qualifier parameter has been provided.
None.
Correct the value passed for message qualifier in the method invocation.
Either the Userid, Password or Server Name entered is longer than required.
System action is not required.
Re-enter the correct Userid, Password or Server name.
The size field may not exceed the length of the data array.
System action is not required.
Specify larger data array.
Unless using a local Gateway, it is invalid to attempt to get an event without specifying a termIndex, since you may obtain events intended for other terminal resources.
System action is not required.
Specify a termIndex.
The Gateway daemon was invoked under a 64-bit JVM.
This message is logged and the Gateway daemon fails to start.
Configure the Gateway daemon to use a non-64-bit JVM and restart the Gateway daemon.
The Gateway daemon Java classes are unable to load the CICS TG JNI native library DLL.
This message is logged. The Gateway daemon fails to start.
This might be because of a corrupted installation. Reinstall the CICS Transaction Gateway. If the problem persists contact your service organization.
Invalid call type passed to ECIRequest
System action is not required.
Check call type.
Commarea outbound length must always be a positive integer.
Could not create a Commarea outbound length of this size; default length is set.
Check if Commarea outbound length is a positive integer.
eci_timeout can only be 0 or a positive integer.
Could not set ECI timeout; default timeout is set.
Check if eci_time is a positive integer.
An attempt to connect a terminal failed as no JavaGateway or EPIGateway instance has been associated with that terminal instance.
None.
Create and Configure a JavaGateway or EPIGateway instance and use the appropriate methods or constructors to associate this instance with the instance of the terminal.
An attempt to use the extended Connect Methods on a terminal has failed. The Extended Connect methods can only be used on extended terminal instances.
None.
Use the standard connect method or create an extended terminal instance if you wish to use the extended connect methods.
An attempt to convert a CICS code page to a Java format, (for example, 850 to Cp850), failed. error is the Java error.
System action is not required.
Check the Java error and the CICS Code page.
Return code RC was received when attempting to invoke a security type method method
None.
Look up the return code to determine the cause of failure.
A Java encoding was specified for a terminal, but no equivalent host CCSid is known for this encoding.
None.
Check the documentation for the list of allowed Java encodings that have equivalent CCSid values.
Invalid call type passed to EPIRequest.
System action is not required.
Check call type.
Invalid event passed.
System action is not required.
Check event.
It is invalid to attempt to get an event without specifying a termIndex, since you may obtain events intended for other terminal resources.
System action is not required.
Specify a termIndex.
Where index is the invalid termIndex.
System action is not required.
Check that termIndex is available and unique to this connection.
Where index is the invalid termIndex.
System action is not required.
Check that termIndex is unique to this connection.
Where error is the error.
Exit application.
For information only.
An exception occurred while screen handler beans where being loaded from the path specified. Possible causes are: the classpath is incorrect, a screen handler bean did not have a public constructor , a file or directory could not be accessed.
System action is not required.
Check if classpath exist and classes are available.
An exception occurred while the specified class was being loaded. Possible causes are: the class could not be found, the class did not have a public constructor.
System action is not required.
Check exception and that class is available and has a public constructor.
Where exception is the exception.
System action is not required.
Check where exception has occurred.
More data was returned by CICS than could be handled.
System action is not required.
For information only.
An internal error has occurred. The terminal state is incorrect.
System action is not required.
For information only.
If a transaction ID parameter is passed to send, it must be a valid string.
System action is not required.
Check if a valid transaction ID is given.
An action was requested when the terminal was in the wrong state, for example: disconnect while the terminal was not idle.
Wait and try again after a fixed period of time.
Wait and try again after a period of time.
Either the row row number or the column (1} are off the screen.
System action is not required.
Check if either the row or the column are out of range.
The datastream received from CICS could not be parsed.
System action is not required.
For information only.
Transaction transaction failed to start, did not complete, or timed out.
None.
Check the Read Timeout value for the terminal if the transaction timed out. Check the Client and CICS server logs for more information on why the transaction failed.
Terminal could not be deleted.
Wait, then try again.
Check if terminal is still in use.
The attribute type type is not supported.
System action is not required.
Check attribute type.
The return code from the RRMS resource manager registration call (crggrm). The return code is in hexadecimal.
CICS Transaction Gateway processing continues.
If the return code is non-zero, contact your service organization for more information and diagnosis, or see the z/OS MVS Programming: Resource Recovery book, for details of the return code and any corrective action which should be taken. Common failing return codes are: 700 - CRG_RM_NAME_REGISTERED - The resource manager is already registered. 300 - CRG_RM_NAME_INVALID - The resource manager name is invalid. If the CICS TG registers as an unauthorized resource manager a .IBM.UA suffix is required. See the administration guide for details on which configurations the CICS TG registers as unauthorized and which characters are valid in an RM name.
This displays the return code from the RRMS set exit information call (crgseif). The return code is in hexadecimal.
If the return code is non-zero the Gateway daemon or ctgmaster process which encountered the problem fails to start.
If the return code is non-zero, contact your service organization for more information and diagnosis, or see the z/OS MVS Programming: Resource Recovery book, for details of the return code and any corrective action which should be taken.
If a zero length password is given then the return code is -2, otherwise this displays the return code from the __passwd call used to authenticate the username and password. If the return code is not zero then errno and errno2 were set by the call. Refer to the problem determination section of the z/OS Administration Guide for further details of security errors. Here is a brief list of possible return codes: 111 - EACCES - The password was not authorized. 121 - EINVAL - The userid or password was invalid. 143 - ESRCH - The userid was unknown or not defined to the kernel. 157 - EMVSERR - The __passwd is not supported in an address space where a load was done from an uncontrolled library. 163 - EMVSSAFEXTRERR - The userid access has been revoked. 164 - EMVSSAF2ERR - Internal processing error. 168 - EMVSEXPIRE - The password has expired. 169 - EMVSPASSWORD - The new password was not valid, or did not meet the installation-exit requirements.
If the return code is non-zero, a return code of ECI_SECURITY_ERROR will be returned to the application.
If the return code is non-zero, see the C/C++ Run-Time Library Reference book, and refer to the section describing the __passwd() call. More detail on the reason code can be found in the UNIX System Services Messages and Codes book.
The call to Retrieve Side Information Fast (atrrusf) failed with the specified return code. The return code is in hexadecimal.
A system error is returned on the associated ECI request.
Refer to the z/OS MVS Programming: Resource Recovery book, for details of the return code and any corrective action which should be taken. If the problem persists, contact your service organization.
The call to Retrieve Current Context Token (ctxrcc) failed with the specified return code. The return code is in hexadecimal.
A system error is returned on the associated ECI request.
Refer to the z/OS MVS Programming: Resource Recovery book, for details of the return code and any corrective action which should be taken. If the problem persists, contact your service organization.
The call to Switch Context (ctxswch) failed with the specified return code. The return code is in hexadecimal.
A system error is returned on the associated ECI request.
Refer to the z/OS MVS Programming: Resource Recovery book, for details of the return code and any corrective action which should be taken. If the problem persists, contact your service organization.
The call to Begin Context (ctxbegc) failed with the specified return code. The return code is in hexadecimal.
A system error is returned on the associated ECI request.
If the return code is non-zero, contact your service organization for more information and diagnosis, or refer to the z/OS MVS Programming: Resource Recovery book, for details of the return code and any corrective action which should be taken. A common failing return code is: 756 - CTX_AUTH_FAILURE - The resource manager is PKM 8-15 problem state and specified a resource manager token that does not belong to a PKM 8-15 problem state resource manager registered in the home address space. This may be due to CTG6806E with return code 700 - CRG_RM_NAME_REGISTERED - The resource manager is already registered.
The call to End Context (ctxendc) failed with the specified return code.
A system error is returned on the associated ECI request.
Refer to the z/OS MVS Programming: Resource Recovery book, for details of the return code and any corrective action which should be taken. If the problem persists, contact your service organization.
The call to GetStringPlatform has failed with the specified return code and information. This is an internal error.
CICS Transaction Gateway processing continues.
If the problem persists, contact your service organisation.
The call to GetStringPlatformlength has failed with the specified return code and information. This is an internal error.
CICS Transaction Gateway processing continues.
If the problem persists, contact your service organisation.
The EXCI call failed with the error codes displayed.
An error is returned to the Java Client application.
Refer to the CICS External Interfaces Guide for further information on the error. The EXCI function being performed is specified by the Function Call data in the message, which maps to the EXCI calls as follows; 1=Initialize_User, 2=Allocate_Pipe, 3=Open_Pipe, 4=Close_Pipe, 5=Deallocate_Pipe, 6=DPL_Request.
A request failed with a DPL specific error. The error codes returned by the DPL_REQUEST are displayed.
An error is returned to the Java Client application.
Refer to the CICS External Interfaces Guide for further information on the error.
An attempt was made to change the JNI trace filename whilst trace was running.
This message is logged. Tracing continues to the previous filename.
Deactivate JNI trace before changing the filename. If you want to enable JNI tracing when the CICS Transaction Gateway starts, ensure that you set the trace parameters only once. For example, do not specify both an environment variable setting and a Java directive setting.
This message is issued when an invalid EXCI call is being attempted. The only valid call types for use with EXCI are ECI_SYNC, ECI_STATE_SYNC and ECI_SYNC_TPN.
An error is returned to the Java Client application.
Use a call type that is supported on the z/OS platform.
The commarea length defined, or the actual length of the commarea is too large, and is therefore invalid. The maximum length supported is 32659 bytes.
An error is returned to the Java Client application.
Ensure that the maximum length of the commarea used does not exceed 32659 bytes.
An error message has been returned directly from the CICS region, and is displayed.
CICS Transaction Gateway processing continues.
Refer to the CICS Messages and Codes book, for details of the error.
An attempt to change the JNI Trace file name to file name has failed.
A TFileException is thrown. CICS Transaction Gateway processing continues. JNI tracing continues using the existing file name.
User code should handle the exception. Check that the file name is valid and can be written to.
EXCI connection reuse has already been initialized.
The CICS Transaction Gateway will return an ECI_ERR_SYSTEM_ERROR error.
Contact your service organization for more information and diagnosis.
The CICS Transaction Gateway was unable to allocate memory for the number of TCB entries specified.
The CICS Transaction Gateway returns an ECI_ERR_RESOURCE_SHORTAGE error.
Ensure that the CICS Transaction Gateway has enough memory available to it to operate correctly.
An EXCI call has returned a warning.
CICS Transaction Gateway processing continues.
Diagnose the warning by referring to the CICS External Interfaces Guide.
An EXCI call has returned an error.
CICS Transaction Gateway processing continues.
Diagnose the error by referring to the CICS External Interfaces Guide.
JNI Tracing has sent an unknown trace point to the formatter.
Cannot be sure what will happen as we do not know this trace point.
Contact your service organization.
The surrogate user check has failed. The MVS External Security Manager's return code and reason code are subreason codes 1 and 2.
The ECI request is rejected.
Check whether SURROGCHK has been set to YES in DFHXCOPT, and that the credentials are accurate.
An attempt has been made to open a pipe. The target CICS system associated with the pipe has no free receive sessions. The server name field server name identifies the target CICS server specified on the ECI call.
The call fails, and DFHXCURM (replaceable) is invoked. If the target CICS system is changed by DFHXCURM the change will not be reflected by the text of this message.
Retry the request to CICS when the system is under less load. Review the Receivecount setting of the CICS session definition.
The error number and error reason will indicate the cause of the failure. Detailed descriptions of these errors can be found in the z/OS C/C++ Run-Time Library Reference under the __mlockall() library function. If the user ID running the CICS Transaction Gateway does not have READ access to BPX.STOR.SWAP, errno is set to 139 - EPERM - and the reason code 0X9300000.
The CICS Transaction Gateway has been unable to make the address space non-swappable and continues to run in a swappable mode.
If the problem persists, contact your service organization.
This message is output when approximately 90% of available pipes are in use.
The message is logged and the CICS Transaction Gateway continues.
If you have not planned your system for the pipe usage to be as high at this point, consider increasing the number of pipes available to the CICS Transaction Gateway. Alternatively the CICS Transaction Gateway offers a choice of pipe caching models, which can reduce pipe usage in some circumstances. See the Administration book for more details.
This message is output when all the available pipes are in use.
The message is logged and the CICS Transaction Gateway continues.
If the CICS Transaction Gateway attempts to allocate any more pipes, requests will start to fail with resource shortage errors. If you are not expecting all pipes to be in use at this point, consider increasing the total number of pipes available to the CICS Transaction Gateway. Alternatively, the CICS Transaction Gateway offers a choice of pipe caching models, which can reduce pipe usage in some circumstances. See the Administration book for more details.
This message is logged if the value specified to CICS for the maximum number of EXCI pipes is outside the allowed range (100 to 250).
This message is logged, the maximum number of EXCI pipes available is assumed to be the default of 100 and the CICS Transaction Gateway continues.
Reconfigure the maximum number of pipes under CICS to a value within the allowed range.
This message is logged if a call to the z/OS name token retrieval service fails with an unexpected error. The name of the assembler service call which failed is IEANTRT and return code is the value this call returned. See the z/OS Assembler Services reference for details on IEANTRT return codes.
This message is logged and the maximum number of EXCI pipes available is assumed to be the default of 100. The CICS Transaction Gateway continues.
If this message persists, or a value other than the default has been specified for the maximum number of concurrent pipes, contact your service organization.
The CICS Transaction Gateway could not open trace file filename for writing. errno is the operating system return code for the failure.
This message is logged and tracing is deactivated. No trace points will be written.
Investigate why the CICS Transaction Gateway cannot to write to filename . For example, check that the user ID under which the CICS Transaction Gateway is running has write access to the file and directory specified.
An internal error occurred. The Client was unable to allocate memory to allowserver statistics to be gathered.
The message is written to the error log and the Client tries to continue, although attempts to reference this shared memory element may result in a trap. Server statistics will not be available for collection.
Ensure that all orphaned shared memory is purged from the system and that there are sufficient memory resources. The way that you do this depends on your operating system although most Unix and Linux systems provide the ipcs and ipcrm utilities. If the problem persists, contact your service organisation.
The version of the CICS TG JNI native library is different from the version of the Gateway daemon java classes.
This message is logged. The Gateway daemon fails to start.
This might be because of a corrupted installation. Reinstall the CICS Transaction Gateway. If the problem persists contact your service organization.
The CICS TG Java classes are from a different release, compared to the CICS TG JNI DLL.
This error is thrown to the Java client application. Subsequent calls to the CICS TG API will fail.
Ensure the version of the CICS TG JNI referred to in the Java library path is the same as the CICS TG jar files in the application's CLASSPATH. The CICS TG application trace can be used to display the java library path setting used.
A Java client application is unable to find the CICS TG JNI native library.
This error is thrown to the Java client application. Subsequent CICS TG API calls will fail.
Check that the CICS TG bin directory is in the library path. The CICS TG application trace can be used to display the java library path setting used.
CICSTERM could not find or open the specified color, or keyboard, binding file.
The emulator terminates.
Ensure the required binding files exist and are correctly specified, then restart the emulator.
CICSTERM ran out of memory while processing a color, or keyboard, binding file.
The emulator terminates.
Reduce the number of bindings specified in the file or try to provide more system free memory; then restart the emulator.
CICSTERM detected an error in a color, or keyboard, binding file. Only one binding is allowed for the specified item.
The emulator terminates.
Correct the binding file and restart the emulator.
CICSTERM detected an error in a color, or keyboard, binding file. The specified command was not a valid binding command.
The emulator terminates.
Correct the binding file and restart the emulator.
CICSTERM detected an error in a keyboard binding file. The specified item was not a valid 3270 keyboard function.
The emulator terminates.
Correct the binding file and restart the emulator.
CICSTERM detected an error in a keyboard binding file. The specified item was not a valid workstation keyboard modifier value.
The emulator terminates.
Correct the binding file and restart the emulator.
CICSTERM detected an error in a keyboard binding file. The specified item was not a valid workstation key name.
The emulator terminates.
Correct the binding file and restart the emulator.
CICSTERM detected an error in a color binding file. The specified item was not a valid 3270 screen field attribute.
The emulator terminates.
Correct the binding file and restart the emulator.
CICSTERM detected an error in a color binding file. The specified item was not a valid workstation display color.
The emulator terminates.
Correct the binding file and restart the emulator.
CICSTERM or CICSPRNT could not communicate with the Client daemon. This probably means the Client daemon was unable to start.
The emulator terminates.
Try to start the Client daemon using the CICSCLI /S command.
CICSTERM or CICSPRNT did not start because the Client daemon was not, or could not be, started.
The emulator terminates.
Try to start the Client daemon using the CICSCLI /S command.
The server returned a terminal definition that contained an invalid screen width for the terminal emulator. (Screen widths are normally 40, 80, or 132 columns.)
The emulator resets the screen width to a standard 80 columns. Output may appear corrupted because the client and server terminal definitions may not match.
Check with the server system administrator to determine why the terminal definition is incorrect.
The server returned a terminal definition that contained a screen size too large for the terminal emulator. The product of screen width and screen depth cannot exceed 4096.
The emulator resets the screen depth to the maximum number of rows. Output may appear corrupted because the client and server terminal definitions may not match.
Check with the server system administrator to determine why the terminal definition is incorrect.
The connection with the specified server has been lost. This would normally indicate that the server is no longer available.
The emulator waits until the server is available again and tries to reconnect.
Wait for the connection to be reestablished or clear the error message and terminate the emulator.
The Client daemon returned a resource shortage error. This indicates either a shortage of free memory, or if SNA communications are being used, there may be insufficient LU6.2 sessions available.
The emulator attempts to continue, although further requests to the Client daemon may receive the same error response.
If the Client is very busy, the resource shortage may disappear when the work load decreases. Otherwise, examine the Client log to determine the cause of the error, stop the Client and restart it with more resources.
CICSTERM or CICSPRNT could not be started because the Client daemon is closing down.
The emulator terminates.
Wait for the Client daemon to close down, then restart the emulator.
The Client daemon indicated that the specified server name is unknown.
The emulator terminates.
Ensure the required server name is one of those listed in the configuration file, or use the /S option to select from a list of valid names.
The Client daemon was unable to connect to the specified server.
The emulator terminates.
Check for other messages and examine the Client error log to determine the cause of the error.
The emulator tried to send more data than the Client daemon could accept.
The data is ignored and the emulator continues.
Increase the MaxBufferSize value in the Client section of the configuration file, then stop and restart the product.
Client 3270 emulator terminals are not supported by all CICS servers. The specified server is one of those that does not provide this support. If this is a CICS/400 server this message can also be generated if CICS is unavailable.
The emulator terminates.
Select a server that does support client terminals or check with the server system administrator to determine why client terminals are not supported.
The specified server is secure and required a valid userid and password before it could install a client terminal.
The emulator terminates.
Enter a valid userid and password when prompted by the Client daemon. Alternatively, to avoid the prompt use the CICSCLI /C command to set the userid and password.
The Client daemon encountered errors while communicating with the specified server.
The emulator ignores the errors and tries to continue.
Check for other messages and examine the Client error log to determine the cause of the error.
The server rejected the terminal because the specified NetName was invalid.
The emulator terminates.
Ensure the requested terminal NetName is correct and defined at the server. If the error persists, check with the server system administrator for the cause of the error.
The server rejected the terminal because the specified Model was invalid.
The emulator terminates.
Ensure the requested terminal Model is correct and defined at the server. If the error persists, check with the server system administrator for the cause of the error.
The server rejected the request because another terminal was already installed with the same NetName.
The emulator terminates.
Ensure the requested terminal NetName is correct. If the error persists, check with the server system administrator for the cause of the error.
The server was unable to accept the terminal and rejected the installation request.
The emulator terminates.
Check with the server system administrator to determine why the terminal was rejected.
The server rejected the terminal.
The emulator terminates.
Check with the server system administrator to determine why the terminal was rejected.
The terminal emulator was unable to open or create the local print file specified by the PrintFile option in the configuration file.
The print request is ignored and the terminal emulator continues.
Ensure the name of the print file you specified in the configuration file is correct and accessible.
The terminal was unable to write to the local print file specified by the PrintFile option in the configuration file.
The print request is ignored and the emulator continues.
Ensure the name of the print file you specified in the configuration file is correct and accessible.
The terminal emulator is unable to execute the local print command specified by the PrintCommand option in the configuration file. The errno value indicates the return code from the operating system.
The print request is ignored and the emulator continues.
Ensure the print command you specified in the configuration file is correct. A fully qualified filename should be used.
The specified server reported an ABEND while trying to run the current transaction. This may have been caused by a communications failure between the Client daemon and server.
The terminal emulator ignores the errors and tries to continue.
Examine any other messages and the Client error log and server error log to determine the cause of the error.
The server returned a terminal definition that contained an invalid screen depth for the terminal emulator. (Screen depths are normally between 10 and 60 rows).
The terminal emulator has reset the screen depth to a standard 24 rows. Output may appear corrupted because the terminal emulator and server terminal definitions may not match.
Check with the server system administrator to determine why the terminal definition is incorrect.
The server returned more data than the terminal emulator can accept.
The excess data is ignored and the terminal emulator tries to continue.
Check with the server system administrator to determine why such a large amount of data is being generated. Client trace information may be helpful when trying to find these errors.
The Client daemon can only communicate simultaneously with the number of servers specified by the MaxServers option in the Client section of the configuration file (ctg.ini). This limit has been reached.
The emulator terminates.
Use the CICSCLI /X command to close connections to servers that are no longer required, or increase the "MaxServers" setting in the configuration file; then stop and restart the product.
The server rejected the terminal because the server terminal definition does not represent a 3270 device.
The emulator terminates.
Ensure the requested terminal Model or NetName is correct and correctly defined at the server. If the error persists, check with the server system administrator for the cause of the error.
The server rejected the terminal emulator because the server was too busy.
The emulator terminates.
Retry the request sometime later when the server is not so busy.
The terminal emulator detected an unexpected internal error.
Error information is written to the Client error log.
Obtain the Client error log - and, if possible, trace information - and refer the problem to your support organization.
An internal emulator function failed.
The message is written to the error log and the emulator terminates. The function name and error code are logged.
If the problem persists, contact your service organization.
An internal Windows function failed.
The message is written to the error log and the emulator terminates. The function name is logged.
If the problem persists, contact your service organization.
The emulator is unable to allocate enough memory to create an internal control structure.
The message is written to the error log and the emulator terminates.
Try altering the system configuration to provide more free memory when the emulator is started, then restart the emulator.
The emulator has received incorrect data from the Client daemon.
The message is written to the error log and the emulator continues.
If the problem persists, contact your service organization.
The emulator has received too many outstanding ATI requests from the server.
The message is written to the error log and the emulator continues.
Try to establish why the emulator is receiving large numbers of ATI requests while being unable to initiate them. If the problem persists contact your service organization.
There no CICS servers available for the emulator to use.
The emulator terminates.
Check that there are one or more valid CICS servers in the configuration file. If the workload manager is active, check that at least one of the servers the emulator tried to connect to is available. Examine the Client trace to see which servers the workload manager attempted to connect to.
The EPI user exit (CICSEPIX) returned CICS_EXIT_DONT_ADD_TERMINAL and rejected the CICS_EpiAddTerminal request.
The EPI terminal is not added.
Check with the server system administrator to determine why the terminal was rejected.
The screen size available is too small for cicsterm. The minimum size is 25 rows by 80 columns.
The terminal emulator has not been started.
Change the screen size of your terminal before starting cicsterm and retry.
One or more required exits have not been initialized.
client will continue but exits will not be used
Define the exits as defined in writing your own exits (in info centre)
The application PID cannot determine whether Workload Manager is active.
This message is written to the log, and Workload Manager is switched off in application PID .
If the problem persists, contact your service organization.
A user application specified a program which has no affinity with any of the active regions defined to the Workload Manager.
It is possible to define program affinity to CICS regions on the Workload Manager, to indicate that a program is defined on a particular CICS region. If using the biasing algorithm, the Workload Manager sends requests only to regions with the correct affinity.
A trace point prior to this one gives the name of the program. Check that the program has affinity with one of the regions defined to the Workload Manager, and that at least one of the CICS regions with affinity is running. The 'cicscli -l' command will indicate if the connection to the CICS server is active.
The Workload Manager is unable to read the specified file, which contains working configuration data. The file is created and maintained by the Workload Manager.
The message is written to the log and the Load Manager is disabled.
Make sure that the INI file being read exists on the disk, and that it is not read-protected. If the problem persists, contact your service organization.
This is a warning. A duplicate parameter heading has been detected in the Workload Manager section of the configuration file ctg.ini.
The Client continues to read the configuration file ctg.ini, but all duplicate parameters are ignored.
Remove any duplicate parameters from the configuration file ctg.ini.
This is a warning. A duplicate section heading has been detected in the Workload Manager section of the configuration file ctg.ini.
The Client continues to read the configuration file ctg.ini, but all duplicate sections are ignored.
Remove any duplicate sections from the configuration file ctg.ini.
The Workload Manager found an invalid section in the configuration file ctg.ini, the specified section could not be read.
The Client continues but the Workload Manager is disabled.
Remove or correct the invalid section in the configuration file ctg.ini.
A mandatory parameter could not be found in the Workload Manager INI file.
The Workload Manager will be disabled.
Make sure that the Workload Manager INI file is valid.
The specified parameter has an invalid value.
The Workload Manager will be disabled.
Make sure that the Workload Manager INI file is valid.
The value of the specified parameter is too large.
The Workload Manager will be disabled.
Make sure that the value specified is within the required range.
CICSCLI could not communicate with the Client daemon process. This probably means that the Client daemon was unable to start.
CICSCLI performs no action.
Try starting the Client daemon using the CICSCLI /S command.
The Client daemon was unable to set the requested trace state.
Service tracing remains unchanged.
Examine any other messages and the Client error log to determine the cause of the error.
The specified server name was not defined in the configuration file.
CICSCLI performs no action.
Correct the server name and reissue the command. If required, add the server to the configuration file, then stop and restart the product to activate the changes.
The Client daemon was unable to disconnect from the server.
CICSCLI performs no action.
Try using CICSCLI /I; if this fails examine any other messages and the Client error log to determine the cause of the error.
The Client daemon was unable to complete the request to start the connection to a server.
CICSCLI performs no action.
Examine any other messages and the Client error log to determine the cause of the error.
The Client daemon was unable to perform a request to list the current server connection details.
CICSCLI performs no action.
Examine any other messages and the Client error log to determine the cause of the error.
A CICSCLI command was issued with the /U or /P options but without the /C option specifying a server name.
CICSCLI performs no action.
Reissue the command with the correct options.
The Client daemon was unable to perform the request to change the userid and password information for a secure server.
CICSCLI performs no action.
Examine any other messages and the Client error log to determine the cause of the error.
The Client daemon was unable to perform a request to connect to the named server, because a connection with the server already exists.
CICSCLI performs no action.
If the connection is no longer required, use the CICSCLI /X command to close it.
The Client daemon was unable to perform the request to start a connection with the specified server.
CICSCLI performs no action.
Examine any other messages and the Client error log to determine the cause of the error.
The Client daemon can only communicate simultaneously with the number of servers specified by the MaxServers option in the Client section of the configuration file. This limit has been reached.
CICSCLI performs no action.
Use the CICSCLI /X command to close connections to servers that are no longer required. Alternatively, increase the MaxServers setting in the configuration file; then stop and restart the product.
The CICSCLI /D command to start Client tracing can include an optional numeric value specifying the maximum size of data to be traced. The specified size is either not a numeric value or is outside the permitted range of 1 - 32767.
CICSCLI performs no action.
Reissue the command with the correct value.
The Client daemon was unable to set the security and error pop-up state requested by a CICSCLI /E or CICSCLI /N command.
Error and security pop-ups remain unchanged.
Examine any other messages and the Client error log to determine the cause of the error.
The /F option to specify a configuration file was included on a CICSCLI command, but this option can be specified only when starting the Client daemon with the CICSCLI /S command.
CICSCLI performs no action.
If a different configuration file is required, the product must be stopped and restarted.
A request to restart the Client daemon timed out while waiting for the Client daemon to stop. Cicscli waits up to 60 seconds for the Client daemon to stop. It can take some time to stop the Client daemon, because all active conversations with the server must complete first. On some network protocols a specific sequence of data flows must be exchanged with the server during shutdown; this can also take some time.
The restart command terminates, and the Client daemon will not be restarted.
Wait for the cclclnt process to terminate; this means that the Client daemon has stopped. Then issue a start request.
The Client daemon was unable to set the requested trace state.
Service tracing to the memory buffer remains unchanged.
Examine any other messages and the Client error log to determine the cause of the error.
The Client daemon was unable to start the trace to the memory buffer. This is probably because sufficient storage could not be allocated.
Service tracing to the memory buffer was not started.
Examine any other messages and the Client error log to determine the cause of the error.
A request to start the Client daemon has timed out because another instance of the Client daemon is currently shutting down. Cicscli waits for up to 60 seconds for the Client daemon instance to shut down. For shutdown to complete, all active server conversations must complete and network connections must have ended and this may take some time.
The start command terminates and the Client daemon will not start.
Wait for the cclclnt process to terminate, showing the Client daemon has stopped, and reissue the start request.
The length of the userid string supplied exceeds the maximum supported by the CICS Client.
CICSCLI performs no action.
Reissue the command with a valid string.
The length of the password string supplied exceeds the maximum supported by the CICS Client.
CICSCLI performs no action.
Reissue the command with a valid string.
The message id indicated could not be located within the message file.
No action has been taken.
Contact your service organization with the message id.
An exception was thrown when trying to open a connection to the Gateway daemon on the specified port. The exception message is provided.
The requested action cannot be completed.
The exception may provide more information into the problem.
An exception was thrown when trying to authenticate the client with the Gateway daemon at the specified URL. The exception message is provided.
The requested action cannot be completed.
The exception may provide more information into the problem.
An unexpected return code was received when trying to authenticate the client with the Gateway daemon at the specified URL.
The requested action cannot be completed.
The return code may provide more information into the problem.
CTGAdmin cannot handle the security protocols in place on the Gateway daemon at the specified URL.
The requested action cannot be completed.
Obtain a later version of ctgadmin.jar, or disable the protocols at Gateway gateway .
The indicated security protocol, unknown to CTGAdmin, reported a failure of the specified return code.
The requested action cannot be completed.
Obtain a later version of ctgadmin.jar, or disable the protocols at Gateway protocol .
An unexpected return code was received trying to send the request from the authenticated client.
The requested action cannot be completed.
The return code may provide more information into the problem.
An unexpected return code was received trying to initialize with the Gateway daemon from an authenticated client at the specified URL.
The requested action cannot be completed.
The return code may provide more information into the problem.
An exception was thrown when trying to send a request from an authenticated client to the Gateway daemon at the specified URL. The exception message is provided.
The requested action cannot be completed.
The exception may provide more information into the problem.
An unexpected return code was received trying to send a request to the Gateway daemon from an authenticated client at the specified URL.
The requested action cannot be completed.
The return code may provide more information into the problem.
The Gateway daemon at the specified URL was unable to locate its management server.
The requested action cannot be completed.
Obtain a trace from the Gateway daemon and contact your service organization.
CTGAdmin cannot handle information sent by the Gateway daemon at the specified URL.
The requested action cannot be completed.
Ensure that the Java level on the Java client is at least as high as that on the Gateway daemon. Also check that you have the latest version of ctgadmin.jar installed.
The mandatory option was not specified.
The requested action cannot be completed.
Reissue the command, specifying the required option.
An unexpected error occurred when processing the specified option.
The requested action cannot be completed.
Contact your service organization.
The specified option appears more than once in the request; this is not allowed.
The requested action cannot be completed.
Correct the request and try again.
The specified option is not recognized.
The requested action cannot be completed.
Correct the request and try again.
A parameter was provided but did not start with a minus sign.
The requested action cannot be completed.
Correct the request and try again.
An unexpected internal error occurred.
The requested action cannot be completed.
If the problem persists, contact your service organization.
CTGAdmin did not recognize the specified action.
The requested action cannot be completed.
Correct the request and try again. Refer to help for a list of valid actions.
This action requires options, but no valid ones were specified.
The requested action cannot be completed.
Correct the request and try again.
The parameter for the specified option was not a number and is required to be a number.
The requested action cannot be completed.
Correct the request and try again.
The parameter for the specified option was not within the range specified by min -max .
The requested action cannot be completed.
Correct the request and try again.
For the trace action you cannot specify the fulldatadump option with the dumpoffset option or the truncationsize option.
The requested action cannot be completed.
Correct the request and try again. Specify fulldatadump if you want the complete contents of the dump. Specify dumpoffset, or truncationsize, or both, if you want a partial dump.
The client machine is not authorized to perform administrative commands on the specified URL.
The requested action cannot be completed.
Check that the host from which you are issuing the command appears in the list of authorized hosts at the Gateway daemon that you are attempting to administer (configuration tool, TCPAdmin panel).
The parameter for the specified option was too low and cannot be used.
The requested action cannot be completed.
Correct the request and try again.
The specified port does not refer to the local Admin port but refers to a standard TCP protocol handler.
The requested action cannot be completed.
specify the port for the local admin handler and reissue the request.
An exception was returned from the Gateway daemon at the specified URL.
The requested action cannot be completed.
The exception message will provide more information on the problem.
The specified option is not recognized.
The requested action cannot be completed.
Correct the request and try again.
An unexpected return code was received when trying to authenticate the client with the Gateway daemon at the specified URL.
The requested action cannot be completed.
The return code may provide more information into the problem.
The Gateway daemon at the URL specified tried to send an exception back which cannot be handled by CTGAdmin.
The requested action cannot be completed.
Ensure that the Java level on the Java client is at least as high as that on the Gateway daemon. Also check that you have the latest version of ctgadmin.jar installed.
For the trace action, the jnifile option was specified but no parameter was given. A parameter must be specified.
The requested action cannot be completed.
Correct the request and try again.
You entered options for an action, but at least one of the options has been specified in its full form and its short form. This is equivalent to specifying the same option twice.
The requested action cannot be completed.
Correct the request by specifying either the full version of the option or its short form.
The option specified had an associated parameter, but the option doesn't require a parameter.
The requested action cannot be completed.
Correct the request and try again.
The CICS Transaction Gateway does not support setting the Gateway trace file through SDSF.
The Gateway daemon continues running.
If trace is required to go to a specific file, specify the file in the configuration file used when the Gateway daemon starts.
The CICS Transaction Gateway does not support setting the JNI trace file through SDSF.
The Gateway daemon continues running.
If JNI trace is required to go to a specific file, specify the file in the CTG_JNI_TRACE environment variable.
The 'stats' action accepts only one of the '-gs', '-si', '-rg' options.
The requested action cannot be completed
Correct the request and try again
A request for statistical information specified one or more IDs that do not exist.
The requested action completes.
Correct the IDs and try again.
ID id was specified more that once in a request for statistics.
The requested action completes.
Remove the duplicate ID to remove this message.
The command contained a request for statistic id and its resource group resource group
The requested action completes and the results for resource group are displayed.
Remove either the statistic ID or the resource group ID and rerun the command.
An error occurred in the CICS TG while attempting to retrieve statistic id
The requested action completes.
Check the CICS TG error logs for details of the error.
An error occurred in the CICS TG while retrieving one or more statistics as part of the request for statistics in resource group id .
The requested action completes.
Check the CICS TG error logs for details of the error.
The administration request was rejected as it was sent to an incorrect Gateway daemon port.
The requested action cannot be completed.
Resend the request to the Gateway daemon port identified by the adminport parameter.
The Gateway daemon received the dump request but returned a null response
The Gateway daemon returned an invalid response to the dump request, which might not be completed.
Check the Gateway daemon log for earlier messages indicating the dump request completed successfully.
The remote JVM executing the Gateway daemon does not support the INSERT-0 dump type.
The requested action cannot be completed.
Correct the request by requesting a dump type supported by the remote JVM.
The request to the Gateway daemon completed but an error was detected.
The Gateway daemon returned an error during the dump request, which might not be completed.
Check the Gateway daemon log for earlier messages indicating the dump request completed successfully.
The Gateway daemon received the dump request but returned an invalid response
The Gateway daemon returned an invalid response to the dump request, which might not be completed.
Check the Gateway daemon log for earlier messages indicating the dump request completed successfully.
A request for statistical information specified one or more statistical types that do not exist.
The invalid types are ignored and the requested action completes. If the statistical type list contained no valid statistical types then all results will be displayed.
Correct the specified statistical types and try again.
During initialization the request monitoring exit class_name failed with exception exception_message .
The Gateway daemon or Java Client classes will continue to initialize with the exit disabled.
Correct the error in the exit identified by the exception_message and restart the Gateway daemon to enable this exit.
The request monitoring exit class_name failed with exception exception_message when the exitFired method was called.
Processing continues with the exit disabled.
Correct the error in the exit identified by the exception_message and restart the Gateway daemon to enable this exit.
The specified log handler has failed to start. The destination is either unknown, or unsupported on this platform.
This message is written to the error stream. The log that failed to start is now written to stdout or stderr, depending on whether the error or information log was being configured.
Check the configuration file to ensure the destination is specified correctly and has valid parameters.
The file logging handler has failed to start because it is unsupported on this platform.
This message is written to the error stream. The log stream that failed to start is now written to stdout or stderr, depending on whether the error or information log was being configured.
Correct the configuration file to use a log handler that is supported on this platform.
The specified log failed to start because expected parameters are missing.
This message is written to the error stream. The log that failed to start is now written to stdout or stderr, depending on whether the error or information log was being configured.
Add the parameters which are missing, and ensure that they have valid values.
The specified log failed to start because the parameters supplied are outside permitted values.
This message is written to the error stream. The log that failed to start is now written to stdout or stderr, depending on whether the error or information log was being configured.
Correct the errors in the configuration file.
The log to file failed to start because it was unable to write to the specified file.
This message is written to the error stream. The log that failed to start is now written to stdout or stderr, depending on whether the error or information log was being configured.
Check that the file system is not full, and that the CICS Transaction Gateway has the necessary permissions to write to the file.
Both information and error log streams are configured to log to the same file, but have different parameters specified for the file properties.
This message is written to the error stream. The file handler will start using the larger of the two values.
The reason gives more information about the mismatched parameters. Correct the configuration file by either specifying different filenames for the two log streams, or ensure that both streams have the same parameters if you want to log both streams to the same file.
An incorrect log stream was specified.
This message is written to the error stream.
Check the configuration file to ensure the log stream is specified correctly. Refer to the Administration book for details of the supported stream types.
Either the HTTP or HTTPS protocol handler is specified in the configuration file.
The Gateway daemon continues, but does not start the handler for the specified protocol.
Migrate to the TCP or SSL handlers, and then remove references to the protocol from the configuration file by loading the file into the Configuration Tool and then saving it, or by editing the file in a text editor.
The command line override 'parameter' was specified on a distributed platform Gateway daemon when it isonly supported on z/OS.
This message is logged and the Gateway daemon fails to start.
Restart the gateway daemon without specifying the command line override.
Parameter ÔÇÿNAMEÔÇÖ has a maximum length of 'LEN' characters. This has been exceeded.
This message is output and the Gateway daemon fails to start.
Reconfigure the parameter to be within the allowed limit and restart the Gateway.
The physical socket connection was established, but CICS rejected the connection.
Any requests that were attempting to use the CICS server CICS Server name as defined in the INI file. will fail with ECI_ERR_NO_CICS. Requests that are received after this point will also fail until the server retry interval has expired, at which point the connection will be retried.
Check that the IPIC server CICS Server name as defined in the INI file. is defined correctly in the INI file (remote mode) or Server URL(local mode) and check the reason text Response code from CICS . Check the console log for the CICS server. Check topic "DFHIS1011" in the CICS infocenter for the meaning of the return code.
The CICS connection defined as CICS Server name as defined in the INI file. has been purged at the CICS end. This has caused all work on that connection to be aborted. The work can be identified with the transaction tokenXID or IPIC LUW token (if relevant) for the transaction. and mirror transaction Mirror task in CICS that was used for this transaction. .
CICS Transaction Gateway will end the work and free each purged conversation to CICS.
>
The physical socket connection could not be established to the target CICS server.
Any requests that were attempting to use the CICS server CICS Server name as defined in the INI file. will fail with ECI_ERR_NO_CICS. Requests that are received after this point will also fail until the server retry interval has expired, at which point the connection will be retried.
Check that the IPIC server is defined correctly in the INI file (remote mode) or Server URL(local mode) and check the reason text Failure reason text. .
An error occurred while reading the IPIC server definition.
The Gateway will ignore the named server definition.
Check that the IPIC server is defined correctly in the INI file.
The named IPIC server definition is a duplicate of another definition within the ini file.
The Gateway will ignore the duplicate server definition.
Check that the IPIC server is defined correctly in the INI file.
The IPIC Server definition was not created properly in the configuration file.
The Gateway will ignore the server definition.
Check that each IPIC server is defined correctly in the INI file.
An invalid command option was specified when using the CICSBMSC command.
CICSBMSC performs no action.
Reissue the command with the correct option.
The CICSBMSC command requires a BMS source file as input.
CICSBMSC performs no action.
Reissue the command with the correct BMS source file name.
The CICSBMSC command could not find, or could not read the supplied BMS source file.
CICSBMSC performs no action.
Check that the BMS source file name is correct, that the file is available and can be read.
The CICSBMSC command is unable to create output files.
CICSBMSC processing ends.
Check that there is sufficient disk space available for the CICSBMSC output files.
The CICSBMSC command has found an error in an input BMS source file.
CICSBMSC processing ends.
Check the BMS macro source at the line indicated.
Ths CICS Transaction Gateway was unable to map an XA standard XID to a RRMS unit of recovery.
This message is logged, or traced, and the CICS Transaction Gateway continues.
If this message is logged and the problem perisists contact your service organization.
The CICS Transaction Gateway was unable to remove a reference to the XID from the XID mapping table. If the table is shared, a common error would be that the ctgmaster process has been ended prematurely.
The entry will remain in the mapping table.
If the problem persists, contact your service organisation. Recycle the CICS TG or if IP Spraying, recycle the ctgmaster and then the CICS TG which will cause the entry to be freed up.
A call to the RRMS API (ATREINT1) failed. RRMS returned the return code rrms_rc . The CICS Transaction Gateway was unable to express interest in a transactional unit of recovery.
The CICS Transaction Gateway resource adapter returns a resource manager failure error (XAER_RMERR) on the transaction. The transaction fails to start and no work can be performed against it.
If this problem persists contact your service organization.
In order to execute RRMS function , the CICS Transaction Gateway uses CTGRRMS services. Attempting to call the service failed with error auth return code . Return code values are: * 0x04 - Version number check failed (RRMSInit call) * 0x08 - Parameter length checks failed * 0x0C - Security check failed * 0x10 - Internal error (ASID table) * 0x14 - Function not supported
The RRMS function is not executed and a resource manager failure error will be returned to the calling application.
The CICS Transaction Gateway administration guide contains details on the mandatory steps required to be able to use the CTGRRMS services.
A call to the RRMS API to prepare a transaction failed with return code rrms return code .
If rrms return code is non zero, this error is logged and the CICS Transaction Gateway resource adapter returns a failure return code to the transaction manager. The transaction manager may attempt to re-issue the prepare or may back out the transaction.
Check the Gateway daemon log for further log messages that may more specific information on the cause of the problem. If the problem persists, contact your service organization.
A request to RRMS to commit a transaction failed. The transaction is a one-phase-commit optimized XA transaction.
The resource adapter returns a serious error to the transaction manager for the affected transaction, which might not be completed. The CICS Transaction Gateway continues to process transactions.
The RRMS system administrator should check the status of the transaction, and manually complete it if necessary. Check the Gateway daemon log for further messages related to this transaction.
A request to RRMS to commit a two-phase-commit XA-based transaction failed. The return code indicates that a repeated request is not likely to succeed.
The resource adapter returns a serious error to the transaction manager for the affected transaction, which might not be completed. The CICS Transaction Gateway continues to process transactions.
The RRMS system administrator should check the status of the transaction, and manually complete it if necessary. Check the Gateway daemon log for further messages related to this transaction.
Unable to transfer XID data between Java and C. This would normally denote an environment issue.
The XA request is rejected.
Contact your service organisation to resolve this problem.
CICS TG has been unable to determine the XA options used on the transaction request.
The request is rejected and no state-change is made on the transaction.
Contact your service organisation.
A request to the RRMS API set syncpoint controls failed. The Gateway daemon was unable to set itself as the correct type of syncpoint manager with RRMS in order to peform actions on a transaction.
It might be not be possible to prepare, commit or backout the transaction. In this case the resource adapter will return an error to the transaction manager. The CICS Transaction Gateway continues to process requests for other transactions.
If the problem persists, contact your service organistation.
The CICS TG has received a request to start a transaction, but could not store temporary information needed to identify the transaction.
The CICS TG cannot start the transaction.
If the problem persists contact your service organization.
Either RRMS has been restarted, or the master process (ctgmaster) terminated whilst this instance of the Gateway daemon was running.
All transactions through this instance of the Gateway daemon will fail.
If not using load balancing restart this instance of the Gateway daemon. If load balancing restart every instance of the Gateway daemon in the load balancing group and restar the master process. See the administration guide for details on the correct shutdown and restart sequence.
An RRMS API return code indicated that an unexpected error occurred whilst processing a unit of recovery, and that the transaction may have been damaged.
The resource adapter will return a serious error to the transaction manager for the affected transaction. The CICS Transaction Gateway continues to process other transactions.
The RRMS administrator should view the transaction and make any changes necessary.
Due to an internal processing error, it is not possible for the Gateway daemon to commit, or backout a transaction.
The resource adapter will return a serious error to the transaction manager for the transaction in question. The CICS Transaction Gateway continues to process other transactions.
The RRMS administrator should resolve the transaction manually.
CTG_RRMNAME parameter exceeded 32 characters in length.
The name is truncated to 32 characters before registering with RRMS. This message is output and the CICS Transaction Gateway continues.
To avoid this message on startup, specifiy a name less than or equal to 32 characters.
To support XA based requests, the CICS Transaction Gateway issues authorized RRS calls, through CTGRRMS services. It was not possible to enable these services. Return code values are: * 0x04 - Version number check failed (RRMSInit call) * 0x08 - Parameter length checks failed * 0x0C - Security check failed * 0x10 - Internal error (ASID table) * 0x14 - Function not supported
This message is logged. The CICS Transaction Gateway does not start up.
If XA support is required, see the information center for information on how to start CTGRRMS services. If XA support is not required, set the xasupport configuration parameter off and restart the CICS Transaction Gateway.
The CICS Transaction Gateway or CTGMASTER was unable to deregister from the CTGRRMS Services during the shutdown process.
This message is logged and the CICS Transaction Gateway process ends.
If the CTGRRMS services are to be refreshed or stopped, use the -f option, because this Gateway instance or CTGMASTER process will still be shown as registered.
This CICS Transaction Gateway has been configured as part of a TCP/IP load balancing group but the CTGMASTER process is not running. The CTGMASTER process should use the name name for RRS registration.
This message is logged. The CICS Transaction Gateway does not start up.
Configure and start a CTGMASTER instance for the name given in the CTG_MASTER_RRMNAME environment variable and restart the CICS Transaction Gateway.
An internal error has occurred, the XA commit option specified is invalid.
It is not possible for the CICS Transaction Gateway to commit the UR. A serious error is returned to the transaction manager.
The RRMS administrator should resolve the transaction manually. If the problem persists, contact your service organistation.
The CICS Transaction Gateway encountered and error while writing to the JNI trace file.
This message is logged and tracing is deactivated. No further trace points will be written.
Investigate why the CICS Transaction Gateway can no longer write to the trace file. For example, check that the file system where the file is written has sufficient free space.
Ctgmaster could not start.
The ctgmaster process ends.
Check the logs for error messages and correct any reported problems.
The CICS Transaction Gateway or CICS Universal Client is not installed correctly. Registry keys are created at install time.
The command line application terminates.
Reinstall the CICS Transaction Gateway or CICS Universal Client.
The program tried to read from the registry but cannot read the appropriate registry key. This is normally caused by security settings in the registry.
The command line application terminates.
Get your system administrator to give read permission to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\CICS Transaction Gateway or HKEY_LOCAL_MACHINE\SOFTWARE\IBM\CICS Universal Client.
The program tried to write to the registry but cannot write the appropriate registry key. This is normally caused by security settings in the registry.
The command line application terminates.
Logon as a user who has permissions to write to either HKEY_LOCAL_MACHINE\SOFTWARE\IBM\CICS Transaction Gateway or HKEY_LOCAL_MACHINE\SOFTWARE\IBM\CICS Universal Client. Then repeat the command line option.
When trying to run a Java application, the application launcher tries to find a JVM, it does this by querying the registry.
The command line application terminates.
Install a JVM, or use the CTGJAVA command to point to the Java Virtual Machine to run.
When trying to run a Java application, the Java runtime classes could not be found.
The command line application terminates.
Install the Java Virtual Machine (JVM) correctly.
The file specified does not exist.
The command line application terminates.
Specify the fully qualified path to a Java Virtual Machine.
When trying to point to a Java Virtual Machine using the CTGJAVA command, the specified JVM is tested and determined to be at an unsupported level.
The command line application terminates.
Specify a supported Java Virtual Machine to CTGJAVA.
When trying to run a Java application, the application launcher tests the currently set JVM. It is determined to be at an unsupported level.
The command line application terminates.
Use the CTGJAVA command to point to a supported Java Virtual Machine to run.
The operating system you are running, as detected by the JVM, is not supported.
The application terminates.
Ensure that you are running a supported Operating System.
The Client daemon must be started before the Gateway daemon. The 'ctgstart' command called 'cicscli' to start the Client daemon and the Client daemon failed to start. On Windows platforms this failure can also occur when starting the IBM CICS Universal Client service.
The 'ctgstart' command terminates, the Gateway daemon is not started.
Examine any other console messages and the Client error log to determine the cause of the error. Additionally on Windows operating systems check the application event log for messages generated by the IBM CICS Universal Client service.
The operating system returned the specified error to the application.
The command line application terminates.
Retry the start attempt. If problems persist, contact your Service organisation.
The AUTH_USERID_PASSWORD environment variable contains an incorrect value. User IDs and passwords will be authenticated against the appropriate security mechanisms.
User ID and password authentication is enabled.
Set the environment variable AUTH_USERID_PASSWORD to either YES or NO. Set this environment variable to YES to enable user ID and password authentication. Set it to NO to disable user ID and password authentication.
The CTG_MIXEDCASE_PW environment variable controls whether or not passwords are converted to upper case before authentication. It is required only if AUTH_USERID_PASSWORD is set.
All passwords will be converted to upper case before authentication takes place.
Set the environment variable CTG_MIXEDCASE_PW to either 'YES' or 'NO'. Set this environment variable to YES to enable mixed case passwords. Set it to NO to convert passwords to upper case.
The CTG_MIXEDCASE_PW environment variable contains an incorrect value. All passwords will be converted to upper case before authentication takes place.
All passwords will be converted to upper case before authentication takes place.
Set the environment variable CTG_MIXEDCASE_PW to either YES or NO. Set this environment variable to YES to enable mixed case passwords. Set it to NO to convert passwords to upper case.
The environment variable AUTH_USERID_PASSWORD controls whether or not user IDs and passwords supplied on CICS requests are authenticated.
User ID and password authentication is not enabled.
Set the environment variable AUTH_USERID_PASSWORD to either 'YES' or 'NO'. Set this environment variable to YES to enable user ID and password authentication. Set it to NO to disable user ID and password authentication.
The ctgmaster program was invoked with the -input switch, but value is not a valid value.
Execution of ctgmaster continues, using the console type defined in the CTG_MASTER_INPUT environment variable. If the environment variable is undefined or not valid, the default of STDIN is used instead.
Check that the -input switch specifies a string value of STDIN if running in the USS shell, or CONSOLE if running in batch mode.
The ctgmaster program was invoked with the xa_max_tran switch, but value1 is not a valid value.
Execution of ctgmaster continues, using the value defined in the CTG_XA_MAX_TRAN environment variable. If the environment variable is undefined or not valid, the default value of 8192 is used instead.
Check that the -xa_max_tran switch specifies an integer between 1 and 8192.
The ctgmaster program was invoked with the -trace switch, but the value specified is not valid.
Execution of ctgmaster continues, using the value defined in the CTG_MASTER_TRACE environment variable. If the environment variable is undefined or not valid, trace output is written to STDERR.
Check that the -trace switch specifies a string value that represents a valid HFS file name, on a path to which the user has write access.
The ctgmaster program was invoked with the -natlang switch, but value is not a valid value.
Execution of ctgmaster continues, using the value defined in the CTG_MASTER_NATLANG environment variable. If the environment variable is undefined or not valid, the default English (EN) NLS message bundle is used instead.
Check that the -natlang switch is one of the following two-character strings: EN (English) JA (Japanese) ZH (Simplified Chinese).
The ctgmaster program was invoked with the -rrmname switch, but value is not a valid value.
Execution of ctgmaster continues, using the value defined in the CTG_MASTER_RRMNAME environment variable. If the environment variable is undefined or not valid, the default master RRMNAME of CICSTG.DEFAULT.MASTERRRM is used instead.
Check that the -rrmname switch specifies a valid string that is no longer than 32 characters. See the Administration Guide for more details.
Environment variable CTG_MASTER_TRACE_ON is set to an incorrect value value1 .
Execution of ctgmaster continues, using the default value value2 instead.
Check that the CTG_MASTER_TRACE_ON environment variable is set to either YES or NO.
Environment variable CTG_MASTER_RRMNAME is not defined. This environment variable defines the RRMNAME that is to be used in this TCP/IP load balancing group.
Execution of ctgmaster continues, using the default value value .
Check that the CTG_MASTER_RRMNAME environment variable is defined. The RRMNAME must be no longer than 32 characters. See the Adminstration guide for more information.
Environment variable CTG_MASTER_INPUT is set to an incorrect value value1 .
Execution of ctgmaster continues, using the default value value2 .
Set the CTG_MASTER_INPUT environment variable to STDIN if running from the USS shell, or CONSOLE if running in batch mode.
Environment variable CTG_XA_MAX_TRAN is set to an incorrect value value1 .
Execution of ctgmaster continues, using the default value value2 .
Set the CTG_XA_MAX_TRAN environment variable to an integer between 1 and 8192. As a guide, take the sum of the MAXCONNECT values of each Gateway daemon in the IP load-balancing group.
Environment variable CTG_MASTER_NATLANG is set to an incorrect value value1 .
Execution of ctgmaster continues, using the default value value2 .
Set the CTG_MASTER_NATLANG environment variable to one of the following two-character strings: EN (English) JA (Japanese) ZH (Simplified Chinese).
The ctgmaster program could not obtain an exclusive ENQ on resource name (value1 ). This is required to ensure the integrity of ctgmaster resources.
Execution of ctgmaster is ended.
Check that the resource name value1 is valid, and that no other address space is holding an ENQ on the same resource name. The ctgmaster ENQ name should be of the form SYSZCTG.<CTG_MASTER_RRMNAME>, where <CTG_MASTER_RRMNAME> is the value of the CTG_MASTER_RRMNAME environment variable. If problems persist, collect ctgmaster trace output and contact your service organization.
The ctgmaster program could not initialize the RRMS PC services, which are provided by the CTGRRMS service address space.
Execution of ctgmaster is ended.
Ensure that the user ID starting the ctgmaster program has at least UPDATE access to the RACF profile CTG.RRMS.SERVICE. If problems persist, collect ctgmaster trace output and contact your service organization.
The ctgmaster program could not register with RRMS.
Execution of ctgmaster is ended.
Ensure that the CTG_MASTER_RRMNAME is valid and is not already being used by another process. The name should be no longer than 32 characters, and should not end with .UA; see the Adminstration Guide for full details. If problems persist, collect ctgmaster trace output and contact your service organization.
The ctgmaster program could not start the console listener thread, which is needed for user interaction.
Execution of ctgmaster is ended.
Ensure that ctgmaster has been started with the correct input type for the runtime environment. The input type is determine by either the CTG_MASTER_INPUT environment variable, or the command line -input switch. When ctgmaster is running in batch mode (via CTGBATCH, or BPXBATCH from JCL), the input type must be set to CONSOLE. When ctgmaster is running in the USS shell, the input type must be set to STDIN.
Whilst attempting to start an XA transaction, the given XID was found to be a duplicate of the XID of an existing transaction.
The transaction branch is not started.
Resolve the existing transaction in RRMS or contact your service organization.
The CICS Transaction Gateway could not complete the transaction because too many XA transactions are active.
The transaction is rolled back.
Stop the Gateway daemon or ctgmaster process. Increase the value of the CTG_XA_MAX_TRAN environment variable, and then restart.
The CTGMaster process could not delete the shared memory that it owns.
CTGMaster continues to shut down, and the shared memory remains.
Contact your service organization.
Details of which processes are attached to shared memory cannot be found by CTGMaster.
CTGMaster will shutdown regardless, the memory will be removed such that existing users still have access until they terminate. New connections will not be possible until a new CTGMaster is established.
Contact your service organisation.
CTGMaster needs to determine where the install directory is so that it can get to necessary data files.
CTGMaster will be unable to start.
If running under USS, add the <CICS TG install>/bin directory to the system path, otherwise launch ctgmaster with an absolute pathname i.e. '/usr/lpp/cicstg/bin/ctgmaster'.
The userid under which the ctgmaster program is running does not have sufficient security priviledges to access the CTGRRMS service address space.
The ctgmaster program will terminate.
In order to successfully initialize, the userid under which the ctgmaster program is executing must have at least UPDATE access to the profile 'CTG.RRMS.SERVICE'.
The version of ctgmaster being run is different from the version of the CTGRRMS service address space which is running.
The ctgmaster program terminates.
Ensure that the versions of ctgmaster and the CTGRRMS services are the same. Refer to the z/OS Administration Guide for details on how to refresh the CTGRRMS Services.
The RRM name for the ctgmaster process, as defined by the CTG_MASTER_RRMNAME environment variable, or the -rrmname switch of the ctgmaster command, is too long. The message is issued when an attempt is made to start either a ctgmaster process, or a Gateway daemon that is part of a TCP/IP port sharing group.
This message is output and the ctgmaster process or Gateway daemon fails to start.
Specify a name less than or equal to 32 characters.
ctgmaster was started without a stdin console. This is likely to be caused by running ctgmaster under CTGBATCH without using the override "-input=console".
ctgmaster will terminate
Add the "-input=console" override to the ctgmaster command in the PARM for CTGBATCH, or set the environment variable "CTG_MASTER_INPUT=CONSOLE".
An error occurred writing an internal message to a message queue. In UNIX and Linux systems, the Client daemon communicates internally using message queues. In systems other than AIX, the default configuration settings for these queues are too small to allow for large client data flows.
The Client daemon is unable to operate.
Change the configuration settings of the message queues to allow for large client data flows. The way that you do this depends on your operating system. Refer to the UNIX and Linux Administration book for further information on configuring message queues. If this does not resolve the problem, contact your service organization.
On a Windows platform an attempt to get addressability to a shared memory element has failed for some operating system reason.
The message is written to the error log and the Client tries to continue, although attempts to reference this shared memory element will result in a trap.
If the problem persists, contact your service organization.
On a UNIX or Linux platform, a call to determine the maximum number of file descriptors available to a process has returned an error code. The error value indicates the value from the sysconf system call.
The message is written to the error log. The Client continues using a default number of file descriptors.
If the problem persists, contact your service organization.
On a UNIX or Linux platform, an attempt to close all inherited file descriptors failed, for at least one descriptor. The error value indicates the return code from the operating system.
The message is written to the error log and the Client continues. Applications using the Client may encounter problems restarting after termination if this error has occurred.
If the problem persists, contact your service organization
The Client API component tried to create an Operating System message queue that already exists. The queue key is queue key and is based on the process ID (PID) of the Client API component. In the case of the CICS TG, this will be the Gateway daemon PID and in the case of the CICS UC, this will be the Client application PID.
The message is written to the client log and user application requests can no longer be processed.
Shut down and then restart the Gateway daemon, or restart the Client application, as appropriate.
The transaction manager has issued an XA call on a transaction, but the resource adapter cannot comply, because the transaction is not in a state that allows this request.
The XA call is not actioned. The resource adapter returns a protocol error to the transaction manager. This message is logged, with the relevant XA and RRMS transaction identifier information.
If the transaction manager cannot resolve the transaction, use the RRMS or transaction manager administration tools to resolve the transaction manually.
An error prevents the master process or Gateway daemon from storing details of XA transactions
The Gateway daemon or master process fails to start.
Take action according to the return code. For return code 1007, increase the amount of memory available to the Gateway daemon process, or reduce the value for CTG_XA_MAX_TRAN. For return code 1014, reduce the number of shared memory segments running on the system. See the Unix System Services documentation for details on the of interprocess communication limits. For return code 1027 ensure that the CICS TG <install_path>/bin directory is on the path, and. Ensure that the ctgmaster executable file is in the <install_path>/bin directory.
An attempt is made to start a ctgmaster process or Gateway daemon, but another application is already using the resource manager name supplied. The application could be another instance of the Gateway daemon or a third party product.
The error is logged and the ctgmaster process or Gateway daemon fails to start.
Correct the configuration and try again. See the Adminstration Guide for information on resource manager names and when to invoke a CICS TG master process.
A attempt is made to start a ctgmaster process or Gateway daemon, but an instance of ctgmaster is already using the resource manager name supplied.
The error is logged and the ctgmaster or Gateway daemon fails to start.
Correct the configuration and try again. See the Adminstration Guide for information on resource manager names and when to invoke a CICS TG master process.
An attempt is made to start a Gateway daemon as part of a TCP/IP load balancing group. A ctgmaster is registered with resource manager name (CTG_MASTER_RRMNAME). However, the Gateway daemon cannot access the shared storage that is needed to share information about XA transactions. This could be because the ctgmaster and Gateway daemon have been started using different HFS installations, or the ctgmaster is in the process of shutting down.
This message is logged and the Gateway daemon fails to start.
Ensure that the ctgmaster and Gateway daemon processes were started using the same HFS installation and the the CTG_MASTER_RRMNAME specified by the Gateway daemon points to an active ctgmaster process and not a ctgmaster in the process of shutting down.
The call to GetMethodID has failed. This is an internal error.
CICS Transaction Gateway processing continues.
If the problem persists, contact your service organisation.
The call to NewByteArray has failed. This is an internal error.
CICS Transaction Gateway processing continues.
If the problem persists, contact your service organisation.
The userid under which the Gateway daemon is running does not have sufficient security priviledges to access the CTGRRMS service address space.
The Gateway daemon will terminate.
In order to successfully initialize with xasupport=ON, the userid under which the Gateway daemon is executing must have at least UPDATE access to the profile 'CTG.RRMS.SERVICE'.
When TCP/IP load balancing for XA transaction support is enabled, the maximum number of concurrent XA transactions is controlled by the value of environment variable CTG_XA_MAX_TRAN specified in the CTGMASTER address space. CTG_XA_MAX_TRAN is required for a standalone Gateway daemon configured for XA transactional support.
The value of CTG_XA_MAX_TRAN specified for this Gateway daemon is ignored. The value of CTG_XA_MAX_TRAN specified in the CTGMASTER address space is used instead.
Correct the configuration by unsetting CTG_XA_MAX_TRAN for this Gateway daemon.
The version of the CICS Transaction Gateway being run is different from the version of the CTGRRMS service address space which is running.
The CICS Transaction Gateway terminates.
Ensure that the versions of the CICS Transaction Gateway and the CTGRRMS services are at the same version. Refer to the z/OS Administration Guide for details on how to refresh the CTGRRMS Services.
Environment variable CTG_XA_MAX_TRAN is set to an incorrect value value1 .
Execution of the gateway daemon continues, using the default value value2 .
Set the CTG_XA_MAX_TRAN environment variable to an integer between 1 and 8192.
An attempt was made to start a ctgmaster process or Gateway daemon, but a Gateway daemon is already using the resource manager name supplied.
The error is logged and the ctgmaster process or Gateway daemon fails to start.
Correct the configuration and try again. See the information center for information on resource manager names and when to invoke a CICS TG master process.
The Gateway daemon is attempting to start as part of a Gateway group but cannot verify that the owner of the RRMS registration is a ctgmaster process.
The error is logged and the Gateway daemon fails to start.
Contact your service organisation.
The CICS Transaction Gateway application is running in 64-bit mode. The CICS TG attempted to call an internal 31-bit API, but was unable to allocate sufficient storage within the 31-bit address range to pass data to the API.
This message is logged and CICS Transaction Gateway processing continues. If the memory allocation failure prevented an EXCI request from completing, Cics_Rc is set to ECI_ERR_RESOURCE_SHORTAGE.
Configure the system to give give the process invoking the CICS TG classes more storage below the 2 gigabyte line. Consult the z/OS documentation for details on how to do this.
This message indicates a malloc() failure when attempting to allocate memory. The memory was required for the call that determines the jobname associated with the Gateway daemon.
CICS Transaction Gateway processing continues. Messages written to the system log will contain spaces in place of the jobname.
Refer to the z/OS documentation to determine what corrective action is necessary to provide adequate memory to the CICS Transaction Gateway process.
This message indicates a Unix System Services call 'BPX1GTH' failed. The Gateway daemon uses this call to determine its jobname.
CICS Transaction Gateway processing continues. Messages written to the system log will contain spaces in place of the jobname.
Refer to the z/OS Assembler Services Reference to determine what the return code and reason code values signify.
To support XA based requests, the CICS Transaction Gateway issues authorized RRS calls, through CTGRRMS services. It was not possible to invoke the initialization of these services.
This message is logged. The CICS Transaction Gateway does not start.
If XA support is required, see the information center for information on how to start CTGRRMS services. If XA support is not required, set the xasupport configuration parameter off and restart the CICS Transaction Gateway.
The Gateway daemon attempted to write an SMF record. This failed because the user ID does not have sufficient authority. The user ID that the Gateway daemon runs under is required to have read access to the BPX.SMF facility class.For further details, see the RACF and Unix System Services documentation
This message is logged. All data in the current SMF record is lost.
If writing to SMF is required, update z/OS RACF with the pre-requisite permissions and restart the Gateway daemon.
The Gateway daemon issued a call to the Unix System Services API call __smf_record. This failed with the following return codes: errno1 and errno2
This message is logged. All data in the current SMF record is lost.
Verify with the z/OS systems administrator that the SMF subsystem is working correctly.See the CICS Transaction Gateway Information Center for further information onCICS Transaction Gateway recording to SMF.For further details on the error codes see the C/C++ Run-Time Library Reference, and refer to the section describing the __smf_record() call. If the problem persists contact your service organisation.
The Gateway daemon attempted to write a record to SMF. The Unix System Services call __smf_record failed with reason code JRSMFNotAccepting, indicating that SMF is not currently accepting records.
This message is logged. All data in the current SMF record is lost.
Contact the systems administrator responsible for SMF. For further details on the error code see the UNIX System Services Messages and Codes book, and refer to the section on reason codes.
A call to the UNIX System Services API malloc failed, which indicates that it did not have enough memory available.
This message is logged. All data in the SMF record is lost.
See the CICS Transaction Gateway Information Centre for details on dealing with out of memory errors.
The Client was unable to allocate the amount of memory required to hold the returned data. The error value indicates the system return code.
The message is written to the error log and the function fails.
Try reducing the amount of data requested and try again. If the problem persists contact your service organization.
An invalid value (as indicated by call_type ) was specified for the ECI call type.
The message is written to the error log and the function fails.
Correct the program so that a supported value is specified for the ECI call type.
The value specified for the length of the commarea is larger than the amount of data supplied.
The message is written to the error log and the call fails.
Correct the program so that the specified length of the commarea is equal to, or exceeds, the amount of data being passed to the ECI.
An invalid value (as indicated by value ) has been specified for the ECI extended mode parameter.
The message is written to the error log and the call fails.
Correct the program so that a supported value is specified for the extended mode parameter.
An invalid value (as indicated by version ) has been specified for the ECI version parameter.
The message is written to the error log and the function fails.
Correct the program so that a supported value is specified for the ECI version parameter.
The call to the ECI has completed but an error was detected. No data is returned to the calling application in the commarea.
The message is written to the trace file if tracing is enabled.
Information on the type of error can be determined from earlier entries in the trace log.
An error was encountered during execution of the code. The value of rc indicates the failing error code.
The message is written to the trace file if tracing is enabled.
Refer to the CICS Client/Server Programming book for an explanation of the error codes.
The maximum number of parameters that can be passed to the CICS TG has been exceeded.
The CICS TG service terminates.
Reduce the number of arguments and try again.
The service cannot find the Java native runtime dll and is unable to start the CICS TG.
The CICS TG service terminates.
Reinstall your Java Virtual Machine
Upon starting the CICS TG service enough resources could not be allocated.
The CICS TG service terminates.
Free up some memory and try again
An error occurred whilst trying to start the Java Virtual Machine for the Gateway service to run under. The options used when trying to creat the JVM will be output when this condition occurs.
The CICS TG service terminates.
Check the options supplied and try again with different parameters
When attempting to start the CICS TG service the required Java class could not be found. This class can be found in the supplied CTGSERVER.JAR.
The CICS TG service terminates.
Update your classpath and try again.
When attempting to start the CICS TG service the main() method cannot be found within the JGate class.
The CICS TG service terminates.
Reinstall the CICS Transaction Gateway.
Whilst running the CICS TG service no free memory was available for new resources.
The CICS TG service terminates.
If this occurs under expected load then more memory may be needed to satisfy the performance needs for the specific CICS TG installation.
An attempt to start the Windows service control dispatcher failed.
The CICS TG service terminates.
Restart the machine and try to start the service again.
The option specified is not supported by the ctgservice command line executable.
The usage statement is displayed
Adjust the parameters you pass to ctgservice.exe
Installation of the CICS TG service failed. An error code describing why failure occurred is supplied.
The command line application terminates
Check that the service isn't already installed and try again.
When trying to stop the CICS TG service before uninstallation an error occurred.
The command line application terminates.
Try to stop the service manually and try the uninstall again.
During an uninstall of the CICS TG service the service could not be opened.
The command line application terminates.
Check to see if the service is installed and try again.
During an uninstall of the CICS TG service the service could not be deleted.
The command line application terminates.
Check to see if the service is installed and try again.
Whilst attempting to create the specified subkey to be used by the CICS TG in the registry an error occurred.
The command line application terminates.
Restart the machine and try again.
Whilst attempting to create the specified string to be used by the CICS TG in the registry an error occurred.
The command line application terminates.
Restart the machine and try again.
Whilst attempting to store the parameters to be used by the CICS TG in the registry an error occurred.
The command line application terminates.
Restart the machine and try again.
During an install of the CICS TG service the service could not be created.
The command line application terminates.
Check to see if the service is already installed.
During an install of the CICS TG service the Service Control Manager could not be opened.
The command line application terminates.
Restart the machine and try again.
The named service cannot be started from the command line.
The command line application terminates.
Use the Windows Service Control Manager to start the named service.
An internal function has returned an error.
The service failed to complete the requested task.
If the problem persists, contact your service organization.
An internal function has returned an error.
The service failed to complete the requested task.
If the problem persists, contact your service organization.
A problem occurred when the named service was being started. values are the parameters that were defined for the service.
The service failed to start. This message is written to the application event log of the Windows operating system.
Inspect the application event log for other messages that help to explain the problem. Address the cause of failure and retry the command.
An invalid value was defined for use with the named service.
The named service fails to start. This message is written to the application event log of the Windows operating system.
Change or remove the invalid parameter value and retry.
One or more invalid parameter values were defined for use with the named service.
The named service fails to start. This message is written to the application event log of the Windows operating system.
Inspect the application event log for messages detailing invalid parameters, and change or remove the invalid parameter values.
A problem occurred when starting the Client daemon.
The named service ends. This message is written to the application event log of the Windows operating system.
Check the parameter values that were passed to the Client daemon are valid. To do this issue the cicscli command with the parameters that were used. Change any parameters if necessary and restart the service. If parameters are valid inspect the Client error log for other messages.
The connection has already been closed and so cannot be closed again.
System action is not required.
You are attempting to close a connection that has already been closed.
The connection returned by the ConnectionManager is not of the correct type for use with the CICS resource adapters. This is an internal error.
System action is not required.
The CICS Resource Adapter was returned a connection that was either null, or not of the correct type.
Due to an unrecoverable error the ManagedConnection object that your application is using has become damaged and cannot be used for any further interactions with CICS.
None.
If the problem persists, contact your service organization.
The transaction failed to commit on CICS and so a rollback was carried out to back out any work done within the transaction.
The system tried to commit the transaction but cannot do so. The transaction has therefore been rolled back.
If the problem persists, contact your service organization.
An ECIManagedConnection can process only one transaction at a time. An XA transaction has already been started on the ECIManagedConnection, so a local transaction may not start until the XA transaction is finished.
System action is not required.
Review the Java Client application that tried to start a second transaction. Refer to the Programming Guide for further details.
An ECIManagedConnection can process only one transaction at a time. A local transaction has already been started on the ECIManagedConnection, so an XA transaction may not start until the local transaction is finished.
System action is not required.
Review the Java Client application that tried to start a second transaction. Refer to the Programming Guide for further details.
An ECIManagedConnection can process only one transaction at a time. A local transaction has already been started on the ECIManagedConnection, so you may not start another.
System action is not required.
Review the Java Client application that tried to start a second transaction. Refer to the Programming Guide for further details.
A local transaction has not been started on the ECIManagedConnection so any calls to commit() or rollback() will fail.
System action is not required.
The local transaction has not been started, so cannot commit.
An ECIManagedConnection can process only one transaction at a time. An XA transaction has already been started on the ECIManagedConnection, so you may not start another.
System action is not required.
Review the Java Client application that tried to start a second transaction. Refer to the Programming Guide for further details.
An XAException occurred processing XA request.
System action is not required.
Check the JNI and application server logs for further details.
An input flag that has been received on an XA_START or XA_END Request is not valid. The request has failed.
System action is not required.
Check the application Server logs for further details.
A request was made, but failed, possibly due to a communications error.
System action is not required.
Due to an error, this transaction cannot be committed or rolled back.
Access to this ECIConnection is no longer allowed as it has been closed. A new ECIConnection must be acquired for any further interaction to occur with CICS.
System action is not required.
This connection is closed, no further work through this handle is allowed.
When trying to associate a connection with an ECIManagedConnection the connection type must be ECIConnection. This is an internal error.
System action is not required.
Connection handle supplied is null.
When trying to associate a connection with an ECIManagedConnection the connection type must be ECIConnection. This is an internal error.
System action is not required.
The Connection handle is not of the correct type.
The ConnectionManager has not returned an Connection object from the allocateConnection() method.
System action is not required.
The Connection handle returned is not of the correct type.
The ECI resource adapter only supports ConnectionSpec objects of the type ECIConnectionSpec.
System action is not required.
The ConnectionSpec handle is not of the correct type.
The ConnectionRequestInfo object being supplied to the ECI resource adapter is not of the correct type. This is an internal error.
System action is not required.
The ConnectionRequestInfo handle is not of the correct type.
The ConnectionManager supplied to the ECIConnectionFactory is null. In a managed environment this is a internal error to the environment. In a nonmanaged environment you must not supply a null ConnectionManager to the ECIConnectionFactory constructor.
System action is not required.
The ConnectionManager handle is null.
You cannot do any further work with this ECIInteraction object as it has been closed.
System action is not required.
The ECIInteraction has been closed, further work is not allowed.
The ECIConnection object associated with the current ECIInteraction object is null so the interaction cannot continue. This is an internal error.
System action is not required.
The Connection handle is null for this interaction.
The ECIConnection that is being used by your ECIInteraction is not of the correct type. This is an internal error.
System action is not required.
The Connection handle for this interaction is not of the correct type.
An I/O exception was thrown by the record when the resource adapter attempted to populate it with the relevant information. The record exception is linked to this one.
None.
Review the linked exception for an indication of any corrective action needed.
Only InteractionSpec objects of the type ECIInteractionSpec can passed to the ECIInteraction.execute() method.
System action is not required.
InteractionSpec passed in to the execute method is not of the correct type.
When calling ECIInteraction.execute() a non null ECIInteractionSpec must be supplied at all times.
System action is not required.
Null was passed to the ECIInteractionSpec.execute method.
An IOException occurred during an interaction with a CICS server. The CICS exception is linked to this one.
None.
Review the linked exception for an indication of any corrective action needed.
During an interaction with a CICS server a known error has occurred in the underlying CICS Transaction Gateway runtime. The supplied error code can be referenced in the CICS Transaction Gateway documentation. This is an internal error.
None.
The supplied error code can be referenced in the CICS Transaction Gateway documentation.
A reply to a SYNC_SEND interaction is pending. No further SYNC_SEND or SYNC_SEND_RECEIVE interactions are allowed until a SYNC_RECEIVE is executed.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
A SYNC_SEND interaction must be executed before a reply from CICS can be received using SYNC_RECEIVE.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
Input record objects supplied to the ECIInteraction.execute() method must support the javax.resource.cci.Streamable interface.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
When specifying an InteractionVerb of SYNC_SEND or SYNC_SEND_RECEIVE a non null input Record object must be supplied as input to CICS.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
Output record objects supplied to the ECIInteraction.execute() method must support the javax.resource.cci.Streamable interface.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
When specifying an InteractionVerb of SYNC_RECEIVE or SYNC_SEND_RECEIVE a non null output Record object must be supplied to hold the reply from CICS.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
During the Interaction with CICS a Transaction Abend occurred on the server. The supplied code is that which is returned by CICS.
None.
Check the abend code in the CICS documentation for an indication of any corrective action needed.
The EPIConnection has been closed and can no longer be used.
System action is not required.
Connection is closed, no further work possible.
The ConnectionManager did not return an EPIConnection for use by the application.
System action is not required.
No connection returned by the ConnectionManager.
An unusable Connection object was returned by the ConnectionManager.
System action is not required.
Invalid connection was returned by ConnectionManager.
Only ConnectionSpecs of the type EPIConnectionSpec are accepted in the getConnection() method of EPIConnectionFactory.
System action is not required.
Invalid ConnectionSpec was supplied, must be an EPIConnectionSpec instance.
The EPIInteraction is closed so no further work can be carried out on it.
System action is not required.
Connection is closed, no further work possible.
An EPIInteractionSpec must be supplied when EPIConnection.execute() is called.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
An EPIInteractionSpec must be supplied when EPIConnection.execute() is called.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
When attempting to associate a Connection object with an EPIManagedConnection the incorrect type was used. The EPI resource adapter supports only EPIConnection objects being passed to the associateConnection() method.
None.
If the problem persists, contact your service organization.
When attempting to associate a Connection object with an EPIManagedConnection the incorrect type was used. The EPI resource adapter only supports EPIConnection objects being passed to the associateConnection() method.
System action is not required.
A null connection was passed to associateConnection() method by the application server.
The amount of data stored in the input Record object does not correspond to the amount required for the currently defined screen size.
System action is not required.
Streamable input record information does not contain the correct amount of data.
Input record objects supplied to EPIInteraction.execute() must implement the javax.resource.cci.Streamable interface in order to be used by the EPI resource adapter.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
Output record objects supplied to EPIInteraction.execute() must implement the javax.resource.cci.Streamable interface in order to be used by the EPI resource adapter.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
When executing a SYNC_RECEIVE or SYNC_SEND_RECEIVE an output record must be supplied to hold the reply from CICS.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
When executing a SYNC_SEND or SYNC_SEND_RECEIVE an input record must be supplied to hold the data to be sent to CICS.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
An exception was thrown while the LogonLogoff class specified was being accessed. The original exception can be accessed using the getCause method.
None.
Review the linked exception for an indication of any corrective action needed.
The LogonLogoff class specified could not be found in the current CLASSPATH. Check that any required files are in your systems CLASSPATH.
None.
Check that the LogonLogoff class specified is on the system CLASSPATH.
An error occurred whilst trying to instantiate the LogonLogoff class specified.
None.
Check that the name of the LogonLogoff class is specified correctly in the Java Client application.
The Java Client application does not have the required authorization to create the specified LogonLogoff class.
None.
Refer to the "Writing LogonLogoff classes" section of the Programming Guide for further details on how to grant Java security permissions.
The resource adapter was unable to create a Subject object required to be passed to the registered LogonLogoff class. This could be because the required Java Security permissions are not available.
None.
Refer to the "Writing LogonLogoff classes" section of the Programming Guide for further details on how to grant Java security permissions.
A Request to create a connection factory has failed because a null connection manager was passed to the createConnectionFactory method.
None.
If the problem persists, contact your service organization.
The EPIConnection that your component is trying to use is not the current Connection being processed by the EPI resource adapter. The current working Connection must be closed before work can continue. This is an internal error.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
The CICS transaction has ended, but it is not possible to determine if resources were committed or rolled back.
None.
If the problem persists, contact your service organization.
The ExecuteTimeout property on the ECIInteractionSpec must be a positive value.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
A valid value for InteractionVerb was not passed within the ECIInteractionSpec.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
In order to carry out an Interaction with CICS a FunctionName must be provided in the ECIInteractionSpec. This FunctionName maps to the program that is to be executed on the CICS server.
System action is not required.
The function name in the ECIInteractionSpec is empty, request not valid.
An ECI request is being executed as part of an XA transaction but no Xid is available on the associated XAResource object. The transaction is not in a valid state.
System action is not required.
Check the application server logs for further details.
An attempt was made to end an XA transaction which had not been started.
System action is not required.
Check the application server logs for further details.
The Xid received on an XA_END flow is not the same as that received on the XA_START flow. The XA_END flow has failed.
System action is not required.
Check the application server logs for further details.
The input record provided does not match the EPI resource adapter's representation of the screen.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
A LocalTransaction cannot be started because it was obtained from a Connection which is now closed.
System action is not required
Check that begin() is not being invoked after the connection is closed.
A SYNC_RECEIVE interaction requires the COMMAREA length or reply length to be specified in the InteractionSpec, and neither have been specified.
None.
Review the Java Client application to resolve the problem. Refer to the "Programming using the J2EE Connector Architecture" section of the Programming Guide for further details.
The SSL protocol was specified for the connectionURL, but no key ring has been specified.
System action is not required.
No SSL key ring was provided for SSL protocol.
An exception was thrown by the screenable record when the EPI resource adapter tried to populate it with the relevant information. The record exception is linked to this one.
None.
Review the linked exception for an indication of any corrective action needed.
An I/O exception was thrown by the record when the resource adapter attempted to read the information. The record exception is linked to this one.
None.
Review the linked exception for an indication of any corrective action needed.
An application has attempted to obtain a Local Transaction from a connection which cannot be provided. This will result from using the ECI resource adapter configured for local: connections on WebSphere for z/OS.
A NotSupportedException was thrown back to the application.
The application needs to be changed to not use local transactions obtained from the connection instance. Or the resource adapter needs to be configured for remote connections to a CTG daemon.
During a read of the terminal, an exception has occurred. The original exception has been linked.
The terminal read could not continue.
Retrieve the linked exception from the CICSUserInputException and diagnose from the original message.
During a write to the terminal, an exception has occurred. The original exception has been linked.
The terminal write could not continue.
Retrieve the linked exception from the CICSUserInputException and diagnose from the original message.
The application has attempted to execute an XA transaction using a CICS TG that does not support XA transactions.
System action is not required.
Either re-configure the application to connect to a CICS TG that supports XA transactions, or do not use XA transactions within this application.
The application has attempted to execute an XA transaction using a CICS TG that does not have XA transaction support enabled.
System action is not required.
Enable support for XA transactions within the CICS TG, or re-configure to connect to a CICS TG that has XA transaction support enabled, or do not use XA transactions with this application.
The Input MappedRecord object that has been passed to the Resource Adapter is not of the correct type. It cannot be treated as a Channel object because it is not of type ECIChannelRecord.
The request is rejected.
Check the type of the input record.
The Output MappedRecord object that has been passed to the Resource Adapter is not of the correct type. It cannot be treated as a Channel object because it is not of type ECIChannelRecord.
The request is rejected.
Check the type of the input record.
The message id indicated could not be located within the message file.
No action taken.
Contact your service organization with the message id.
A Management Bean received a request to get or set an attribute but this attribute is unknown to it.
No action taken.
Ensure the management bean being invoked supports this attribute.
A request to set an attribute on a management bean failed because the value provided was not valid.
The attribute doesn't change.
Ensure the value provided is valid for the attribute.
A management bean throw an exception which was not expected by the system.
No action taken.
The linked exception may provide more information on the problem.
An exception occurred whilst trying to set the Gateway trace file to the specified file. This might be because the specified file is a directory, is not writeable or cannot be opened for another reason.
The Gateway trace file is not changed.
Check that the file specified is a valid file and is in a writeable location.
An exception occurred whilst trying to set the JNI trace file to the specified file. This might be because the specified file is a directory, is not writeable or cannot be opened for another reason.
The JNI trace file is not changed.
Check that the file specified is a valid file and is in a writeable location.
When trying to make multiple changes to the Gateway daemon value failed.
The Gateway daemon settings are not changed.
Check that the parameters used in the change are correct.
When trying to make multiple changes to the Gateway daemon requested value failed. Then when trying to undo the changes already made, a further change associated value failed.
The Gateway daemon settings are left in an undefined state.
Check that the parameters used in the change are correct.
When trying to change a Gateway trace setting, the value provided was not valid.
The Gateway daemon setting is not changed.
Check that the value used for the setting is correct.
When trying to change a Gateway JNI trace setting, the value provided was not valid.
The Gateway daemon setting is not changed.
Check that the value used for the setting is correct.
When trying to set the Gateway trace file, the value specified a directory.
The trace file is not changed.
Specify a trace file that is not a directory.
When trying to set the Gateway trace file, the value specified an invalid path.
The trace file is not changed.
Specify a trace file using a valid path for the platform.
When trying to set the Gateway trace file, the value specified a file on which the Gateway daemon does not have write permissions, or a directory in which the Gateway daemon cannot create or write a file.
The trace file is not changed.
Specify a trace file which is writeable, or in a location which is writeable, by the Gateway daemon.
When trying to set the JNI trace file, the value specified an invalid path.
The JNI trace file is not changed.
Specify a JNI trace file using a valid path for the platform.
When trying to set the JNI trace file, the value specified a file on The CICS Transaction Gateway does not have write permissions to the specified JNI trace file, or the CICS TG does not have permission to create, or write, a file in the specified directory.
The JNI trace file is not changed.
Specify a trace file which can be written to by the CICS Transaction Gateway.
The user attempted to change the JNI trace filename whilst trace was running.
This message is output. Tracing continues to the previous filename.
Deactivate JNI trace before changing the filename.