|
|
|
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
The update of the SNA Group Filters list was cancelled.
System Action:
None
User Action:
None
Reason:
A Repeat/Insert of an SNA Group Filter has been attempted which would cause the maximum number of entries to be exceeded.
System Action:
The action is disallowed.
User Action:
None
Reason:
A list of valid resource names was displayed and no value was selected from it.
System Action:
Field highlighted in error.
User Action:
Enter a different name or select a valid name from the list displayed.
Reason:
The only valid values for 'weight type' are FIXED or PROPORTIONAL. Values of 'F' or 'P' are acceptable.
System Action:
Field highlighted in error.
User Action:
Enter one of the valid weight type values.
Reason:
The only valid value for 'weight type' is FIXED when applied to a single resource or PROPORTIONAL when applied to an UPSTREAM/DOWNSTREAM filter.
System Action:
Field highlighted in error.
User Action:
Change the value to 'FIXED'.
Reason:
A combination of NAME, TYPE and FILTER may only appear once within an SNA Resource Filter list.
System Action:
Fields highlighted in error.
User Action:
Change the NAME, TYPE or FILTER to make the entry unique.
Reason:
A name has been entered which consists of wildcard characters only. This is an invalid situation as the same effect can be achieved by specifying a single % or * .
System Action:
Field highlighted in error.
User Action:
Use % or * to achieve the desired effect.
Reason:
The use of the Generic Character * is not supported when Pattern Matching Characters % and/or _ are present. % may be used to indicate generic matching if pattern matching is being performed on the same field.
System Action:
Field highlighted in error.
User Action:
Remove either the Generic Character * or the Pattern Matching Characters
% and/or _. Alternatively % may be used to replace *.
Reason:
The use of the Field Prompt ? is not supported when any of the WildCard Characters, % or _ or * or Upstream/Downstream Characters > or < are present.
System Action:
Field highlighted in error.
User Action:
Remove either the Field Prompt or the Wildcard/Upstream/Downstream Characters.
Reason:
The value in the NAME field must be no more than eight characters in length. The only characters allowed in the resource name field are ALPHA, NUMERIC, NATIONAL, the three wildcards, % , _ or * or the upstream and downstream indicators > and < .
System Action:
Field highlighted in error.
User Action:
Enter a valid value.
Reason:
The use of the Upstream/Downstream characters, > and < ,is not supported when Pattern Matching Characters % and/or _ are present.
System Action:
Field highlighted in error.
User Action:
Remove either the Upstream/Downstream characters, > or < ,or the Pattern Matching Characters % and/or _.
Reason:
The use of the Upstream/Downstream characters, > and < ,is not supported when Generic Matching Wildcard * is present.
System Action:
Field highlighted in error.
User Action:
Remove either the Upstream/Downstream characters, > or < ,or the Generic Matching Wildcard *.
Reason:
If present, the Upstream character(s), < , must appear as the first one or two characters of the name field.
System Action:
Field highlighted in error.
User Action:
Place the Upstream character(s), < , at the start of the name field.
Reason:
If present, the Downstream character(s), > , must appear at the end of the name field.
System Action:
Field highlighted in error.
User Action:
Place the Downstream character, > , at the end of the name field.
Reason:
The TYPE field in an SNA Resource Group Filter Line cannot be totally generic if the NAME field is already totally generic, as this implies ALL SNA resources of ANY type, which is effectively the entire network, which could lead to performance degradation.
System Action:
Field highlighted in error.
User Action:
Make either the NAME field more specific or specifiy a particular TYPE.
Reason:
The TYPE field in an SNA Group Filter Line must be generic if the NAME field is using the UPSTREAM or DOWNSTREAM characters. This will select resources of more than one type.
System Action:
Field highlighted in error.
User Action:
Enter '*' for TYPE or remove the UPSTREM/DOWNSTREAM characters from the NAME field.
Reason:
If the NAME and TYPE fields for a Group Filter entry both contain only WILDCARD characters then the FILTER field is mandatory, otherwise this filter line would select the entire network and this is undesirable.
System Action:
Field highlighted in error.
User Action:
Specify a filter name or change the value of the NAME of TYPE fields so that they are not wildcard only.
Reason:
The service procedure identified by P1 was invoked with an invalid value for the keyword identified by P2 of P3.
System Action:
Request rejected
User Action:
Correct the keyword value and re-try
Reason:
A value was entered into the highlighted field which is not a valid value for that field.
System Action:
Field highlighted in error.
User Action:
Correct the value and re-try.
Reason:
The option identified by P1 is only valid when a process name is also supplied.
System Action:
Field highlighted in error.
User Action:
Provide the required process name and re-try.
Reason:
The request has been accepted.
System Action:
Processing continues.
User Action:
None.
Reason:
A group query was requested against the resource identified by P1 but no entry was found in the Group Manager's internal Resource Control Table.
System Action:
None
User Action:
None
Reason:
P1 is not a supported action for the P2 resource type.
System Action:
None.
User Action:
None.
Reason:
Action P1 is not supported for a Rapid Transit Protocol (RTP) resource with a type of RSTP (route setup).
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
No resource of the type identified by P1 found to be displayed in the selection list.
System Action:
None.
User Action:
None.
Reason:
Update is in progress on this definition by other user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
The NetMaster Automation CNM/PPO ACB initalization procedure $RSAC01C failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected, and the $RSAC01C procedure terminates.
User Action:
Check the syntax of the call to procedure $RSAC01C.
Reason:
The result of the attempt to perform the P1 action on the ACB is not known because the USERID (BSYS) does not have monitor status as described by the message N10639 written to the log for the parameter group concerned.
System Action:
The process assumes the attempt was successful and continues processing accordingly.
User Action:
If correct processing is required, it is advised that the affected USERID (BSYS) be given monitor status.
Reason:
The network discovery screening table code has executed the maximum number of commands allowed within the time specified in the ICS parameter group. No commands will be issued until P1 seconds have passed.
System Action:
Discovery is paused for at least P1 seconds.
User Action:
None.
Reason:
Discovery has found P1 resources that passed the filtering criteria specified in the ICS parameter group. The next phase of network discovery (database alignment) is being initiated.
System Action:
Database alignment is initiated.
User Action:
None.
Reason:
Network discovery timed out while waiting for a response to the P1 VTAM command. Network discovery may be incomplete.
System Action:
Network discovery continues with the next resource.
User Action:
Check that the responses from the command is not exceeding the POAQLIM defined for the primary ACB. Ensure that VTAM and the region are allocated sufficient CPU resource to function normally.
Reason:
Network discovery received an IST983E message in response to the P1 VTAM command. Network discovery may be incomplete.
System Action:
Network discovery continues with the next resource.
User Action:
Increase the POAQLIM value defined for the primary ACB.
Reason:
An invalid value was specified for the keyword P1. The value specified was P2.
System Action:
The request is rejected and processing terminates.
User Action:
Specify a valid value for the keyword.
Reason:
The action P1 for the class P2 was successfully performed.
System Action:
None.
User Action:
None.
Reason:
A display command was requested for resource P1 but the resource definition does not define a display command nor a display process. The resource cannot be displayed.
System Action:
The request is rejected.
User Action:
Define a display command or display process for the resource.
Reason:
The Command Processor was unable to read the SNA Resource definition identified by P1 from the database. Return Code P2 and Message P3 describe the error which occurred.
System Action:
Command processing is terminated.
User Action:
None.
Reason:
An invalid keyword was passed to the SNA Command Processor. The invalid keyword is identified by P1 and the invalid value is identified by P2.
System Action:
The request is rejected.
User Action:
Correct the calling procedure and rerun.
Reason:
This is an informational message issued when a command processor is invoked to perform function P1 against resource P2.
System Action:
None
User Action:
None
Reason:
The processing for command type P1 has been abandoned because it was detected that processing for command type P2 was already in progress.
System Action:
Command processing terminated.
User Action:
None.
Reason:
The Command Processor was unable to read the SNA Resource definition identified by P1 from the database. Return Code P2 and Message P3 describe the error which occurred.
System Action:
Command processing is terminated.
User Action:
None.
Reason:
The Command Processor executed the process identified by P1 for the resource identified by P2.
System Action:
Informational only.
User Action:
None.
Reason:
The process identified by P1 which was run for the resource identified by P2 ended with return code P3 and message P4.
System Action:
Informational only.
User Action:
None.
Reason:
An error occurred executing a process. Error message is returned in P1.
System Action:
Informational only.
User Action:
None.
Reason:
A return code of 99 was received from a process. A return code of 99 indicates that the command processor is to wait for the desired state change event to arrive for the specified timeout period.
System Action:
Informational only.
User Action:
None.
Reason:
The Command Processor has been unsuccessful in processing the request, in that the timeout figure was exceeded without the receipt of the required state change event.
System Action:
Informational only.
User Action:
None.
Reason:
Solicited Message received by the Command Processor.
System Action:
Informational only.
User Action:
None.
Reason:
The request is successful. The resource, P1 , has the desired state, P2 . P2 may be followed by the actual status in parentheses, which indicates that although the underlying status has been successfully set, the actual status is different.
System Action:
None.
User Action:
None.
Reason:
The request has timeout, the Command Processor has therefore set the status to the Timeout Status indicated in the Resource Model Definition.
System Action:
Informational only.
User Action:
None.
Reason:
The Command Processor initiated force inactivation processing.
System Action:
Informational only.
User Action:
None.
Reason:
The activation retry time limit has elapsed for the resource P1. If the resource has not become active by this then if a command or process was specified in the model definition it will executed at this time.
System Action:
Run command or process if specified.
User Action:
None.
Reason:
A display of the resource identified by P1 has returned a state of P2.
System Action:
Informational only.
User Action:
None.
Reason:
The Command Processor has been notified of a resource status change.
System Action:
Informational only.
User Action:
None.
Reason:
The Command Processor will issue the command identified by P1 for the resource identified by P2.
System Action:
Informational only.
User Action:
None.
Reason:
The activation retry attempt limit has elapsed for the resource P1. If the resource has not become active by this then if a command or process was specified in the model definition it will executed at this time.
System Action:
Run command or process if specified.
User Action:
None.
Reason:
The command processor for resource P1 has ended.
System Action:
Informational only.
User Action:
None.
Reason:
Recovery limits have been exceeded, the Command Processor has therefore set the status to the value indicated in the Resource Model Definition, as identified by P2.
System Action:
Informational only.
User Action:
None.
Reason:
The region failed to activate the SNA resource, P1 . The resource is in the FAILED state, and further recovery attempts are aborted.
System Action:
Recovery is aborted, and the resource remains in the FAILED state.
User Action:
Determine the reason for the resource failure, and correct the situation. Retry the activation request.
Reason:
Update is in progress on this definition by another user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
Automatic refresh of the list was turned on or off by use of the RefDelay command or function key. When automatic refresh is OFF the screen only refreshes when ENTER is pressed. When automatic refresh is ON the screen refreshes each time the RefDelay time period expires and a resource state change has occurred.
System Action:
None.
User Action:
None.
Reason:
The RefDelay command was entered with an invalid parameter. The following values may be used:
integer - set the refresh delay interval to 'integer' seconds where integer is a number between 1 and 60
ON - turn refresh delay processing on - the list will be refreshed automatically when events are received
OFF - do not refresh the list unless the Enter key or a function key is pressed blank - toggle refresh delay processing on and off
System Action:
The command is rejected.
User Action:
Correct the parameter and retry.
Reason:
The refresh delay interval was successfully altered.
System Action:
The list will be refreshed automatically the indicated number of seconds after an event has occured that indicates a change in the list.
User Action:
None.
Reason:
A request was made to view resources upstream/downstream from the resource identified by P2 ,but this is the resource whose upstream/ downstream resources are currently being displayed and so there is no sense in doing the same display again.
System Action:
Request denied.
User Action:
None.
Reason:
A request to ZOOM on an SNA Group is unable to be honoured because Network Discovery is still in progress.
System Action:
Command is rejected.
User Action:
Wait until Network Dicovery completes.
Reason:
A request to present a list of selected resources that is static (ie. resources will not appear or disappear from the list dynamically, but will be updated with status changes) could not be satisfied because there were no selected resources.
System Action:
None.
User Action:
Use the SS selection command to select resources before issueing the SS primary command.
Reason:
This message is issued if the SORT command is entered without any sort fields or with a '?'. It lists the valid sort fields in P1.
System Action:
None.
User Action:
Enter the SORT command with upto four of the valid sort fields in the manner: SORT field1,field2,field3,field4
Reason:
This message is issued if the SORT command is entered with too many sort fields. Four is the maximum number supported.
System Action:
Command is rejected.
User Action:
Enter the SORT command with upto four of the valid sort fields in the manner: SORT field1,field2,field3,field4 Use SORT ? to view valid sort fields.
Reason:
This message is issued if the SORT command is entered with an invalid sort field. P1 identifies the invalid field.
System Action:
Command is rejected.
User Action:
Enter the SORT command with upto four of the valid sort fields in the manner: SORT field1,field2,field3,field4 Use SORT ? to view valid sort fields.
Reason:
This message is issued if the ZOOM command is entered against an SNAGRP that does not contain any resources.
System Action:
The command is rejected.
User Action:
None.
Reason:
The network resource list process terminated because the system is performing Network Discovery.
System Action:
The network resource list is replaced by the Network Discovery Status panel.
User Action:
Wait for the Network Discovery to complete or try later.
Reason:
This message is a trace record from the CA NetMaster Network Automation APPC Transaction Server.
P1 is the trace ID.
P2 is the NCL process ID.
P3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The APPC request P1 failed with return code P2 and feedback code P3 , the message associated with the codes is P4 .
System Action:
Processing terminates.
User Action:
Determine whether the remote system is still available. Contact your systems administrator.
Reason:
Procedure in unexpected APPC "What Received" State. The state code is
P1 .
System Action:
None.
User Action:
Contact System Administrator.
Reason:
The request for data could not be satisified because the system is currently performing network discovery.
System Action:
Request rejected.
User Action:
Try later.
Reason:
This is a trace message produced by the database maintenance tracing facility. The information within these messages is for debugging purposes.
System Action:
None.
User Action:
Send the Activity Log with these messages to your local support representative.
Reason:
An invalid value was specified for the keyword P1. The value specified was P2.
System Action:
The request is rejected and processing terminates.
User Action:
Specify a valid value for the keyword.
Reason:
An error occurred processing the NDB request P1. The database being accessed was P2 and the NDB return code was P3. The error information associated with the return code (if relevent) is P4.
System Action:
The request is rejected and processing terminates.
User Action:
Contact the systems administrator.
Reason:
An error occurred defining the field P5 to the NDB database P2 . The action being performed was P1 and the return code was P3 . The error information associated with the return code (if relevent) is P4 .
System Action:
The request is rejected and processing continues with the next field definition.
User Action:
Contact the systems administrator.
Reason:
An error occurred accessing the AOM Global Database. The action being performed was P1 , the feedback code was P2 and the key was P3 .
System Action:
The request is rejected and processing terminates.
User Action:
Contact the systems administrator.
Reason:
An error occurred creating the NDB format P2 for the database P1 . The return code was P3 .
System Action:
The request is rejected and processing terminates.
User Action:
Contact the systems administrator.
Reason:
The object P1 was not found in the database.
System Action:
None.
User Action:
None.
Reason:
The object P1 was already in the database.
System Action:
None.
User Action:
None.
Reason:
A request to pass a message to the AOM Screening Table failed. The AOMALERT feedback code was P1.
System Action:
The requested action is not performed.
User Action:
The following table describes the feedback code and the corresponding action:
|
Code |
Description |
Action |
|---|---|---|
|
32 |
Storage shortage |
Increase the region size for the task, or try later. |
|
44 |
The AOM SSI does not exist |
Ensure that the AOM Sub-system Interface Identifier is defined and correctly specified in the OPSYSIDS parameter group. |
|
56 |
No screening table loaded |
Ensure that initialization has completed successfully and that the OPSYSIDS parameter group has not had errors. |
|
60 |
Screening table not active |
As above. |
|
other |
Internal error |
Contact Technical Support. |
Reason:
An invalid action was requested for the class P2 . The class does not support the action P1 .
System Action:
The request is rejected and processing terminates.
User Action:
Specify a valid action for the class or ensure that the class is correct.
Reason:
A request to perform network discovery was accepted. P1 is the SSCP name for the requesting domain and P2 is the host PU name, P3 specifies the level from where discovery is to begin.
System Action:
Network discovery is initiated.
User Action:
None.
Reason:
The network model filter criteria contained an invalid statement on line P2 of the criteria text. The invalid statement was P1 .
System Action:
The remainder of the resource filter is ignored.
User Action:
Correct the filter specifications and retry the request.
Reason:
The network model filter criteria contained an invalid keyword specification. The statement is P1 and is on line P2 and the error is P3 .
System Action:
The remainder of the resource filter is ignored.
User Action:
Correct the filter specifications and retry the request.
Reason:
Network Model database alignment has successfully completed. The statistics on the processing that occurred is as follows:
DUR= P1 - Duration/Elapsed time (dddd.hhmmss).
RES= P2 - Total number of network resources processed.
GET= P3 - Total number of resources retrieved from the database.
UPD= P4 - Total number of resources updated.
ADD= P5 - Total number of resources added to the database.
UNK= P6 - Total number of resources which existed on the database before network discovery but which were not discovered.
DEL= P7 - Total number of resources excluded/deleted by the installation user exit.
System Action:
None.
User Action:
None.
Reason:
A request to IDCAMS failed with return code P2 . The request was P1 . See the accompaning RSDBMS15 messages for more details.
System Action:
Processing continues but performance may be impacted.
User Action:
See the accompaning RSDBMS15 messages for more information.
Reason:
This message is a header for the messages returned from IDCAMS. P1 is the IDCAMS message returned from an IDCAMS request.
System Action:
None.
User Action:
Determine the meaning of all the messages as a whole and correct the problem.
Reason:
The criteria P1 was successfully compiled into a resource filter.
System Action:
None.
User Action:
None.
Reason:
Serialization for access to resource P1 failed.
System Action:
Request is rejected.
User Action:
Retry the request.
Reason:
The model template P1 could not be loaded for use. The reason is described by message P2 .
System Action:
None.
User Action:
Determine the reason for the failure and correct the error before trying again.
Reason:
The APPC request P1 failed with return code P2 and feedback code P3 , the message associated with the codes is P4 .
System Action:
Processing terminates.
User Action:
Determine whether the remote system is still available. Contact your systems administrator.
Reason:
Dynamic discovery was initiated for resource P1 and it completed successfully. The total number of resources processed was P2. Of those, P3 were new resources and P4 were existing resources. Of the existing resources, P5 of them involved a configuration change rather than just a state change.
System Action:
None.
User Action:
None.
Reason:
An attempt to return data for all profiled domains could not be satisfied because one or more domains were not available or could not be contacted or an error occurred obtaining the data or the domain was performing network discovery. If an error occurred getting the data then a message will be in the log indicating the error (one message for each failed access).
P1 is the total number of domains that could have their totals added to to the summary. P2 is the total number that had errors. P3 is the total number that were doing network discovery.
System Action:
Only the accessable domains have contributed to the totals.
User Action:
None.
Reason:
An attempt to perform dynamic resource discovery or parent activation failed because the resource was not a network resource known to VTAM.
System Action:
None.
User Action:
None.
Reason:
An attempt to perform dynamic resource discovery or parent activation failed because the resource was a major node and its type is not supported.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
This message indicates that database alignment is starting. This phase of network discovery aligns the database with the latest data discovered. Once aligned the data will be maintained as events arrive.
System Action:
None.
User Action:
None.
Reason:
P1 records were added to the GDB for use by network discovery.
System Action:
None.
User Action:
None.
Reason:
The SNA model P1 was loaded.
System Action:
None.
User Action:
None.
Reason:
P1 SNA models were loaded.
System Action:
None.
User Action:
None.
Reason:
The work volume and/or dataset used as a work file was invalid.
System Action:
Alignment of the database with the network discovery is terminated.
User Action:
Verify the dataset name and volume serial specified in the ICS parameter group $RM AUTOSNAFILE. Once corrected, action the parameter group and retry network discovery.
Reason:
The database alignment phase of network discovery was cancelled.
System Action:
Alignment of the database with the network discovery is terminated.
User Action:
None.
Reason:
The user exit procedure P1 was disabled and will not be called again for the duration of network discovery. The exit was disabled because it returned an erroneous return code. The return code returned was P1 and message was P3.
System Action:
Network discovery continues but will not invoke the user exit.
User Action:
Contact your systems administrator.
Reason:
Database alignment is already in progress.
System Action:
Alignment is terminated.
User Action:
None.
Reason:
The filter specified logically excludes all resources from being discovered. This is an invalid filter.
System Action:
Request is rejected.
User Action:
Ensure that at least one resource will be included by the filter.
Reason:
An attempt to return data for all profiled domains could not be satisfied because of one of the following conditions:
- One or more domains were not available. - One or more domains could not be contacted. - An error occurred while obtaining the data from one or more domains. - One or more domains was performing network discovery.
If an error occurred while getting the data, a message is logged indicating the error (one message for each failed access).
System Action:
The request is rejected.
User Action:
Determine the reason for the errors, and retry at a later time.
Reason:
A resource that was dynamically deleted from VTAM was deleted together with all its children.
System Action:
None.
User Action:
None.
Reason:
The debugging tool for tracing database maintenance has been turned on or off. P1 is the value it has been turned to.
System Action:
Database maintenance tracing is turned on or off.
User Action:
If you have turned tracing ON then turn it OFF when the error has been recreated and send the Activity Log output with the trace messages in it to your local support representative. If you have turned it OFF then send the Activity Log output with the trace messages in it to your local support representative.
Reason:
An event arrived indicating that a P1 was changing status to ACTIVE or STARTING, however the resource's desired status is INACTIVE. Because undesired resource termination is not in effect the action to terminate the resoure has been bypassed.
System Action:
No action is taken to change the resources status.
User Action:
None. This behaviour is controlled by the AUTOSNACNTL parameter group and can be changed by updating the "Bypass Term. if Undesired Active"field.
Reason:
The ALLOCATION of the VARTABLE described by P1, with a NAME and SCOPE of P2 and P3 failed with &ZFDBK of P4.
System Action:
The SNA GROUP MANAGER will fail to initialize.
User Action:
Try to ascertain the reason for the inability to allocate a vartable, correct it and re-start the SNA Service Manager.
Reason:
Only one SNA Group Manager may be active. This message indicates that a second copy of the SNA Group Manager procedure attempted to start but detected that a previous copy was active and so terminated.
System Action:
The second SNA GROUP MANAGER will fail to initialize.
User Action:
None.
Reason:
An attempt to read the SNA Group Definition, identified by P1, was unsuccessful. The Return Code P2 was returned along with error message P3.
System Action:
Processing continues.
User Action:
None
Reason:
The requested processing has completed. P1 is the type of processing that was requested.
System Action:
None.
User Action:
None.
Reason:
The recycle (inactivate and activate) of the SNA resource P1 completed successfully.
System Action:
None.
User Action:
None.
Reason:
The Template System Image version specified is not valid as the Active SNA Model Image.
System Action:
The field is highlighted and a message is displayed.
User Action:
Enter a valid Template System Image version.
Reason:
The PPOPROC was started and did not return an indication that it had successfully initialized within the time allowed.
System Action:
The parameter group fails.
User Action:
Determine the reason the PPOPROC failed. Use the $LOG command to access the activity log. Look for any messages that indicate that the procedure has ended, either normally or as a result of an abend.
Reason:
Template definition is a special definition which must be accessed only via the Administration menus.
System Action:
The request is rejected.
User Action:
Access Template definition from the Administration (Resource Definition) menu.
Reason:
The NetMaster Automation Model command validation procedure $RSMD02V failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected, and the $RSMD02V procedure terminates.
User Action:
Check the syntax of the call to procedure $RSMD02V.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The supplied command is not recognized.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
An invalid value was specified for the keyword P1 . The value specified was P2 .
System Action:
The request is rejected and processing terminates.
User Action:
Specify a valid value for the keyword.
Reason:
A duplicate monitor process for events from P1 was started. This duplicate process has detected the duplication and has terminated itself.
System Action:
None.
User Action:
None.
Reason:
An event was issued to prompt the screening table process of discovery.
System Action:
None.
User Action:
None.
Reason:
An event from the screening table was received and the event class was not known by the monitor. The event ID was P1 the class was P2 and the event text was P3.
System Action:
None.
User Action:
Contact your local support office.
Reason:
The resource P2 entered the VTAM state P1 and the state is not known to automation. Automation will assume a status of UNKNOWN.
System Action:
The resource's status is assumed as UNKNOWN.
User Action:
Contact your local support office.
Reason:
Network discovery processing was triggered on P1 (date) at P2 (time).
System Action:
Network discovery starts.
User Action:
None.
Reason:
The resource P1 was a duplicate resource ie actually a different resource but with the same name as another. It's VTAM state is RESET and it cannot be activated.
System Action:
None.
User Action:
Check the definitions in your VTAMLST dataset.
Reason:
An attempt to execute the actions associated with a message failed. The reason is that the get for the actions from the vartable failed with feedback code P3 . The resource that triggered the action was P2 and the action key is P1 . The message ID that triggered the action is P4 .
System Action:
Message actions are not executed.
User Action:
Contact the systems administrator.
Reason:
The message actions to be executed on behalf of resource P2 failed. The reason is in the previous message.
System Action:
None.
User Action:
Check the previous message.
Reason:
During discovery P1 state change/action events arrived which were buffered until after database alignment. All buffered events were processed.
System Action:
None.
User Action:
None.
Reason:
During the processing of a VTAM display response the IST1315I message was received. This message indicates that the display was truncated by the display MAX= parameter setting. This indicates that the VTAMOPTS parameter DSLPYMAX was set too low. Network discovery may not discover all the resources covered by the display command of type P1.
System Action:
Discovery continues, but some resources may not be discovered.
User Action:
Ensure that the VTAM option DSPLYMAX is sufficiently high to allow all displays to complete. Note that a D NET,TERMS is NOT done and need not be catered for.
Reason:
A Network Discovery command was issued via the SPO interface as requested by the screening table. The command issued was P1.
System Action:
The command responses are passed to the screening table for processing.
User Action:
None.
Reason:
The region detects that the PPO message flow has been enabled. This indicates that the flow was disabled for an unknown period of time, during which resources may have changed status without being detected. A discovery of the network is scheduled to ensure that all states are correct.
System Action:
Network discovery is scheduled.
User Action:
You do not need to take any action. However, if you do not want the region to perform discovery automatically when this condition is detected again, change the value of the Schedule Discovery on PPO Start field in the AUTOSNACNTL parameter group to NO and action the group. (To display the list of parameter groups, enter the /PARMS path.)
Reason:
The heartbeat monitor could not be started for the P1 resource, and the resource cannot be monitored. The resource is using the P2 model. For additional information, see the previous message in the log.
System Action:
Heartbeating for the resource is not performed.
User Action:
Contact your local support representative.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
Version specified was not a numeric value.
System Action:
The request is rejected.
User Action:
Enter a valid number.
Reason:
Template definition is a special definition which must be accessed only from Customisation Menu option "T".
System Action:
The request is rejected.
User Action:
Access Template definition from Customisation menu option "T".
Reason:
Command P1 is invalid.
System Action:
Command is rejected.
User Action:
Correct the command and retry the request.
Reason:
Network discovery has completed.
System Action:
None.
User Action:
None.
Reason:
Network discovery was already in progress and another discovery was initiated. The current discovery has been cancelled and a new discovery is in progress.
System Action:
Network discovery is cancelled and another discovery started.
User Action:
None.
Reason:
A request to perform Network Discovery was accepted.
System Action:
Network discovery is started.
User Action:
None.
Reason:
The current Network Discovery will be a Cold Start.
System Action:
None.
User Action:
None.
Reason:
The screening table processing phase of network discovery has not responded within the defined processing window. Network discovery has failed. P1 is the time and P2 is the date at which the time was detected.
System Action:
Network discovery terminates.
User Action:
Note the messages that follow and restart network discovery. Also note any messages that appear in the SYSLOG and that were issued between when network discovery started and when the timeout was detected. Contact Technical Support.
Reason:
The screening table processing phase of network discovery has not responded within the defined processing window. Network discovery has failed. This message preceeds diagnostic messages and is a header only.
System Action:
None.
User Action:
None.
Reason:
This message provides various diagnostic information.
System Action:
None.
User Action:
Note down the data in this message.
Reason:
This message indicates that the screening table processing phase of network discovery has not performed any actions for network discovery for P1 seconds.
System Action:
None.
User Action:
None.
Reason:
The system detected that the Network ID or Domain Name was different to that currently stored on the file or that the file was empty. Any of these conditions indicate that a COLD start is required.
System Action:
A COLD start is forced.
User Action:
None.
Reason:
The call to the prediscovery exit failed. P1 contains the value of &RETCODE, and P2 contains the value of &SYSMSG.
System Action:
Network discovery terminates.
User Action:
Note the values of &RETCODE and &SYSMSG. Contact your systems programmer.
Reason:
The call to the prediscovery exit returned a code indicating that discovery should be aborted. P1 contains the value of the return code from the exit.
System Action:
Network discovery terminates.
User Action:
Note the return code. Contact your systems programmer.
Reason:
The call to the prediscovery exit returned a code indicating that processing has finished. P1 contains the value of the return code from the exit.
System Action:
Network discovery continues. The return code set by the exit may affect the parameters for the current discovery.
User Action:
None.
Reason:
The call to the postdiscovery exit finished. P1 contains the value of &RETCODE, and P2 contains the value of the return code from the exit.
System Action:
None.
User Action:
None.
Reason:
During Network Discovery an attempt to read a VSAM state from the AOMGDB was unsuccessful. P1 is the key that was accessed and P2 is the resource being processed at the time of the error.
System Action:
The Normalised State for the resource is set to UNKNOWN and processing continues.
User Action:
Contact Technical Support.
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:
A selection made from the menu is not supported by the menu service procedure and cannot be processed.
System Action:
The selection is rejected.
User Action:
Contact the local support representative.
Reason:
Access to the file identified by P1 has been denied by the validation exit NCLEX01.
System Action:
The request is rejected.
User Action:
Contact the systems administrator if access to this file is required.
Reason:
A read error occurred during processing of the P1 file. The return and VSAM feedback codes are identified by P2 and P3 respectively.
System Action:
File processing is terminated.
User Action:
Contact the systems administrator and report the error.
Reason:
The NetMaster Automation Network Resource Problem Determination interface procedure $RSNR01C failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected, and the $RSNR01C procedure terminates.
User Action:
Check the syntax of the call to procedure $RSNR01C.
Reason:
The NetMaster Automation Network Resource Problem Determination interface procedure $RSNR01C failed during request processing because it was passed too many parameters. P1 is the action to which the parameters are supposed to be related.
System Action:
The request is rejected, and the $RSNR01C procedure terminates.
User Action:
Check the syntax of the call to procedure $RSNR01C.
Reason:
The NetMaster Automation Network Resource Problem Determination interface procedure $RSNR01C failed during request processing because an invalid or null value was supplied on the SESSTYPE keyword. This keyword is mandatory when the request is for an NTS Session List and must be either "Primary" or "Secondary".
System Action:
The request is rejected, and the $RSNR01C procedure terminates.
User Action:
Check the syntax of the call to procedure $RSNR01C.
Reason:
The procedure P1 which is required to perform the action P2 for class P3 for P4 was not found in the COMMANDS DD concatenation.
System Action:
The request is rejected and procedure $RSNR01C terminates.
User Action:
Check that the library containing the required procedure is included in the COMMANDS DD concatenation.
Reason:
The NetMaster Automation Network Resource Problem Determination command validation procedure $RSNR02V failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected, and the $RSNR02V procedure terminates.
User Action:
Check the syntax of the call to procedure $RSNR02V.
Reason:
The command entered on the command line was not recognized by the procedure.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The value for P1 must be supplied.
System Action:
The command is rejected.
User Action:
Enter the value and retry.
Reason:
The supplied command is not recognized.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The supplied value must be a valid link name. A Link Name may be 1 to 12 characters in length, must start with an alphanumic character and may contain any graphic character except for asterisk (*).
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
P1 is not a supported action for the P2 resource type.
System Action:
None.
User Action:
None.
Reason:
Action P1 is not supported for a Rapid Transit Protocol (RTP) resource with a type of RSTP (route setup).
System Action:
None.
User Action:
None.
Reason:
A NetSpy synchronous request returned data in multiple, repeated units, but none of those matches the specific request. For example, DV returned information on multiple TPs but there is no data for the required one.
System Action:
The NetSpy API interface returns an error message to the caller. The request was probably not satisfied, as specific data was not found.
User Action:
Check the logic of the request, pattern, and scope. Change and resubmit the request if errors found. If the situation is repeated, report the problem to the developers.
Reason:
This message is the second of two messages that are issued when an internal error occurs in the SNA network summary display procedure. P1 is the ID of the message associated with the error. The P1 message is the first message of the group. Both messages are written to the activity log.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The SORT command has set the sort sequence according to the value in P1. Resource lists displayed from this point will be sorted according to this sort sequence.
System Action:
None.
User Action:
None.
Reason:
This message is the first of two messages that are issued when an internal error occurs in the SNA network summary display procedure. P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
This message is a trace of the Network Summary display procedure.
P1 is the trace ID.
P2 is the NCL process ID.
P3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The message displays a NetSpy Alert Manager trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
A request to start a copy of the $RSNSEVM procedure was ignored because another copy is currently running.
System Action:
A new copy of the procedure is not started.
User Action:
None.
Reason:
NetMaster Automation for SNA NetSpy Alert Manager procedure has failed because of an internal system error. P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The NetMaster Automation for SNA NetSpy Alert Manager is ready to process NetSpy alerts.
System Action:
The region is ready for NetSpy alerts.
User Action:
None.
Reason:
The NetMaster Automation for SNA NetSpy Alert Manager received an incomplete NetSpy alert.
P1 is NSPALERT for a new or duplicate alert, or NSPCLEAR for a Clear Alert event.
P2 is the NetSpy alert text.
System Action:
The NetSpy alert event is ignored.
User Action:
Contact Technical Support.
Reason:
The NetMaster Automation for SNA NetSpy Alert Manager procedure encountered a recoverable error.
System Action:
NetSpy alert processing continues. However, some alerts might have been lost.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Relevant messages in the activity log
Reason:
An invalid keyword was passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact the systems administrator.
Reason:
The SORT command has been issued and has successfully set the sort sequence to the value displayed in P1. Resource lists displayed from this point will be sorted according to this sort sequence.
System Action:
None
User Action:
None
Reason:
VTAM Domains consolidation has been modified.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword was passed to the service procedure.
System Action:
The request is rejected.
User Action:
Correct the calling procedure to the service procedure and rerun exec.
Reason:
At least one domain must be included for the Network Summary display.
System Action:
The request is rejected.
User Action:
Do not exclude all domains.
Reason:
An invalid keyword was passed to the procedure.
System Action:
The request is rejected.
User Action:
Contact the systems administrator.
Reason:
Validation found no entry specified on mandatory field/s.
System Action:
The request is rejected.
User Action:
Specify entry on field/s in error.
Reason:
Update is in progress on this definition by another user.
System Action:
The request is rejected.
User Action:
Try again later.
Reason:
No value selected from the selection list displayed.
System Action:
None.
User Action:
None.
Reason:
An invalid keyword value was passed to the procedure.
System Action:
The procedure terminates.
User Action:
If the cause of this error is not apparent, contact Technical Support.
Reason:
An error occurred during a 'zoom' of an SNA group from the web interface. The region responsible for the group could not be identified. P1 may contain further information.
System Action:
The 'zoom' fails.
User Action:
This problem may occur if the Automation Services region is loading a system image. If this is the case, wait until the operation completes and try again. If the problem persists, contact Technical Support.
| Copyright © 2012 CA. All rights reserved. |
|