Table of Contents

Subtask Problems

LU 6.2 Connection (SERVER Subtask)
TCP/IP Connection (TCP Subtask)
PPI Subtask with NetView
PPI Task Failure under NetView
Data Gathering Errors
Using Mainframe Commands for Troubleshooting

Using the SHOW ADDR Command
Using the SHOW FLOW Command
Using the SHOW FREEQ Command
Using the SHOW TASK Command

Workstation Overrun by Mainframe

Mainframe Messages

Troubleshooting the Mainframe Application

Use this chapter to identify and resolve problems with the 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:

• Subtask Problems describes how to resolve failures that are attributable to mainframe subtask problems.

• Mainframe Messages lists the meaning of and appropriate user response for each message generated by the mainframe application.

Subtask Problems

This section describes corrective measures for mainframe subtask failures. Almost all subtask startup failures are accompanied by one or more messages that are written to the SYSLOG, to the output job log, or to both. Check the list of mainframe messages in the section "Mainframe Messages" for a course of action to take when a specific error message is displayed.

The following sections describe the appropriate actions to take when a failure of a specific subtask occurs.

• LU 6.2 Connection (SERVER Subtask)

• TCP/IP Connection (TCP Subtask)

• PPI Subtask with NetView

• PPI Task Failure under NetView

• Data Gathering Errors

• Using Mainframe Commands for Troubleshooting

• Workstation Overrun by Mainframe

LU 6.2 Connection (SERVER Subtask)

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.

Step 1 Verify that the SYSIN deck has a SERVER parameter card with the following five parameters:

• VTAM APPL resource

• VTAM independent LU

• PARALLEL parameter

• Transaction program name for the host command interface (NSPOPNMS)

• Transaction program name for the host command server (NSPOPNCS)

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.resource

Where:

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.

TCP/IP Connection (TCP Subtask)

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 to the IBM TCP/IP protocol stack is an 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 will usually generate the following error message:

If this message is displayed during startup, ensure that all steps needed 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.

PPI Subtask with NetView

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 section "Mainframe Messages".

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 and look for messages indicating a failure of the NSPVPPI optional task that must be running in the NetView address space.

PPI Task Failure under NetView

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:

To avoid this problem when NetView starts (and avoid restarting the NSPVPPI 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:

• The subsystem interface address space must start with the same four characters as the NetView address space. For example, if the NetView address space is named "NETVIEW", then the first four characters of the subsystem interface address space must be "NETV".

• The four-character subsystem name must be listed in the SYS1.PARMLIB(IEFSSNxx) member. Any change to this member requires an IPL.

• You must define the CNMCSSIR task in NetView's DSIDMN member. CNMCSSIR is defined with INIT=N.

After the problem is corrected, restart the NSPVPPI task from the NetView operator session using the START TASK=NSPVPPI command.

Data Gathering Errors

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.

• Use the F NSPOPEN,SHOW TASK command to ensure that the PPI or PPO subtask and the STATUS subtask are active.

• Use the F NSPOPEN,SHOW FLOW command to check the INFLOW and OUTFLOW values for the PPI or PPO subtask and for the STATUS subtask. Those values should be greater than 0 and should increment each time a status change occurs.

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 1 Ensure that the VTAM PPOLOG parameter is set to yes (MODIFY vtamproc,PPOLOG=YES) as documented in the "Updating MVS and VTAM" section in the "Updating the Mainframe Application Software" chapter.

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.

Using Mainframe Commands for Troubleshooting

You can use some of the mainframe commands described in the section "Issuing Mainframe Commands"to help debug the mainframe task.

Using the SHOW ADDR Command

The SHOW ADDR command displays important subtask information that might be required by the Cisco TAC.

Using the SHOW FLOW Command

The SHOW FLOW command displays several key fields for troubleshooting, as shown in Table 6-2.

Using the SHOW FREEQ Command

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.

Using the SHOW TASK Command

Use the SHOW TASK command to ensure that the PPI or PPO subtask and the STATUS subtask are active.

Workstation Overrun by Mainframe

The mainframe component can send PU/LU status updates and discovery data. Consequently, the workstation needs to 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), it is possible that the workstation will not be able to keep up with the mainframe.

Here are some symptoms of this problem that you might see:

• Commands from the workstation fail to receive responses.

• The status that the workstation displays for a PU or LU is inaccurate for long periods of time even though the view is refreshed.

If you see these symptoms, issue the following mainframe command:

If 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 try to free up some of the CPU to get more processing time.

Mainframe Messages

This section provides information about the messages generated by the mainframe application. The messages are described in numerical order.

