|
|
Use this chapter to identify and resolve problems with the SNA View mainframe application. When you encounter an unfamiliar message or problem, read this chapter before you take any further action.
This chapter contains two major sections:
This section describes corrective measures for SNA View 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 Error Messages" for a course 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 book and the CiscoWorks Blue SNA View Workstation Installation and User Guide. All network connections must be up and available, and all parameters used by both the mainframe and the workstation must match exactly.
If the LU 6.2 session fails to connect, perform the steps shown below.
Step 1 Verify that the SYSIN deck has a SERVER parameter card with the following five parameters:
Step 2 Verify that the VTAM APPL resource is defined in SYS1.VTAMLST with the parameter APPC=YES and 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 Use the VTAM APING command to verify that the SNA View workstation is reachable from the mainframe.
Where the netid.resource should be the fully qualified name of the SNA View workstation. Until this returns a positive response, SNA View will not be able to connect to the workstation.
Step 5 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.
Step 6 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 publication VTAM Programming for LU 6.2.
RCPRI/RCSEC combinations commonly encountered when installing SNA View are listed in Table 6-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 transaction program 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 transaction program name profiles on the workstation. |
| 4 hex | 9 hex | The workstation recognizes the executable name but cannot start it. Verify that the executable file names specified in the workstation transaction program name 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, restart SNA. (The workstation recognizes the transaction program name as 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 network identifier (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 ps -ef | grep sv command on the UNIX 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 you receive an NSP112 message 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 Communications Server for AIX 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 the 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 an LU 6.2 connection instead.
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 (see Step 1) 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 Ensure that the TCPIP prefix is set correctly in the NSPOPEN procedure (located in NSP.NSPS120I.NSPSSAMP). Change the characters TCPHLL in PARM='=TCPIP_PREFIX=TCPHLL' to your installation-defined high-level qualifier for TCP/IP. For example, if the profile DD statement in the TCP/IP PROC is TCPMVS2.TCPIP1.PROFILE.TCPIP, then the high-level qualifier is TCPMVS2.TCPIP1, and the PARM would be specified as this:
The most common cause for failure of the PPI subtask is that the NetView subsystem interface is not active. This results in the display of an NSP091 message with a return code from NetView. The possible return code values for the NSP091 message are listed in an appendix in the NetView Application Programming Guide. For information about the NSP091 message, see "Mainframe Error Messages" later in this chapter.
Check the SNA View startup JCL to ensure that the STEPLIB includes the NetView load library (loadlib) that contains the CNMCNETV load module.
Also, check the SYSLOG during 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 generates both an NSP302 and an NSP311 message. If the NSPLU62 task fails to initialize, additional NSPxxx messages are 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 problem 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, you can restart the NSPLU62 task from the NetView operator session using the command START TASK=NSPLU62.
The Status/Discovery process at the workstation receives updated PU information from the mainframe when a status change occurs or when a new PU is discovered. If status updates are not being received at the SNA View workstation, you should determine whether the message is flowing from VTAM to SNA View on the mainframe. You can use the following methods to help diagnose the problem.
You can use some of the SNA View commands described in "Issuing SNA View Commands" in the "Using the SNA View Mainframe Application" chapter, to help debug the SNA View task.
The SHOW ADDR command displays important subtask information that might be required by the Cisco TAC.
The SHOW FLOW command displays several key fields for troubleshooting, as shown in Table 6-2.
| Field | Purpose |
|---|---|
| TASKNAME | Identifies the subtask by subtask name. |
| INPUTQ | This is the number of message buffers queued to the main SNA View task by this subtask. If this number grows rapidly and continues to stay high, there could be a problem with the subtask or the main task. |
| OUTPUTQ | This is the number of message buffers queued to this subtask for processing. If this number grows rapidly and continues to stay high, there could be a problem with the subtask. |
| MC | Message count; number of message buffers allocated to this subtask. If this number grows rapidly and continues to stay high, there could be a problem with the subtask. |
The SHOW FREEQ command displays the number of elements in the queue for each subtask. Look at the number in the FREE column. If the number in the FREE column goes to 0, there is a problem with the subtask.
Use the F NSPOPEN,SHOW TASK command to ensure that the PPI or PPO subtask and the STATUS subtask are active.
This section provides information about the error messages generated by the SNA View mainframe application.
Error Message NSP002 type SUBTASK INITIALIZED
type is the subtask type.
Explanation The SNA View subtask has successfully initialized. If the subtask has an associated VTAM access method control block (ACB), the ACB information is given. Task-specific information is also given. Processing continues.
Recommended Action No user action is required.
Error Message NSP005 COULD NOT OPEN VSAM FILE WITH DDNAME DDNAME.DDNAME is the name of the VSAM file used to store PU data; it is either XIDDATA or XIDBACK.
Explanation You issued a SHOW DLC command, but the VSAM file named DDNAME, used to store PU information for SNA View (either XIDDATA or XIDBACK), could not be opened.
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 an invalid card from SYSIN. 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. Ensure that all other lines begin with an asterisk (*), which indicates that they are comment lines.
Error Message NSP009 DUPLICATE subtask CARD ON LINE number IGNORED
subtask is the type of the 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 duplicate card is skipped. Processing continues with the next SYSIN card.
Recommended Action Correct or remove the duplicate 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 the subtask: SERVER, SPO, TCP, or SUBTASK.
number is the line number of SYSIN.
Explanation SNA View has reached the maximum number of subtasks of the type named in the subtask field. The definition card on the line specified by the number field will not be processed.
The subtask field identifies the type of subtask whose maximum has been reached: SERVER, SPO, or TCP. If the subtask field contains the word "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 ignored parameter cards are skipped. Processing continues.
Recommended Action Decrease the number of SYSIN parameter cards of the type named.
Error Message NSP017 NO DATA FOUND MATCHING REQUESTED KEYExplanation You issued a SHOW DLC command, but no data was available for the requested PU name.
Recommended Action No user action is required.
Error Message NSP018 VTAM ACB GENERATION FOR subtask acb FAILED, RC = rcnumbersubtask is the type of the subtask.
acb is the name of the failing ACB.
rcnumber is the return code from the Get VTAM ACB routine.
Explanation An initializing subtask attempted to get a VTAM ACB and failed. The SNA View subtask terminates.
Recommended Action Verify that the ACB named in acb is active. Use the SNA View 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 initializing subtask attempted to open a VTAM ACB and failed. The SNA View subtask terminates.
Recommended Action Verify that the ACB is correctly defined and not already in use. See the IBM VTAM Programming manual for descriptions of the return code and error code.
Error Message NSP020 subtask 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 the message.
Explanation This message follows the NSP019 message to alert you 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 the 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 = commandtextcommandtext is an SNA View command.
Explanation 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 secondary program operator (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 Get 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 secondary program operator (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 the Cisco TAC.
Error Message NSP038 VTAM COMMAND SUPPORT UNAVAILABLEExplanation SNA View could not process the VTAM command because there are no active secondary program operator (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 NSP039 NODE node_name REMAINS IN PENDING STATEnode_name is the node name of a PU.
Explanation SNA View detected a PU (node_name) in the pending state after VTAM message IST590I indicated that the connection was established. SNA View then tried to display the PU within the time defined by the delay_time option of the STATUS parameter card, but failed.
Recommended Action Increase the value of the delay_time option on the STATUS parameter card.
Error Message NSP091 PPI INITIALIZATION FAILED, STEP = stepnum RC = rcnumberstepnum is the step of initialization that failed:
1 indicates that a subsystem interface is not active.
2 indicates that an attempt to get an address space control block (ASCB) value failed.
3 indicates that an attempt to register as a receiver failed.
rcnumber is the return code from call to NetView (CNMNETV).
Explanation An attempt by the primary program operator subtask to access the CNMNETV module failed. The SNA View PPI subtask terminates.
Recommended Action Table 6-3 shows you what to do depending on the value of stepnum.
| stepnum | Action |
|---|---|
| 1 | Check the status of the subsystem interface. |
| 2 | Check the status of the NetView or SOLVE:Netmaster program-to-program interface. If it is inactive, activate it and restart the SNA View PPI subtask. |
| 3 | Verify that no other application is attached to the NetView or SOLVE:Netmaster program-to-program interface. |
rcnumber is the return code from the PPI call.
Explanation A Receive request for the program-to-program interface (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 program-to-program interface (PPI) failed. The SNA View PPI subtask terminates.
Recommended Action See 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 (SNASVCMG or PARALLEL).
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 failed during the initialization of the subtask.. The SNA View subtask terminates.
Recommended Action See the publication VTAM Programming for LU 6.2 for the meaning of the RCPRI and RCSEC return codes.
subtask is the name of the subtask.
mode is the mode name (SNASVCMG or PARALLEL).
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 completed for subtask. Processing continues.
Recommended Action If status is "failed," stop SNA View and check the output job log for more information. See the publication 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. The following types are possible:
| outbound | Allocation from the mainframe to the workstation |
| inbound | Allocation from the workstation to the mainframe |
| send | Message transmission from the mainframe to the workstation |
| receive | Message transmission from the workstation to the mainframe |
wsagent is the workstation agent. These agents are possible:
| command | Workstation command agent |
| message | Workstation message agent |
rcnumber is the return code from the LU 6.2 call.
Explanation Establishment of LU 6.2 sessions 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,direction is the direction of the message. These directions are possible:
| Send to | From the mainframe to the workstation |
| Receive from | From the workstation to the mainframe |
wsserver is the workstation server. These servers are possible:
| command | Host command server |
| HCI | Host connection interface |
rcnumber is the return code from the 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 the message. These directions are possible:
| outbound | From the mainframe to the workstation |
| inbound | From the workstation to the mainframe |
action is the attempted action. These actions are possible:
| allocate | Allocation of an LU 6.2 conversation |
| receive | Sending a message over an established conversation |
ctrlblk is the control block being dumped. These control blocks are possible:
| RPL | VTAM Request Parameter List |
| RPL6X | VTAM Request Parameter List Extension |
Explanation SNA View subtask encountered an error in LU 6.2 communications to the workstation. Following this message, a dump of the control block specified by ctrlblk will be given to aid in problem determination. The SNA View SERVER subtask terminates.
Recommended Action See 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 The subtask will not process the command that was issued from the workstation because there is a backlog of num messages to be sent to the workstation. The 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 subtask's output queue.
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 1-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 the Cisco TAC.
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 event control block (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 the Send command 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 LOSTname is the console name.
Explanation 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 the following command:
DISPLAY CONSOLES, CN=name
If messages do not resume queuing to the extended console, restart SNA View to ensure that the console comes down cleanly. You might need to define a new console 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 the following command:
DISPLAY CONSOLES, CN=name
If messages do not resume queuing to the extended console, restart SNA View, making sure that the console comes down cleanly.
Error Message NSP207 MVS CONSOLE name STOPPED BY INTERNAL ERRORname is the console name.
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 status of extended console with the following command:
DISPLAY CONSOLES, CN=name
Restart 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 status of extended console with the following command:
DISPLAY CONSOLES, CN=name
If the queue shortage is not relieved shortly, stop and restart the SNA View mainframe PROC.
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 status of the extended console with the following command:
DISPLAY CONSOLES, CN=name
Restart 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 status of the extended console with the following command:
DISPLAY CONSOLES, CN=name
Error Message
NSP302 name: SNA VIEW PPI TASK INITIALIZED
name is the name of the NetView program-to-program interface (PPI) subtask.
Explanation The PPI 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 program-to-program interface (PPI) subtask.
Explanation The PPI task for SNA View has been terminated in the NetView address space. Processing continues, but SNA View will no longer receive unsolicited VTAM messages or 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 STORAGE
name is the name of the NetView program-to-program interface (PPI) subtask.
Explanation The SNA View PPI subtask received an error return code from the NetView DSIFRE macro 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 program-to-program interface (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 program-to-program interface (PPI) subtask.
Explanation The SNA View PPI subtask received an error return code from the NetView DSIFRE macro 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 program-to-program interface (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. You might need to increase the region size of the NetView address space.
Error Message NSP308 name: ENQ ERRORname is the name of the NetView program-to-program interface (PPI) subtask.
Explanation An enqueue request (ENQ) on the NetView's task vector block (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 program-to-program interface (PPI) subtask.
Explanation A dequeue request (DEQ) on the NetView's task vector block (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 program-to-program interface (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 program-to-program interface (PPI) subtask.
Explanation The loading of the CNMNETV module 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 program-to-program interface (PPI) subtask.
Explanation The loading of the CNMNETV module 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 program-to-program interface (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 See 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 program-to-program interface (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 you reassembled the subtask with the CMDREC lines uncommented.
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 TASK 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 No user action is required.
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 No user action is required.
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 No user action is required.
Error Message NSP607 CiscoWorks Blue SNAView version Copyright copyright Cisco Systemsversion is the version number of the installed SNA View.
copyright lists the copyright years for the installed SNA View.
Explanation Issued in response to the SHOW VERSION command to specify the version of the SNA View workstation program.
Recommended Action No user action is required.
Error Message NSP608 TASKNAME DATE TIMEExplanation Header line issued in response to the SHOW VERSION command. The date and time of the load-module compilation are listed below this line for each subtask.
Recommended Action No user action is required.
Error Message NSP609 filter1 [filter2 ... filtern]filter1 [filter2 ... filtern] is the list of message filters that are currently set.
Explanation Displays the output of the SHOW FILTER command.
Recommended Action No user action is required.
Error Message NSP610 Message filter filter actionfilter is the message ID to be added to or deleted from the message filter.
action indicates whether the message ID is "added" or "deleted" in the message filter.
Explanation Displays the output of the FILTER ADD or FILTER DEL command.
Recommended Action No user action is required.
Error Message NSP611 Message filter filter not foundfilter is the message filter.
Explanation Displays the output of 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 Displays the output of the SHOW FILTER command when no filters are currently defined.
Recommended Action No user action is required.
Error Message NSP625 Invalid MESSAGE value: message_value specified.message_value is the invalid parameter you included on the MESSAGES parameter card or command.
Explanation You entered an invalid parameter on a MESSAGES parameter card in the NSPPARM data set or on a MESSAGES command. The valid parameter values for MESSAGES are ON, OFF, MVS, and VTAM.
Recommended Action Change the MESSAGES parameter card in the NSPPARM file or reenter the MESSAGES command with a valid parameter.
Error Message NSP690 SNAView STOP Command acceptedExplanation Displays the output of the STOP command. SNA View terminates.
Recommended Action No user action is required.
Error Message NSP695 SNA View cmdtype command processed.cmdtype is the SNA View command just processed.
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 subtasks.
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 You entered an invalid SNA View command.
Recommended Action Check the command and try again. Use the HELP command to see a list of valid SNA View 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 = maxmsgsizeM 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 USEDTNUM is the task number for the subtask.
TASKNAME is the task name for the subtask.
FREE is the number of free slots in the queue.
USED is the number of used slots in the queue.
Explanation Displays the output of the SHOW FREEQ command. SNA View lists the number of free and used slots on each task's queue.
Recommended Action No user action is required.
Error Message NSP706 TNUM TASKNAME SPECIFIC CLIENTTNUM is the task number for the subtask.
TASKNAME is the task name for the subtask.
SPECIFIC is information specific to the subtask.
CLIENT identifies the workstation connected to the subtask.
Explanation Displays the output of the SHOW CONN command. SNA View displays the host name or TCP/IP address of the workstation connected to each TCP/IP subtask. If no workstation is connected, "NO CONNECTION" is displayed.
Recommended Action No user action is required.
Error Message NSP708 pu_name xid local_mac local_sap remote_mac remote_sap rifpu_name is the PU name.
xid is the exchange identifier.
local_mac is the MAC address for the local node.
local_sap is the SAP for the local node.
remote_mac is the MAC address for the remote node.
remote_sap is the SAP for the local remote.
rif is the Routing Information Field.
Explanation Displays the output of the SHOW DLC command. The data recorded for the PU name during the exchange of XIDs is displayed.
Recommended Action No user action is required.
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 the 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 = rcnumbername 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 No user action is required. 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 No user action is required.
Error Message NSP907 LU6.2 return codes RCPRI = x, RCSEC = yExplanation Issued for LU 6.2 error conditions, listing the primary and secondary return codes.
Recommended Action Record the return codes for problem determination.
Error Message NSP2000I DATA RECORDED TO dbtype FOR PU punamedbtype is the identifier for the database to which the PU data was recorded. Values for this variable are PRIMARY and BACKUP.
puname is the PU name for which data was recorded.
Explanation Data for the PU identified by puname was successfully recorded in the database identified by dbtype.
Recommended Action No action is required.
Error Message NSP2003E dbtype XID OUTPUT DATA SET UNAVAILABLE.dbtype is the identifier for the database that did not open. Values for this variable are PRIMARY and BACKUP.
Explanation OPEN failed for the database identified by dbtype.
In the event that switching is necessary and no BACKUP is available, all vector processing is suppressed. In either case, loss of data is probable.
Recommended Action Failure to open the PRIMARY database must be corrected immediately for the data recording function to initialize. Failure to open the BACKUP is less severe and can be deferred, with the possible consequence that data may eventually be lost if switching is ever required. Usually a failure to open is caused by a configuration problem rather than a component failure. Check the allocation for the identified database to ensure that it is allocated correctly. Databases are identified in the VTAM startup procedure. The PRIMARY database is identified by the XIDDATA DD statement; the BACKUP database is identified by the XIDBACK DD statement. Verify that the DSNAMES (DSN keyword) identify the correct data sets.
Error Message NSP2005E WRONG VECTOR PASSED.Explanation An internal failure in the SNA View Exit Manager caused an invalid vector to be passed to the XID data recording function. Though no damage is reported by this message, it can be caused by storage overlays.
Recommended Action Use the following command sequence to reinitialize the exit routine.
F NET,EXIT,ID=ISTEXCCS,OPT=INACT
F NET,EXIT,ID=ISTEXCCS,OPT=ACT,MODULE=exitname
Where exitname is the name given to the NSP Exit Manager load module. If the problem recurs, notify the Cisco TAC.
Error Message NSP2006E PUT NOT SUCCESSFUL R15 = r15value RC = rcvaluer15value is the decimal value of the return code resulting from the VSAM PUT.
rcvalue is the decimal value of the FDBK field associated with the above return code.
Explanation An attempt to write a data record to a database has failed. If recording to the PRIMARY database is active, the SNA View Data Recording Function attempts to switch to the BACKUP database. This message can also mean that the VSAM databases are too small for tracking the network. In this case, reallocate the databases. A sample job stream for database allocation can be found in prefix.NSPS120I.NSPSSAMP in member NSPDBVSM.
Recommended Action If the databases are too small, reallocate them and increase their size. Otherwise, verify the integrity of the VSAM databases. Databases are identified in the VTAM startup procedure. The PRIMARY database is identified by the XIDDATA DD statement; the BACKUP database is identified by the XIDBACK DD statement.
Error Message NSP2007E NO DATASET AVAILABLE FOR OUTPUT.Explanation One of the following occurred:
Recommended Action Failure to open the PRIMARY database must be corrected immediately for the data recording function to initialize. Failure to open the BACKUP database is less severe and can be deferred, with the possible consequence that data may eventually be lost if switching is ever required.
Database switching should not occur. It usually occurs because the database is too small for the network being tracked. Increase the amount of space allocated to the PRIMARY and BACKUP databases. A sample job stream to allocate databases is included in prefix.NSPS120I.NSPSSAMP in member NSPDBVSM. Change the allocation parameters to those appropriate for your network.
Error Message NSP2008E DID NOT PUT DB KEY R15 = r15value RC = rcvaluer15value is the decimal value of the return code resulting from the VSAM PUT.
rcvalue is the decimal value of the FDBK field associated with the above return code.
Explanation An attempt to write a VSAM key to a database failed.
Recommended Action Verify the integrity of the VSAM databases. Databases are identified in the VTAM startup procedure. The PRIMARY database is identified by the XIDDATA DD statement, and the BACKUP database is identified by the XIDBACK DD statement.
Error Message NSP2009E MODCB OF RECLEN FAILED FOR NEW RECORDExplanation An attempt to set the record length (RECLEN) value for a new database record failed.
Recommended Action Notify the Cisco TAC.
Error Message NSP2010E MODCB OF RECLEN FAILED FOR UPDATEExplanation An attempt to set the RECLEN value for update of an existing database record failed.
Recommended Action Notify the Cisco TAC.
Error Message NSP2011E MODCB OF PUT RPL TO BACKUP FAILEDExplanation The attempted switch from PRIMARY to BACKUP databases failed. All subsequent data recording will be suppressed.
Recommended Action Notify the Cisco TAC.
Error Message NSP2012E MODCB OF UPDATE RPL TO BACKUP FAILEDExplanation The attempted switch from PRIMARY to BACKUP databases failed. All subsequent data recording will be suppressed.
Recommended Action Notify the Cisco TAC.
Error Message NSP2013E MODCB OF RECLEN FAILED FOR NEW DB KEYExplanation An attempt to set the record length for a new database record failed.
Recommended Action Notify the Cisco TAC.
Error Message NSP2014E MODCB OF RECLEN FAILED FOR UPDATE OF DB KEYExplanation An attempt to set the record length for an existing database record failed.
Recommended Action Notify the Cisco TAC.
|
|