To display information about each message table (original or replacement) for CA-L-Serv or for client applications, issue this command:
DISPLAY MSGTABLE
CA-L-Serv displays information in message LDM0422I. For each message table, CA-L-Serv displays a name, language, and number of messages per table or language.
Reason:
The command contains unmatched parentheses.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
The command contains unmatched quotes.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
The command contains misplaced parentheses.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the statement in error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
The command member invoked at CA-L-Serv startup contains inconsistent data.
Action:
Review CA-L-Serv's message log to identify the statement(s) in error. Messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information. Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The command contains the invalid parameter xxxx.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
One of the command members invoked at CA-L-Serv startup contains an invalid keyword.
Action:
Review CA-L-Serv's message log to identify the error. Restart CA-L-Serv after correcting the problem. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
A statement executed at CA-L-Serv startup contains an invalid repetition of keyword xxxx.
Action:
Review CA-L-Serv's message log to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
A CA-L-Serv command contains an abbreviated keyword that cannot be processed because it is ambiguous.
Action:
Reissue the command specifying the full form of the keyword.
Reason:
The command exceeds the maximum number of subparameters allowed for one of its keywords.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error.
Reason:
The command specified a value that is in excess of the maximum length allowed.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
The value specified by the command is in excess of the maximum allowed.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
The command specified a nonnumeric value where a numeric value was expected.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
The command specified an invalid option. 'options' specifies the list of valid options for the command.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information.
Reason:
The command specified an abbreviated option that could be 'option1' or 'option2'.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information. Reissue the command specifying the full form of the option keyword.
Reason:
The value xxxx is numeric and must be comprised between minimum value n1 and maximum value n2.
Action:
Reissue the command specifying a valid value for the parameter.
Reason:
The xxxx parameter must specify a text string with a maximum length of nn.
Action:
Reissue the command specifying a valid value for the parameter.
Reason:
Parameter xxxx is required for this command.
Action:
Review CA-L-Serv's message log and use the information provided in [location] to identify the error. When issued at CA-L-Serv startup rather than as a response to a console command, messages LDM083E, LDM084E and LDM085E are also displayed and provide additional information. Reissue the command specifying a valid value for the parameter.
Reason:
The first number you specified in a range is larger than the second number for that range.
Action:
Reissue the command specifying a valid range for the parameter.
Reason:
The value value specified on the command is lower than the minimum required. The minimum permissible value is nnn.
Action:
Reissue the command specifying a valid value for the parameter.
Reason:
The value can also be comprised between minimum n1 and maximum n2.
Action:
Reissue the command specifying a valid value for the parameter.
Reason:
A text string of maximum length nnn can also be specified.
Action:
Reissue the command specifying a valid value for the parameter.
Reason:
The options indicated by optionlist are also valid for the command.
Action:
Reissue the command specifying valid options.
Reason:
The options indicated by optionlist are valid for the command.
Action:
Reissue the command specifying valid options.
Reason:
Keyword xxxx must be specified for this command.
Action:
Reissue the command including keyword xxxx.
Reason:
Keywords xxxx and yyyy are mutually exclusive.
Action:
Reissue the command specifying only one of the mutually exclusive keywords.
Reason:
At least one of the keywords specified by keywords must be specified when issuing the command.
Action:
Reissue the command specifying at least one of the keywords.
Reason:
The parameter indicated by xxxx must only contain characters 0-9 and A-F and its length must not exceed nnn bytes.
Action:
Reissue the command specifying a valid hex string.
Reason:
Message xx was not found in any of CA-L-Serv's message tables.
Action:
Make sure all message tables in their current versions are allocated to CA-L-Serv. If you have recently upgraded from a prior release, verify that the LSERVMSG message table in the LDMPARM data set was also upgraded.
Retain CA-L-Serv's logs and call CA Support.
Reason:
WTO in CSECT csect failed for message xx with a return code of xxxx.
Action:
Consult the relevant IBM documentation for an explanation of the return code. Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
WTOR in CSECT csect failed for message xx because it was invoked with an invalid parameter list.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
Message xx does not have any text.
Action:
Make sure all message tables in their current versions are allocated to CA-L-Serv. If you have recently upgraded from a prior release, verify that the LSERVMSG message table in the LDMPARM data set was also upgraded.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An invalid line type xx was specified for a multi-line message on the MSG statement.
Valid line types for multi-line messages are:
Action:
See the CA-L-Serv Command Reference and the comments in the LSERVMSG message table provided in the CAI.CAIOPTN data set for a description of the syntax for the MSG statement.
Reason:
The message table that CA-L-Serv attempted to read contains syntax errors.
Action:
This would happen after making changes to a message table (such as translating standard English messages to a different language). Check the syntax of the messages you modified. Retain the appropriate diagnostic information and call CA Support.
Reason:
Abbreviated parameter xxxx is ambiguous. CA-L-Serv cannot process the command.
Action:
Reissue the command specifying one of the full-length values: yyyy or zzzz.
Reason:
CA-L-Serv does not recognize command xxxx.
Action:
If the command was correctly spelled, use the DISPLAY command to verify that the target component is active: CA-L-Serv commands are only valid when the corresponding component is active.
Reason:
Positional operand xxxx is not valid for the command.
Action:
Check the description of the command's syntax.
Reason:
The corresponding CA-L-Serv component is not active.
Action:
Use the DISPLAY command to list the currently active components. After you determine why the target component was not active, you can issue the ATTACH command to activate it.
Reason:
Incorrect routing information was specified on a message definition
Action:
Correct the message definition and use the MSGTABLE command to refresh the copy of the message table in storage.
Reason:
CA-L-Serv command command was issued from console ucmid.
Action:
None.
Reason:
The message writes the values specified on the PARM parameter of the EXEC statement of CA-L-Serv's startup procedure.
Action:
None.
Reason:
CA-L-Serv is terminating due to a syntax error on the PARM parameter of the EXEC statement of CA-L-Serv's start-up procedure. Messages LDM0084E and LDM0085E identify the statement that contains the error.
Action:
Check the syntax for the PARM parameter.
Reason:
CA-L-Serv is terminating because a command in CA-L-Serv's parameter data set contains a syntax error. Messages LDM0084E and LDM0085E identify the command that contains the error.
Action:
Check for additional messages in CA-L-Serv's message log.
Reason:
CA-L-Serv is terminating due to a syntax error on the PARM parameter of the EXEC statement of CA-L-Serv's start-up procedure. Messages LDM0084E and LDM0085E identify the statement that contains the error.
Action:
Check the syntax for the PARM parameter.
Reason:
CA-L-Serv is terminating due to a syntax error on the PARM parameter of the EXEC statement of CA-L-Serv's start-up procedure. Messages LDM0084E and LDM0085E identify the statement that contains the error.
Action:
Check the syntax for the PARM parameter.
Reason:
CA-L-Serv is terminating because it cannot find or access its parameter data set.
Action:
Add a DD statement for the CA-L-Serv parameter data set in the CA-L-Serv startup procedure (LSVPROC).
Reason:
CA-L-Serv cannot find the specified member in its parameter data set. If this member is critical, CA-L-Serv terminates.
Action:
Verify that the member you specified in CA-L-Serv's start-up procedure is a member of the PDS allocated to DDN=LDMCMND. Verify that every INCLUDE statement in this member specify actual members of the PDS.
Reason:
CA-L-Serv is terminating because it encountered an error when trying to open its parameter data set. If this message follows message LDM0086E, it indicates a user error. Otherwise, it indicates an internal logic error.
Action:
Examine previous messages for information on what type of error occurred. If an internal logic error produced this message, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An entry in CA-L-Serv's parameter data set is too long. The maximum length of an entry is 800 bytes; additional characters are ignored. The last LDM0090I message identifies the statement containing the error.
Action:
Correct the entry in one of these ways:
Reason:
An entry in CA-L-Serv's parameter data set is too long. The maximum length of an entry is 800 bytes; additional characters are ignored. The last LDM0090I message identifies the statement containing the error.
Action:
Correct the entry in one of these ways:
Reason:
An entry in CA-L-Serv's parameter data set is too long. The maximum length of an entry is 800 bytes; additional characters are ignored. The last LDM0090I message identifies the statement containing the error.
Action:
Correct the entry in one of these ways:
Reason:
Acknowledges successful processing of an operator's action.
Action:
None.
Reason:
The command can only be issued at CA-L-Serv start-up.
Action:
If the changes to CA-L-Serv's current configuration must be implemented immediately, terminate and restart CA-L-Serv. Otherwise make the necessary changes to LDMPARM or the start-up proc so that they will be implemented the next time CA-L-Serv is recycled.
Reason:
The command is incomplete.
Action:
See the description of the command's syntax.
Reason:
An INCLUDE statement in LDMPARM does not specify a member name.
Action:
Check the INCLUDE statements in each LDMPARM member.
Reason:
CA-L-Serv finished reading the member named on an INCLUDE statement and will begin to read the member named xxxx again.
Action:
None.
Reason:
Signals that CA-L-Serv is ready to process requests from client applications.
Action:
None.
Reason:
One of CA-L-Serv's components has abended. In most cases, CA-L-Serv's recovery routines will ensure that the region and its subtasks will remain active after performing necessary clean up.
Action:
Look up the abend code in the System Codes manual for your version of MVS. If you are unable to determine the cause of the error, gather the appropriate diagnostic information (symptom dump, abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
Acknowledgment of a SHUTDOWN command. CA-L-Serv will terminate.
Action:
None.
Reason:
CA-L-Serv shutdown has completed.
Action:
None.
Reason:
A syntax error in the LDMPARM command members or the start-up procedure has prevented CA-L-Serv form initializing successfully. CA-L-Serv terminates.
Action:
Review CA-L-Serv's message log to identify the statement in error.
Reason:
An ESTAE routine within CA-L-Serv experienced an abend while trying to perform error recovery processing.
Action:
Look up the abend code in the System Codes manual appropriate for your version of MVS. If you are unable to determine the cause of the error, gather the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A CA-L-Serv region with subsystem name ssname is active on the system. CA-L-Serv terminates.
Action:
Determine why a second region with the same subsystem name was started on the same system.
Reason:
An internal error has occurred.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The code executing in component and CA-L-Serv are not at the same release level and are incompatible.
Action:
Ensure that component came from the same release or PTF tape as the version of CA-L-Serv that you are running.
Reason:
CA-L-Serv's default initialization values are in error.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv experienced an error while trying to obtain storage.
Action:
Look up the return code in the appropriate manual for your version of MVS. You may need to increase the size of CA-L-Serv's region. If you cannot determine the cause of the error, gather the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv experienced an error while trying to free storage.
Action:
Look up the return code in the appropriate manual for your version of MVS. If you cannot determine the cause of the error, gather the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv's recovery code is designed to take optional SVC dumps to assist in diagnosing potential problems. The message indicates that the SVC dump option is not active.
Action:
Look for other messages which may help determine the cause of the problem and why CA-L-Serv abended. You should probably reset the SVCDUMP option to YES to gather appropriate diagnostic data in the event of a reoccurrence.
Reason:
CA-L-Serv's recovery routines were unable to capture a dump.
Action:
Look for other messages which may help determine the cause of the problem and why CA-L-Serv abended.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
One of CA-L-Serv's log data sets has been disabled due to an I/O error. CA-L-Serv will route the messages concerning this log data set to the system log until the problem is corrected.
Action:
Review CA-L-Serv's logs and the system log to determine the cause of the I/O error. For more information, see the IECxxxx messages in CA-L-Serv's job log or the system log.
Reason:
These messages display the internal sessions active for a CA-L-Serv region.
Action:
None.
Reason:
These messages display the internal sessions active for a CA-L-Serv region.
Action:
None.
Reason:
These messages display the internal sessions active for a CA-L-Serv region.
Action:
None.
Reason:
CA-L-Serv has successfully processed the command.
Action:
None.
Reason:
CA-L-Serv has successfully processed the command.
Action:
None.
Reason:
CA-L-Serv abended while processing command xxxx.
Action:
Gather the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
While trying to initialize, CA-L-Serv detected that it was not running APF authorized.
Action:
Check that the CA-L-Serv loadlib is APF authorized, making sure that the dsname and the volser in the APFlist are spelled correctly. Check the link-edit attributes of the modules in the CA-L-Serv loadlib. Most CA-L-Serv modules need to have been link-edited with an authorization code of 1—AC(1).
Reason:
A client application is initializing a session with the communications server.
Action:
None.
Reason:
The communications server is creating internal definitions for a client application.
Action:
None.
Reason:
The communications server encountered an error while attempting to create internal definitions for client application productid executing on system - sysid.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The communications server attempted to create internal definitions for client application productid that is active on system sysid.
Action:
Look for error messages issued by the client application. Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call the client application's CA Support.
Reason:
The communications server attempted to create internal definitions for a client application but the attempt failed.
Action:
Look for error messages issued by the client application. Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call the client application's CA Support.
Reason:
CA-L-Serv was unable to acquire the storage necessary to create a new communications server application.
Action:
Look for error messages issued by the client application. Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call the client application's CA Support.
Reason:
A client application terminated before ending its session with the communications server.
Action:
None. The communications server will perform clean up for the client application.
Reason:
A client application is ending its session with the communications server.
Action:
None.
Reason:
A client application attempted to terminate a session with an application on another system but that application is not active.
Action:
None.
Reason:
The communications server regularly broadcasts service messages to all his partners in the complex. This message is issued when the local communications server receives a broadcast message from the communications server running on system sysid.
Action:
None.
Reason:
The local communications server received a broadcast from an undefined communications server or a communications server that had been marked inactive.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv failed to acquire storage.
Action:
Identify the cause for the failure using the value in R15 and the relevant IBM documentation. If this does not result from a more general storage problem on the z/OS system, collect the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The communications server encountered an internal logic error.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The communication server session for client application productid executing on system sysid has terminated.
Action:
None.
Reason:
A client application is using all its available transmission buffers. Incoming data is rejected until the client application receives the buffers' contents.
Action:
If this occurs on a fairly frequent basis, you may need to increase the HOLDBUF value specified when the communications server is activated. You may also need to increase the number of buffers specified through the SENDLIMIT keyword of the ATTACH command.
Reason:
CA-L-Serv failed to acquire storage.
Action:
Identify the cause for the failure using the value in R15 and the relevant IBM documentation. After ruling out a more general storage problem on the z/OS system, collect the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A client application is ending its session with the communications server.
Action:
None.
Reason:
The client application productid executing on system sysid has terminated.
Action:
None.
Reason:
A communications server session between source and target has terminated.
Action:
None.
Reason:
The communications server regularly broadcasts service messages to all his partners in the complex. This message is issued when the local communications server queues a broadcast message bound for the communications server running on system sysid.
Action:
None.
Reason:
The communications server regularly broadcasts service messages to all his partners in the complex. This message is issued when the local communications server queues a broadcast message bound for all active systems in the complex.
Action:
None.
Reason:
The VTAM component of the communications server is initializing.
Action:
None.
Reason:
The VTAM component of the communications server is terminating.
Action:
None.
Reason:
VTAM reported a communication error on the named route. The codes reflect VTAM values, returned from the RPL.
Action:
The message names the route where the error occurred. Use the DISPLAY ACTIVE and DISPLAY ROUTES commands on both CA-L-Serv nodes involved to check the status of the Communication Server and the communications routes. In many instances, this message does not signal a functional problem with CA-L-Serv. It may only signal that a partner of the local communications server is shutting down, inactive or has not yet initialized.
See the IBM manuals relevant to your environment for a full discussion of the VTAM action and the return codes displayed as part of the message.
Reason:
VTAM reported a communication error within an LU6.2 session. The codes reflect VTAM values, returned from the RPL.
Action:
The message names the route where the error occurred. Use the DISPLAY ACTIVE and DISPLAY ROUTES commands on both CA-L-Serv nodes involved to check the status of the Communication Server and the communications routes. In many instances, this message does not signal a functional problem with CA-L-Serv. It may only signal that a partner of the local communications server is shutting down, inactive or has not yet initialized.
See the IBM manuals relevant to your environment for a full discussion of the return codes displayed as part of the message.
Reason:
These introductory messages are displayed in response to any successful DISPLAY command. They are also a reminder of the release and maintenance level of CA-L-Serv running. They are followed by messages that are specific to the requested display.
Action:
None.
Reason:
These introductory messages are displayed in response to any successful DISPLAY command. They are also a reminder of the release and maintenance level of CA-L-Serv running. They are followed by messages that are specific to the requested display.
Action:
None.
Reason:
These introductory messages are displayed in response to any successful DISPLAY command. They are also a reminder of the release and maintenance level of CA-L-Serv running. They are followed by messages that are specific to the requested display.
Action:
None.
LDM0010I MEMBER=member LDM0010I REUSE=value LDM0010I SSNAME=ssname LDM0010I SYSNAME=sysname
Reason:
These messages display the current values of the following parameters, which are set in CA-L-Serv's startup procedure:
Member that CA-L-Serv is using as its source of start-up commands.
Indicates whether CA-L-Serv is reusing common intercepts and storage.
Subsystem name being used by CA-L-Serv.
Name assigned to the local system.
Action:
None.
LDM0010I SVCDUMP=value? LDM0010I TRACE=value
Reason:
These messages display the current values of the following operands of the OPTIONS command:
Indicates whether CA-L-Serv generates an SVC dump if an error occurs in its address space.
Indicates whether CA-L-Serv's trace feature is active or inactive.
Action:
None.
Name Status SSCTUSE SSCTSUS2 SSCTSSVT ssname status address address address
Reason:
These messages display information about subsystems and are CA-L-Serv's response to the DISPLAY SSNAME command. The name, status, and associated control block addresses are shown for each subsystem. Message LDM0412I is repeated for all subsystems defined to the z/OS system.
Action:
None.
Reason:
There are no messages defined to the z/OS system.
Action:
None.
Reason:
This message signals that CA-L-Serv has successfully completed the requested display.
Action:
None.
Reason:
CA-L-Serv was unable to allocate data set ddname.
Action:
Look up the codes shown in this message in the section on SVC 99 return codes in the appropriate manual for your version of MVS. Possible causes may include a dsname that is misspelled, or a data set allocated to another task or user.
Reason:
These messages are CA-L-Serv's response to the DISPLAY TASKS command. Message LDM0421I is repeated for each active task.
Action:
None.
Reason:
These messages are CA-L-Serv's response to the DISPLAY TASKS command. Message LDM0421I is repeated for each active task.
Action:
None.
Reason:
These messages show the names of CA-L-Serv's message tables, the languages they support, and the number of messages per table and language. An asterisk (*) before a language identifies the default language for a message table.
Action:
None.
Reason:
These messages show the names of CA-L-Serv's message tables, the languages they support, and the number of messages per table and language. An asterisk (*) before a language identifies the default language for a message table.
Action:
None.
Reason:
These messages show the names of CA-L-Serv's message tables, the languages they support, and the number of messages per table and language. An asterisk (*) before a language identifies the default language for a message table.
Action:
None.
Reason:
These messages display storage information for CA-L-Serv:
Size of a storage block (in bytes).
Number of blocks allocated.
Total storage for blocks of this size.
Number of times this size storage block was used.
Action:
None.
Reason:
These messages display storage information for CA-L-Serv:
Size of a storage block (in bytes).
Number of blocks allocated.
Total storage for blocks of this size.
Number of times this size storage block was used.
Action:
None.
Reason:
These messages display storage information for CA-L-Serv:
Size of a storage block (in bytes).
Number of blocks allocated.
Total storage for blocks of this size.
Number of times this size storage block was used.
Action:
None.
Reason:
An installation error or short-on-storage condition may have occurred.
Action:
Look for an z/OS IEAxxxxx or IEFxxxxx message or a dump and retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The task specified on the ATTACH or DETACH command is not valid.
Action:
Reissue the command specifying a valid task name.
Reason:
The task subtask has already been activated through a prior ATTACH command.
Action:
Review CA-L-Serv's message logs and determine why the subtask is active.
Reason:
The truncation for a task name is invalid. CA-L-Serv cannot determine which of the two tasks is being referred to.
Action:
Reissue the command, specifying the full task name.
Reason:
You attempted to ATTACH or DETACH a task that is part of the CA-L-Serv kernel. These tasks are automatically initialized at CA-L-Serv start-up and remain active until CA-L-Serv is shut down. They cannot be ATTACHed or DETACHed.
Action:
Use the ATTACH and DETACH commands only for relevant tasks such as the file server or the communications server.
Reason:
An internal error occurred in the CA-L-Serv kernel.
Action:
Collect the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An attempt was made to DETACH a task that is not active.
Action:
Determine why the task is not active. Issue the DISPLAY ACTIVE command to determine which tasks are active in the CA-L-Serv region. If the task should have been active, review CA-L-Serv's logs and look for prior error messages and determine why the task is no longer active.
Reason:
An installation error or short-on-storage condition may have occurred.
Action:
Look for a z/OS IEAxxxxx or IEFxxxxx message or a dump and retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The specified function has abended. CA-L-Serv requests a dump if SVCDUMP(YES) was specified. If possible, CA-L-Serv continues without the function.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The File Server has successfully completed initialization.
Action:
None.
Reason:
The File Server has terminated.
Action:
None.
Reason:
An ADDFILE command for file ddname failed because the command did not specify a dsname.
Action:
Reissue the command specifying a valid dsname.
Reason:
An ADDFILE command for file ddname completed successfully. The data set is now allocated to the CA-L-Serv region.
Action:
None.
Reason:
An ADDFILE command for file ddname specified a dsname that is allocated to this same dsname.
Action:
Use the DISPLAY DATA command to list data sets allocated to CA-L-Serv.
Review CA-L-Serv's logs to determine why the data set is allocated to CA-L-Serv and if a prior REMOVEFILE command failed to de-allocate the data set.
If any operational problems are detected, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An ADDFILE command was issued against a non-VSAM data set. CA-L-Serv does not support the file organization shown in dsorg. (This value is shown as four hexadecimal digits taken from the dynalloc control block.)
Action:
Reissue the ADDFILE command specifying a VSAM file.
Reason:
An attempt was made to activate a component of CA-L-Serv through an ATTACH command but the component is active.
Action:
None. This is only CA-L-Serv's response when an attempt is made to activate a second file server or communications server in a given CA-L-Serv region.
Reason:
A file server request could not be serviced because the function code was invalid. An installation error may have occurred. Request type xxxx and address yyyy are displayed to help determine the cause of the problem.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The file server could not service the request because context information was missing or invalid. The values displayed as part of the message will help CA Support determine the cause of the problem.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An error occurred while VSAM was processing an OPEN request for the specified ddname. (Another job or task may be using this data set.) The file is marked as ERROR in the database display and cannot be used until the error is corrected.
Action:
Look up the error code in the appropriate VSAM macro reference manual and correct the error. Then use the OPENFILE command to make the file available.
Reason:
An error occurred following a VSAM open for the specified ddname. Code1 represents the VSAM function, which was invoked when the error occurred while code2 and code respectively indicate the return-code and the feedback code upon returning from VSAM.
Action:
Look up the return-code and feedback code in the appropriate VSAM macro reference manual and correct the error. Then use the OPENFILE command to make the file available.
Reason:
The file server experienced an abend while it serviced a request. The request is suspended and an SVC dump is requested. The message is issued while the file server is attempting to recover from the abend.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv successfully processed a request to create shared VSAM buffer pool nn.
Action:
None.
Reason:
An attempt was made to create shared buffer pool nn that had been defined to VSAM through a prior ADDPOOL command.
Action:
Use the DISPLAY BUFFER command to list the defined shared buffer pools. Review CA-L-Serv's logs to determine when the buffer pool was defined.
Reason:
A VSAM error occurred when CA-L-Serv tried to build a buffer pool.
Action:
Look up the value for code in your VSAM macro reference manual (macro BLDVRP). Usually, a shortage in storage space (RC=8) causes this problem. If so, reduce the number of buffers in the pool or increase the value for the REGION parameter in CA-L-Serv's start-up procedure.
Reason:
A file server request failed for ddname ddname. The function being performed by the File Server is represented by a two-digit (xx) value, which is usually of interest only for CA Support. However, values 0-5 are reserved for I/O requests and are consistent with the VSAM terminology found in the RPLREQ field of the RPL macro - 0=GET, 1=PUT and so on. A number of other function codes correspond to internal requests, which fall outside the scope of this manual.
Action:
See the information on the applicable return and reason codes.
If necessary retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
These messages display information for all managed files in response to the DISPLAY DATABASE command.
For each file, CA-L-Serv displays:
Action:
None.
Reason:
These messages display information for all managed files in response to the DISPLAY DATABASE command.
For each file, CA-L-Serv displays:
Action:
None.
Reason:
These messages display information for all managed files in response to the DISPLAY DATABASE command.
For each file, CA-L-Serv displays:
Action:
None.
Reason:
A command such as REMOVEFILE or DISPLAY DATA specified ddname ddname that is not under CA-L-Serv's control.
Action:
Use the DISPLAY DATA command to list all data sets under CA-L-Serv's control. If appropriate, reissue the command specifying the correct ddname.
LDM0010I BUFFERSIZE=bytes LDM0010I COMMSERVERSSN=ssname LDM0010I MAXDORM=seconds LDM0010I SERVERTYPE=type
Reason:
These messages are displayed in response to the DISPLAY TASK(FILESERVER),OPTIONS command.
One of the following values appears on SERVERTYPE:
Action:
None.
Reason:
An attempt was made to refer to file group xxx but the file group does not exist.
Action:
See the information about file groups and the commands that allow the monitoring of file groups.
Reason:
The file server is inactive.
Action:
Take one or more of these actions:
Reason:
A RELEASEFILE command against file ddname was successfully processed by CA-L-Serv.
Action:
None.
Reason:
A CLOSEFILE command against file ddname was successfully processed by CA-L-Serv.
Action:
None. The file is unavailable to users and jobs until it is reopened by an OPENFILE command.
Reason:
An OPENFILE command against file ddname was successfully processed by CA-L-Serv.
Action:
None. The file is now available to users and jobs.
Reason:
A REMOVEFILE command against file ddname was successfully processed by CA-L-Serv.
Action:
None. The file is de-allocated from CA-L-Serv and is now available to other jobs.
Reason:
A HOLDFILE command against file ddname was successfully processed by CA-L-Serv.
Action:
None. The file is now unavailable to users and jobs.
Reason:
A file management command, such as OPENFILE or CLOSEFILE, referred to file ddname but the file is not under CA-L-Serv's management.
Action:
Use the DISPLAY DATA command to list all data sets managed by CA-L-Serv. Determine why the ddname specified on the command does not correspond to a file under CA-L-Serv's management.
Reason:
All files in a file group must share certain attributes such as logical record length, key length and key offset (for KSDS files).
Action:
See the discussion of file groups and their characteristics.
Reason:
VSAM deferred writes are only available to LSR data sets. Because no buffer pool was specified on the ADDFILE command CA-L-Serv will attempt to open the data set NSR.
See the CA-L-Serv administrating/reference topics and to the IBM manual z/OS DFSMS Using Data Sets for a discussion of NSR and LSR restrictions as well as information about private and shared buffer pools.
Action:
Specify a valid buffer pool on the ADDFILE command and reissue the command. If no suitable buffer pool exists for the data set use the ADDPOOL command to define the buffer pool.
Reason:
A buffer pool specified on an ADDFILE command does not exist.
Action:
Review CA-L-Serv's logs to determine why the buffer pool does not exist and whether a prior ADDPOOL command failed. If the ADDPOOL command failed determine the cause of the error and reissue the command after correcting the problem.
If the error cannot be corrected or if any operational problems are detected, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
File ddname was successfully opened by the file server.
Action:
None.
Reason:
File ddname was successfully closed by the file server.
Action:
None.
LDM0547I Ddname PUT SEQ GET DIR GET ERASE RETRY LDM0549I ddname nn nn nn nn nn LDM0550I [avg. n.n n.n n.n n.n n.n]
Reason:
In response to the DISPLAY STATISTICS command, these messages display counts of VSAM file I/O activity.
ddname of a managed file. If you specify a ddname on the DISPLAY command, CA-L-Serv displays information about that file only. Otherwise, it displays information about all managed files.
Number of logical write requests issued for the data set.
Number of logical read requests issued for the data set in sequential mode.
Number of random read requests issued for the data set.
Number of records deleted from the data set.
Number of I/O requests that had to be retried.
If you specify the SERVICE operand on the DISPLAY command, CA-L-Serv displays average service times (in milliseconds) in message LDM0550I.
Action:
None.
LDM0553I Pool Size Count BFRFND BUFRDS UIW NUIW LDM0554I nn nn nn nn nn nn nn
Reason:
In response to the DISPLAY BUFFER command, these messages display information about LSR buffer pools.
Number assigned to a buffer pool.
Size (in bytes) of one set of buffers in the pool.
Buffers of a given size contained in the pool.
Number of read requests that could be satisfied without an I/O operation because VSAM found the data in a buffer.
Number of times VSAM had to bring data into a buffer.
Number of user-initiated write (PUT) requests.
Number of write requests initiated by VSAM buffer management. These are write operations that VSAM was forced to do because no buffers were available for reading the contents of a control interval.
For additional information on keywords BFRFND, BUFRDS, UIW, and NUIW as well as the interpretation of the figures listed under these headings, see the IBM manual Using Data Sets relevant to your z/OS level.
Action:
None.
LDM0556I System Type Sends Receives Resp Split LDM0557I sysname type nn nn nn nn
Reason:
These messages display information about all systems where the file server is running:
System name.
Type of server. Possible values are LOCAL, REMOTE, and HOST.
Number of send requests issued by this server.
Number of receive requests issued by this server.
Average response time (in milliseconds) per receive request.
Number of times CA-L-Serv split large records to get them to fit in a data buffer.
Action:
None.
Reason:
There are no other file servers active in the complex.
Action:
None.
Reason:
The maximum default interval between deferred writes is nn seconds. For additional information on the MAXDORM keyword, see message LDM0526I and the administrating/reference topics.
Action:
None.
Reason:
An all-purpose message that displays information about the file server in response to commands such as DISPLAY ALL and DISPLAY DATABASE.
Action:
None.
Reason:
There are no data sets under the control of the file server. This informational message is typical of a remote file server.
Action:
None.
Reason:
The operator issued a command that is only supported on CA-L-Serv regions that run a local or a host file server. Examples of such commands are the ADDFILE and ADDPOOL commands, which cannot be issued against remote systems.
Action:
Review CA-L-Serv's logs to locate the command that caused the message to be displayed. Determine why the command was issued against a remote system.
Reason:
This messages indicates that the client executing in the referenced address-space (ASCB=xx, TCB=yy, FCG/ASID=zz) has terminated without ending this session with CA-L-Serv.
Action:
None.
Reason:
An attempt was made to place data set filename under CA-L-Serv's control, but the attempt failed because the data set was under the control of another CA-L-Serv.
Note: This message may also be displayed because the data set is under the control of a client application such as CA Endevor Software Change Manager.
Action:
Review the system logs to determine why the data set is under the control of another CA-L-Serv or has been allocated by CA Endevor Software Change Manager users. This may occur after CA-L-Serv was shut down and restarted. Depending on the operational circumstances, you may need to terminate all jobs and users holding ENQ's with a major name of LSERVDSN before you can successfully place the data set under CA-L-Serv's control. When a number of data sets are involved, it may be preferable to terminate all jobs and users and restart CA-L-Serv than attempting to address each data set individually.
Reason:
There are no data sets under the control of the file server. This informational message is also issued in response to a DISPLAY DATABASE command on a remote file server.
Action:
None. This message is informational.
Reason:
A file management command, such as OPENFILE or CLOSEFILE, specified file ddname, but the file is not under CA-L-Serv's management.
Action:
Use the DISPLAY DATA command to list all data sets currently managed by CA-L-Serv. Determine why ddname filename is not under CA-L-Serv's management.
Reason:
The CA-L-Serv kernel has successfully activated the scheduler component of CA Bundl. For more information on the scheduler, see the CA Bundl documentation.
Action:
None.
Reason:
The scheduler component of CA Bundl has terminated. For more information on the scheduler component, see the CA Bundl documentation.
Action:
None.
LDM0603I Name Status Date Time LDM0604I name status date time
Reason:
These messages display information about scheduled events. For each event (identified by name), the current status is shown as follows:
The date and time variables indicate the next time that the event is scheduled to take place.
Note: For information on the scheduler, see the appropriate CA Bundl documentation.
Action:
None.
Reason:
CA-L-Serv is not managing the schedule database you specified. For additional information on the scheduler, see the CA Bundl documentation.
Action:
Check the ddname that you specified on the ATTACH command. If it is misspelled, reissue the command. If the ddname is correct, issue an ADDFILE command for the ddname.
Reason:
An installation error or a short-on-storage condition may have occurred.
Action:
Look for a z/OS IEAxxxxx or IEFxxxxx message or a dump, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
This member is not located in the data set pointed to by the //JCLLIB DD statement. The member name may have been misspelled on the CA Bundl SCH Detail Screen.
Action:
Check the spelling of the member name on the CA Bundl screen. If it is correct, check that the member is contained in the CA Bundl CNTL library.
Reason:
The processing of member member was cancelled by the indicated module.
Action:
For more information on the scheduler component, see the CA Bundl documentation.
Reason:
An I/O error occurred in the scheduler component of CA Bundl.
Action:
Take the appropriate action:
Reason:
For information on the scheduler, see the CA Bundl documentation.
Action:
None.
Reason:
No scheduler events are defined to the scheduler component of CA Bundl.
Action:
None.
Reason:
The OPTIONS command specified an unknown event.
Action:
For additional information, see the CA Bundl documentation.
Reason:
A host file server is active on system sysname.
Action:
Attach the file server on the local system as a remote file server or detach the current host file server, then attach the local file server as the host.
Reason:
The file server failed to initialize a session with the communications server. The file server terminates.
Action:
Use the values specified for xx and yy to determine the cause of the error and the corresponding response.
If xx is 0 or 4, yy is one of the following:
If xx is anything except 0 or 4, ignore yy and look up the value for xx as follows:
Reason:
This message is issued at one-minute intervals until the communications server has initialized.
Action:
Start the communications server on the local system. If you experience problems activating the communications server, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A remote file server is attempting to establish communication with the host file server but the host file server is not active. The attempt will be retried at one-minute intervals until successful.
Action:
Attach the host file server. If the system that usually runs the host file server is experiencing problems, you can detach the remote file server and attach it as the host.
Reason:
A remote file server attempted to locate the HOST system but the attempt was unsuccessful.
Action:
Use the values of xx and yy to determine the cause of the error and the corresponding response.
If xx is 0, yy is one of the following:
If xx is anything except 0 or 4, ignore yy and look up the value for xx as follows:
Reason:
The communications server has terminated the local file server's session. This message is informational.
Action:
None.
Reason:
The communications server on the local system has terminated.
Action:
None
Reason:
The file server established a session with the communications server identified by ssname. This file server is a host server (if HOST is shown) or a remote server (if RMT is shown).
Action:
None.
Reason:
An external system (sysname) joined the configuration. The file server on that system is the host server (if HOST is shown) or a remote server (if RMT is shown). The communications server being used is further identified by ssname.
Action:
None.
Reason:
An external system (sysname) left the configuration. The file server on that system is the host server (if HOST is shown) or a remote server (if RMT is shown). The communications server being used is identified by ssname.
Action:
If that system was a host system, other systems will not be able to access files until it is restarted or you designate a new host system.
Reason:
The local communications server attempted to receive data from one of its partners but the receive failed.
Action:
Use the values of xx and yy to determine the cause of the error. If xx is 0, yy is one of the following:
If xx is anything except 0 or 4, ignore yy and look up the value for xx as follows:
Reason:
Accumulated length of the transmission is not valid. The communications server abends the request.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The local communications server attempted to send data to one of its partners but the send failed.
Action:
Try to determine the cause of the error by looking at xx and yy. If xx is 0, yy is one of the following.
If xx is anything except 0 or 4, ignore yy and look up the value for xx as follows:
Reason:
The local communications server received invalid data from the communications server executing on system system.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
This is the first message in CA-L-Serv's message log. It displays the date and the system's sysid.
Action:
None.
Reason:
A multiple line WTO failed with return code = code.
Action:
See the appropriate IBM manual for a list of possible return codes for multiple line WTOs.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv did not find the message identified by xxxx in any of its message tables.
Action:
Verify that the corresponding message table is allocated to CA-L-Serv and that the message was not accidentally removed from the message table. If you have recently upgraded CA-L-Serv or any client applications, verify that the corresponding message tables were also upgraded.
Reason:
The log server component of CA-L-Serv abended. CA-L-Serv tries to recover from the abend.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An error occurred when CA-L-Serv's log server attempted to open log logname.
Action:
Review CA-L-Serv' logs and the system log for IECxxxx messages explaining the cause of the error.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An I/O error occurred when CA-L-Serv's log server attempted to write to log logname.
Action:
Review CA-L-Serv's logs and the system log for IECxxxx messages explaining the cause of the error.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
Log logname has been disabled. Logging for this log will be directed to the default log.
Action:
Review CA-L-Serv's logs and the system log for additional LDMxxxx and IECxxxx messages that may explain the cause of the error.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An ADDLOG command was successfully processed.
Action:
None.
Reason:
An ADDLOG command failed because the data set whose dsname was specified on the command is not cataloged.
Action:
Review CA-L-Serv's message log and reissue the command with the correct dsname.
Reason:
The entries for log logname will now be written to SYSOUT CLASS or data set xxxx.
Action:
None.
Reason:
Logging to log logname has terminated. This normally follows a successfully processed CLOSELOG command.
Action:
None.
Reason:
The logical record length (LRECL) of the new log file is not the same as the LRECL of the old log file. This occurs after a log switch when the logging for logname was directed to a wrap-around series of data sets through the DDNAMES or DSNAMES options of the ADDLOG command.
Action:
Define files so that they have the same LRECL value.
Reason:
A REMOVELOG command issued against logname was successfully processed.
Action:
None.
Reason:
CA-L-Serv encountered a dynamic allocation error when it attempted to allocate file ddname for log logname. CA-L-Serv provides a return code in the format xx-yyyy-zzzz, where xx is the R15 return code from SVC 99; yyyy is the reason code; and zzzz is the error reason code.
Action:
See the appropriate IBM publication to determine the meaning of the codes. If this is not an operational error, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv could not allocate or access the indicated log file. CA-L-Serv drops the file from the list of files for that log. If other files can be accessed successfully, CA-L-Serv continues log processing with a reduced file list.
Action:
To work from a full file list, correct the problem. Then use the REMOVELOG command to delete the log definition, followed by the ADDLOG command to redefine the log file.
Reason:
Log logname was allocated to a group of cataloged data sets through the DDNAME or DSNAMES options of the ADDLOG command. None of the data sets are accessible. This message follows messages LDM0721E and LDM0724E. This message is also issued when the ADDLOG command specifies a log name that is allocated.
Action:
Review CA-L-Serv's logs to determine the cause of the problem. Use the REMOVELOG command to delete the log definition, followed by the ADDLOG command to redefine the log file.
Reason:
CA-L-Serv must run under the Job Entry Subsystem to direct logging to SYSOUT data sets.
Action:
Redirect the log to cataloged data sets, or run CA-L-Serv under JES. Note, that when the procname is the same as the subsystem name, the z/OS START command causes the target started task to run under the z/OS Master Scheduler rather than the Job Entry Subsystem. Under these circumstances, it is necessary to direct CA-L-Serv to execute under the Job Entry Subsystem by using the SUB=JESx keyword of the z/OS START command.
Reason:
Dynamic allocation failed for file ddname because the corresponding data set could not be located.
Action:
Verify the spelling of the data set name on the ADDLOG command.
Reason:
The CA-L-Serv log logname is now available. This message indicates that the log server has successfully opened the corresponding file or that an OPENLOG command was successfully processed.
Action:
None.
Reason:
An ADDLOG command was issued with the DDNAMES option. There is no corresponding DD statement for xxxx in the CA-L-Serv start-up procedure.
Action:
Add the DD statement to the CA-L-Serv procedure and recycle CA-L-Serv or issue the ADDLOG command from the console specifying the DSNAMES keyword if CA-L-Serv cannot conveniently be restarted.
Reason:
The displayed log ID is in use by a log automatically defined by CA-L-Serv.
Action:
Specify a different log id in the ADDLOG command for this log.
Reason:
The displayed log ID cannot be the target of a REMOVELOG command because it defines a log that is vital to CA-L-Serv operation.
Action:
You may use the PRINTLOG command to spin off the log to a SYSOUT class where you will be able to print or purge it.
Reason:
A log directed to a SYSOUT class could not be opened because JES is not available. The messages destined for the log will be written to the system log.
Action:
Determine why the Job Entry Subsystem is not available. Review the CA-L-Serv's logs and the system log for other LDMxxxx messages or IBM messages that could help determine the cause of the problem.
Reason:
The log server encountered an error while attempting to reposition against log logname.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv was performing operation optcode when it encountered an error while writing messages to a log file.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The log server encountered an error while attempting to reposition against a log data set
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An ADDLOG command was issued specifying two or more DDNAMES. CA-L-Serv found that at least one of the ddnames is allocated to a SYSOUT class in CA-L-Serv's start-up procedure.
Action:
Issue the ADDLOG in one of the following ways:
Reason:
CA-L-Serv found a data set with an unsupported data set organization in a group of files allocated to a log.
Action:
To work from a full file list, correct the problem by allocating a data set with the appropriate data set organization. Then use the REMOVELOG command to delete the log definition, followed by the ADDLOG command to redefine the log file.
Reason:
CA-L-Serv was unable to open a data set in a file list.
Action:
To work from a full file list, review CA-L-Serv's logs and the system log looking for IECxxxx messages, which will help determine the reason why the OPEN for the data set failed.
If unable to determine the cause of the failure, collect the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
CA-L-Serv could not locate a log file on the volume identified by the JCL.
Action:
Determine why the log file does not reside on the specified volume. Use the ADDLOG command to specify a new log data set.
Reason:
The WRITELOG command was processed successfully.
Action:
None.
Reason:
You issued a SWITCHLOG command for the indicated logname, but one of the following problems occurred:
Action:
Use the DISPLAY LOGS command to verify that multiple data sets are defined for the log and that none of them is allocated to a SYSOUT class.
Reason:
The SWITCHLOG command was processed successfully.
Action:
None.
Reason:
The logid specified on the command is invalid.
Action:
See the CA-L-Serv Command Reference for additional information concerning syntax and usage rules relative to log names.
Reason:
CA-L-Serv's log server task is disabled. All messaging will now use WTO's and will be directed to the system log.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
You issued a PRINTLOG command for a log file that was not defined as a SYSOUT class.
Action:
Check the spelling of the log name on the PRINTLOG command. If the log name is spelled correctly, use the ADDLOG command to redefine the log file as a SYSOUT class.
Reason:
A PRINTLOG command was issued against log logname but the log is not active.
Action:
Review CA‑L-Serv's logs to determine why the log is inactive.
Reason:
The PRINTLOG command was processed successfully. Log logname will now be directed to a new sysout data set. The old sysout data set can now be purged or printed.
Action:
None.
Reason:
No logs are available to CA-L-Serv. The message will be written to the system log through WTOs.
Action:
Review the CA-L-Serv's job log and the system log to determine why no logs are available.
Collect the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
LDM0751I Log name Status Count Time File name LDM0752I log name status nn time filename
Reason:
These messages display information about CA-L-Serv's logs, as follows:
The name TRACE refers to the trace log; the name MSGLOG refers to the message log. All other names refer to data base change logs or auxiliary message logs.
Status of the log.
Number of records in the log file.
Time that the last record was written to the log file.
Data set names or sysout class assigned to the log.
Action:
None.
Reason:
You issued a DISPLAY LOGS or DISPLAY ALL command but there are no logs defined to CA-L-Serv.
Action:
None.
Reason:
The LDMAMS utility encountered an invalid SYSIN statement.
Action:
Correct the SYSIN statement and resubmit the job.
Reason:
The operand specified on the LDMAMS statement is invalid.
Action:
See the full description of the LDMAMS statement.
Reason:
Unmatched parentheses in an LDMAMS statement.
Action:
See the statement's syntax details.
Reason:
The LDMAMS utility could not establish a session with CA-L-Serv.
Action:
Verify that CA-L-Serv is active and that the job running the LDMAMS utility indicates the correct subsystem name (through the SSN$xxxx DD DUMMY statement).
If this is not an operational error, call CA Support.
Reason:
The LDMAMS utility needs the data set specified in the SYSIN statement with the infile or outfile keyword to be allocated in the job's JCL.
Action:
Add the DD statement to the JCL and resubmit the job.
Reason:
The LDMAMS utility encountered an error when it tried to open the input or output file.
Action:
Review the job's log looking for a z/OS IEC141 message that explains the error more fully.
Reason:
CA-L-Serv could not obtain exclusive control of the input file. A file server problem occurred.
Action:
The file may currently be accessed by online users or another LDMAMS job. You may have to reschedule the LDMAMS job later.
Reason:
The LDMAMS utility has successfully reset the contents of data set outfile.
Action:
None.
Reason:
CA-L-Serv could not find text for message xxxx in its message table. The message is discarded.
Action:
Verify that the corresponding message table is allocated to CA-L-Serv and that the message was not accidentally removed from the message table. If you have recently upgraded CA-L-Serv, verify that the CA-L-Serv message table was also upgraded.
Reason:
The LDMAMS utility has successfully performed a REPRO operation from VSAM data set infile to sequential data set outfile copying nn records.
Action:
None.
Reason:
The LDMAMS utility detected an error in a previous SYSIN statement. The ensuing statements are ignored.
Action:
Review the LDMAMS job log and SYSPRINT for possible causes. Depending on the error, review the CA-L-Serv's logs for other messages.
Reason:
The LDMAMS utility performed a REPRO from sequential data set infile to VSAM data set outfile with the REPLACE option specified. The message displays statistics about the result of the process.
Action:
None.
Reason:
The LDMAMS utility found a syntax error in a REPRO statement specifying the FROMKEY or TOKEY keywords.
Action:
See the full description of LDMAMS statements.
Reason:
An error occurred when CA-L-Serv tried to delete the contents of a VSAM file. The file may be in use by another task or user, or it may not be managed by CA-L-Serv.
Action:
Verify that the file is not in use by another task or user, that it is managed by CA-L-Serv and that the cluster was defined with the REUSE attribute.
Reason:
CA-L-Serv encountered an error when it tried to copy a record from a VSAM file to a sequential file. The message may occur if someone issues a SHUTDOWN or CLOSEFILE command before the LDMAMS utility completes its operation.
Action:
Review CA-L-Serv's logs for additional messages issued at the same time. See the list of CA-L-Serv's return codes in this reference.
If this is not an operational problem, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An error occurred when CA-L-Serv tried to write a record from a sequential file to a VSAM file. The message may occur if someone issues a SHUTDOWN or CLOSEFILE command before the LDMAMS utility completes its operation.
Action:
Review CA-L-Serv's logs for additional messages issued at the same time. See the list of CA-L-Serv's return codes in this reference.
If this is not an operational problem, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The LDMAMS utility does not support spanned record format for sequential data sets.
Action:
Reallocate the data set ddname with a record format of FB or VB and rerun the job.
Reason:
CA-L-Serv encountered an error when it tried to open the input or output file.
Action:
Use the DISPLAY DATABASE to verify that the data set is under CA-L-Serv's control.
Review CA-L-Serv's logs or the system log for IECxxxx messages, which may explain the cause of the problem. See the list of CA-L-Serv's return codes in this reference.
If this is not an operational problem, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An external security problem occurred when CA-L-Serv tried to access ddname.
Action:
Address the security problem and resubmit the job.
Reason:
The LDMAMS utility detected that neither the INFILE nor GROUP keyword was specified on an ARCHIVE statement.
Action:
Correct the ARCHIVE statement.
Reason:
The LDMAMS utility detected that file group xxxx is not defined to CA-L-Serv.
Action:
Define the file group to CA-L-Serv and resubmit the job.
Reason:
INFILE and GROUP were specified on an ARCHIVE statement but file xx is not part of group yy.
Action:
Use the DISPLAY DATABASE command to display the group and specify one the files belonging to the group.
Reason:
A file in a file group must be full to be eligible for archiving. The LDMAMS utility did not find any files in file group xx that were full.
Action:
Review CA-L-Serv's logs to determine if any of the files on the file group were eligible for archiving. If this is not an operational error, call CA Support.
Reason:
An archive or repro operation copied nnn records from file to ddname.
Action:
None.
Reason:
The LDMAMS utility successfully completed the ARCHIVE operation.
Action:
None.
Reason:
The LDMAMS utility detected that target data set xxxx is empty and that no archiving is necessary.
Action:
None.
Reason:
A record's logical record length exceeds the OUTPUT file's maximum LRECL value.
Action:
Increase the OUTPUT file's maximum LRECL value to accommodate the largest LRECL value for any record in the source file.
Reason:
The LDMAMS job was unable to establish communication with CA-L-Serv.
Action:
Verify that CA-L-Serv is active and that the //SSN$xxxx DD DUMMY statement in the LDMAMS JCL specifies the correct subsystem name.
Reason:
This message is issued when using the LDMAMS utility to verify the successful installation of the communications server. For a complete description of the communications server's installation verification procedure, see the CA-L-Serv implementing topics.
Action:
When the communications server IVP runs successfully, you will receive a return-code and a reason code of 0. Otherwise, see the list of return and reason codes, correct the problem and rerun the communications server's IVP.
Reason:
When running the communications server's installation verification procedure, these messages display the IDs of the applications you created to test communication routes.
Action:
None.
Reason:
When running the communications server's installation verification procedure, these messages display the IDs of the applications you created to test communication routes.
Action:
None.
Reason:
When running the communications server's IVP, this message displays basic information about the data transfer.
Action:
For additional information concerning the communications server IVP, see the implementing topics.
Reason:
When running the communications server's IVP, this message indicates that the receiving application is unable to see the sending partner.
Action:
For additional information concerning the communications server IVP, see the implementing topics.
Reason:
The receiving job in the communications server IVP has exceeded the time limit specified with the LIMIT parameter of the WAIT statement and did not receive any data.
Action:
For additional information concerning the communications server's installation verification procedure, see the implementing topics.
Reason:
When running the communications server's IVP using VTAM communication, this indicates a problem with the SYS1.VTAMLST definitions necessary for two copies of CA-L-Serv to be able to communicate.
Action:
Make sure CA-L-Serv's application ID (specified on the ACBNAME operand for the ATTACH command) matches CA-L-Serv's VTAM application ID in your SYS1.VTAMLST data set.
If they do match, collect the appropriate diagnostic information (VTAM definitions and DISPLAYs, CA-L-Serv command member) and call CA Support.
Reason:
CA-L-Serv issued an OPEN against VTAM ACB applid but the ACB was open.
Action:
Change CA-L-Serv's application ID on the ATTACH command's ACBNAME operand and in your SYS1.VTAMLST data set to point to an ACB not open to another task on the system.
Reason:
The communications server will try to reestablish its VTAM session after VTAM performs cleanup processing for CA-L-Serv.
Action:
Look for VTAM messages that tell you whether the session was reestablished.
Reason:
The communications server is in a suspended state because its VTAM application ID was not active when you started it.
Action:
Take one of these actions:
Reason:
The communication route between source and target has been successfully established.
Action:
None.
Reason:
The communication server detected a mismatch in the RECBUFFSIZE definitions.
Action:
Make the values for the ATTACH command's RECBUFFSIZE operand match on all systems and restart communications servers.
Reason:
An invalid BIND was passed between systems.
Action:
Check your VTAM definitions for CA-L-Serv. Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A VTAM error occurred. An application ID, return code, and control block field's contents (xxxx) are shown.
Action:
Consult your VTAM manuals for an explanation of the codes.
If this is not an operational problem, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A VTAM error occurred.
Action:
Consult your VTAM manuals for an explanation of the codes.
If this is not an operational problem, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The communications server is not active on the target system yet.
Action:
Check that CA-L-Serv and the communications server are active on the target system.
Reason:
The route is inactive.
Action:
Use the ACTIVATE resource command to activate the route on the local system.
Reason:
These messages identify the exact level of VTAM running on your systems. They are among the first messages written to the communications server log.
Action:
None.
Reason:
These messages identify the exact level of VTAM running on your systems. They are among the first messages written to the communications server log.
Action:
None.
Reason:
A VTAM macro abended. See VTAM manuals for additional information concerning the return code, feedback code, and sense code.
Action:
You do not have to take an action unless you experience further problems.
Reason:
A VTAM macro abended. See VTAM manuals for additional information concerning the return code, feedback code, and sense code.
Action:
You do not have to take an action unless you experience further problems.
Reason:
A VTAM macro abended. See VTAM manuals for additional information concerning the return code, feedback code, and sense code.
Action:
You do not have to take an action unless you experience further problems.
Reason:
Your version of VTAM does not support LU 6.2 protocols.
Action:
Change the CONTYPE operand's value on the ATTACH commserver or ACTIVATE command from LU62 to LU 0.
Reason:
The version of VTAM on the target system does not support LU 6.2 protocols.
Action:
Change the CONTYPE operand's value on the ATTACH commserver or ACTIVATE command from LU62 to LU 0 on both the source and the target systems.
Reason:
This message is issued in response to a successful ACTIVATE command.
Action:
None.
Reason:
This message is issued in response to an ACTIVATE command: the activate failed because the route is active.
Action:
Review CA-L-Serv's logs to determine why the route is active.
Reason:
The ACB specified on the ATTACH COMMSERVER command and the route specified on the ACTIVATE command are the same.
Action:
The ACB name specified on the ACTIVATE command must be different from the ACB name specified on the ATTACH COMMSERVER command.
Reason:
This message indicates that route xxx has been deactivated.
Action:
None.
Reason:
This message is issued in response to a DEACTIVATE command: the command failed because the route is not active.
Action:
Review CA-L-Serv's logs to determine why the route is not active.
Reason:
The maximum number of users of the communications server is exceeded.
Action:
Stop the communications server, and increase the value for the MAXSESSIONS operand on the server's ATTACH command.
Reason:
The local system attempted to activate a route but the target system is not responding.
Action:
Activate a route from the target system to the source system.
Reason:
The communications server initialization has completed successfully.
Action:
None.
Reason:
The communications server has terminated.
Action:
None.
LDM0010I ACBNAME=name LDM0010I CONTYPE=protocol LDM0010I HOLDBUF=nnn LDM0010I LOGID=logname LDM0010I RETRMAX=nnn LDM0010I RETRY=nnnnn LDM0010I SENDLIMIT=nnn LDM0010I XCF=[YES|NO]
Reason:
These messages display operating values that you can change while the communications server is running:
VTAM application ID for CA-L-Serv.
VTAM communications protocol that the server is using.
Maximum number of transmission buffers per client.
Name of the auxiliary message log for the communications server.
Maximum number of attempts to reactivate an inactive VTAM route. The server retries indefinitely when 0 is shown.
Attempts to reactivate an inactive VTAM route. The server will not try to reactivate the route when 0 is shown. The retry interval is measured in seconds.
Maximum number of pending send requests per client.
Indicates whether the XCF method of data transmission is active.
Action:
None
LDM0010I ACBNAME=applid LDM0010I MAXSENDSIZE=nnn LDM0010I MAXSESSIONS=nnn LDM0010I RECBUFFSIZE=nnn LDM0010I XCF=[YES|NO]
Reason:
These messages display operating values that you cannot change while the communications server is running:
VTAM application ID for CA-L-Serv.
Maximum data size during transmission, in kilobytes.
Maximum number of concurrent sessions with the server.
Size of the server's transmission buffers.
Indicates whether XCF was activated.
Action:
None
LDM0913I Route Status Contype Retry RETRMAX LDM0914I route status protocol nnnnn nnn LDM0917I nodename
Reason:
These messages display information about communication routes:
Target system's ACB name for VTAM routes or the XCF system name for XCF routes.
ACTIVE or INACTIVE.
Communications protocol that the server is using for this route. (For XCF routes, XCF is displayed. For VTAM routes, LU0 or LU6.2 is displayed.)
Interval for attempts to reactivate this route if it becomes inactive. The server does not try to reactivate the route when 0 is shown. The retry interval is measured in seconds.
Maximum number of attempts to reactivate this route if it becomes inactive. The server retries indefinitely when 0 is shown.
Internal node name for a client that is using the communications server.
Action:
None
Reason:
One of these messages will follow LDM0912I if there were no active or inactive routes to display information about.
Action:
None
Reason:
One of these messages will follow LDM0912I if there were no active or inactive routes to display information about.
Action:
None.
LDM0010I DYNAMIC=value LDM0010I PRIORITY=value
Reason:
These messages display client application default values.
Action:
None.
LDM0921I Application Status Pty ---Sends--- --Receives- LDM0922I productid status x x y x y
Reason:
These messages display information about clients using the communications server:
Product ID for a client.
Maximum priority for requests from the client.
H - High
N - Normal
L - Low
Number of pending (x) and completed (y) send requests from this client.
Number of pending (x) and completed (y) receive requests from this client.
Action:
None
Reason:
There are no clients in session with the communications server.
Action:
None.
Reason:
The communications server tried nn times (the maximum number of times) to reactivate this route.
Action:
None.
Reason:
An ACTIVATE or DEACTIVATE command was issued for a VTAM route, but no ACB name was provided to enable VTAM when the communications server was started. ACTIVATE and DEACTIVATE commands are only valid for VTAM.
Action:
Refer to additional information concerning the communications server.
Reason:
You cannot activate or deactivate an XCF route using these commands. ACTIVATE and DEACTIVATE commands are only valid for VTAM communication.
Action:
See the description of the XCF component of the communications server.
Reason:
An attempt was made to initialize XCF communication but it is active.
Action:
Review CA-L-Serv's logs to determine why the XCF component is active.
Reason:
An attempt was made to start up the communications server using XCF, but XCF is not available on this system.
Action:
To implement XCF, you must be running MVS 4.0 at a minimum.
Reason:
The XCF component of the communications server is active.
Action:
Review CA-L-Serv's log and determine why the XCF component is active.
Reason:
The XCF component of the communications server has initialized.
Action:
None.
Reason:
The XCF component of the communications server has terminated.
Action:
None.
Reason:
The communications server has initialized.
Action:
None.
Reason:
The communications server has terminated.
Action:
None.
Reason:
A command was directed towards the communications server, but it is not active.
Action:
Review CA-L-Serv's logs to determine why the communications server is not active. If relevant use the ATTACH command to restart the communications server.
Reason:
A command was directed towards the XCF component of the communications server, but it is not active.
Action:
Use the DISPLAY command or review CA-L-Serv's logs to determine the active options of the communications server. If the XCF component of the communications server needs to be activated, detach the communications server and reattach it specifying the XCF=YES option.
Reason:
A subtask of the communications server ended abnormally with a completion code of completioncode.
Action:
Stop the communications server with the DETACH command and restart it with the ATTACH command to revive the communications server. Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The communications server is terminating because the XCF component did not initialize successfully.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The XCF component did not initialize successfully.
Action:
The nature of the problem can be determined by looking up the listed return and reason codes in IBM's z/OS MVS Programming: Sysplex Services Reference Guide under the IXCJOIN macro.
If this is not caused by an operational problem in your environment, retain the appropriate diagnostic information and call CA Support.
Reason:
The XCF component did not terminate successfully.
Action:
The nature of the problem can be determined by looking up the listed return and reason codes in IBM's Authorized Assembler Reference Guide under the IXCLEAVE macro.
If this is not an operational problem in your environment, retain the appropriate diagnostic information and call CA Support.
Reason:
The XCF component did not initialize successfully.
Action:
The nature of the problem can be determined by looking up the listed return and reason codes in IBM's z/OS MVS Programming: Sysplex Services Reference Guide under the IXCQUERY macro.
If this is not an operational problem in your environment, retain the appropriate diagnostic information and call CA Support.
Reason:
The XCF component did not initialize successfully.
Action:
The nature of the problem can be determined by looking up the listed return and reason codes in IBM's Authorized Assembler Reference Guide under the IXCQUERY macro.
If this is not an operational problem in your environment, retain the appropriate diagnostic information and call CA Support.
Reason:
An attempt was made to activate an XCF communication route to the named system, but a VTAM route to that system was active.
Action:
If you decide to use XCF communications between the two systems, attach the communications server specifying XCF=YES and delete the ACTIVATE statements from the start-up command members.
Reason:
An XCF data transmission failure occurred due to an internal XCF problem. The data transmission may have been lost.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An XCF end-event procedure failed due to an internal XCF problem. The data transmission was successful.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The communications server was forced to end the specified mode of operation, but it did not shut down completely.
Action:
Stop the communications server with the DETACH command and restart it with the ATTACH command.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An abend occurred during XCF processing. If the XCF component does not recover, message LDM1135E is also issued. The data transmission may have been lost.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An abend occurred during XCF processing. If the XCF component does not recover, message LDM1135E is also issued. Status information about data transmissions may have been lost.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An abend occurred during XCF processing. If the XCF component does not recover, message LDM1135E is also issued.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An abend occurred during XCF processing. If the XCF component does not recover, message LDM1135E is also issued.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
XCF terminated due to an unrecoverable abend.
Action:
Review CA-L-Serv's logs for prior messages identifying the reason for the abend.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A message was split into segments for transmission by the named system, but the segments were not received in the proper order.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A message from system sysname was split into segments, but part of the message was lost in the transmission.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
XCF could not send data to the named system due to an internal XCF problem.
Action:
The nature of the problem can be determined by looking up the listed return and reason codes in IBM's z/OS MVS Programming: Sysplex Services Reference Guide under the IXCMSGO macro.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An XCF message acknowledgment received from the named system does not match the information for the message being sent.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An XCF message acknowledgment was received from the named system, but no message was sent to that system.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The XCF component of the file server failed to initialize.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A record was not written to this file because the file is full. The file server will switch to the next file in the group.
Action:
None.
Reason:
The file server detected that a file in a file group is full and submitted a job to perform the archive.
Action:
None.
Reason:
Processing of a file management command has not completed and is preventing the command you issued from executing.
Action:
Review the CA-L-Serv's logs looking for previous error messages for possible abends of the file server. If no abend is found and CA-L-Serv did not take an SVC dump, take a console dump of the CA-L-Serv region including private storage and all system areas.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The file server was unable to switch to a new file in the file group because there are no empty files available.
Action:
Review the output of recent archive jobs looking for errors. You may need to run a manual archive if the automatic archive failed.
Reason:
A SWITCHFILE command was issued but the ddname specified is not part of the file group.
Action:
Use the DISPLAY DATABASE command to list the files belonging to the file group.
See the description of the SWITCHFILE and DISPLAY DATABASE commands.
Reason:
A command specified file group name xx but the file group was not defined to the file server by prior ADDFILE commands.
Action:
Use the DISPLAY command to list the active file groups.
Reason:
The file server detected that a file in a file group was full and has switched to the next available file in the group.
Action:
None.
Reason:
The message lists the active file in a file group.
Action:
None.
Reason:
All files in the file group are full.
Action:
Determine why all files are full. Look for possible problems with automatic archive jobs (whether they ran, whether they ran successfully). If no operational error is found, call CA Support.
Reason:
The XCF Driver has initialized.
Action:
None.
Reason:
The XCF Driver has terminated.
Action:
None.
Reason:
The system does not support XCF or the XCF component is not available.
Action:
Review CA-L-Serv's logs to determine why the XCF component was unable to initialize.
Retain appropriate diagnostic information (SVC dumps, logs) and call CA Support.
Reason:
XCF is busy, but a retry will be attempted.
Action:
If the condition persists, call CA Support.
Reason:
The XCF component of the communications server was unable to send a message due to an XCF problem.
Action:
Look up the return and reason codes for the IXCMSGO macro in the Authorized Assembler Reference manuals relevant to your installation.
If the condition persists, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The XCF component of the communications server failed to issue the IXCQUERY macro.
Action:
Look up the return code and reason code for the IXCQUERY macro in the Authorized Assembler Reference manuals relevant to your installation.
If the condition persists, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
XCF terminated because of a query failure.
Action:
Check the contents of message LDM3953E.
Reason:
XCF attempted to send a message to an XCF member that is no longer part of the sysplex group.
Action:
Review the system log and CA-L-Serv's logs on the target system to determine why the member is no longer active.
Reason:
The SQL server has successfully initialized.
Action:
None.
Reason:
This message is used to echo SQL statements found in the file defined by the LDMSQDEF member of the LDMPARM data set to the CA-L-Serv log.
Action:
None.
Reason:
The SQL Server has terminated as a result of a DETACH SQLSERVER command, a series of fatal errors during SQL execution, or the termination of CA-L-Serv.
Action:
None.
Reason:
The SQL Server processed the command successfully.
Action:
None.
Reason:
An LSQL SELECT statement did not find any rows matching the selection criteria.
Action:
This may be a normal condition.
Reason:
The SQL server abended.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The SQL Server requires the File Server to be active; when this requirement is not met, this message is issued.
Action:
Review CA-L-Serv's logs to determine why the file server is inactive.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The SQL Server or CA-L-Serv was stopped while an SQL statement was executing. The SQL statement may or may not have executed, or it may have been partially executed.
Action:
Review the CA-L-Serv's logs looking for previous error messages and for possible abends of the SQL server.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An internal SQL server error was encountered while processing an SQL statement.
Action:
Review the CA-L-Serv's logs looking for prior error messages and possible abends of the SQL server.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An internal SQL server error was encountered while processing an SQL statement.
Action:
Review the CA-L-Serv's logs looking for prior error messages and possible abends of the SQL server.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The SQL server was unable to acquire the storage required to process an SQL statement.
Action:
You may need to increase the CA-L-Serv region.
If no operational problem is found, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An internal error was encountered while processing an SQL statement.
Action:
Review the CA-L-Serv logs looking for prior error messages and possible abends of the SQL server.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The SQL server was unable to acquire the storage required to process an SQL statement.
Action:
You may need to increase the CA-L-Serv's region.
If no operational problem is found, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An internal error was encountered while processing an SQL statement.
Action:
Review the CA-L-Serv's logs looking for prior error messages and possible abends of the SQL server.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
An internal error was encountered while processing an SQL statement.
Action:
Review the CA-L-Serv's logs looking for prior error messages and possible abends of the SQL server.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
Internal error while processing an SQL statement.
Action:
Review the CA-L-Serv logs looking for prior error messages and possible abends of the SQL server.
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
This message is issued when the LSQL command is entered without any accompanying arguments.
Action:
For additional information concerning the LSQL command, see the reference topics.
Reason:
The SQL server has scanned the maximum number of records defined by the SCANLIMIT parameter of the ATTACH SQLSERVER command.
Action:
If necessary, increase the SCANLIMIT value.
Reason:
For tables defined with leading NULL bytes, a new column could not be added because there was not enough room in the leading SQL NULL bytes to contain the new column's NULL bit.
Action:
For additional information, review the SQL statements reference topics.
Reason:
An SQL statement could not update or delete rows for a table because there were other operations in progress against the same table (for this same statement). This can occur when the SQL statement references the same table more than once (such as the main table and the table in a subquery or join operation). This type of conflict can occur for two different tables if the two tables are contained in the same VSAM file. This restriction prevents VSAM Control Interval lockouts.
Action:
Reformulate the SQL statement to avoid this deadlock. Usually, this requires using two different SQL statements.
Reason:
These messages acknowledge the various types of updates performed against an SQL table.
Action:
None.
Reason:
These messages acknowledge the various types of updates performed against an SQL table.
Action:
None.
Reason:
These messages acknowledge the various types of updates performed against an SQL table.
Action:
None.
Reason:
These messages acknowledge the various types of updates performed against an SQL table.
Action:
None.
Reason:
These messages acknowledge the various types of updates performed against an SQL table.
Action:
None.
Reason:
These messages acknowledge the various types of updates performed against an SQL table.
Action:
None.
Reason:
The SQL server was unable to access the column referenced by COL# or the column is missing.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The SQL server was unable to access the column referenced by xxxx because the corresponding table specifies an invalid data type for the column.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
In the TABLE data dictionary table, the row that describes a relational table is missing or damaged. The SQL server marks that table as damaged so that it is no longer accessible.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
This message always follows other error messages that indicate reporting a problem with the dictionary structure for the table. This message signals that access to the table is no longer allowed.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
This message is issued during SQL initialization to signal that the identified table is now ready for access.
Action:
None.
Reason:
The table id xxxx is invalid. The SQL server will fail requests attempting to access the table.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
The number of rows read in a table does not match the number of rows specified for that table. (The ROW COUNT column of the TABLE data dictionary table indicates how many rows are specified for that table.) The SQL server automatically updates the ROW COUNT column to reflect the number of rows read in.
Action:
This message usually appears after other messages report that certain data rows were discarded. If this is not the case, retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
This message is issued when the SQL server has completed initialization and is ready to process SQL queries.
Action:
None.
Reason:
The SQL server is unable to initialize and terminates.
Action:
Review the CA-L-Serv logs looking for previous error messages to determine why the SQL server is unable to initialize.
Gather the appropriate diagnostic information, and call CA Support.
Reason:
The SQL server encountered an error and did not initialize successfully.
Action:
Gather the appropriate diagnostic information, and call CA Support.
Reason:
The SQL server abended and did not initialize successfully.
Action:
Gather the appropriate diagnostic information, and call CA Support.
Reason:
The SQL server encountered an error and did not initialize successfully.
Action:
Gather the appropriate diagnostic information, and call CA Support.
Reason:
A CREATE TABLE statement does not indicate the data set against which the table is to be mapped.
Action:
See the description of the CREATE TABLE statement.
Reason:
The CREATE TABLE statement for table xxxx is in error.
Action:
See the description of the CREATE TABLE statement.
Reason:
Parameters in the DATABASE clause of the CREATE TABLE statement are invalid. This message is followed by additional messages indicating the problem.
Action:
See the description of the CREATE TABLE statement.
Reason:
The CREATE statement and the offset value specified when the VSAM data set was defined are inconsistent: the relational table's primary key must include the VSAM file key.
Action:
See the description of the CREATE TABLE statement.
Reason:
The length specified for a primary key exceeds the maximum length of 100 bytes.
Action:
See the description of the CREATE TABLE statement.
Reason:
The length of a primary key cannot exceed the length specified when the VSAM data set was created.
Action:
See the description of the CREATE TABLE statement.
Reason:
The total row size nn1 adds up to more than the maximum record length specified when the VSAM data set was created.
Action:
See the description of the CREATE TABLE statement.
Reason:
This message is issued when a VSAM record does not match its corresponding SQL table. This can occur when a table is associated with the wrong file, or when a CREATE TABLE statement was incorrectly formulated.
Action:
Review the CREATE TABLE statement.
Reason:
This message is issued when a VSAM record does not match its corresponding SQL table. This can occur when a table is associated with the wrong file, or when a CREATE TABLE statement was incorrectly formulated.
Action:
Review the CREATE TABLE statement.
Reason:
The SQL Server cannot open the VSAM file filename. The most common cause of this is the absence of a file definition for the file, as established with the ADDFILE command.
Action:
Review the file server log to determine possible errors concerning the file. Issue a DISPLAY DATABASE command to list the current status of the file.
Reason:
This message is issued if any statement other than a CREATE TABLE or DROP TABLE appears in the LDMSQDEF file at startup.
Action:
Remove improper statements from LDMSQDEF file.
Reason:
The SQL server encountered an internal logic error.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
Reason:
A statement could not be executed because the requestor is not authorized at the necessary level.
Action:
If you need more authorization, contact your security administrator.
Reason:
This message is issued by the LSQL command after the command failed to verify the file underlying an SQL table. The code is the CA-L-Serv return code.
Action:
Retain the appropriate diagnostic information (abend dumps, SVC dumps, system logs, and supporting data) and call CA Support.
LDM4081I Statement Count DB Activity Count LDM4082I statement nn1 type nn2 LDM4083I LDM4084I Last Row Table Row (Key) Time LDM4090I Selected name name time LDM4091I Fetched name name time LDM4092I Inserted name name time LDM4093I Updated name name time LDM4094I Deleted name name time LDM4083I LDM4086I Compilations: nn Avg Service Time: nn LDM4087I Execution: nn nn LDM4083I LDM4088I Errors: Compilation Execution Logic LDM4089I nn nn nn
Reason:
These messages display information about the SQL server's SQL activities, as follows:
Action:
None.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message and reference the information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message and reference additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Use SPF EDIT in HEX mode to find the character then respecify the statement.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message.
Reason:
The statement contains more than the maximum level of parentheses allowed.
Action:
Refer to additional information concerning the statement's syntax.
Reason:
The SQL server found an unpaired apostrophe.
Action:
Refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
A column name or table name specification is invalid. Each table or column name level must be no more than 18 characters long.
Action:
Refer to additional information concerning the statement's syntax and specifications.
Reason:
Word appears in the wrong place or does not belong in the SQL statement.
Action:
Refer to additional information concerning the statement's syntax and specifications.
Reason:
The table name or column name specified in the statement exceeds the maximum length of eighteen characters.
Action:
Refer to additional information concerning the syntax of SQL statements.
Reason:
The host variable name specified in the statement exceeds the maximum length of thirty-two characters.
Action:
Refer to additional information concerning naming conventions for host variables.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
You must use the syntax X'nnnn' for the hexadecimal string, where nnnn contains hexadecimal digits 0-9 or A-F.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
A column name was specified in the tablename.columnname format, but tablename is not otherwise defined as a table within the statement.
Action:
To determine why the table was not defined, see the CA-L-Serv's logs.
Reason:
The number of base tables specified exceeds the maximum supported. The maximum number of tables that can be specified is 8.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The statement refers to column xxxx as the primary key, but the column has not yet been defined.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The number of subqueries specified exceeds the maximum supported. The maximum number of subqueries that can be specified is 7. (The number of subqueries allowed can be less than 7 if the statement contains joins.)
Action:
Refer to additional information concerning the statement's syntax.
Reason:
In a SELECT statement containing a GROUP BY clause, a column name was requested in the selection list but not in the GROUP BY column list. Only values in the GROUP BY column list can be referenced.
Action:
Review the information in the message and refer to additional information concerning the utilization of the GROUP BY clause.
Reason:
A column was mentioned more than once in the GROUP BY clause.
Action:
Review the information in the message to determine the error and refer to additional information concerning the syntax of the GROUP BY clause.
Reason:
The GROUP BY clause was not followed by at least one grouping column name.
Action:
Refer to additional information concerning the utilization of the GROUP BY clause.
Reason:
A HAVING clause was encountered on a SELECT statement but there was no corresponding GROUP BY clause. A GROUP BY clause must follow the HAVING clause on a SELECT statement.
Action:
Refer to additional information concerning the utilization of the GROUP BY and the HAVING clause.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL statement exceeds the maximum size which can be compiled.
Action:
Refer to additional information concerning SQL server restrictions.
Reason:
The SQL server detected a syntax error. In a SELECT statement selection list, you cannot specify one or more column names (perhaps within a function) along with one or more aggregate value functions such as COUNT, MIN, or SUM.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax and usage rules.
Reason:
The SQL server detected a syntax error.
Action:
Provide a character value at the indicated point.
Reason:
The matching pattern specified with a LIKE predicate is invalid. This message can occur when you specify something like the following:
. . . LIKE 'abcX' ESCAPE 'X'
An error occurred because there were no additional characters after the escape character 'X' in the matching pattern.
Action:
Refer to additional information concerning the LIKE predicate.
Reason:
There are occasions in the SQL syntax where only a single 1-byte character string can be specified, such as the following:
LIKE '...' ESCAPE 'XY'
With ESCAPE, you can specify only a single character.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
An argument for the identified function is incorrectly specified.
Action:
Review the information in the message and refer to additional information about specifying the function.
Reason:
The function being enacted requires an integer argument but received some other value type.
Action:
Review the information in the message and refer to additional information concerning the function and SQL value types.
Reason:
The function being enacted requires a character string argument but received some other value type.
Action:
Review the information in the message and refer to additional information concerning the function and SQL value types.
Reason:
Table names must contain from 1 to 18 alphanumeric characters, starting with an alphabetic character. Underscore characters can also be used in table names.
Action:
Refer to additional information concerning SQL syntax rules.
Reason:
Column names must contain from 1 to 18 alphanumeric characters, starting with an alphabetic character. Underscore characters can also be used in column names.
Action:
Review the information in the message and refer to additional information concerning SQL syntax rules.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message and refer to additional information concerning the statement's syntax.
Reason:
You cannot specify PRIMARY KEY within a column definition and after all columns are defined. Choose one way or the other.
Action:
Refer to additional information concerning PRIMARY KEY specification.
Reason:
The SQL server detected a syntax error.
Action:
Review the information contained in the message and refer to additional information concerning the statement's syntax.
Reason:
The DEFAULT clause does not introduce a value.
Action:
Review the information contained in the message and refer to additional information concerning the DEFAULT clause.
Reason:
The value specified in the DEFAULT clause is invalid.
Action:
Refer to additional information concerning the DEFAULT clause.
Reason:
The value nn exceeds the storage capacity defined for a column. If the column's data type is INTEGER, the maximum value is 2147483647. If the data type is SMALLINT, the maximum value is 32767.
Action:
Refer to additional information concerning maximum values supported for each data type.
Reason:
The SQL server detected a syntax error.
Action:
Use the syntax CHAR(n) or HEX(n), where n is a numeric string.
Review the information contained in the message and refer to additional information concerning the DEFAULT clause.
Reason:
The SQL server encountered duplicate column names.
Action:
Review the SQL log to identify the process leading up to the duplicate definition.
Reason:
The statement requires a VALUES clause.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
A value was specified that was not of a valid format for the function being enacted.
Action:
Refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a discrepancy between the number of columns in the table and the values specified in the statement.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected a syntax error.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The SQL server detected an invalid or incomplete predicate.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The feature is not supported by CA-L-Serv SQL.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
A WHERE clause is required for this statement.
Action:
Review the information in the message and refer to additional information concerning the statement's syntax.
Reason:
The WHERE clause contains an unknown expression.
Action:
Review the information in the message and refer to additional information concerning the syntax of WHERE clauses.
Reason:
The search criteria contain more than three levels of parentheses.
Action:
Refer to additional information concerning the specification of search criteria.
Reason:
The WHERE clause does not contain search criteria or the search criteria specified are invalid.
Action:
Refer to additional information concerning the specification of search criteria.
Reason:
The SQL server detected a syntax error.
Action:
Review the text of the message and refer to additional information concerning the statement's syntax.
Reason:
Because of the imprecision of floating point numbers, columns of data type FLOAT, DOUBLE PRECISION, and REAL cannot be primary keys.
Action:
Refer to additional information concerning the specification of primary keys.
Reason:
The host variable name specified in the statement is invalid.
Action:
Refer to additional information concerning the specification of host variables.
Reason:
A FROM clause specified after a SELECT or DELETE verb is missing or the clause is invalid.
Action:
Review the text of the message and refer to additional information concerning the specification of FROM clauses.
Reason:
The SQL server detected a logic error in an SQL statement. The numbers of host variables and column values are inconsistent.
Action:
Correct the inconsistency.
Reason:
The SQL server detected a logic error in an SQL statement. The numbers of host variables and columns are inconsistent.
Action:
Correct the inconsistency.
Reason:
The SQL server detected a syntax error in a DECLARE statement.
Action:
Refer to additional information concerning the DECLARE statement.
Reason:
The SQL server detected an invalid cursor name.
Action:
Refer to additional information concerning the specification of cursors.
Reason:
The SQL server detected that an SELECT clause is missing.
Action:
Refer to additional information concerning usage rules for SELECT clauses.
Reason:
The SQL server detected a syntax error
Action:
Review the text of the message and refer to additional information concerning statement's syntax.
Reason:
An IN predicate specified a numeric expression.
Action:
Review the text of the message and refer to additional information concerning statement's syntax.
Reason:
The IN predicate does not specify an argument list or the argument list specified is invalid.
Action:
Review the text of the message and refer to additional information concerning statement's syntax.
Reason:
The SQL server detected that the maximum number of columns for a table was exceeded.
Action:
Review the text of the message additional information concerning table definitions.
Reason:
The SQL server detected that the maximum size of a column for a table was exceeded.
Action:
Review the text of the message and refer to additional information concerning column definitions.
Reason:
The column definition is not consistent with the null value specified.
Action:
Review the text of the message and refer to additional information concerning data types and column definitions.
Reason:
The primary key definition exceeds the maximum of 100 bytes.
Action:
Refer to additional information concerning primary key definitions.
Reason:
The SQL server detected a syntax error in an ALTER TABLE statement.
Action:
Review the text of the message and refer to additional information concerning the syntax of the ALTER TABLE statement.
Reason:
The syntax of the DATABASE clause is invalid.
Action:
Review the text of the message and refer to additional information concerning the DATABASE clause.
Reason:
The host variable refers to another column.
Action:
Review the text of the message and refer to additional information concerning host variables.
Reason:
The DECIMAL(nnn) data type was incorrectly formulated on the CREATE TABLE or ALTER TABLE statement.
Action:
Refer to additional information concerning data types and column definitions.
Reason:
The ORDER BY clause was incorrectly formulated.
Action:
Refer to additional information concerning the ORDER BY clause.
Reason:
The ORDER BY clause allows the specification of a relative selection list number (value). For example, 4 would identify the 4th item in the selection list. This message is issued when the value specified is zero or negative, or is larger than the number of items in the selection list.
Action:
Review the text of the message and refer to additional information concerning the ORDER BY clause.
Reason:
The maximum number (255) of ORDER BY items has been exceeded.
Action:
Refer to additional information concerning restrictions with the ORDER BY clause.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|