|
|
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:
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.
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:
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.
| 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 | Step 1 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. Step 2 Restart SNA. |
8 | 0 | Step 1 Verify that SNA and the SNA attachment are active on the workstation. Step 2 If the workstation connection is Token Ring, verify that the 12-digit MAC address is correctly entered on the workstation and that the network identifier (NETID) matches the NETID in the mainframe data set SYS1.VTAMLST(ATCSTRxx). Step 3 Verify that the LU name in the second parameter of the SERVER SYSIN card matches the available VTAM LU. |
8 | 1 | Step 1 Verify that the link station is active on the workstation. Step 2 Verify that the VTAM APPL definition and independent LU (specified in the first and second parameters of the SERVER SYSIN card) are active. |
10 | 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 30 seconds, and then restart the subtask. |
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 there are no extraneous processes 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 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:
NSP150 TCP/IP communications: socket() for workstation message agent failed with errno 39
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.
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.
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 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:
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 procedrue:
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.
You can use some of the mainframe commands described in the section "Issuing Mainframe Commands"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 in Table 6-2.
| Field | Purpose |
|---|---|
TASKNAME | Identifies the subtask by subtask 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 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:
If you see these symptoms, issue the following mainframe command:
F NSPOPEN,SHOW FLOW
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.
This section provides information about the messages generated by the mainframe application. The messages are described in numerical order.
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.
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.
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.
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 may be defined multiple times.
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.
Explanation You issued a SHOW DLC command, but no data was available for the requested PU name.
Recommended Action No user action is required.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Where:
stepnum is the step of initialization that 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.
| 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. |
Where:
rcnumber is the return code from the PPI call.
Explanation A Receive request for the PPI failed because of the length of the buffer size. The PPI subtask terminates.
Recommended Action Use the INIT command to reinitialize the subtask.
Where:
requestid is the ID of the task request.
rcnumber is the return code from the PPI call.
Explanation A Receive request for the PPI failed. The PPI subtask terminates.
Recommended Action See the NetView Application Programming Guide to determine the meaning of the given return code.
Where:
subtask is the name of the subtask.
mode is the mode name (SNASVCMG or PARALLEL).
rcnum is the return code from the CNOS call.
primaryrc is the primary return code from the CNOS request.
secondaryrc is the secondary return code from the CNOS request.
Explanation The LU 6.2 CNOS command for mode failed during the initialization of the subtask. The mainframe subtask terminates.
Recommended Action See the publication VTAM Programming for LU 6.2 for the meaning of the RCPRI and RCSEC return codes.
Where:
subtask is the name of the subtask.
mode is the mode name (SNASVCMG or PARALLEL).
status is the status of the task; it is either "succeeded" or "failed."
primaryrc is the primary return code from the CNOS request.
secondaryrc is the secondary return code from the CNOS request.
Explanation The LU 6.2 CNOS command for mode is completed for subtask. Processing continues.
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.
Where:
msgtype is the type of LU 6.2 message. The following message types are possible:
wsagent is the workstation agent. The following agents are possible:
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.
Where:
direction is the direction of the message. The following directions are possible:
wsserver is the workstation server. The following servers are possible:
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.
Where:
subtask is the subtask name.
direction is the direction of the message. The following directions are possible:
action is the attempted action. The following actions are possible:
ctrlblk is the control block being dumped. The following control blocks are possible:
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.
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.
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.
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.
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.
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.
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.
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:
DISPLAYCONSOLES, CN=name
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.
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:
DISPLAYCONSOLES, CN=name
If messages do not resume queuing to the extended console, restart the mainframe application, ensuring that the console comes down cleanly.
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:
DISPLAYCONSOLES, CN=name
Restart the mainframe application.
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:
DISPLAYCONSOLES, CN=name
If the queue shortage is not relieved shortly, stop and restart the mainframe PROC.
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:
DISPLAYCONSOLES, CN=name
Restart the mainframe application.
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:
DISPLAYCONSOLES, CN=name
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.
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:
START TASK=name
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Explanation Displays the output of the STOP command. The mainframe application terminates.
Recommended Action No user action is required.
Where:
cmdtype is the name of the command just processed.
Explanation The mainframe application completed the initial processing of a console command. Additional messages may be forthcoming, depending on whether any additional work is to be done by the subtasks.
Recommended Action No user action is required.
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.
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.
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.
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 may be terminated, depending on the severity of the queueing problem.
Recommended Action Monitor the mainframe application job log for the next 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.
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.
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.
Where:
rif_data is the Routing Information Field data.
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.
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.
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.
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.
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.
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 may be used to reinitialize the subtask and reset the number of restart attempts. The subtask is terminated.
Recommended Action No user action is required.
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.
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.
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.
In the event that switching is necessary and no BACKUP is available, all vector processing is suppressed. In either case, loss of data is probable.
Recommended Action Failure to open the PRIMARY database must be corrected immediately for the data recording function to initialize. Failure to open the BACKUP is less severe and can be deferred, with the possible consequence that data may eventually be lost if switching is ever required. Usually a failure to open is caused by a configuration problem rather than a component failure. Check the allocation for the identified database to ensure that it is allocated correctly. Databases are identified in the VTAM startup procedure. The PRIMARY database is identified by the XIDDATA DD statement; the BACKUP database is identified by the XIDBACK DD statement. Verify that the DSNAMES (DSN keyword) identify the correct data sets.
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:
F NET,EXIT,ID=ISTEXCCS,OPT=INACT
F NET,EXIT,ID=ISTEXCCS,OPT=ACT,MODULE=exitname
Where exitname is the name given to the NSP Exit Manager load module. If the problem recurs, notify the Cisco TAC.
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.NSPS200I.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.
Explanation One of the following errors occurred:
Recommended Action Failure to open the PRIMARY database must be corrected immediately for the data recording function to initialize. Failure to open the BACKUP database is less severe and can be deferred, with the possible consequence that data may eventually be lost if switching is ever required.
Database switching should not occur. It usually occurs because the database is too small for the network being tracked. Increase the amount of space allocated to the PRIMARY and BACKUP databases. A sample job stream to allocate databases is included in prefix.NSPS200I.NSPSSAMP in member NSPDBVSM. Change the allocation parameters to those appropriate for your network.
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.
Explanation An attempt to set the record length (RECLEN) value for a new database record failed.
Recommended Action Notify the Cisco TAC.
Explanation An attempt to set the RECLEN value for update of an existing database record failed.
Recommended Action Notify the Cisco TAC.
Explanation The attempted switch from PRIMARY to BACKUP databases failed. All subsequent data recording will be suppressed.
Recommended Action Notify the Cisco TAC.
Explanation The attempted switch from PRIMARY to BACKUP databases failed. All subsequent data recording will be suppressed.
Recommended Action Notify the Cisco TAC.
Explanation An attempt to set the record length for a new database record failed.
Recommended Action Notify the Cisco TAC.
Explanation An attempt to set the record length for an existing database record failed.
Recommended Action Notify the Cisco TAC.
Posted: Wed Aug 4 09:41:34 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.