|
|
|
Reason:
User P1 has attempted to invoke a function of the NEWS feature but is not authorised to do so.
System Action:
The process is terminated.
User Action:
Contact your systems administrator if you feel you should have access to NEWS.
Reason:
An invalid selection option has been chosen.
System Action:
The process waits for input from the terminal.
User Action:
Enter a valid selection and retry.
Reason:
An invalid command has been entered.
System Action:
The process waits for input from the terminal.
User Action:
Correct the command and retry or clear the command field.
Reason:
Both the LINK and SSCP names have been entered but only one of the two is allowed.
System Action:
The process waits for input from the terminal.
User Action:
Specify only one LINK or SSCP name (clear one of the two) and retry.
Reason:
A request has timed out whilst waiting for a response from a device. P1 is the amount of time that the request waited for the device to respond.
System Action:
Processing is terminated.
User Action:
Retry the function.
Reason:
Return code P1 was received in response to a request.
System Action:
Processing is terminated.
User Action:
None.
Reason:
When procedure P1 was invoked, it expected to be passed some parameters but these were not supplied.
System Action:
The process is terminated.
User Action:
Retry the procedure supplying the required parameters.
Reason:
An attempt was made to execute procedure P1, but the procedure was not found in the data set(s) that comprise the NCL library.
System Action:
An attempt is made to continue processing if possible.
User Action:
Ensure that the name of the procedure to be invoked is correct and that it resides in the correct library.
Reason:
Option P1 is not valid when used for command P2.
System Action:
The process is terminated.
User Action:
Correct the option and retry.
Reason:
The parameter P1 is not valid when used for command P2.
System Action:
The process is terminated.
User Action:
Correct the parameter and retry.
Reason:
A keyword (P1) has been entered more than once.
System Action:
The process is terminated.
User Action:
Correct the parameters and retry.
Reason:
P1 is not a valid keyword.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
P1 is not a valid operand.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
P1 is not valid for keyword P2.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
The value required for keyword P1 has been omitted.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
Required parameter P1 has been omitted.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
This indicates the end of data for the current display.
System Action:
None.
User Action:
None.
Reason:
This message gives basic details for the response from a solicited device. P1 is the node name of the solicited device, P2 and P3 are the date and time the response was received in the format DAY DD-MON-YEAR and HH:MM:SS respectively.
System Action:
None.
User Action:
None.
Reason:
This message identifies the resource hierarchy for a solicited device. rtyp is the resource type and Pn is the name of the associated resource.
System Action:
None.
User Action:
None.
Reason:
The maximum number of allowable parameters for command P1 has been exceeded.
System Action:
The process terminates.
User Action:
Correct the error and retry.
Reason:
A name has been entered that is invalid for the type indicated by P1.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
A required name of the type indicated by P1 has been omitted.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
P1 is not a valid name for the type indicated by P2.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
Both the LINK and DOMAIN names have been entered but only one of the two is allowed.
System Action:
None.
User Action:
Specify only one LINK or DOMAIN name (clear one of the two) and retry.
Reason:
Both the SSCP and DOMAIN names have been entered but only one of the two is allowed.
System Action:
None.
User Action:
Specify only one SSCP or DOMAIN name (clear one of the two) and retry.
Reason:
Return code P1 was received from procedure P2 but is not supported.
System Action:
None.
User Action:
Determine the cause of the problem and, if possible, correct it.
Reason:
An attempt to access the NEWSFILE 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 the NCL Reference in the section for the &FILEID verb.
Reason:
A value other than 'Y' or 'N' or no value has been entered in the field flagged as being in error.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
A value other than 'B', 'D' or 'R' or no value has been entered in the field flagged as being in error.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
The entire display has not been made available because the user is not authorised by NPF to view all of it.
System Action:
Processing continues.
User Action:
None.
Reason:
Press the 'ENTER' key to confirm the deletion(s), or press F3 to cancel the request.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to confirm, or press 'F3' to cancel.
Reason:
A NEWS Control Functions panel was exited but no changes were made to the current settings.
System Action:
None.
User Action:
None.
Reason:
An invalid value has been entered in a field capable of accepting a valid scroll amount value.
System Action:
None.
User Action:
Correct the error and retry. Valid scroll values are P(age), H(alf), C(ursor), D(ata) and any positive numeric value up to 100000.
Reason:
The value supplied is not numeric.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
The number entered is not within the range bounded by P1 and P2.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
A lock is in place on the NEWS database temporarily restricting access to it.
System Action:
None.
User Action:
Retry the action. If the problem persists, consult your systems administrator.
Reason:
A request for a "HELP" display has been made but no help is available for this display.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to use the MDO named P1 by procedure P2 but the MDO cannot be accessed by the procedure.
System Action:
The process is terminated.
User Action:
Ensure that the name of the MDO to be used is correct and that it is accessible to the procedure.
Reason:
A backward scroll was requested but the display is already positioned at the top of the data.
System Action:
None.
User Action:
None.
Reason:
A forward scroll was requested but the display is already positioned at the bottom of the data.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to invoke feature P1, which is either excluded from use on this processor or is not licenced for use on this processor.
System Action:
The function is terminated.
User Action:
Contact the System Administrator.
Reason:
The name indicated as being in error is invalid because is does not conform to the format "netid.NAUname".
System Action:
None.
User Action:
Correct the error and retry.
Reason:
A panel has been displayed showing details of the record that the user has requested be deleted. The user is requested to confirm or cancel the deletion of the definition presented.
System Action:
None.
User Action:
Press the CONFIRM key to allow the deletion, or press the CANCEL key to cancel the delete request.
Reason:
The user P1 attempted to modify or delete records in the NEWS database but did not have the appropriate authority level to do so.
System Action:
The process is terminated.
User Action:
Contact your systems administrator to upgrade your level of authority.
Reason:
The CNM interface is not active. You can access history data; however, recent events are not recorded.
System Action:
None.
User Action:
If the CNM interface should be active, press F9 (Swap), enter /PARMS, and action the $SN CNM Customizer parameter group.
Reason:
An explanation of the status code for an event associated with a 3x74 controller cannot be found because the NETINFO file is unavailable.
System Action:
Processing continues.
User Action:
Determine whether or not the file should be available and correct take the appropriate action.
Reason:
A VSAM error occurred during a NETINFO1 file get I/O operation. P1 is the filekey of the record, P2 is the file return code and P3 is the VSAM FDBK code.
System Action:
Processing continues.
User Action:
Take note of the message and inform your systems administrator if you are unable to resolve the problem.
Reason:
Procedure $NWFS032 has been called to format a RECMS record for display purposes but the recording mode (R-MODE) of the record is unknown to the procedure. The meaning of the record contents is R-MODE dependent.
System Action:
As much as possible of the meaning of the record contents is displayed.
User Action:
None.
Reason:
CNMPROC has released the NEWSFILE.
System Action:
Processing continues.
User Action:
None.
Reason:
PROCESS-ID P1 defined for a record by Category 003 of the NSCNTL file was not found in category 004 of the NSCNTL file.
System Action:
The record is discarded and CNMPROC processing continues.
User Action:
Correct the name of the PROCESS-ID in Cat. 003 of the NSCNTL file or add the required PROCESS-ID to Cat. 004 of the NSCNTL file.
Reason:
CNMPROC was unable to map the $CNM map to an MDO to process arriving CNM records. P1 is the Return Code from the assign of the map to the MDO and P2 is the FDBK code.
System Action:
Processing continues.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
CNMPROC was unable to map the $CNM map to an MDO to process arriving CNM records. Without the $CNM map successfully loaded, CNMPROC is not able to process any data.
System Action:
CNMPROC terminates.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
This message appears as an alert description, and is written to the activity log when the CNM procedure creates an alert (for the Alert Monitor) which has no description. P1 includes additional diagnostic information
System Action:
The message is written to the activity log allong with several EW4F* diagnostic messages.
User Action:
This is an internal error which should be reported to your local product support office. You should provide the except of the log showing this message and all following EW4F* messages.
Reason:
CNMPROC attempted to set an exclusive lock on the Newsfile but was unsuccessful because it was already held by another procedure. The owner of the lock is indicated by P1. P2 is the return code and P3 is the FDBK code from the &LOCK statement.
System Action:
The record is written to the activity log and processing continues.
User Action:
If the problem persists, determine the cause and take any necessary action to correct the problem.
Reason:
While attempting to delete records that were above the wrap count limit for a node, NEWS reached the limit of records for the node before the expected count of records was exceeded. P1 is the key of the master record of the node for which wrap count processing was being done.
System Action:
None.
User Action:
None.
Reason:
A VSAM error occurred during NEWSFILE I/O operation P1 (GET, DELETE, ADD or PUT). P2 is the filekey of the master record, P3 is the file return code and P4 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
CNMPROC has released the NEWSFILE.
System Action:
None.
User Action:
None.
Reason:
CNMPROC has been unable to log P1 records because logging to the NEWSFILE has been suspended. This message appears whenever the lost record count threshold is matched and is preceded by a message giving the reason why logging was suspended.
System Action:
None.
User Action:
Determine whether logging should still be suspended, if not take the appropriate action to resume logging.
Reason:
Counters for statistical totals for node P1 have overflowed and will be written to the activity log before being reset.
System Action:
The counters will be written to the activity log and then cleared.
User Action:
None.
Reason:
This message follows message EW1106 and lists the total statistical counts for a node prior to resetting them to zero.
System Action:
None.
User Action:
None.
Reason:
This message follows message EW1107 and lists the total statistical counts for a node prior to resetting them to zero.
System Action:
None.
User Action:
None.
Reason:
The statistical totals for the node P1 have been reset on the NEWSFILE.
System Action:
Processing continues.
User Action:
None.
Reason:
The one of the data counts maintained in the NEWSFILE master record for node P1 has exceeded the maximum. The counts will be written to the activity log and reset in the master record.
System Action:
Processing continues.
User Action:
None.
Reason:
This message follows message EW1110 and details the average response time for Response Time Monitor definition 1 (first character received). P1 is the accumulated response time in 10ths of seconds and P2 is the total number of transactions recorded for this definition.
System Action:
Processing continues.
User Action:
None.
Reason:
This message follows message EW1111 and details the average response time for Response Time Monitor definition 2 (keyboard unlock). P1 is the accumulated response time in 10ths of seconds and P2 is the total number of transactions recorded for this definition.
System Action:
Processing continues.
User Action:
None.
Reason:
This message follows message EW1112 and details the average response time for Response Time Monitor definition 2 (Change Direction/End Bracket received). P1 is the accumulated response time in 10ths of seconds and P2 is the total number of transactions recorded for this definition.
System Action:
Processing continues.
User Action:
None.
Reason:
This message follows message EW1113 and details the average response time for Response Time Monitor definition 4 (last character received). P1 is the accumulated response time in 10ths of seconds and P2 is the total number of transactions recorded for this definition.
System Action:
Processing continues.
User Action:
None.
Reason:
P1 is the total count of overflow responses from all response definitions.
System Action:
Processing continues.
User Action:
None.
Reason:
The total counts maintained in the master record for node P1 have been reset.
System Action:
Processing continues.
User Action:
None.
Reason:
The RTM statistical data from node P1 contained counts that included at least one negative number. This is not valid data.
System Action:
The record containing the incorrect data is discarded.
User Action:
If possible have corrective maintenance applied to the controller generating the invalid data to stop the problem re-occurring.
Reason:
CNMPROC has suspended the logging of all records because the NEWSFILE is unavailable. Return code P1 indicates the reason why the file is not available.
System Action:
Processing continues.
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 the NCL Reference in the section for the &FILEID verb.
Reason:
CNMPROC has suspended the logging of all records to the NEWSFILE because it was unable to retrieve a master record for updating. P1 is the file return code and P2 is the VSAM FDBK code.
System Action:
Processing continues.
User Action:
Report the problem to your systems administrator. The meaning of the return code can be found in the NCL Reference in the section for the &FILEGET verb.
Reason:
CNMPROC has suspended the logging of all records to the NEWSFILE because it was unable to delete a record during wrap count processing. P1 is the file return code and P2 is the VSAM FDBK code.
System Action:
Processing continues.
User Action:
Report the problem to your systems administrator. The meaning of the return code can be found in the NCL Reference in the section for the &FILEDEL verb.
Reason:
CNMPROC has suspended the logging of all records to the NEWSFILE because it was unable to add a record. P1 is the file return code and P2 is the VSAM FDBK code.
System Action:
Processing continues.
User Action:
Report the problem to your systems administrator. The meaning of the return code can be found in the NCL Reference in the section for the &FILEADD verb.
Reason:
CNMPROC has suspended the logging of all records to the NEWSFILE because it was unable to replace a master record after updating it. P1 is the file return code and P2 is the VSAM FDBK code.
System Action:
Processing continues.
User Action:
Report the problem to your systems administrator. The meaning of the return code can be found in the NCL Reference in the section for the &FILEPUT verb.
Reason:
An attempt to access the NEWSFILE failed because it was unavailable. The return code (P1) indicates the cause. The message P2 written to the LOG will provide further information on the cause of the failure.
System Action:
None.
User Action:
Determine if the file should be available and if so, why it isn't. For an explanation of the return code, see the section about the &FILE SET verb in the NCL Reference.
Reason:
When attempting to log a record to the NEWSFILE, CNMPROC received a return code from VSAM indicating that the file was full. CNMPROC is now performing a re-organisation of the file to reclaim lost space.
System Action:
Processing continues.
User Action:
None.
Reason:
The re-organisation of the NEWSFILE has completed successfully.
System Action:
Processing continues.
User Action:
None.
Reason:
Logging of records to the NEWSFILE by CNMPROC has now been resumed.
System Action:
Processing continues.
User Action:
None.
Reason:
The NEWSFILE is still full after a re-organisation.
System Action:
NEWSFILE database logging remains suspended.
User Action:
Determine if the NEWSFILE needs to be re-allocated with a larger amount of space or, if possible, delete from the file records you no longer require and then attempt another re- organisation of the file.
Reason:
When attempting to log a record to the NEWSFILE, CNMPROC received a return code from VSAM indicating that the file was full. A re-organisation of the file is required to reclaim lost space.
System Action:
NEWS database logging is suspended.
User Action:
Follow your installation's standards to recover from this condition or notify your systems administrator.
Reason:
When attempting to log a record to the NEWSFILE, CNMPROC received a return code from VSAM indicating that the file was full. CNMPROC is unable to close the NEWSFILE to perform a re-organisation because the file is still in use by other users.
System Action:
NEWS database logging is suspended.
User Action:
Ensure no users are accessing the file and then perform a manual re-organisation. You may use the Perform Re-org of NEWS Database option within NEWS Control Functions, NEWS Database Functions, NEWS Database Maintenance.
Reason:
Following a successful re-organisation of the NEWSFILE, CNMPROC failed to regain normal access to the NEWSFILE.
System Action:
NEWS database logging remains suspended.
User Action:
Follow your installation's standards to recover from this condition or notify your systems administrator.
Reason:
When attempting to log a record to the NEWSFILE, CNMPROC received a return code from VSAM indicating that the file was full. CNMPROC attempted a re-organisation of the file to reclaim lost space but was unsuccessful. More details of the failure may be found in the activity log.
System Action:
Logging is suspended.
User Action:
Determine the cause of the failure, correct and retry.
Reason:
A re-organisation of the NEWSFILE has been attempted but the operating system does not support IDCAMS (the method of re-organisation).
System Action:
The procedure is terminated.
User Action:
Perform the file re-organisation according to your installation's procedures or contact your systems administrator.
Reason:
The utility program UTIL0007 was passed invalid parameters.
System Action:
The procedure is terminated.
User Action:
Correct the parameters and retry.
Reason:
The utility program UTIL0007 returned an error return code from IDCAMS indicating an error.
System Action:
The procedure is terminated.
User Action:
Determine and correct the reason for the error or contact your systems administrator.
Reason:
The initial display formatting procedure has been invoked for a solicited record but was not passed any CNM data. No display is possible.
System Action:
None.
User Action:
Determine the cause and correct the problem.
Reason:
PROCESS-ID P1 defined for a record by Category 003 of the Network Services Control File was not found in Category 004 of the Network Services Control File.
System Action:
No display is processed.
User Action:
Correct the name of the PROCESS-ID in Category 003 of the Network Services Control File or add the required PROCESS-ID to Category 004 of the Network Services Control File.
Reason:
No record was found in Category 003 of the Network Services Control File to match the key provided.
System Action:
Processing of the record is terminated.
User Action:
Add the required details to the Network Services Control File if desired.
Reason:
Procedure $NWCNMSR was invoked to send RU data to a device but none was supplied.
System Action:
Processing terminates.
User Action:
Correct and retry.
Reason:
The network name was either not supplied or greater than eight characters in length.
System Action:
Processing terminates.
User Action:
Correct and retry.
Reason:
The wait option P1 is not numeric or not within the range 0 to 9999.
System Action:
Processing terminates.
User Action:
Correct and retry.
Reason:
No data has been returned in response to a CNMSEND request.
System Action:
Processing terminates.
User Action:
None.
Reason:
An error, indicated by return code P1 occurred during an &CNMREAD.
System Action:
Processing terminates.
User Action:
Determine the cause of the error. The meaning of the return code indicated can be found in the NCL User Guide.
Reason:
The contents of variable CNMFORMAT did not contain either 'BASIC' or 'GENERIC' to indicate the type of alert to be sent.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No alert type was passed to $NWALERT in variable CNMALTYPE.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No alert description was passed to $NWALERT in variable CNMALDESC.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No probable cause was passed to $NWALERT in variable CNMPCAUSE.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No User Action code was passed to $NWALERT in variable CNMUACTION.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No action code for an Installation Cause was passed to $NWALERT in variable CNMIACTION.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No action code for a Failure Cause was passed to $NWALERT in variable
CNMFACTION.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No General Cause code was passed to $NWALERT in variable CNMGCAUSE.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No Specific Component code was passed to $NWALERT in variable CNMCOMP.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
No User Action code was passed to $NWALERT in variable CNMACTION.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
The vector type P2 is not a valid Detail Text subvector. It must be type x'A0' or x'A1'. P1 is the sequence number of the Detail Text sub-vector within all Detail Text sub-vectors.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
The data supplied to build an alert must be valid hexadecimal.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
An alert has been successfully built and sent.
System Action:
None.
User Action:
None.
Reason:
No text has been entered for an alert to be sent.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
An alert has been successfully built and sent.
System Action:
None.
User Action:
None.
Reason:
Procedure $NWDS06D encountered an error whilst verifying the Element data supplied by a 3710 in response to a request.
System Action:
The procedure terminates.
User Action:
Investigate the cause and correct the error.
Reason:
Procedure $NWDS06E expected to be invoked with a parameter of either 'RECON', 'LOAD' or '?' but received an unknown parameter instead.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
Information only - will be followed by message EW1D03. Together, these two messages detail the function of procedure $NWDS06E when it is invoked.
System Action:
None.
User Action:
None.
Reason:
Information only - will be preceded by message EW1D02. Together, these two messages detail the function of procedure $NWDS06E when it is invoked.
System Action:
None.
User Action:
None.
Reason:
A value other than 'L' or 'R' or no value has been entered in the 'TARGET MODEM' field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
This message is part of the response to a list active ring command. It is followed by one or more EW1G02 messages which provide the segment number and name of all active segments on the token-ring.
System Action:
None.
User Action:
None.
Reason:
This message contains details of a segment in response to a list active ring command. P1 and P2 are respectively the number and name of a segment of the token-ring.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a list active ring request is unable to be satisfied. P1 is the sense code giving the reason for the request failure.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW1G05.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received from a response to a request.
System Action:
None.
User Action:
None.
Reason:
Both the hardware and software common names cannot be entered together.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A resource type other than 'SSCP', 'PU', 'LU', 'CHANNEL', 'STATION' or 'LINE' has been entered in one of the resource type fields.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
An alert has been successfully built and sent.
System Action:
None.
User Action:
None.
Reason:
The required field, indicated by P1 ,has not been entered.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The field indicated by P1 does not contain only hexadecimal data.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
Both the hardware and software common names cannot be entered together.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A resource type other than 'SSCP', 'PU', 'LU', 'CHANNEL', 'STATION' or 'LINE' has been entered in one of the resource type fields.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
An alert has been successfully built and sent.
System Action:
None.
User Action:
None.
Reason:
The required field, indicated by P1 ,has not been entered.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The field indicated by P1 does not contain only hexadecimal data.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The mandatory sub-vector x'9A' was not found when processing a statistical record.
System Action:
The record is discarded, processing continues.
User Action:
None.
Reason:
The mandatory X'03' name-list sub-vector was not found in a record received from an SNA_HUB.
System Action:
The record is discarded, processing continues.
User Action:
None.
Reason:
This message is displayed to maintain the details of the number of records discarded.
System Action:
Processing of other CNM records continues.
User Action:
If desired, add support for the discarded record to the Network Services Control File so that future records can be processed as desired.
Reason:
The second &CNMREAD function failed to return any more data for a chained RECFMS record from an SNA_HUB. Details contained in the record are therefore incomplete. This message will be followed by another indicating the reason the &CNMREAD failed.
System Action:
The first RECFMS record is written to the activity log.
User Action:
None.
Reason:
Because the second &CNMREAD for a chained record from an SNA_HUB failed, NEWS is unable to store the records in the database. Instead the contents of the first record received are written to the activity log for inspection.
System Action:
Contents of the first record are written to the activity log and processing then terminates.
User Action:
None.
Reason:
A value other than 'L' or 'R' or no value has been entered in the 'TARGET MODEM' field.
System Action:
The process waits for input from the terminal.
User Action:
Enter an allowed value in the required field or press PF03 to exit the panel.
Reason:
A value other than 'L', 'R' or 'A' or no value has been entered in the 'TARGET MODEM' field.
System Action:
The process waits for input from the terminal.
User Action:
Enter an allowed value in the required field or press PF03 to exit the panel.
Reason:
A value other than 'F' or 'B' or no value has been entered in the 'TARGET MODEM' field.
System Action:
The process waits for input from the terminal.
User Action:
Enter an allowed value in the required field or press PF03 to exit the panel.
Reason:
The total number of characters entered in the 'PREFIX', '1ST NUMBER' and '2ND NUMBER' fields exceeds 41.
System Action:
The process waits for input from the terminal.
User Action:
Ensure that total number of digits does not exceed 41 and retry or press PF03 to exit the panel.
Reason:
No value for the number of test sequences to be performed has been entered.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the number of test sequences to be performed is not numeric.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the number of test sequences to be performed is outside the range 1 to 10.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The current values for the configuration or coupler parameters were not retrieved for a 'CHANGE' command for an LPDA-2 modem.
System Action:
Processing continues.
User Action:
Enter the new values required or press PF03 to exit the panel and cancel the change.
Reason:
Press the 'ENTER' key to confirm the changes to the Configuration or Coupler parameters and send the request to update the same.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to send the update or press 'PF03' to exit the panel.
Reason:
A value other than 'M' or 'P' or no value has been entered in the 'Configuration' field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A value other than 'P' or 'S' or no value has been entered in the 'Network function' field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A value other than 'L' or 'S' or no value has been entered in the 'Training sequence' field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A value other than 'L' or 'D' or no value has been entered in the 'Speed control' field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A value other than 'B' or 'F' or no value has been entered in the 'Default speed' field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the RFS Delay time is not numeric.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the RFS Delay time is outside the range 0 to 255.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Receive level alarm threshold is not numeric.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Receive level alarm threshold is not within the range -43 to 0.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Line Quality alarm threshold is not numeric.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Line Quality alarm threshold is not within the range 0 to 14.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Impulse Hits alarm threshold is not numeric.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Impulse Hits alarm threshold is not within the range 0 to 63.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
No data for a RUNCMD command has been entered.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
No textual response was received in reply to a RUNCMD request.
System Action:
None.
User Action:
None.
Reason:
A solicitation request to a node for Product Set Identification data has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
The user in the displayed message is already using LPDA-2 services for the nominated station.
System Action:
Control is returned back to the LPDA-2 primary menu with this message.
User Action:
Try again.
Reason:
The LINE= or STATION= parm on the LPDA command must be entered but both may not appear on the same command.
System Action:
LPDA command terminated.
User Action:
Correct the error and retry.
Reason:
An LPDA-2 command was attempted for the specified link but LPDA support is disabled for the link.
System Action:
LPDA-2 command is terminated.
User Action:
Setup the link to allow LPDA commands.
Reason:
An LPDA-2 command was attempted against a MODEM/DSU but LPDA-2 support for that device is not valid.
System Action:
LPDA-2 command is terminated.
User Action:
Enter in the correct option for the device.
Reason:
Sense code has been received from LPDA command.
System Action:
The process is terminated.
User Action:
Use NETINFO1 to find out the error based upon the sense code and correct the problem.
Reason:
The data associated with this parameter must be greater than 0 and less than 256.
System Action:
The data will not be printed since the COPIES parameter is in error.
User Action:
N/A
Reason:
The data associated with this parameter must be either YES or NO.
System Action:
The data will not be printed since the HOLD parameter is in error.
User Action:
N/A
Reason:
If no data appears when PRINT is issued, the PRINT will be denied.
System Action:
The data will not be printed since only the title and headings would print out.
User Action:
N/A
Reason:
Check Print Services Manager (PSM) to make sure that $PSPOOL is allocated and opened. Also make sure that the printer which was specified is set up correctly.
System Action:
The data will not be printed since a request number was not returned from $PSCALL.
User Action:
Check PSM.
Reason:
This message tells the user that the PRINT command was successful but that the printout is on the queue because the HOLD=YES parameter was coded on the PRINT command.
System Action:
The list is on the queue.
User Action:
The printout can be seen on Print Services Manager under the USERID of the user. The request number which is contained in this message can be used as an identifier on the PSM.
Reason:
This message tells the user that the PRINT command was successful and also reveals what printer the list was sent to.
System Action:
The list has been printed.
User Action:
N/A.
Reason:
An LPDA-2 command was attempted for the specified link station but LPDA-2 support is disabled for the link station specified.
System Action:
LPDA-2 command is terminated.
User Action:
Setup the link station to allow LPDA commands.
Reason:
The user specified an invalid node name on the input panel.
System Action:
Control is returned back to the LPDA-2 primary menu with this message.
User Action:
Try again with a valid node name.
Reason:
The user specified an invalid ncp name on the input panel.
System Action:
Control is returned back to the LPDA-2 primary menu with this message.
User Action:
Try again with a valid ncp name.
Reason:
An invalid link name has been entered.
System Action:
None
User Action:
Correct the error and retry.
Reason:
An invalid SSCP name has been entered.
System Action:
None
User Action:
Correct the error and retry.
Reason:
Both the LINK and SSCP names have been entered but only one of the two is allowed.
System Action:
The process waits for input from the terminal.
User Action:
Specify only one LINK or SSCP name (clear one of the two) and retry.
Reason:
The user specified an invalid line name on the input panel.
System Action:
Control is returned back to the LPDA-2 primary menu with this message.
User Action:
Try again with a valid line name.
Reason:
The NCP name must be specified when issuing line type commands. It is not necessary for station commands as the owning NCP can be derived from the station information, this is not the case for lines.
System Action:
Command is terminated.
User Action:
Specify proper NCP name for given line.
Reason:
The command P1 is not recognised by procedure $NWDS300.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The value entered for the Ring or Bus Segment number is not within the range x'0' - x'0FFF'.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The value entered for the Routing Information is not valid hexadecimal.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The value entered for the Routing Information does not conform to the format AAAB......ZZZ where AAA is the Source Adapter Ring Number, B is the Bridge Number and ZZZ is the Target Adapter Ring Number.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The value entered for the Bridge number is not within the range x'0' - x'F'.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The value entered for the Percentage Frame Lost threshold is not within the range 0 - 99.99.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The value entered for the Performance Notification Interval is not within the range 0 - 99.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The value entered for the Adapter Hop-count is not within the range 1 - 7.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The new password for a Link must be not less than six and not greater than eight characters in length.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
The new password (P1) for a Link contains characters other than A-F, 0-9 and the symbols '@', '#', '$' and '%'.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry.
Reason:
User P1 has sent a request to remove adapter P2 from segment P3 of the token-ring.
System Action:
None.
User Action:
None.
Reason:
This is the first message display line in response to a LAN Adapter list command. P1 is the LAN Segment number and P2 is the Bus type of the LAN manager adapter.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list the active adapters on a LAN. It will be followed by one or more EW3104 messages which provide details of all active adapters on the LAN segment.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list the active adapters on a LAN. It provides the adapter address P1 and name P2 (if known) of all active adapters on the LAN segment. If connected to an MAU, then its address P3 , name P4 (if known), lobe number P5 and lobe state P6 will also be displayed.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a LAN adapter detail request is unable to be satisfied. P1 is the sense code which gives the reason why the request failed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide a profile of an adapter on a LAN segment and appears if the adapter is attached to a token-ring. Details of the adapter follow.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. P1 and P2 are the address and name respectively of the profiled adapter. If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. P1 and P2 are the number and type respectively of the LAN segment to which the profiled adapter is attached.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. P1 and P2 are the address and name respectively of the active adapter immediately prior to the profiled adapter on the ring segment (Nearest Active Upstream Neighbour). If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. P1 is the serial number and machine type (Product Id) of the hardware containing the adapter card of the profiled adapter.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. P1 is the microcode level of the profiled adapter and P2 indicates whether or not the adapter is monitored.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. P1 and P2 are the universal and group addresses of the profiled adapter. If no universal address was specified then 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. P1 is the functional address of the profiled adapter.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide a profile of an adapter on a LAN segment and appears if the adapter is attached to a PC network. Details of the adapter follow.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment and shows the number of CRC and Alignment errors that have occurred for this adapter. The error counts are reset every minute.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment and shows the number of collision errors and aborted transmissions that have occurred for this adapter. The error counts are reset every minute.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment and shows the number of packets sent and received by this adapter. These counts are reset every minute.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment and shows the number of resource errors that have occurred for this adapter. The error counts are reset every minute.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3120.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received from a response to a request.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment and appears when the adapter is defined on more than one segment.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment and appears when the adapter is defined on more than one segment. Message EW3123 follows and lists the segment number(s) on which the adapter is defined.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. It lists the segment number(s) on which the adapter is defined.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. P1 and P2 are the address and name respectively of the MAU to which the profiled adapter is connected. If the adapter is not attached to an MAU, or if the MAU is not named, 'N/A' is displayed in the appropriate place.
System Action:
None.
User Action:
None.
Reason:
This message is part of an adapter profile display for an adapter attached to a LAN segment. If the adapter is attached to an MAU, P1 and P2 are the MAU lobe number and lobe state respectively. Otherwise 'N/A' is displayed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list the active adapters on a LAN. It will be followed by one or more EW3127 messages which provide details of all active adapters on the LAN segment.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list the active adapters on a LAN. It provides the adapter address P1 and name P2 (if known) of all active adapters on the LAN segment.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the bridge name, P2 is the bridge number and P3 is the bridge type.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the bridge version information (in the format Vvv.rr.ll) and P2 is the bridge program number.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 indicates whether or not Frame forwarding is active and P2 is the size, in bytes, of the largest frame that can go through the bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the percentage frames lost threshold which is the number of frames lost per ten thousand expressed as a percent. When this number is exceeded, the bridge sends an alert to the LAN manager.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 indicates whether or not single-route broadcasting will be performed automatically and P2 is the frequency (in minutes) with which the bridge sends performance counters to the LAN manager. If the interval is zero, no performance counters will be sent.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the specific path taken by requests and responses through the bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 and P2 are the date (MM-DD-YY) and time respectively that the performance counters were last queried.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. This message is the main heading for the details of the two LAN segments connected to the bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the segment number and P2 is the LAN type linked to the bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 and P2 are the address and name respectively of a bridge adapter. If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 indicates whether or not single-route broadcasting is enabled for the adapter and P2 is the count of the maximum number of bridges a broadcast frame can pass through before being stopped by this bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the number of broadcast and single-route broadcast frames that have passed through the bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the number of broadcast and single-route broadcast bytes that have passed through the bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the number of frames directed to a specific address on a specific segment across specific bridges that have passed through the bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the number of bytes directed to a specific address on a specific segment across specific bridges that have passed through the bridge.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the number of frames not passed through this adapter and bridge because of any of the following reasons : i ) Beaconing adapter ii ) Continuous carrier iii) No carrier iv ) 16 consecutive collisions on the LAN segment of the other bridge adapter
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the number of frames not passed through the bridge because of heavy traffic congestion on the bridge adapter.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the number of frames not passed through the bridge because of problems with the telecommunications link between the two bridge stations.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. P1 is the number of frames not passed through the bridge for reasons other than those given in messages EW3216, EW3217 and EW3218.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. This message is the main heading for the details of users of the bridge reporting links.
System Action:
None.
User Action:
None.
Reason:
This message is part of a bridge profile display for a bridge linking two LAN segments. This message is the heading for the details of the LAN manager using Reporting link P1, where P1 is a number in the range 0-3.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a LAN bridge profile request is unable to be satisfied. P1 is the sense code which gives the reason why the request failed.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3224.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received from a response to a request.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P3 that the Bridge P2 be linked.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P3 that the Bridge P2 be unlinked.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P2 that SOLVE:LAN controlling segment P3 at that service point be reset.
System Action:
None.
User Action:
None.
Reason:
This message appears when a beacon error is detected during a reset of the LAN and is the main heading for beacon error details following.
System Action:
None.
User Action:
None.
Reason:
This message appears when a beacon error is detected during a reset of the LAN. P1 and P2 are the address and name respectively of the beaconing adapter. If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message appears when a beacon error is detected during a reset of the LAN. P1 and P2 are the address and name respectively of the active adapter immediately prior to the beaconing adapter on the ring segment (Nearest Active Upstream Neighbour). If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message appears when a beacon error is detected during a reset of the LAN. P1 is the type of beacon error that occurred.
System Action:
None.
User Action:
None.
Reason:
This message appears when hot carrier is detected during a reset of the LAN and is the main heading for the carrier error details following.
System Action:
None.
User Action:
None.
Reason:
This message appears when hot carrier is detected during a reset of the LAN. P1 and P2 are the address and name respectively of the adapter (carrier) experiencing this error. If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3309.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received in response to a request.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a LAN reset request is unable to be satisfied. P1 is the sense code which gives the reason why the request failed.
System Action:
None.
User Action:
None.
Reason:
This message is the main heading for a response resulting from a request to provide details of the status of the LAN network. Attached LAN segment details follow.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN. Details of all connected segments follow.
System Action:
None.
User Action:
None.
Reason:
This message is the main heading for a response resulting from a request to provide details of the status of the LAN network. Details of LAN segments attached by a bridge follow.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN and is immediately followed by message EW3405 which continues the heading.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN and is immediately preceded by message EW3404.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN. P1 (if present) is the bridge name joining segment P2 to the LAN, P3 is the segment type, P4 is the segment status and P5 shows the network operating mode.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a LAN query Network status request is unable to be satisfied. P1 is the sense code which gives the reason why the request failed.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3409.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received in response to a request.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN. Details of all connected segments follow.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN. P1 (if present) is the bridge name joining segment P2 to the LAN, P3 is the segment type and P4 is the segment status.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN and is immediately followed by message EW3413 which continues the heading.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN and is immediately preceded by message EW3412.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide the Network Status of a LAN. P1 is the bridge name joining segment P2 to the LAN and P3 is the segment number on the other side of the bridge.
System Action:
None.
User Action:
None.
Reason:
This message appears when a beacon error is detected during a LAN segment test and is the main heading for beacon error details following.
System Action:
None.
User Action:
None.
Reason:
This message appears when a beacon error is detected during a LAN segment test. P1 and P2 are the address and name respectively of the beaconing adapter. If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message appears when a beacon error is detected during a LAN segment test. P1 and P2 are the address and name respectively of the active adapter immediately prior to the beaconing adapter on the ring segment (Nearest Active Upstream Neighbour). If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message appears when a beacon error is detected during a LAN segment test. P1 is the type of beacon error that occurred.
System Action:
None.
User Action:
None.
Reason:
This message appears when hot carrier is detected during a LAN segment test and is the main heading for the carrier error details following.
System Action:
None.
User Action:
None.
Reason:
This message appears when hot carrier is detected during a LAN segment test. P1 and P2 are the address and name respectively of the adapter (carrier) experiencing this error. If the adapter has no name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3508.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received in response to a request.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a LAN segment or path test request is unable to be satisfied. P1 is the sense code which gives the reason why the request failed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a LAN path test request. It details the source adapter (starting point) of the path test where P1 is the source adapter address and P2 is the source adapter name.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a LAN path test request. It contains the source LAN segment number of the source adapter (starting point).
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a LAN path test request. It details the target adapter (end point) of the path test where P1 is the target adapter address and P2 is the target adapter name.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a LAN path test request. It contains the target LAN segment number of the target adapter (end point).
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a LAN path test request and is the main heading for details of the path taken to reach the target adapter.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a LAN path test request and is the column heading for details of the path taken (bridges used) to reach the target adapter.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response to a LAN path test request and lists the status of the bridges used to reach the target adapter.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that Bridge P2 change its number to P3.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to change the segment number for adapter P2 to P4 on Bridge P3.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that the performance notification interval for bridge P3 be changed to P2 minutes.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that link password P2 for bridge P3 be changed.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P3 that 'Frame Forwarding' be activated for Bridge P2.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P3 that 'Frame Forwarding' be de-activated for Bridge P2.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that the Frame Lost threshold for Bridge P3 be changed to P2%.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that 'Single-route Broadcasts' be enabled for Adapter P2 on Bridge P3.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that 'Single-route Broadcasts' be disabled for Adapter P2 on Bridge P3.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that the Single-route Broadcast Mode be altered to P3 for Bridge P2.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P5 that the Hop-count for adapter P3 on Bridge P4 be changed to P2.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a request to alter the status of a bridge is unable to be satisfied. P1 is the sense code which gives the reason why the request failed.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3614.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received in response to a request.
System Action:
None.
User Action:
None.
Reason:
This message is the main heading for a response resulting from a request to provide details of the LAN segments controlled by LAN/MASTER at this Service Point. Attached LAN segment details follow.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide details of the LAN segments controlled by LAN/MASTER at this Service Point. Attached LAN segment details follow.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to provide details of the LAN segments controlled by LAN/MASTER at this Service Point. P1 is the number of the Ring Segment and P2 (if present) is the name of the attached Ring Segment.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a command to list LAN ring segments controlled by LAN/MASTER is unable to be satisfied. P1 is the sense code which gives the reason why the request failed.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3706.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received in response to a request.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to disable adapter P2 from segment P3 of the token-ring.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to modify the control settings of MAU P2 from segment P3 of the token-ring.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from MAU commands. It appears if the MAU is attached to a token-ring. Details of the token- ring follow.
System Action:
None.
User Action:
None.
Reason:
This is the first message display line for token-ring details. P1 is the LAN Segment number and P2 is the operating speed of the token-ring.
System Action:
None.
User Action:
None.
Reason:
This message appears as part of token-ring details where P1 is the network mode.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list all active MAUs on a segment of the token-ring. It is followed by one or more EW3807 messages with details of the MAUs formatted in 2 columns.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list all active MAUs on a segment of the token-ring. It provides the MAU address and name (if known) of all active MAUs on the LAN segment.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list the disabled adapters on a LAN. It will be followed by one or more EW3809 messages which provide details of all disabled adapters on the specified segment of the token-ring.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list the disabled adapters on a LAN. P1 is the adapter address, P2 is its name (if known). P3 is the address of the MAU to which the disabled adapter is connected, P4 is its name (if known) and P5 is the MAU lobe number.
System Action:
None.
User Action:
None.
Reason:
This message is part of an MAU profile display for a MAU attached to a LAN segment. P1 and P2 are the address and name respectively of the profiled MAU. If the MAU has no name, 'N/A' is displayed in its place. P3 is the number of lobes present on this MAU.
System Action:
None.
User Action:
None.
Reason:
This message is part of an MAU profile display for an MAU attached to a LAN segment. P1 and P2 are the address and name respectively of its nearest upstream neighbour MAU. If it doesn't have a name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message is part of an MAU profile display for an MAU attached to a LAN segment. P1 and P2 are the address and name respectively of its nearest downstream neighbour MAU. If it doesn't have a name, 'N/A' is displayed in its place.
System Action:
None.
User Action:
None.
Reason:
This message is part of an MAU profile display for an MAU attached to a LAN segment. P1 and P2 are the RI phantom current and RI enable state respectively of the profiled MAU.
System Action:
None.
User Action:
None.
Reason:
This message is part of an MAU profile display for an MAU attached to a LAN segment. P1 and P2 are the RI fault tolerance state and RI fault tolerance enable state respectively of the profiled MAU.
System Action:
None.
User Action:
None.
Reason:
This message is part of an MAU profile display for an MAU attached to a LAN segment. P1 and P2 are the RO phantom current and RO enable state respectively of the profiled MAU.
System Action:
None.
User Action:
None.
Reason:
This message is part of an MAU profile display for an MAU attached to a LAN segment. P1 and P2 are the RO fault tolerance state and RO fault tolerance enable state respectively of the profiled MAU.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request for a MAU profile status. It is followed by one or more EW3818 messages which provide details of all the lobes of the profiled MAU.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request for a MAU profile status. It provides information on a lobe of the profiled MAU. P1 and P2 are the address and name respectively of the adapter (if any) connected to this lobe. P3 and P4 are the phantom current and the enable state of the lobe.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when a MAU command request is unable to be satisfied. P1 is the sense code giving the reason for the request failure.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3821.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received from a response to a request.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to modify the threshold of alert filter P2 on segment P4 of the token-ring. The new threshold value is P3 .
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from Alert Filtering commands. Details of the token-ring follow.
System Action:
None.
User Action:
None.
Reason:
This is the first message display line for token-ring details. P1 is the LAN Segment number and P2 is the operating speed of the token-ring.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list the threshold(s) of alert filter(s). It is followed by one or more EW3905 messages which provide the threshold values of alert filters.
System Action:
None.
User Action:
None.
Reason:
This message is part of the response resulting from a request to list the threshold(s) of alert filter(s). P1 is the description of the alert filter while P2 is its threshold value.
System Action:
None.
User Action:
None.
Reason:
This message is sent in response when an alert filter request is unable to be satisfied. P1 is the sense code giving the reason for the request failure.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EW3908.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received from a response to a request.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P2 that the LAN manager at that service point be reset.
System Action:
None.
User Action:
None.
Reason:
Press the 'ENTER' key to confirm and send the request to reset the LAN manager or press PF03 to cancel the request.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to send the request or press 'PF03' to cancel the request.
Reason:
A value for the Ring or Bus Segment Number has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
The value entered for the Ring or Bus Segment Number is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
The value entered for the Ring or Bus Segment number is not within the range x'0' to x'0FFF'.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The name or number of the source adapter must be entered in the respective field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Source Adapter Name field is not a valid adapter name.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Source Adapter Number field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Source Adapter Number field is not a valid adapter number.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The name or number of the target adapter must be entered in the respective field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Target Adapter Name field is not a valid adapter name.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Target Adapter Number field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Target Adapter Number field is not a valid adapter number.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A value for the Routing Info field has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Routing Info field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Routing Info field does not conform to the format AAAB......ZZZ where AAA is the Source Adapter Ring Number, B is the Bridge Number and ZZZ is the Target Adapter Ring Number.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
User P1 has sent a request to remove adapter P2 from segment P3 of the token-ring.
System Action:
None.
User Action:
None.
Reason:
Press the 'ENTER' key to confirm and send the request to remove the specified adapter from the token-ring or press PF03 to cancel the request.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to send the request or press 'PF03' to cancel the request.
Reason:
A value for the Ring or Bus Segment Number has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Ring or Bus Segment Number is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Ring or Bus Segment number is not within the range x'0' to x'0FFF'.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The name or number of the adapter must be entered in the respective field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Name field is not a valid adapter name.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Number field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Number field is not a valid adapter number.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
User P1 has sent a request to service point (node) P3 that the Bridge P2 be linked.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P3 that the Bridge P2 be unlinked.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that Bridge P2 change its number to P3.
System Action:
None.
User Action:
None.
Reason:
Press the 'ENTER' key to confirm and send the request to change the Bridge/Segment number or press PF03 to cancel the request.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to send the request or press 'PF03' to cancel the request.
Reason:
User P1 has sent a request to change the segment number for adapter P2 to P4 on Bridge P3.
System Action:
None.
User Action:
None.
Reason:
A value for the Bridge Number has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Bridge Number is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The name or number of the adapter must be entered in the respective field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Name field is not a valid adapter name.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Number field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Number field is not a valid adapter number.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A value for the Ring or Bus Segment Number has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Ring or Bus Segment Number is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Ring or Bus Segment number is not within the range x'1' - x'0FFF'.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The number specified on the 'LU=nnn' parameter was outside the range 2 - 129.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
A request for RTM (Response Time Monitor) data has been issued but the LU responding has returned data that is not in the expected format.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. The RTM function in the LU responding to this request has been disabled. No RTM data collection has been performed.
System Action:
None.
User Action:
If RTM data is to be collected for this LU, the RTM function must be re-enabled.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. The LU responding to this request has possibly lost some RTM data. The reason (if known) follows in messages EW4105 and EW4106.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 and P2 contain 'YES' or 'NO' to indicate potential causes of RTM data loss.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 and P2 contain 'YES' or 'NO' to indicate potential causes of RTM data loss.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 contains 'YES' or 'NO' to indicate if RTM is active for this LU and P2 contains 'ENABLED' or 'DISABLED' to indicate if RTM data can be locally displayed.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 and P2 contain 'YES' or 'NO' to indicate when RTM data is to be sent unsolicited.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 and P2 contain 'CONFIGURATION' or 'HOST' to indicate where the RTM definition and boundaries were set.
System Action:
None.
User Action:
None.
Reason:
A request for RTM (Response Time Monitor) data has been issued but the LU responding has no RTM data to send.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 is the definition of an event used to signify the response time measurement.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. In conjunction with message EW4113, this message forms the main heading for boundary interval measurements and their transaction counts.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. In conjunction with message EW4112, this message forms the main heading for boundary interval measurements and their transaction counts.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 is the boundary interval for a measurement and P2 is the count of transactions falling within that interval.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 is the total number of transactions for this LU and P2 is the duration (in seconds) of the last transaction measured.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 is ratio of 'OVERFLOW' transactions to total transactions, expressed as a percentage. P2 is the average response time of a transaction for the LU.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 is the session name for the class assigned by NTS and P2 is the objective response time required for that class.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 is the objective percentage of responses to be met for the NTS class shown in message EW4118 and P2 is the actual percentage of responses to fall within that boundary.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. The RTM counters for this LU were reset after the data was sent.
System Action:
None.
User Action:
None.
Reason:
This is the last of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued and indicates that there is no more information to follow for this request.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for RTM (Response Time Monitor) data has been issued. P1 is the network name of the LU, P2 is its local address and P3 is the name of the application in session with it. If the name of the application is not known, 'N/A' is shown in its place.
System Action:
None.
User Action:
None.
Reason:
The SNA address list common subvector returned is of a type with which NEWS is not familiar. P1 is the address format type of the subvector.
System Action:
The process is terminated.
User Action:
None.
Reason:
A request for RTM (Response Time Monitor) data has been issued and the response has indicated an error in processing the request. The System Sense code P1 and User Sense code P2 indicate the nature of the failure.
System Action:
None.
User Action:
Investigate the reason for the failure.
Reason:
An RTM solicitation request to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
An invalid LU number or no LU number has been passed to the procedure $NWDS025.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
The SNA address list common subvector returned is of a type with which NEWS is not familiar. P1 is the address format type of the subvector.
System Action:
Processing of the record by CNMPROC is terminated.
User Action:
None.
Reason:
An attempt to assign the map $NWCNMREC to an MDO for CNM data processing failed. The return code (P1) and FDBK code (P2) indicate the reason.
System Action:
None.
User Action:
Determine what has changed in the system map $NMCNMREC or if the correct OSCNTL file has been allocated. The meaning of the return code can be found in the NCL Reference section on &ZMDORC and &ZMDOFDBK variables.
Reason:
An attempt to map the data found in the map for processing CNM records has returned no valid CNM data.
System Action:
Processing of the CNM record is terminated.
User Action:
None.
Reason:
Because the NSCNTL file is unavailable, procedure $NWLMSUP is unable to build the options for the LAN Management menu. P1 is the code returned from the file access attempt.
System Action:
The LAN Management menu is not displayed.
User Action:
Refer the problem to your installation help desk. Determine if the file should be available. The meaning of the return code can be found in the NCL Reference in the section for the &FILEID verb.
Reason:
$NWLMSUP is unable to format the options for the LAN Management menu because the category for the NSCNTL file containing them is empty.
System Action:
The LAN Management menu is not displayed.
User Action:
Add the necessary record to category 7 (Device Support Selection Options) of the NSCNTL file or report the problem to your System Administrator.
Reason:
A VSAM error occurred during NSCNTL file I/O operation 'GET' in procedure $NWLMSUP. P1 is the filekey of the record, P2 is the file return code and P3 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, take note of the error message and report the problem to your installation help desk facility.
Reason:
$NWLMSUP is unable to format the options for the LAN Management menu because the category of the NSCNTL file containing them has no LAN Management type records flagged as displayable options.
System Action:
The Device Support menu is not displayed.
User Action:
Amend the exclusion option of the records you require to be displayed on the Lan Management Menu. These records are found incategory 7 (Device Support Selection Options) of the NSCNTL file or report the problem to your System Administrator.
Reason:
User P1 has sent a request to service point (node) P3 that 'Frame Forwarding' be activated for Bridge P2.
System Action:
None.
User Action:
None.
Reason:
Press the ENTER key to confirm and send the request to change the Bridge configuration or press PF03 to cancel the request.
System Action:
The process waits for input from the terminal.
User Action:
Confirm the request details before actioning.
Reason:
User P1 has sent a request to service point (node) P3 that 'Frame Forwarding' be de- activated for Bridge P2.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that the Notification Interval for Bridge P3 be changed to P2.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that the 'Frame Lost threshold' for Bridge P3 be changed to P2%.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P5 that the Hop-count for adapter P3 on Bridge P4 be changed to P2.
System Action:
None.
User Action:
None.
Reason:
A value for the Performance Notification Interval in field 'New Value' has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Performance Notification Interval in field 'New Value' is not numeric.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Performance Notification Interval in field 'New Value' is not within the range 0 - 99.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A value for the Frame Lost threshold in field 'New Value' has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Percentage Frame Lost threshold in field 'New Value' is not numeric.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Percentage Frame Lost threshold in field 'New Value' is not within the range 0 - 99.99.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A value for the Adapter Hop-count in field 'New Value' has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Adapter Hop-count in field 'New Value' is not numeric.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered for the Adapter Hop-count in field 'New Value' is not within the range 1 - 7.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The name or number of the adapter must be entered in the respective field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Name field is not a valid adapter name.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Number field is not valid hexadecimal. All characters must be numeric or alphabetic in the range A to F.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Number field is not a valid adapter number.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
User P1 has sent a request to service point (node) P4 that 'Single-route Broadcasts' be enabled for Adapter P2 on Bridge P3.
System Action:
None.
User Action:
None.
Reason:
Press the ENTER key to confirm and send the request to change the status of Single-route Broadcasts for an Adapter or press PF03 to cancel the request.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to send the request or press 'PF03' to cancel the request.
Reason:
User P1 has sent a request to service point (node) P4 that 'Single-route Broadcasts' be disabled for Adapter P2 on Bridge P3.
System Action:
None.
User Action:
None.
Reason:
User P1 has sent a request to service point (node) P4 that the Single-route Broadcast Mode be altered to P3 for Bridge P2.
System Action:
None.
User Action:
None.
Reason:
A value for the Broadcast Mode has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
A broadcast mode of A or M should be entered or press PF03 to exit the panel.
Reason:
A value other than 'A' or 'M' has been entered in the 'BROADCAST MODE' field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The name or number of the adapter must be entered in the respective field.
System Action:
The process waits for input from the terminal.
User Action:
Supply either value and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Name field is not a valid adapter name.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Number field is not valid hexadecimal. It should contain numerics or alphabetic characters in the range A to F.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The value entered in the Adapter Number field is not a valid adapter number.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
User P1 has sent a request to service point (node) P4 that the password for Link P2 on Bridge P3 be altered.
System Action:
None.
User Action:
None.
Reason:
Type in the new password again to confirm that the password is as you wish.
System Action:
The process waits for input from the terminal.
User Action:
Re-type the new password and press 'ENTER' or press 'PF03' to cancel the password change request.
Reason:
When the password was re-entered it did not match the password previously entered.
System Action:
The password change is cancelled.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The request to change the password for a Link has been cancelled.
System Action:
None.
User Action:
None.
Reason:
A new password for a Link has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Supply the new value or press PF03 to exit the panel.
Reason:
The new password for a Link must be not less than six and not greater than eight characters in length.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The new password for a Link contains characters other than A-F, 0-9 and the symbols '@', '#', '$' and '%'.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
A request has timed out whilst waiting for a response from a device.
System Action:
Processing is terminated.
User Action:
Retry the function.
Reason:
An MDO mapping error occurred during the mapping of a CNM record using the $CNM map. P1 is the Return Code from the assign of the map to the MDO and P2 is the associated FDBK code.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
An MDO mapping error occurred during the mapping of a CNM record using the $CNM map. P1 is the Return Code from the assign of the map to the MDO and P2 is the associated FDBK code.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
The length of the text command to be sent in the EXECUTE request is greater than 232 characters.
System Action:
The RUNCMD is rejected.
User Action:
Shorten the text of the command and retry the function.
Reason:
The request that was issued could not be routed to the control point. The sense code returned was P1 .
System Action:
None.
User Action:
Obtain information on the sense code, correct the condition if possible, and retry. Check that the specified resource name is correct.
Reason:
A request to display information about a detail record, such as DUMP or VECTOR, is unable to be satisfied.
System Action:
None.
User Action:
None.
Reason:
This is the heading for series of messages that contain the contents of a CNM record and associated information. It is used when a request to write the record information to the activity log has been issued.
System Action:
None.
User Action:
None.
Reason:
This is the heading for series of messages that contain the contents of a CNM record and associated information. This message displays 16 bytes of data ( P1 ) in the following format: oooo : xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx : cccc cccc cccc cccc where: oooo = offset xxxxxxxx = hex-expanded data cccc = character data (EDCDIC)
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the alert severity.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. If the CNM record is an NMVT (Network Management Vector Transport), then it contains a major vector. P1 indicates the major vector type.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. If the CNM record is an NMVT (Network Management Vector Transport), then it contains a major vector. P1 is a list of the sub-vectors contained within the first major vector.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the network name of the device that sent the record.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the hierarchy of nodes upstream of the node that sent the record.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the processing option currently assigned to the record but may change later in the processing cycle.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is a description of the contents of the record.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 contains the codes used to determine the processing and possible display of the record.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the record resource identifier (RID) which is usually assigned from category 1 or 2 of the NSCNTL file.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the record event identifier (EID) which is usually assigned from category 1 or 2 of the NSCNTL file.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the record process identifier (PID) which is usually assigned from category 3 of the NSCNTL file.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the record old process identifier (OPID). This is usually the same the process identifier (PID) unless changed after initial assignment.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the last NCL return code set during processing for this record.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request to write CNM record information to the activity log has been issued. P1 is the type of CNM processing procedure and P2 is the procedure name.
System Action:
None.
User Action:
None.
Reason:
This is the final message of a series of messages issued when a request to write CNM record information to the activity log has been issued.
System Action:
None.
User Action:
None.
Reason:
An error has occurred decoding CMIP data present in the x'132F' major vector which accompanies the x'1330' major vector. The &RETCODE ( P1 ) and &ZFDBK ( P2 ) values apply to the &DECODE NCL verb. This message, plus another message with additional details (normally N24N02) is written to the activity log.
System Action:
As much of the display is built as possible without compromising the contents.
User Action:
Report the problem to your installation help desk.
This problem occurs because the ASN.1 map does not support the particular BER data in the x'132F' major vector and should be reported to your product supplier with the following information:
1. The messages on the log. The &DECODE failure message, normally N24N02, contains the failure reason and offset information. This message (EW5101) contains the &DECODE feedback code.
2. A hex dump of the major vector. The x'132F' major vector is usually the second major vector and can be displayed using the V2 command from the alert display. Alternatively a hex dump of the whole record (using the D command) should be provided.
Reason:
An error has occurred processing the the x'132F' major vector which accompanies the x'1330' major vector. The x'132F' major vector cannot be isolated from the CNM record.
System Action:
As much of the display is built as possible without compromising the contents.
User Action:
Report the problem to your installation help desk.
This problem should not occur and should be reported to your product supplier. A hex dump of the whole CNM record (displayable using the D command) should be provided.
Reason:
An error has occurred processing the data in the managed object class of the CMIP record. The type of data following cannot be determined and no further processing of CMIP data for this record can be performed.
System Action:
As much of the display is built as possible without compromising the contents.
User Action:
Report the problem to your installation help desk.
This problem should not occur and should be reported to your product supplier. A hex dump of the whole CNM record (displayable using the D command) should be provided.
Reason:
This message indicates the map components used in the failed DECODE process referred to in message EW5G01. The "to" map is the name of the map in which the decoded data is to be placed while, the "from" map is the map from which the data is extracted.
System Action:
Processing continues.
User Action:
Report the problem to your installation help desk.
This problem occurs because the ASN.1 map does not support the particular BER data and should be reported to your product supplier with the following information:
1. The messages on the log. The &DECODE failure message, normally N24N02, contains the failure reason and offset information.
2. A hex dump of the major vector. The x'132F' major vector is usually the second major vector and can be displayed using the V2 command from the alert display. Alternatively a hex dump of the whole record (using the D command) should be provided.
Reason:
Procedure $NWCFILE was invoked to access the NSCNTL file but the key provided (P1) does not match any record in the file.
System Action:
The process is terminated.
User Action:
None.
Reason:
An error occurred during vartable I/O operation P1 (ADD or DELETE).
P2 is the key of the vartable record and P3 is the vartable FDBK code.
System Action:
Processing continues.
User Action:
Retry the operation, if unsuccessful, take note of the error message and contact your systems administrator.
Reason:
An attempt to access to NSCNTL file has returned an error code indicating that no access is allowed to the file.
System Action:
The process is terminated.
User Action:
Refer the problem to your installation help desk.
Reason:
An attempt to access the NSCNTL failed because it was unavailable. The return code (P1) indicates the cause.
System Action:
The process is terminated.
User Action:
Determine if the NSCNTL file is available. The meaning of the return code can be found in the NCL Reference in the section for the &FILE OPEN verb.
Reason:
The user P1 attempted to modify or delete records in the NSCNTL file without the appropriate authority level.
System Action:
The process is terminated.
User Action:
Contact your systems administrator to upgrade your level of authority.
Reason:
An file action failed for the NSCNTL file:
P1 is the file action, GET, ADD, PUT, or DELETE.
P2 is the filekey of the record.
P3 is the file return code.
P4 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Use the VSAM feedback value to determine the cause of the error. Correct the problem and retry.
Reason:
An attempt was made to add a record to the NSCNTL file but the record already exists.
System Action:
The process is terminated.
User Action:
Ensure that the data to be added is correct and retry.
Reason:
A record has been successfully added to the NSCNTL file.
System Action:
None.
User Action:
None.
Reason:
A record has been successfully added to the $NWCACHE vartable.
System Action:
None.
User Action:
None.
Reason:
An attempt to add or save a modified record to the NSCNTL failed because the file was in use.
System Action:
None.
User Action:
Retry the operation.
Reason:
A record has been successfully replaced in the NSCNTL file.
System Action:
None.
User Action:
None.
Reason:
An error occurred during a vartable get operation. P1 is the key of the vartable record and P2 is the vartable FDBK code.
System Action:
Processing continues.
User Action:
Retry the operation, if unsuccessful, take note of the error message and contact your systems administrator.
Reason:
A file action failed for the NSCNTL file. P1 is the file action, ADD, PUT, or DELETE. These actions requires that the file is open for output actions but the file was opened for input actions only.
System Action:
The process is terminated.
User Action:
If the output action is required, the file must be closed and reopened with the correct attributes. To do this:
1. Use the /PARMS shortcut to display the Customizer : Parameter Groups list.
2. Update the NSCNTL parameter group (in the FILES section).
3. Review the NSCNTL File VSAM Options values:
- the value INPUT, if present, restricts the file to input actions only
- remove the value INPUT and use F6=Action to action the group. This will cause the file to be closed and reopened.
4. Use F3=File to save the updated values
5. Retry the action.
Reason:
An FCS solicitation request to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
An undetermined error occurred during the solicitation of an FCS device. P1 is the type of request that was issued.
System Action:
The process is terminated.
User Action:
Retry the operation to try to gather more information about the error.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
No Alert description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The Alert description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
No probable cause was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The probable cause category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing. P1 is the sub-vector in error.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
An attempt was made to execute procedure P1, but the procedure was not found in the NCL libraries accessible to the user. P2 is the code point in category 14 of the NSCNTL file that references the procedure name.
System Action:
Processing is terminated.
User Action:
Ensure that the name of the procedure to be invoked is correct and that it resides in the correct library or remove it from the appropriate record in category 14 of the NSCNTL file.
Reason:
An attempt was made to execute procedure P1, but the procedure was not found in NCL libraries accessible to the user. P2 is the code point in category 15 of the NSCNTL file that references the procedure name.
System Action:
Processing is terminated.
User Action:
Ensure that the name of the procedure to be invoked is correct and that it resides in the correct library or remove it from the appropriate record in category 15 of the NSCNTL file.
Reason:
An attempt was made to execute procedure P1, but the procedure was not found in the NCL libraries accessible to the user. P2 is the code point in category 16 of the NSCNTL file that references the procedure name.
System Action:
Processing is terminated.
User Action:
Ensure that the name of the procedure to be invoked is correct and that it resides in the correct library or remove it from the appropriate record in category 16 of the NSCNTL file.
Reason:
During the formatting of the Alert display an undetermined error occurred.
System Action:
The formatted display may be incomplete.
User Action:
Report the problem to your installation help desk. Try to determine the cause of the error - a dump of the record may reveal inconsistent data.
Reason:
During the formatting of the Alert display an undetermined error occurred.
System Action:
As much of the display is built as possible without compromising the contents.
User Action:
Report the problem to your installation help desk. Try to determine the cause of the error - a dump of the record may reveal inconsistent data.
Reason:
An error has occurred decoding CMIP data present in the x'132F' major vector which accompanies the x'1330' major vector. The &RETCODE ( P1 ) and &ZFDBK ( P2 ) values apply to the &DECODE NCL verb. This message, plus another message with additional details (normally N24N02) is written to the activity log.
System Action:
As much of the display is built as possible without compromising the contents.
User Action:
Report the problem to your installation help desk.
This problem occurs because the ASN.1 map does not support the particular BER data in the x'132F' major vector and should be reported to your product supplier with the following information:
1. The messages on the log. The &DECODE failure message, normally N24N02, contains the failure reason and offset information. This message (EW5G01) contains the &DECODE feedback code.
2. A hex dump of the major vector. The x'132F' major vector is usually the second major vector and can be displayed using the V2 command from the alert display. Alternatively a hex dump of the whole record (using the D command) should be provided.
Reason:
An error has occurred processing the the x'132F' major vector which accompanies the x'1330' major vector. The x'132F' major vector cannot be isolated from the CNM record.
System Action:
As much of the display is built as possible without compromising the contents.
User Action:
Report the problem to your installation help desk.
This problem should not occur and should be reported to your product supplier. A hex dump of the whole CNM record (displayable using the D command) should be provided.
Reason:
No Alert description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The Alert description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
No probable cause was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The probable cause category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
While attempting to build a display from details contained in the subvector, an error occurred in the processing. P1 is the subvector in error.
System Action:
The building of information from the subvector is discontinued.
User Action:
A display of the contents of the subvector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
An error has occurred processing the data in the managed object class of the CMIP record. The type of data following cannot be determined and no further processing of CMIP data for this record can be performed.
System Action:
As much of the display is built as possible without compromising the contents.
User Action:
Report the problem to your installation help desk.
This problem should not occur and should be reported to your product supplier. A hex dump of the whole CNM record (displayable using the D command) should be provided.
Reason:
An unknown Object Identifier has caused processing the contents of the Local Distinguished Name to be terminated. P1 is the Object Identifier causing the problem.
System Action:
As much of the display is built as possible without compromising the contents.
User Action:
Report the problem to your installation help desk.
This problem should not occur and should be reported to your product supplier. A hex dump of the whole CNM record (displayable using the D command) should be provided.
Reason:
This message indicates the map components used in the failed DECODE process referred to in message EW5G01. The "to" map is the name of the map in which the decoded data is to be placed while, the "from" map is the map from which the data is extracted.
System Action:
Processing continues.
User Action:
Report the problem to your installation help desk.
This problem occurs because the ASN.1 map does not support the particular BER data and should be reported to your product supplier with the following information:
1. The messages on the log. The &DECODE failure message, normally N24N02, contains the failure reason and offset information.
2. A hex dump of the major vector. The x'132F' major vector is usually the second major vector and can be displayed using the V2 command from the alert display. Alternatively a hex dump of the whole record (using the D command) should be provided.
Reason:
The NEWS Object ID to SNA code point translation procedure $NWCMCPT failed during request processing because it was passed an invalid keyword value. The keyword is P1 and P2 is the invalid value.
System Action:
The request is rejected and procedure $NWCMCPT terminates.
User Action:
Check the syntax of the call to procedure $NWCMCPT.
Reason:
The NEWS Object ID to SNA code point translation procedure $NWCMCPT was unable to match the supplied Object Identifier to an SNA Alert code point.
System Action:
As much of the display is built as possible without compromising the contents. No substitution is performed for the Object Identifier in the resulting display.
User Action:
Report the problem to your installation help desk.
This problem occurs because an unknown Object Identifier has been encountered and should be reported to your product supplier with the following information:
- A hex dump of the major vector. The x'132F' major vector is usually the second major vector and can be displayed using the V2 command from the alert display. Alternatively a hex dump of the whole record (using the D command) should be provided.
Reason:
The requested entry point definition does not exist on the database.
System Action:
The action is rejected.
User Action:
None.
Reason:
A request was made to add an Entry Point which already exists on the database.
System Action:
The add request is rejected.
User Action:
Change the Entry Point name being added or use the update option to change the existing Entry Point definition.
Reason:
The add of an Entry Point definition was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
The update of an Entry Point definition was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
The Entry Point definition for node P1 was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
An invalid value has been entered in the Desired Status field.
System Action:
None.
User Action:
Correct the error and retry or press F6 to exit the panel.
Reason:
The deletion of an Entry Point definition was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
Invalid data was found during the building of a 'Summary Error Data Display'.
System Action:
The building of the display is terminated.
User Action:
None.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
An unknown Communication Adapter counter type (P1) was found during the building of a 'Communication Adapter Error Statistics Display'.
System Action:
The building of the display is terminated.
User Action:
None.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
An unknown RECFMS Type 4 records (PU/LU dependent data) is received with unsupported configuration type P1 . The prcoessing is terminated.
System Action:
Processing is terminated.
User Action:
Report the problem to your installation help desk.
Reason:
The display of E/C level data for a device with BLK-ID P1 is not supported.
System Action:
The display is not built.
User Action:
Determine how best the information may be displayed and make the appropriate changes to the NSCNTL file or contact your systems administrator.
Reason:
The format of E/C level data for a 3274 or equivalent device is invalid.
System Action:
The display is not built.
User Action:
Determine how best the information may be displayed and make the appropriate changes to the NSCNTL file or contact your systems administrator.
Reason:
The format of E/C level data for a 3174 or equivalent device is invalid.
System Action:
The display is not built.
User Action:
Determine how best the information may be displayed and make the appropriate changes to the NSCNTL file or contact your systems administrator.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
Link Problem Determination Aid 1 (LPDA-1) test type P1 is not supported for display.
System Action:
The building of the display is terminated.
User Action:
None.
Reason:
A component description, blkno of 000, is invalid. There is a configuration mismatch between the host application and product.
System Action:
None.
User Action:
Correct generation problem.
Contact Technical Support.
Reason:
The value entered in the CODE field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
The formatted display of RECFMS6 data from a device identified by BLK-ID P1 with a P2 record type is not supported.
System Action:
The building of the display is terminated.
User Action:
None.
Reason:
A CNM record indicating that it contains Response Time Data from an FCS device does not contain any valid data of that type.
System Action:
The building of the display is terminated.
User Action:
None.
Reason:
Response Time data from FCS device P1 was not returned because the node is not recording work station response times.
System Action:
The building of the display is terminated.
User Action:
None.
Reason:
A request for Response Time data from an FCS device returned data indicating that the device did not support such a request.
System Action:
The building of the display is terminated.
User Action:
None.
Reason:
Procedure $NWSV10 was unable to properly format Product-Set ID data from a device for an undetermined reason.
System Action:
The building of the display is terminated.
User Action:
None.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
No Event description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The Event description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
The value entered in the CODE field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
The value entered in the DATA-ID field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
The value entered in the CODE field is not valid hexadecimal.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
The format of E/C level data for a 3174 or equivalent device is invalid.
System Action:
The display is not built.
User Action:
Determine how best the information may be displayed and make the appropriate changes to the NSCNTL file or contact your systems administrator.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
The format of E/C level data for a 3274 or equivalent device is invalid.
System Action:
The display is not built.
User Action:
Determine how best the information may be displayed and make the appropriate changes to the NSCNTL file or contact your systems administrator.
Reason:
An undetermined error occurred during processing in procedure $NWCFILE. P1 is the key of the NSCNTL file record passed to $NWCFILE for retrieval.
System Action:
Building of the display is terminated.
User Action:
Report the problem to your system administrator.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
A value other than 'Y' or 'N' has been entered in a field during NEWS Control File Maintenance, but the field only allows these values to be entered. The erroneous field is highlighted.
System Action:
None.
User Action:
Correct the value to 'Y' or 'N' and retry.
Reason:
A value other than 'B', 'L' or 'M' has been entered in the Process Option field. (These are the only valid values.)
System Action:
The process waits for input from the terminal.
User Action:
Correct the value and retry.
Reason:
A value other than 'S', 'SMF', 'V' or 'VSAM' has been entered in the File Type field. (These are the only valid values.)
System Action:
The process waits for input from the terminal.
User Action:
Correct the value and retry.
Reason:
No value has been entered in the Identifier field.
System Action:
The process waits for input from the terminal.
User Action:
Add the correct value and retry.
Reason:
The value entered in the Identifier field is not within the numerical range 200 - 255.
System Action:
The process waits for input from the terminal.
User Action:
Correct the value and retry.
Reason:
The value entered in the Return Code field is not a valid hexadecimal value.
System Action:
The process waits for input from the terminal.
User Action:
Correct the value and retry.
Reason:
No component description was found in the NSCNTL file to match the code point in this record.
System Action:
None.
User Action:
The component description category and code can be found in the 'CODES' display for this record. Have the code point and description added to the appropriate category of the NSCNTL file.
Reason:
An undetermined error occurred during the processing of LPDA-2 data in procedure in $NWSV50. P1 is the return code from procedure $NWSV50.
System Action:
The process is terminated.
User Action:
None.
Reason:
Procedure $NWSV50 did not return the name of a panel to be displayed to its calling procedure due to an undetermined error. No formatted data will be displayed.
System Action:
A dump of the record will be displayed.
User Action:
None.
Reason:
On receipt of solicited CNM record, flags in the record indicated more data was to follow. A request for more data to the device resulted in no more data being returned.
System Action:
The process is terminated because the amount of data returned is not sufficient to build an accurate display.
User Action:
Retry the operation.
Reason:
An unknown element type was found during the building of a configuration display for a 3710.
System Action:
The process is terminated.
User Action:
None.
Reason:
Procedure $NWFP003 was unable to identify the record type chosen for display from a selection list.
System Action:
The procedure waits for input from the terminal.
User Action:
Retry the operation or make another selection.
Reason:
A procedure was invoked to access the NEWS database but was not passed a record key.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
The command P1 is not valid from this display.
System Action:
The command is rejected.
User Action:
Correct the error.
Reason:
The recording mode P1 is not supported when formatting a display.
System Action:
The contents of the record are ignored.
User Action:
None.
Reason:
A request to display information about a detail record, such as DUMP or VECTOR, cannot be satisfied because the requested information is not available.
System Action:
None.
User Action:
None.
Reason:
A request to display the CNM record dump cannot be satisfied because the requested information is not available.
System Action:
None.
User Action:
None.
Reason:
A destination type other than 'DOMAIN', 'LINKNAME' or 'SSCPNAME' has been appended to the 'RESEND' command.
System Action:
None.
User Action:
Correct the destination type and name and retry the command.
Reason:
A CNM record has been successfully resent using the 'RESEND' command.
System Action:
None.
User Action:
None.
Reason:
This message is displayed when the ASCII or EBCDIC command has been entered during display of a NEWS record. It confirms that the command has been successful and that the character formatted data will now be displayed in the format requested ( P1 is ASCII or EBCDIC).
System Action:
None.
User Action:
None.
Reason:
One or more parameters supplied to procedure $NWLPDA2 are in error.
System Action:
The process is terminated.
User Action:
Correct the error(s) and retry.
Reason:
The value P1 for parameter 'LEVEL=' is not '1' or '2'.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The value P1 for parameter 'MODEM=' is not 'LOCAL', 'BROADCAST' or 'REMOTE'.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The value P1 for parameter 'FILE=' is not 'YES', 'NO' or 'ONLY'.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The 'DISPLAY=' parameter has been specified but the procedure was not invoked from a fullscreen environment.
System Action:
The process is terminated.
User Action:
Correct the parameters of the procedure so it can be executed from the current environment or execute the command from a fullscreen environment if a display is required.
Reason:
The value P1 for parameter 'DISPLAY=' is not 'CONFIG' or 'COUPLER'.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The 'CHANGE=' parameter has been specified but the procedure was not invoked from a fullscreen environment.
System Action:
The process is terminated.
User Action:
Correct the parameters of the procedure so it can be executed from the current environment or execute the command from a fullscreen environment if a display is required.
Reason:
The value P1 for parameter 'CHANGE=' is not 'CONFIG' or 'COUPLER'.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The value P1 for parameter 'SPEED=' is not 'FULL' or 'BACKUP'.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The value P1 for parameter 'CONTACT=' is not 'QUERY, 'OPEN' or 'CLOSE'.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The 'TEST=' parameter has been specified but the procedure was not invoked from a fullscreen environment.
System Action:
The process is terminated.
User Action:
Correct the parameters of the procedure so it can be executed from the current environment or execute the command from a fullscreen environment if a display is required.
Reason:
The value P1 for parameter 'TEST=' is not 'MS', 'LA' or 'TR(n)'.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The number of sequence exchanges to be performed as specified in the parameter 'TEST=TR(n)' is not within the range 1 - 10 where n is the number of sequence exchanges.
System Action:
The process is terminated.
User Action:
Correct the parameter in error and retry.
Reason:
The value for parameter 'STATION=' or the entire parameter 'STATION=' has been omitted.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
A parameter specifying the LPDA2 command to be performed was omitted.
System Action:
The process is terminated.
User Action:
Add the required parameter and retry.
Reason:
An LPDA2 solicitation request to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
An NMVT sub-vector x'50', expected as part of the result to a request was not received.
System Action:
The process is terminated.
User Action:
Determine the reason why no valid data was received and retry the request if necessary.
Reason:
Procedure $NWFP002 experienced an undetermined error while processing LPDA2 data. P1 is the return code from procedure $NWFP002.
System Action:
The process is terminated.
User Action:
Determine the cause of the error and, if possible, correct it.
Reason:
The LPDA2 command requested has successfully completed.
System Action:
The process terminates.
User Action:
None.
Reason:
An invalid link name has been entered.
System Action:
None
User Action:
Correct the error and retry.
Reason:
An invalid SSCP name has been entered.
System Action:
None
User Action:
Correct the error and retry.
Reason:
Both the LINK and SSCP names have been entered but only one of the two is allowed.
System Action:
The process waits for input from the terminal.
User Action:
Specify only one LINK or SSCP name (clear one of the two) and retry.
Reason:
User P1 has attempted to invoke a function of the NEWS feature but is not authorised to do so.
System Action:
The process is terminated.
User Action:
Contact your security administrator if you feel you should have access to NEWS.
Reason:
An error has occurred due to the user specifying invalid parms on the LPDA command.
System Action:
LPDA command is terminated.
User Action:
Specify correct parms on LPDA command.
Reason:
An error has occurred due to the user specifying invalid FILE= parm on the LPDA command.
System Action:
LPDA command is terminated.
User Action:
Specify correct FILE= parm on LPDA command. Valid parms are: YES, NO or ONLY.
Reason:
An error has occurred due to the user not specifying a STATION= or LINE= parm on the LPDA command.
System Action:
LPDA command is terminated.
User Action:
Specify a LINE= or STATION= parm on the LPDA command.
Reason:
The LINE= or STATION= parm on the LPDA command must be entered but both may not appear on the same command.
System Action:
LPDA command terminated.
User Action:
Correct the error and retry.
Reason:
The LPDA command expects to see either a X'82', X'84' or X'7D' sub-vector but didn't receive any of these therefore a severe error is encountered.
System Action:
LPDA command terminated.
User Action:
Re-issue the command.
Reason:
An error has occurred due to the user specifying invalid COMMAND= parm on the LPDA command.
System Action:
LPDA command is terminated.
User Action:
Specify correct COMMAND= parm on the LPDA command. Valid parms are: QUERY, ALLOW, BLOCK
Reason:
An error has occurred due to the user specifying invalid COMMAND= parm on the LPDA command.
System Action:
LPDA command is terminated.
User Action:
Specify correct COMMAND= parm on the LPDA command. Valid parms are: QUERY, NONE, TYPE1, TYPE2, TYPE3
Reason:
Sense code has been received from LPDA command.
System Action:
The process is terminated.
User Action:
Use NETINFO1 to find out the error based upon the sense code and correct the problem.
Reason:
An invalid link name has been entered.
System Action:
None
User Action:
Correct the error and retry.
Reason:
An invalid SSCP name has been entered.
System Action:
None
User Action:
Correct the error and retry.
Reason:
Both the LINK and SSCP names have been entered but only one of the two is allowed.
System Action:
The process waits for input from the terminal.
User Action:
Specify only one LINK or SSCP name (clear one of the two) and retry.
Reason:
The NEWSFILE has been successfully cleared. P1 is the number of records deleted.
System Action:
IF logging was in force before the clear operation, it will be re-started.
User Action:
None.
Reason:
A request to clear the NEWSFILE was cancelled by the user when confirmation was requested.
System Action:
Processing terminates.
User Action:
None.
Reason:
The user P1 attempted to modify or delete records in the NEWS database without the appropriate authority level.
System Action:
The process is terminated.
User Action:
Contact your systems administrator to upgrade your level of authority.
Reason:
A procedure was invoked to access the NEWS database but was not passed record key.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
The key passed to procedure $NWDBDEL does not match any category in the NEWSFILE. P1 is the invalid key passed to the procedure.
System Action:
The process is terminated.
User Action:
Retry the operation. If unsuccessful, contact your systems administrator.
Reason:
P1 records were successfully deleted as requested.
System Action:
None.
User Action:
None.
Reason:
The record was successfully deleted as requested.
System Action:
None.
User Action:
None.
Reason:
The user P1 attempted to update the logging limit (wrap count) for a particular node name within a category without the appropriate authority level.
System Action:
The process is terminated.
User Action:
Contact your systems administrator to upgrade your level of authority.
Reason:
A change to the logging limit (wrap count) for the Attentions category was made from other than the Set NEWS Database Logging Options panel. The update is rejected.
System Action:
No change is made to the limit.
User Action:
If you wish to change the wrap count for the Attentions category, use the Set NEWS Database Logging Options facility within NEWS Control Functions, NEWS Database Functions.
Reason:
Procedure $NWDBLUP expected to be passed two parameters when invoked but received other than two parameters. P1 and P2 are the two parameters passed (if present).
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
The logging limit for node P1 was not changed.
System Action:
None.
User Action:
None.
Reason:
A value other than asterisk (*) or a number in the range 1 - 999 was entered in the current logging limit field.
System Action:
The process waits for input from the terminal.
User Action:
Enter the required value and press ENTER or exit by pressing PF03.
Reason:
No value has been entered in the current logging limit field.
System Action:
The process waits for input from the terminal.
User Action:
Enter the required value and press ENTER or exit by pressing PF03.
Reason:
The logging limit for the node P2 has been reset to the limit for the category (P1) in which the node occurs.
System Action:
When a record next arrives, CNMPROC will adjust the number of records in the node if necessary.
User Action:
None.
Reason:
The logging limit for the node P2 has been set to P1 for the category in which the node occurs.
System Action:
When a record next arrives, CNMPROC will adjust the number of records in the node if necessary.
User Action:
None.
Reason:
The logging limit for the node P1 was ignored because it already matches that set for the node.
System Action:
None.
User Action:
None.
Reason:
The logging limit for the node P1 was ignored because it already matches that set for the node (the category default).
System Action:
None.
User Action:
None.
Reason:
After processing the record deletion request, no records were found to match the specified criteria.
System Action:
None.
User Action:
None.
Reason:
Parameter P1 is not in the format expected by procedure $NWDBPRG. P2 is the contents of the invalid parameter.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
A key with an invalid date format has been encountered on the NEWSFILE during a database purge operation.
System Action:
The record with this key value will not be deleted. Processing continues for remaining records.
User Action:
Notify your system support representative.
Reason:
Procedure $NWDBPRG was not supplied the required parameter described by
P1 .
System Action:
The process is terminated.
User Action:
Retry the operation. If unsuccessful, contact your systems administrator.
Reason:
A command P1 was entered in the command field of a node detail record display invoked from somewhere other than NEWS Database Review. The command is only supported when the selection list is invoked from NEWS Database Review.
System Action:
The process waits for input from the terminal.
User Action:
Correct the command and retry.
Reason:
The category (P1) passed to procedure $NWDBRDL does not match any category known to the procedure.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
The SNA address list common subvector returned is of a type with which NEWS is not familiar. P1 is the address format type of the subvector.
System Action:
Processing of the RTM record is terminated.
User Action:
None.
Reason:
Procedure $NWDBREF must not run whilst CNMPROC is active.
System Action:
The process is terminated.
User Action:
Stop CNMPROC and retry.
Reason:
PROCESS-ID P1 defined for a record by Category 003 of the NSCNTL file was not found in category 004 of the NSCNTL file.
System Action:
The record is discarded and CNMPROC processing continues.
User Action:
Correct the name of the PROCESS-ID in Cat. 003 of the NSCNTL file or add the required PROCESS-ID to Cat. 004 of the NSCNTL file.
Reason:
A VSAM error occurred during NEWSFILE I/O operation P1 (READ, DELETE or PUT). P2 is the filekey of the master record, P3 is the file return code and P4 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
The conversion of the NEWS Database from V2.0 has begun. This may take some time depending on the amount of records in the database.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWDBREF was unable to create a VARTABLE of the name specified by the 'ID=' in the message. The reason for failure is indicated by the FDBK code in P1.
System Action:
The process is terminated.
User Action:
Determine the reason for failure, correct and retry. The FDBK code definitions may be found in the &VARTABLE ALLOC statement description in the NCL Reference.
Reason:
P1 is a count of the Category 05 records deleted from the NEWSFILE during conversion.
System Action:
Processing continues.
User Action:
None.
Reason:
P1 is a count of the Category 9 records deleted from the NEWSFILE during conversion.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWDBREF is unable reformat any more records because the required VARTABLE is not allocated.
System Action:
The process is terminated.
User Action:
Determine the reason for failure, correct and retry.
Reason:
Procedure $NWDBREF has successfully completed reformatting the NEWSFILE.
System Action:
Processing continues.
User Action:
None.
Reason:
CNMPROC may now be started.
System Action:
The process terminates.
User Action:
Start CNMPROC as required.
Reason:
Not all records have been reformatted.
System Action:
The process is terminated.
User Action:
Determine the cause for failure, correct the error and retry.
Reason:
Procedure $NWDBREF was unable to add a record identified by P1 to the VARTABLE. The reason for failure is indicated by the FDBK code in P2.
System Action:
The process is terminated.
User Action:
Determine the reason for failure, correct and retry. The FDBK code definitions may be found in the &VARTABLE ADD statement description in the NCL Reference.
Reason:
Procedure $NWDBREF was unable to convert the record identified by the key P1 to the new NEWSFILE format. The record has been deleted.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWDBREF detected a record (identified by P1 ) that used a non-standard (user defined) display procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
A VSAM error occurred during the update of a NEWSFILE master record. P1 is the filekey of the master record, P2 is the file return code and P3 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
Procedure $NWDBREF attempted to set an exclusive lock on the NEWSFILE but was unsuccessful. The owner of the lock is indicated by P1. P2 is the return code and P3 is the FDBK code from the LOCK statement.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
P1, P2 and P3 are the respective number of detail records updated, master records updated and records deleted.
System Action:
Processing continues.
User Action:
None.
Reason:
The node name passed to procedure $NWNCPGT to determine the owning NCP does not belong to a PU or resides in another domain.
System Action:
None.
User Action:
Determine the owning NCP through other means.
Reason:
The owning NCP for node P1 cannot be determined.
System Action:
None.
User Action:
Ensure that the specified node name is correct, if so the owning NCP will have to be determined through other means.
Reason:
A request has timed out whilst waiting for a response.
System Action:
Processing is terminated.
User Action:
Retry the function.
Reason:
An incorrect number of parameters were passed to procedure $NWNPFCK.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
A value other than 'D', 'M' or 'V' was passed to procedure $NWNPFCK as the type of check to be performed.
System Action:
None.
User Action:
Correct the error and retry.
Reason:
NPF checking has determined that User P1 is denied access to the specified resource.
System Action:
Access to the resource is denied.
User Action:
Contact your systems administrator if you require access to this resource.
Reason:
The user P1 attempted to update the NSCNTL file without the appropriate authority level.
System Action:
The process is terminated.
User Action:
Contact your systems administrator if you need this level of authority.
Reason:
The input data set name required to update the NSCNTL file has been omitted.
System Action:
The process waits for input from the terminal.
User Action:
Enter the required data set name or press PF03 to exit the procedure.
Reason:
The input data set name required to update the NSCNTL file is invalid.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the procedure.
Reason:
The operating system P1 is not known, so the file cannot be dynamically allocated.
System Action:
The process waits for input from the terminal.
User Action:
Take note of the message and contact your systems administrator.
Reason:
While attempting to allocate the NSCNTL file update input data set, the INTREAD queue limit was exceeded. It cannot be determined if the file was successfully allocated.
System Action:
The process waits for input from the terminal.
User Action:
Retry the operation, if unsuccessful contact your systems administrator in order to increase the queue limit.
Reason:
While attempting to open the NSCNTL file update input file P1, the INTREAD queue limit was exceeded. It cannot be determined if the file was successfully opened.
System Action:
The process waits for input from the terminal.
User Action:
Retry the operation, if unsuccessful contact your systems administrator in order to increase the queue limit.
Reason:
An attempt to access the file P1 failed because it was unavailable. The return code (P2) 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 the NCL Reference in the section for the &FILEID verb.
Reason:
A VSAM error occurred during a get I/O operation on the NSCNTL update input file. P1 is the file return code and P2 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, take note of the error message and contact your systems administrator.
Reason:
The file specified as input to the NSCNTL file update was found to be empty.
System Action:
The process terminates.
User Action:
Ensure that the correct data set name has been specified and retry the operation.
Reason:
The update of the NSCNTL file has completed successfully.
System Action:
None.
User Action:
None.
Reason:
An attempt to access the NSCNTL file 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 the NCL Reference in the section for the &FILEID verb.
Reason:
A VSAM error occurred during a NSCNTL file get I/O operation. P1 is the filekey of the record, P2 is the file return code and P3 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, take note of the error message and contact your systems administrator.
Reason:
Press the 'ENTER' key to confirm the update of the current NSCNTL file record or press PF03 to cancel it.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to confirm or press 'PF03' to cancel.
Reason:
A VSAM error occurred during a NSCNTL file put I/O operation. P1 is the filekey of the record, P2 is the file return code and P3 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, take note of the error message and contact your systems administrator.
Reason:
The Backup Focal Point definition has not been defined and therefore cannot be browsed or deleted.
System Action:
The action is rejected.
User Action:
None.
Reason:
The update of the Backup Focal Point definition was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
The Backup Focal Point definition was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
The deletion of the Backup Focal Point definition was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
The Nesting Focal Point definition has not been defined and therefore cannot be browsed or deleted.
System Action:
The action is rejected.
User Action:
None.
Reason:
The update of the Nesting Focal Point definition was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
The Nesting Focal Point definition was successfully deleted.
System Action:
None.
User Action:
None.
Reason:
The deletion of the Nesting Focal Point definition was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
A value other than a number in the range 2 - 129 was entered in the LU LOCADDR field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and press ENTER or exit by pressing PF03.
Reason:
A number outside the range 2 - 255 was entered in the LU LOCADDR field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and press ENTER or exit by pressing PF03.
Reason:
The category (P1) passed to procedure $NWDBRNL does not match any category known to the procedure.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
Procedure $NWDBRO is unable to close the NEWSFILE to perform a re-organisation because the file is still in use by other users.
System Action:
Processing is terminated.
User Action:
Ensure no users are accessing the file and then retry the operation.
Reason:
Following a successful re-organisation of the NEWSFILE, $NWDBRO failed to successfully open the NEWSFILE.
System Action:
News database logging remains suspended.
User Action:
Follow your installation's standards to recover from this condition or notify your systems administrator.
Reason:
A request to re-organise the NEWSFILE was cancelled by the user when confirmation was requested.
System Action:
Processing terminates.
User Action:
None.
Reason:
A request to re-organise the NEWSFILE has completed successfully.
System Action:
If CNMPROC and NEWS database logging was active, logging will now resume.
User Action:
None.
Reason:
$NWDBRO received an error code indicating that the attempt to re-organise the NEWSFILE was unsuccessful. More details of the failure may be found in the activity log.
System Action:
Logging is suspended.
User Action:
Determine the cause of the failure, correct and retry.
Reason:
A re-organisation of the NEWSFILE is currently in progress.
System Action:
NEWS logging is suspended and processing continues.
User Action:
None.
Reason:
Following a successful re-organisation of the NEWSFILE, $NWDBRO failed to successfully open the NEWSFILE.
System Action:
News database logging remains suspended.
User Action:
Follow your installation's standards to recover from this condition or notify your systems administrator.
Reason:
$NWDBRO received an error code indicating that the attempt to re-organise the NEWSFILE was unsuccessful. More details of the failure may be found in the activity log.
System Action:
Logging is suspended.
User Action:
Determine the cause of the failure, correct and retry.
Reason:
A procedure was invoked to access the NEWS database but was not passed a record key.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
A procedure was invoked to access the NEWS database but was not passed a record key.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
Procedure $NWDBSYN expected to be passed two parameters when invoked but received other than two parameters. P1 and P2 are the two parameters passed (if present).
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, contact your systems administrator.
Reason:
The count of detail records in the master record for node P1 within a category has been successfully resynchronised to match the count of actual detail records.
System Action:
None.
User Action:
None.
Reason:
A VSAM error occurred during NEWSFILE I/O operation P1 (GET or PUT). P2 is the filekey of the master record, P3 is the file return code and P4 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
The count of detail records in the master record for node P1 within a category matches the count of actual of actual detail records. No resynchronisation is necessary.
System Action:
None.
User Action:
None.
Reason:
An attempt to access the NEWSFILE failed because it was unavailable. The return code (P1) indicates the cause. The message P2 written to the LOG will provide further information on the cause of the failure.
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 the NCL Reference in the section for the &FILE SET verb.
Reason:
A request to display information about a detail record, such as DUMP or VECTOR, is unable to be satisfied because the requested information is not available.
System Action:
None.
User Action:
None.
Reason:
A 'RESEND' request has been received for a record but there is no CNM data associated with the record.
System Action:
None.
User Action:
None.
Reason:
A destination type other than 'DOMAIN', 'LINKNAME' or 'SSCPNAME' has been appended to the 'RESEND' command.
System Action:
None.
User Action:
Correct the destination type and name and retry the command.
Reason:
A CNM record has been successfully resent using the 'RESEND' command.
System Action:
None.
User Action:
None.
Reason:
This message is displayed when the ASCII or EBCDIC command has been entered during display of a NEWS record. It confirms that the command has been successful and that the character formatted data will now be displayed in the format requested ( p1 = ASCII or EBCDIC).
System Action:
None.
User Action:
None.
Reason:
A solicitation request to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
A number outside the range 2 - 129 was entered in the 3x74 LU LOCADDR field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and press ENTER or exit by pressing PF03.
Reason:
A number outside the range 2 - 129 was entered in the RETRIEVE STATUS field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and press ENTER or exit by pressing PF03.
Reason:
A value other than 'N' or a number in the range 2 - 129 was entered in the RETRIEVE STATUS field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and press ENTER or exit by pressing PF03.
Reason:
The request P1 passed to procedure $NWREQMS is invalid.
System Action:
The request is rejected.
User Action:
Correct the error and retry.
Reason:
When CNMPROC attempted to write an SMF record, it discovered that SMF was not active. P1 is the FDBK code from the SMFWRITE verb.
System Action:
The record is not written to SMF.
User Action:
Start SMF, or turn SMF logging off in the Network Services facility.
Reason:
When attempting to write a record to SMF, CNMPROC received a return code indicating that the write was unsuccessful. P1 is the FDBK code from the
SMFWRITE verb.
System Action:
SMF logging for NEWS records is turned off.
User Action:
Determine the cause of the error and correct it.
Reason:
When attempting to write a record to SMF, CNMPROC received a return code indicating that the write failed because SMF is not supported or CNMPROC is not APF authorised to write SMF records.
System Action:
SMF logging for NEWS records is turned off.
User Action:
Have CNMPROC APF authorised to write SMF records and turn on SMF logging in the Network Services facility.
Reason:
When attempting to write a record to SMF, CNMPROC received a return code indicating that the write failed because it was not authorised to write Type 37 SMF records.
System Action:
SMF logging for NEWS records is turned off.
User Action:
Have CNMPROC authorised to write Type 37 SMF records and turn on SMF logging in the Network Services facility.
Reason:
The value P1 cannot be specified for the 'RESPONSE=' parameter when the 'REPORT' parameter is set to 'EC'.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
A solicitation request for secondary end error data to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
This is the last of a series of messages issued when a request for secondary end error data has been issued and indicates that there is no more information to follow for this request.
System Action:
None.
User Action:
None.
Reason:
An undetermined error occurred during a P1 solicitation request.
System Action:
The process is terminated.
User Action:
Determine the cause of the error and, if possible, correct it before retrying the command.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the description of the component (device) being solicited.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the BLK-ID of the device being solicited.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued and is the major heading for the results of the test performed.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of Test commands received by the PU (with or without valid FCS) and P2 is the count of Test responses sent by the PU in response to a Test command with a valid FCS.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the difference between the two counts in message EWDD08.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued and is the major heading for the results of the test performed.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. The PU responding to this request failed to return any valid data for the test.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of hardware errors detected by the device and P2 is the count of communication adapter errors.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of negative responses originated by the PU.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. This message indicates that communications adapter errors have occurred but have not yet been reported via a RECFMS type 3 record.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. This message indicates that communications adapter errors have occurred but have already been reported via a RECFMS type 3 record.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued and is the major heading for the results of the test performed.
System Action:
None.
User Action:
None.
Reason:
P1 is a type of communications adapter that is not known to this procedure.
System Action:
The formatting for error statistics cannot proceed if the adapter type is unknown because the counters are device (adapter) dependent.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the type of communications adapter.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of the number of productive timeouts and P2 is the count of primary station aborts.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of non-productive timeouts/receive overruns and P2 is the count of primary station aborts.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of idle timeouts and P2 is the count of SDLC command rejects caused by invalid SDLC frames.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of frames retransmitted and P2 is count of DCE errors.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of overruns and P2 is the count of transmit timeouts.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of underruns and P2 is the count of invalid status conditions caused by hardware errors.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of times the connection command retry count was exceeded and P2 is the count of times the communication adapter has caused a machine check.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of FCS (Frame Check Sequence) errors.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the total count of all errors displayed by previous messages.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of non-productive timeouts and P2 is the count of I-frames transmitted.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of I-frames received and P2 is the count of frames retransmitted.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of FCS (Frame Check Sequence) errors and P2 is the count of SDLC command rejects caused by invalid SDLC frames.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of DCE errors.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of commands rejected because of no initialization and P2 is the count of data errors detected during internal cycle-steal operations.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of SDLC command rejects caused by invalid SDLC frames and P2 is the count of data checks.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count Sense commands received when the adapter was not initialised and P2 is the count of RUs that were too long.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of parity errors detected on the channel bus-out during the selection sequence and P2 is the count of Connect commands received when already connected.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of errors due to a parity check on the bus-out during a Write and P2 is the count of Disconnect commands received when the PU was active.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of internal parity errors during channel writes and P2 is the count of RUs that were too long to be accepted.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count internal parity errors during reads and P2 is the count of Connect parameter errors.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count internal parity errors during channel reads and P2 is the count of frames incorrectly sequenced.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count I-frames transmitted and P2 is the count of I-frames received.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count RR-frames transmitted and P2 is the count of RR-frames received.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count RNR-frames transmitted and P2 is the count of RNR-frames received.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of reject frames transmitted and P2 is the count of reject frames received.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of retransmissions and P2 is the count of FCS (Frame Check Sequence) errors.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of errors on the receive side and P2 is the count of receive-side overruns.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of underruns on the transmit side.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of I-packets transmitted and P2 is the count of I-packets received.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of RR packets sent and P2 is the count of RR packets received.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of RNR packets sent and P2 is the count of RNR packets received.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of interrupt packets transmitted and P2 is the count of interrupt packets received.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of connection requests and P2 is the count of connections.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count of reset indications and P2 is the count of clear indications.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for secondary end error data has been issued. P1 is the count data packets with the D-bit transmitted and P2 is the count of data packets with the D-bit received.
System Action:
None.
User Action:
None.
Reason:
Procedure $NWSV0C was called to format a x'0C' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV0C was called to build a x'0C' sub-vector but one of the supplied hierarchy names (P1) passed is greater than eight characters in length.
System Action:
The process is terminated.
User Action:
Correct the hierarchy name and retry the operation.
Reason:
Procedure $NWSV0C was called to build a x'0C' sub-vector but one of the supplied hierarchy names (P1) passed has no associated resource type.
System Action:
The process is terminated.
User Action:
Ensure each name has an associated resource type and retry the operation.
Reason:
Procedure $NWSV0C was called to build a x'0C' sub-vector but no hierarchy names were passed to build the sub-vector.
System Action:
The process is terminated.
User Action:
Ensure that the resource hierarchy names and associated types are supplied and retry the operation.
Reason:
RTM status information is not available for LU P1.
System Action:
The process waits for input from the terminal.
User Action:
Enter required data in all fields to continue or exit by pressing PF03.
Reason:
A value other than 'Y' or 'N' has been entered in the field flagged as being in error.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to return to the previous panel.
Reason:
A value less than the previous boundary value or greater than 1638.3 has been entered in one of the 'New Boundary' fields or a 'New Boundary' field has been left blank when one of the following 'New Boundary' fields contains a value.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
A value other than a number in the range 1 - 4 has been entered in the 'Set RTM Definition' field.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry.
Reason:
Press the 'ENTER' key to send the RTM configuration update to the specified device(s).
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to send the update or press 'PF03' to exit the panel.
Reason:
Press the 'ENTER' key to send a request to reset the RTM counters for the specified device(s).
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to send the reset request or press 'PF03' to exit the panel.
Reason:
No fields have been changed on the 'Alter RTM Status' panel.
System Action:
The process waits for input from the terminal.
User Action:
Make the required changes and continue or press 'PF03' to exit the panel.
Reason:
The request to alter RTM status for the specified LU(s) has been accepted by the PU.
System Action:
None.
User Action:
None.
Reason:
A request for RTM (Response Time Monitor) status for a specific LU P1 has been sent but the response has indicated an error in processing the request. The System Sense code P2 and User Sense code P3 indicate the nature of the failure.
System Action:
None.
User Action:
Investigate the reason for the failure.
Reason:
Press the 'ENTER' key to see the alternate RTM display.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to see the alternate RTM display, select an LU for display or press 'PF03' to exit the panel.
Reason:
An RU was received that did not contain any valid RTM data.
System Action:
The contents of the RU are ignored.
User Action:
None.
Reason:
The reset of RTM counters for the specified LU(s) has completed.
System Action:
None.
User Action:
None.
Reason:
The SNA address list common subvector returned is of a type with which NEWS is not familiar. P1 is the address format type of the subvector.
System Action:
The process is terminated.
User Action:
None.
Reason:
There are no RTM Status details available for display.
System Action:
None.
User Action:
None.
Reason:
There is no more data to be displayed following/preceding the current display. P1 indicates the current scrolling direction.
System Action:
None.
User Action:
None.
Reason:
A solicitation request to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
The request to set a new alert generation interval for an FCS device has been accepted by the device.
System Action:
None.
User Action:
None.
Reason:
A value for the Alert Generation Timer Interval for an FCS device has been omitted when the option to alter the interval has been chosen.
System Action:
None.
User Action:
Enter the new value for the Timer Interval and retry or press PF03 to exit the panel.
Reason:
The value entered for the new Alert Generation Interval is not numeric.
System Action:
None.
User Action:
Correct the Timer Interval value and retry or press PF03 to exit the panel.
Reason:
The value entered for the new Alert Generation Interval is not within the range 10 - 9999.
System Action:
None.
User Action:
Ensure that the Timer Interval value is numeric and retry or press PF03 to exit the panel.
Reason:
A solicitation request to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
A solicitation request to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
The request option (P1) passed to procedure $NWDS051 is invalid.
System Action:
Processing is terminated.
User Action:
Correct the error and retry.
Reason:
The response from node P1 is invalid.
System Action:
Processing is terminated.
User Action:
Determine whether the node should support the request. If so, further investigation may be required to determine why an invalid response was returned.
Reason:
The CNM path between the SNA_HUB and the downstream PU is valid and currently active.
System Action:
None.
User Action:
None.
Reason:
The CNM path between the SNA_HUB and the downstream PU is valid but is currently inactive.
System Action:
None.
User Action:
None.
Reason:
The CNM path between the SNA_HUB and the downstream PU is invalid.
System Action:
None.
User Action:
Ensure that the 'DOWNSTREAM PU NAME(S)' are correct. If an invalid name was entered, this message will always be returned in response to a path validation request.
Reason:
Procedure $NWSV01 was called to format a x'01' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV01 was called to format a x'01' sub-vector but the mandatory Local Date/Time subfield (X'10') was not found.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV03 was called to format a x'03' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV03 was called to build a x'03' sub-vector but one of the supplied hierarchy names (P1) passed is greater than eight characters in length.
System Action:
The process is terminated.
User Action:
Correct the hierarchy name and retry the operation.
Reason:
Procedure $NWSV03 was called to build a x'03' sub-vector but one of the supplied hierarchy names (P1) passed has no associated resource type.
System Action:
The process is terminated.
User Action:
Ensure each name has an associated resource type and retry the operation.
Reason:
Procedure $NWSV03 was called to build a x'03' sub-vector but no hierarchy names were passed to build the sub-vector.
System Action:
The process is terminated.
User Action:
Ensure that the resource hierarchy names and associated types are supplied and retry the operation.
Reason:
Procedure $NWSV04 was called to format a x'04' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV04 was called to format a x'04' sub-vector but the supplied format type of the sub-vector (P1) is not supported by this procedure.
System Action:
Processing continues, ignoring the contents of the sub-vector.
User Action:
None.
Reason:
Procedure $NWSV04 was called to build a x'04' (SNA address list) sub-vector but the supplied address format type to be built is not supported by this procedure.
System Action:
The process is terminated.
User Action:
Correct the address format to be built and retry the operation.
Reason:
Procedure $NWSV05 was called to format a x'05' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV05 was called to format a x'05' (resource hierarchy) sub-vector but did not find any of the mandatory sub-fields it expected.
System Action:
Processing continues, ignoring the x'05' sub-vector data.
User Action:
None.
Reason:
Procedure $NWSV10 was called to format a x'10' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV10 was called to format a x'10' sub-vector but no x'11' sub-vector was found within the x'10' sub-vector.
System Action:
Processing continues, ignoring the x'10' sub-vector data.
User Action:
None.
Reason:
Procedure $NWSV31 was called to format a x'31' (free-form text) sub-vector but the variable containing the text was not found.
System Action:
Processing continues, ignoring the free-form text not found.
User Action:
None.
Reason:
The response from node P1 is invalid because no End-of-data flag was included in the RU.
System Action:
Processing is terminated.
User Action:
Determine whether the node should support the request. If so, further investigation may be required to determine why an invalid response was returned.
Reason:
The wait time for response to a request expired before any data was received.
System Action:
Processing is terminated.
User Action:
Retry the command.
Reason:
The request to alter the line status for a 3710 has been accepted by the PU.
System Action:
None.
User Action:
None.
Reason:
No value for the new Line Status for a 3710 device has been entered.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
An incorrect value for the new Line Status for a 3710 device has been entered.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Line Name or Port Number of the line that is changing status must be entered.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Line Name or Port Number of the line that is changing status must be entered but both may not appear on the panel at the same time.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Port Number must be valid hexadecimal.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Port Number must be valid hexadecimal within the range 01AA - 16BB.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Line Name or Port Number being tested must be entered.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Line Name or Port Number being tested must be entered but both may not appear on the panel at the same time.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Port Number must be valid hexadecimal.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Port Number must be valid hexadecimal within the range 01AA - 16BB.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
No new password has been entered.
System Action:
None.
User Action:
Enter the required field and retry or press PF03 to exit the panel.
Reason:
The new password must be not less than 6 and not more than 8 characters in length.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The new password entered is invalid. It must conform to SNA naming conventions.
System Action:
None.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The request to set a new password for a 3710 device has been accepted by the device.
System Action:
None.
User Action:
None.
Reason:
Press the 'ENTER' key to confirm and send the request to change the threshold(s) for the specified device or press PF03 to cancel the change.
System Action:
The process waits for input from the terminal.
User Action:
Press the 'ENTER' key to send the update or press 'PF03' to cancel the change.
Reason:
No value for the new Line Status for a 3710 device has been entered.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Station Type entered must be a numeric value within the range 1 - 5.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The Station Type entered is outside the range 1 - 5.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
No new Threshold values have been entered although a request to alter at least one of these values has been made.
System Action:
The process waits for input from the terminal.
User Action:
Add the required threshold values and retry.
Reason:
The new Threshold value entered must be a numeric value within the range 0‑65535.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The new Threshold value entered is outside the range 0 - 65535.
System Action:
The process waits for input from the terminal.
User Action:
Correct the error and retry or press PF03 to exit the panel.
Reason:
The request to change the threshold(s) for the specified device has been accepted by the device.
System Action:
None.
User Action:
None.
Reason:
The response from node P1 is invalid because no End-of-data flag was included in the RU.
System Action:
Processing is terminated.
User Action:
Determine whether the node should support the request. If so, further investigation may be required to determine why an invalid response was returned.
Reason:
The wait time for response to a request expired before any data was received.
System Action:
Processing is terminated.
User Action:
Retry the command.
Reason:
The device identified by P1 failed to execute the requested command, it instead sent invalid data in response.
System Action:
Processing is terminated.
User Action:
Determine whether the node should support the request. If so, further investigation may be required to determine why invalid data was returned.
Reason:
An invalid RECFMS RU was received in response to a command.
System Action:
The procedure terminates.
User Action:
Investigate the cause and correct the error.
Reason:
An invalid Element ID was detected in a response to a command.
System Action:
The procedure terminates.
User Action:
Investigate the cause and correct the error.
Reason:
Procedure $NWDS069 encountered an error whilst verifying a translate table from a 3710.
System Action:
The procedure terminates.
User Action:
Investigate the cause and correct the error.
Reason:
Procedure $NWDS069 encountered an error whilst verifying the User Data supplied by a 3710 in response to a request.
System Action:
The procedure terminates.
User Action:
Investigate the cause and correct the error.
Reason:
Procedure $NWDS069 encountered an error whilst verifying Configuration data supplied by a 3710 in response to a request.
System Action:
The procedure terminates.
User Action:
Investigate the cause and correct the error.
Reason:
Procedure $NWSV42 was called to format a x'42' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
P1 is the sense code returned when an LPDA-2 command has been executed. If the sense code indicates that an error has occurred during the command, the screen display will give a detailed reason for the error if known.
System Action:
None.
User Action:
None.
Reason:
Procedure $NWSV50 was unable to determine what command was sent to an LPDA-2 modem when attempting to display the results of the command. P1 is the unknown command code.
System Action:
None.
User Action:
None.
Reason:
Procedure $NWSV50 attempted to format a x'50' LPDA-2 response sub-vector but the sub-vector was not passed to it or the contents of the sub-vector did not contain expected sub-fields.
System Action:
Processing of the sub-vector terminates.
User Action:
None.
Reason:
Procedure $NWSV50 was called to format a x'50' sub-vector but the configuration code (P1) used to describe the configuration data to be displayed is not known to the procedure.
System Action:
Processing the x'50' sub-vector terminates.
User Action:
None.
Reason:
Procedure $NWSV51 was called to format a x'51' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV52 was called to format a x'52' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV53 was called to format a x'53' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV53 was called to format a x'53' (link station counters) sub-vector but did not find any of the mandatory sub-fields it expected.
System Action:
Processing continues, ignoring the x'53' sub-vector data.
User Action:
None.
Reason:
Sub-vector X'50' of an NMVT does not exist or is in error. The sub-vector must be present and without error.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to access the NETINFO1 database in order to find information on a sense code which was found in sub-vector X'50' but the file was not available.
System Action:
None.
User Action:
None.
Reason:
A sense code was found in sub-vector X'50' but no information was found on NETINFO1 for this particular code.
System Action:
None.
User Action:
None.
Reason:
Procedure $NWSV54 was called to format a x'54' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV54 was called to format a x'54' (BSC link station counters) sub-vector but did not find any of the mandatory sub-fields it expected.
System Action:
Processing continues, ignoring the x'54' sub-vector data.
User Action:
None.
Reason:
Procedure $NWSV56 was called to format a x'56' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV56 was called to format a x'56' (optional link station counters) sub-vector but did not find any of the mandatory sub-fields it expected.
System Action:
Processing continues, ignoring the x'56' sub-vector data.
User Action:
None.
Reason:
Procedure $NWSV57 was called to format a x'57' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV57 was called to format a x'57' (LAN physical link station counters) sub-vector but did not find any of the mandatory sub-fields it expected.
System Action:
Processing continues, ignoring the x'57' sub-vector data.
User Action:
None.
Reason:
Procedure $NWSV58 was called to format a x'58' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV58 was called to format a x'58' (NCP specific product data) sub-vector but did not find any of the mandatory sub-fields it expected.
System Action:
Processing continues, ignoring the x'58' sub-vector data.
User Action:
None.
Reason:
Procedure $NWSV8A was called to format a x'8A' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV8A was called to format a x'8A' (link event) sub-vector but did not find any of the mandatory sub-fields it expected.
System Action:
Processing continues, ignoring the x'8A' sub-vector data.
User Action:
None.
Reason:
Procedure $NWSV8C was called to format a x'8C' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV8C was called to format a x'8C' (link station data) sub-vector but did not find any of the mandatory sub-fields it expected.
System Action:
Processing continues, ignoring the x'8C' sub-vector data.
User Action:
None.
Reason:
Procedure $NWSV96 was called to format a x'96' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
Procedure $NWSV98 was called to format a x'98' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
While attempting to build a display from details contained in the sub-vector, an error occurred in the processing.
System Action:
The building of information from the sub-vector is discontinued.
User Action:
A display of the contents of the sub-vector is available from the main display if desired. This is shown when 'V' is entered in the command field and the ENTER key is pressed.
Reason:
A solicitation request to a node for P1 status data has been accepted by by the node. P1 indicates whether LINK or DTE status data was requested.
System Action:
None.
User Action:
None.
Reason:
An undetermined error occurred during a P1 solicitation request where P1 is the type of status request made - LINK or DTE.
System Action:
The process is terminated.
User Action:
Determine the cause of the error and, if possible, correct it before retrying the command.
Reason:
Any parameter other than "FILE" is invalid for the "RESPONSE" keyword when a file DDNAME is specified.
System Action:
The process is terminated.
User Action:
Correct the "RESPONSE" keyword operand and retry the operation.
Reason:
Procedure $NWVPDSO cannot detect whether the vital product data output file P2 opened or closed successfully because it is unable to read the responses from the open or close command. This is because the INTREAD queue limit has been exceeded. P1 is the operation attempted.
System Action:
The process is terminated.
User Action:
Investigate why the queue has become congested. The maximum queue limit is 32767.
Reason:
A solicitation request for vital product data to a node has been accepted by the node.
System Action:
None.
User Action:
None.
Reason:
This is the last of a series of messages issued when a request for vital product data has been issued and indicates that there is no more information to follow for this request.
System Action:
None.
User Action:
None.
Reason:
An undetermined error occurred during a vital product data solicitation request. P1 is the code returned indicating that an error occurred.
System Action:
The process is terminated.
User Action:
Determine the cause of the error and, if possible, correct it before retrying the command.
Reason:
All vital product data is returned as part of a x'10 sub-vector, but none was received. No vital product data can be created.
System Action:
The process continues if the option is to solicit data for the controller and all attached devices, else the process is terminated.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the component description of the product as defined in category 1 of the Network Services Control (NSCNTL) file.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the type and model (if applicable) of the hardware product. e.g. 3745 (MODEL 170).
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the serial number of the hardware product.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the repair identifier number of the hardware product.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the program number of the software product.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the data and time (in the format DD-MON-YEAR HH:MM) that the software product was modified by the user.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the type and model (if applicable) of the hardware product (e.g. 3745 (MODEL 170)) being emulated.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the software serviceable component number of the product as defined by service personnel.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the release level of the software serviceable component.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the common level (in the format Vvv.rr.mm) of the software product.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the common name of the software product.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 identifies the set of executable instructions of the software product customised by the user.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the Engineering Change (EC) level of the microcode component of the hardware product.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the common name of the hardware product.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the LU address of a device attached to a PU.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 may be either a sequence number to indicate the relative order of records delivered or an interval of time measurement since an alert was last sent by the device.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the unique port number of the owning PU to which the device is attached.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the hardware group of the attached device.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the type of port to which the device is attached.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the port number relative to the hardware group in which it is defined.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is set to 'ON', 'OFF' or 'UNKNOWN' to indicate the current power-on status of the device.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is set to 'YES', 'NO' or 'UNKNOWN' to indicate whether or not the device has been powered on since the last time vital product data was sent by the device.
System Action:
None.
User Action:
None.
Reason:
An attempt to access the vital product data output file (identified by P1 ) was unsuccessful. The return code (P2) indicates the cause.
System Action:
The process is terminated.
User Action:
Determine why the file is unavailable, correct the problem and retry the operation.
Reason:
A VSAM error occurred during a put I/O operation to the vital product data output file (identified by P1). P2 is the filekey of the record, P3 is the file return code and P4 is the VSAM FDBK code.
System Action:
Processing continues, attempting to write any more records to the file.
User Action:
Take note of the message and inform your systems administrator if you are unable to resolve the problem.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 identifies the product vendor, e.g. the company.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 describes the physical location of the product.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is the LAN universally-assigned address which is unique across all LAN adapters whose addresses are controlled by the IEEE.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is a description of the data following in message EWG935.
System Action:
None.
User Action:
None.
Reason:
This is one of a series of messages issued when a request for vital product data has been issued. P1 is data as described by the text of message EWG934 which immediately precedes this message.
System Action:
None.
User Action:
None.
Reason:
Any parameter other than FILE is invalid for the RESPONSE keyword when the YEARFMT parameter is specified.
System Action:
The process is terminated.
User Action:
Correct the RESPONSE keyword operand and retry the operation.
Reason:
The PPI alert receiver procedure $NWPPIAR has terminated during start-up processing. This message follows another message which gives the reason for the termination of the procedure.
System Action:
The process terminates.
User Action:
Dtermine the original failure reason, correct, and retry.
Reason:
The PPI alert receiver procedure $NWPPIAR has terminated during start-up processing because the Program-to-Program Interface is unavailable.
System Action:
The process terminates.
User Action:
None.
Reason:
The PPI alert receiver procedure $NWPPIAR has terminated during start-up processing because the &PPI DEFINE failed. P1 and P2 are, respectively, the return and FDBK codes from the &PPI DEFINE verb.
System Action:
The process terminates.
User Action:
None
Reason:
The PPI alert receiver procedure $NWPPIAR has terminated. P1 and P2 are, respectively, the return and FDBK codes from the &PPI RECEIVE verb.
System Action:
The process terminates.
User Action:
None
Reason:
Procedure $NWPPIAR has received an alert across the PPI from P2 but the length (P1) is invalid because it is outside the range of 12 to 512. Message EWGE06 follows, displaying the 12 bytes of data from the alert.
System Action:
The alert data received is ignored.
User Action:
None
Reason:
Procedure $NWPPIAR has received an alert across the PPI but the record is invalid. P1 is the first 12 bytes of the rejected record.
System Action:
None
User Action:
None
Reason:
Procedure $NWPPIAR has received an alert across the PPI from P1 but the alert header is invalid. Message EWGE06 follows, displaying the first 12 bytes of data from the alert.
System Action:
The alert data received is ignored.
User Action:
None
Reason:
Procedure $NWPPIAR has received an alert across the PPI from P3 but the length specified in the major vector header (x'P1') does not match the total length of the data sent. Message EWGE06 follows, displaying the first 12 bytes of data from the alert.
System Action:
The alert data received is ignored.
User Action:
None
Reason:
Procedure $NWPPIAR attempted to send an alert from P1 to CNMPROC but failed. P2 is the return code from the &CNMALERT verb. A message follows giving the reason why the alert failed.
System Action:
Processing continues.
User Action:
None
Reason:
The PPI alert receiver procedure $NWPPIAR has successfully registered to the Program- to-Program Interface as an alert receiver. The NCLID of the process is shown ( P1 ).
System Action:
None
User Action:
None
Reason:
The PPI alert receiver procedure $NWPPIAR is already active. Only one instance of the receiver can be active. The instance that is currently active is identified by its NCLID ( P1 ).
System Action:
The PPI receiver is not started.
User Action:
None
Reason:
The PPI alert receiver procedure $NWPPIAR has terminated during start-up processing because the &PPI DEFINE failed with FDBK=16 indicating that the names receiver ID ( P1 ) is already active in another region in this LPAR. The other region may be NetMaster or another application.
System Action:
The process terminates.
User Action:
If using the Netmaster SubSystem Interface (NMSSI), use the NMSSI's SHOW PPIUSERS command to determine which region is using it. Note that the command must be executed by the NMSSI, for example: SYSCMD F NMSSI,SHOW PPIUSERS
Reason:
The formatting proc for sub-vector X'A0' couldn't interpret the vectors within the X'A0' vector.
System Action:
Format proc ends.
User Action:
Report to tech support if problem persist.
Reason:
Procedure $NWSV4A was called to format a x'4A' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV5C was called to format a x'5C' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
Procedure $NWSV5D was called to format a x'5D' sub-vector but one was not passed to the procedure.
System Action:
Processing continues.
User Action:
None.
Reason:
The generation of a NEWS report failed because the record category to be processed by the Report Writer service procedure was not specified.
System Action:
The generation of the report is terminated.
User Action:
Determine the cause, correct and retry.
Reason:
The generation of a NEWS report failed because an invalid record category was specified.
System Action:
The generation of the report is terminated.
User Action:
Determine the cause, correct and retry.
Reason:
The generation of a NEWS report failed because the system name (NEWS file id) was not specified.
System Action:
The generation of the report is terminated.
User Action:
Determine the cause, correct and retry.
Reason:
The generation of a NEWS report failed because the Report Writer service procedure was unable to access the specified NEWS file.
System Action:
The generation of the report is terminated.
User Action:
Determine the cause, correct and retry.
Reason:
The generation of a NEWS report failed because the Report Writer service procedure detected an error when getting a record from the NEWS file.
System Action:
The generation of the report is terminated.
User Action:
Determine the cause, correct and retry.
Reason:
A X'7D' key was received in a deliver RU. A probably cause is that the session has been terminated by a NetView CSCF session.
System Action:
Control is returned back to the CSCF primary menu with this message.
User Action:
Try again.
Reason:
The INWAIT value on a PANEL statement has expired.
System Action:
User is logged off and returned to the primary menu with this message.
User Action:
Try again.
Reason:
An error has occurred on a FILE process. This is the NSCNTL file.
System Action:
User is logged off and returned to the primary menu with this message.
User Action:
Determine cause of file problem.
Reason:
An error has occurred on a FILE OPEN process.
System Action:
User is logged off and returned to the primary menu with this message.
User Action:
Determine cause of file problem.
Reason:
An error has occurred due to the user specifying invalid parms on the print command.
System Action:
Print function is terminated.
User Action:
Specify correct parms on print command.
Reason:
A PRINT PRINTER=LOG was entered at the COMMAND line and the current screen was printed to the activity log.
System Action:
None.
User Action:
None.
Reason:
This message is presented after a user enters an 'FL' (force logoff) command from the primary CSCF menu.
System Action:
None.
User Action:
User will now be able to use CSCF Control Functions (option 'C') against the controller. NOTE: if there was a user using CSCF against a controller that has just been forced off, the next ENTER or PFKEY will cause a timeout of their session. This is expected, and not a problem.
Reason:
This message is presented to a user if unexpected panel information is sent to CSCF by the controller.
System Action:
None.
User Action:
Call support.
Reason:
A X'7D' key was received in a deliver RU. A probable cause is that the session has been terminated by a NetView CSCF session.
System Action:
Control is returned to the CSCF primary menu with this message.
User Action:
Try again.
Reason:
A CNMREAD with a WAIT=NN has expired and processing has stopped. NOTE: This will be a common occurrence during an IML, since the controller will not respond.
System Action:
Control is returned back to the CSCF primary menu with this message.
User Action:
Try again.
Reason:
An attempt to delete a panel from the CSCF panel menu was unsuccessful as the user doesn't have the proper authorisation to delete CSCF PANELS. The user must have NEWS RESET authority.
System Action:
Panel is not deleted from the NSCNTL file.
User Action:
Contact your system administrator who has the proper authority to delete any CSCF panels.
Reason:
An attempt to purge panels from the command line was was unsuccessful as the user didn't specify the proper parameters for the PURGE commands.
System Action:
Error message returned to user.
User Action:
Enter the correct parameters for the PURGE command.
Reason:
An attempt to purge panels from the command line was was unsuccessful as the user didn't specify the proper parameters for the PURGE command.
System Action:
Error message returned to user.
User Action:
Enter the correct parameters for the PURGE command.
Reason:
An attempt to delete a panel from the CSCF panel menu failed.
System Action:
The CSCF panel is not deleted from the NSCNTL file.
User Action:
Display the panel again, and if it shows up on the CSCF panel menu and you can't delete it then call the support center.
Reason:
An attempt to delete a panel from the CSCF panel menu was successful.
System Action:
Panel is deleted from the NSCNTL file.
User Action:
None.
Reason:
A purge command was issued with a purge date and the number of panels deleted is indicated in the message text.
System Action:
The panels are deleted from the NSCNTL file.
User Action:
None.
Reason:
PRINT is available to the CSCF online user from any controller panel. This message informs the user that the PRINT was successful.
System Action:
The list has been printed.
User Action:
None.
Reason:
The COPIES parameter is available to any CSCF panel on a PRINT command. However, the data associated with this parameter must be greater than 0 and less than 256.
System Action:
The data will not be printed since the COPIES parameter is in error.
User Action:
Correct the copies parameter when retrying the PRINT command so that it is within the specified range.
Reason:
The HOLD parameter is available to any CSCF menu for a PRINT command. However, the data associated with this parameter must be either YES or NO.
System Action:
The data will not be printed since the HOLD parameter is in error.
User Action:
N/A
Reason:
PRINT is available to any CSCF panel from the command line. However, if no data is available then the print will be denied.
System Action:
Nothing will be printed as this is an internal error. The calling proc must ensure that all of the proper variables are in place.
User Action:
N/A
Reason:
When a CSCF print attempted to open up a print request, a request number could not be had. Check Print Services Manager (PSM) to make sure that $PSPOOL is allocated and opened. Also make sure that the printer which was specified is set up correctly.
System Action:
The data will not be printed since a request number was not returned from $PSCALL.
User Action:
Check PSM.
Reason:
PRINT is available to the CSCF online user at any controller panel. This message tells the administrator that the PRINT command was successful but that the printout is on the queue because the HOLD=YES parameter was coded on the PRINT command.
System Action:
The list is on the queue.
User Action:
The printout can be seen on Print Services Manager under the USERID of the administrator. The request number which is contained in this message can be used as an identifier on the PSM.
Reason:
An error has occurred due to the user specifying invalid parms on the call to the CSCF batch interface.
System Action:
Non-zero return code and this message are returned.
User Action:
Correct keyword parm.
Reason:
An error has occurred due to the user specifying invalid value for the FUNC parm for the CSCF batch interface.
System Action:
Non-zero return code and this message are returned.
User Action:
Correct keyword parm value.
Reason:
An error has occurred due to the user not providing a NODE parm for the the CSCF batch interface.
System Action:
Non-zero return code and this message are returned.
User Action:
Supply NODE parm
Reason:
An error has occurred due to the user not providing a KEY parm for the the CSCF batch interface.
System Action:
Non-zero return code and this message are returned.
User Action:
Supply KEY parm
Reason:
An error has occurred due to the user providing a KEY parm other than a PFKEY or ENTER for the CSCF batch interface.
System Action:
Non-zero return code and this message are returned.
User Action:
Supply correct KEY parm
Reason:
An error has occurred due to no $NWCS#ID variable for the CSCF batch interface. Be sure that the calling procedure has CONTROL SHRVARS=($NWCS#,$NW#USR).
System Action:
Non-zero return code and this message are returned.
User Action:
Retry Batch procedure.
Reason:
An attempt to call the CSCF batch interface by a user that does not have NEWS authority.
System Action:
End processing.
User Action:
Obtain NEWS authority.
Reason:
A procedure was invoked to access the NEWSFILE file but was not passed any record key.
System Action:
The process is terminated.
User Action:
None.
Reason:
An attempt to access the NSCNTL failed. The return code (P1) indicates the cause.
System Action:
The process is terminated.
User Action:
Determine if the NSCNTL file is available. The meaning of the return code can be found in the NCL Reference in the section for the &FILEID verb.
Reason:
An attempt to break down a CNM record into its constituent parts has failed.
System Action:
Processing of the CNM record is terminated.
User Action:
None.
Reason:
The procedure for decoding CNM records for the problem management application has encountered an MDO mapped by an unrecognised map. P1 is the name of the unrecognised map.
System Action:
Processing of the CNM record is terminated.
User Action:
None.
Reason:
An attempt to break down a CNM record into its constituent parts has failed.
System Action:
Processing of the CNM record is terminated.
User Action:
None.
Reason:
The procedure for decoding CNM records for the problem management application was unable to extract any valid information from a CNM record.
System Action:
Processing of the CNM record is terminated.
User Action:
None.
Reason:
The NEWS problem management server ($NWPRMON) is no longer supported.
System Action:
None.
User Action:
Update your NetMaster for SNA initialization procedure, normally $NSINIT, to remove the call.
Reason:
The user P1 attempted to modify or delete records in the NSCNTL file without the appropriate authority level.
System Action:
The process is terminated.
User Action:
Contact your security administrator to upgrade your level of authority.
Reason:
An attempt to access the NSCNTL failed because it was unavailable. The return code (P1) indicates the cause.
System Action:
The process is terminated.
User Action:
Determine if the NSCNTL file is available. The meaning of the return code can be found in the NCL User Reference in the section for the
FILEID verb.
Reason:
The number of records indicated by P1 have been deleted from Category 027 of the NSCNTL file.
System Action:
None.
User Action:
None.
Reason:
When attempting to delete Category 027 of the NSCNTL file, a VSAM error occurred. P1 is the file return code and P2 is the VSAM FDBK code.
System Action:
Processing terminates.
User Action:
Determine the cause of the error and retry after correction.
Reason:
A request has timed out whilst waiting for a response from a device.
System Action:
Processing is terminated.
User Action:
Retry the function.
Reason:
A parameter was not supplied when calling the Frame Route details procedure.
System Action:
None.
User Action:
Correct the command and retry.
Reason:
A parameter was not supplied when calling the NEWSFILE common processor.
System Action:
None.
User Action:
Correct the command and retry.
Reason:
The value supplied for the keyword P1 does not match any of the valid values defined. P2 is the invalid value.
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
An attempt to access the NEWSFILE 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 the NCL Reference in the section for the &FILE SET verb.
Reason:
An attempt to access the NEWSFILE failed because it was unavailable. The return code (P1) indicates the cause. The message P2 written to the LOG will provide further information on the cause of the failure.
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 the NCL Reference in the section for the &FILE SET verb.
Reason:
A lock is in place on the NEWS database, temporarily restricting access to it.
System Action:
None.
User Action:
Retry the action. If the problem persists, consult your systems administrator.
Reason:
A VSAM error occurred during NEWSFILE I/O operation P1 (GET, DELETE, ADD or PUT). P2 is the filekey of the record, P3 is the file return code and P4 is the VSAM FDBK code.
System Action:
The file operation is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
A VSAM error occurred during NEWSFILE I/O operation P1 (GET, DELETE, ADD or PUT). P2 is the key of the record, P3 is the file return code and P4 is the VSAM FDBK code. The message P2 written to the LOG will provide further information on the cause of the failure.
System Action:
The file operation is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
The specified sequence name does not exist.
System Action:
The call is rejected.
User Action:
Correct the call and retry.
Reason:
The call parameters conflict with those used when the sequence was created.
System Action:
The call is rejected.
User Action:
Correct the call and retry.
Reason:
A VSAM error occurred during NEWSFILE I/O operation P1 (GET, DELETE, ADD or PUT). P2 is the filekey of the record, P3 is the file return code.
System Action:
The file operation is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
The NEWSFILE access procedure was invoked to retrieve a record from the NEWS database but the key provided does not match any record in the NEWS database.
System Action:
The process is terminated.
User Action:
Retry the operation, if unsuccessful, the record has probably been deleted.
Reason:
The name of the Backup Focal Point has not been defined for use by Entry Points registered to this Focal Point.
System Action:
No Backup Focal Point is defined.
User Action:
If this is required, use SNA : Focal Point Administration (/SNAFPA) to define the entry.
Reason:
An attempt to obtain the name of the Backup Focal Point (for Entry Points registered to this system's Focal Point for Alert Management) from the NSCNTL file has failed. P1 is the reference to the activity log message that more fully describes the file error.
System Action:
The Backup Focal Point is not defined.
User Action:
See the explanation for the referenced message.
Reason:
An attempt to initiate a relationship (for Problem Management) between this system's Focal Point (as an Entry Point) and our nesting Focal Point has failed because the name of the nesting Focal Point has not been defined to this system.
System Action:
No Nesting Focal Point is defined.
User Action:
If this is required, use SNA : Focal Point Administration (/SNAFPA) to define the entry.
Reason:
An attempt to obtain the name of the Problem Management nesting Focal Point from the NSCNTL file has failed. P1 is the reference to the activity log message that more fully describes the file error.
System Action:
The Nesting Focal Point is not defined.
User Action:
See the explanation for the referenced message.
Reason:
An attempt to access the NSCNTL file has returned an error code indicating that no access is allowed to the file.
System Action:
The process is terminated.
User Action:
Refer the problem to your systems administrator. This error indicates that your administrator has restricted access to the file using the NCLEX01 exit.
Reason:
In attempt to access the NSCNTL failed because it was unavailable. P1 is the reference to the activity log message that more fully describes the file error.
System Action:
The process is terminated.
User Action:
See the explanation for the referenced message.
Reason:
A VSAM error occurred during NSCNTL file GET I/O operation. P1 is the file key of the record, P2 is the file return code and P3 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem. See the NCL Reference Manual for an explanation of &FILE return code values.
Reason:
The command generated is sent as a sub-vector 31 Self-Defining Text Message. The maximum that it can accommodate is 253 characters. This request has exceeded the limit, possibly due to lengthy names.
System Action:
The request is ignored.
User Action:
Check all inputs. If possible, split the request into two or more commands.
Reason:
This message is sent in response when the command request is unable to be satisfied. P1 is the sense code giving the reason for the request failure.
System Action:
None.
User Action:
None.
Reason:
Heading line to indicate free-form message text follows. All following text will be prefixed by message number EWR004.
System Action:
None.
User Action:
None.
Reason:
Free-form message text received from a response to a request.
System Action:
None.
User Action:
None.
Reason:
An attempt to access the NSCNTL file has returned an error code indicating that no access is allowed to the file.
System Action:
The process is terminated.
User Action:
Refer the problem to your installation help desk.
Reason:
An attempt to access the NSCNTL failed because it was unavailable. The return code (P1) indicates the cause.
System Action:
The process is terminated.
User Action:
Determine if the NSCNTL file is available. The meaning of the return code can be found in the NCL User Reference in the section for the
FILE OPEN verb.
Reason:
A VSAM error occurred during NSCNTL I/O operation P1 (GET, DELETE, ADD or PUT). P2 is the filekey of the record, P3 is the file return code and P4 is the VSAM FDBK code.
System Action:
The process is terminated.
User Action:
Determine the cause and take the necessary action to correct the problem.
Reason:
An error occurred during an attempt to map the data received from the node P1 .
System Action:
A dump of the data that was received and other diagnostic information are written to the log.
User Action:
Send the diagnostic information to your local support representative, with a detailed description on how the problem can be repeated.
Reason:
An unexpected response P1 was received by the $NWDS14S procedure in in response to an execute command that was previously sent.
System Action:
A dump of the response is written to the log along with other diagnostic information.
User Action:
This problem may be due to an SNA/Management Services application that is violating the protocol. Thus it may not be a SOLVE problem.
A dump of the request and reply MDOs will be written to the log to aid diagnosis of the problem.
If you believe it is a SOLVE problem, pass the diagnostic information to your local support representative, with a detailed description on how the problem can be repeated.
Reason:
The $NWDS14S attempted to receive some data but there was no associated outstanding request. This condition should not occur.
System Action:
A dump of the request is written to the log along with other diagnostic information.
User Action:
A dump of the request will be written to the log to aid diagnosis of the problem. Pass the diagnostic information to your local support representative, with a detailed description on how the problem can be repeated.
Reason:
A request has timed out during the wait for a response from a device.
P1 is the amount of wait time before the request was abandoned.
System Action:
The request fails.
User Action:
Retry the function.
Reason:
A request sent to the remote node P1 was rejected with a sense code of
P2 .
System Action:
None.
User Action:
Obtain information on the sense code, correct the condition if possible, and retry.
Reason:
The request that was issued could not be routed to the control point. The sense code returned was P1 .
System Action:
None.
User Action:
Obtain information on the sense code, correct the condition if possible, and retry. Check that the specified resource name is correct.
Reason:
THe SNAMS feature is not licenced.
System Action:
The requested function is not performed.
User Action:
If the SNAMS feature was excluded at SOLVE startup, include it. Otherwise arrange to have the SNAMS feature licenced.
Reason:
User P1 has attempted to invoke a function of the Network Management feature but is not authorised to do so.
System Action:
The process is terminated.
User Action:
Contact your systems administrator if you feel you should have access to the Network Management feature.
Reason:
Required parameter P1 has been omitted when calling the procedure $NWDS14S.
System Action:
The process is terminated.
User Action:
Correct the error and retry.
Reason:
An unexpected error has occurred when the $NWDS14S procedure sent an SNAMS request to the indicated node.
System Action:
The process is terminated.
User Action:
Contact your product support representative.
| Copyright © 2012 CA. All rights reserved. |
|