Error Message   

Where:

type is the subtask type.

Explanation   The mainframe 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   

Where:

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 the mainframe task (either XIDDATA or XIDBACK), could not be opened.

Recommended Action   Determine why the file cannot be opened. The XIDDATA or XIDBACK DD cards might be incorrect.

Error Message   

Where:

number is the line number of SYSIN.

Explanation   The mainframe application 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 cards. Ensure that all other lines begin with an asterisk (*), which indicates that they are comment lines.

Error Message   

Where:

subtask is the type of the subtask.

number is the line number of SYSIN.

Explanation   The mainframe application 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 might be defined multiple times.

Error Message   

Where:

subtask is the type of the subtask: SERVER, SPO, TCP, or SUBTASK.

number is the line number of SYSIN.

Explanation   The mainframe application 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", the mainframe program 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   

Explanation   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   

Where:

subtask 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 subtask terminates.

Recommended Action   Verify that the ACB named in acb is active. Use the INIT command to reinitialize the subtask.

Error Message   

Where:

subtask 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 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   

Where:

subtask 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 mainframe 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   

Where:

msgtype is the type of the message.

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.

Recommended Action   Verify that the ACB is defined.

Error Message   

Where:

subtask 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 subtask terminates.

Recommended Action   Use the INIT command to reinitialize the subtask.

Error Message   

Where:

task1 is the name of the subtask attempting to add a message to another subtask's free queue.

task2 is the name of the subtask whose queue is being added to.

count is the number of times the attempt has failed.

Explanation   An attempt by one subtask to add to another subtask's free queue has failed. The request is retried.

Recommended Action   No action is required. This is a diagostic message that can be used to determine the cause of other problems that will be indicated with their own error messages.

Error Message   

Where:

commandtext is a mainframe command.

Explanation   The command text issued via the mainframe application is logged to SYSLOG and processing continues.

Recommended Action   No user action is required.

Error Message   

Where:

name 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 SPO subtask terminates.

Recommended Action   Use the INIT command to reinitialize the subtask.

Error Message   

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.

Recommended Action   Reissue the VTAM command. If the proper responses are still not returned, contact the Cisco TAC.

Error Message   

Explanation   The mainframe application could not process the VTAM command because there are no active secondary program operator (SPO) subtasks. The command is discarded.

Recommended 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 codea SEC NO parameter card.

Error Message   

Where:

node_name is the node name of a PU.

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.

Recommended Action   Increase the value of the delay_time option on the STATUS parameter card.

Error Message   

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.

Recommended Action   If you want to allow SNA Resources to be activated or deactivated from the workstation, provide a SEC NO parameter card.

Error Message   

Explanation   You supplied both the PPO and PPI parameter cards. Only one can be specified.

Recommended Action   Determine whether or not an existing product on the mainframe is already 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 have done 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.

Error Message   

Explanation   The indicated subtask card (subtask_name) was not specified and is a required card.

Recommended Action   Add a correctly coded entry for this card to the parameter file.

Error Message   

Explanation   The indicated subtask card (subtask_name) was not specified and is a recommended card.

Recommended Action   If you intended to not code this card and understand the implications then this message can be ignored. If the card was not supplied by accident then add a correctly coded card to the parameter file.

Error Message   

Explanation   Neither the PPI or PPO card was specified. You have to specify one or the other.

Recommended Action   Determine whether or not an existing product on the mainframe is already 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 have done 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.

Error Message   

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.

Recommended Action   Determine what connectivity you would like to use (TCP/IP or LU 6.2) and code the appropriate card.

Error Message   

Where:

file is the name of the member that could not be opened.

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.

Recommended Action   If the error is received for any member name other than the host VTAM, contact the Cisco TAC.

Error Message   

Where:

task is the name of the subtask that is attempting to free messages

count is the number of times the operation has been attempted.

Recommended Action   No action is required. This is a diagostic message that can be used to determine the cause of other problems that will be indicated with their own error messages.

Error Message   

Explanation   The STOP command was issued with a parameter. This is not a valid command.

Recommended 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.

Error Message   

Where:

stepnum 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 PPI subtask terminates.

Recommended Action   Table 6-3 shows you what to do depending on the value of stepnum.

Recommended Action   If status is "failed," stop the mainframe application and check the output job log for more information. See the section "Configuring LU 6.2 Connectivity". Also, see the publication VTAM Programming for LU 6.2 for a translation of the RCPRI and RCSEC return codes.

Error Message   

Where:

msgtype is the type of LU 6.2 message. The following message 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. The following 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 SERVER subtask terminates.

