|
|
|
Reason:
User P1 has attempted to invoke a function of the Network Management feature but is not authorised to do so.
System Action:
The process is terminated.
User Action:
Contact your systems administrator if you feel you should have access to the Network Management feature.
Reason:
P1 is not a valid keyword.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
The keyword P1 has been specified more than once.
System Action:
The process is terminated.
User Action:
Correct the parameters and retry.
Reason:
P1 is not valid for keyword P2.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
The value required for keyword P1 has been omitted.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
Required parameter P1 has been omitted.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
This indicates the end of data for the current display.
System Action:
None.
User Action:
None.
Reason:
User P2 has no access priviledge to the resource P1.
System Action:
Access to the resource is denied.
User Action:
Contact your security administrator if you require access to this resource.
Reason:
A request has timed out whilst waiting for a response from a device. P1 is the amount of time waited for before the request was abandoned.
System Action:
The process is terminated.
User Action:
Retry the function.
Reason:
P1 is not valid for P2 .
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
THe SNAMS feature is not licenced.
System Action:
The requested function is not performed.
User Action:
If the SNAMS feature was excluded at SOLVE startup, include it. Otherwise arrange to have the SNAMS feature licenced.
Reason:
A request for a focal point relationship has been accepted. This message is followed by messages AN0102 and AN0103, which contain the MS category code, application name, focal point, and entry point nodes for the established FP/EP relationship.
System Action:
None
User Action:
None
Reason:
This message appears after AN0101 when a focal point relationship is accepted. It contains the MS category P1 and the focal point application name P2 for the established focal point.
System Action:
None
User Action:
None
Reason:
This message appears after AN0101 when a focal point relationship is accepted. It contains the focal point node P1 and entry point node P2 of the established FP/EP relationship.
System Action:
None
User Action:
None
Reason:
A request for a focal point relationship has been rejected.
P1 describes the reason for the rejection, P2 is node name, and P3 is the type of request, one of:
EP - acquire Explicit Primary Entry Point
DEFAULT - acquire Network Node Entry Point
FP - acquire Implicit Primary Focal Point
BACKUP - acquire Backup Focal Point
DOMAIN - notification of active Focal Point to Entry Point
System Action:
None
User Action:
Correct the condition if possible and retry. Use the /CODES menu shortcut to access SNA Sense Code information. The cause is normally either a misspelt node name, or the node cannot be reached due to a connectivity problem.
Reason:
An unexpected reply P1 is received by the $ANCALL procedure in response to an MS Capabilities request previously sent.
System Action:
The process is terminated.
User Action:
Contact your product support representative.
Reason:
An unexpected error has occurred when the $ANCALL procedure sent an MS Capabilities request to the indicated node.
System Action:
The process is terminated.
User Action:
Contact your product support representative.
Reason:
An unexpected error has occurred when the $ANCALL procedure attempted to receive an MS Capabilities request from the indicated node.
System Action:
The process is terminated.
User Action:
Contact your product support representative.
| Copyright © 2012 CA. All rights reserved. |
|