|
|
This chapter can help you to identify and resolve problems with the mainframe application. When you encounter an unfamiliar message or problem, refer to this chapter before you take any further action.
This chapter includes the following major sections:
This section describes corrective measures for mainframe subtask failures. Almost all subtask startup failures are accompanied by one or more messages written to the SYSLOG, or the output job log, or both. Check the list of mainframe messages in the "Mainframe Messages" section for the course of action to take when an error message is displayed.
The following subsections describe the appropriate action 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 Maps and SNA View Workstation Installation and Administration 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.
 |
Note Restart the mainframe application address space each time a modification is made to a data set or resource. |
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 workstation application is reachable from the mainframe:
D net,aping,id=netid.resourceWhere:
netid.resource is the fully qualified name of the workstation. Until this command returns a positive response, the mainframe application cannot connect to the workstation.
Step 5 Stop the mainframe application's 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 the CiscoWorks Blue host component are listed in Table 6-1.
| RCPRI (hex) | RCSEC (hex) | Meaning and User Action |
|---|---|---|
0 | 0 | Connection completed successfully. No action required. |
0 | 1 | Connection completed successfully. No action required. |
0 | 2 | Connection completed successfully. No action required. |
4 | 8 | Workstation did not recognize the transaction program name 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 | 9 | Workstation recognizes the executable name but cannot start it. Verify that the executable file name specified in the workstation transaction program name profiles match the actual executable program name (cwbstarttp). |
4 | A | Check the file permissions and ownership of the /opt/CSCOcb/bin/cwbstarttp workstation executable programs. It should be owned by "root" with the `S' bit set. Restart SNA. |
8 | 0 | Verify that SNA and the SNA attachment are active on the workstation. If the workstation connection is Token Ring, verify that the 12-digit MAC address is entered correctly on the workstation and that the network identifier (NETID) matches the NETID in the mainframe data set SYS1.VTAMLST(ATCSTRxx). Verify that the LU name in the second parameter of the SERVER SYSIN card matches the available VTAM LU. |
8 | 1 | Verify that the link station is active on the workstation. Verify that the VTAM APPL definition and independent LU (specified in the first and second parameters of the SERVER SYSIN card) are active. |
10 | 2 | VTAM is attempting to process two requests of the same mode type on the same LU. This problem is frequently caused by multiple restart attempts within a short period of time. Stop the SERVER subtask, wait |
14 | 0 | 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 cwbh command on the UNIX workstation to verify that no extraneous processes are running. |
2C | 1 | 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 | 0 | LU 6.2 conversation was terminated prematurely. Check to see if SNA was stopped on the workstation. |
4C | 0 | Session used for the LU 6.2 conversation is terminated, possibly because of a line or modem failure. Check for a break in the physical connection between the workstation and the mainframe. |
98 | 0 | 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 requires a TCP/IP package installed on the mainframe. If a TCP/IP stack is not available, you must use an LU 6.2 connection instead.
A common problem with the TCP/IP connection to the IBM TCP/IP protocol stack is the inability of the 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 the mainframe application is unable to find the TCP/IP address space or the TCP/IP profile data sets, it usually generates the following error message:
NSP150 TCP/IP communications: socket() for workstation message agent failed with errno 39
If this message is displayed during startup, ensure that all steps required to configure TCP/IP were performed.
If the TCP subtask starts but is unable to connect, check that the ports on the TCP card match the ports in the /etc/svopen_config_DOMAINNAME file.
If the problem persists, call the Cisco TAC.
The most common cause for failure of the PPI subtask is that the NetView subsystem interface is not active. This failure 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 the "Mainframe Messages" section.
Check the 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 for messages indicating a failure of the NSPVPPI optional task that must be running in the NetView address space.
The NSPVPPI optional task under NetView starts automatically while NetView is initializing. A successful initialization of the NSPVPPI task generates both the NSP302 and an NSP311 message. If the NSPVPPI task fails to initialize, additional NSPxxx messages are displayed during NetView initialization. Check the list of messages in this chapter to determine why the NSPVPPI task failed to initialize.
If the NetView subsystem interface is not active when NetView starts, the NSPVPPI task will not load, and the following message is issued from NSPVPPI before it terminates:
NSP313 NSPVPPI : NETVIEW INTERFACE FAILURE, RC=0018
To avoid this problem, (and avoid restarting the NSPVPPI task manually), start the subsystem interface address space before starting the NetView address space.
If you have not run the subsystem interface before, review the NetView Installation Guide for instructions on subsystem interface setup, paying special attention to the following:
After the problem is corrected, restart the NSPVPPI task from the NetView operator session using the START TASK=NSPVPPI command.
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 received at the workstation, you should determine whether the message is flowing from VTAM to the mainframe application. You can use the following methods to help diagnose the problem.
If the PPI or PPO INFLOW and OUTFLOW values are incrementing, but the STATUS INFLOW or OUTFLOW values are not incrementing, check the PULU_FILTER and INCLUDE_SW_MAJORNODES and EXCLUDE_SW_MAJORNODES configuration statements.
If the PPI or PPO INFLOW and OUTFLOW values are not incrementing, use the following procedure:
Step 2 Ensure that the NetView NSPVPPI DST (data services terminal) and NSPAUTO1 autotask are active:
list nspvppi
list nspauto1
If you used a different name for the autotask, use it here instead of NSPAUTO1.
Step 3 Ensure that the NSPSVTBL member is included in the automation table and that the automation table is reloaded.
Step 4 Issue the NetView DISBQL ALL command to check PPI connectivity to the mainframe task.
You can use some of the mainframe commands described in the "Issuing Mainframe Commands" section to help debug the mainframe 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 inTable 6-2
| Field | Purpose |
|---|---|
TASKNAME | Identifies the subtask by its name. |
INPUTQ | Number of message buffers queued to the main task by this subtask. If this number grows rapidly and continues to stay high, there might be a problem with the subtask or the main task. |
OUTPUTQ | Number of message buffers queued to this subtask for processing. If this number grows rapidly and continues to stay high, there might be a problem with the subtask. |
MC | Number of message buffers allocated to this subtask. If this number grows rapidly and continues to stay high, there might 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 SHOW TASK command to ensure that the PPI or PPO subtask and the STATUS subtask are active.
The mainframe component can send PU/LU status updates and discovery data. Consequently, the workstation must be able to process this data as fast as it is sent to the workstation.
If the workstation's performance is not fast enough (for example, if it is an overloaded machine), the workstation may be unable to keep up with the mainframe.
Here are some symptoms of this problem that you might see:
If you see these symptoms, issue the following mainframe command:
F NSPOPEN,SHOW FLOWIf there are large numbers in the INPUTQ or OUTPUTQ columns of the transport subtask you are using (TCP or SERVER), your workstation probably is not powerful enough to keep up with the traffic. You could also lengthen the polling cycles to free up some of the CPU to get more processing time.
This section provides information about the messages generated by the mainframe application. The messages are described in numerical order.
NSP001 RCVSYN returned a RPLRTNCD of number
Explanation An internal error has occurred in NSPOPEN application.
Action Notify the Cisco TAC.
NSP002 type SUBTASK INITIALIZED
Explanation The mainframe subtask has successfully initialized. If the subtask has an associated VTAM access method control block (ACB), the ACB information is provided. Task-specific information also is given. Processing continues.
Action No user action is required.
NSP003 FUNCTION returned with rc = NUMBER
Explanation This message is used to issue unexpected errors from internal function to the system log and job stream.
Action Notify the Cisco TAC.
NSP004 RCVSYN received an unexpected RPLFDB2 of NUMBER
Explanation An unexpected return code was issued from the RCVSYN function.
Action Notify the Cisco TAC.
NSP005 COULD NOT OPEN VSAM FILE WITH DDNAME DDNAME.
Explanation You issued a SHOW DLC command, but the VSAM file named DDNAME, used to store PU information for the mainframe task (either XIDDATA or XIDBACK), could not be opened.
Action Determine why the file cannot be opened. The XIDDATA or XIDBACK DD cards might be incorrect.
NSP006 Invalid length %d in message received
Explanation An invalid messages length was specified for a message sent to NSPOPEN.
Action Notify the Cisco TAC.
NSP007 Lost connection with the workstation
Explanation This message issued when the connection to a workstations broken. This message is followed by additional message describing the effected workstation.
Action No user action is required.
NSP008 INVALID INPUT PARAMETER CARD ON LINE number
Explanation The mainframe application read an invalid card from SYSIN. The invalid card is skipped. Processing continues with the next SYSIN card.
Action Correct the input card on the given line number of SYSIN. "Updating the Mainframe Application Software," provides valid values for task cards. Ensure that all other lines begin with an asterisk (*), which indicates that they are comment lines.
NSP009 DUPLICATE subtask CARD ON LINE number IGNORED
Explanation The mainframe application read a definition card from SYSIN for a subtask name, which was already defined. The duplicate card is skipped. Processing continues with the next SYSIN card.
Action Correct or remove the duplicate input card on the given line number of SYSIN. See "Updating the Mainframe Application Software," for names of input parameter cards that might be defined multiple times.
NSP010 MAXIMUM NUMBER OF subtask CARDS REACHED; IGNORING LINE number
Explanation The mainframe application has reached the maximum number of subtasks of the type named in that 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", the mainframe program has reached the maximum allowed subtasks that can be defined; consequently, all SYSIN parameter cards from that line number forward will be ignored. Processing continues.
Action Decrease the number of SYSIN parameter cards of the type named.
NSP011 Invalid msg/command type %d received by task %s
Explanation An internal error has occurred in the NSPOPEN application.
Action Notify the Cisco TAC.
NSP012 Invalid command COMMAND received by task TASK
Explanation An internal error has occurred in the NSPOPEN application.
Action Notify the Cisco TAC.
NSP013 Enqueue failed for TASK OPERATION rc RC
Explanation An internal error has occurred in the NSPOPEN application.
Action Notify the Cisco TAC.
NSP014 Size:BYTES of message too large, max:MAX
Explanation An internal error has occurred in the NSPOPEN application.
Action Notify the Cisco TAC.
NSP015 Error in retrieving VTAM data, location ADDRESS
Explanation An internal error has occurred in the NSPOPEN at the ADDRESS specified in message.
Action Notify the Cisco TAC.
NSP016 Enqueue failed for TASK OPERATION rc RC or NSP016 Dequeue failed for TASK OPERATION rc RC
Explanation An internal error has occurred in the NSPOPEN application.
Action Notify the Cisco TAC.
NSP017 NO DATA FOUND MATCHING REQUESTED KEY
Explanation You issued a SHOW DLC command, but no data was available for the requested PU name.
Action No user action is required.
NSP018 VTAM ACB GENERATION FOR subtask acb FAILED, RC = rcnumber
Explanation An initializing subtask attempted to get a VTAM ACB and failed. The subtask terminates.
Action Verify that the ACB named in acb is active. Use the INIT command to reinitialize the subtask.
NSP019 VTAM subtask OPEN FOR acb FAILED, RC = rcnumber, ERROR = enumber
Explanation An initializing subtask attempted to open a VTAM ACB and failed. The subtask terminates.
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.
NSP020 subtask IS CURRENTLY IN USE
Explanation This message immediately follows the NSP019 message if an exclusive subtask ACB is in use by another program. The mainframe subtask terminates.
Action Verify that the ACB is not being taken by another program on the host, such as NetView or SOLVE:Netmaster.
NSP021 UNSOLICITED msgtype DATA IS UNAVAILABLE
Explanation This message follows the NSP019 message to alert you that the mainframe program is not able to receive unsolicited data because it is unable to access an ACB. The subtask terminates.
Action Verify that the ACB is defined.
NSP022 LEVEL trace enabled for SUBTASK
Explanation Tracing is starting on the specified class.
Action No user action is required.
NSP023 %s trace disabled for %s
Explanation Tracing is stopped on the specified class.
Action No user action is required.
NSP024 No task matching name SUBTASK found
Explanation The task specified for the previous command cannot be found.
Action Verify the subtask name is specified correctly and re-issue the command.
NSP026 UNEXPECTED subtask RETURN CODE, RC = rcnumber
Explanation The subtask Receive routine received an unexpected return code while attempting to receive messages. The subtask terminates.
Action Use the INIT command to reinitialize the subtask.
NSP027 Memory allocation failed
Explanation NSPOPEN was unable to allocate required storage.
Action Increase the amount of storage specified for the NCPOPEN application. If this problem persists notify the Cisco TAC.
NSP028 Task going down, message not queued
Explanation One of the subtask is terminating. This message indicates that information sent to task will be lost.
Action No action required. This is a diagnostic message that can be used to determine cause of other problems that will be indicated with their own error messages.
NSP029 Attempt to free %p when counter %d
Explanation An internal error has occurred in the NSPOPEN application.
Action Notify the Cisco TAC.
NSP030 task COULD NOT ADD ADDRESS TO task2 FREE QUEUE (count)
Explanation An attempt by one subtask to add to another subtask's free queue has failed. The request is retried.
Action No action is required. This is a diagnostic message, which can be used to determine the cause of other problems that are indicated by their own error messages.
NSP031 Attempt to free a message for invalid task %p
Explanation An internal error has occurred in the NSPOPEN application in the ADDRESS specified in message.
Action Notify the Cisco TAC.
NSP032 Task %s failed to free memory
Explanation An internal error has occurred in the NSPOPEN application.
Action Notify the Cisco TAC.
NSP033 SNA Host COMMAND = commandtext
Explanation The command text issued via the mainframe application is logged to SYSLOG and processing continues.
Action No user action is required.
NSP034 INITIALIZATION OF SPO name FAILED IN reqtype PROCESSING, RC1 = addr RC2 = size
Explanation The SPO subtask failed while calling the VTAM Get RPL routine. The SPO subtask terminates.
Action Use the INIT command to reinitialize the subtask.
NSP035 SPO WARNING: FAILURE RETRIEVING COMMAND RESPONSES, MAX RETRIES REACHED
Explanation The mainframe application'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.
Action Reissue the VTAM command. If the proper responses still are not returned, contact the Cisco TAC.
NSP036 Failure in obtaining rif data, location NUMBER
Explanation An error has occurred while retrieving rif data for a Physical Unit.
Action No action required. This is a diagnostic message that can be used to determine cause of other problems that will be indicated with their own error messages.
NSP037 Wrong MDB type TYPE received, expected ETYPE
Explanation An internal error has occurred in the NSPOPEN application.
Action No action required. This is a diagnostic message that can be used to determine cause of other problems that will be indicated with their own error messages.
NSP038 VTAM COMMAND SUPPORT UNAVAILABLE
Explanation The mainframe application could not process the VTAM command because there are no active secondary program operator (SPO) subtasks. The command is discarded.
Action If command support from the workstation is desired, restart the mainframe application 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. Also, you might code a SEC NO parameter card.
NSP039 NODE node_name REMAINS IN PENDING STATE
Explanation The mainframe application detected a PU (node_name) in the pending state after VTAM message IST590I indicated that the connection was established. The mainframe application then tried to display the PU within the time defined by the delay_time option of the STATUS parameter card, but failed.
Action Increase the value of the delay_time option on the STATUS parameter card.
NSP040 Resource RESOURCE not found in database:VSAM RC = RC errno = ERRNO
Explanation The NSPOPEN application was unable to locate information for a physical unit.
Action Verify the VTAM ISTEXCCS exit has been activate and is operational. If this problem persists, contact Cisco TAC.
NSP041 Unable to obtain DLC information for RESOURCE
Explanation The NSPOPEN application was unable to locate DLC information for a physical unit.
Action Verify the VTAM ISTEXCCS exit has been activate and is operational. If this problem persists, contact Cisco TAC.
NSP042 ONLY_SWITCHED_PUS not supported for this VTAM level
Explanation The level of VTAM currently running does not support the following format of the display clusters command.
Action None.
NSP043 SPO card ignored since SEC NO not specified
Explanation You did not provide a SEC NO parameter card, so SNA Resources cannot be activated or deactivated from the workstation. You also provided an SPO parameter card, which specifies a secondary program operator for activating and deactivating SNA resources from the workstation. The SPO card is ignored.
Action If you want to allow SNA Resources to be activated or deactivated from the workstation, provide a SEC NO parameter card.
NSP044 [PPO|PPI] already specified. You cannot specify both PPO and PPI
Explanation You supplied both the PPO and PPI parameter cards. Only one can be specified.
Action Determine whether or not an existing product on the mainframe is defined as the Primary Program Operator (PPO) (such as NetView or Solve:NetMaster). If a PPO already exists, then code the PPI card and ensure that you accomplished the correct NetView or Solve:Netmaster customization. If no product is currently defined as the PPO, then code the PPO card. These definitions are contained in the parameter file.
NSP045 subtask_name card was not specified and is required
Explanation The indicated subtask card (subtask_name) was not specified and is a required card.
Action Add a correctly coded entry for this card to the parameter file.
NSP046 subtask_name card was not specified and is recommended
Explanation The indicated subtask card (subtask_name) was not specified and is a recommended card.
Action If you understand the implications of not coding this card, then this message can be ignored. If you accidently omit the card, you must add a correctly coded card to the parameter file.
NSP047 No PPI or PPO card was specified. One or the other is required
Explanation Neither the PPI or PPO card was specified. You have to specify one or the other.
Action Determine whether or not an existing product on the mainframe is defined as the Primary Program Operator (PPO) (such as NetView or Solve:NetMaster). If a PPO already exists, then code the PPI card and ensure that you accomplished the correct NetView or Solve:Netmaster customization. If no product is currently defined as the PPO, then code the PPO card. These definitions are contained in the parameter file.
NSP048 No TCP or SERVER card was specified. At least one is required
Explanation No TCP or SERVER cards were specified. You need to configure at least one of these in order for a workstation to connect to the mainframe server to acquire the VTAM SNA information.
Action Determine what connectivity you would like to use (TCP/IP or LU 6.2) and code the appropriate card.
NSP049 ERROR OPENING FILE file
Explanation The application could not open the requested file. You might receive this message with the member name being that of the HOSTPU for the VTAM, this is not a problem.
Action If the error is received for any member name other than the host VTAM, contact the Cisco TAC.
NSP050 task COULD NOT FREE MESSAGES (count)
Action No action is required. This is a diagnostic message, which can be used to determine the cause of other problems that are indicated by their own error messages.
NSP051 NO PARAMETERS ALLOWED ON THE STOP COMMAND. TRY KILL
Explanation The STOP command was issued with a parameter. This is not a valid command.
Action Enter the STOP command without any parameters to stop the address space. If you are attempting to stop only one subtask, use the KILL command.
NSP091 PPI INITIALIZATION FAILED, STEP = stepnum RC = rcnumber
Explanation An attempt by the primary program operator subtask to access the CNMNETV module failed. The PPI subtask terminates.
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 PPI subtask. |
3 | Verify that no other application is attached to the NetView or SOLVE:Netmaster program-to-program interface. |
NSP095 SNA Host PPI BUFFER SIZE ERROR, RC = rcnumber
Explanation A Receive request for the PPI failed due to the length of the buffer size. The PPI subtask terminates.
Action Use the INIT command to reinitialize the subtask.
NSP096 SNA Host PPI INTERFACE FAILED, ID = requestid, RC = rcnumber
Explanation A Receive request for the PPI failed. The PPI subtask terminates.
Action See the NetView Application Programming Guide to determine the meaning of the given return code.
NSP111 subtask CNOS mode FAILED, RC = rcnum RCPRI = primaryrc RCSEC = secondaryrc
Explanation The LU 6.2 CNOS command for mode failed during the initialization of the subtask. The mainframe subtask terminates.
Action See the publication VTAM Programming for LU 6.2 for the meaning of the RCPRI and RCSEC return codes.
|
Note The RCPRI and RCSEC codes are valid only if rcnum = B0000. Depending on the codes, you might need to make a correction to a workstation profile or the mainframe VTAM definitions. A dump of the VTAM request parameter list (RPL) control block follows this message. Restart the mainframe application to recover the subtask. |
NSP112 subtask CNOS FOR mode status (RCPRI=primaryrc RCSEC=secondaryrc)
Explanation The LU 6.2 CNOS command for mode is completed for subtask. Processing continues.
Action If status is "failed," stop the mainframe application and check the output job log for more information. See the "Configuring LU 6.2 Connectivity" section. Also, see the publication VTAM Programming for LU 6.2 for a translation of the RCPRI and RCSEC return codes.
NSP113 UNABLE TO ESTABLISH msgtype LU 6.2 COMMUNICATION WITH THE WORKSTATION wsagent AGENT, RC = rcnumber
Explanation Establishment of LU 6.2 sessions between the mainframe and the workstation failed. The SERVER subtask terminates.
Action Verify that the parameters of the SERVER SYSIN card match the VTAM resource names defined for the mainframe application, and that they match the resource names entered in the workstation communications setup.
NSP114 ERROR IN LU 6.2 direction WORKSTATION wsserver SERVER,
RC = rcnumber
Explanation An error occurred in the sending or receiving of an LU 6.2 message between the mainframe and the workstation. The SERVER subtask terminates.
Action Verify the status of the LU 6.2 sessions between the mainframe and the workstation.
NSP115 DUMPING subtask direction action ctrlblk
Explanation The mainframe application subtask encountered an error in LU 6.2 communications to the workstation. Following this message, a dump of the control block specified by ctrlblk is given to aid in problem determination. The SERVER subtask terminates.
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.
NSP119 num MESSAGES QUEUED ON subtask. COMMAND REJECTED: command
Explanation The subtask will not process the command issued from the workstation because of a backlog of messages to be sent to the workstation. The command is discarded. Processing continues on the remaining messages in the subtask's queue.
Action Wait until the existing backlog of messages is processed and then reissue the command. Use the SHOW TASK command to view the number of messages in the subtask's output queue.
NSP121 MVS CONSOLE name COULD NOT OBTAIN A MIGRATION ID
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.
Action No user action is required.
NSP122 MVS CONSOLE name INITIALIZATION FAILED, RC = rcnumber
Explanation The initialization of the MVS console failed. The MVS subtask terminates.
Action Record the return code and report it to the Cisco TAC.
NSP150 TCP/IP COMMUNICATIONS: function FOR WORKSTATION component AGENT FAILED WITH ERRNO value
Explanation A TCP/IP communication error has occurred. The error might have taken place during TCP/IP communication setup, or during a send or receive between the mainframe and the agent specified. The TCP subtask terminates.
Action Verify the availability of TCP/IP communication between the workstation and the mainframe. Use the INIT command to reinitialize the subtask.
NSP151 SNA Host FAILURE IN COMMUNICATION TO TCP/IP
Explanation The mainframe application received an error while attempting to receive data from a TCP/IP socket or event control block (ECB). The TCP/IP subtask terminates.
Action Use the INIT command to reinitialize the subtask.
NSP160 CONSOLE COMMAND RETURN CODE = rcnumber
Explanation An MVS command request completed with a non-zero return code. Processing continues.
Action If an expected command response is not received, record the return code and contact your support representative.
NSP205 MVS CONSOLE name REACHED MEMORY LIMIT. DATA LOST
Explanation The extended console defined for the mainframe application has filled all the available cells in the data space. The incoming message is not queued. Processing continues.
Action Check the status of the extended console with the following command:
NSP206 MVS CONSOLE name REACHED QUEUE LIMIT. DATA LOST
Explanation The extended console defined for the mainframe application has reached its maximum queue depth. The incoming message will not be queued. Processing continues.
Action Check the status of the extended console with the following command:
NSP207 MVS CONSOLE name STOPPED BY INTERNAL ERROR
Explanation The extended console defined for the mainframe application received an error during the processing of its message queues. The mainframe application deactivates the MVS console.
Action Check status of extended console with the following command:
NSP208 MVS CONSOLE name REACHED ALERT PERCENTAGE
Action Verify that messages are being displayed on the MVS messages client on the workstation. Check status of extended console with the following command:
NSP209 MVS CONSOLE name SUSPENDED BY REQUEST
Explanation An error occurred in the extended console defined for the mainframe application, and MVS has requested the deactivation of the console. The mainframe application deactivates the console.
Action Check the status of the extended console with the following command:
NSP210 MVS CONSOLE name ALERT ECB POSTED FOR UNKNOWN REASON
Explanation The extended console defined for the mainframe application was posted with an alert indicating a problem, but no error flags are set in the console's status area. Processing continues.
Action Check the status of the extended console with the following command:
NSP302 name: SNA Host PPI TASK INITIALIZED
Explanation The PPI subtask for the mainframe application was successfully initialized in the NetView address space. Processing continues.
Action No user action is required.
NSP303 name: SNA Host PPI TASK TERMINATED
Explanation The PPI task is terminated in the NetView address space. Processing continues, but the mainframe application no longer receives unsolicited VTAM messages or alerts from NetView.
Action If NetView has terminated, restart NetView. If only the PPI subtask has terminated, restart the subtask from a NetView operator session with the following command:
NSP304 name: DSIFRE FAILED FOR USER STORAGE
Explanation The PPI subtask received an error return code from the NetView DSIFRE macro while attempting to free the 4-KB work area of memory during subtask shutdown. Subtask shutdown processing continues.
Action Notify the system programmer that a potential memory leak exists in the currently running NetView.
NSP305 name: DSIFRE FAILED FOR QUEUED STORAGE
Explanation The 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.
Action Notify the system programmer that a potential memory leak exists in the currently running NetView.
NSP306 name: DSIFRE FAILED FOR MQS BUFFER
Explanation The 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.
Action Notify the system programmer that a potential memory leak exists in the currently running NetView.
NSP307 name: DSIGET FAILED FOR USER STORAGE
Explanation The PPI subtask failed to get a 4 KB block of memory for use during processing. The task termination flag is set.
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.
NSP308 name: ENQ ERROR
Explanation An enqueue request (ENQ) on the NetView's task vector block (TVB) chain failed. If the process is not already terminated, the task termination flag is set.
Action Notify the system programmer. Restart the PPI subtask.
NSP309 name: DEQ ERROR
Explanation A dequeue request (DEQ) on the NetView's task vector block (TVB) chain failed. If the process is not already terminated, the task termination flag is set.
Action Notify the system programmer. Restart the PPI subtask.
NSP310 name: TASK ALREADY EXISTS
Explanation The 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.
Action Verify that another instance of the subtask is not already running under this NetView. Restart the PPI subtask.
NSP311 name: LOAD OF CNMNETV COMPLETE
Explanation The loading of the CNMNETV module into virtual storage completed successfully. Processing continues.
Action No user action is required.
NSP312 name: UNABLE TO LOAD CNMNETV
Explanation The loading of the CNMNETV module into virtual storage failed. The subtask terminates.
Action Verify that load module CNMNETV exists in a NetView STEPLIB data set. Restart the PPI subtask.
NSP313 name: NETVIEW INTERFACE FAILURE, RC = rcnumber
Explanation A call to the CNMNETV interface routine failed. The message is discarded.
Action See the NetView Application Programming Guide to determine the meaning of the given return code.
NSP314 name: NETVIEW COMMAND RECEIVED
Explanation A message was successfully received from the PPI interface routine. Processing continues.
Action No user action is required. This message appears for debugging purposes, and appears only if you reassembled the subtask with the CMDREC lines uncommented.
NSP595 COMMAND ENTERED:cmdtxt
Explanation The mainframe application received a command from a console. Processing continues with the execution of the command.
Action No user action is required.
NSP600 TNUM TASKNAME STATUS RESTARTS/LIMIT SPECIFIC
Explanation This message is issued in response to the SHOW TASK command. An entry is displayed for each subtask along with its status, the number of times it was restarted, and task-specific information.
Action No user action is required.
NSP603 TNUM TASKNAME ADDRESS HEADER TCB
Explanation This message is issued in response to the SHOW ADDR command. An entry is displayed for each subtask along with its address, task header address, and TCB address.
Action No user action is required.
NSP605 TNUM TASKNAME INPUTQ OUTPUTQ INFLOW OUTFLOW MC
Explanation This message is 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 passed through, and the number of message buffers currently allocated to the task.
Action No user action is required.
NSP607 CiscoWorks Blue SNA Host version Copyright copyright Cisco Systems
Explanation This message is issued in response to the SHOW VERSION command to specify the version of the workstation program.
Action No user action is required.
NSP608 TASKNAME DATE TIME
Explanation This is the 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.
Action No user action is required.
NSP690 SNA Host STOP Command accepted
Explanation Displays the output of the STOP command. The mainframe application terminates.
Action No user action is required.
NSP695 SNA Host cmdtype command processed.
Explanation The mainframe application completed the initial processing of a console command. Additional messages might be forthcoming, depending on whether any additional work is to be done by the subtasks.
Action No user action is required.
NSP698 Subtask task is already status
Explanation A subtask modification command was invalid because of the current state of the target subtask. Processing continues.
Action Use the SHOW TASK command to check the subtask's status.
NSP699 Invalid operator command entered
Explanation You entered an invalid command.
Action Check the command and try again. Use the HELP command to see a list of valid commands.
NSP701 Starting subtask #idnum for info
Explanation The mainframe application attached a subtask with the information given in info. Processing continues with the ATTACH attempt.
Action No user action is required.
NSP702 Buffer size = sizeM, Queue depth = totalmsg, Maximum = maxmsg
Explanation A message queuing problem occurred for an MCS console defined for the mainframe application. This message appears only in the mainframe application job log and is followed immediately by a more detailed message. Processing continues. The MCS console might be terminated, depending on the severity of the queueing problem.
Action Monitor the mainframe application job log for the next message.
NSP705 TNUM TASKNAME FREE USED
Explanation This message displays the output of the SHOW FREEQ command. The mainframe application lists the number of free and used slots on each task's queue.
Action No user action is required.
NSP706 TNUM TASKNAME SPECIFIC CLIENT
Explanation This message displays the output of the SHOW CONN command. The mainframe application 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.
Action No user action is required.
NSP708 pu_name xid local_mac local_sap remote_mac remote_sap rif
Explanation This message displays the output of the SHOW DLC command. The data recorded for the PU name during the exchange of XIDs is displayed.
Action No user action is required.
NSP710 rif_data
NSP901 Stopping subtask # number: name
Explanation This message is issued in response to a STOP command. One message is issued for each subtask. A termination command is sent to each named subtask.
Action No user action is required.
NSP902 name subtask terminated, RC = rcnumber
Explanation The named subtask has been terminated. Any queues or memory allocated for the subtask are freed.
Action No user action is required.
NSP903 name in/out queue freed, RC = rcnumber
An allocated message queue for the named subtask is freed. Processing continues.
Action No user action is required.
NSP904 All SNA Host subtasks completed
Explanation The mainframe application has completed the shutdown of all subtasks. Processing continues with the shutdown of the main task.
Action No user action is required.
NSP905 Restart # attempt of subtask task will be attempted in time seconds
Explanation The named subtask terminated and attempts to restart automatically in the stated number of seconds. The subtask sleeps for the specified number of seconds before attempting to restart itself.
Action No user action is required. The INIT command is used during the delay to bypass the delay and perform an immediate restart of the subtask. The KILL command is used to bring down the subtask and cancel any further automatic restart attempts.
NSP906 No auto restart for task. Use INIT command to restart.
Explanation The named subtask terminated and does not attempt to restart itself because either the operator explicitly issued a KILL command against the subtask, or the maximum number of restart attempts was exceeded. The INIT command might be used to reinitialize the subtask and reset the number of restart attempts. The subtask is terminated.
Action No user action is required.
NSP907 LU6.2 return codes RCPRI = x, RCSEC = y
Explanation This message is issued for LU 6.2 error conditions, listing the primary and secondary return codes.
Action Record the return codes for problem determination.
NSP2000I DATA RECORDED TO dbtype FOR PU puname
Explanation Data for the PU identified by puname was successfully recorded in the database identified by dbtype.
Action No action is required.
NSP2003E dbtype XID OUTPUT DATA SET UNAVAILABLE.
Explanation OPEN failed for the database identified by dbtype.
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 of lost data in the event switching is 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.
NSP2005E WRONG VECTOR PASSED.
Explanation An internal failure in the 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.
Action Use the following command sequence to reinitialize the exit routine:
NSP2006E PUT NOT SUCCESSFUL R15 = r15value RC = rcvalue
Explanation An attempt to write a data record to a database failed. If recording to the PRIMARY database is active, the 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.NSPS300.NSPSSAMP in member NSPDBVSM.
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.
NSP2007E NO DATASET AVAILABLE FOR OUTPUT.
Explanation One of the following errors occurred:
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 of lost data in the event switching is required.
NSP2008E DID NOT PUT DB KEY R15 = r15value RC = rcvalue
Explanation An attempt to write a VSAM key to a database failed.
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.
NSP2009E MODCB OF RECLEN FAILED FOR NEW RECORD
Explanation An attempt to set the record length (RECLEN) value for a new database record failed.
Action Notify the Cisco TAC.
NSP2010E MODCB OF RECLEN FAILED FOR UPDATE
Explanation An attempt to set the RECLEN value for update of an existing database record failed.
Action Notify the Cisco TAC.
NSP2011E MODCB OF PUT RPL TO BACKUP FAILED
Explanation The attempted switch from PRIMARY to BACKUP databases failed. All subsequent data recording will be suppressed.
Action Notify the Cisco TAC.
NSP2012E MODCB OF UPDATE RPL TO BACKUP FAILED
Explanation The attempted switch from PRIMARY to BACKUP databases failed. All subsequent data recording will be suppressed.
Action Notify the Cisco TAC.
NSP2013E MODCB OF RECLEN FAILED FOR NEW DB KEY
Explanation An attempt to set the record length for a new database record failed.
Action Notify the Cisco TAC.
NSP2014E MODCB OF RECLEN FAILED FOR UPDATE OF DB KEY
Explanation An attempt to set the record length for an existing database record failed.
Action Notify the Cisco TAC
Posted: Mon Sep 4 09:22:09 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.