Reason:
The action indicated by P1 is not supported by procedure P2 which was invoked to perform it.
System Action:
The action is not performed.
User Action:
Amend the procedure P2 to support this action type.
Reason:
An APPC error occurred whilst communicating with the remote domain P4 . The APPC verb that encountered the error was P1 , the return code set by the verb was P2 and the feedback code set by the verb was P3 . If a sysmsg was set it will be displayed as P5 .
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
The Alert Monitor's proxy agent appc transaction $AMAGTPZ encountered a message that it did not expect. The message is P1.
System Action:
Processing continues.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The Alert Monitor proxy agent appc transaction ($AMAGTPZ) received some unexpected data whilst communicating with the remote domain P4. The APPC verb that encountered the error was P1, the what received indicator had a value of P2, the conversation state was P3.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
An APPC error occurred whilst communicating with the remote domain P4. The APPC verb that encountered the error was P1, the return code set by the verb was P2 and the feedback code set by the verb was P3. If a sysmsg was set it will be displayed as P5.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
The Alert Monitor's agent appc transaction $AMAGTTZ (which is started by a remote SOLVE system) encountered a message that it did not expect. The message is P1.
System Action:
Processing continues.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The alert monitor agent appc transaction ($AMAGTTZ) received some unexpected data whilst communicating with the remote domain P4. The APPC verb that encountered the error was P1, the what received indicator had a value of P2, the conversation state was P3.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
The Alert Monitor's agent appc transaction ($AMAGTTZ) (which is started by a remote SOLVE system) could not queue a request to an alert monitor agent process ($AMPAGTZ).
System Action:
Processing continues.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The P1 receiver failed when issuing an EPS request.
P1 is the EPS Receiver ID.
P2 is the type of EPS request (for example, CONNECT).
P3 is the return code.
P4 is the error number.
P5 is the reason (for example, EPS UNAVAILABLE).
If possible, recovery is attempted as indicated by the next message (see also AMALRCV04, AMALRCV05, or AMALRCV06).
System Action:
The P1 receiver attempts recovery.
User Action:
If the message is not followed by a recovery message, the error is probably related to data corruption. The event is discarded, and processing continues.
If the problem cannot be resolved, contact CA Support.
Reason:
The alert receiver failed due to an MDO error. The failure is identified by the following:
This failure indicates one of the following causes:
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The P1 receiver procedure is now ready to receive events using EPS Services. P1 is the EPS receiver ID.
System Action:
The region is ready to receive events from external applications.
User Action:
None.
Reason:
This message follows message AMALRCV01. P1 is the EPS receiver ID.
The recovery is attempted after an EPS request failure (see AMALRCV01).
System Action:
Reconnection to EPS is attempted.
User Action:
See message AMALRCV01 for the EPS return and error codes.
If the problem cannot be resolved, contact CA Support.
Reason:
This message follows message AMALRCV01. The required EPS services are currently unavailable. P1 events processing will resume as soon as EPS services are restored. P1 is the EPS receiver ID.
System Action:
Wait for EPS to become available.
User Action:
Ensure that an SSI region is currently active with its event processor is enabled.
Enter the /PARMS shortcut, and check the SSI parameter group. Ensure that the Sub-System Interface ID field contains the correct ID.
Reason:
This message follows message AMALRCV01. P1 is the EPS receiver ID.
An unrecoverable error occurred during an EPS request (see message AMALRCV01). P1 event processing has stopped.
System Action:
The P1 receiver is terminated.
User Action:
Contact CA Support.
Reason:
A P1 request was received but rejected because the SERIALNM field of the incoming MDO was blank. The SERIALNM field is used to uniquely identify the ALERT that is to have action P1 performed on it.
System Action:
Request rejected.
User Action:
Ensure the SERIALNM field in the MDO contains a unique alert identifier.
Reason:
A P1 request was received but rejected because the SERIALNM field of the incoming MDO contained a value that the Alert Receiver was unable to match to any value in the internal Alert Identifier table ($AMALRCV)
System Action:
Request rejected.
User Action:
Ensure the SERIALNM field in the MDO contains a value that had previously been used to CREATE an alert.
Reason:
The Alert Receiver has successfully registered application P1 with a description of P2 to the Alert Monitor. This application is now able to raise alerts.
System Action:
The application is registered with the Alert Monitor and is able to raise alerts using the Alert Receiver.
User Action:
None.
Reason:
The Alert Receiver has received a request to register an application but the field identified by P1 was missing. The value of P1 may be APPLID or DESCRIPTION.
System Action:
The request is rejected.
User Action:
Ensure both APPLID and DESCRIPTION are specified for a registration request.
Reason:
The P1 Receiver cannot run on an operating system identified by P2.
System Action:
The P1 receiver is terminated.
User Action:
None.
Reason:
The Alert Monitor attempted to call back an application to process an automated action for an alert, but an error was encountered loading the application's OML call-back package. The procedure being loaded was P1 which was in the package P2. The OML error code was P3.
System Action:
Processing of the automated action for the alert is terminated.
User Action:
Determine why the application package is not loading by referring to messages in the log.
Reason:
The Alert Monitor attempted to call back an application to process an automated action for an alert, but the application returned an error. The application procedure that was called was P1 which was in the OML package P2. The return code set by the application was P3.
System Action:
None.
User Action:
Refer to the log for the message that was returned by the application.
Reason:
The Alert Monitor attempted to call back an application to process an automated action for an alert, but the application's call-back package did not contain a procedure for processing the action. The action being performed was P1 for the alert class P2. The application OML package that was called was P3.
System Action:
Processing of the automated action for the alert is terminated.
User Action:
Implement the procedure in the application's call-back package to process the action.
Reason:
The automated action P1 was removed from the list of defined actions.
System Action:
None.
User Action:
None.
Reason:
An error occurred whilst attempting to remove the automated action P1. P2 is the feedback code from &VARTABLE DELETE.
System Action:
None.
User Action:
FDBK value of 4 indicates that the action has already been deleted. For other FDBK values, ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
If you cannot resolve the problem, contact Technical Support at http://ca.com/support.
Reason:
The selection list service procedure $AMAREDL does not support the calltype P1 from the selection list manager.
System Action:
Selection list terminates.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
When asked to select an action you pressed F3=Exit instead of selecting an action. The add request is cancelled.
System Action:
None.
User Action:
Retry the add request, selecting an action from the list of available actions.
Reason:
You attempted to add an automated action, but another action could not be added as there are too many actions already.
System Action:
None.
User Action:
None.
Reason:
A request to add or update a list of actions has been canceled.
System Action:
Current changes have been abandoned.
User Action:
None.
Reason:
You have attempted to perform an operation which was to be routed to a remote system but the link to the remote system with a domain ID of P1 was unavailable.
System Action:
Request rejected.
User Action:
Determine why the link to the remote system was not available. Issue a SHOW LINKS command to see the status of links. Issue a SHOW DOMAINS command to see the status of domains that are known to the local system. A LINK START command may be required.
Reason:
You have attempted to perform an operation which was to be routed to a remote system, but the userid P1 was not defined on the remote system that has a domain ID of P2.
System Action:
Request rejected.
User Action:
Contact the administrator for the remote system and arrange for your userid to be defined. To see a list of domain IDs and their details issue a SHOW DOMAINS command. The output from this command will help identify the remote system.
Reason:
The selection list service procedure $AMAVACL does not support the calltype P1 from the selection list manager.
System Action:
Selection list terminates.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The creation of an Alert in the Alert Monitor was rejected because the passed alert did not have all the mandatory attributes set.
System Action:
Create of alert rejected.
User Action:
Make sure the Alert MDO has all the mandatory attributes set in it before you call $AMCALL:Alert_Create to create the alert.
Reason:
Whilst processing an alert create request, the Alert Monitor attempted to start the Alert Monitor Alert Receiver (which is a long running server process). An error occurred when attempting to start the server. The return code set by the &APPC START verb is P1.
System Action:
Create of alert rejected.
User Action:
Refer to the log for any related error messages.
Reason:
The creation of an Alert in the Alert Monitor was rejected because the the alert server process that the alert is queued to has reached its queue limit (32767).
System Action:
Creation of alert rejected.
User Action:
Investigate the reasons for excessive alert creation.
Reason:
The creation of an Alert in the Alert Monitor was rejected because the passed alert MDO exceeded the maximum allowable size.
System Action:
Create of alert rejected.
User Action:
Make sure the Alert MDO does not exceed the maximum MDO size.
Reason:
The creation of an Alert in the Alert Monitor was rejected because the alert server process was not running (even after the alert create processing attempted to automatically start it).
System Action:
Create of alert rejected.
User Action:
Check the log for any related error messages. Contact your Systems Administrator.
Reason:
The request of type P1 to $AMCALL failed because the attribute P2 had an invalid value of P3 .
System Action:
None.
User Action:
Contact your Systems Administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An error occurred while manipulating an NCL VARTABLE in the procedure $AMCALL. P1 is the vartable Identifier, P2 is the function being performed and P3 is the feedback code set by the vartable verb.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
You have attempted to edit the automated actions in an alert rule but the procedure which invoked $AMCALL:AlertRule_Edit did not set all of the mandatory parameters in the &$AMALERTRULE MDO.
System Action:
Request fails.
User Action:
Contact your Systems Administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An application has attempted to create an alert, but the alert MDO that it shared with $AMCALL:AlertCreate did not have all the mandatory fields set in it.
System Action:
Request fails.
User Action:
Contact your Systems Administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
You have attempted to access alert information from a remote system, but the link to the remote system is currently unavailable.
System Action:
Request rejected.
User Action:
Check that the remote system is running and that the link to the remote system is active. Use the SHOW LINKS command to see the status of the INMC links.
Reason:
The action P2 was not performed because the required attribute P1 was not set.
System Action:
The action is not performed.
User Action:
Make sure the MDO has all the mandatory attributes set in it before you attempt to perform the action again.
Reason:
The request of type P1 failed because the attribute P2 had an invalid value of P3 .
System Action:
The action is not performed.
User Action:
Ensure that all attributes are correctly set before retrying the action.
Reason:
You requested resource history for an alert that does not have the resource field set. You can only get resource history for alerts that have the resource field set.
System Action:
None.
User Action:
None.
Reason:
The file action P1 failed, the file return code was P2. If applicable, P3 is the key value and P4 is the specific VSAM error code.
System Action:
The action is not performed.
User Action:
Determine the cause of the error and retry.
Reason:
The field highlighted in error is a required field but no value was entered.
System Action:
None.
User Action:
Enter a value for the field.
Reason:
You cannot use the alert monitor trouble ticket interface because it has not yet been configured.
System Action:
None.
User Action:
The system administrator should configure the trouble ticket interface. Enter the /ALTTI shortcut to start configuring the interface.
Reason:
The configured trouble ticket interface type is P1 but it is not supported on this system.
System Action:
None.
User Action:
Contact your System Administrator.
Reason:
The trouble ticket user exit routine P1 stopped the creation of a trouble ticket from the alert monitor by setting a non-zero return code.
System Action:
None.
User Action:
None.
Reason:
The trouble ticket request was sent by e-mail to the address P1 . This message indicates that the request was queued to the MVS based SMTP agent. It does not guarantee that the message was received by the address.
System Action:
None.
User Action:
None.
Reason:
The alert is now being tracked by the userid P1. This is due to the user P1 using the T=Track selection list option against the alert on the list of alerts.
System Action:
None.
User Action:
None.
Reason:
The alert is no longer being tracked. This is due to the user who was tracking the alert using the T=Track option against the alert on the list of alerts having turned tracking off.
System Action:
None.
User Action:
None.
Reason:
The alert's severity has been changed from the level P1 to the level
P3 by the userId P3 .
System Action:
None.
User Action:
None.
Reason:
The value entered for the user ID is invalid.
System Action:
None.
User Action:
Correct the value entered and retry the operation.
Reason:
The value entered for the procedure name is invalid.
System Action:
None.
User Action:
Correct the value entered and retry the operation.
Reason:
The value entered for the command name is invalid.
System Action:
None.
User Action:
Correct the value entered and retry the operation.
Reason:
The call to the user exit procedure P1 for the email trouble ticket interface failed because the procedure could not be found in the procedure library.
System Action:
No further calls to the procedure will be made while creating the current trouble ticket but trouble ticket creation will continue.
User Action:
Ensure the correct name is specified for the exit procedure in the trouble ticket definition or remove the procedure name.
Reason:
The call to the user exit procedure P1 for the email trouble ticket interface failed. P2 is the error number associated with the cause of the failure. P3 contains the ID of an error message that may provide a more detailed explanation of the failure.
System Action:
Trouble Ticket processing continues.
User Action:
Correct the indicated error or remove the procedure name from the User Exit field.
Reason:
The call to the user specified procedure P1 for the Custom Trouble Ticket interface failed because the procedure could not be found in the procedure library.
System Action:
The trouble ticket creation is terminated.
User Action:
Ensure the correct name is specified for the procedure in the trouble ticket interface definition.
Reason:
The call to the user specified procedure P1 for the Custom Trouble Ticket interface failed. P2 is the error number associated with the cause of the failure. P3 contains the ID of an error message that may provide a more detailed explanation of the failure.
System Action:
Generation of the Trouble Ticket is terminated.
User Action:
Correct the indicated error in the procedure.
Reason:
A request has been made to create a Service Desk record that corresponds to this alert.
This message indicates that this region sent the request to the external Web services SOAP client CALSDI/soap. It does not guarantee that the request was received by the Service Desk server, or that a Service Desk record has been created.
System Action:
Internal processing of this request commences. This processing uses the CA Common Services for z/OS components CAICCI and CAISDI/soap to communicate using HTTP(S)/IP, and invoke a Web service provided by the Service Desk server.
User Action:
None.
When all processing and communication completes successfully, a Service Desk record corresponding to this alert should be created.
If the Service Desk server supports the ITIL user interface, an Incident record is created; otherwise, a Request record is created.
Reason:
CA Service Desk Request/Incident record P1 has been created by one of the following:
This alert has a trouble ticket type of SERVICEDESK. P2 is the Service Desk server that created this record.
If the Service Desk server supports the ITIL user interface, an Incident record is created; otherwise, a Request record is created.
System Action:
None.
User Action:
This record is now accessible to CA Service Desk users.
Authorized users can log in to the CA Service Desk client application on this server and administer this record.
By default, this record appears as an assigned Request or Incident record with an assignee and user of System_NetMaster_User (Your Service Desk Administrator can change these values.)
Reason:
The severity level of the alert has not changed because it is already set to level P1 .
System Action:
None.
User Action:
None.
Reason:
An attempt was made to create a CA Service Desk record from a CA NetMaster alert, but the attempt failed due to an error condition in the CA NetMaster to CA Service Desk interface.
This interface involves multiple components, including the CA Common Services for z/OS 'CAICCI' and 'CAISDI/soap' SOAP Client components. These combine to communicate from the z/OS systems using HTTP/s to the CA Service Desk server.
Specific error details are written to the activity log.
Some likely causes of these failures include the following:
System Action:
No CA Service Desk record is created.
User Action:
Examine the activity log for further error details in message BASOAP03.
Examine the output of the CA Common Services for z/OS CAISDI/soap SOAP Client started task.
To diagnose these conditions, you may need help from your Systems Programmer (who implemented CAISDI/soap) and your CA Service Desk Administrator.
For more information, see the Service Desk Integration Guide, and the CA Common Services for z/OS Message Guide.
Reason:
The P1 email address cannot be resolved.
System Action:
The trouble ticket email is not sent.
User Action:
Ensure that the values specified in the following panels are correct:
If you use an exit procedure, ensure that all values and code are correct.
Correct any errors.
Reason:
An error occurred whilst attempting to add an alert to the active alerts vartable. The feedback code set by the vartable add verb is P1.
System Action:
Alert creation rejected.
User Action:
Check the log for any related error messages. Contact your Systems Administrator.
Reason:
A call was made to the Alert Monitor to set the attributes of an alert, but the alert object that was passed on the set request contained one or more attributes that cannot be set. The first attribute found in the request that cannot be set was P1.
System Action:
Set of alert rejected.
User Action:
Check the log for any related error messages. Contact your Systems Administrator.
Reason:
An error occurred whilst starting the alert rule processor. P1 is a description of the error.
System Action:
No rule processing performed for alert.
User Action:
Check the log for any related error messages. Contact your Systems Administrator.
Reason:
The Alert Monitor attempted to process an Alert or a user request but could not proceed because it needed to call back the application id P1 which currently is not registered with the alert monitor.
System Action:
None.
User Action:
Determine why the application has not registered with the Alert Monitor.
Reason:
The Alert Monitor attempted to call back an application that has registered with the alert monitor, but an error was encountered loading the call-back package. The procedure being loaded was P1 which was in the package P2. The OML error code was P3. This message is written to the log.
System Action:
None.
User Action:
Determine why the application package is not loading by referring to messages in the log.
Reason:
The Alert Monitor attempted to call back an application that has registered with the alert monitor, but the application returned an error. The application procedure that was called was P1 which in the package P2. The return code set by the application was P3.
System Action:
None.
User Action:
Refer to the log for the message that was returned by the application.
Reason:
The Alert Monitor attempted to call back an application that has registered with the alert monitor, but the application had not specified a call-back package when it registered with the alert monitor. The applId was P1 .
System Action:
None.
User Action:
Determine why the application did not specify a call-back package when it registered.
Reason:
An error occurred while manipulating an NCL VARTABLE in the procedure $AMDBMS. P1 is the vartable Identifier, P2 is the function being performed, P3 is the feedback code set by the vartable verb and P4 is the vartable key being accessed.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
The Alert Monitor called back an application that has registered with the alert monitor, but the application's call-back procedure P1 in the package P2 returned an object that was the same as the object that was shared with it (the application call-back procedure did not set any data in the object mdo). The application call-back procedure also set a return code of 0.
System Action:
None.
User Action:
Determine why the application package is not setting data in the object that is returned to the alert monitor.
Reason:
The Alert Monitor successfully closed an active alert. The alert will now only be in the alert history file.
System Action:
None.
User Action:
None.
Reason:
This message is placed in the alert annotation text and identifies that the user P1 closed the alert.
System Action:
None.
User Action:
None.
Reason:
This message is placed in the alert annotation text and identifies that the alert was cleared by another alert. To find the time that the alert was cleared, look at the alert closed time.
System Action:
None.
User Action:
None.
Reason:
This message is placed in the alert annotation text and identifies that the alert was replaced by another alert. To find the time that the alert was replaced, look at the alert closed time.
System Action:
None.
User Action:
None.
Reason:
The selected alert does not exist.
System Action:
None.
User Action:
None.
Reason:
The action P1 is not supported by the application Id P2 for the alert class P3 or any of its parent alert classes.
System Action:
None.
User Action:
Check the log for other errors as this error may be due to an OML call-back package not being able to load (compile error) or it could be due to no call-back packages specifying they support the action.
Reason:
An error occurred attempting to start the Alert Monitor history NDB.
P1 is the message returned from the NDB START command.
System Action:
None.
User Action:
Refer to the AMDBMS17 message(s) in the log which describe the NDB return code set in the message from the NDB start command.
Reason:
This message contains text that is an interpretation of an NDB return code. This message follows a AMDBMS16 message.
P1 contains text from the NETINFO database for the NDB return code.
System Action:
None.
User Action:
Refer to the AMDBMS16 message in the log which contains the message returned from the NDB start command.
Reason:
A response from the command P1 was not received within an adequate amount of time by the procedure $AMDBMS.
System Action:
Could not complete requested function.
User Action:
Determine why there is no response to the P1 command and correct problem. Check for the message AMDBMS19 in the log which will contain the last message received. If no messages were received, this message will not be in the log.
Reason:
This message is written to the log as a result of a command not completing within an adequate amount of time. P1 is the text of the last message that was received before the command timed-out.
System Action:
Command times out.
User Action:
Determine why the command is timing out. Also look for the message AMDBMS19 in the log which identifies the command that was issued.
Reason:
The Alert Monitor procedure $AMDBMS was unable to open the Alert History NDB. The name of the NDB being accessed was P1 and the NDB return code was P2 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using the appendix titled NDB Response Codes in the Network Control Language Programmer Guide.
Reason:
The Alert Monitor procedure $AMDBMS was unable to add an Alert to the Alert History NDB. The name of the NDB being accessed was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
The Alert Monitor procedure $AMDBMS was unable to close the Alert History NDB. The name of the NDB being accessed was P1 and the NDB return code was P2 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
The Alert Monitor procedure $AMDBMS was unable to add a field definition to the History NDB. The name of the NDB being accessed was P1 , the NDB return code was P2 and the field name was P3 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
The Alert Monitor procedure $AMDBMS was unable to define a format to the History NDB. The name of the NDB being accessed was P1 , the NDB return code was P2 and the format name was P3 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
The Alert Monitor procedure $AMDBMS was unable to update an Alert in the Alert History NDB. The name of the NDB being accessed was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
The alert that you selected to close has already been closed.
System Action:
None.
User Action:
None.
Reason:
The Alert Monitor procedure $AMDBMS was unable to get an Alert from the Alert History NDB. The name of the NDB being accessed was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
The Alert Monitor procedure $AMDBMS was unable to delete an Alert from the Alert History NDB. The name of the NDB being accessed was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Processing is terminated.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
An error occurred whilst scanning the Alert History NDB for records. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
None.
User Action:
Interpret the NDB return codes using the appendix titled NDB Response Codes in the NCL Programmer Guide.
Reason:
The Alert Monitor history file cleanup processing has ended and deleted
P1 alerts from the history file.
System Action:
None.
User Action:
None.
Reason:
The Alert History parameters defintion cannot be updated because of an unknown file error. P1 is the VSAM feedback code.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your Systems Adminstrator.
Reason:
The current function cannot complete because the VFS file is opened for read only access and cannot be written to.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your Systems Adminstrator.
Reason:
The current function cannot complete because the VFS file cannot be accessed.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your Systems Adminstrator.
Reason:
The Alert History parameters definition cannot be updated because of an unknown file error on the VFS file. P1 is the return code of the file open command.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your Systems Administrator.
Reason:
The Alert History parameters definition has been successfully updated and saved.
System Action:
None.
User Action:
None.
Reason:
The Alert History parms definition cannot be updated because of an unknown file error on the VFS file. P1 is file action that failed and
P2 is the VSAM feedback code.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your Systems Administrator.
Reason:
This message follows a AMDBMS09 message and contains information that can aid the diagnosis of the problem.
P1 is the applId attribute that was returned from the AlertRule_Get call to the application call-back package.
P2 is the classId attribute that was returned from the AlertRule_Get call to the application call-back package.
P3 is the ruleId attribute that was returned from the AlertRule_Get call to the application call-back package.
This message is issued because one or more of the above attributes was not set in the &$AMAlertRule MDO by the application call-back package.
System Action:
Automated Action for an alert not processed.
User Action:
Determine why the application package is not setting data in the object that is returned to the alert monitor.
Reason:
This message is issued when an attempt is made to create an alert that is greater than 30K in size.
P1 can be ADD or UPDATE
P2 is the Application Id that attempted to add the alert
P3 is the Class Id of the alert (optional)
P4 is the resource name in the alert (optional)
You could get this message if you attempt to add an excessive amount of notes to an alert.
System Action:
If creating a new alert, the alert is discarded (not created). If updating an alert, the update will be rejected.
User Action:
Determine what is issuing such large alerts and change it so that the alert does not contain so much information.
Reason:
This message is issued if the alert history NDB is not started. This could be due to the alert history DD ALERTH was not allocated in the RUNSYSIN member for the SOLVE system.
System Action:
History information unavailable.
User Action:
Allocate the history NDB with a DDNAME of ALERTH. Once allocated issue the following command to open and start the history database:
$CAPKCAL $AMDBMS HistoryNdb_Start
Reason:
The alert history NDB is locked due to an error (such as running out of space).
System Action:
History information is not available, and alerts are not logged in history NDB.
User Action:
See the region log for any other errors that indicate why the NDB is locked. For example, in a situation where the file is full, you should see a VSAM I/O error message in the log.
To recover from a full NDB
The history NDB closes when no users are using it.
The closed NDB is unallocated from the region.
The information is restored to the redefined NDB.
Note: If you do not need to keep the records in the existing history NDB, you do not need to back up the NDB. Define a new NDB, and update the ALERTHIST parameter group with the new data set name and apply the change.
Reason:
This is an information message issued by the Alert Monitor indicating that some change has occurred to an Alert with a severity of P2 , which is not in the current window. P1 is either ABOVE or BELOW and indicates the direction in which the change is to be found.
System Action:
None.
User Action:
If it is desired to see the change which has occurred, scroll the list in the indicated direction.
Reason:
You have requested an action to be performed on an alert appearing on the Alert Monitor display, but this action is not applicable to or not supported for the type of alert selected.
System Action:
The requested action is not performed. Alert Monitor processing continues as normal.
User Action:
Check that the action code that you specified is correct. Check that you have selected the correct alert, as the actions supported depend upon the class of the alert and the application it came from.
Not all alerts support all actions. Enter a ? next to an alert to display the full list of actions available.
Reason:
You placed a ? next to an alert on the alert selection list to get a list of available actions. F3=Exit was pressed instead of selecting an action.
System Action:
You are returned to the Alert selection list.
User Action:
Redisplay the actions list by entering a ? in front of the alert and then S next to the desired action.
Reason:
You specified P1 as a column name to sort on on the SORT command but the column name is not recognized.
System Action:
Sort command rejected.
User Action:
Specify a valid column name.
Reason:
You specified P1 as a sort order for a column on the SORT command but the sort order is invalid.
System Action:
Sort command rejected.
User Action:
Specify a valid sort order. Valid values are A, ASCENDING, D and DESCENDING. For example, to sort on the severity column in decending order then issue the command SORT SEVERITY D.
Reason:
An unexpected message was received by the procedure $AMDISPL.
P1 is a message that was received.
System Action:
None.
User Action:
Check the log for any related error messages. Contact your Systems Administrator.
Reason:
You have requested to locate the first alert that has a date that is equal to the date of the record cyrrently displayed on the top of the list (by specifying '*' as the date), but since the list is empty this is not possible.
System Action:
None.
User Action:
Make sure the list has something displayed before you specify '*' as a date on the locate command.
Reason:
A request to access a specific date failed because the format of the data does not match one of the following: DD-MON-YYYY YY.DDD DD/MM/YY or MM/DD/YY (if US language code) YY/MM/DD YYMMDD YYYYMMDD = (todays date) * (the date of the record displayed on the top of the list)
System Action:
None.
User Action:
Correct the date entered to match one of the supported formats.
Reason:
The selection list service procedure $AMDISPL did not support the calltype P1 from the selection list manager.
System Action:
Selection List Terminates.
User Action:
Contact your System Administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
You have specified two dates on the DATE command indicating a start date and an end date, but the end date is not greater than the start date.
System Action:
None.
User Action:
Correct the end date entered so that it is greater than the start date. The end date is the second operand specified on the date command.
Reason:
A request to access a specific date failed because the format of the data does not match one of the following: DD-MON-YYYY YY.DDD DD/MM/YY or MM/DD/YY (if US language code) YY/MM/DD YYMMDD YYYYMMDD = (todays date) * (the date of the record displayed on the top of the list)
System Action:
None.
User Action:
Correct the date entered to match one of the supported formats.
Reason:
You have pressed F6=Hold to stop the alert monitor display from being updated. This means that any new alerts or updates to alerts will not be reflected on the alert monitor display until you press F6=Resume. Be aware that if you change the attributes of an alert such as the severity for example, the display will not be updated to indicate the new alert severity.
System Action:
None.
User Action:
None.
Reason:
You have pressed F6=Resume to resume the display of updates and new alerts. The alert monitor display will be refreshed with the current alert information.
System Action:
None.
User Action:
None.
Reason:
The Filter that you specified is not defined.
System Action:
Command ignored.
User Action:
Specify an existing Filter. (Selection list available)
Reason:
You entered the 'FILTER' command with no name specified and when the list of available filters was displayed you pressed F3=Exit instead of selecting one.
System Action:
The Filter Command is ignored.
User Action:
Select a Filter from the available Filters list by entering an S next to the desired Filter.
Reason:
The DEFINE command format is DEFINE 'command type' 'name' where 'command type' can be either FILTER or FORMAT and where name is optional.
System Action:
The DEFINE command is ignored.
User Action:
Complete the DEFINE command as specified.
Reason:
Command P1 was issued from within the Alert Monitor History Display. This command is not valid within the history display.
System Action:
None.
User Action:
Do not use this command here.
Reason:
The Specified Profile element P1 has been set to the displayed value P2
System Action:
None.
User Action:
The Alert Monitor will use the new Value for its Displays.
Reason:
The link specified, P1 is not currently known. The link may not be active or the name may be invalid.
System Action:
The History command is terminated.
User Action:
Check the Link named. The 'SHOW LINKS' command will display all Links and their status or use the 'HISTORY ?' command to get a selection list of all active Links.
Reason:
A request to monitor Alerts for a number of links was made but the links indicated are currently not contactable.
System Action:
Warning message only.
User Action:
Check the Links.
Reason:
You have requested action P1 to be performed, but this action is not supported. To update the filter or format defined in your user profile, issue the PROFILE command.
System Action:
The requested action is not performed.
User Action:
Issue the PROFILE command to update your user profile.
Reason:
No value selected from the selection list displayed.
System Action:
None.
User Action:
None.
Reason:
The current filter has a SYSTEM field expression in its definition. SYSTEM field filter expressions are not valid in Alert Monitor History. This individual expression is ignored, and the remaining filter expressions are used.
System Action:
System filter expression ignored, remaining filter expressions used.
User Action:
Use another filter if required.
Reason:
You have attempted to access alert information from a remote system, but the link to the remote system is currently unavailable.
System Action:
Request rejected.
User Action:
Check that the remote system is running and that the link to the remote system is active. Use the SHOW LINKS command to see the status of INMC links.
Reason:
A request to present a list of filters failed because there were no filters defined within the range specified.
System Action:
The request is rejected.
User Action:
New filters can be created via the DEFINE FILTER command.
Reason:
You issued a CLOSE command; however, no alerts were found that match the criteria.
System Action:
CLOSE command is ignored.
User Action:
None.
Reason:
The Alert Monitor CLOSE command successfully closed P1 active alerts.
System Action:
None.
User Action:
None.
Reason:
This is a confirmation message, which lets you confirm that you want to close the P1 alerts identified by the CLOSE command.
System Action:
None.
User Action:
Press F6 (Action) to action the CLOSE command or press F12 (Cancel) to cancel the action.
Reason:
The P1 action was cancelled at your request.
System Action:
None.
User Action:
None.
Reason:
The Alert Monitor CLOSE command successfully closed P1 active alerts but failed to close P2 alerts because of errors.
System Action:
None.
User Action:
See log for error messages on the failed attempts.
Reason:
This message appears when one or more alerts displayed on the alert monitor have a time that occurred after a backwards local time offset change on this LPAR.
Alerts are normally sorted by time. When a backward time change occurs, such as for Daylight Saving, the most recent alerts may be interleaved with earlier alerts.
To distinguish the alerts that occurred during the second time through the same local time interval, a + is displayed after the time.
System Action:
None.
User Action:
None.
Reason:
This message contains a dump of the data about to be written to the mail dataset. This message is followed by multiple AMEMAI02 messages that contain the dump data.
System Action:
None.
User Action:
Send the output to your local suport representative.
Reason:
This message follows a AMEMAI01 message in the activity log. This message contains a dump of the data about to be written to the mail dataset. The fields are:
P1 - the offset into the datastream
P2-P5 - the hexadecimal display of the ASCII characters
P6 - the EBCDIC character form of the data
System Action:
None.
User Action:
Refer to the earlier AMEMAI01 message.
Reason:
The destination type, specified by the DESTTYPE parameter, either was omitted or had an invalid value specified. The DESTTYPE parameter must be specified as one of the following values:
NMVT - Indicates that the alert is to be forwarded to the NETVALRT PPI receiver as an NMVT. This allows the alert to be processed by the SOLVE:Netmaster NEWS component, or by IBM's NetView (TME10). The format of the NMVT can be controlled by using the NMVTTYPE parameter. SNMPTRAP - Indicates that the alert is to be forwarded to an IP Host as an SNMP Trap. The host is identified by the DESTADDR, DESTPORT, and COMMNAME parameters.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
The destination address, specified by the DESTADDR parameter, was omitted. The DESTADDR parameter must take one of the following formats:
* an IP address in dotted notation, for example 123.123.123.123 * an IP host name which can be resolved by the Domain Name Server to an IP address.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
The destination address P1 is an IPv6 address; however, the SOCKETS API for the region is not enabled for IPv6.
System Action:
The command is rejected.
User Action:
Correct the operand and retry, or change the SOCKETS parameter group to use type IBMV6.
Reason:
A socket error occurred. The socket action was P1 , the return code was
P2 , the feedback code was P3 , the error number was P4 - P5 is the name of the error, and the TCPIP vendor specific error code is P6 .
System Action:
The action fails, but recovery is attempted.
User Action:
If the problem persists determine the cause from the error codes and correct the problem.
Reason:
The destination port number, specified by the DESTPORT parameter, was invalid. If specified, the DESTPORT parameter must be numeric in the range 1 to 65535. If omitted, port number 162 is used.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
The destination address, specified by the DESTADDR parameter, was entered as a host name but the name cannot be resolved to an IP address.
System Action:
The command is rejected.
User Action:
Check the following:
- the name you have specified is correct.
- the IP Interface is active
- the Domain Name Server (DNS) is active and functioning normally.
Correct and retry.
Reason:
The NMVT format type, specified by the NMVTTYPE parameter, has an invalid value. The NMVTTYPE parameter must be specified as one of the following values:
GENALERT - Indicates that the alert is to be forwarded to the NETVALRT PPI receiver as an NMVT, formatted as a Generic Alert, major vector type x'0000'. This is the default value.
OPERMSG - Indicates that the alert is to be forwarded to the NETVALRT PPI receiver as an NMVT, formatted as a Send Message to Operator NMVT, major vector type x'006F', accompanied by a Text Data major vector, type x'1300'.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
The Alert Clear option, specified by the CLEAR parameter, has an invalid value. The CLEAR parameter must be specified as one of the following values:
YES - Indicates that Alert Clear events are to be forwarded. This is the default if the operand is omitted.
NO - Indicates that Alert Clear events are not to be forwarded.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
The NMVT receiver ID, specified by the NETVALRT parameter, has an invalid value. If specified, the name must conform to PDS member name rules.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
Alerts will be forwarded to specified destination. P1 identifies the alert forwarding process. It is the NCL ID of the particular instance of the $AMEVFWD procedure.
This message forms part of a group of messages: AMEVFWD10, AMEVFWD11, AMEVFWD12, AMEVFWD13, and AMEVFWD17.
System Action:
The group of messages is written to the activity log. Alerts that match the criteria outlined in AMEVFWD13 will be reformatted and sent to the specified destination.
User Action:
If the particular process needs to be stopped, enter the following command:
FLUSH ID=n
where n is P1 .
Reason:
Alerts will be forwarded as NMVT generic alerts to the NetView region by using the NETVALRT PPI receiver ID.
This message forms part of a group of messages: AMEVFWD10, AMEVFWD11, AMEVFWD12, AMEVFWD13, and AMEVFWD17.
System Action:
The group of messages is written to the activity log. Alerts that match the criteria outlined in AMEVFWD13 will be reformatted and sent to the specified destination.
User Action:
None.
Reason:
Alerts will be forwarded as SNMP traps to the following destination:
P1 is the address of the destination.
P2 is the port number.
P3 is the community name.
This message forms part of a group of messages: AMEVFWD10, AMEVFWD11, AMEVFWD12, AMEVFWD13, and AMEVFWD17.
System Action:
The group of messages is written to the activity log. Alerts that match the criteria outlined in AMEVFWD13 will be reformatted and sent to the specified destination.
User Action:
None.
Reason:
P1 displays the criteria that determine whether an alert will be forwarded. The criteria consist of a string of parameters. For example, APPL=XYZ indicates that only alerts from the XYZ application are forwarded. If the value of a parameter is *all*, no filtering is applied to that parameter.
This message forms part of a group of messages: AMEVFWD10, AMEVFWD11, AMEVFWD12, AMEVFWD13, and AMEVFWD17.
System Action:
The group of messages is written to the activity log. Alerts that match the criteria outlined in AMEVFWD13 will be reformatted and sent to the specified destination.
User Action:
None.
Reason:
An invalid value was specified for the SEND parameter. Valid values are:
UDP - alerts will be forwarded to the specified host using the UDP protocol. This is the default.
WRITE - alerts will be written to the response queue of the parent process. If this method is used, $AMEVFWD must be invoked by using INTCMD.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
An invalid value was specified for the ALERTS parameter. Valid values are:
NEW - Only new alerts are forwarded as they occur. This is the default if the operand is omitted.
ALL - All current alerts are forwarded, followed by any new alerts as they occur.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
The Inactive TCP/IP Interface action option, specified by the IPINACT parameter, has an invalid value. The parameter must be specified as one of the following values:
WAIT - Indicates that alert forwarding is to be suspended until the TCP/IP interface becomes active. This is the default if the operand is omitted.
IGNORE - Indicates that alerts will not be forwarded while the TCP/IP interface is not active.
System Action:
The command is rejected.
User Action:
Correct the operand and retry.
Reason:
Alerts will be passed as messages to CA NSM. P1 identifies the destination.
This message forms part of a group of messages: AMEVFWD10, AMEVFWD11, AMEVFWD12, AMEVFWD13, and AMEVFWD17.
System Action:
The group of messages is written to the activity log. Alerts that match the criteria outlined in AMEVFWD13 will be reformatted and sent to the specified destination.
User Action:
None.
Reason:
Alert forwarding using the CA NSM API received a non-zero return code.
Return code values are:
4 ENF not active.
8 Error in ENF processing.
16 Error in EMWTO parameter list.
System Action:
This message will be logged once on first failure. Message AMEVFWD19 will be logged if alert forwarding to CA NSM recovers.
User Action:
Check that CA NSM has been installed. If necessary, contact Technical Support.
Reason:
Alert forwarding using the CA NSM API received a zero return code following prior failures. The interface is now operational.
System Action:
None.
User Action:
None.
Reason:
A CA Service Desk Request will be created for every alert passing the associated filter criteria.
P1 is the URL of the Web Services definitions on the CA Service
Desk server.
P2 is the CCI SYSID of the CCI system that will locate and pass requests to the CAISDI/soap SOAP Client started task.
P3 is the request format: HTML (default) or TEXT
The Login, CreateRequest and Logout, Web Services are invoked. A Service Desk Request Number is returned and placed in the alert.
System Action:
Alerts that match the criteria outlined in AMEVFWD13 are reformatted and sent to the specified CA Service Desk server.
User Action:
Requests, after they are opened, are accessible to CA Service Desk users.
Authorized users can log in to the CA Service Desk application and administer the requests.
By default, these requests appear as 'assigned' requests, with an assignee and end user of System_NetMaster_User. (Your Service Desk Administrator may change these values.)
Reason:
Alert Forwarding as NMVTs has been requested (EXEC $AMEVFWD DESTTYPE=NMVT) but an attempt to send an alert failed with the indicated feedback code ( P1 ). This is translated as a failure reason ( P2 ).
System Action:
The alert is not forwarded but processing continues.
User Action:
Check the feedback/reason.
If the reason is shown as 'Internal Error', you should contact your product supplier, providing the exact text of the message.
Other reasons indicate a usage error as follows:
* NETVALRT Receiver not defined (FDBK=26) There is no (SOLVE, NetView, or other) NETVALRT PPI Receive process active in this LPAR.
For NetMaster you should ensure that procedure $NWPPIAR is running in a background region for the NetMaster system in this LPAR.
For TME 10 NetView you should ensure that the CNMCALRT task is defined and active.
* NETVALRT Receiver queue full (FDBK=35) The NETVALRT PPI Receive process is defined to the system, that is, was active since the last IPL. However, the current state of the process is one of the following:
- Inactive, and its receive queue limit has been reached. (See the explanation for NETVALRT Receiver not defined, above.)
- Active, but is not emptying the queue at a fast enough rate.
To display the receiver queues:
- For NetMaster, send the SHOW PPIUSERS command to the SOLVE SSI started task which owns the PPI. For example, from OCS: SYSCMD F SOLVESSI,SHOW PPIUSERS
- For TME 10 NetView, issue the DISPPI command. For example, from OCS: SYSCMD F TMESSI,DSIPPI BUFQ ALL from a NetView terminal: DSIPPI BUFQ ALL
* PPI is not active (FDBK=24) PPI has not been started. Ensure that the PPI started task is running.
* Storage shortage (FDBK=32) There is a storage shortage either in this domain or in the PPI domain. Other messages in the relevant domain will indicate which domain has the storage shortage.
Reason:
Alert Forwarding as NMVTs has been requested (EXEC $AMEVFWD DESTTYPE=NMVT) but an attempt to send an alert failed with the indicated feedback code ( P1 ). This is translated as a failure reason ( P2 ). The PPI Receiver ID ( P3 ) is also shown.
System Action:
The alert is not forwarded but processing continues.
User Action:
Check the feedback/reason.
If the reason is shown as 'Internal Error', you should contact your product supplier, providing the exact text of the message.
Other reasons indicate a usage error as follows:
* NETVALRT Receiver not defined (FDBK=26) There is no (SOLVE, NetView, or other) NETVALRT PPI Receive process active in this LPAR.
For NetMaster for SNA you should ensure that procedure $NWPPIAR is running in a background region for the NetMaster for SNA system in this LPAR.
For TME 10 NetView you should ensure that the CNMCALRT task is defined and active.
* NETVALRT Receiver queue full (FDBK=35) The NETVALRT PPI Receive process is defined to the system, that is, was active since the last IPL. However, the current state of the process is one of the following:
- Inactive, and its receive queue limit has been reached. (See the explanation for NETVALRT Receiver not defined, above.)
- Active, but is not emptying the queue at a fast enough rate.
To display the receiver queues:
- For NetMaster for SNA, send the SHOW PPIUSERS command to the SOLVE SSI started task which owns the PPI. For example, from OCS: SYSCMD F SOLVESSI,SHOW PPIUSERS
- For TME 10 NetView, issue the DISPPI command. For example, from OCS: SYSCMD F TMESSI,DSIPPI BUFQ ALL from a NetView terminal: DSIPPI BUFQ ALL
* PPI is not active (FDBK=24) PPI has not been started. Ensure that the PPI started task is running.
* Storage shortage (FDBK=32) There is a storage shortage either in this domain or in the PPI domain. Other messages in the relevant domain will indicate which domain has the storage shortage.
Reason:
An attempt was made to create a CA Service Desk Request from a CA NetMaster alert, but the attempt failed due to an error condition in the CA NetMaster to CA Service Desk interface.
This interface involves multiple components, including the CA Common Services for z/OS 'CAICCI' and 'CAISDI/soap' SOAP Client components. These combine to communicate from the z/OS systems using HTTPs to the CA Service Desk server.
Specific error details are written to the activity log.
Some likely causes of these failures include the following:
System Action:
This message is logged once at the first failure. Message AMEVFWD24 is logged if alert forwarding to CA Service Desk recovers.
User Action:
Examine the activity log for further error details in message BASOAP03.
Examine the output of the CA Common Services for z/OS CAISDI/soap SOAP Client started task.
To diagnose these conditions, you may need help from your Systems Programmer (who implemented CAISDI/soap) and your CA Service Desk Administrator.
For more information, see the Service Desk Integration Guide, and the CA Common Services for z/OS Message Guide.
Reason:
Alert forwarding to CA Service Desk received a zero return code following prior failures. The interface is now operational.
System Action:
None.
User Action:
Use the CA Service Desk client interface to administer the Service Desk requests.
Reason:
The identified CA Service Desk request has been created by forwarding an alert to a destination type of SERVICEDESK.
P2 is the CA Service Desk server on which this request was created.
System Action:
None.
User Action:
This request is now accessible to CA Service Desk users.
Authorized users can log in to the CA Service Desk application on the indicated server and administer this request.
By default, this request appears as an assigned request, with an assignee and user of System_NetMaster_User. (Your Service Desk Administrator may change this default.)
Reason:
An alert forwarding process is already active for the destination. The forwarding type is P1 and the destination details are described by P2 .
System Action:
This alert forwarding process terminates.
User Action:
Check the $NM ALERTS parameter group to ensure that duplicate details are not present.
Reason:
An alert forwarding process was started with an invalid parameter value.
p1 identifies the parameter.
p2 is the value of the parameter.
System Action:
This alert forwarding process terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
This message is issued when an alert has arrived which needs to be forwarded as an SNMP Trap using UDP, but the TCP/IP interface is not active.
The Process ID ( P1 ) is the NCLID of the particular instance of procedure $AMEVFWD that has been suspended. This relates to the group of messages, headed by AMEVFWD10, that were written to the log when the process was started.
System Action:
The process is suspended until the TCP/IP interface becomes active. When the process is resumed, message AMEVFWD32 is issued.
User Action:
If the particular process needs to be stopped, use the following SOLVE command:
FLUSH ID=nnnnnn
where nnnnnn is the process ID ( P1 ) in this message.
Reason:
This message is issued when alert forwarding has been resumed after it was previously suspended.
The Process ID ( P1 ) is the NCLID of the particular instance of procedure $AMEVFWD that had been suspended. This relates to message AMEVFWD31 that was written when the process was suspended.
System Action:
Alert forwarding for this process continues.
User Action:
None.
Reason:
The number of alert history records waiting to be processed by the alert history listener exceeded the NMIQLIM setting. All records exceeding the limit are discarded.
System Action:
The listener continues processing. Lost data cannot be accumulated and subsequent details may be inaccurate.
User Action:
Investigate why the message build up occurred.
If you are collecting history data in a very large network, you may have reached maximum NMIQLIM value. Consider redesigning your application or contact Technical Support.
Reason:
The alert history listener has started to receive and log history data.
System Action:
Alert history logging commences.
User Action:
None.
Reason:
The call to the procedure failed because the Keyword identified by P1 had an invalid value, identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your Systems Administrator.
Reason:
The indicated field must be completed.
System Action:
The required field is highlighted.
User Action:
Specify a value in the indicated field.
Reason:
P1 displays the criteria that determine whether an alert is forwarded. The criteria consist of a string of parameters. For example, APPL=XYZ indicates that alerts from the XYZ application only are forwarded. If the value of a parameter is *all*, no filtering is applied to that parameter.
See the alert forwarding messages that follow: AMEVFWD10, AMEVFWD11,
System Action:
The group of messages is written to the activity log. Alerts that match the displayed criteria are reformatted and sent to the specified
User Action:
Reason:
The destination address, specified in the Dest Address field, was entered as a host name, but the name cannot be resolved to an IP
System Action:
User Action:
Check the following:
- The name you have specified is correct
- The IP interface is active
- The Domain Name Server (DNS) is active and functioning normally
Reason:
The destination address specified in the Dest Address field is entered as an IPv6 address; however, the sockets API set by the SOCKETS parameter group is not enabled for IPv6 support.
System Action:
The field is set in error.
User Action:
Choose an IPv4 address or change the SOCKETS parameter group to use type IBMV6.
Reason:
A request to present a list of filters failed because there are no filters defined.
System Action:
The request is rejected.
User Action:
New filters can be created using the Alert Monitor Filter Definition List (/ALFILT).
Reason:
System Action:
User Action:
Specify an existing filter from the Filter List. To display the list,
Reason:
A request was made to list filters beginning with the characters P1 but
System Action:
User Action:
Reason:
System Action:
User Action:
Reason:
The destination details are the same in this entry as an earlier alert
System Action:
User Action:
Change the destination details (address, port, PPI receiver) to avoid
Reason:
You specified an invalid field separator character. The 1-byte separator should be a non-blank and can be one of the following characters:
› * + | \ ^ ; < > ? / ,
The literal delimiter character TAB is allowed and internally represented as EBCDIC X'05'.
System Action:
The field in error is highlighted.
User Action:
Specify a valid character separator.
Reason:
An IPv6 address has been entered in the URL field, but the sockets API supports IPv4 addresses only.
System Action:
The field is highlighted in error.
User Action:
Specify a host name or IPv4 address in the URL field. Alternatively, check the SOCKETS parameter group (/PARMS). For IPv6 support, the TCP/IP Software Type must specify IBMV6.
Reason:
The extraction of alert records is in progress.
System Action:
None.
User Action:
None.
Reason:
The extraction of alert records ended. The number of records written (P2) of the total extracted (P3) is indicated.
System Action:
None.
User Action:
If the number of updated records is less than the total, review the activity log to determine the error reason.
Reason:
An error occurred when a P1 command is being performed on the extract data set. P2 is the return code and, optionally, P3 describes the error condition.
System Action:
Processing terminates.
User Action:
Review the activity log to determine the cause of the error.
Note: For information about abend error conditions, see the z/OS MVS System Codes manual.
Reason:
This message is issued if the alert monitor filter definition database is not available. The DD name ( P1 ) and file open return code ( P2 ) are shown. For return code 16, an additional message is written to the activity log before this message.
System Action:
The filter definition information is unavailable.
User Action:
Check that the filter definition database is allocated and opened.
Reason:
This message is issued if an attempt to read a record from the alert monitor filter definition database fails. The DD name ( P1 ), file get return code ( P2 ) and file error code ( P3 ) are shown. For return code 16, an additional message is written to the activity log before this message.
System Action:
The filter definition is unavailable.
User Action:
Use the return code and feedback (error code) to determine the cause of the error.
Reason:
The specified alert monitor filter definition ( P1 ) does not exist.
System Action:
None
User Action:
None
Reason:
This message is issued if an attempt to deleta a record from the alert monitor filter definition database fails. The DD name ( P1 ), file delete return code ( P2 ) and file error code ( P3 ) are shown. For return code 16, an additional message is written to the activity log before this message.
System Action:
The filter definition is not written.
User Action:
Use the return code and feedback (error code) to determine the cause of the error.
Reason:
The only possible values are YES and NO.
System Action:
Request rejected.
User Action:
Input either YES or NO.
Reason:
The Extract DSN is not valid with the selected option.
System Action:
The field in error is highlighted.
User Action:
Clear the Extract DSN field and retry the selected option.
Reason:
The specified filter P1 is not defined.
System Action:
The field in error is highlighted.
User Action:
Enter ? to display a list of filters.
Reason:
You requested a list of filters beginning with the characters P1 but none were found.
System Action:
The field in error is highlighted.
User Action:
Enter ? to display a list of filters.
Reason:
No selection was made from the filter selection list.
System Action:
None.
User Action:
None.
Reason:
The data set name specified in the Extract DSN field does not have the required data set attributes.
System Action:
The field in error is highlighted.
User Action:
Ensure that the data set specified is allocated as a sequential data set with a variable length record format and a record length of at least 300 bytes.
Reason:
A request to present a list of filters failed because there are no filters defined.
System Action:
The request is rejected.
User Action:
New filters can be created using the Alert Monitor Filter Definition List (/ALFILT).
Reason:
You pressed the F12=Cancel function key whilst in the Add Notes panel.
System Action:
None.
User Action:
None.
Reason:
This is a message that is sent to another process by an alert monitor agent object. An MDO is usually carried with the message.
P1 is the message type and can be one of: REQUEST CHAINEDREPLY FINALREPLY EVENT ERROR
P2 is the object class and can be one of: ALERT AGENT
P3 is the operation and can be one of: GETALERTS
System Action:
None.
User Action:
None.
Reason:
An error occurred whilst starting the peer system manager ($AMPSMGZ).
P1 is a description of the error. The peer system manager is required for obtaining alerts from remote SOLVE systems.
System Action:
None.
User Action:
Check the log for any related error messages. Contact your systems administrator.
Reason:
An error occurred while manipulating an NCL VARTABLE in the procedure $AMPAGTZ. P1 is the vartable Identifier, P2 is the function being performed, P3 is the feedback code set by the vartable verb and P4 is the key specified on the verb.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
There were no alerts in the history file that matched the criteria that was supplied for building the selection list.
System Action:
List terminates.
User Action:
If you were asked to specify some form of criteria, check that it is correct and retry.
Reason:
An error occurred whilst scanning the NDB for records to build the list with. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Selection List Terminates.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
An error occurred getting a record from the NDB whilst building the list. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Selection List Terminates.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
The NDB which the list was accessing could not be opened. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Request rejected.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
An error has occurred whilst defining an NDB format for the list. The NDB return code was P1 and the NDB error information was P2 .
System Action:
The selection list terminates.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
The NDB which the list was accessing could not be closed. The name of the NDB was P1 , the NDB return code was P2 and the NDB error information was P3 .
System Action:
Request rejected.
User Action:
Interpret the NDB return codes using the NCL Programmer Guide.
Reason:
An unexpected message was received by the procedure $AMPAGTZ.
P1 is a message that was received.
System Action:
None.
User Action:
Check the log for any related error messages. Contact your systems administrator.
Reason:
A set request was queued to the alert monitor agent containing the P1 attribute which is not settable.
System Action:
Message written to Log. Processing continues.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
This message is issued if the alert history NDB is not started. This could be due to the alert history file ID not being set in ICS.
System Action:
History information unavailable.
User Action:
Set up Alert History File Specification in ICS parameter group ALERTHIST.
Reason:
This message is issued if the alert history NDB is locked due to an error (such as running out of space).
System Action:
History information unavailable and alerts will not be logged in history file.
User Action:
Refer to the log for any other errors that indicate why the database is locked. For example, in a situation where the file is full you should see a VSAM I/O error message in the log.
If the file is full, do the following:
1. Issue a UDBCTL CLOSE=ALERTH command.
2. Unallocate the ALERTH DD by issuing the following command: UNALLOC DD=ALERTH
3. Repro the NDB out.
4. Delete and redefine the existing history NDB (increase allocation if appropriate).
5. Repro the history information back in.
6. Reallocate the history file to solve by issuing the following command: ALLOC DD=ALERTH DSN=????? DISP=SHR
7. Issue the following commands to reset the locked status of the history NDB: UDBCTL OPEN=ALERTH ID=$ALERTH LSR EXIT=NO NDB START $ALERTH UNLOCK NDB STOP $ALERTH
8. Issue the following command to start the alert monitor history processing: $CAPKCAL $AMDBMS HistoryNdb_Start
Reason:
The filter that you specified is not defined.
System Action:
The command is ignored.
User Action:
Specify an existing filter. (Use the selection list.)
Reason:
This message is sent to another process by a timer started by an Alert Monitor request agent object. An MDO is not included with the message.
P1 is the message type and can be one of: REQUEST
P2 is the object class and can be one of: TIMER
P3 is the operation and can be one of: UPDATECLOCK
System Action:
None.
User Action:
None.
Reason:
There were no active alerts that matched the criteria that was supplied.
System Action:
None.
User Action:
None. Alerts matching the resource criteria will appear automatically.
Reason:
The procedure $AMPARMP failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $AMPARMP terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The command that was specified on the command line is not valid.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The automated action P1 was added to the list of actions.
System Action:
None.
User Action:
None.
Reason:
The automated action P1 was updated.
System Action:
None
User Action:
None
Reason:
The operation P1 (which can be add, update or copy) on the automated action P2 was cancelled.
System Action:
None.
User Action:
None.
Reason:
One of the fields required for the CA Service Desk Trouble Ticket interface has an incorrect value.
The fields, their usage, and their valid values are described below.
This is the HTTP URL of the Web Services definitions on the CA Service Desk server. This server is where requests are created from alerts when you use the TT command.
In some cases, you can leave this value blank to let the CAISDI/soap component determine the default server.
This value must satisfy the following:
This URL points to the Web Services definitions that CAISDI/soap invokes to create the requests. It is not the same as the URL that is used to log in to the CA Service Desk client application.
Example: http://hostname:8080/axis/services/USD_R11_WebService
This is the CCI system ID of the system (MVS LPAR) where the target CAISDI/soap task is active. This value is the SYSID name specified in the CAICCI startup JCL.
Typically, you should leave this value blank to use the CAICCI facilities on this system.
This controls whether the Request Description field is produced in HTML (HTML) or in plain text (TEXT).
HTML formatting provides CA Service Desk operators with features such as hyperlinks back to this region's WebCenter interface.
Typically, you should set this value to HTML. If there are third party procedures that extract request descriptions and cannot render HTML, then set this value to TEXT.
Note: In many cases, the following values are sufficient:
If this does not work, review these values with your Systems Programmer who implemented the CAISDI/soap component and your CA Service Desk Administrator.
You may also need to refer to the Service Desk Integration Getting Started guide.
System Action:
None.
User Action:
Correct the field in error, and retry the operation.
Reason:
An APPC error occurred while communicating with a remote domain.
Identifies the APPC verb that encountered the error.
Is the return code set by the verb.
Is the feedback code set by the verb.
Identifies the remote domain.
Displays a sysmsg if set.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes, and retry.
Reason:
The alert monitor peer link process ($AMPSLKZ) received some unexpected data whilst communicating with the remote domain P4 . The APPC verb that encountered the error was P1 , the what received indicator had a value of P2 , the conversation state was P3 .
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
The Alert Monitor's peer link process $AMPSLKZ encountered a message that it did not expect. The message is P1 .
System Action:
Processing continues.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The link to the system P1 which is where this alert originated from is currently unavailable. Because the link is unavailable you will not be getting updates to this alert from the remote system.
System Action:
None.
User Action:
Check why the link to the remote system is unavailable.
Reason:
The procedure $AMPSMGZ failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
Procedure $AMPSMGZ terminates.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The Alert Monitor's peer link manager procedure $AMPSMGZ encountered an error and terminated. The error message is P1 .
System Action:
Peer System Manager will be restarted when a user goes into the SOLVE : Alert Monitor display.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
This is an internal message that is qyeued to a peer link process indicating an Alert Monitor Agent has ended. P1 is the NCLID of the agent that ended.
System Action:
None.
User Action:
None.
Reason:
The Alert Monitor's peer link manager procedure $AMPSMGZ encountered a message that it did not expect. The message is P1 .
System Action:
Processing continues.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
This is an internal message that is qyeued to a peer link process telling it to shut down the link to the remote system and end.
System Action:
None.
User Action:
None.
Reason:
The Alert Monitor's peer link manager procedure $AMPSMGZ attempted to start a peer link process ($AMPSLKZ) to communicate with a remote SOLVE system, but encountered an error starting the process. The error message returned was P1 .
System Action:
Processing continues.
User Action:
Contact your local Systems Administrator. Ensure that the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The number of alerts matching the supplied filter exceeds the specified limit p1.
System Action:
The number of returned alerts is limited to p1. Any subsequent alerts matching the filter are ignored.
User Action:
The default limit can be changed on the Alerts RSS Feed specification in the INTERFACES WEBCENTER parameter group of the associated region.
The limit can also be overridden by adding &LIMIT=nn to the URL, for example:
webcenter_url/public/nmdata.rss?channel=alerts&limit=200
webcenter_url specifies the URL of WebCenter.
Reason:
The RSS feed for p1 has been registered. Default parameters sets are p2.
System Action:
RSS feed requests for channel p1 are now honored.
User Action:
None.
Reason:
The RSS feed for p1 has been registered.
System Action:
RSS feed requests for channel p1 are ignored.
User Action:
None.
Reason:
The diagnostic test for the alert monitor is starting.
System Action:
None.
User Action:
None.
Reason:
This is a warning to inform you that the alert monitor currently has has no active alerts.
System Action:
None.
User Action:
None.
Reason:
This is an informational message, which informs you that the alert monitor is currently active on this region.
System Action:
None.
User Action:
None.
Reason:
This is an informational message, which displays the number of active alerts for each linked region running the alert monitor.
System Action:
None.
User Action:
None.
Reason:
This is an informational message, which displays the name of a linked region running the alert monitor.
System Action:
None.
User Action:
None.
Reason:
This informational message is displayed by the alert monitor selftest when an alert is created without errors.
System Action:
None.
User Action:
None.
Reason:
This informational message is displayed by the alert monitor selftest when an alert is closed successfully.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to an ALTEST command, which specifies an invalid parmameter.
System Action:
None.
User Action:
Reissue the ALTEST command with a valid parmameter.
The syntax of the ALTEST command is:
ALTEST <info=Y|N> <output=TERM|LOG>
All parameters are optional.
If <info=Y|N> is not specified, it defaults to INFO=Y INFO=N suppresses all information- only messages. If <output=TERM|LOG> is not specified, it defaults to OUTPUT=TERM OUTPUT=LOG writes all messages to the activity log.
Examples: ALTEST ALTEST INFO=N ALTEST INFO=N OUTPUT=LOG
Reason:
This warning indicates that the link to region P1 is no longer active.
System Action:
None.
User Action:
Investigate why the region is no longer available.
Reason:
This is an informational message, which indicates that the Peer System Manager procedure was initiated by the user ID specified in P1.
System Action:
None.
User Action:
None.
Reason:
This is a warning message, which indicates that there is a problem with the handling of linked systems running the alert monitor.
System Action:
None.
User Action:
Stop and restart the alert monitor. To do this, exit the M.A option and then select M.A again.
Reason:
This is an informational message, which indicates that the Peer Link Process procedure $AMPSLKZ, or the Agent APPC Transaction procedure $AMAGTTZ, were initiated by the user ID specified in P1 with NCLID P2. These processes ensure that the APPC communication is handled correctly.
System Action:
None.
User Action:
None.
Reason:
This is a warning, which indicates that the Peer Link Processes are not active. The alert monitor is not connected to any remote regions.
System Action:
None.
User Action:
Investigate why the regions are not available.
Reason:
This is an informational message, which indicates that the Alert Monitor Agent procedure $AMPAGTZ was initiated by the user ID specified in P1 and is running under the NCLID specified in P2.
System Action:
None.
User Action:
None.
Reason:
This is a warning, which indicates that the Alert Monitor Agent procedure $AMPAGTZ is not active. If this procedure is not running, new alerts are not added to the alert monitor.
System Action:
None.
User Action:
Restart the alert monitor on this region. To do this, exit the M.A. option and then reselect it.
Reason:
The action described in P1 found an error. This is described in P2.
System Action:
None.
User Action:
Investigate the error and take the appropriate action.
Reason:
The application ID described in P1 and P2 is registered with the Alert Monitor. Alerts are only displayed by the Alert Monitor if their application has been registered previously. If there is a discrepancy between the Alert Monitor count in the self test and the alerts displayed on your screen, it may be because the alert's application has not been registered.
System Action:
None.
User Action:
If the application is not user-defined, report the error to your Technical Support representative.
Reason:
This is an informational message that indicates that the External Alert Receiver procedure, $AMALRCV, was initiated by the user ID specified in P1 and is running under the NCLID specified in P2.
System Action:
None.
User Action:
None.
Reason:
This is a warning that indicates that the External Alert Receiver procedure, $AMALRCV, is not active. If this procedure is not running, external applications are unable to raise/modify alerts.
System Action:
None.
User Action:
If alerts from external applications are required, update the ALERTS parameter group (/PARMS) and set the field "Enable External Alerts?" to YES.
Reason:
This message displays the destinations of the Alert Monitor Trouble Ticket Interface, and the Alert Forwarding Interfaces.
The Trouble Ticket Interface is specified by menu shortcut /ALTTI .
The Alert Forwarding Destinations are specified by Customer Parameter Group $NM ALERTS 'Alert Monitor Interface'.
System Action:
None
User Action:
None
Reason:
The CA Desk server was contacted by this region, and a successful test login was performed.
This indicates that it should be ready to create CA Service Desk Requests when required by Alert Monitor Trouble Ticket and/or Alert Forwarding processing.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to contact the CA Service Desk server, but this failed. Additional error details are written to the activity log.
System Action:
None.
Until this failure condition is rectified, no alerts can be sent as Trouble Tickets or through Alert Forwarding to CA Service Desk.
User Action:
Ensure that the CA Service Desk server is operational and is in a state where Service Desk Requests can be created.
Verify that the CA Common Services CAISDI/soap component has been completely and correctly installed and set up. The CAISDI/soap MVS started task must be running and be configured with the correct Service Desk server details.
For more information, see the CA Common Services publication: Service Desk Integration Guide.
Reason:
The Alert Monitor exit specified in P1 is in use.
System Action:
None.
User Action:
None.
Reason:
This message displays the following help information, issued in response to an ALTTEST ? or ALTTEST HELP command.
ALTTEST can be run from OCS by using the following command:
ALTTEST <INFO=Y|N> <OUTPUT=TERM|LOG|ALL>
All parameters are optional.
Other optional parmameters: INFO=Y|N (default Y) OUTPUT=TERM|LOG|ALL (default TERM)
INFO=N suppresses information-only messages OUTPUT=LOG writes the output to the activity log only OUTPUT=ALL writes the output to the log and terminal
System Action:
None
User Action:
Enter the ALTTEST OCS command with the desired parameters.
Reason:
Alert Monitor Self Test is complete. The total number of warnings and errors are indicated. In general, severities are allocated as follows:
Errors Affect all or a large number of alert monitor functions. Errors should never be disregarded.
Warnings Affect at least one function, but other functions may be unaffected. If you do not require the function, warnings can be disregarded.
Notes Informational only. May not affect any processing.
System Action:
None.
User Action:
None.
Reason:
The Trouble Ticket data entry definition cannot be updated because of security restrictions on the VFS file. You need read-write access; the access allowed is P1 .
System Action:
The action is rejected.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket data entry definition lines consist of the word 'FIELD' followed by keyword=value pairs to set various characteristics of the field. Field definitions can span multiple lines, but new field defintions must begin with the word 'field'.
System Action:
None
User Action:
Insert the word 'field' before the field definition.
Reason:
The Trouble Ticket data entry definition is already being updated by the user P1 and can be updated by only one user at a time.
System Action:
The action is rejected.
User Action:
Retry the operation later.
Reason:
The Trouble Ticket data entry definition is invalid - this could be caused by a string which needs to be quoted.
System Action:
None
User Action:
Correct the definition and retry.
Reason:
The Trouble Ticket data entry definition is invalid - A FIELD statement is missing a value for the keyword specified as P1
System Action:
None
User Action:
Correct the definition and retry.
Reason:
The Trouble Ticket data definition cannot be updated because of an unexpected file error. P1 is the file action that failed and P2 is the VSAM feedback code.
System Action:
The action is rejected.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket data entry definition has been stored.
System Action:
None.
User Action:
None.
Reason:
No value was found for the required keyword IFACE.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your system administrator.
Reason:
The Trouble Ticket definition procedure does not recognize the interface type specified by the IFACE keyword parameter.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your system administrator.
Reason:
The Trouble Ticket interface definition template is already being updated by the user P1 and can only be updated by one user at a time.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Retry the operation later.
Reason:
The Trouble Ticket definition template cannot be updated because the file it is saved in cannot be written to.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket definition template cannot be updated because the file it is saved in cannot be accessed.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket definition template cannot be updated because of an unknown file error. P1 is the return code of the file open command.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket definition template cannot be updated because of an unknown file error. P1 is the file action that failed and P2 is the VSAM feedback code.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket interface definition template has been successfully updated and saved.
System Action:
None.
User Action:
None.
Reason:
The user has cancelled the update of the Trouble Ticket data details. No data has been modified.
System Action:
None.
User Action:
None.
Reason:
You must specify host name, node name and jobname, or, if you are using TCPaccess, you can specify destination ID. On IBM systems specify: * Host Name, which is the name of the local host * SMTP Node Name, which is the NJE node name of the local system * SMTP Jobname, which is the jobname of the SMTP task On TCPaccess systems specify: * DestId, which is the JES destination of the TCPaccess SPOOL#4 process.
System Action:
None
User Action:
Enter valid values and retry.
Reason:
You specified NONE in the Interface Type field on the Alert Monitor Trouble Ticket Interface Definition panel. This clears any previous interface type.
The Alert Monitor TT command and auto-trouble-ticket action are not available until you define a specific trouble ticket interface type.
System Action:
None.
User Action:
None.
Reason:
The call to the procedure failed because the keyword identified by P1 had an invalid value, identified by P2 .
System Action:
The request is rejected.
User Action:
Contact your local system administrator.
Reason:
The indicated field must be completed.
System Action:
The required field is highlighted.
User Action:
Specify a value in the indicated field.
Reason:
The Trouble Ticket interface definition template is already being updated by the user P1 and can only be updated by one user at a time.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Retry the operation later.
Reason:
The Trouble Ticket definition template cannot be updated because the file it is saved in cannot be written to.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket definition template cannot be updated because the file it is saved in cannot be accessed.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket definition template cannot be updated because of an unknown file error. P1 is the return code of the file open command.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your systems administrator.
Reason:
The Trouble Ticket definition template cannot be updated because of an unknown file error. P1 is the VSAM feedback code.
System Action:
The action is rejected and control is returned to the calling procedure.
User Action:
Contact your systems administrator.
Reason:
The EMAIL interface not available on MSP or VOS3 operating systems.
System Action:
The action is rejected.
User Action:
Chose another interface type.
Reason:
This is a trace message generated by the Alert Monitor Web Agent procedure when the TRACE keyword parameter is set to YES.
System Action:
None.
User Action:
None.
Reason:
A request passed to the Alert Monitor Web Agent procedure contained invalid data. P1 is the name of the element that was in error P2 is an explanation of the error
System Action:
The request is not processed.
User Action:
Contact your local support representative.
Reason:
A request passed to the Alert Monitor Web Agent procedure contained an invalid parameter name or value. P1 is the parameter name P2 is the value assigned to the parameter
System Action:
The request is not processed.
User Action:
Contact your local support representative.
Reason:
A set request passed to the Alert Monitor Web Agent procedure did not contain any field values to be set. P1 is the command that was passed
System Action:
The request is not processed.
User Action:
Contact your local support representative.
Reason:
A request passed to the Alert Monitor Web Agent procedure could not be parsed because it was incorrectly quoted or contained an invalid parameter name. P1 is an explanation of the error
System Action:
The request is not processed.
User Action:
Contact your local support representative.
Reason:
A request to modify the attributes of the alert collection process failed because the process has not been started.
System Action:
The request is not processed.
User Action:
Contact your local support representative.
Reason:
An indeterminate error occurred in the Alert Monitor Web agent. P1 is an explanation of the error
System Action:
The request is not processed.
User Action:
Contact your local support representative.
Reason:
User P1 entered the Track command against the alert and is now tracking the alert.
System Action:
None
User Action:
None
Reason:
A user entered the Track command for an alert that he/she was tracking, causing the tracking flag to be turned off.
System Action:
None
User Action:
None
Reason:
User P2 entered a command against the alert to change its severity to
P1 .
System Action:
None
User Action:
None
|
Copyright © 2014 CA.
All rights reserved.
|
|