|
Use this chapter to identify and resolve problems with the SNA View mainframe application. When you encounter an unfamiliar message or problem, consult this chapter before taking any other action.
This chapter contains two major sections:
This section describes corrective measures for SNA View malfunctions attributable to mainframe subtask failures. Almost all subtask startup failures are accompanied by one or more messages that are written to the SYSLOG, to the SNA View output job log, or to both. Check the list of SNA View mainframe messages in the section "Mainframe Messages" for courses of action to take when a given error message is displayed.
The following sections describe the appropriate actions to take when a failure of a specific subtask occurs.
A successful LU 6.2 connection requires exact compliance with the setup instructions given in this manual and the CiscoWorks Blue SNA View Workstation Installation Guide. All steps in the connection must be up and available, and all parameters between the mainframe and the workstation must match exactly.
If the LU 6.2 session fails to connect, perform the following steps.
Step 1 Verify that the SYSIN deck has a SERVER card with the following five parameters:
Step 2 Verify that the VTAM APPL resource is defined in SYS1.VTAMLST with the parameter APPC=YES. Verify that the resource is activated under VTAM.
Step 3 Verify that the VTAM LU is defined as an independent LU, either by a LOCADDR=0 definition under its PU, or as a CDRSC in a CDRSC major node definition. Verify that the LU is activated under VTAM.
Step 4 Stop the SNA View address space and check the bottom of the output job log for messages. The most significant messages are the primary and secondary return codes (RCPRI and RCSEC) from the LU 6.2 connection request.
Check the job log for the first occurrence of message NSP111, NSP112, or NSP907. The RCPRI and RCSEC codes are fully documented in the IBM VTAM Programming for LU 6.2 manual.
RCPRI/RCSEC combinations commonly encountered when installing SNA View are listed in Table 4-1.
RCPRI | RCSEC | Meaning and User Action |
---|---|---|
0 hex | 0 hex | Connection completed successfully. No action required. |
0 hex | 1 hex | Connection completed successfully. No action required. |
0 hex | 2 hex | Connection completed successfully. No action required. |
4 hex | 8 hex | The workstation did not recognize the TPN name that was sent from the mainframe. Check for a mismatch in the spelling of the fourth and fifth parameters of the SERVER SYSIN card against the spelling of the TPN profiles on the workstation. |
4 hex | 9 hex | The workstation recognizes the executable name, but cannot start it. Verify that the executable filenames specified in the workstation TPN profiles match the actual executable program names. Recall that the executable names have the domain name appended to them during installation. |
4 hex | A hex | Step 1 Start the svhci_server program manually on the workstation and verify that it starts without error.
Step 2 Check the file permissions on the workstation executable programs. Step 3 If running on an HP workstation, recycle SNA. (The workstation recognizes the TPN executable, but encountered a problem while activating it.) |
8 hex | 0 hex | Step 1 Verify that SNA and the SNA attachment are active on the workstation.
Step 2 If the workstation connection is by Token Ring, verify that the 12-digit MAC address is correctly entered on the workstation and that the NETID matches the NETID in the mainframe data set SYS1.VTAMLST(ATCSTRxx). Step 3 Verify that the LU name in the second parameter of the SERVER SYSIN card matches the available VTAM LU. |
8 hex | 1 hex | Step 1 Verify that the link station is active on the workstation.
Step 2 Verify that the VTAM APPL definition and independent LU (specified in the first and second parameters of the SERVER SYSIN card) are active. |
10 hex | 2 hex | VTAM is attempting to process two requests of the same mode type on the same LU. This is frequently caused by multiple restart attempts within a short period of time. Stop the SERVER subtask, wait 30 seconds, and then restart it. |
14 hex | 0 hex | The transaction program on the workstation terminated abnormally. Wait until all ports on the workstation are cleared. Before retrying the connection, enter the command, ps -ef | grep sv on the workstation to verify that there are no extraneous processes running.
|
2C hex | 1 hex | The logmode name specified in the third parameter of the SERVER SYSIN card was not recognized on the workstation. If an NSP112 message was issued to indicate that the SNASVCMG CNOS succeeded, but the PARALLEL CNOS failed, verify that SNA and the SNA attachment are active on the workstation. |
48 hex | 0 | The LU 6.2 conversation was terminated prematurely. Check to see if either SNA services or SNA server was stopped on the workstation. |
4C hex | 0 | The session used for the LU 6.2 conversation has been terminated, possibly because of a line or modem failure. Check for a break in the physical connection between the workstation and mainframe. |
98 hex | 0 | An overload of commands with large replies is causing a memory shortage while sending data. |
Setting up a TCP/IP connection is less complex than setting up an LU 6.2 connection, but it requires that the mainframe has a TCP/IP package installed. If a TCP/IP stack is not available, you must use the LU 6.2 connection method.
The most common problem with the TCP/IP connection is an inability of the SNA View TCP subtask to communicate with IBM's TCP/IP package. Usually the name of either the TCP/IP address space or the TCP/IP data sets has been changed from the default. When SNA View is unable to find the TCP/IP address space or the TCP/IP profile data sets, it will usually generate the following error message:
NSP150 TCP/IP communications: socket() for workstation message agent failed with errno 39
If this message is displayed during SNA View startup, perform the following steps (not all of these steps may be relevant on your system).
Step 1 If the TCP/IP data sets are not using the default high-level qualifier, make a copy of the hlq.TCPIP.DATA data set and name it TCPIP.TCPIP.DATA.
Step 2 If the TCP/IP address space is not named TCPIP, edit the TCPIP.TCPIP.DATA data set that you just created and verify that the TCPIPJOBNAME or TCPIPUSERID parameter is correctly set to the name of the TCP/IP address space.
Step 3 If the parameter in your TCPIP.TCPIP.DATA data set is TCPIPJOBNAME, change it to TCPIPUSERID. (Older versions of the TCP/IP connection software do not recognize TCPIPJOBNAME.)
Step 4 Specify the TCP/IP prefix as the optional third parameter on the TCP parameter card in NSPPARM. It should be the HLQ for where the TCP data sets are located. For example, if the profile DD statement in the TCP/IP PROC is TCPMVS2.TCPIP1.PROFILE>TCPIP, then the HLQ is TCPMVS2.TCPIP1 and the TCP parameter card would be as follows:
The most common cause for failure of the PPI subtask is that the NetView subsystem interface is not active, which will cause the display of an NSP091 message with an RC=24. The possible values for RC on the NSP091 message are listed in an appendix in the NetView Application Programming Guide.
Also, check the SNA View startup JCL to ensure that the STEPLIB includes the NetView loadlib that contains the CNMCNETV load module.
Additionally, check the SYSLOG during the time of NetView startup and look for messages indicating a failure of the NSPLU62 optional task that must be running in the NetView address space.
The NSPLU62 optional task under NetView should start automatically while NetView is initializing. A successful initialization of the NSPLU62 task will generate both an NSP302 and an NSP311 message. If the NSPLU62 task fails to initialize, additional NSPxxx messages will be displayed during NetView initialization. Check the list of SNA View messages in this chapter to determine why the NSPLU62 task failed to initialize.
If the NetView subsystem interface is not active when NetView starts, the NSPLU62 task will not load and the following message will be issued from NSPLU62 before it terminates:
NSP313 NSPLU62 : NETVIEW INTERFACE FAILURE, RC=0018
To avoid this message when NetView starts (and thus to avoid having to restart the NSPLU62 task manually), start the subsystem interface address space before starting the NetView address space.
If the system has not previously had the subsystem interface running, review the NetView Installation Guide for instructions on subsystem interface setup, paying special attention to the following:
After the problem is corrected, the NSPLU62 task can be restarted from the NetView operator session using the command START TASK=NSPLU62.
This section explains the messages generated by the SNA View mainframe application.
Error Message NSP002
type subtask initialized
Explanation The SNA View subtask has initialized successfully. If the subtask has an associated ACB, the ACB information is given. Task-specific information is also given. Processing continues.
Recommended Action No user action is required.
Error Message NSP008 Invalid input parameter card on line numbernumber is the line number of SYSIN.
Explanation SNA View read a line from SYSIN that it did not understand. The invalid card is skipped. Processing continues with the next SYSIN card.
Recommended Action Correct the input card on the given line number of SYSIN. The "Updating the Mainframe Application Software" chapter provides valid values for task registration cards. Make sure that all other lines must begin with an asterisk (*) to denote that they are comment lines.
Error Message NSP009 Duplicate subtask
card on line number ignored
subtask is the type of subtask.
number is the line number of SYSIN.
Explanation SNA View read a definition card from SYSIN for a subtask name that has already been defined. The invalid card is skipped. Processing continues with the next SYSIN card.
Recommended Action Correct or remove the input card on the given line number of SYSIN. See the "Updating the Mainframe Application Software" chapter for names of input parameter cards that may be defined multiple times.
Error Message NSP010 Maximum number of subtask cards reached; ignoring line numbersubtask is the type of subtask.
number is the line number of SYSIN.
Explanation SNA View has reached the maximum number of subtasks of the type named. The definition card on the named line will not be processed. If subtask=subtask, SNA View has reached the maximum number of total subtasks that can be defined, and all SYSIN parameter cards from that line number forward will be ignored. The parameter card(s) are skipped and processing continues.
Recommended Action Decrease the number of SYSIN parameter cards of the type named.
Error Message NSPV010E NO DATA FOUND MATCHING KEY ENTEREDExplanation Issued in response to the SHOW DLC command. No data was recorded for the requested PU.
Recommended Action None.
Error Message NSPV011E Could not open VSAM file.Explanation Issued in response to the SHOW DLC command, if the VSAM file used to store PU information for SNAView could not be opened.
Recommended Action None.
Error Message NSPV012I pu_name xid local_mac local_sap remote_mac remote_sap rifExplanation Issued in response to the SHOW DLC command. The data recorded for the PU name during XID exchange is displayed.
Recommended Action None.
Error Message NSP018 VTAM ACB generation for subtask acb failed, RC = rcnumbersubtask is the type of subtask.
acb is the name of the failing ACB.
rcnumber is the return code from the Get VTAM ACB routine.
Explanation An attempt by an initializing subtask to get a VTAM ACB failed. The SNA View subtask terminates.
Recommended Action Verify that the acb is active. Use the INIT command to reinitialize the subtask.
Error Message NSP019 VTAM subtask open for acb failed, RC = rcnumber, error = enumbersubtask is the type of the subtask.
acb is the name of the failing ACB.
rcnumber is the return code from the Open VTAM ACB routine.
enumber is the error code within the ACB.
Explanation An attempt by an initializing subtask to open a VTAM ACB failed. The SNA View subtask terminates with a condition code 8.
Recommended Action Verify that the ACB is correctly defined and not already in use. See VTAM Programming manual for descriptions of the return code and error code.
Error Message NSP020subtask is currently in usesubtask is the type of the subtask.
Explanation This message follows immediately after the NSP019 message if an exclusive subtask ACB is already in use by another program. The SNA View subtask terminates.
Recommended Action Verify that the ACB is not being taken by another program on the host, such as NetView or SOLVE: Netmaster.
Error Message NSP021 Unsolicited msgtype data is unavailablemsgtype is the type of message.
Explanation This message follows the NSP019 message to alert the user that SNA View will not be able to receive unsolicited data because it was unable to access an ACB. The SNA View subtask terminates.
Recommended Action No user action is required.
Error Message NSP026 Unexpected subtask return code, RC = rcnumbersubtask is the type of subtask.
rcnumber is the return code from the Receive routine.
Explanation The subtask Receive routine received an unexpected return code while attempting to receive messages. The SNA View subtask terminates.
Recommended Action Use the INIT command to reinitialize the subtask.
Error Message NSP033 SNA View COMMAND = commandtextExplanation The command text issued via SNA View has been logged to SYSLOG. Processing continues.
Recommended Action No user action is required.
Error Message NSP034 Initialization of SPO name failed in reqtype processing, RC1 = addr RC2 = sizename is the name of the SPO subtask.
reqtype is the type of the request being processed.
addr is the returned address from the Get RPL routine.
size is the returned size from the Get RPL routine.
Explanation The SPO subtask failed while calling the VTAM RPL routine. The SNA View SPO subtask terminates.
Recommended Action Use the INIT command to reinitialize the subtask.
Error Message NSP035 SPO Warning: Failure retrieving command responses, max retries reachedExplanation SNA View's SPO interface subtask encountered a failure while attempting to retrieve the command responses from an issued VTAM command. All responses were not retrieved. Processing continues.
Recommended Action Reissue the VTAM command. If the proper responses are still not returned, contact your technical support representative.
Error Message NSP038 VTAM command support unavailableExplanation SNA View could not process the VTAM command because there are no active SPO subtasks. The command is discarded.
Recommended Action Restart SNA View with an SPO card in the SYSIN deck that identifies a valid VTAM APPL resource to be used as an SPO. Verify that the named VTAM resource is active.
Error Message NSP091 PPI initialization failed, step = stepnum RC = rcnumberstepnum is the step of initialization that failed:
rcnumber is the return code from call to CNMNETV.
Explanation An attempt by the PPI subtask to access the CNMNETV module failed. The SNA View PPI subtask terminates.
Recommended Action If stepnum = 1, check the status of the subsystem interface. If stepnum = 3, verify that no other application is attached to the NetView or Netmaster PPI.
Error Message NSP095 SNA View PPI buffer size error, RC = rcnumberrcnumber is the return code from the PPI call.
Explanation A Receive request for the PPI failed due to the length of the buffer size. The SNA View PPI subtask terminates.
Recommended Action Use the INIT command to reinitialize the subtask.
Error Message NSP096 SNA View PPI interface failed, ID = requestid, RC = rcnumberrequestid is the ID of the task request.
rcnumber is the return code from the PPI call.
Explanation A Receive request for the PPI failed. The SNA View PPI subtask terminates.
Recommended Action Consult the NetView Application Programming Guide to determine the meaning of the given return code.
Error Message NSP111 subtask CNOS mode failed, RC = rcnum RCPRI = primaryrc RCSEC = secondaryrcsubtask is the name of the subtask.
mode is the mode name.
rcnum is the return code from the CNOS call.
primaryrc is the primary return code from the CNOS request.
secondaryrc is the secondary return code from the CNOS request.
Explanation The LU 6.2 CNOS command for mode mode failed during the initialization of subtask subtask. The SNA View subtask terminates.
Recommended Action Consult VTAM Programming for LU 6.2 for a translation of the RCPRI and RCSEC return codes.
subtask is the name of the subtask.
mode is the mode name.
status is the status of the task; it is either "succeeded" or "failed."
primaryrc is the primary return code from the CNOS request.
secondaryrc is the secondary return code from the CNOS request.
Explanation The LU 6.2 CNOS command for mode mode completed for subtask subtask. Processing continues.
Recommended Action If status is "failed," stop SNA View and check the output job log for more information. Consult VTAM Programming for LU 6.2 for a translation of the RCPRI and RCSEC return codes.
Error Message NSP113 Unable to establish msgtype LU 6.2 communication with the workstation wsagent agent, RC = rcnumbermsgtype is the type of LU 6.2 message:
is the workstation agent:
rcnumber is the return code from the LU 6.2 call.
Explanation Establishment of LU 6.2 session(s) between the mainframe and the workstation failed. The SNA View SERVER subtask terminates.
Recommended Action Verify that the parameters of the SERVER SYSIN card match the VTAM resource names defined for SNA View and also match the resource names entered in the workstation communications setup.
Error Message NSP114 Error in LU 6.2 direction workstation wsserver server, RC = rcnumberdirection is the direction of the message:
wsserver is the workstation server:
rcnumber is the return code from LU 6.2 call.
Explanation An error occurred in the sending or receiving of an LU 6.2 message between the mainframe and the workstation. The SNA View SERVER subtask terminates.
Recommended Action Verify the status of the LU 6.2 session(s) between the mainframe and the workstation.
Error Message NSP115 Dumping subtask direction action ctrlblksubtask is the subtask name.
direction is the direction of message:
action is the attempted action:
ctrlblk is the control block being dumped:
Explanation SNA View subtask encountered an error in LU 6.2 communications to the workstation. Following this message, a dump of the control block ctrlblk will be given to aid in problem determination. The SNA View SERVER subtask terminates.
Recommended Action Consult the VTAM Programming manual for a mapping of the control block. Correct the error and use the INIT command to reinitialize the subtask.
Error Message NSP119 num messages queued on subtask. Command rejected: commandnum is the number of messages.
subtask is the subtask name.
command is the command entered.
Explanation Subtask subtask will not process the command issued from the workstation because there is a backlog of num messages that are waiting to be sent to the workstation. The command command is discarded. Processing continues on the remaining messages in the subtask's queue.
Recommended Action Wait until the existing backlog of messages has been processed and then reissue the command. Use the SHOW TASK command to view the number of messages in the output queue of the subtask.
Error Message NSP121 MVS console name could not obtain a migration IDname is the name of the console to be defined.
Explanation The MVS console being defined requested a one-byte migration ID, but the console initialization routine was unable to provide one. Initialization of the console continues.
Recommended Action No user action is required.
Error Message NSP122 MVS console name initialization failed, RC = rcnumbername is the name of the console to be defined.
rcnumber is the return code from the initialization routine.
Explanation The initialization of the MVS console failed. The SNA View MVS subtask terminates.
Recommended Action Record the return code and report it to your support representative.
Error Message NSP150 TCP/IP communications: function for workstation component agent failed with errno valuefunction is the failing communication function.
component is the workstation component that detected the failure.
value is the integer error value.
Explanation A TCP/IP communication error has occurred. The error could have taken place during TCP/IP communication establishment or during a send or receive between the mainframe and the agent specified. The SNA View TCP subtask terminates.
Recommended Action Verify the availability of TCP/IP communication between the workstation and the mainframe. Use the INIT command to reinitialize the subtask.
Error Message NSP151 SNA View failure in communication to TCP/IPExplanation SNA View received an error while attempting to receive data from a TCP/IP socket or ECB. The TCP/IP subtask terminates.
Recommended Action Use the INIT command to reinitialize the subtask.
Error Message NSP160 Console command return code = rcnumberrcnumber is the return code from command send subroutine.
Explanation An MVS command request completed with a non-zero return code. Processing continues.
Recommended Action If an expected command response is not received, record the return code and contact your support representative.
Error Message NSP205 MVS console name reached memory limit. Data lostExplanation The extended console defined for SNA View has filled all of the available cells in the data space. The incoming message is not queued. Processing continues.
Recommended Action Check the status of the extended console with a DISPLAY CONSOLES, CN=name. If messages do not resume queuing to the extended console, recycle SNA View, making sure that the console comes down cleanly. A new console may need to be defined with a larger message data space.
Error Message NSP206 MVS console name reached queue limit. Data lostname is the console name.
Explanation The extended console defined for SNA View has reached its maximum queue depth. The incoming message will not be queued. Processing continues.
Recommended Action Check the status of the extended console with a DISPLAY CONSOLES, CN=name. If messages do not resume queuing to the extended console, recycle SNA View, making sure that the console comes down cleanly.
Error Message NSP207 MVS console name stopped by internal errorname is the name of the console.
Explanation The extended console defined for SNA View received an error during the processing of its message queues. SNA View deactivates the MVS console.
Recommended Action Check the status of the extended console with a DISPLAY CONSOLES, CN=name. Recycle SNA View.
Error Message NSP208 MVS console name reached alert percentagename is the console name.
Explanation The number of messages queued to the extended console for SNA View has reached a certain percentage of the maximum queue depth. Processing continues.
Recommended Action Verify that messages are being displayed on the MVS messages client on the workstation. Check the status of the extended console with the command DISPLAY CONSOLES, CN=name. If the queue shortage is not relieved shortly, recycle SNA View, ensuring that the console comes down cleanly.
Error Message NSP209 MVS console name suspended by requestname is the console name.
Explanation A condition has developed in the extended console defined for SNA View such that MVS has requested the deactivation of the console. SNA View deactivates the console.
Recommended Action Check the condition of the console with the command DISPLAY CONSOLES, CN=name. Recycle SNA View.
Error Message NSP210 MVS console name alert ECB posted for unknown reasonname is the console name.
Explanation The extended console defined for SNA View was posted with an alert indicating a problem, but no error flags were set in the console's status area. Processing continues.
Recommended Action Check the condition of the console with the command DISPLAY CONSOLES, CN=name.
Error Message NSP302 name: SNA View PPI TASK INITIALIZEDname is the name of the NetView PPI subtask.
Explanation The program-to-program interface subtask for SNA View was successfully initialized in the NetView address space. Processing continues.
Recommended Action No user action is required.
Error Message NSP303 name: SNA View PPI TASK TERMINATEDname is the name of the NetView PPI subtask.
Explanation The program-to-program interface task for SNA View has been terminated in the NetView address space. Processing continues, but SNA View will no longer receive unsolicited VTAM messages and alerts from NetView.
Recommended Action If NetView has terminated, restart NetView. If only the PPI subtask has terminated, restart the subtask from a NetView operator session with this command: START TASK=name
Error Message NSP304 name: DSIFRE FAILED FOR USER STORAGEname is the name of the NetView PPI subtask.
Explanation The SNA View PPI subtask received an error return code from NetView macro DSIFRE while attempting to free the 4K work area of memory during subtask shutdown. Subtask shutdown processing continues.
Recommended Action Notify the system programmer that a potential memory leak exists in the currently running NetView.
Error Message NSP305 name: DSIFRE FAILED FOR QUEUED STORAGEname is the name of the NetView PPI subtask.
Explanation The SNA View PPI subtask received an error return code from the NetView macro DSIFRE while attempting to free all remaining subtask memory during subtask shutdown. Subtask shutdown processing continues.
Recommended Action Notify the system programmer that a potential memory leak exists in the currently running NetView.
Error Message NSP306 name: DSIFRE FAILED FOR MQS BUFFERname is the name of the NetView PPI subtask.
Explanation The SNA View PPI subtask received an error return code from the NetView macro DSIFRE while attempting to free the memory allocated for the private message queue. Processing continues.
Recommended Action Notify the system programmer that a potential memory leak exists in the currently running NetView.
Error Message NSP307 name: DSIGET FAILED FOR USER STORAGEname is the name of the NetView PPI subtask.
Explanation The SNA View PPI subtask failed to get a 4K block of memory for use during processing. The task termination flag is set.
Recommended Action Notify the system programmer that a potential memory shortage exists in the currently running NetView. The region size of the NetView address space may need to be increased.
Error Message NSP308 name: ENQ ERRORname is the name of the NetView PPI subtask.
Explanation An ENQ on the NetView's TVB chain failed. If not already in termination processing, the task termination flag is set.
Recommended Action Notify the system programmer. Restart the PPI subtask.
Error Message NSP309 name: DEQ ERRORname is the name of the NetView PPI subtask.
Explanation A DEQ on the NetView's TVB chain failed. If not already in termination processing, the task termination flag is set.
Recommended Action Notify the system programmer. Restart the PPI subtask.
Error Message NSP310 name: TASK ALREADY EXISTSname is the name of the NetView PPI subtask.
Explanation The SNA View PPI subtask attempted to add itself to the NetView TVB chain, but found another task with the same name already on the chain. The task termination flag is set.
Recommended Action Verify that another instance of the subtask is not already running under this NetView. Restart the PPI subtask.
Error Message NSP311 name: LOAD OF CNMNETV COMPLETEname is the name of the NetView PPI subtask.
Explanation The loading of module CNMNETV into virtual storage completed successfully. Processing continues.
Recommended Action No user action is required.
Error Message NSP312 name: UNABLE TO LOAD CNMNETVname is the name of the NetView PPI subtask.
Explanation The loading of module CNMNETV into virtual storage failed. The subtask terminates.
Recommended Action Verify that load module CNMNETV exists in a NetView STEPLIB data set. Restart the PPI subtask.
Error Message NSP313 name: NETVIEW INTERFACE FAILURE, RC = rcnumbername is the name of the NetView PPI subtask.
rcnumber is the hexadecimal return code from CNMNETV call.
Explanation A call to the CNMNETV interface routine failed. The message is discarded.
Recommended Action Consult the NetView Application Programming Guide to determine the meaning of the given return code.
Error Message NSP314 name: NETVIEW COMMAND RECEIVEDname is the name of the NetView PPI subtask.
Explanation A message was successfully received from the PPI interface routine. Processing continues.
Recommended Action No user action is required. This message appears for debugging purposes, and only if the subtask has been reassembled with the CMDREC lines uncommented.
Error Message NSP315 autotask COMMAND EXECUTION FAILED, CORR = commcorrautotask is the name of the NetView autotask that executes the command.
commcorr is the command correlator.
Explanation A failure occurred in a command that was to be executed under NetView on behalf of SNA View. The command is discarded.
Recommended Action Verify that the autotask defined under NetView during SNA View installation is active. Verify that the NTICMD and NTIMVS command lists are present in a NetView DSICLD data set. Verify that the name in the NSPCMD_OPERATOR field on the workstation (which you specified while running the svXconfig program) matches the autotask name defined under NetView.
Error Message NSP595 Command entered:cmdtxtcmdtxt is the text of the command entered.
Explanation SNA View received a command from a console. Processing continues with the execution of the command.
Recommended Action No user action is required.
Error Message NSP600 TNUM TASKNAME STATUS RESTARTS/LIMIT SPECIFICExplanation Issued in response to the SHOW TASKs command. An entry will be displayed for each subtask along with its status, the number of times it has been restarted, and task specific information.
Recommended Action None.
Error Message NSP603 TNUM TASKNAME ADDRESS HEADER TCBExplanation Issued in response to the SHOW ADDR command. An entry will be displayed for each subtask along with its address, task header address and TCB address.
Recommended Action None.
Error Message NSP605 TNUM TASKNAME INPUTQ OUTPUTQ INFLOW OUTFLOW MCExplanation Issued in response to the SHOW FLOW command. An entry will be displayed for each subtask, along with the size of its I/O queues, the number of messages that have passed through, and the number of message buffers currently allocated to the task.
Recommended Action None.
Error Message NSP607 CiscoWorks Blue SNAView $version$ Copyright $copyright$ Cisco Systems $version$ is the version of the installed product $copyright$ is the copyright for the installed productExplanation Issued in response to the SHOW VERsion command.
Recommended Action None.
Error Message NSP608 TASKNAME DATE TIMEExplanation Issued in response to the SHOW VERsion command. For each subtask the load module compile date and time is listed.
Recommended Action None.
Error Message NSP609 $filters$ $filters$ is the list of currently set message filtersExplanation Issued in response to the SHOW FILTER command.
Recommended Action None.
Error Message NSP610 Message filter $filter$ $action$ $filter$ is the message filter $action$ is 'added' or 'deleted'Explanation Issued in response to the FILTER <ADD|DEL> command.
Recommended Action None.
Error Message NSP611 Message filter $filter$ not found$filter$ is the message filter
Explanation Issued in response to the FILTER DEL command.
Recommended Action Check the filter and try again. Issue the SHOW FILTER command to see the current filters.
Error Message NSP612 No filters definedExplanation Issued in response to the SHOW FILTER command when no filters are currently defined.
Recommended Action None.
Error Message NSP690 SNAView STOP Command acceptedExplanation Issued in response to the STOP command. SNAView will terminate.
Recommended Action None.
Error Message NSP695 SNA View cmdtype command processed.cmdtype is the command type.
Explanation SNA View completed the initial processing of a console command. Additional messages may be forthcoming, depending on whether any additional work is to be done by the subtask(s).
Recommended Action No user action is required.
Error Message NSP698 Subtask task is already statustask is the subtask name.
status is the subtask status.
Explanation A subtask modification command was invalid because of the current state of the target subtask. Processing continues.
Recommended Action Use the SHOW TASK command to check the subtask's status.
Error Message NSP699 Invalid operator command enteredExplanation A command was entered to SNAView that was not valid.
Recommended Action Check the command, and try again. Try the HELP command to see a list of valid SNAView commands.
Error Message NSP701 Starting subtask #idnum for infoidnum is the numerical ID for the newly started subtask.
info is the information sent to the ATTACH macro.
Explanation SNA View attached a subtask with the information given in info. Processing continues with the ATTACH attempt.
Recommended Action No user action is required.
Error Message NSP702 Buffer size = sizeM, Queue depth = totalmsg, Maximum = maxmsgsize is the size (in megabytes) allocated for messages.
totalmsg is the total message queue depth.
maxmsg is the maximum message queue depth permitted.
Explanation A message queuing problem has occurred for an MCS console defined for SNA View. This message appears only in the SNA View job log and is immediately followed by a message that gives more detailed information. Processing continues. The MCS console may be terminated, depending on the severity of the queueing problem.
Recommended Action Monitor the SNA View job log for the next message.
Error Message NSP705 TNUM TASKNAME FREE USEDExplanation Issued in response to the SHOW FREEQ command. SNAView will list the number of slots free and used on each task's free queue.
Recommended Action None.
Error Message NSP706 TNUM TASKNAME SPECIFIC CLIENTExplanation Issued in response to the SHOW CONNections command. SNAView will display the hostname (or tcp/ip address) of the workstation connected to each TCP/IP subtask, or "NO CONNECTION" if no workstation is connected.
Recommended Action None.
Error Message NSP901 Stopping subtask #number: namenumber is the subtask number.
name is the subtask name.
Explanation This message is issued in response to a STOP command. One message is issued for each SNA View subtask. A termination command is sent to each named subtask.
Recommended Action No user action is required.
Error Message NSP902 name subtask terminated, RC = rcnumbername is the name of subtask.
rcnumber is the return code from the termination call.
Explanation The named subtask has been terminated. Any queues or memory allocated for the subtask are freed.
Recommended Action No user action is required.
Error Message NSP903 name in/
out queue freed, RC = rcnumber
name is the name of the subtask.
in/out is input or output.
rcnumber is the return code from the Free call.
Explanation An allocated message queue for the named subtask has been freed. Processing continues.
Recommended Action No user action is required.
Error Message NSP904 All SNA View subtasks completedExplanation SNA View has completed the shutdown of all subtasks. Processing continues with the shutdown of the main task.
Recommended Action No user action is required.
Error Message NSP905 Restart #attempt of subtask task will be attempted in time secondsattempt is the number of times the subtask has been restarted.
task is the subtask name.
time is the number of seconds until the next restart attempt is made.
Explanation The named subtask has terminated and will attempt to restart itself automatically in the stated number of seconds. The subtask sleeps for the specified number of seconds before attempting to restart itself.
Recommended Action None. The INIT command can be used during the delay to bypass the delay and do an immediate restart of the subtask. The KILL command can be used to bring down the subtask and cancel any further automatic restart attempts.
Error Message NSP906 No auto restart for task. Use INIT command to restart.task is the subtask name.
Explanation The named subtask has terminated and will not attempt to restart itself because either the operator explicitly issued a KILL command against the subtask, or the maximum number of restart attempts has been exceeded for the subtask. The INIT command may be used to reinitialize the subtask and reset the number of restart attempts. The subtask is terminated.
Recommended Action None.
Error Message NSP907 LU6.2 return codes RCPRI = x, RCSEC = xExplanation Issued for LU 6.2 error conditions, listing the primary and secondary return codes.
Recommended Action Record the return codes for problem determination.
|