|
|
|
Reason:
A request for a detail display of a CNM alert has failed. When the alert was generated, the CNM record was not saved as an event in the NEWS database (NEWSFILE).
System Action:
None.
User Action:
Event recording options are specified, by event category, in the CNMFILTERS ICS parameter group. If detailed displays are required, the event recording option must be E (Event) or higher.
Reason:
An SNA interface or exit action has failed:
P1 is the resource type (CNM, CNMEXIT, SAW, SAWEXIT).
P2 is the action (START or STOP).
P3 is the resource name (exit or interface ACB name).
P4 is the reason.
System Action:
The action is not performed.
User Action:
This situation should not occur and should be reported to your product supplier.
Reason:
The alert monitor initialization action has completed successfully.
System Action:
None.
User Action:
None. For information only.
Reason:
The NCP monitor initialization action has completed successfully.
System Action:
None.
User Action:
None. For information only.
Reason:
The NSCNTL cache has been opened successfully. The maximum cache size is P1 .
System Action:
The cache will be used to enhance access to the NSCNTL file.
User Action:
None
Reason:
A request to resume or suspend NEWS database logging through the CNMLOGGING parameter group was successful. p1 identifies the request type.
System Action:
For resumed, logging of CNM records to the NEWS database is started.
For suspended, logging of CNM records to the NEWS database are stopped until one of the following occurs:
- The CNMPROC is restarted (or the region restarted).
- A request to resume logging is successful.
User Action:
None.
Reason:
An exit ( P1 is the exit type, CNM or SAW, and P2 is the exit name) has been stopped as a result of one of the following:
- An explicit request to suspend the exit
- The name of the exit being changed; the old exit must be stopped before the new exit can be started.
System Action:
If the exit name is being changed, another message will indicate this.
User Action:
None
Reason:
An exit ( P1 is the exit type, CNM or SAW, and P2 is the exit name) has been started as a result of one of the following:
- An explicit request to activate the exit
- The name of the exit being changed
System Action:
If the exit name is being changed, a previous message will indicate this.
User Action:
None
Reason:
An interface ( P1 is the interface type, CNM, SAW, or SAW logging) has been stopped as a result of one of the following:
- An explicit request to suspend the interface
- The ACB name of the interface being changed; the old interface must be stopped before the new interface can be started.
System Action:
If the interface ACB name is being changed, another message will indicate this.
User Action:
None
Reason:
An interface ( P1 is the interface type, CNM, SAW, or SAW logging) has been started as a result of one of the following:
- An explicit request to activate the interface
- The ACB name for the interface being changed
System Action:
If the interface ACB name is being changed, a previous message will indicate this.
User Action:
None
Reason:
An interface ( P1 is the interface type, CNM, SAW) has been defined with the initially active option set to NO.
System Action:
The interface is not started during system startup.
User Action:
None.
Reason:
An interface ( P1 is the interface type, CNM, SAW) has been defined with the currently active option set to NO.
System Action:
The interface is not started as a result of actioning the parameter group.
User Action:
None.
Reason:
The alert monitor initialization action failed; the reason is given in a message (AMCALLnn) which follows.
System Action:
Alert monitor initialization for NetMaster for SNA alerts is incomplete. Alert monitoring functions for NetMaster for SNA alerts will not function correctly.
User Action:
Review the help for the appropriate AMCALLnn message.
Reason:
The NCP monitor initialization action failed; the reason is given in a message (DFCALLnn) which follows.
System Action:
NCP monitor initialization is incomplete. NCP monitoring functions will not function correctly.
User Action:
Review the help for the appropriate DFCALLnn message.
Reason:
An attempt to open the NSCNTL cache (vartable $NWCACHE) failed. P1 is the FDBK code returned from the &VARTABLE ALLOC statement.
System Action:
The cache is not referenced.
User Action:
Determine the reason for the error and correct the problem as necessary. The meaning of the FDBK code can be found in the NCL Reference under the &VARTABLE ALLOC statement.
Reason:
A request to resume NEWS database logging is invalid because the CNM procedure is not active.
System Action:
NEWS database logging remains suspended.
User Action:
Start the CNM interface using the CNM parameter group and then return to the CNMLOGGING parameter group to review the NEWS database logging status.
Reason:
The field indicated ( P1 ) must be specified for a request to activate it (by field P2 ).
System Action:
None
User Action:
Either specify the indicated exit or ACB name, or do not request either initial or current activation.
Reason:
The user supplied procedure P1 failed during processing; the message returned was P2 .
System Action:
Processing continues. The result of the user supplied procedure may be partially in effect.
User Action:
Investigate and correct the cause of the failure in the user supplied procedure, and then action the parameter group.
Reason:
An attempt to start the Session Awareness (SAW) interface has failed because another application is already in session with the VTAM ISTPDCLU application. P1 identifies the job with the ACB name P2 that is currently in session with ISTPDCLU.
System Action:
SAW Start fails, and session awareness is not available.
User Action:
Use the NOVTAM SAW Start option in the SAW parameter group if you do not need to collect local active session data. Alternatively, retry the request when the other application has released the interface.
Reason:
A request to resume or suspend the NEWS PPI alert receiver was successful. p1 is the request type - resumed or suspended.
System Action:
For resumed, the NETVALRT PPI receiver is active and CNM records are received through PPI.
For suspended, the NETVALRT PPI receiver is inactive.
User Action:
None.
Reason:
A request to start the NEWS PPI alert receiver ($NWPPIAR) failed.
System Action:
The error messages from the PPI receiver are logged. An attempt to restart the receiver is made after 30 seconds.
User Action:
Review the EWGExx messages in the activity log. Check that the procedure providing the PPI service is active.
Reason:
A request to display NNP resources (such as Ports, Stations, Sessions, or HPR connections) has failed because no resources match the specified criteria.
System Action:
None.
User Action:
Retry using other criteria.
Reason:
A request to display NNP resources (such as Ports, Stations, Sessions, or HPR connections) has resulted in a large number of resources. The list has been truncated to the first P1 resources.
The truncation value ( P1 ) varies, based on the resource type and available data (for example, length of DLC types or partner node names) because the restriction is based on the number of characters present in the response, rather than the number of resources.
System Action:
None.
User Action:
Refine the selection criteria and retry. For example, rather than selecting all stations, include a status value such as "Not Active."
Reason:
A request to display a specific NNP resource has failed because the name of the resource was not provided. The type of resource ( P1 ) will be one of the following:
portname - The port name for a port
linkname - The link name for a station
sessionid - The 16 (hexadecimal-digit) session ID for a session
System Action:
None.
User Action:
Correct the procedure that invoked $SNNPAPI ACTION=GET to specify the NAME= parameter for the resource class. For example: &CALL PROC=$SNNPAPI + PARMS=(ACTION=GET,+ CLASS=PORT,+ NAME=&portname,+ other parameters ...
Reason:
A request to display the partner for a Link Station or a Session has failed due to one of the following:
- A link station does not have a host partner
- The link name for the Link Station or Session is SPMOSSE
System Action:
None.
User Action:
None.
Reason:
The required action is not available for SNAMS Focal Point (FP) or Entry Point (EP) records. This is because there are no SNAMS records distributed on the NSCNTL file as all records contain SNA network resource names that are site specific.
System Action:
None
User Action:
None
Reason:
A file operation has failed:
P1 is the DD name for the file. This is either: SNNSCNTL - the "old" NSCNTL file as identified by the DSN= parameter NSCNTL - the NSCNTL file for the current release
P2 is the file operation, for example Open, Close, Get, Put
P3 is the file return code (&FILERC)
P4 is the VSAM feedback code (&VSAMFDBK) where relevant
P5 is the record key where relevant
P6 is the system message (&SYSMSG) where relevant
System Action:
The utility terminates.
User Action:
Determine the cause of the error and retry.
Reason:
The record selected for copy (Key= P1 ) was not found on the "old" NSCNTL file. The record may have been deleted by another user.
System Action:
The record is not copied.
User Action:
None
Reason:
Procedure was called with the CAT parameter specifying a category not defined in the NSCNTL file.
System Action:
Categories list displayed.
User Action:
Proceed by selecting from the displayed list or change parameters when calling the procedure.
Reason:
An attempt to obtain the NSCNTL file DSN failed, indicating that it was not available.
System Action:
Processing terminates.
User Action:
Ensure that the file is present and allocated.
Reason:
An attempt to open or close the NSCNTL file resulted in an error, with a a return code provided.
System Action:
Operation terminates.
User Action:
Ensure that the NSCNTL file is available and not corrupted or locked.
Reason:
A Read/Write error was detected while processing the NSCNTL file.
System Action:
Operation terminates.
User Action:
Act according to the error message provided.
Reason:
Modify/Add action was requested but the NSCNTL file was opened in read only mode.
System Action:
Action rejected.
User Action:
Ensure that the NSCNTL file is not corrupted or used in exclusive mode.
Reason:
Delete action was requested while NSCNTL file was not opened for delete access.
System Action:
Delete action is rejected.
User Action:
Ensure that the NSCNTL file is not corrupted or used in exclusive mode.
Reason:
The functional procedure supporting the currently selected category returned an error code and/or message.
System Action:
Operation continues.
User Action:
Check relevant error code/message and perform correcting action.
Reason:
User whose user ID is provided is not authorized to use NEWS services.
System Action:
Procedure terminates.
User Action:
Ensure that the proper level of authorization is obtained.
Reason:
The locate function failed to locate record with the key containing specified string P1 .
System Action:
The record list is not repositioned.
User Action:
Check the string looked for.
Reason:
The DSN parameter, which specifies the dataset name of the "old"NSCNTL file, was omitted. This is a mandatory parameter.
System Action:
The utility terminates.
User Action:
Specify the dataset name (parameter) and retry. Format: $SNNSCNV DSN=datasetname
Reason:
A file operation has failed:
P1 is the DD name for the file. This is either: SNNSCNTL - the "old" NSCNTL file as identified by the DSN= parameter NSCNTL - the NSCNTL file for the current release
P2 is the file operation, for example Open, Close, Get, Put
P3 is the file return code (&FILERC)
P4 is the VSAM feedback code (&VSAMFDBK) where relevant
P5 is the record key where relevant
P6 is the system message (&SYSMSG) where relevant
System Action:
The utility terminates.
User Action:
Determine the cause of the error and retry.
| Copyright © 2012 CA. All rights reserved. |
|