Recommended Action   Verify that the parameters of the SERVER SYSIN card match the VTAM resource names defined for the mainframe application and also match the resource names entered in the workstation communications setup.

Error Message   

Where:

direction is the direction of the message. The following directions are possible:

• Send to --- Message flows from the mainframe to the workstation.

• Receive from--- Message flows from the workstation to the mainframe.

wsserver is the workstation server. The following 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 SERVER subtask terminates.

Recommended Action   Verify the status of the LU 6.2 sessions between the mainframe and the workstation.

Error Message   

Where:

subtask is the subtask name.

direction is the direction of the message. The following directions are possible:

• outbound --- From the mainframe to the workstation.

• inbound --- From the workstation to the mainframe.

action is the attempted action. The following 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. The following control blocks are possible:

• RPL--- VTAM Request Parameter List.

• RPL6X--- VTAM Request Parameter List Extension.

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.

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   

Where:

num 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 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 is 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   

Where:

name 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   

Where:

name 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 MVS subtask terminates.

Recommended Action   Record the return code and report it to the Cisco TAC.

Error Message   

Where:

function 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 might have taken place during TCP/IP communication establishment or during a send or receive between the mainframe and the agent specified. The 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   

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.

Recommended Action   Use the INIT command to reinitialize the subtask.

Error Message   

Where:

rcnumber 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   

Where:

name is the console name.

Explanation   The extended console defined for the mainframe application 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:

If messages do not resume queuing to the extended console, restart the mainframe application to ensure that the console comes down cleanly. You might need to define a new console with a larger message data space.

Error Message   

Where:

name is the console name.

Explanation   The extended console defined for the mainframe application 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:

If messages do not resume queuing to the extended console, restart the mainframe application, ensuring that the console comes down cleanly.

Error Message   

Where:

name is the console name.

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.

Recommended Action   Check status of extended console with the following command:

Restart the mainframe application.

Error Message   

Where:

name is the console name.

Explanation   The number of messages queued to the extended console for the mainframe application 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:

If the queue shortage is not relieved shortly, stop and restart the mainframe PROC.

Error Message   

Where:

name is the console name.

Explanation   A 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.

Recommended Action   Check the status of the extended console with the following command:

Restart the mainframe application.

Error Message   

Where:

name is the console name.

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.

Recommended Action   Check the status of the extended console with the following command:

Error Message   

name is the name of the NetView program-to-program interface (PPI) subtask.

Explanation   The PPI subtask for the mainframe application was successfully initialized in the NetView address space. Processing continues.

Recommended Action   No user action is required.

Error Message   

Where:

name is the name of the NetView PPI subtask.

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.

Recommended 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:

Error Message   

Where:

name is the name of the NetView PPI subtask.

Explanation   The PPI subtask received an error return code from the NetView DSIFRE macro while attempting to free the 4 Kbyte 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   

Where:

name is the name of the NetView PPI subtask.

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.

Recommended Action   Notify the system programmer that a potential memory leak exists in the currently running NetView.

Error Message   

Where:

name is the name of the NetView PPI subtask.

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.

Recommended Action   Notify the system programmer that a potential memory leak exists in the currently running NetView.

Error Message   

Where:

name is the name of the NetView PPI subtask.

Explanation   The PPI subtask failed to get a 4 KB 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   

Where:

name is the name of the NetView PPI subtask.

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.

Recommended Action   Notify the system programmer. Restart the PPI subtask.

Error Message   

Where:

name is the name of the NetView PPI subtask.

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.

Recommended Action   Notify the system programmer. Restart the PPI subtask.

Error Message   

Where:

name is the name of the NetView PPI subtask.

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.

Recommended Action   Verify that another instance of the subtask is not already running under this NetView. Restart the PPI subtask.

Error Message   

Where:

name is the name of the NetView 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   

Where:

name is the name of the NetView 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   

Where:

name is the name of the NetView PPI subtask.

rcnumber is the hexadecimal return code from CNMNETV call.

Explanation   A call to the CNMNETV interface routine failed. The message is discarded.

Recommended Action   See the NetView Application Programming Guide to determine the meaning of the given return code.

Error Message   

Where:

name is the name of the NetView PPI subtask.

Explanation   A message was successfully received from the PPI interface routine. Processing continues.

Recommended Action   No user action is required. This message appears for debugging purposes, and appears only if you reassembled the subtask with the CMDREC lines uncommented.

Error Message   

Where:

cmdtxt is the text of the command entered.

Explanation   The mainframe application received a command from a console. Processing continues with the execution of the command.

Recommended Action   No user action is required.

