|
|
|
The following messages are generated by the CAISDI/soap, CAISDI/med and CAISDI/els components.
Note: For customers with CA Service Desk ITIL configurations, the term “requests” in the following messages refers to “incidents,” and the term “assets” refers to “configuration items.”
Reason:
This indicates the CAISDI/soap Client address space has started up.
Displays the current date in Mmm DD YYYY format.
Action:
No action is required.
Reason:
This is the initialization message from the CAISDI/soap Client.
Action:
No action is required.
Reason:
This message is issued in response to a shutdown or LIST command. (Messages CASD003I-CASD006I are a group.) A new UNIX System Services process has been created to perform this function.
Displays the UNIX System Services process ID.
Action:
No action is required.
Reason:
This message is issued in response to a shutdown or LIST command. (Messages CASD003I-CASD006I are a group.)
Displays the number of transactions processed.
Action:
No action is required.
Reason:
This message is issued in response to a shutdown or LIST command. (Messages CASD003I-CASD006I are a group.)
Displays the number of transactions in error.
Action:
No action is required.
Reason:
This message is issued in response to a shutdown or LIST command. (Messages CASD003I-CASD006I are a group.)
Displays the number of CPU seconds attributable to user transactions.
Displays the number of CPU seconds attributable to system activities.
Action:
No action is required.
Reason:
The POSIX environment is not on.
Action:
UNIX System Services must be started with POSIX set to ON for the CAISDI/soap address space to execute.
Reason:
Unable to set the UID to zero in CAISDI/soap Client address space.
Action:
Make sure the user ID associated with the CAISDI/soap address space either has UID 0 or is a superuser-level ID.
Reason:
An error occurred while parsing the configuration data.
Action:
Check the output for more specific messages.
Reason:
Unable to obtain storage for CAICCI communications.
Action:
Increase the REGION size for the CAISDI/soap Client address space.
Reason:
In attempting to process a command, CAISDI/soap attempted to initiate a UNIX System Services thread. An unanticipated failure was encountered when the function pthread_create() was executed.
Action:
Check the JOBLOG for messages.
Reason:
In attempting to set up a background process, CAISDI/soap attempted to initiate a UNIX System Services thread. An unanticipated failure was encountered when the function pthread_create() was executed.
Action:
Check the JOBLOG for messages.
Reason:
The CAISDI/soap Client has been requested to terminate (either by command or due to internal error).
Displays the CAICCI return code that was detected.
Action:
If not requested to shut down, check for other error messages and see CAISDI/soap API Return Codes in the chapter "Codes."
Reason:
Error occurred when trying to open the configuration input file.
Identifies the specific file being read. If an HFS file was being used for input, it will be the HFS path.
Gives a more specific reason for the failure.
Action:
Check for other error messages.
Reason:
Error occurred parsing the configuration input. A variable was to be continued on the next line, but the continuation was not found.
Action:
Correct the variable in the configuration file.
Reason:
Error occurred parsing the configuration input. The input line exceeds the maximum length allowed of 256 bytes.
Action:
Correct the configuration file.
Reason:
Both SSL_SAF and SSL_HFS cannot be specified.
Action:
Correct the configuration file to specify either SSL_SAF or SSL_HFS.
Reason:
The value specified in the configuration file for TIMEOUT_IO was not within range.
Action:
Specify a value between 1 and 3600.
Reason:
The value specified in the configuration file for TIMEOUT_CONNECT was not within range.
Action:
Specify a value between 1 and 3600.
Reason:
Initialization has successfully completed.
Action:
None.
Reason:
The pthread_mutex_init() failed with error errno (decimal) for output file file.
Action:
Initialization terminates.
Reason:
The Environmental Variable CCI_APPLNAME specifies a string that is more than 20 characters.
Action:
Change CCI_APPLNAME to be less than 20 characters. See configuration documentation.
Reason:
The support routine module indicated a fatal error was encountered. Currently module is one of CAS0SCR, CAS0SCS, CAS0SCI or CAS0SCT.
Action:
The server will terminate.
Reason:
The CCI initialization routine CAS0SCI returned (decimal) return code rc, (hexadecimal) reason code reason and (hexadecimal) CCI return code CCI_RC.
Action:
The server will terminate.
Reason:
The pthread_att_init() function returned (decimal) error errno).
Action:
The server will terminate.
Reason:
The command entered had invalid syntax.
Action:
Correct the command and re-enter.
Reason:
There was no value specified for the specified environmental variable.
Action:
Correct the environmental variable and re-start the server.
Reason:
The level specified for the environmental variable SD_WSDL_LEVEL in not valid.
Action:
Correct the environmental variable and re-start the server.
Reason:
Error error was returned from iconv_open for the specified codepages.
Action:
The server terminates.
Reason:
The malloc() function failed for the specified type and size.
Action:
The server terminates.
Reason:
The length of the value for SD_URL, including the null terminator, exceeds the stated maximum.
Action:
Correct the environmental variable and re-start the server.
Reason:
The URL specified indicates a WSDL level that is not supported.
Action:
Correct the environmental variable and re-start the server.
Reason:
An invalid value was specified for the specified environmental variable.
Action:
Correct the environmental variable and re-start the server.
Reason:
Both SSL_HFS and SSL_SAF were specified. May only specify one of them.
Action:
Correct the environmental variables and re-start the server.
Reason:
The specified environmental variable only takes, YES, Y, NO or N for a value.
Action:
Correct the environmental variables and re-start the server.
Reason:
The number of transactions processed and the number in error are displayed.
Action:
None.
Reason:
The CCI termination routine CAS0SCT returned (decimal) return code rc, (hexadecimal) reason code reason and (hexadecimal) CCI return code CCI_RC.
Action:
The server continues with termination.
Reason:
At initialization any stale CAICCI queue is deleted.
Displays the return code from the internal CAICCI queue cleanup processing.
Action:
No action is required.
Reason:
A command was entered from the system console by an operator.
Displays the command given to the CAISDI/soap Client address space.
Action:
No action is required.
Reason:
This initialization message is issued from the CAISDI/soap Client when it starts up.
Displays the name under which the CAISDI/soap Client address space is executing.
Action:
No action is required.
Reason:
The operator command DEBUG, TRACE, CCI_DUMP_BUFFER or TRACE_XML_PARSE was entered. This message indicates the state after processing the command.
flag is “DEBUG”, “TRACE”, “CCI_DUMP_BUFFER” or “TRACE_XML_PARSE”
state is “enabled” or “disabled”.
Action:
None.
Reason:
A command was received from the system console, but it is not recognized.
Displays the image of the command that was received.
Action:
Correct the spelling and repeat the command.
Reason:
The command process is terminating in response to a stop command.
Action:
No action is required.
Reason:
An TIMEOUT_IO command was specified with no value.
Action:
Specify TIMEOUT_IO=nnnn.
Reason:
The value specified on the TIMEOUT_IO command was not within range.
Action:
Specify TIMEOUT_IO=nnnn where nnnn is between 0 and 3600 inclusive.
Reason:
A valid TIMEOUT_IO command was entered.
Action:
The TIMEOUT_IO value in seconds is set to nnnn.
Reason:
A TIMEOUT_CONNECT command was specified with no value.
Action:
Specify TIMEOUT_CONNECT=nnnn.
Reason:
The value specified on the TIMEOUT_CONNECT command was not within range.
Action:
Specify TIMEOUT_CONNECT=nnnn where nnnn is between 0 and 3600 inclusive.
Reason:
A valid TIMEOUT_CONNECT command was entered.
Action:
The TIMEOUT_CONNECT value in seconds is set to nnnn.
Reason:
Unable to set the UID to zero in Script process.
Action:
Make sure the user ID either has UID 0 or is a superuser.
Reason:
An unanticipated error occurred during the creation of the internal message queue for the CAISDI/soap Client address space. The IPC_CREAT failed.
Action:
Collect the messages and contact CA Support.
Reason:
CAISDI/soap was attempting to acquire storage for internal buffers, but not enough storage was available. The IPC_CREAT failed.
Action:
Increase the REGION space and try starting the CAISDI/soap Client address space again. If the problem persists, collect the messages and contact CA Support.
Reason:
This is an initialization message from the CAISDI/soap Script process.
Displays the IPC message ID.
Action:
No action is required.
Reason:
Script process is terminating.
Displays the number of requests that have been processed.
Action:
No action is required.
Reason:
An internal CAISDI/soap process has timed out.
Displays the process ID of that process.
Action:
No action is required.
Reason:
The operator command DEBUG was entered toggling the debug state.
Indicates the current debug setting and can be either “enabled” or “disabled.”
Action:
No action is required.
Reason:
CAISDI/soap Client address space was attempting to send a piped request when an unanticipated error from the pipe() request was detected.
Displays a more detailed reason for the problem.
Action:
No action is required.
Reason:
The CAISDI/soap Client address space encountered an unexpected error using the fopen() function to open a file. An attempt to open the DD named ddname is made first, and then the file fileid is tried. The errmsg text is passed back from the fopen() function.
Action:
Ensure the file and ddname exists or that the permissions allow access.
Reason:
The CAISDI/soap Client address space encountered an unexpected error using the fopen() function to open a file for output.
Displays the ddname or, if an HFS file is being opened, the HFS path.
Displays the reason for the failure returned from the fopen() function.
Action:
Ensure the ddname exists or that the permissions allow access.
Reason:
A connect() request failed to a remote server.
Displays either “1” for blocking mode or “0” for nonblocking mode.
Identifies the target for the TCP/IP connection.
Displays the reason for the error.
Action:
Make sure the remote address and port are correct. Check TCP/IP logs.
Reason:
A connect() request failed to connect with a remote server.
Identifies the target for the TCP/IP connection.
Displays the reason for the error.
Action:
Make sure the remote address and port are correct. Check TCP/IP logs.
Reason:
Unable to obtain storage for local block describing SSL parameters.
Action:
Check the job log. If no message appear indicating a problem with authorization, increase the REGION size and try starting the CAISDI/soap Client address space.
Reason:
The configuration file indicated SSL_HFS, which requires SSL_STASH to be specified.
Action:
Correct the configuration file by adding the SSL_STASH control parameter.
Reason:
An https request was received but SSL was not specified in the configuration file.
Action:
Correct the configuration file by adding the SSL_SAF startup parameter.
Reason:
The gsk_attribute_set_buffer() failed opening the GSK_KEYRING_FILE.
Displays the return code from the SSL API.
Action:
Correct the SAF or HFS definitions.
Reason:
The call to the gsk_attribute_set_enum() function failed.
Displays the return code from the SSL API.
Action:
Record the return code rc and contact CA Support.
Reason:
The call to the gsk_attribute_set_buffer() function failed using the GSK_KEYRING_FILE.
Is either SAF or HFS.
Displays the return code from the SSL API.
Action:
Correct the SAF or HFS definitions.
Reason:
The call to the gsk_attribute_set_buffer() function failed for GSK_KEYRING_STASH_FILE.
Displays the return code from the SSL API.
Action:
Correct the HFS definitions.
Reason:
The call to the gsk_environment_init() function failed.
Displays the return code from the SSL API.
Action:
Verify that SSL has been properly configured. If rc is 416, the user ID associated with CAISDI/soap Client address space does not have sufficient authority. The user ID must have read access to the IRR.DIGTCERT.LISTRING and IRR.DIGTCERT.LIST resources.
Reason:
In attempting to start a secured connection, the call to the gsk_secure_socket_open() function unexpectedly failed.
Displays the return code from the SSL API.
Action:
Collect documentation and contact CA Support.
Reason:
The call to the gsk_attribute_set_numeric_value() function failed for GSK_FD.
Displays the return code from the SSL API.
Action:
Collect documentation and contact CA Support.
Reason:
The call to the gsk_attribute_set_numeric_enum() function failed for CLIENT.
Displays the return code from the SSL API.
Action:
Collect documentation and contact CA Support.
Reason:
The call to the gsk_attribute_set_callback() function failed for GSK_IO_CALLBACK.
Displays the return code from the SSL API.
Action:
Collect documentation and contact CA Support.
Reason:
The call to the gsk_secure_socket_init() function failed.
Displays the return code from the SSL API.
Action:
Make sure your SSL certificate is on file and that it has not been corrupted. Check the certificate and TCP/IP connection.
Reason:
The call to the gsk_environment_close() function failed.
Displays the return code from the SSL API.
Action:
Collect documentation and contact CA Support.
Reason:
The call to the gsk_environment_close() function succeeded.
Action:
No action is required.
Reason:
Unable to obtain storage for the local block describing TCP parameters.
Action:
Check the job log.
Reason:
Unable to obtain storage for the TCP receives.
Action:
Check the job log.
Reason:
Unable to open UTF-8 translation to IBM-1047.
Action:
Check the job log.
Reason:
Unable to obtain storage for the local control block for HTTP.
Action:
Check the job log.
Reason:
Unable to obtain storage for the HTTP buffer.
Action:
Check the job log.
Reason:
Unable to obtain storage for the local control block for XML processing.
Action:
Check the job log.
Reason:
The SSL API gsk_attribute_set_buffer returned error code retcode.
Action:
The request is not processed.
Reason:
The socket received a SIGPIPE interrupt.
Action:
The request is not processed.
Reason:
The CAISDI/med address space has been started.
Action:
No action is required.
Reason:
The CAISDI/med address space is active and ready to process events and requests.
Action:
No action is required.
Reason:
The CAISDI/med address space has started the initialization process.
Action:
No action is required.
Reason:
The CAISDI/med has encountered an unexpected failure attempting to LOAD the interface routine to the SOAP Client.
Action:
Verify that the CAISDI/soap Client Service module, CAS0PCSI, is either in the system link list, or is in a STEPLIB that is available to the CAISDI/med address space.
Reason:
The CAISDI/med address space has detected that an existing copy of the CAISDI/med address space is already executing in the system.
Action:
The CAISDI/med address space terminates.
Reason:
The CAISDI/med address space has detected an unexpected error during initialization.
Action:
Refer to previous initialization failure messages that detail the nature of the problem.
Reason:
The CAISDI/med address space has successfully completed initialization.
Action:
No action is required.
Reason:
An unexpected service routine failure has been encountered. The service routine, requested function, return code, and reason code are displayed.
Action:
Collect all relevant documentation and contact CA Support.
Reason:
OPEN processing failed for the initialization data set specified on the MEDPARMS DD in the CASDIMED JCL startup PROC.
Action:
Check the MEDPARMS DD in the CASDIMED JCL startup PROC. Make sure that the data set and member (if applicable) specified are correct and accessible.
Reason:
The statement image from the CAISDI/med initialization data set is logged to SYSLOG. Each line of the initialization data set is echoed on a CASD249I message.
Action:
No action is required.
Reason:
A portion of the normalized statement image from the initialization data set is logged to SYSLOG when INIT DEBUGMSG=YES. This message is for debugging purposes only.
Action:
No action is required.
Reason:
At least one SERVER statement must be defined.
Action:
Make sure that at least one SERVER statement is defined in the initialization data set.
Reason:
At least one PRODUCT statement must be defined.
Action:
Make sure that at least one PRODUCT statement is defined in the initialization data set.
Reason:
The indicated SERVER (server) specified on the indicated PRODUCT statement (product) is not valid.
Action:
Correct the indicated PRODUCT statement in the initialization data set so that a valid SERVER name is specified. The PRODUCT statement must specify a SERVER that has been defined on a SERVER statement in the initialization data set.
Reason:
The statement in the initialization data set is invalid.
Action:
Correct the statement in the initialization data set. Valid statements are INIT, SERVER, PRODUCT, EVENT, and EXCLUDE.
Reason:
The statement provided in the initialization data set is not recognized.
Action:
Correct the statement in the initialization data set. Recognized statements are INIT, SERVER, PRODUCT, EVENT, and EXCLUDE.
Reason:
The statement provided in the initialization data set requires at least one operand, but no operands were specified.
Action:
Correct the statement in the initialization data set to include the required operands.
Reason:
The SERVER statement specifies the same name as a previously defined SERVER statement.
Action:
Delete the duplicate SERVER statement or change the name on the SERVER statement so that it does not specify the same name as a previously defined SERVER statement. SERVER statements are specified in the initialization data set.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The indicated CAISDI/med task has encountered an error attempting to execute the named web service at the named server. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided. The return code generated by web server, src, is provided if available. The fault string, error code, and error message, if any, returned by the CA Service Desk web server are displayed.
Action:
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." For an explanation of the src value, fault string, error code, and error message returned by the web server, see the CA Service Desk WEB Services User Guide.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The indicated CAISDI/med task has been timed out by the CA Service Desk server.
Action:
The named CAISDI/med task will log into the CA Service Desk server and retry the operation.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes."
For an explanation of the src value, fault string, error code, and error message returned by the web server, see the CA Service Desk WEB Services User Guide.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The CAISDI/soap Client address space is required to communicate with a CA Service Desk server.
Action:
The request in progress is retried.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." Make sure that the CAISDI/soap Client address space is started and is accessible to the local system through CAICCI.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided. The return code generated by web server, src, is provided if available. The fault string, error code, and error message, if any, returned by the CA Service Desk web server are displayed.
Action:
The request in progress is cancelled.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." For an explanation of the src value, fault string, error code, and error message returned by the web server, see the CA Service Desk Web Services User Guide.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The CA Service Desk server has detected a delay in processing a request. This could be due to network traffic or server request activity. The indicated CAISDI/med task has encountered an error attempting to execute the named web service at the named server. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided. The return code generated by web server, src, is provided if available. The fault string, error code, and error message, if any, returned by the CA Service Desk web server are displayed.
Action:
The CAISDI/med task will terminate its current session with CA Service Desk, establish a new session, and retry the request.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." For an explanation of the src value, fault string, error code, and error message returned by the web server, see the CA Service Desk Web Services User Guide.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
CAICCI is required to communicate with the CAISDI/soap Client address space.
Action:
The request in progress is retried.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." Make sure that the CAICCI address space is started and is accessible.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The indicated CAISDI/med task has encountered an error attempting to communicate to the named web service at the named server. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided. The return code generated by web server, src, is provided if available. The fault string, error code, and error message, if any, returned by the CA Service Desk web server are displayed.
Action:
The CAISDI/med task will terminate its current session with CA Service Desk, establish a new session, and retry the current request.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." For an explanation of the src value, fault string, error code, and error message returned by the web server, see the CA Service Desk Web Services User Guide. Make sure that the CA Service Desk server at the named URL address is active and is accessible to the CAISDI/soap Client address space.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The indicated CAISDI/med task has encountered an error attempting to make a request to the CAISDI/soap Client address space. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided.
Action:
The CAISDI/med task will automatically be stopped.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." Verify that the correct levels of CAISDI/med and CAISDI/soap are installed.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The CAISDI/soap Client address space has indicated a resource shortage while processing a request from the CAISDI/med task. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided.
Action:
The CAISDI/med task will terminate its current session with CA Service Desk, establish a new session, and retry the current request.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes."
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The CAISDI/soap Client address space has detected a structural or syntactical error in the URL address. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided.
Action:
The CAISDI/med task will automatically be stopped.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." Correct the URL operand specification on the SERVER initialization statement for the named CAISDI/med task in the MEDPARMS data set, then stop and restart the CAISDI/med address space.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The CAISDI/soap Client address space has encountered an error attempting to communicate with a CA Service Desk server. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided.
Action:
The CAISDI/med task will terminate its current session with CA Service Desk, establish a new session, and retry the current request.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." Refer to any messages issued by the CAISDI/soap Client address space regarding network errors.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The indicated CAISDI/med task has encountered a receive type error attempting to make a request to the CA Service Desk server through a CAISDI/soap Client address space.
Action:
The request failed.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The indicated CAISDI/med task has encountered an error attempting to make a request to the CAISDI/soap Client address space. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided.
Action:
The current request is cancelled.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." Verify that the correct levels of CAISDI/med and CAISDI/soap are installed.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
CAICCI has indicated that the CAICCI HOSTNAME specification is not valid.
Action:
The CAISDI/med task will automatically be stopped.
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." Correct the HOSTNAME operand specification on the SERVER initialization statement for the named CAISDI/med task in the MEDPARMS data set, then stop and restart the CAISDI/med address space.
Where sss is API, CCI, UNK, or WS. WS stands for Web Server and refers to the return code, reason code, set by the SOAP Server.
Reason:
The indicated CAISDI/med task has encountered an error when attempting to login to the CA Service Desk server through a CAISDI/soap Client address space. The WEB server has refused the connection. The return code, rc, and detailed return code, drc, from the CAISDI/soap Client API call are provided.
Action:
For an explanation of the #SOAP rc and drc values, see CAISDI/soap API Return Codes in the chapter "Codes." Verify that the correct levels of CAISDI/med and CAISDI/soap are installed.
Reason:
The indicated CAISDI/med task has successfully generated a request ticket with a CA Service Desk server at the named URL address. The session ID, new request handle, and new request number are displayed as well.
Action:
No action is required.
Reason:
The indicated CAISDI/med task has successfully logged in to a CA Service Desk server at the named URL address. The named session ID was returned by the server.
Action:
No action is required.
Reason:
The indicated CAISDI/med task has successfully logged out from a CA Service Desk server at the named URL address. The named session ID was previously returned by the server.
Action:
No action is required.
Reason:
CAISDI/med detected that a requested CA Service Desk template name is not predefined.
Action:
The CAISDI/med task will ignore the CA Service Desk template name specification when opening the current request ticket. AFFECTED_END_USER, REPORTED_BY, ASSIGNEE, and PRIORITY values must be present, or they will take default values.
If CA Service Desk templates are to be used to open request tickets, they must be predefined on the CA Service Desk server to which the request tickets are directed.
Reason:
CAISDI/med detected that a requested CA Service Desk AFFECTED_END_USER contact name is not predefined.
Action:
The CAISDI/med task will ignore the CA Service Desk contact name specification when opening the current request ticket. A contact name of System_SD_User will be used by default.
The AFFECTED_END_USER contact name specified must be predefined on the CA Service Desk server to which the request tickets are directed.
Reason:
CAISDI/med detected that a requested CA Service Desk priority name is not predefined.
Action:
The CAISDI/med task will ignore the CA Service Desk priority name specification when opening the current request ticket, unless a TEMPLATE name has not been specified on the associated PRODUCT statement, in which case, a priority name of NONE will be used by default.
The priority name specified must be predefined on the CA Service Desk server to which the request tickets are directed.
Reason:
The CAISDI/med detected that a requested CA Service Desk REPORTED_BY contact name is not predefined.
Action:
The CAISDI/med task will ignore the CA Service Desk REPORTED_BY contact name specification when opening the current request ticket unless a TEMPLATE name has not been specified on the associated PRODUCT statement, in which case a contact name of System_SD_User will be used by default.
The REPORTED_BY contact name specified must be predefined on the CA Service Desk server to which the request tickets are directed.
Reason:
CAISDI/med detected that a requested CA Service Desk ASSIGNEE contact name is not predefined.
Action:
The CAISDI/med task will ignore the CA Service Desk ASSIGNEE contact name specification when opening the current request ticket. No default ASSIGNEE contact name is used. If a TEMPLATE name is specified on the associated PRODUCT statement, and that CA Service Desk template has an ASSIGNEE contact name defined, then the ASSIGNEE contact name on the template will be used on the current request ticket.
The ASSIGNEE contact name specified must be predefined on the CA Service Desk server to which the request tickets are directed.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an internal error while parsing a statement or a command.
Action:
Collect relevant documentation and contact CA Support.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Correct the statement or reenter the command.
Reason:
The CA Service Desk Interface address space has detected an internal error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Collect relevant documentation and contact CA Support.
Reason:
The CA Service Desk Interface address space has detected an internal error while parsing a statement or a command. The incorrect operand and keyword, if applicable, are conditionally shown in the message if this information can be determined.
Action:
Collect relevant documentation and contact CA Support.
Reason:
This message displays the CAISDI/med initialization values that are set on an INIT statement. For a detailed description of the meanings of these settings, see the section CAISDI/med Control Statement in the chapter “Running CAISDI” in the CA Service Desk Integration Guide.
Action:
No action is required.
Reason:
This message displays the CAISDI/med values that can be altered by the use of a SET OPTION command. For a detailed description of the meanings of these settings, see the section CAISDI/med Control Statement in the chapter “Running CAISDI” in the CA Service Desk Integration Guide.
Action:
No action is required.
Reason:
This message is issued in response to a DISPLAY MODULES command.
Action:
No action is required.
Reason:
This message is issued in response to a DISPLAY MODULES command. The CASD345I message shows the release of the CAISDI/med address space.
Action:
No action is required.
Reason:
This message is issued in response to a DISPLAY MODULES command. A CASD346I message is displayed for each CAISDI/med load module that shows the load module name, origin virtual address, and load module length. Following the CASD346I message is a tabular display of each control section within the named load module. Each line shows the CSECT name, virtual address, CSECT length, last applied APAR, assembly date, and assembly time.
Action:
No action is required.
Reason:
A DISPLAY PRODUCTS command was issued. The values are as follows:
Displays the product name.
Displays the job name.
Identifies the server that should receive the requests.
Displays the request priority.
Displays the Service Desk template name.
Identifies the end user affected by the request tickets.
Identifies the reporting user.
Displays the Service Desk contact ID to be assigned to every request ticket.
Displays the event qualifiers.
Action:
No action is required.
Reason:
A DISPLAY PRODUCTS NAME=product_name command was issued. No PRODUCT definitions matching the specified product_name were found.
Action:
Either correct the DISPLAY command to specify a valid product_name or define a product matching the desired name.
Reason:
A DISPLAY SERVERS command was issued. The values are as follows:
Displays the server name.
Indicates the server status.
Displays the CAISDI/soap Client CCI host name.
Displays the CAISDI/soap Client timeout in seconds.
Displays the CA Service Desk Server URL address.
Action:
No action is required.
Reason:
A DISPLAY SERVERS NAME=server_name command was issued. No SERVER definitions matching the specified server_name were found.
Action:
Either correct the DISPLAY command to specify a valid server_name or define a server matching the desired name.
Reason:
A CAISDI/med DISPLAY TASK operator command has been entered. A tabular display that includes the task name, task status, TCB address, and STE address, is returned. The task status can be one of the following:
Indicates that a previously stopped task is in the process of starting as a result of an operator START task command.
Indicates that the attached task is beginning initialization at startup.
Indicates that the task is active.
Indicates that the task is in the process of stopping as the result of an operator STOP task command.
Indicates that the task has stopped as a result of an operator STOP task command.
Indicates that the task has ended during shutdown processing.
Indicates that the task has encountered an unexpected abend.
Action:
No action is required.
Reason:
The indicated name is not a valid task name for a CAISDI/med operator START, STOP, or KILL command.
Action:
Use a valid task name. The DISPLAY TASK command can be used to determine valid task names.
Reason:
The indicated task has been scheduled to stop as the result of an operator STOP command.
Action:
No action is required. The task can be started again with a START task command.
Reason:
The indicated task has been scheduled to terminate through a directed abend as the result of an operator KILL command.
Action:
No action is required. The task can be started again with a START task command.
Reason:
The indicated task has been scheduled to start as the result of an operator START command.
Action:
No action is required.
Reason:
The indicated task was requested to start by an operator START command; however, the task is already started.
Action:
No action is required.
Reason:
The indicated task was requested to stop by an operator STOP command; however, the task is not eligible to be stopped.
Action:
No action is required.
Reason:
A CAISDI/med operator command was being processed and encountered an unexpected abend. The command response has been truncated.
Action:
No action is required.
Reason:
An operator has entered a STOP command for the CAISDI/med address space. The CAISDI/med address space will begin termination processing shortly.
Action:
No action is required.
Reason:
The indicated CAISDI/med operator command is being processed.
Action:
No action is required.
Reason:
The indicated CAISDI/med operator command encountered an unexpected abend during command processing.
Action:
Collect relevant documentation, including SVC dump and SYSLOG, and contact CA Support.
Reason:
A target command response location was entered on a CAISDI/med operator command. However, the indicated console response location is invalid or the target response console is not active.
Displays the hexadecimal return code returned by the CONVCON service.
Displays the hexadecimal reason code returned by the CONVCON service.
Action:
Enter the CAISDI/med operator command and specify a valid console response area.
Reason:
A CAISDI/med operator command has been entered; however, the command verb is missing or is invalid.
Action:
Enter a valid CAISDI/med operator command.
Reason:
A CAISDI/med operator command has been entered; however, the command verb is not recognized.
Action:
Enter a valid CAISDI/med operator command.
Reason:
A CAISDI/med operator command has been entered that requires command operands; however, the command operands have been omitted or are invalid.
Action:
Enter a valid CAISDI/med operator command.
Reason:
This message is issued in response to a SET OPTION command.
Action:
No action is required.
Reason:
This message is issued in response to the successful completion of a SET OPTION command.
Action:
No action is required.
Reason:
This message is issued in response to a SET SERVER command.
Action:
No action is required.
Reason:
This message is issued in response to a SET SERVER command that referenced an invalid server name.
Action:
The command is not executed. Use the DISPLAY SERVERS command to obtain the names of valid CAISDI/med server interface tasks.
Reason:
This message is issued in response to the successful completion of a SET SERVER command.
Action:
No action is required.
Reason:
The named task, with the given TCB address has been attached.
Action:
No action is required.
Reason:
The named task, with the given TCB address has been detached. The task has ended with the given completion code.
Action:
No action is required.
Reason:
This message displays the CAISDI/med initialization values that are set on an EXCLUDE ABEND statement. For a detailed description of the meanings of these settings, see the section CAISDI/med Control Statements, in the “Running CAISDI” chapter of the CA Service Desk Integration Guide.
Action:
No action is required.
Reason:
This message displays the CAISDI/med initialization values that are set on the EVENT ABEND statements. For a detailed description of the meanings of these settings, see the section CAISDI/med Control Statements, in the “Running CAISDI” chapter of the CA Service Desk Integration Guide.
Action:
No action is required.
Reason:
The CAISDI/med address space has been requested to shut down by an operating system STOP command.
Action:
No action is required. The CAISDI/med address space begins shutdown processing.
Reason:
The CAISDI/med address space has completed the shutdown process.
Action:
No action is required. The CAISDI/med address space ends.
Reason:
The CAISDI/els Interface Controller has started. It logs out the time of day and the language that will be used for writing messages to the log. The language selected for use for any given product controlled by this interface is independent of this language setting.
Displays the CA Common Services level identifier for CAISDI/els.
Action:
No action is required.
Reason:
The CAISDI/els uses a language table to create messages and report headings. The language elements are identified by name.
Identifies the element missing from the table.
Action:
CAISDI/els will use the internal symbolic name instead of the correct language element. In most cases, this will be the English version of a word. Contact CA Support to alert them to the problem.
Reason:
The CAISDI/els uses a language table to create messages and report headings. The language elements are identified by name.
Identifies the element that exceeds the maximum length for this context.
Action:
The language element (word) will be truncated from longer (the word as the translator specified it) to shorter (the word as it will be used in the CAISDI/els reports). Contact CA Support to alert them to the problem.
Reason:
The CAISDI/els component requires space to work in the address space built. This space will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
The CAISDI/els uses a language table to create messages and report heading.
Identifies the message that is missing.
Displays the internal variable values that were to be used in building the message text are dumped in the format of “keyword=value,keyword=value”. This will help CA Support determine the underlying meaning of the message.
Action:
Contact CA Support with the details of this message even if you are able to determine the meaning from the variable list that is presented.
Reason:
The CAISDI/els uses a language table to create messages and report headings.
Identifies the message that has been corrupted in some way.
Displays the internal variable values that were to be used in building the message text are dumped in the format of “keyword=value,keyword=value”. This will help CA Support determine the underlying meaning of the message.
Action:
Contact CA Support with the details of this message even if you are able to determine the meaning from the variable list that is presented.
Reason:
When you code PARM=value on your JCL EXEC statement you will receive this message. Both the CAISDI/els Controller Interface and Trigger utility allow you to specify “&PARM” anywhere in the command input. This message is notifying you of the replacement string that will be used for &PARM.
Action:
The internal symbolic variable &PARM has been assigned the value shown as value.
Reason:
Every control statement processed is logged out in the SYSPRINT data set.
Displays the control input as seen by CAISDI/els. Any sequence numbers on the control input will not be present in this image. Also, certain control input, such as passwords, will be masked out.
Action:
No action is required.
Reason:
The CAISDI/els component was expecting to receive a command from the control input at this point, but instead it encountered word, which is not a command.
Action:
Check for improper continuation of the previous command or typographical errors. If your language setting is not English, check with your local CA Support staff to determine the degree of translation employed. Commands and control parameters may be translated also.
Reason:
An unclassifiable syntax error was detected. This should never occur.
Action:
Study the control statement image on the preceding CASD408I message. The value column indicates the position of the parsing scan at the time the error was detected. The value of column is relative to one.
Reason:
CAISDI/els was parsing the parameters for the command named cmd. The control statement indicated a continuation onto the next input record, but there was no more data in the control input file.
Action:
Processing for the command named cmd is terminated. The control input stream may have been accidentally truncated. Look for misplaced DD statements in the JCL that may have inadvertently truncated the control input stream.
Reason:
A syntactical error was discovered in the current command as evidenced by an error message printed preceding this message. CAISDI/els flushes out the rest of the command stream based on continuation indicators until a new command is encountered.
Displays an image of the control statement being skipped.
Action:
Processing continues with the next command in the command stream.
Reason:
A valid command is being parsed. During the parsing the word parm was found in a position where CAISDI/els would expect a parameter. This word is not a recognized parameter for any Interface Controller commands.
Action:
Processing for the current command will be terminated. Verify the spelling of this parameter. Verify the placement of embedded comments. At least one blank must follow a comma when continuation to the next statement is desired. If your language setting is not English, check with your local CA Support staff to determine the degree of translation employed. Commands and control parameters may be translated also.
Reason:
While parsing the valid command named cmd, CAISDI/els encountered the parameter named parm. While parm is a valid parameter is some contexts, it is not valid to use it with the command named cmd.
Action:
Processing for the current command is terminated. Processing will resume with the next command encountered in the command stream. Remove the parameter named parm from the control statement.
Reason:
The valid parameter named parm was correctly parsed during the processing of this command. You cannot specify this parameter again on the same command.
Action:
Processing for the current command is terminated. Processing will resume with the next command encountered in the command stream. Remove the parameter named parm from the control statement.
Reason:
The valid parameter named parm was being parsed. CAISDI/els was in the process of extracting the value, if any, when a syntactical error was discovered.
Action:
Processing is terminated for the current command. Ensure the parameter you have coded is supposed to have a value assignment. If a value assignment is expected, make sure you use the format parameter=value or parameter=”value” in your specifications. If you need to continue a long string value onto a continuation statement, add a trailing “+” on the command line to be continued, such as parameter=”long string”+ and begin the continued statement with “ value”.
Reason:
The valid parameter named parm was being parsed. CAISDI/els was in the process of extracting the value, if any, when a syntactical error was discovered. The value of the parameter is not delimited as required.
Action:
Processing is terminated for the current command. A value assignment is expected for this parameter. Make sure you use the format parameter=value or parameter=”value” in your specifications. If you need to continue a long string value onto a continuation statement, add a trailing “+” on the command line to be continued, such as parameter=”long string”+ and begin the continued statement with “ value”.
Reason:
The previous control statement ended with a string value showing a continuation onto the next statement. No continuation was found.
Action:
You cannot embed an all-blank control statement where a continuation is expected. If you need to continue a long string value onto a continuation statement, add a trailing “+” on the command line to be continued, such as parameter=”long string”+ and begin the continued statement with “ value”. Make sure you user the same delimiter, either the single or double quote, on the continued line as you used on the statement that was marked as continued.
Reason:
The previous control statement ended with a string value showing a continuation onto the next statement. The first nonblank character on the continued statement must be the delimiter that was being used on the string being continued. The delimiter used on the previous line was dlm. The continued string value may be placed in any input column.
Action:
To continue a long string value onto a continuation statement, add a trailing “+” on the command line to be continued, such as parameter=”long string”+ and begin the continued statement with “ value”. Make sure you use the same delimiter, either the single or double quote, on the continued line as you used on the statement that was marked as continued.
Reason:
The parameter named parm has just been parsed. The complete value of this parameter has been extracted. CAISDI/els expects to find either a comma or a blank following the value, indicating either more parameters or end of all parameters, respectively.
Action:
Examine the control statement and correct the text following the value of the parameter named parm. Comments must be separated from the command parameters with at least one blank.
Reason:
The command named cmd was being parsed. The previous control statement indicated a continuation onto the current control statement, but this statement is blank. You cannot embed an all-blank control statement in the middle of a command
Action:
Remove the blank line.
Reason:
CAISDI/els was in the process of extracting the value of the parameter named parm. The value was marked as being continued on the next line, but no more data remains in the command stream.
Action:
Processing for this command is terminated. The control input stream may have been accidentally truncated. Look for misplaced DD statements in the JCL that may have inadvertently truncated the control input stream.
Reason:
Certain control parameters have a maximum length. The value for the parameter named parm can be no longer than the number nbr characters long. The value you specified is longer than this.
Action:
Correct the parameter by shortening the value you specified.
Reason:
Each command has a large, but limited amount of space allocated to text strings. The command you specified consumed all of the string space before the parsing was completed.
Action:
In the unlikely event that this error is seen, contact CA Support for a correction.
Reason:
Certain control parameters must contain all numeric data. The parameter named parm is one of those parameters.
Action:
Correct the value by removing any nonnumeric characters from the value assignment.
Reason:
Certain control parameters have numeric values that have a range of valid values. The value you coded for the parm parameter is out the valid range of values for that parameter.
Action:
Specify a value for the parm parameter that is less than or equal to lmt.
Reason:
Certain control parameters have alphabetic values that have a limited number of valid values. The value you coded, value, is not one of those choices.
Action:
See the chapter “Running CAISDI” in the CA Service Desk Integration Guide for the list of value choices for the parameter named parm.
Reason:
Certain control parameters require their value assignments to conform to specific and strict formats. For example, the MINTIME parameter expects the input to be in the format of MINTIME=hh:mm, where the hh portion is expected to be a numeric value expressing hours and mm is expected to be a numeric value expressing minutes, with all of the numeric range limits you would expect. The value you code as value does not conform to the format rules of the parameter named parm.
Action:
See the chapter “Running CAISDI” in the CA Service Desk Integration Guide for the correct format of the parameter named parm.
Reason:
Certain control parameters are required for certain commands. In this case the command named cmd requires the parameter named parm to be specified, but you did not specify it.
Action:
Add the parm parameter to the command specification and rerun the command. Note that the DEFAULTS command can be used to specify this parameter once at the beginning of the command stream. Any subsequent command requiring this parameter will be satisfied by the parameter values set by the DEFAULTS command.
Reason:
Certain control parameters cannot be used in conjunction with certain other control parameters. The command named cmd is being parsed when the parameter named parm1 was encountered. The parameter named parm2 had already been specified previously. These parameters cannot coexist on the same command.
Action:
Remove either parm1 or parm2 from the command.
Reason:
This marks the normal end of all command processing.
Action:
No action is required.
Reason:
An error processing this command is listed preceding this message. This is notification that the command is being aborted.
Action:
Processing continues with the next control statement. Correct the problems identified by the preceding message.
Reason:
All command parameters have been successfully parsed and the command named cmd is being dispatched to the module that services it.
Action:
No action is required.
Reason:
Because some parameters, even required parameters, may have received their values from a previous DEFAULTS control statement, this message is used to alert you to all the relevant control parameter settings being used, whether or not they were actually coded on the current command.
Action:
No action is required.
Reason:
Because some parameters, even required parameters, may have received their values from a previous DEFAULTS control statement, this message is used to alert you to all the relevant control parameter settings being used, whether or not they were actually coded on the current command.
Action:
No action is required.
Reason:
The DEFAULTS command has changed the default values for the parameter named parm. The new value, value, will be used in all subsequent commands where the parameter named parm is not specified.
Action:
No action is required.
Reason:
The DEFAULTS command has changed the default setting for the parameter named parm. The new setting will be used in all subsequent commands where the parameter named parm is not specified.
Action:
No action is required.
Reason:
The product control member for a CA product using the interface is being processed by the DEFINE command. All product control parameters have been parsed and the product definition is now beginning.
Action:
No action is required.
Reason:
The product control member for a specific product is being processed. All control parameters have been read and accepted. This message is notifying you of all relevant parameter values, whether or not they were specified.
Action:
No action is required.
Reason:
The product control member for a specific product is being processed. All control parameters have been read and accepted. This message is notifying you of all relevant parameter values, whether or not they were specified.
Action:
No action is required.
Reason:
The command module for the command named cmd has completed all processing and returned control to the Interface Controller. The return, reason, and information codes it returned are logged out.
Action:
If any nonzero value appears for rc, this indicates problems were encountered during processing. Scan back up the log searching for previously logged error or warning messages to determine the exact problem encountered.
Reason:
All commands have now been processed from the command stream.
Displays the value of the highest return code from the processed commands.
Action:
If any nonzero value appears for rc, this indicates problems were encountered during processing. Scan back up the log searching for CASD442I messages showing nonzero return codes, and then scan back to find previously logged error or warning messages to determine the exact problem encountered.
Reason:
CAISDI/els is in the process to defining a CA product to the interface. It is preparing to load the product event members from the product's event library. The event library data set is dsn, which is on the disk volume volser. The DD used to access this library is named ddname.
Action:
No action is required.
Reason:
CAISDI/els was attempting to allocate a product's event library, but the library could not be accessed. Either the system LOCATE function indicated the library was not cataloged or the system OBTAIN function indicated the library was not on the volume the system catalog indicated.
Displays the return code from the system function.
Action:
Ensure the correct data set name has been specified in the EVENTLIB control parameter for this product. Ensure that data set is cataloged. If you are running on multiple systems, make sure the library is cataloged in a user catalog that is properly connected to all systems in question.
Reason:
CAISDI/els was unable to allocate the event library.
Action:
Refer to IBM documentation on the DYNALLOC system function to interpret the values of rc, err, and info.
Reason:
The event library specified by EVENTLIB=dsn identifies a data set, but this data set is not a partitioned data set (PDS).
Action:
Change the EVENTLIB specification on the DEFINE control statement to name the correct event library.
Reason:
The event library specified by EVENTLIB=dsn identifies a data set, but this data set does not have a supported record format. CAISDI/els supports event libraries whose record format is fixed or variable, blocked or unblocked. Undefined record format, control character usage, and spanned records are not supported.
Action:
Change the EVENTLIB specification on the DEFINE control statement to name the correct event library.
Reason:
CAISDI/els was loading the event library directory into memory, but ran out of available storage. This space will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
CAISDI/els was loading the event library directory into memory, but ran out of available storage. This space will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
CAISDI/els was trying to read the event table library member into memory, but ran out of available storage. This space will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
CAISDI/els attempted to open the event library, but the OPEN system function failed.
Action:
Review the console log or the job log for system messages that identify the problem that was encountered.
Reason:
The system service named DESERV is used to read the event library's directory. An unanticipated error occurred.
Displays the return code from DESERV.
Action:
Refer to IBM documentation on the DESERV system function to interpret the values of rc and rs.
Reason:
The system service named POINT is used to orient to various members within the event library. An unanticipated error occurred while positioning to the member name memname.
Displays the return code from POINT.
Action:
Refer to IBM documentation on the POINT system function to interpret the values of rc and rs.
Reason:
All processing for the event library name dsn has been concluded. The library is no longer needed and is being released.
Action:
No action is required.
Reason:
Every product defined to the CAISDI/els interface must have a product control member. The member named memname is the member CAISDI/els was seeking, but this member name was not found.
Action:
Verify the correct product control member name. Make sure the DEFINE control statement includes the PRODCNTL control parameter naming the correct member. If PRODCNTL is not specified, a default member name is assumed which may not be the case for this product.
Reason:
A member named memname exists and is assumed to be the product control member. CAISDI/els will read the control information contained in memname.
Action:
No action is required.
Reason:
The product control information for the product being defined to the CAISDI/els interface has been successfully processed.
Action:
No action is required.
Reason:
Errors were encountered during the attempt to define the product named prodname to the CAISDI/els interface. The definition for this product has failed.
Action:
Review the preceding messages in the log to determine the exact cause of the failure.
Reason:
The PRODUCT parameter of the DEFINE control statement indicates prodid1 while the PRODUCT parameter of the SETUP command in the product control member indicates prodid2. These codes must match.
Action:
Ensure the EVENTLIB control parameter on the DEFINE statement names the correct event library. If multiple products are defined in a single event library, make sure the PRODCNTL parameter of the DEFINE statement is naming the correct product control member name.
Reason:
Certain control parameters accept a range of numeric values. If a value for one of these control parameters is exceeded, CAISDI/els simply reduces the setting down to the maximum allowed and continues processing without error. The parameter name parm is one of those parameters. The value of nbr was greater than the limit value of limit, so it was reduced to that value.
Action:
Processing continues with the reduced value.
Reason:
The CAISDI/els component requires space to build various tables. This space will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
The internal table management routines encountered an unexpected error during processing. The values of rc and rs are the return and reason codes from the table management services.
Action:
Contact CA Support for assistance in determining the cause of this error.
Reason:
CAISDI/els was applying the MASK control parameter to filter the list of event library members down to include only event member names. However, no event library member names match this mask value.
Action:
Ensure the EVENTLIB= parameter of the DEFINE command identifies the correct event library. Verify the MASK value is set according to the member naming conventions. Ensure all current maintenance has been applied to the CA product being defined to this interface.
Reason:
Event members can be published in several different languages. The event code is the first six characters of the event member name and the language code is last two characters. CAISDI/els determines which languages are supportable by the event members present. This message heads a list of languages identified by subsequent CASD466I messages.
Action:
No action is required.
Reason:
For each language detected among the event members, a CASD466I message will be issued.
Displays the two-character language code detected.
Names the language.
Action:
No action is required.
Reason:
If some, but not all, events have been translated from English into other languages, CAISDI/els will use the English versions of any untranslated messages. This message notes the beginning of that analysis.
Action:
No action is required.
Reason:
CAISDI/els has detected an event that has not been translated into one of the languages published for this product. The member named memname is the expected member name and langname identifies the language. This may be irrelevant if the language identified by langname is not chosen as the target language for this product's CA Service Desk request tickets.
Action:
No action is required.
Reason:
The language selected for this product's CA Service Desk request tickets requires one of the messages identified in a previous CASD468W message. The English version must be used in order to cover all of the events supported by this product.
Action:
Contact CA Support and notify them of this problem. Until the translated version of this event is published, the English version will be used.
Reason:
The language selected for this product, identified by langname, has no events at all translated for it. The cd value is the associated language code. The English version will be substituted for all events.
Action:
No action is required.
Reason:
CAISDI/els is beginning the process of loading all of the event members into control storage for later reference by the CAISDI/els API module.
Action:
No action is required.
Reason:
CAISDI/els is detecting if CCI is available and the name of the local node.
Action:
No action is required.
Reason:
The local CCI node (ccinode) has been detected.
Action:
No action is required.
Reason:
A SOAP client has been identified, but CAICCI indicates this CAISDI/soap address space is not active at the moment. The general location of “Local” or “Remote” indicates where the CAISDI/soap address space is running.
Identifies the CAICCI node serving that CAISDI/soap address space.
Action:
No action is required.
Reason:
CAISDI/els requires the CAISDI/soap address space in order to open CA Service Desk request tickets. Without the CAISDI/soap interface being available, the CAISDI/els interface cannot be established.
Action:
Ensure the CAISDI/els interface is properly installed and configured. Ensure the CAISDI/soap address space is started, and the CAICCI connections are configured and available.
Reason:
One or more CAISDI/soap address spaces have been detected in your environment. These address spaces are considered candidates until they have been tested for a good connection to the target CA Service Desk server.
Action:
No action is required.
Reason:
The CAISDI/els component requires space to build various tables. This space will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
The CAISDI/els component requires space to build various tables. This space will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
The internal table management routines encountered an unexpected error during processing.
Displays the return code from the table management services.
Displays the reason code from the table management services.
Action:
Contact CA Support for assistance in determining the cause of this error.
Reason:
An unanticipated error occurred during the SOAP client discovery process.
Displays the CAICCI return code for the function indicated: INIT, INQY, or TERM.
Displays the CAICCI general return code.
Displays the CAICCI specific return code.
Displays the CAICCI extended return code.
Action:
Ensure CAICCI is started on the system where this failure occurred. See CAICCI Return Codes in the chapter “Codes” for a more detailed description of the problem.
Reason:
The CAISDI/els Interface Controller will use the CAISDI/soap address space on the CAICCI node named ccinode for all current communications to the CA Service Desk server.
Action:
No action is required.
Reason:
Displays the name of the environmental variable defined in the SOAP Server that holds the URL. The default name is SD_URL.
Action:
No action is required.
Reason:
Each candidate CAISDI/soap address space found is tested to see if it can connect to the target CA Service Desk server. Access to that server through the CAISDI/soap address space on CAICCI node ccinode is being attempted. If a connection is made, this CAISDI/soap address space may be used as the primary or failover connection in subsequent processing.
Action:
No action is required.
Reason:
The connection to ServiceDesk was refused. The err_text has additional diagnostic information.
Action:
The request fails.
Reason:
After a successful logon, CAICCI/els encountered an unexpected error from the Service Desk server during a query sequence. In many cases, CAISDI/els will retry the failing query up to five times in case the error resulted from a transient problem in the network. The rc, rs, and info codes are the return codes from the CAISDI/soap API.
Action:
If the retry sequence succeeds, processing continues; otherwise, a follow-up failure message will be displayed. See CAISDI/soap API Return Codes in the chapter "Codes" for a more detailed description of the problem.
Reason:
After a successful logon, CAICCI/els encountered an unexpected error from the Service Desk server during the logoff sequence. This is not retried. The rc, rs, and info codes are the return codes from the CAISDI/soap API.
Action:
See CAISDI/soap API Return Codes in the chapter "Codes" for a more detailed description of the problem.
Reason:
Each candidate CAISDI/soap address space found is tested to see if it can connect to the target CA Service Desk. Access to that URL through the CAISDI/soap address space on CAICCI node ccinode was successful. The response time is noted. This SOAP address space may be used as the primary or failover connection in subsequent processing.
Action:
No action is required.
Reason:
Multiple CAISDI/soap address spaces successfully connected to the target CA Service Desk parameter. However, this particular CAISDI/soap address space, on CAICCI node ccinode, had the best response time, so it will be used as the primary connection.
Action:
No action is required.
Reason:
Only one CAISDI/soap address space, on CAICCI node ccinode, successfully connected. Since there is only one possible connection, the response time analysis is skipped.
Action:
No action is required.
Reason:
All available CAISDI/soap address spaces were tested for a connection to the URL you designated. The CAISDI/els interface could not be enabled. If this is an actual URL, urlref will be the full IP address of the server. If the URL is being addressed symbolically through CAISDI/soap environmental variables, urlref will be the clause “URL defined by CAISDI/soap variable varname” where varname identifies a variable from the CAISDI/soap configuration file. The default variable name is SD_URL.
Action:
Verify the URL designates the correct server name. Ensure the Service Desk server is up and running. Look for previous error messages that may indicate a problem with the ID or password used to logon to the Service Desk. If varname is a CAISDI/soap variable reference, examine the configuration file that the CAISDI/soap client address space reads when it starts, and look for the variable assignment for the variable named varname.
Reason:
If multiple products are being defined in a single execution of the CAISDI/els Interface Controller and those products are being directed to the same instance of the Service Desk, the connections are not retested. The previous test results and response time will be used to set up this product. If this is an actual URL, urlref will be the full IP address of the server. If the URL is being addressed symbolically through CAISDI/soap environmental variables, urlrel will be the clause “URL defined by CAISDI/soap variable varname” where varname identifies a variable from the CAISDI/soap configuration file.
Action:
No action is required.
Reason:
After successfully testing the connection and selecting a specific CAISDI/soap address space, the initial logon for the DEFINE command failed. The rc and rs codes are the return codes from the CAISDI/soap API.
Action:
Processing terminates. See CAISDI/soap API Return Codes in the chapter "Codes."
Reason:
The XML data from ServiceDesk to the SOAP Server did not contain the expected data for the specified varname.
Action:
Contact CA Support for assistance in determining the cause of this error.
Reason:
CAISDI/els was querying the Service Desk for information regarding Contacts defined within the Service Desk database when an unanticipated error occurred. The rc, rs, and info codes are the return codes from the CAISDI/soap API.
Action:
Contact CA Support. For more information, see CAISDI/soap API Return Codes.
Reason:
The CAISDI/els Interface Controller is assigning the CAISDI/soap address space on CAICCI node ccinode to be the main connection handler for the interface. If alternate CAISDI/soap address spaces can be used, they will be listed next in subsequent CASD496I messages.
Action:
No action is required.
Reason:
The CAISDI/els Interface Controller is assigning the CAISDI/soap address space on CAICCI node ccinode the role of a failover connection handler for the interface in the event the primary connection fails. Failover address spaces are listed in the order of response time, with the fastest being listed first.
Action:
No action is required.
Reason:
If only one CAISDI/soap address space successfully connected to the Service Desk, you cannot have any failover assignments.
Action:
Consider setting up another CAISDI/soap address space on another system for failover purposes.
Reason:
The CAISDI/els Interface Controller is about to check the Service Desk contacts you identified in the REPORTED_BY, ASSIGNEE, and AFFECTED_END_USER control parameters.
Action:
No action is required.
Reason:
The contact, whose Service Desk logon ID is id, was not in the Service Desk data base and USD_AUTODEF=NO was in effect.
Action:
Use the ID of a valid contact in the CA Service Desk and attempt the DEFINE again. Alternatively, set USD_AUTODEF=YES and attempt the DEFINE again.
Reason:
The contact, whose Service Desk ID is id, was not in the Service Desk database, and USD_AUTODEF=YES was in effect, so CAISDI/els created this contact in the Service Desk database.
Action:
No action is required.
Reason:
The contact, whose Service Desk logon ID is id, was not in the Service Desk data base, and USD_AUTODEF=YES was in effect, so CAISDI/els created this contact in the Service Desk database. Since this contact will be used in the role of being assigned to the request, this contact was created as the type “Analyst.”
Action:
No action is required.
Reason:
The contact, whose Service Desk logon ID is id, was not in the Service Desk database, and USD_AUTODEF=YES was in effect, so CAISDI/els attempted to create this contact in the Service Desk database. This message is preceded by a more specific error message describing the error condition itself.
Action:
Use the logon ID of a valid contact in CA Service Desk and attempt the DEFINE again. Alternatively, research the underlying cause of the automatic define failure.
Reason:
The contact, whose Service Desk logon ID is id, was defined in the Service Desk database, but this contact must be of the type “Analyst” to be used as the assignee on the Service Desk request tickets that are opened.
Action:
Use the logon ID of a valid contact in the CA Service Desk that is of the type “Analyst” and attempt the DEFINE again.
Reason:
The CAISDI/els Interface Controller is about to check the Service Desk asset you identified in the ASSET control parameter.
Action:
No action is required.
Reason:
The asset, whose Service Desk network resource name is assetname, is not in the Service Desk database and USD_AUTODEF=NO was in effect.
Action:
Use the name of a valid asset in the CA Service Desk and attempt the DEFINE again. Alternatively, set USD_AUTODEF=YES and attempt the DEFINE again.
Reason:
The asset named assetname was not in the Service Desk database, and USD_AUTODEF=YES was in effect, so CAISDI/els created this asset in the Service Desk database under the asset class of “Software.”
Action:
No action is required.
Reason:
The asset named assetname was not in the Service Desk database, but USD_AUTODEF=YES was in effect, so CAISDI/els attempted to create this asset in the Service Desk database. The rc, rs, and info codes will help in problem determination. The rc, rs, and info codes are the return codes from the CAISDI/soap API.
Action:
Use a valid asset name from CA Service Desk and attempt the DEFINE again. Alternatively, research the underlying cause of the automatic define failure. For more information, see CAISDI/soap API Return Codes.
Reason:
The CAISDI/els Interface Controller is about to check the Service Desk template you identified in the TEMPLATE control parameter.
Action:
No action is required.
Reason:
The template, whose Service Desk name is tempname, is not in the Service Desk database.
Action:
Use the name of a valid template in the CA Service Desk and attempt the DEFINE again.
Reason:
CAISDI/els is preparing to access the event member named memname in the DEFINE process.
Action:
No action is required.
Reason:
An unanticipated error occurred while attempting to read an event member. Messages immediately preceding this message will describe the error in detail.
Action:
Processing for the current command terminates. Examine the preceding message to determine the problem.
Reason:
This message marks the conclusion of processing for the event member named memname. It is only displayed if TRACE=EVENTS or TRACE=ALL is specified.
Action:
No action is required.
Reason:
The SET command must be the final and only control statement in the event member. More data was detected in the event member after the SET control statement. Those lines are displayed in one or more CASD516E messages that follow.
Action:
Remove the lines following the SET command. If you need to add comments to this member, comment lines are only valid if placed after the OPTIONS tag and before the SET command. Comments are notated with an asterisk in column one.
Reason:
The SET command must be the final and only control statement in the event member. More data was detected in the event member after SET control statement.
Displays the data that was found following the SET command.
Action:
Remove the lines following the SET command. If you need to add comments to this member, comment lines are only valid if placed after the OPTIONS tag and before the SET command. Comments are notated with an asterisk in column one.
Reason:
This event member is not in the correct format.
Action:
Ensure that the most current and correct event library is being accessed.
Do not combine events from multiple event libraries into a single event library. If you have saved a nonevent member in an event library, you run the risk of it being interpreted as an event member. If the failing product's product control member contains a MASK parameter on the SETUP command, ensure all members matching the mask are truly event members.
Any product group may choose to call a given event by the same name as an unrelated event from another product, so each product's event members must be kept separate from all others.
Reason:
The event member section headers may not contain any other data or comments.
Action:
Remove the extra text from this event member's section identified as sectionid.
Reason:
There has been an error in editing this event member. Each section head may appear only once in any given event member.
Action:
Look for improper duplication of lines within the event member and remove the duplicate section.
Reason:
The current event member contains an imbedded symbolic parameter that exceeds the maximum length of eight characters, not including the “&”. The symbolic names are only known to the product that is using the CAISDI/els interface.
Action:
Contact the product support group for the product identified by the PRODUCT= parameter on the current DEFINE command.
Reason:
Each event member must have SUMMARY, DESCRIPTION, and OPTIONS sections. The section identified by sectionid is missing.
Action:
Ensure that the most current and correct event library is being accessed.
Do not combine events from multiple event libraries into a single event library unless directed to do so by that product's documentation. If you have saved a nonevent member in an event library, you run the risk of it being interpreted as an event member. If the failing product's product control member contains a MASK parameter on the SETUP command, ensure all members matching the mask are truly event members.
Any product group may choose to call a given event by the same name as an unrelated event from another product, so each product's event members must be kept separate from all others unless they have been named in such a way that MASK control parameters can keep them separated.
Reason:
The CAISDI/els component requires space to build the Product Control Structure, both in local memory and in Extended CSA. The local storage will be released when this process terminates. This storage is not retained for purposes of keeping the interface active, but the Extended CSA is retained until a SHUTDOWN or REMOVE command frees it.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
All event members identified by the product control member have been successfully processed. The Product Event Table of this product can now be built in Extended CSA.
Action:
No action is required.
Reason:
The value of nbr1 indicates the total amount of text data loaded from the product event members. While this data is not compressed, CAISDI/els attempts to save space by building the text pool so that strings of text that are used in one event, which match identically the text of another event, are stored only once and referred to by both events. The value of nbr2 indicates the total space required to store all of the text plus the control headers that address it.
Action:
No action is required.
Reason:
The value of nbr indicates the total amount of Extended CSA required to store this product's Product Event Table.
Action:
No action is required.
Reason:
There is one Event Anchor Block from which all Product Event Tables are chained, located in Extended CSA.
Action:
No action is required.
Reason:
There is one Product Event Table for each product defined to the CAISDI/els interface.
Displays the ID of a product defined.
Displays the location in Extended CSA.
Action:
No action is required.
Reason:
An unanticipated error occurred when the CAISDI/els Interface Controller was attempting for find or lock the Event Anchor Block.
Action:
The rc and rs codes will help you research the problem. The more common values of rc are:
|
rc |
Meaning of Return Code |
|---|---|
|
8 |
ENQ failure, rs is the ENQ return code |
|
16 |
DEQ failure, rs is the DEQ return code |
|
20 and higher |
Problems with Name and Token Services |
Reason:
You are attempting to DEFINE PRODUCT=prodid and it is already defined to the interface. This DEFINE attempt will fail, but processing will continue with the next command.
Action:
This can result from running your normal startup control statements after the CAISDI/els interface has already been enabled.
If you want to refresh a given product's interface, use the REMOVE PRODUCT=prodid followed by a DEFINE PRODUCT=prodid. If you want to refresh the entire CAISDI/els interface, use the SHUTDOWN command followed by the normal startup command set.
Reason:
CAISDI/els was attempting to copy the Product Event Table into Extended CSA when an unexpected error occurred. The values of rc and rs, the return and reason codes, respectively, identify the exact problem.
Action:
The action required depends on the return codes encountered. The rc and rs codes will help you research the problem. The more common values of rc are:
|
rc |
Meaning of Return Code |
|---|---|
|
20 |
Problems with Name and Token Services |
|
24 |
Not enough Extended CSA remains to build the Product Event Table |
|
44 |
Product Event Table update routine could not be installed |
Reason:
CAISDI/els was attempting to delete the Product Event Table from Extended CSA when an unexpected error occurred. The values of rc and rs, the return and reason codes, respectively, identify the exact problem.
Action:
The action required depends on the return codes encountered. The rc and rs codes will help you research the problem. The more common values of rc are:
|
rc |
Meaning of Return Code |
|---|---|
|
20 |
Problems with Name and Token Services |
|
28 |
Attempt to free Extended CSA failed |
Reason:
During SHUTDOWN processing, the Product Event Table update routine is terminated and removed from Extended CSA. An unanticipated failure was encountered.
Action:
The Product Event Table update routine may remain in Extended CSA, but it has been disconnected from the Event Anchor Block. Any subsequent DEFINE command will bring a fresh copy of the update routine into storage. The values of rc are:
|
rc |
Meaning of Return Code |
|---|---|
|
16 |
DEQ of the Event Control Structure failed |
|
20 |
Problems with Name and Token Services |
|
28 |
Attempt to free Extended CSA failed |
Reason:
During SHUTDOWN processing, this message confirms that all Product Event Tables have been disconnected from the Event Anchor Block, and the Extended CSA they occupied has been freed.
Action:
No action is required.
Reason:
This message confirms the Product Event Table for the product identified as prodid has been removed from the CAISDI/els interface, and the Extended CSA that it previously occupied has been freed. The value of nbr indicates the number of bytes returned to Extended CSA.
Action:
No action is required.
Reason:
This message confirms the Product Event Table update routine has been removed from the CAISDI/els interface, and the Extended CSA that it previously occupied has been freed.
Displays the number of bytes returned to Extended CSA.
Action:
No action is required.
Reason:
As a result of SHUTDOWN or REMOVE processing, some quantity of Extended CSA has been freed for each Product Event Table removed. This message summarizes the Extended CSA being freed by the current command.
Action:
No action is required.
Reason:
The current command designates PRODUCT=prodid to direct the command to a specific Product Event Table. The designated Product Event Table does not exist.
Action:
Verify the spelling of the product ID. Ensure the CAISDI/els interface is currently active.
Reason:
Freeform TRIGGER keywords are restricted to eight characters. These keywords must match symbolic parameters embedded in the summary and description text of the event member for the event to be triggered.
Action:
Examine the event member for the event you wish to trigger. Embedded symbolic parameters can be recognized because they all begin with an “&”. If the event member contained the symbolic parameter &DSN, then the TRIGGER control statement should include DSN=some.data.set.name to properly match the symbolic parameter with your keyword.
Reason:
In response to a DISABLE command, the CAISDI/els has successfully disabled, and the CAISDI/els interface for the product identified as prodid.
Action:
No action is required.
Reason:
In response to an ENABLE command or as the final act of the DEFINE command, the CAISDI/els interface for the product identified as prodid is now active and ready for use.
Action:
No action is required.
Reason:
The CAISDI/els Interface Controller requires a DD statement named ddname to be allocated as a REPORT data set. The attempt to OPEN this data set failed.
Action:
Review the job log or console log to find additional error messages that may have been issued by the operating system.
Reason:
CAISDI/els was processing a DISABLE command. CAISDI/els expects the interface for the product identified as prodid to be enabled, but the interface for this product is currently disabled.
Action:
Processing continues as normal, but this results in the return code for the DISABLE command being set to 4.
Reason:
CAISDI/els was processing an ENABLE command. CAISDI/els expects the interface for the product identified as prodid to be disabled, but the interface for this product is currently enabled.
Action:
Processing continues as normal, but this results in the return code for the DISABLE command being set to 4.
Reason:
The query to CA Service Desk completed with no errors. If the value of n is greater than zero, then a report of currently open Service Desk request tickets will be written to the REPORT DD.
Action:
If the value of n seems incorrect, find the CASD482I message earlier in the log and ensure the desired Service Desk was queried. Log on to the Service Desk and check the request status.
Reason:
The LOAD for the CAISDI/soap API module, CAS0PCLI, failed. This module must be in the link list.
Action:
Ensure the CAISDI/soap component is installed in the system where this job is running. The CAISDI/soap address space does not need to be running on this system, but the API module must be available through the link list.
Reason:
The CAISDI/els component requires storage to build various buffers. This storage will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M and run the job again.
Reason:
The sessions with the CA Service Desk begin with a logon and continue with queries and then end with a logoff. CAISDI/els tracks the total wait for all of the interactions with the Service Desk and the number of queries made, including the logon and logoff. After the logoff, this message is printed to inform you of the quality of the connection you are using.
Action:
No action is required.
Reason:
Certain errors occurring during a query sequence may be due to transient network conditions, so CAISDI/els retries many of its queries if they are of a class that might be due to transient network conditions. CAISDI/els will retry a failing query up to five times. If the retry is successful, message CASD549I will be issued.
Action:
No action is required.
Reason:
As a follow-up to CASD548I, this message indicates the query failure displayed immediately preceding the CASD548I message was a transient problem that cleared up.
Action:
No action is required.
Reason:
The internal buffer used for constructing the XML packets was not large enough to hold the required XML.
Action:
The internal structures defining the XML sequences have been corrupted. Ensure the most current maintenance has been properly applied.
Reason:
When event member text is loaded into the Product Event Tables, certain characters are translated into XML symbolic references. For example, “<” and “>” are translated into “<” and “>” to allow the text to be transported through XML to CA Service Desk. This causes the text length to increase. If the number of special characters being translated causes the resulting string to overrun the internal buffer, this message is produced.
Identifies the event member being processed.
Displays the editing progress that had been made up to the time of failure.
Action:
Split the offending line into multiple lines.
Reason:
CAISDI/els was processing the current command and needed to acquire additional storage, but the GETMAIN failed.
Action:
The current command is terminated. Increase the REGION size and try the command again.
Reason:
CAISDI/els was processing a command that required the CAISDI/els interface to be active, but it was not.
Action:
The command is terminated with a return code of 8. Processing continues with the next command.
Reason:
This CAISDI/soap client received and error performing function function. The Unicenter Service Desk indicated the error message in err_text.
Action:
Examine the error message. If the err_text indicates the ID or password may be invalid or expired, contact your internal Service Desk personnel and ask for a valid ID and password, and then specify that ID and password in the SD_USER and SD_PASS variable settings in the CAISDI/soap configuration file. If you update the configuration file, the CAISDI/soap Client address space must be stopped and restarted..
Reason:
CAISDI/els requested function be performed but the #SOAPSDI interface routine returned error rc.
Action:
Examine the error codes in the CAISDI/soap component.
Reason:
CAISDI/els requested function be performed by the CAISDI/soap Server but CCI indicated an error communicating with the SOAP Server.
Action:
Examine the CCI error or contact CA Support.
Reason:
CAISDI/els requested function be performed by the CAISDI/soap Server which indicated return code rc and reason code rs.
Action:
Examine the error codes in the CAISDI/soap component.
Reason:
CAISDI/els was attempting to process the LIST command when the SOAP Client indicated return code rc and reason code rs.
Action:
Contact CA Support. For more information, see CAISDI/soap API Return Codes.
Reason:
A CA program has called the CAISDI/els API module to open a CA Service Desk request ticket, but a serious error in the CAISDI/els interface or in the environment was detected. This message is issued on behalf of that CA product. The CA program that called the CAISDI/els API was given these return codes and control was passed back to it.
Displays the common name of the CA product that called the CAISDI/els API.
Indicates the condition the product was trying to report in the CA Service Desk request ticket.
Displays the return code.
Displays the reason code.
Displays the information code.
Action:
See CAISDI/els API Return Codes in the chapter "Codes."
Reason:
A new request was opened in the CA Service Desk for the product prodid. The request number assigned was reqnbr.
Action:
No action is required.
Reason:
Each product event member may contain the MINTIME specification in the form of MINTIME=hh:mm. This is a throttling mechanism to prevent a flood of Service Desk request tickets from being opened when a given event may be recognized concurrently by many different tasks. For example, in the CA 1 Tape Management system, many different processes may discover the scratch tape subpool running out of tapes. You would only want one request opened for that condition. The first process to encounter the condition would open the request ticket and all subsequent redundant request tickets would be rejected until the time interval from MINTIME expires.
Action:
No action is required.
Reason:
Each product event member may contain the MAXCOUNT specification in the form of MAXCOUNT=n. This is a throttling mechanism to prevent a flood of Service Desk request tickets from being opened when a given event may be recognized concurrently by many different tasks. You may only want one or two request tickets opened for a specific event. Each occurrence of a given event in a given system increments the count for that event. Once the count reaches the MAXCOUNT value, all subsequent request tickets are rejected. The only way to reset the event counters is to remove the associated Product Event Table with either the REMOVE PRODUCT=prodid command or the SHUTDOWN command, and then use the DEFINE PRODUCT=prodid command to rebuild the Product Event Table.
Action:
No action is required.
Reason:
The entire CAISDI/els interface has been disabled. This can only happen if CA technicians are currently debugging the Event Control Structure.
Action:
Retry the request later.
Reason:
The Product Event Table for this product is currently in a disabled state. This is the result of using the DISABLE PRODUCT=prodid command.
Action:
To enable the Product Event Table, use the ENABLE PRODUCT=prodid command.
Reason:
The CAISDI/els interface module is not in the link list or STEPLIB.
Action:
Ensure the CAISDI/els component has been installed on the current system.
Reason:
The CAISDI/els Interface Controller has not processed any DEFINE commands on this system since the IPL. The first DEFINE command successfully processed causes the Event Control Structure to be initialized on the system where it was run. The Event Anchor Block remains resident for the duration of the IPL, even after a SHUTDOWN command has been processed.
Action:
Run the CAISDI/els Interface Controller with a DEFINE command for the product whose event you want to trigger.
Reason:
The Event Control Structure is in place, so the CAISDI/els Interface Controller has been run with at least one DEFINE command. However, either the DEFINE PRODUCT=prodid command was never run, or a subsequent REMOVE PRODUCT=prodid command was run.
Action:
Run the CAISDI/els Interface Controller with a DEFINE PRODUCT=prodid command for the product whose event you want to trigger.
Reason:
The Event Control Structure and the Product Event Table is in place, so the CAISDI/els Interface Controller has been run with the DEFINE PRODUCT=prodid command. However, no event library member whose name begins with eventid was processed. Event member names are comprised of a six-character event code followed by a two-character language code.
Action:
Review the processing log from the DEFINE PRODUCT=prodid command to see a complete list of event members that were processed.
Reason:
The LOAD for the CAISDI/soap API module, CAS0PCLI, failed. This module must be in the linklist.
Action:
Ensure the CAISDI/soap component is installed in the system where this job is running. The SOAP address space does not need to be running on this system, but the API module must be available through the linklist.
Reason:
The CAISDI/soap API passed back unexpected failure codes.
Displays the return code that describes the general severity of the error.
Displays the reason code that describes the problem.
Action:
See CAISDI Return Codes and Reason Codes in the chapter "Codes."
Reason:
The CAISDI/els component requires space to build various structures and buffers. This space will be released when this process terminates. This storage is not retained for purposes of keeping the interface active.
Action:
Increase the region size or specify REGION=0M, and run the job again.
Reason:
CAISDI/els received every indication that the Service Desk request was opened correctly, but the request number of the newly opened request could not be found in the response packet from the Service Desk.
Action:
Verify the release levels of both the CAISDI/els component and the CA Service Desk server.
Reason:
This message logs out error conditions that should never occur. If they do, the modules themselves have become corrupted or improper maintenance has been applied.
Action:
Ensure the current levels of both CAISDI/els and CAISDI/soap are installed and all maintenance has been applied.
Reason:
This message logs out error conditions that are not recognized at all. The modules themselves have become corrupted or improper maintenance has been applied.
Action:
Ensure the current levels of both CAISDI/els and CAISDI/soap are installed and all maintenance has been applied.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |