|
|
|
Reason:
The CAS external interface procedure $CACALL 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 procedure $CACALL terminates.
User Action:
Check the syntax of the call to procedure $CACALL.
Reason:
The CAS API procedure $CACALL failed during processing because it was unable to obtain an NCL procedure lock. P1 is the primary name of the lock, P2 is the minor name of the lock and P3 is the text message set by the current holder of the lock.
System Action:
Procedure $CACALL ends.
User Action:
Wait and then retry the request. If the request still fails then contact the System Administrator.
Reason:
An error occurred performing an action on a VARTABLE. P1 is the name of the VARTABLE, P2 is the action that was being performed and P3 is the feedback code returned from the VARTABLE action.
System Action:
The request is rejected.
User Action:
Contact the systems administrator.
Reason:
A procedure invoked by $CACALL return an invalid return code. P1 is the name of the procedure in error and P2 is the invalid return code that was returned by it.
System Action:
$CACALL ends with return code 8
User Action:
Contact the systems administrator.
Reason:
A procedure invoked by $CACALL returned an invalid feedback code. P1 is the name of the procedure in error and P2 is the invalid feedback code that was returned by it.
System Action:
$CACALL ends with return code 8 and feedback 8
User Action:
Contact the systems administrator.
Reason:
The CAS external interface procedure $CACALL failed during request processing because it was invoked with a value set in variable $LHCRIT1 and a value set in keyword CRITERIA. Variable $LHCRIT1 and keyword CRITERIA are mutually exclusive.
System Action:
The request is rejected and procedure $CACALL terminates.
User Action:
Correct the execution of $CACALL and retry.
Reason:
The CAS external interface procedure $CACALL failed during request processing because the current nesting level exceeds the maximum allowed for actions processed via $CACALL.
System Action:
The request is rejected and procedure $CACALL terminates.
User Action:
None.
Reason:
The CAS external interface procedure $CACALL failed during request processing because it was invoked with a value set in variable $LHCRIT1 and a value set in MDO $LHCRIT1. Variable $LHCRIT1 and MDO $LHCRIT1 are mutually exclusive.
System Action:
The request is rejected and procedure $CACALL terminates.
User Action:
Correct the execution of $CACALL and retry.
Reason:
The CAS external interface procedure $CACALL failed during request processing because it was invoked with a value set in MDO $LHCRIT1 and a value set in keyword CRITERIA. MDO $LHCRIT1 and keyword CRITERIA are mutually exclusive.
System Action:
The request is rejected and procedure $CACALL terminates.
User Action:
Correct the execution of $CACALL and retry.
Reason:
Context Services External Interface Package trace is active. This message displays a Context Services trace record.
P1 is the NCL ID.
P2 is the trace ID.
P3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package P1 procedure has terminated in error.
This message is the first of a group of messages that traps the related error. It is followed by a set of CACS0102 messages that describe the error.
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package procedure has terminated in error.
This message is part of a group of messages that describe the error condition. P1 is the error text.
Message CACS0101 was the first message of the group; it identifies the failed request.
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package procedure P1 has terminated due to a run-time error.
Error details are written to the activity log; see messages CACS0102 .
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package P1 procedure has failed due to an unknown error.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package P1 procedure has failed.
P2 is the error text.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package P1 procedure was called with an incorrect parameter.
P2 is the parameter keyword, P3 is the specified value, and P4 is the error text.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package P1 procedure was called with an incorrect parameter list.
The required P2 parameter was not specified.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package P1 procedure was unable to start the Server Process Initiator $CACS10B (front-runner).
P2 is the APPC START verb return code.
P3 is the associated error message.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
The Context Services External Interface package P1 procedure could not locate the Context Server.
P2 was the specified Context Services handle.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
Context Services Server facilities package trace is active. This message displays a Context Services trace record.
P1 is the NCL ID.
P2 is the trace ID.
P3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The Context Services Server Facilities package P1 procedure has terminated in error.
This message is the first of a group of messages that traps the related error. It is followed by a set of CACS0202 messages that describe the error.
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The Context Services Server facilities package procedure has terminated in error.
This message is part of a group of messages that describe the error condition. P1 is the error text.
Message CACS0201 was the first message of the group; it identifies the failed request.
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The Context Services Server Facilities package procedure P1 has terminated due to a run-time error.
Error details are written to the activity log; see messages CACS0202 .
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The Context Services Server Facilities package P1 procedure has failed due to an unknown error.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
The Context Services Server Facilities package P1 procedure has failed.
P2 is the error text.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
The Context Services Server Facilities package P1 procedure was called with an incorrect parameter.
P2 is the parameter keyword, P3 is the specified value, and P4 is the error text.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
Context Services Server Initiator (front-runner) trace is active. This message displays a Context Services trace record.
P1 is the NCL ID.
P2 is the trace ID.
P3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The Context Services Server Initiator has terminated in error.
This message is the first of a group of messages that traps the related error.
P1 is the Context Services Server procedure name.
P2 is the Context Services Server handle.
This message is followed by a set of CACS1002 messages that describe the error.
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The Context Services Server Initiator has terminated in error.
This message is part of group of messages that describe the error condition. P1 is the error text.
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The Context Services Server Initiator has failed.
P1 is the Context Services Server procedure name.
P2 is the Context Services Server handle.
P3 is the error text.
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
The data type specified in P1 requires a length to be specified. This length must be greater than 1 and less than 41.
System Action:
$CACS11S terminates in error.
User Action:
Correct the initiating procedure calling $CACS12I to specify a length field for all CHAR and REMSTR data types. The length must be in the range of 1 to 40.
Reason:
If this list is inactive for more than two hours, the environment is cleared from the host. This ensures unused storage is cleared.
P1 specifies the name of the list displayed.
System Action:
The list processing environment is cleared.
User Action:
Click the tab that displays the name of the list (near the top of the page) to refresh the page, then click Execute to display the list.
If this does not correct the problem, review the Activity Log and look for any other error conditions that may have caused this problem. If the problem persists, contact Technical Support.
Reason:
A request has been made to context services to retrieve data; however, there is no data available.
System Action:
None.
User Action:
Ensure the application using $CACS11S has returned data.
Reason:
If this list is inactive for more than two hours, the environment is cleared from the host. This ensures unused storage is cleared.
System Action:
The list processing environment is cleared.
User Action:
Click the Execute button to refresh the page.
If this does not correct the problem, review the Activity Log and look for any other error conditions that may have caused this problem. If the problem persists, contact Technical Support.
Reason:
The amount of data returned in response to your request is too large for this environment to display.
System Action:
None.
User Action:
Click the Preferences button and reduce the number of items per page, then click Execute.
If the problem persists, contact Technical Support.
Reason:
This message displays an CSVM trace record. It includes the following information:
P1 -Procedure Name
P2 -Processing Phase
P3 -Time
P4 -Date
System Action:
None.
User Action:
Review messages as requested by Technical Support to determine if any delays are occuring during CSVM processing.
Reason:
This message displays an CSVM trace record. It includes the following information:
P1 - Procedure Name
P2 - Processing Phase
P3 - Function
System Action:
None.
User Action:
Review messages as requested by Technical Support to determine if any delays are occuring in CSVM processing.
Reason:
P1 is an invalid call type. Review procedure $CACS12I for more information about the following valid call types:
STARTSERVER
REFRESH
GETDATA
GETSORT
STOPSERVER
MESSAGEGET
MESSAGECLEAR
System Action:
The request terminates.
User Action:
Correct the call type and rerun the procedure.
Reason:
P1 requires a SPROC parameter that specifies the service procedure name for this context environment.
System Action:
The request terminates.
User Action:
Specify the SPROC procedure name and rerun the procedure.
Reason:
The MAXREC value specified in P1 is out of range; it must be a number in the range of 500 to 10000 .
System Action:
The request terminates.
User Action:
Specify a valid MAXREC value.
Reason:
The call type specified in P1 does not have a handle specified.
System Action:
The request terminates.
User Action:
Specify a valid HANDLE value.
Reason:
P1 is invalid; it must be a number greater than 1 .
System Action:
The request terminates.
User Action:
Specify a valid RECSTART value.
Reason:
P1 is invalid; it must be a number greater than 1 and less than 100 .
System Action:
The request terminates.
User Action:
Specify a valid RECLIMIT value.
Reason:
P1 has been used with one of the following mapping paremeters specified:
MAPNAME
MAPSEG
MAPFIELD
System Action:
The request terminates.
User Action:
Specify a valid mapping parameter.
Reason:
P1 must be either NUM or CHAR.
System Action:
The request terminates.
User Action:
Specify a valid MAPDATA parameter.
Reason:
The Trace parameter P1 is invalid; it must be set to one of the following:
0 -Trace messages are logged, detailing time, date, and parameters passed to $CACS12I and $CACS11S.
1 -Trace messages are logged, detailing time, date, passed parameters, and subroutine name.
System Action:
The request terminates.
User Action:
Specify a valid Trace parameter when invoking either $CACS12I or $CACS11S.
Reason:
This message displays an CSVM trace record. It includes the following information:
P1 -Procedure Name
P2 -Processing Phase
P3 -Time
P4 -Date
System Action:
None.
User Action:
Review messages as requested by Technical Support to determine if any delays are occuring during CSVM processing.
Reason:
This message displays an CSVM trace record. It includes the following information:
P1 - Procedure Name
P2 - Processing Phase
P3 - Function
System Action:
None.
User Action:
Review messages as requested by Technical Support to determine if any delays are occuring in CSVM processing.
Reason:
An error occurred attempting to read a PSM definition. In the message:
P1 is the file ID
P2 is the file return code (&FILERC)
System Action:
The procedure terminates.
User Action:
For return code values, see the &FILE GET verb description in the NCL Reference.
Reason:
An error has occured as part of a SYSDB migration action.
System Action:
This message is written to the activity log.
User Action:
This message and an additional diagnostic message (N4D0nn) are written to the activity log. It indicates a product failure, which you should report to your product supplier.
Reason:
An error has occurred as part of a SYSDB migration action.
System Action:
This message is written to the activity log.
User Action:
This message and an additional diagnostic message (N4D0nn) are written to the activity log. It indicates a product failure, which you should report to your product supplier.
Reason:
An error has occured as part of a SYSDB migration action.
System Action:
This message is written to the activity log.
User Action:
This message and an additional diagnostic message (N4D0nn) are written to the activity log. It indicates a product failure, which you should report to your product supplier.
Reason:
An error has occured as part of a SYSDB migration action.
System Action:
This message is written to the activity log.
User Action:
This message and an additional diagnostic message (N4D0nn) are written to the activity log. It indicates a product failure, which you should report to your product supplier.
Reason:
An error has occured as part of a SYSDB migration action.
System Action:
This message is written to the activity log.
User Action:
This message and an additional diagnostic message (N4D0nn) are written to the activity log. It indicates a product failure, which you should report to your product supplier.
Reason:
An error has occured as part of a SYSDB migration action.
System Action:
This message is written to the activity log.
User Action:
This message indicates a product failure, which you should report to your product supplier.
Reason:
No CAS definitions exist for the type indicated ( P1 ) after applying selection criteria.
System Action:
None.
User Action:
None.
Reason:
No CAS definitions exist for the type indicated ( P1 ) after applying selection criteria.
System Action:
None.
User Action:
None.
Reason:
No CAS entity was selected from the prompt list.
System Action:
The request is ignored.
User Action:
Enter a unique entity name or select an item from the list.
Reason:
This message is issued for operations performed between Global Variables in memory and their persistent copies.
P1 is the Global Variable name.
P2 is the operation performed:
P3 is the value of the Global Variable.
System Action:
None.
User Action:
None.
Reason:
An operation is performed on persistent global variables.
P1 is the operation performed:
P2 is the number of persistent global variables affected.
System Action:
The indicated operation was performed on a number of persistent global variables.
User Action:
None.
Reason:
This message displays the values of the Persistent Global Variable.
P1 is the name of the Persistent Global Variable
P2 is the current (in storage) value of the Global Variable.
P3 is the external (persistent) value of the Global Variable.
Note: The values may be different if the Global Variable value is changed after it is loaded from the external storage and not saved.
System Action:
None.
User Action:
None.
Reason:
This message is issued when an error occurs while processing Persistent Variables. It can be issued during object verification or the manipulation phase.
P1 describes the object that is the subject of verification or operation failure. It can be one of the following:
P2 describes the error. The following may be reported:
The following additional information is provided for failed input and output operations:
P3 is the Return Code (RC).
P4 is the Feedback (FDBK), when provided.
P5 is the additional message, when provided.
System Action:
None.
User Action:
Perform corrective action depending on the type of error and the additional information provided.
Contact your local Technical Support if the error is internal.
Reason:
This is a copy of message N15110.
System Action:
None.
User Action:
None.
Reason:
This is a copy of message N15111; however, persistent global variables are marked with # at the beginning.
System Action:
None.
User Action:
None.
Reason:
This is a copy of message N15112 with the following applied:
System Action:
None.
User Action:
None.
Reason:
This is a copy of message N15113; however, P2 specifies the number of persistent global variables in the selection.
System Action:
None.
User Action:
None.
Reason:
This is an exact copy of message N15112; however, the text that appears is the value of the persistent global variable.
The text displays as many characters as fit the screen width; truncation is indicated by ... at the end of the line.
System Action:
None.
User Action:
None.
Reason:
This is the heading line issued in response to a SHOWGLBL (full) or SHOWGLBL Name=varname (selective) command (equated). Subsequent information lines follow.
Persistent global variables are indicated by # preceding their name.
Note: The SHOWGLBL command is defined by the EQUATE command. Another name can be selected by your installation.
System Action:
None.
User Action:
None.
Reason:
This is the first message issued when improper usage of the SHOWGLBL command is detected. It is followed by more messages giving usage details.
System Action:
None.
User Action:
Change the call syntax, using the guidelines provided in the messages that follow.
Reason:
This is one of the messages issued when improper usage of the SHOWGLBL command is detected.
SHOWGLBL without operands lists the names of all global variables used by the region. Names of global variables having persistence are prefixed with #. Four variables are listed per line.
System Action:
None.
User Action:
Change the call syntax to follow the guidelines provided by the messages.
Reason:
This is one of the messages issued when improper usage of the SHOWGLBL command is detected.
SHOWGLBL NAME= lists the global variables with names starting with the given prefix and their values. Variables are listed one per line. If the variable has persistence, the persistent value is displayed in a separate line. If the persistent value is different from the current value, it is displayed in a different color.
System Action:
None.
User Action:
Change the call syntax to follow the guidelines provided by the messages.
Reason:
This is one of the messages issued when improper usage of the SHOWGLBL command is detected.
SHOWGLBL Name=* lists all global variables with their values. Variables are listed one per line. If the variable has persistence, the persistent value is displayed in a separate line. If the persistent value is different from the current value, it is displayed in a different color.
System Action:
None.
User Action:
Change the call syntax to follow the guidelines provided by the messages.
Reason:
No service procedure is specified in the parameter for the panel driver.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Panel does not exist in the library path.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
Requested process has been completed successfully.
System Action:
None.
User Action:
None.
Reason:
Although a save or file was requested, the record is not saved because no changes were made to the definition.
System Action:
None.
User Action:
None.
Reason:
Requested process has been canceled.
System Action:
None.
User Action:
None.
Reason:
Validation found a mandatory field without an entry.
System Action:
The request is rejected.
User Action:
Specify entry on field in error.
Reason:
Invalid option specified on the panel driver menu selection.
System Action:
The request is rejected.
User Action:
Specify a valid option on the menu display.
Reason:
There is no help for the panel being displayed.
System Action:
The request is rejected.
User Action:
Contact System Administrator.
Reason:
The request to save the record definition to the database has been successfully completed.
System Action:
None.
User Action:
None.
Reason:
The command entered is not supported on this screen.
System Action:
Command is rejected.
User Action:
None.
Reason:
The request to create a new record definition has been successfully completed.
System Action:
None.
User Action:
None.
Reason:
The call to the CAS Panel Display API failed because it received an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The long running procedure (server process) P1 performed a $CAPKG:syncServer_Synchronize but it failed because it could not get an exclusive lock, indicating that the server is already running as another process.
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
The long running procedure (server process) P1 was started and the process that started it timed-out waiting for the server to synchronize with it. This could be caused by a problem in the server process. The timout in seconds that was used was P2 .
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
An error occurred starting the long running server process P1 . The return code set by the APPC START verb was P2 . The error message returned from the APPC START verb was P3 .
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
An unexpected condition was encountered whilst processing a $CAPKG:syncServer_Start request. The server procedure that was being started was P1 . The return code set by the lock verb was P2 and the feedback code was P3 .
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
An unexpected condition was encountered whilst processing a $CAPKG:syncServer_Start request. The server procedure that was being started was P1 . The return code set by the lock verb was P2 and the feedback code was P3 .
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
An error occurred starting the procedure P1 . The return code set by the APPC START verb was P2 . The error message returned from the APPC START verb was P3 .
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
The procedure P1 was started and the process that started it timed-out waiting for the procedure to synchronize with it. This could be caused by a problem in the started procedure. The timout in seconds that was used was P2 .
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
An unexpected condition was encountered whilst processing a $CAPKG:syncProcess_Start request. The procedure that was being started was P1 . The return code set by the lock verb was P2 and the feedback code was P3 .
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
An error occurred issuing the DNR SET command. The command and its reposnses are logged following this message.
System Action:
None.
User Action:
Refer to the following messages and deterine the cause of the error.
Reason:
An MDO assignment failed with Return Code 16 and Feedback Code 0. This indicates that the map P1 does not exist in this system.
System Action:
The action terminates.
User Action:
Ensure that the OSCNTL file has been correctly updated during the installation and/or maintenance of this product.
Reason:
An MDO assignment failed. The Return Code was P1 and the Feedback Code was P2. The map and component for which the error occurred was P3.
System Action:
The action terminates.
User Action:
See the NCL Reference for details of the codes.
Reason:
Some system functions are not supported for all operating systems. This includes writing output members to a PDS - not supported for VM.
System Action:
The action is not performed.
User Action:
None. This function is not supported for this operating system.
Reason:
The target member specified already exists and the Replace Member? option was set to NO.
System Action:
The member is not written.
User Action:
Specify a unique member name or change the Replace Member? field to YES.
Reason:
The target file must specify a partitioned dataset.
System Action:
Field is set in error.
User Action:
Specify a partitioned dataset name.
Reason:
This is the first line of a multi-line heading for the simple timer function.
System Action:
None.
User Action:
See the detailed line messages for an explanation of the timer details.
Reason:
This is the second line of a multi-line heading for the simple timer function.
System Action:
None.
User Action:
See the detailed line messages for an explanation of the timer details.
Reason:
This is the first detail line for a simple timer. P1 is the name of the Timer ID that is being displayed. Subsequent lines describe the timer in detail.
System Action:
None.
User Action:
None.
Reason:
This is the second detail line for a simple timer.
P1 indicates the type of the timer, it can be:
AT - The timer is scheduled to run at a specific time of the day on the date(s) that match the timer specification.
EVERY - The timer is scheduled to run after a specific time interval has passed.
P2 is the interval trigger. For an AT timer this is the time of day at which the timer will run on the dates that match the date pattern. For an EVERY timer this is the time interval between successive runs of the timer.
P3 is the limit of the timer, that is, the maximum number of executions that the timer is allowed to run.
P4 is hit cont or the number of times that the timer has actually run.
P5 is the next time the timer is due to run.
System Action:
None.
User Action:
None.
Reason:
This is the third detail line for a simple timer.
P1 shows the command that runs when the timer is triggered. Only the first 100 bytes of the command are shown.
System Action:
None.
User Action:
None.
Reason:
The timer P1 failed because the system could not schedule the timer at P2. The error message received is P3.
System Action:
The timer is deleted and processing continues with the next timer.
User Action:
Contact your local support representative and supply the timer details and when the timer failure occurred.
Reason:
This is a debugging message issued by the simple timer function.
System Action:
None.
User Action:
Collect these messages and send them to the support represenative that requested them.
Reason:
The request to display timers could not be satisified because no timers matched the specified pattern, or if no pattern was specified, then no timers are currently defined.
System Action:
None.
User Action:
None.
Reason:
This is a timer dump display for timer P1. This message is only issued when errors are encountered during timer setting. This message is used by support for debugging purposes.
System Action:
None.
User Action:
Contact your local support representative and supply this timer message and when the timer failure occurred.
Reason:
The request to delete timer P1 failed because the timer does not exist.
System Action:
None.
User Action:
None.
Reason:
The request to delete a timer(s) was successful and P1 timers were deleted.
System Action:
None.
User Action:
None.
Reason:
The SYSDB ID specified ( P1 ) is not allocated or is not a SYSDB data set because one of the following reasons apply:
- The file is not allocated and open.
- The SYSDB ID is not a KSDS.
- The keylength is incorrect. The keylength for a SYSDB is 120.
System Action:
The request is rejected.
User Action:
Specify a valid SYSDB data set ID.
Reason:
The SYSDB ID specified ( P1 ) is open with read-only access. Read-write access is required.
System Action:
The request is rejected.
User Action:
Specify a valid SYSDB data set ID.
Reason:
The SYSDB ID specified ( P1 ) is open but does not have the correct share option. A share option of LSR or RLS was requested, but the file was not opened with either option.
System Action:
The request is rejected.
User Action:
Specify a valid SYSDB data set ID.
Reason:
The SYSDB data set name specified ( P1 ) does not exist or is not a SYSDB data set.
System Action:
The request is rejected.
User Action:
Specify a valid SYSDB data set name and retry.
Reason:
This is a disgnostic message; it contains variable information to use for support issues.
System Action:
None.
User Action:
Collect all of these messages and send them to the support representative that requested the disgnostic process.
Reason:
The region cannot set a z/OS name/token to the indicated value.
p1 identifies the name/token.
p2 is the required value.
p3 is the return code.
p4 is the feedback code.
System Action:
The name/token is not set and is inaccessible to other address spaces on the z/OS system (LPAR).
User Action:
For assistance, contact CA Support.
Reason:
A server could not register for a TCP socket.
p1 identifies the server.
p2 is either a number (requesting a static port on the socket registration) or a z/OS name/token (requesting a random ephemeral port on the socket registration).
p3 is the return code.
p4 is the feedback code.
p5 is the socket error number and vendor-specific error code.
p6 (optional) is a brief description of the error number.
System Action:
The server is temporarily disabled, and another registration attempt is made in 30 seconds.
User Action:
If a port is indicated, then the problem may be that another application is using that TCP port number. Change either the port number used by that application, or the port number configured for the region and the client.
If a token is indicated, then a general problem with the TCP sockets interface exists on the stack, preventing ports from being allocated to new TCP servers. Check the error codes. For assistance, contact CA Support.
Reason:
A server has successfully registered a TCP socket on a port.
p1 identifies the server.
p2 is the port number.
p3 (optional) is the name/token that stores the port number.
p4 is the name of the procedure that handles the incoming connections on the port.
System Action:
None.
User Action:
None.
Reason:
A server failed to accept a TCP connection on a port.
p1 identifies the server.
p2 is a port number.
p3 (optional)is the name/token that stores the port number.
p4 is the return code.
p5 is the feedback code.
p6 is the socket error number and vendor-specific error code.
p7 (optional) is a brief description of the error number.
System Action:
The server is disabled temporarily, and another registration attempt is made in 30 seconds.
User Action:
Check the error codes. For assistance, contact CA Support.
Reason:
A server attempted to APPC-start a servlet procedure but encountered an error.
p1 identifies the server.
p2 identifies the servlet procedure.
p3 is the return code.
p4 (optional) is a message that further describes the error.
System Action:
The specific connection is closed.
User Action:
Check the error codes. For assistance, contact CA Support.
Reason:
A server failed to transfer a TCP connection to a servlet.
p1 identifies the server.
p2 is the TCP socket ID.
p3 is the NCL ID of the servlet process.
p4 is the return code.
p5 is the feedback code.
p6 is the socket error number and vendor-specific error code.
p7 (optional) is a brief description of the error number.
System Action:
The specific connection is closed.
User Action:
Check the error codes. For assistance, contact CA Support.
Reason:
This message displays the following information about a server:
p1 identifies the server.
p2 is the number of connections accepted by the server since starting.
p3 is the time when the server started.
System Action:
None.
User Action:
None.
Reason:
This message displays the total statistics for all connections on a server:
p1 identifies the server.
P2 is the total connections to the server.
p3 is the number of those connections that failed with an error.
p4 is the total number of bytes received for all connections.
p5 is the total number of bytes sent for all connections.
System Action:
None.
User Action:
None.
Reason:
This message contains connection information.
System Action:
None.
User Action:
None.
Reason:
This error message is issued from a server procedure when a socket call fails.
p1 identifies the procedure.
p2 is the return code from the operation.
p3 is the feedback code.
p4 is the socket error number.
p5 identifies the line in the procedure where the call was made.
If further explanation of the error number is available, a second message follows.
System Action:
The servlet procedure is terminated. Most servers restart automatically.
User Action:
Check that the server has restarted.
Reason:
This information message is issued after CAPKG039E and contains a further explanation of the error number if available.
System Action:
The servlet procedure is terminated. Most servers restart automatically.
User Action:
Check that the server has restarted.
Reason:
A socket servlet was started to handle a TCP connection to a server. The connection socket was not transferred to the servlet within a reasonable time limit.
p1 identifies the server.
System Action:
The specific connection is closed.
User Action:
Check the log for other errors. For assistance, contact CA Support.
Reason:
A socket servlet received an unexpected notification message for a socket transfer.
p1 is the name of the server.
p2 is the message received.
System Action:
The specific connection is closed.
User Action:
Check the log for other errors. For assistance, contact CA Support.
Reason:
A servlet failed to accept a socket transfer of a TCP connection from a server.
p1 identifies the server.
p2 is the return code.
p3 is the feedback code.
p4 is the socket error number and vendor-specific error code.
p5 (optional) is a brief description of the error number.
System Action:
The specific connection is closed.
User Action:
Check the error codes. For assistance, contact CA Support.
Reason:
A server is yet to successfully register a TCP socket on a port.
p1 identifies the server.
System Action:
Registration is retried every 30 seconds.
User Action:
Check the job log for error messages.
Reason:
There is no log data available to display.
System Action:
None.
User Action:
None.
Reason:
The CLEAR command was actioned and the log is clear.
System Action:
None.
User Action:
None.
Reason:
Refresh operation requested but both active and saved values are identical.
System Action:
None.
User Action:
None.
Reason:
Update operation resulted in value not changed.
System Action:
None.
User Action:
None.
Reason:
Operation P1 cancelled.
System Action:
None.
User Action:
None.
Reason:
Variable selected for update is being updated by P1.
System Action:
None.
User Action:
Coordinate your update with the user listed by the message.
Reason:
Procedure providing persistent variables services failed with RC=8. P1 is the accompanying message.
System Action:
None.
User Action:
Investigate possible I/O problems, and check the activity log for more details. If Internal Error reported, contact local Technical Support with log details.
Reason:
An unrecognized shortcut or command was entered.
System Action:
None.
User Action:
Enter a valid shortcut, menu option, panel path, or command.
Note: The following documentation assumes that shortcuts are enabled and preceded with a /, which is the default shortcut character. The shortcut character is defined in the PMENUCONTROL parameter group, and can be set to something other than a / or disabled. When enabled, the Primary Menu displays the shortcut character on the right of the title line (for example, SCHAR=/).
Enter a shortcut name, preceded by a slash, at the ===> prompt (for example, /levels, /parms, or /ipmon).
This takes you directly to the function.
To see a list of all shortcuts and their associated functions, enter a single slash (/) at the ===> prompt. Select the desired shortcut from the list by entering S next to it.
If a shortcut exists for a menu option, it is displayed in turquoise to the right of the option description.
You can also combine shortcuts with menu options (for example, /bcast.s or =/bcast.s).
You can invoke shortcuts in two ways:
To retain and nest the current screen level, use a nested shortcut:
/shortcut_name
Exiting brings you back to the last nested screen in this window. You can next screens to a maximum of 64 levels.
To close all currently nested screen levels, use a shortcut skip:
=/shortcut_name
Exiting takes you back to the Primary Menu.
If you no longer need any nested screens, a shortcut skip saves storage and resources.
(If you are currently at the Primary Menu, a nested shortcut and a shortcut skip behave the same.)
Each menu option is identified by a one- to three-character option string, displayed in yellow.
Enter the option you want at the ===> prompt.
Like shortcuts, panel paths move directly to a function without having to access each submenu between it and the current menu. A panel path consists of multiple menu options separated by periods (for example =U.M).
Also, like shortcuts, the = sign functions as a skip character, closing all nested screens and effectively entering the path from the Primary Menu. (If you are currently at the Primary Menu, the skip character is not required.)
Frequently used panel paths have associated shortcuts. If you do not remember a shortcut, enter / at the ===> prompt for a list. Select one from the list, or enter it at the ===> prompt.
There is no difference between accessing a function using a panel path skip or a shortcut skip, although the shortcut should be easier to remember. Both methods close the current screen and go straight to the function.
Entering == at the ===> prompt from any panel closes all nested screens and returns you to the Primary Menu.
Reason:
An invalid scroll amount was specified. Valid scroll amounts are CSR, DATA, HALF, MAX, PAGE or a number between 1 and 9999.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a valid value in the scroll field.
Reason:
This is a prompt message which is displayed to allow the user to verify that the selected actions are correct before they are carried out.
System Action:
None.
User Action:
Press the ENTER key to execute the highlighted selections, or press the CANCEL function key to cancel the requested actions.
Reason:
Action P1 was entered but could not be processed because of one of the following reasons:
The action may be valid on other lines. This display may contain lines at different levels of hierarchy, such as headings, subheadings, and data. Lines may also present data from very different functions. Because of this, actions that work on one line may not make sense on another.
The HLP (Help) action is available on every line. Alternatively, use F1=Help with the cursor on the required line.
Pressing Enter , with the cursor anywhere on a line, invokes the default action for that line. This is particularly useful with expandable and collapsable lines.
System Action:
The valid list of supported actions is presented. You should choose an action from this list.
User Action:
Check that you have not mistyped the action or entered it on an incorrect line.
Select an action from the list of valid actions presented.
Use the online help for more information about available actions.
Reason:
A user request failed and the process did not return to the caller. The viewer waited up to 5 seconds but no response was received.
System Action:
Action is terminated and processing continues.
User Action:
Check the log for any error messages and retry the request.
Reason:
A user requested the FIND command but specified invalid parameters. The valid syntax for the find command is:
FIND string {NEXT|PREV|FIRST|LAST} ----
The string can be specified as a single string with no imbedded blanks or a quoted string with imbedded blanks or other special characters. The default find option is NEXT. The valid abbreviations for FIND are: F, FI and FIN.
System Action:
Command is rejected.
User Action:
Correct the syntax and re-issue the command.
Reason:
A user requested the Locate command but specified invalid parameters. The valid syntax for the locate command is:
LOCATE key [NEXT|PREV|FIRST|LAST]
The key can be specified as a single string with no imbedded blanks or a quoted string with imbedded blanks or other special characters. The default locate option is NEXT. The valid abbreviations for LOCATE are L, LO, LOC, LOCA and LOCAT.
Once a locate command has been specified, then specifying locate without parameters will do the same locate from the next key position.
System Action:
Command is rejected.
User Action:
Specify a complete locate command.
Reason:
A user requested the Locate command but specified invalid parameters. The valid syntax for the locate command is:
LOCATE key NEXT|PREV|FIRST|LASTÙ ----
The key can be specified as a single string with no imbedded blanks or a quoted string with imbedded blanks or other special characters. If you do NOT want the key to be automatically uppercased then specify it as:
c'key'
The default locate option is NEXT. The valid abbreviation for LOCATE is L.
System Action:
Command is rejected.
User Action:
Correct the syntax and re-issue the command.
Reason:
A user request to locate the key P1 in the display completed successfully.
System Action:
The display is positioned with the located record as the first line on the display.
User Action:
None.
Reason:
The repeat locate command was entered and the locate position is already at the last set of key ranges in the display.
System Action:
None.
User Action:
You can repeat locate to have the locate begin at the first key range.
Reason:
The repeat locate command was entered and the locate position is already at the top set of key ranges in the display.
System Action:
None.
User Action:
You can repeat locate to have the locate begin at the last key range.
Reason:
A user requested the FIND command but specified invalid parameters. The valid syntax for the command is:
FIND string [NEXT|PREV|FIRST|LAST]
The string can be specified as a single string with no imbedded blanks or a quoted string with imbedded blanks or other special characters. The default find option is NEXT. The valid abbreviations for FIND are: F, FI and FIN.
Once a find command has been specified, then specifying find without parameters will do the same find from the next cursor position.
System Action:
Command is rejected.
User Action:
Specify a complete find command.
Reason:
A user requested the Locate command but specified invalid parameters. The valid syntax for the locate command is:
FIND string NEXT|PREV|FIRST|LASTÙ ----
The string can be specified as a single word with no imbedded blanks or a quoted string with imbedded blanks or other special characters. If you do NOT want the string to be automatically uppercased then specify it as:
c'string'
The default find option is NEXT. The valid abreviation for FIND is F.
System Action:
Command is rejected.
User Action:
Correct the syntax and re-issue the command.
Reason:
A user request to find the string P1 in the display completed successfully.
System Action:
The display is positioned with the found string visible on the display and the cursor on the first character of the string.
User Action:
None.
Reason:
An invalid widget share prefix was defined for a widget. Valid shares must be at least 3 characters long and cannot start with @ or #. P1 is the share specified.
System Action:
Widget viewer terminates.
User Action:
Contact Technical Support.
Reason:
The default selection option '/' is not valid on this line because the line has no default option.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the selection option and retry.
Reason:
The zoom selection option is not valid on this line because the line does not define a zoomable presentation component.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the selection option and retry.
Reason:
The expand/collapse selection option is not valid on this line because the line does not define an expandable/collapsable presentation component.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the selection option and retry.
Reason:
A presentation component could not be displayed because it is a remote component and the system on which it is located is not active or the link to that system is not active. The remote system is P1.
System Action:
None.
User Action:
Ensure that the remote system and the links to that system are active.
Reason:
The bottom of data was reached when trying to find a string specified with the Find command.
System Action:
None.
User Action:
To continue the search press the Find function key. The search will continue from the top.
Reason:
The top of data was reached when trying to find a string specified with the Find command.
System Action:
None.
User Action:
To continue the search press the Find function key. The search will continue from the bottom.
Reason:
A request to find characters stopped because the search limit was reached. P1 is the number of lines searched since the search was initiated.
System Action:
Searching stops.
User Action:
Repeat the find command without any parameters or press the Find function key to continue the search. The search continues from where it finished last.
You can use the FPROMPT command to change the number of lines searched before this message is re-issued. The FPROMPT command has the following syntax:
FPROMPT [ 0 | NO | OFF | DFLT | DEFAULT | number ]
You can turn off the find prompt message by using the 0 or NO or OFF parameters with the command. Specifying DFLT or DEFAULT resets the current setting to the system default. Specify a number to set the maximum number of records to search before the prompt message is issued. If no parameters are passed, a message is issued indicating the current setting.
Reason:
The text P2 was not found. The total number of records searched was P1.
System Action:
The find command terminates.
User Action:
None.
Reason:
An APPC error occurred attempting to remotely execute a procedure on system P1. The error may be link-related or the target procedure failed during execution. P2 provides more information about the error; however, you should check the log for all related error messages that fully describe the error.
System Action:
Processing terminates.
User Action:
Check the log for more details about the cause of the problem. The following are the most common problems:
- The link specified in P1 is not defined or does not support APPC.
- The target procedure does not exist on the remote system. This may be due to incompatible versions or the function attempted is not available on the remote system
- The target procedure terminated in error on the remote system.
The log messages assist in determining what the actual cause is and what further action may be required.
Reason:
The maximum number of lines searched for a find command before a prompt is issued is set to P1.
System Action:
None.
User Action:
None.
Reason:
The maximum number of lines searched for a find command before a prompt is issued has been turned off. Prompting will not occur for the find command.
System Action:
None.
User Action:
None.
Reason:
The parameter to the FPROMPT command is invalid. It must be a number between 100 and 9999999999.
System Action:
Command rejected.
User Action:
Correct the paramter and retry the command.
Reason:
The maximum number of entries that could be selected on this list was exceeded. The maximum is P1.
System Action:
The list is redisplayed with fields set in error.
User Action:
Reduce the number of selected entries to be less than or equal to the maximum, and retry.
Reason:
The user pressed the CANCEL key or entered the CANCEL command, and the function was canceled.
System Action:
The function is terminated.
User Action:
None.
Reason:
You tried to expand an expandable/collapsable presentation component. However, there were no lines to display.
System Action:
None.
User Action:
None.
Reason:
The number of widglets contained within a widget has exceeded the system maximum of P1. The ID identifies the current widget being processed and consists of package P2, class P3 and name P4.
System Action:
Processing is terminated.
User Action:
Please contact your local support representative.
Reason:
An invalid action was used to select an item from a list of valid values.
System Action:
Field is set in error.
User Action:
Use the S, Q or / action to select the required value from the list.
Alternatively you can place the cursor beside the required value on the list and press the enter key; this automatically selects the item from the list.
Reason:
A request to load the Command Handler Commands failed because another user was already loading the commands. The other user was P1 .
System Action:
The request is rejected.
User Action:
Retry the request later.
Reason:
The Command Handler failed to load the commands because the vartable that contains the command tables was in error. The feedback code from the GET operation was P1.
System Action:
Procedure $CACM000 terminates.
User Action:
This condition can occur if the NCL/CAS environment has not been initialized successfully. Ensure that NCL/CAS initialized successfully; if so, contact your system administrator. Ensure that the installation was performed as stated in the installation instructions because the cause of the error may be due to incorrect installation.
Reason:
The commands and menu shortcuts were successfully loaded in the region, and are now available for use.
System Action:
None.
User Action:
None.
Reason:
The P2 menu shortcut, P1 , was not loaded because a shortcut of the same name already existed.
System Action:
The loading of shortcuts continues.
User Action:
Rename this or the other duplicated shortcut.
Reason:
The value identified by P1 is not a valid COMMAND or SHORTCUT .
System Action:
None.
User Action:
Correct the shortcut or command and retry.
COMMANDS
To see a list of all valid CAS Commands enter the shortcut /CAS.L at the ===> prompt.
SHORTCUTS
Enter a shortcut name, preceded by a slash, at the ===> prompt (for example, /LEVELS or /INFO). This will take you directly to the function.
To see a list of all shortcuts and their associated functions, enter a single slash (/) at the ===> prompt. Select the desired shortcut from the list by entering 'S' beside it.
If a shortcut exists for a menu option, it is displayed in turquoise, on the same line as the option description.
Shortcuts may also be combined with menu options (for example, /CAS.CM)
Shortcuts can be invoked in two ways:
1. A 'nested' shortcut
2. A shortcut skip
To retain and nest the current screen level, use a nested shortcut:
/shortcut_name
Exit will bring you back to the last nested screen in this window. Screens may be nested to a maximum of 64 levels.
To close all currently nested screen levels, use a shortcut skip:
=/shortcut_name
Exit will take you back to the Primary Menu. If you no longer need any nested screens, a shortcut skips saves storage and resources.
If you are currently at the Primary Menu, a nested shortcut and a shortcut skip behave the same.
Entering == at the ===> prompt from any panel closes all nested screens and returns you to the Primary Menu.
Reason:
A request to get a criteria failed because the criteria definition is not defined. The criteria to access belongs to application ID P1 , its type is P2 , its owner's user ID if private is P3 , and its name is
P4 .
System Action:
The request is rejected.
User Action:
Specify a criteria definition previously defined and retry.
Reason:
A request to recall a criteria was rejected because the Criteria panel was to be displayed and the request was not invoked from a full-screen environment.
System Action:
The request is rejected.
User Action:
Invoke the request from a full-screen environment.
Reason:
A request to recall a criteria failed because the criteria definition is not defined. The criteria to recall belonged to application ID P1 , with type P2 , and owner's user ID (if private) P3 , and name P4 .
System Action:
The request is rejected.
User Action:
Specify a criteria definition previously defined and retry.
Reason:
A request to recall a criteria failed because the criteria exit procedure for the criteria was not found in the procedure library. The name of the procedure was P1 .
System Action:
The request is rejected.
User Action:
Correct the criteria exit procedure name in the criteria definition, or create the procedure and retry.
Reason:
A request to recall a criteria failed because the criteria exit procedure returned an invalid return code. The name of the procedure was P1 and the invalid return code was P2 .
System Action:
The request is rejected.
User Action:
Correct the setting of the return code by the criteria exit procedure and retry.
Reason:
A request to recall a criteria failed because the criteria exit procedure returned a return code that was not valid for the option set in variable &$CROPT. The value of variable &$CROPT was P1 and the name of the procedure was P2 .
System Action:
The request is rejected.
User Action:
Correct the setting of the return code by the criteria exit procedure and retry.
Reason:
A request to recall a criteria failed because the criteria exit returned a return code that was not valid for the command set in variable &$CRCOMMAND. The value of variable &$CRCOMMAND was P1 and the name of the procedure was P2 .
System Action:
The request is rejected.
User Action:
Correct the setting of the return code by the criteria exit procedure and retry.
Reason:
During a request to recall a criteria, the criteria exit set return code
P1 and did not set variable $SYSMSG to an error message. The name of the procedure was P2 .
System Action:
None.
User Action:
Correct the criteria exit procedure to set &SYSMSG to an error message and retry.
Reason:
Function key P1 was pressed and the command assigned to it is invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
A request to recall a criteria was rejected because a run time panel was to be displayed and the request was not invoked from a full-screen environment. The criteria belonged to appl ID P1 , type was P2 , owner's user ID (if private) was P3 , and name was P4 .
System Action:
The request is rejected.
User Action:
Invoke the request from a full-screen environment.
Reason:
The user ID P1 is not authorized to use the Network Control System.
System Action:
The request is rejected.
User Action:
Contact your System Administrator if the function is required.
Reason:
You entered the P (APING) action against a line entry for a virtual node.
System Action:
The action field in error is highlighted.
User Action:
Blank the action field in error. Enter the P action against real hosts, for example, type BN, NN, or EN.
Reason:
A character string was not specified on the find command.
System Action:
The command is rejected.
User Action:
Enter the character string to be found with the find command and retry.
Reason:
The specified character string was not found in the data.
System Action:
None.
User Action:
None.
Reason:
The end of the data was reached before finding the specified character string.
System Action:
None.
User Action:
Press the Find key to continue the search from the top/bottom of the data.
Reason:
An attempt to access the NETINFO failed because it was unavailable. The return code (P1) indicates the cause.
System Action:
None.
User Action:
Determine if the file should be available and if so, why it isn't. The meaning of the return code can be found in NCL Reference.
Reason:
The select action specified was invalid. Possible reasons are:
* The action is not defined * The action is not applicable to the selected line for the reason shown ( P1 )
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the selection action and retry. Valid actions are listed in the function help which can be obtained by pressing the F1 key.
Reason:
Configuration details were requested from an NCS display but the NCS Configuration Details Service procedure ($NCCNFG) cannot be located.
System Action:
No configuration details are available.
User Action:
Refer to your systems administrator as the service procedure, $NCCNFG, may be in a library that is not included in your COMMANDS concatenation.
Reason:
The text string specified in the FIND command was found. The cursor is positioned at the beginning of the text string.
System Action:
None.
User Action:
None.
Reason:
The command specified was invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the command and retry. Valid commands are listed in the function help which can be obtained by pressing the F1 key.
Reason:
The resource name specified P1 is unknown to VTAM.
System Action:
None.
User Action:
Specify a correct resource name and retry.
Reason:
The value supplied for the field ( P1 ) has an incorrect syntax or value Possible causes are:
* For the Node Name or Node/CP Name field
- The field contains embedded blanks
- The field is not a valid node (resource) name. Node names may be either:
1) A 1-8 character non-qualified name (for example, TERM01)
2) A network-qualified name in the form netid.node where the netid and node parts are each 1-8 character values separated by a full stop (period) without spaces (for example, NET01.TERM01). The The netid value can also be expressed as an asterisk (*).
Note: Network-qualified names are not supported for the List SNA Resources (/SNADIAG.L) option. You must use a non-qualified name. A trailing asterisk is permitted and is assumed if omitted, and the name is less than 8 characters.
* For the Resource Type field
- Valid values are XCF, TCP, or MPC
* For the Link Name field
- The field contains embedded blanks
System Action:
None
User Action:
Review the full-screen help for the panel, correct the value, and retry.
Reason:
The NCS list handler service procedure $NCGP02L failed because it received an invalid value for a shared variable. The variable name was P1 and its value was P2 .
System Action:
Procedure $NCGP02L 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 NCS list handler service procedure $NCGP02L failed because an unexpected message was returned from a SHOW LINKS command. The message ID was P1 and it has been written to the log.
System Action:
Procedure $NCGP02L terminates.
User Action:
Contact the system administrator. Browse the activity log for the message ID and review the description of that message. If necessary contact your product supplier.
Reason:
The "D" selection line command was entered against the entry for the linkname P1 but this had not been previously selected.
System Action:
The command is ignored.
User Action:
Only entries marked as ** SELECTED ** may be deselected.
Reason:
You have exited from the INMC Links Selection List without selecting any systems. The local system is automatically selected by default.
System Action:
None, warning message only.
User Action:
If you intend using any of the summary displays and do not want the local system to be the only system included in the displays you should respecify your choice(s) from the list. The local system may be excluded (deselected) in which case at least one other system must be selected.
Reason:
You have selected an INMC link which is not active.
System Action:
The selection is ignored.
User Action:
Correct the error and retry. If necessary determine why the link is not active.
Reason:
The VTAM D DIRECTRY command is supported on Network Nodes only. The following message was received:
IST1258I D DIRECTRY IS NOT VALID FOR p1
System Action:
None.
User Action:
Choose a link for a system that is configured as a Network Node.
Reason:
The resource (node) name was not specified.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Specify a resource (node) name and retry.
Reason:
The node name specified was more than 8 characters. This error should not occur if the node name was entered on the NCS Node display panel. However it may occur if the Graphic Node display procedure is called from another source specifying an invalid name, for example use of the DG command from OCS or Command Entry.
System Action:
The cursor is placed in the field in error, the field is highlighted, and the name truncated to 8 characters.
User Action:
Specify a correct node name and retry.
Reason:
The description for a resource status code was selected but the resource selected has no associated status.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
None.
Reason:
The X selection option has been used to display a cross-domain resource in the home domain. The home domain is unavailable because either:
1. The selection has been made against a node which forms part of the hierarchical display which is invalid. The option is only available for nodes in the scrollable subordinate nodes list on the left hand side of the display
2. The INMC link to the NetMaster for SNA system that resides on the home domain has not been selected.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
If the selection was made against an entry in the node hierarchy clear the selection and make another selection.
If the selection was made against an entry in the list of subnodes the INMC link must be selected. To do this you must exit the display and go to the NCS Primary Menu, select the INMC Link Selection option and select the appropriate INMC link(s).
Reason:
The description for a resource status code was selected but there is no description on the NETINFO database.
System Action:
None.
User Action:
None.
Reason:
The NCS NETINFO Database Access procedure ($NCINFO) was called to read a record but a VSAM file error occured (FILERC=8). The VSAM feedback Code ( P1 ) and file key ( P2 ) are shown.
System Action:
Procedure $NCINFO terminates with return code 8.
User Action:
Use the VSAM Feedback code to determine the exact cause of error, correct the NETINFO file allocation or calling procedure and retry.
Reason:
The NCS NETINFO Database Access procedure ($NCINFO) was called to read a record but a file error occured. The file return Code (FILERC= P1 ) and system message ( P2 ) are shown.
System Action:
Procedure $NCINFO terminates with return code 8.
User Action:
Use the return code and message to determine the exact cause of error, correct the NETINFO file allocation or calling procedure and retry.
Reason:
There are no configuration details for the specified node ( P1 ).
System Action:
No configuration details are available.
User Action:
None.
Reason:
Configuration details were requested from an NCS display but the NCS Configuration Details Service procedure ($NCCNFG) has been unable to obtain details from the Configuration system, and no other message is available.
System Action:
No configuration details are available.
User Action:
Refer to your systems administrator as the service procedure, $NCCNFG, may have been updated for your site's requirements.
Reason:
The NCS Configuration Details Service procedure ($NCCNFG) has attempted to call another procedure to supply configuration details but the procedure ( P1 ) cannot be located.
System Action:
No configuration details are available.
User Action:
Refer to your systems administrator as the specified procedure may be in a library that is not included in your COMMANDS concatenation.
Reason:
Configuration details were requested from an NCS display but the NCS Configuration Details Service procedure ($NCCNFG) has been unable to obtain details because the INFO/MASTER configuration system details are incomplete.
System Action:
No configuration details are available.
User Action:
Refer to your systems administrator as the Configuration Database system to be used by NCS has not been set up correctly.
To access an INFO/MASTER system you must have the INFO/MASTER system, category and NDB name set up. These are defined in the following global variables:
&&000$NCSCSYS - INFO/MASTER System
&&000$NCSCCAT - INFO/MASTER Category
&&000$NCSCNDB - INFO/MASTER NDB name
These variables are normally initialized in the NMINIT or $NSINIT procedure by your systems administrator.
Reason:
The NCS External Interface procedure, $NCXTRNL, has been called to process the option ( P1 ) but this option is not supported.
System Action:
The request is rejected.
User Action:
Contact your product supplier.
Reason:
The node name specified ( P1 ) is unknown to VTAM (or VTAM-G).
System Action:
None.
User Action:
Specify a correct node name and retry.
Reason:
The NCS Recycle procedure was called without specifying a node name. This is required.
System Action:
The request is rejected.
User Action:
Correct the command and retry.
Reason:
The NCS Recycle procedure timed out while attempting to activate or inactivate the indicated network node. The necessary responses have not been received from VTAM.
P1 identifies the network node.
P2 indicates the action: ACTIVATE or INACTIVATE.
System Action:
The request is rejected.
User Action:
Retry.
If the problem persists, contact your network systems administrator. This may be due to a congested network or to a new release of VTAM.
Reason:
The node name specified ( P1 ) is unknown to VTAM (or VTAM-G).
System Action:
None.
User Action:
Specify a correct node name and retry.
Reason:
The node name ( P1 ) has been sucessfully recycled and is now active.
System Action:
None.
User Action:
None.
Reason:
An attempt to recycle a network node ( P1 ) has failed as an unexpected message ( P2 ) has been received.
System Action:
The node is not recycled.
User Action:
Contact your network systems administrator.
Reason:
VTAM has accepted the request to inactivate a network node ( P1 ) and inactivation is in progress.
System Action:
The recycle process continues.
User Action:
None.
Reason:
VTAM has sucessfully inactivated a network node ( P1 ) and activation is now in progress.
System Action:
The recycle process continues.
User Action:
None.
Reason:
The NCS Display Graphic procedure was called without specifying a node name. This is required.
System Action:
The request is rejected.
User Action:
Correct the command and retry.
Reason:
A request was made to display an APPN Directory Entry from a system that is running on an Operating System P1 for which there is no APPN support by either the related VTAM product, or the NetMaster version.
The error occurs when the SOLVE system is not running on an IBM OS/390 (z/OS) or VM (z/VM) operating system.
This may apply to either the local system, or, if an INMC Link Name was specified, to the remote system for that link.
System Action:
The request is rejected.
User Action:
Correct the NetMaster system name (INMC Link Name) and retry.
Reason:
The name specified P1 is unknown to VTAM as a Directory Entry.
System Action:
None.
User Action:
Specify a correct node name and retry.
Reason:
The NCS List Handler service procedure $NCND16L failed because it received an invalid value for a shared variable. The variable name was P1 and its value was P2.
System Action:
Procedure $NCND16L terminates.
User Action:
Contact your system 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:
A request was made to display APPN Topology data from a system that is running on an Operating System P1 for which there is no APPN support by either the related VTAM product, or the NetMaster version.
The error occurs when the SOLVE system is not running on an IBM OS/390 (z/OS) or VM (z/VM) operating system.
This may apply to either the local system, or, if an INMC Link Name was specified, to the remote system for that link.
System Action:
The request is rejected.
User Action:
Correct the NetMaster system name (INMC Link Name) and retry.
Reason:
The NCS List Handler service procedure $NCND20L failed because it received an invalid value for a shared variable. The variable name was P1 and its value was P2.
System Action:
Procedure $NCND20L terminates.
User Action:
Contact the system 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 selected action is not valid on this line. The first line in the list is the Origin Control Point. Subsequent lines are Destination Control Points that are adjacent to the Origin. Possible causes for this error are:
Option A (Display Adjacent Control Points) * Not to be used on the first line in the list as it would provide the same list as is currently displayed. Note: Use the F6 key to refresh the list.
* Only valid if the adjacent Control Point is a Network Node (NN).
Option TG (Display Transmission Group Attributes) * Not to be used on the first line in the list as it is used to display attributes of the Transmission Group between the Origin Control Point (the first line on the display) and a nominated Destination Control Point.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
The D NET,APING function is not supported by this VTAM.
System Action:
None.
User Action:
None.
Reason:
A request for APING information failed with the sense code P1 .
System Action:
None.
User Action:
Use the sense code to determine the cause of the error.
Reason:
A request for APING information completed for node P1 . The session allocation took P2 milliseconds. The data echo times (minimum/average/ maximum) are shown in milliseconds as P3, P4, P5 respectively.
System Action:
None.
User Action:
None.
Reason:
An ALS command has specified a name that is not in the list of adjacent link stations for this logical unit.
System Action:
None.
User Action:
Check that the name specified appears in the ALS column of the session list.
Reason:
A request to list CP-CP sessions failed. No adjacent nodes have CP-CP sessions with this local node.
System Action:
None.
User Action:
None.
Reason:
A request to list an adjacent CP's connections to the local node failed. No transmission group connections were found.
System Action:
None.
User Action:
None.
Reason:
A request to list resources has failed. No resources match the specified prefix ( P1 ).
System Action:
None.
User Action:
Correct the resource name (prefix) and retry.
Reason:
The specified action is not valid on this line. Possible causes for this error are:
Option P (APING) * The resource is not an APPN resource.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
A request to list RTP pipes has failed. If the list was qualified by CPname, then there are no RTP pipes for the specified CPname. If the list was not qualified, then there are no RTP pipes active.
System Action:
None.
User Action:
If using /RTP then review the HPR options for VTAM and APPN connection PUs. Issue command D VTAMOPTS,OPTION=HPR to check that the VTAM default is to support HPR.
If listing RTP pipes for a CP or connection, display the PU and review the High Performance Routing setting. If HPR is enabled, idle connections can be automatically closed by coding DISCNT=DELAY for the PU or model PU for dynamic connection PUs.
In some situations a configuration error may result in unwanted CP connections. Review the requirements for CP connections and modify the network configuration accordingly.
Reason:
A request to display an RTP pipe ( p1 ) failed. When the VTAM resouce was displayed, it was not identified as an RTP, or it no longer exists.
System Action:
None.
User Action:
Contact your product supplier. Provide the following diagnostic information: 1. Output from D RTPS command 2. Output from display of specific pipe(s), that is, D p1 command.
Reason:
The specified action is not valid on this line. Possible causes for this error are:
Options DA (Display) and SA (Select) Adjacent Link Station * The Adjacent Link Station could not be determined. This is only available in OS/390 V2R10 and later.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
A request to list TRL entries has failed. If the list was qualified by control type, then there are no TRL entries for the specified type. If the list was not qualified, then there are no TRL entries defined.
System Action:
None.
User Action:
If a Control Type was specified, specify another type and retry.
Reason:
A request to display an TRL entry ( p1 ) failed. When the VTAM resouce was displayed, it was not identified as a TRLE, or it no longer exists.
System Action:
None.
User Action:
Contact your product supplier. Provide the following diagnostic information: 1. Output from D TRL command 2. Output from display of specific TRL entry(s), that is, the D TRL,TRLE= p1 command.
Reason:
The specified action is not valid on this line. Possible causes for this error are:
XCF options (DX, SX, AX, and PX) which apply to the XCF Adjacent CP * The TRL Control Type is not XCF, or the Adjacent Control Point has not been determined.
ULPID options (DU, SU, AU, and PU) which apply to the ULPID CP Name * The Upper Layer Protocol Control Point has not been determined.
System Action:
None
User Action:
Correct the error and retry.
Reason:
Expected APING results were not received from the internal command interface.
System Action:
None
User Action:
Review the panel input for any logical errors, and retry the command in manual mode. If manual mode works, report the problem to the developer.
Reason:
The value supplied for the field ( P1 ) has an incorrect syntax or value. Possible causes are:
* For the Resource Name field
- The field contains embedded blanks.
- The field is not a valid node (resource) name. Node names can be either:
1) A 1-8 character non-qualified name (for example, TERM01)
2) A network-qualified name in the form netid.node where the netid and node parts are each 1-8 character values separated by a period, without spaces (for example, NET01.TERM01). The netid value can also be expressed as an asterisk (*).
* For the Count field
- The field is not a valid number or is greater than 999. Default is 3 if the field is left empty.
* For the Packet Count field
- The field is not a valid number or is greater than 32763. Default is 1 if the field is left empty.
* For the Packet Size field
- The field is not a valid number, or is greater than 32763 or less than 1. Default is 100 if the field is left empty.
* For the ECHO field
- The field must be empty or YES or NO. YES is the default.
System Action:
None
User Action:
Review the full-screen help for the panel, correct the value, and retry.
Reason:
A request to list DLURs has failed as there are no DLURs defined.
System Action:
None.
User Action:
None.
Reason:
A request to list Major Nodes or Pending Nodes ( P1) failed as there are no nodes that match the specific type.
System Action:
None.
User Action:
If a CPname was specified, specify another CPname and retry.
Reason:
A request to provide a summary list of a given major node type ( P1 ) failed as there are no nodes that match that type.
System Action:
None.
User Action:
If a CPname was specified, specify another CPname and retry.
Reason:
An action was entered next to a line reserved for totals. Actions are only valid against data lines, that is, those with resource names.
System Action:
None.
User Action:
If a CPname was specified, specify another CPname and retry.
Reason:
A SNANMI request to the SOLVE SSI failed with a USS error.
P1 is the USS function name, for example, BPX1CON, BPX1SND, BPX1RCV. P2 is the USS return code.
P3 is the USS reason code.
System Action:
The request fails.
User Action:
Use the USS return and reason codes to determine the error:
BPX1CON RC=0000081 RSN=****006C USS Connection to VTAM SNANMI failure This indicates a problem with the SNAMGMT API of VTAM.
Check that SNAMGMT option is active.
For all other errors, contact Technical Support.
Reason:
The SNANMI interface between the SOLVE SSI and VTAM has terminated.
P1 is the SNANMI return code from the termination call.
P2 is the SNANMI reason code from the termination call.
System Action:
The request fails.
User Action:
Use the return and reason codes to determine the error. Typically, return and reason codes of zero indicate an orderly shutdown of the interface.
Reason:
A SNANMI request issued from the SOLVE SSI has failed.
P1 is the return code from the SNANMI call.
System Action:
The request fails.
User Action:
SUBTASKUNAVAIL - The SNANMI subtask is inactive in the SSI. Ensure that the VTAM option SNAMGMT is active and the PKTANALYZER and SNANMI options are set to YES in the SSI configuration.
For all other errors, contact Technical Support.
Reason:
EE Data Sampling has detected that an EE session to a particular CPname has been restarted within the last data sampling interval.
Any retransmission packet counts that may have occurred on the earlier terminated session will be lost.
System Action:
None. This is an informational message only.
User Action:
Any retransmission packet counts reported by this CPNAME in the last interval may not be accurate. Packet counts pertaining to the previous terminated session after the last sampling call are indeterminate.
Reason:
A Data Sampling error occurred on attribute P1. P2 notes the reason for the sampling error.
System Action:
The data sampling procedure sets a null value and an error message for the attribute. In addition, this message CSAP2905 is logged to the transient log.
User Action:
Investigate the reason for the sampling error, based on the associated error message and the transient log entry.
Reason:
The system has limited the number of EEI connections being monitored. There are P2 known EEI connections. Only the busiest P1 connections are monitored in BYCP attributes in data sampling.
System Action:
When there is no CPname filtering in effect and there are excessive EEI records, the system limits the BYCP attributes sampled by returning only the busiest P1 connections. The unqualified and BYVIPA attributes are set from all connections, irrespective of any limit or CPname filtering. This message will only be issued once or after any user change in the limit value.
User Action:
One of the following actions can be performed:
Reason:
An APPC request to the remote system identified by P1 failed; the INMC link name ( P1 ) does not exist.
System Action:
The request is ignored.
User Action:
Use the SHOW LINKS command to verify INMC Link names and status.
Reason:
An APPC request to the remote system identified by P1 failed; the INMC link name ( P1 ) is not active - the current status is P2
System Action:
The request is ignored.
User Action:
Use the SHOW LINKS command to verify INMC Link names and status.
Reason:
An APPC request to the remote system identified by P1 failed. The remote system is running a back-level version which does not support the type of request. The minimum requirement is P2 .
System Action:
The request is ignored.
User Action:
None.
Reason:
A function identified by P1 failed on the indicated region ( P2 ) for the reason shown ( P3 ).
System Action:
The request is ignored.
User Action:
None.
Reason:
An APPC request to the remote system identified by P1 failed with return code P2 and feedback code P3 .
System Action:
An additional error message may be written to the activity log if RC=16.
User Action:
Contact your System Administrator.
Reason:
Predefined time out expired while waiting for consecutive message from D APING VTAM command.
System Action:
The request is ignored.
User Action:
None.
Reason:
The VTAM command P1 is not supported. Message IST039I or IST452I was returned in response to the command.
System Action:
The requested function is unavailable.
User Action:
None.
Reason:
The VTAM command DISPLAY NET,DLURS is not supported. The host nodetype is probably a Migration Data Host and not an Interchange Node. DLUR is supported for VTAM systems with Nodetype NN only. Nodetype EN is not supported for DLUR. Use D VTAMOPTS to display VTAM's parameters.
System Action:
The requested function is unavailable.
User Action:
None.
Reason:
The display of the NCS resource list timed out while waiting for a VTAM response. There is a 30-second wait for VTAM to respond.
P1 is the command that was issued through the SPO interface.
System Action:
The display request is terminated.
User Action:
Retry.
If the problem persists, contact your network systems administrator. The number of output lines may be exceeding the VTAM message limit (POAQLIM).
Reason:
The responses to the indicated command exceeded the VTAM POAQLIM value.
P1 is the command issued through the SPO interface.
System Action:
The display request is terminated.
User Action:
Contact your network systems administrator. Increase the POAQLIM value defined for the primary ACB.
Reason:
There is no active INMC link to a region on the CP P1. Management of resources on the remote CP is not possible.
System Action:
The display request is terminated.
User Action:
Issue command SHOW ISR=ALL to determine the linked regions and the CP's they manage.
Reason:
The processing for a list of P1 elements reached the implementation maximum. For most lists this is the maximum MDO size of 32768.
System Action:
The list displayed is truncated.
User Action:
For an RTP list, use the /APPNCP function and list RTPs by connection. For an APPLICATION list, press F4 (Display) and view the native VTAM command output.
Reason:
An error occurred attempting to get the most recent RTP connection status for the lines/PUs in a line group. The error encountered is indicated by the message p1 that was written to the activity log.
System Action:
The list displayed does not have line colors set according to the connection status; all lines will show as green.
User Action:
Check the activity log for the error message p1 and take the recommended action for that message.
Reason:
A Packet Analyzer request to the SOLVE SSI failed. The message includes the following details:
p1 is the EPS request type, for example, Connect, Send, or Receive.
p2 is the EPS error number.
p3 is an explanation of the EPS error number.
System Action:
The request fails.
User Action:
Use the EPS error number and reason to determine the error:
Indicates that the connection between this region and the SSI region is not active. Use the $LOG command to check the activity log for related messages.
Use the $NM SSI Customizer parameter group to restart the SOLVE SSI.
For all other errors, contact Technical Support.
Reason:
A Packet Analyzer request to the SOLVE SSI failed because of an invalid connection ID. The message includes the following information:
p1 is the EPS verb name that was issued when the error was detected.
p2 is the EPS connection ID.
p3 is the SSID that identifies the SOLVE SSI region.
p4 is the system name where the region is running.
p5 is the NCL ID of the process.
This message corresponds to an EPS error number 81.
System Action:
The request fails.
User Action:
Retry the request. If the problem persists, contact Technical Support.
Reason:
A Packet Analyzer request to the SOLVE SSI failed because the SSI region cannot be contacted or does not include support for the Packet Analyzer.
p1 is the SSID.
p2 is the system.
p3 is the error number.
p4 is the EPS verb used.
p5 is the EPS connection ID.
The SSI can be the local SSI region or a remote region, possibly on another LPAR.
This message corresponds to EPS error numbers 39 and 70.
System Action:
The request fails.
User Action:
Check the following in the region running on p2:
Ensure that Packet Analyzer support is enabled by specifying PKTANALYZER=YES. Also ensure that the parameters include PALEVEL=FULL.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Note: Only one SOLVE SSI region (per LPAR) can include support for the Packet Analyzer.
Reason:
A Packet Analyzer request to the SOLVE SSI did not complete in a reasonable time.
p1 is the SSID.
p2 is the system.
p3 is the EPS verb.
p4 is the EPS connection ID.
The SSI can be the local SSI region or a remote region, possibly on another LPAR.
This message corresponds to EPS error numbers 48.
System Action:
The request fails.
User Action:
Retry the request. If the problem persists, contact Technical Support.
Reason:
The processing for a list of p1 elements reached the implementation maximum of 4095.
System Action:
The list displayed is truncated.
User Action:
None.
Reason:
From the EE XCA Major Node Summary, you can use simple line commands to start, view, and manage SmartTrace packet traces.
The following SmartTrace line commands are available:
PT starts a packet trace.
PTV views the packets in the trace. (You can view packets while the trace is active.)
PTI inactivates the packet trace. (When inactivated, the trace is automatically deleted after a certain interval. Save it if you want to keep it permanently.)
PTD inactivates and immediately deletes the packet trace.
On the EE XCA Major Node Summary, you can use these commands against the following:
This traces all packets on the EE Connection to the EE Remote CP.
This traces all EE packets on the VIPA associated with the Line Group. If multiple Line Groups share the VIPA, the trace will include packets from all Line Groups using the VIPA.
System Action:
A panel of optional EE trace criteria appears. A SmartTrace packet trace is then started for the Remote CP or VIPA.
User Action:
After the trace is activated, use the PTV command to view and manage the active trace.
More About SmartTrace
To list all EE-related SmartTraces, for all resources and users, use use the L option from the EE SmartTrace Menu (shortcut /EETRALL ).
More About the EE XCA Major Node Summary
As well as packet tracing, many more actions are available from this display, including EE connectivity testing, RTP details and checking, UDP Connection information, and more. Type ? on any line, to see all available commands for that CP or VIPA.
Reason:
From the EE XCA Major Node Summary, you can use line commands to start, view, and manage SmartTrace packet traces.
The following SmartTrace line commands are available:
PT starts a packet trace.
PTV views the packets in the trace. (You can view packets while the trace is active.)
PTI inactivates the packet trace. (When inactivated, the trace is automatically deleted after a certain interval. Save it if you want to keep it permanently.)
PTD inactivates and immediately deletes the packet trace.
On the EE XCA Major Node Summary, you can use these commands against the following:
This traces all EE packets on the VIPA associated with the Line Group. If multiple Line Groups share the VIPA, the trace will include packets from all Line Groups using the VIPA.
This traces all packets on the EE Connection to the EE Remote CP.
System Action:
A panel of optional EE trace criteria appears. A SmartTrace packet trace is then started, for the Remote VIPA or CP.
User Action:
After the trace is activated, use the PTV command to view and manage the active trace.
Tracing a VIPA traces all EE Connections that use the VIPA. If you know which EE Connection has the problem, consider tracing only that EE Connection.
More About SmartTrace
To list all EE-related SmartTraces, for all resources and users, use the L option from the EE SmartTrace Menu (shortcut /EETRALL ).
More About the EE XCA Major Node Summary
Type S against a line group name to expand it and see the EE Connections that use that VIPA.
As well as packet tracing, many more actions are available from this display, including EE connectivity testing, RTP details and checking, UDP Connection information, and more. Type ? on any line to see all available commands for that VIPA or CP.
Reason:
A packet trace request has been rejected because the stack P1 is not known to the Packet Analyzer. The stack is not defined as a monitored IP resource in the region.
System Action:
The packet trace request terminates.
User Action:
Define the stack using the resource administration panels
The TCP/IP Stack List panel appears.
Reason:
A request to activate a packet trace completed successfully.
System Action:
Tracing of IP address (VIPA) P1 commences. All EE packets using the VIPA will be traced. If multiple line groups share the VIPA, packets from all line groups using the VIPA will be traced, and the line groups will each be tagged *PT*.
User Action:
None.
Reason:
Abnormal conditions have occurred for one or more of the listed RTP pipes.
System Action:
None.
User Action:
Use the SORT command to group the affected RTP pipes at the top of the list. For example, SORT CONGEST D groups RTP pipes with congestion at the top of the list.
Reason:
A SORT command has been entered on the RTP Pipe List panel with no parameter or a ?. P1 names the display fields that are supported by the SORT command.
The SORT command syntax is SORT field [ A | D ].
The SORT command syntax supports a field followed by an optional A for ascending or D for descending. The initial sort is the CP field (CP Name column) in ascending order.
System Action:
None.
User Action:
Use the SORT command with one of the named fields to reorder the RTP pipe list as required.
Reason:
A SORT command has been entered on the RTP Pipe List panel where the last value is not a valid sort order operand.
The SORT command syntax supports a field followed by an optional A for ascending or D for descending.
System Action:
The SORT command is not processed.
User Action:
Reenter the SORT command with a valid operand.
Reason:
A SORT command has been entered on the RTP Pipe List panel with a field name that is not supported.
System Action:
The SORT command is highlighted in error.
User Action:
Correct the specified sort field name. If necessary, enter SORT without operands to view the list of supported sort fields.
Reason:
From the EE RTP Pipe List, you can use line commands to start, view, and manage SmartTrace packet traces of individual RTP Pipes.
The following SmartTrace line commands are available:
PT starts a packet trace.
PTV views the packets in the trace. (You can view packets while the trace is active.)
PTI inactivates the packet trace. (When inactivated, the trace is automatically deleted after a certain interval. Save it if you want to keep it permanently.)
PTD inactivates and immediately deletes the packet trace.
System Action:
A panel of optional EE trace criteria appears. A SmartTrace packet trace is then started, for the individual RTP Pipe.
User Action:
After the trace is activated, use the PTV command to view and manage the active trace.
More About SmartTrace
To list all EE-related SmartTraces, for all resources and users, use the L option from the EE SmartTrace Menu (shortcut /EETRALL ).
More About the EE RTP Pipe List
As well as packet tracing, many other actions are available from this list. Use F8 (Right) for more infomation. Type ? on any line to see all available commands.
To health check all EE RTPs, use the EE RTP Health Check ( /EERH ).
Note: SmartTrace only traces RTP Pipes that use EE. It cannot trace RTP Pipes that use transport other than EE.
Reason:
You entered the SELFTEST command on an RTP Health Check panel. The list of RTPs that were checked is displayed for all health checks.
System Action:
Display the RTPs that have been evaluated for health checks.
User Action:
Verify that the list includes all expected RTPs and that the formatting of values is correct.
| Copyright © 2012 CA. All rights reserved. |
|