Error Message   

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 has been restarted, and task-specific information.

Recommended Action   No user action is required.

Error Message   

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.

Recommended Action   No user action is required.

Error Message   

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 have passed through, and the number of message buffers currently allocated to the task.

Recommended Action   No user action is required.

Error Message   

Where:

version is the version number of the installed mainframe application.

copyright lists the copyright years for the installed mainframe application.

Explanation   This message is issued in response to the SHOW VERSION command to specify the version of the workstation program.

Recommended Action   No user action is required.

Error Message   

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.

Recommended Action   No user action is required.

Error Message   

Explanation   Displays the output of the STOP command. The mainframe application terminates.

Recommended Action   No user action is required.

Error Message   

Where:

cmdtype is the name of the command just 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.

Recommended Action   No user action is required.

Error Message   

task 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   

Explanation   You entered an invalid command.

Recommended Action   Check the command and try again. Use the HELP command to see a list of valid commands.

Error Message   

Where:

idnum is the numerical ID for the newly started subtask.

info is the information sent to the ATTACH macro.

Explanation   The mainframe application attached a subtask with the information given in info. Processing continues with the ATTACH attempt.

Recommended Action   No user action is required.

Error Message   

Where:

sizeM 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 occurred for an MCS console defined for the mainframe application. This message appears only in the mainframe application job log and is immediately followed by a message that gives more detailed information. Processing continues. The MCS console might be terminated, depending on the severity of the queueing problem.

Recommended Action   Monitor the mainframe application job log for the next message.

Error Message   

Where:

TNUM 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   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.

Recommended Action   No user action is required.

Error Message   

Where:

TNUM 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   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.

Recommended Action   No user action is required.

Error Message   

Where:

pu_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.

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.

Recommended Action   No user action is required.

Error Message   

Where:

rif_data is the Routing Information Field data.

Error Message   

Where:

number 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 subtask. A termination command is sent to each named subtask.

Recommended Action   No user action is required.

Error Message   

Where:

name 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   

Where:

name is the name of the subtask.

in/out is input or output.

rcnumber is the return code from the Free call.

Explanation   An allocated message queue for the named subtask is freed. Processing continues.

Recommended Action   No user action is required.

Error Message   

Explanation   The mainframe application 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   

Where:

attempt 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 terminated and attempts 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 is used during the delay to bypass the delay and do an immediate restart of the subtask. The KILL command is used to bring down the subtask and cancel any further automatic restart attempts.

Error Message   

task is the subtask name.

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 has been exceeded for the subtask. The INIT command might 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   

Explanation   This message is 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   

Where:

dbtype 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   

Where:

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.

• If dbtype is PRIMARY, all subsequent vector processing will be suppressed.

• If dbtype is BACKUP, processing proceeds, but switching from primary to backup cannot occur.

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 might 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   

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.

Recommended Action   Use the following command sequence to reinitialize the exit routine:

Where exitname is the name given to the NSP Exit Manager load module. If the problem recurs, notify the Cisco TAC.

Error Message   

Where:

r15value 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 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.NSPS210I.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   

Explanation   One of the following errors occurred:

• During initialization of the Data Recording Function, the PRIMARY database, identified by the XIDDATA DD statement in the VTAM startup procedure, could not be opened.

• During routine operation, an attempt was made to switch from the PRIMARY to the BACKUP database, and the switch operation failed.

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 might eventually be lost if switching is ever required.

If you have set the database sizes large enough, it should not be necessary for Maps and SNA View to switch databases. Database switching 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.NSPS210I.NSPSSAMP in member NSPDBVSM. Change the allocation parameters to those appropriate for your network.

Error Message   

Where:

r15value 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   

Explanation   An attempt to set the record length (RECLEN) value for a new database record failed.

Recommended Action   Notify the Cisco TAC.

Error Message   

Explanation   An attempt to set the RECLEN value for update of an existing database record failed.

Recommended Action   Notify the Cisco TAC.

Error Message   

Explanation   The attempted switch from PRIMARY to BACKUP databases failed. All subsequent data recording will be suppressed.

Recommended Action   Notify the Cisco TAC.

Error Message   

Explanation   The attempted switch from PRIMARY to BACKUP databases failed. All subsequent data recording will be suppressed.

Recommended Action   Notify the Cisco TAC.

Error Message   

Explanation   An attempt to set the record length for a new database record failed.

Recommended Action   Notify the Cisco TAC.

Error Message   

Explanation   An attempt to set the record length for an existing database record failed.

Recommended Action   Notify the Cisco TAC.

Posted: Thu Sep 9 08:41:18 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.