Troubleshooting the SNA View Mainframe Application

Subtask Startup Problems

LU6.2 Connection (SERVER Subtask)

TCP/IP Connection (TCP Subtask)

PPI Subtask with NetView

PPI Task Failure Under NetView

Mainframe Messages

Troubleshooting the SNA View Mainframe Application

This chapter contains information useful for identifying and resolving problems that may be encountered on the mainframe while using SNA View.

When an unfamiliar message or problem is encountered, consult this chapter before taking any other action.

This chapter contains two major sections:

Subtask Startup Problems---describes how to resolve SNA View failures that are attributable to mainframe subtask problems.
Mainframe Messages---lists the meaning of and appropriate user response to each message generated by SNA View's mainframe application.

Subtask Startup Problems

This section describes corrective measures for SNA View malfunctions attributable to mainframe subtask failures.

Almost all subtask startup failures are accompanied by one or more messages that are written either to the SYSLOG, the SNA View output job log, or both. Check the list of SNA View mainframe messages (with the format NSPnnn) in this chapter for courses of action to take when any given error message is displayed.

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

LU6.2 Connection (SERVER Subtask)

A successful LU6.2 connection requires exact compliance with the setup instructions given in this manual and the CiscoWorks Blue SNA View Workstation Installation Guide. All steps in the connection must be up and available, and all parameters between the mainframe and the workstation must match exactly.

If the LU6.2 session fails to connect, perform the following steps.

Note The mainframe address space must be restarted each time a modification is made to a dataset or resource.

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

a VTAM APPL resource
a VTAM independent LU
the "PARALLEL" parameter
a TPN for the workstation HCI
a TPN for the workstation Message Server.

Step 2 Verify that the VTAM APPL resource is defined in SYS1.VTAMLST with the parameter APPC=YES. Verify that the resource is activated under VTAM.

Step 3 Verify that the VTAM LU is defined as an independent LU, either by a LOCADDR=0 definition under its PU, or as a CDRSC in a CDRSC major node definition. Verify that the LU is activated under VTAM.

Step 4 Stop the SNA View address space and check the bottom of the output job log for messages. The most significant message is the primary and secondary return codes (RCPRI and RCSEC) from the LU6.2 connection request.

Check the job log for the first occurrence of message NSP111, NSP112, or NSP907. The RCPRI and RCSEC codes are fully documented in IBM's VTAM Programming for LU6.2 manual.

Common RCPRI/RCSEC combinations encountered when installing SNA View are listed in Table 4-1.

Table 4-1 Common RCPRI/RCSEC Combinations

RCPRI RCSEC Meaning and User Action

0 hex 0 hex Connection completed successfully. No action.

0 hex 1 hex Connection completed successfully. No action.

0 hex 2 hex Connection completed successfully. No action.

4 hex 8 hex The workstation did not recognize the TPN name that was sent from the mainframe, so check for a mismatch in the spelling of the fourth and fifth parameters of the SERVER SYSIN card against the spelling of the TPN profiles on the workstation.

4 hex 9 hex The workstation recognizes the executable name, but cannot start it. Verify that the executable filenames specified in the workstation TPN profiles match the actual executable program names. Recall that on IBM AIX installations the executable names have the domain name appended to them during installation.

4 hex A hex Step 1 Start the evohci_server program manually on the workstation and verify that comes up without error. (The most common cause is an invalid license file entry).
Step 2 Check the file permissions on the workstation executable programs.
Step 3 If running on an HP workstation, recycle SNA. (The workstation recognizes the TPN executable, but encountered a problem while activating it.)

8 hex 0 hex Step 1 Verify that SNA and the SNA attachment are active on the workstation.
Step 2 If the workstation connection is via Token Ring, verify that the 12-digit MAC address is correctly entered on the workstation and that the NetID matched the NetID in mainframe dataset SYS1.VTAMLST(ATCSTRxx).
Step 3 Verify that the LU name in the 2nd parameter of the SERVER SYSIN card matches the available VTAM LU.

8 hex 1 hex Step 1 Verify that the link station is active on the workstation.
Step 2 Verify that the VTAM APPL definition and independent LU (specified in the first and second parameters of the SERVER SYSIN card are active.

10 hex 2 hex VTAM is attempting to process two requests of the same mode type on the same LU, frequently caused by multiple restart attempts within a short period of time. Bring the SERVER subtask down, wait 30 seconds, and then bring it back up.

14 hex 0 hex The transaction program on the workstation terminated abnormally. Wait until all ports on the workstation are cleared. Before retrying the connection, enter the command, ps -ef | grep evo on the workstation to verify that there are no extraneous processes running.

2C hex 1 hex The logmode name specified in the 3rd parameter of the SERVER SYSIN card was not recognized on the workstation. If an NSP112 message was issued to indicate the SNASVCMG CNOS succeeded, but the PARALLEL CNOS failed, verify that SNA and the SNA attachment are active on the workstation.

48 0 The LU6.2 conversation was terminated prematurely. Check to see if either SNA Services or SNA Server was stopped on the workstation.

4C 0 The session used for the LU6.2 conversation has been terminated, possibly because of a line or modem failure. Check for a break in the physical connection between the workstation and mainframe.

98 0 An overload of commands with large replies is causing a memory shortage while sending data.

RCPRI	RCSEC	Meaning and User Action
0 hex	0 hex	Connection completed successfully. No action.
0 hex	1 hex	Connection completed successfully. No action.
0 hex	2 hex	Connection completed successfully. No action.
4 hex	8 hex	The workstation did not recognize the TPN name that was sent from the mainframe, so check for a mismatch in the spelling of the fourth and fifth parameters of the SERVER SYSIN card against the spelling of the TPN profiles on the workstation.
4 hex	9 hex	The workstation recognizes the executable name, but cannot start it. Verify that the executable filenames specified in the workstation TPN profiles match the actual executable program names. Recall that on IBM AIX installations the executable names have the domain name appended to them during installation.
4 hex	A hex	Step 1 Start the evohci_server program manually on the workstation and verify that comes up without error. (The most common cause is an invalid license file entry). Step 2 Check the file permissions on the workstation executable programs. Step 3 If running on an HP workstation, recycle SNA. (The workstation recognizes the TPN executable, but encountered a problem while activating it.)
8 hex	0 hex	Step 1 Verify that SNA and the SNA attachment are active on the workstation. Step 2 If the workstation connection is via Token Ring, verify that the 12-digit MAC address is correctly entered on the workstation and that the NetID matched the NetID in mainframe dataset SYS1.VTAMLST(ATCSTRxx). Step 3 Verify that the LU name in the 2nd parameter of the SERVER SYSIN card matches the available VTAM LU.
8 hex	1 hex	Step 1 Verify that the link station is active on the workstation. Step 2 Verify that the VTAM APPL definition and independent LU (specified in the first and second parameters of the SERVER SYSIN card are active.
10 hex	2 hex	VTAM is attempting to process two requests of the same mode type on the same LU, frequently caused by multiple restart attempts within a short period of time. Bring the SERVER subtask down, wait 30 seconds, and then bring it back up.
14 hex	0 hex	The transaction program on the workstation terminated abnormally. Wait until all ports on the workstation are cleared. Before retrying the connection, enter the command, `ps -ef \| grep evo` on the workstation to verify that there are no extraneous processes running.
2C hex	1 hex	The logmode name specified in the 3rd parameter of the SERVER SYSIN card was not recognized on the workstation. If an NSP112 message was issued to indicate the SNASVCMG CNOS succeeded, but the PARALLEL CNOS failed, verify that SNA and the SNA attachment are active on the workstation.
48	0	The LU6.2 conversation was terminated prematurely. Check to see if either SNA Services or SNA Server was stopped on the workstation.
4C	0	The session used for the LU6.2 conversation has been terminated, possibly because of a line or modem failure. Check for a break in the physical connection between the workstation and mainframe.
98	0	An overload of commands with large replies is causing a memory shortage while sending data.

TCP/IP Connection (TCP Subtask)

Setup of a TCP/IP connection is less complex than that of an LU6.2 connection, but it requires that the mainframe has a TCP/IP package installed. If a TCP/IP stack is not available, you must use the LU6.2 connection method.

The most common problem with the TCP/IP connection is an inability of the SNA View TCP subtask to communicate to IBM's TCP/IP package due to the name of either the TCP/IP address space or the TCP/IP datasets having been changed from their defaults. When SNA View is unable to find the TCP/IP address space or the TCP/IP profile datasets, it will usually generate the following error message:

NSP150  TCP/IP communications: socket() for workstation message agent failed 
with errno 39

If this message is displayed during SNA View startup, verify the following points (not all of these points may be relevant on your system):

Note Restart SNA View after each item if any changes are made:

To perform these steps:

Step 1 If the TCP/IP datasets are not using the default high-level qualifier, make a copy of the hlq.TCPIP.DATA dataset and name it TCPIP.TCPIP.DATA.

Step 2 If the TCP/IP address space is not named TCPIP, edit the TCPIP.TCPIP.DATA dataset that you just created and verify that the TCPIPJOBNAME or TCPIPUSERID parameter is correctly set to the name of the TCP/IP address space.

Step 3 If the parameter in your TCPIP.TCPIP.DATA dataset is TCPIPJOBNAME, change it to TCPIPUSERID. (Older versions of the TCP/IP connection software do not recognize TCPIPJOBNAME.)

PPI Subtask with NetView

The most common cause for failure of the PPI subtask is that the NetView subsystem interface (SSI) is not active. This will cause the display of an NSP091 message with an RC=24. The possible values for RC on the NSP091 message are listed the appendix to the NetView Application Programming Guide.

Also, check the SNA View startup JCL to ensure that the STEPLIB includes the NetView loadlib that contains the CNMCNETV load module.

Additionally, check the SYSLOG during the time of NetView startup and look for messages indicating a failure of the NTILU62 optional task that must be running in the NetView address space.

PPI Task Failure Under NetView

The NTILU62 optional task under NetView should come up automatically as NetView is initializing. A successful initialization of the NTILU62 task will generate both an NSP302 and an NSP311 message. If the NTILU62 task fails to initialize, additional NSPxxx messages will be displayed during NetView initialization. Check the list of SNA View messages in this chapter to determine why the NTILU62 task failed to initialize.

If the NetView Subsystem Interface (SSI) is not active when NetView starts, the NTILU62 task will not load and the following message will be issued from NTILU62 before it terminates:

NSP313  NTILU62  : NETVIEW INTERFACE FAILURE, RC=0018

To avoid this message when NetView starts (and thus to avoid having to restart the NTILU62 task manually), start the SSI address space before the NetView address space.

If the system has not previously had the SSI running, review the NetView Installation Guide for instructions on SSI setup, paying special attention to the following:

The SSI 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 SSI address space must be "NETV."
The four-character subsystem name must also be listed in the SYS1.PARMLIB(IEFSSNxx) member. Any change to this member will require an IPL.
The CNMCSSIR and CNMCALRT tasks must be defined in NetView's DSIDMN member with INIT=Y.

After the problem is corrected, the NTILU62 task can be re-started from the NetView operator session using the command START TASK=NTILU62.

Mainframe Messages

This section explains all messages generated by the SNA View mainframe application.

Error Message NSP002

type         subtask initialized

Explanation The SNA View subtask has initialized successfully. If the subtask has an associated ACB, the ACB information is given. Along with this message is task specific information. Processing continues.

Recommended Action No user action is required.

Error Message NSP008

Invalid input parameter card on line number

Explanation SNA View read a line from SYSIN that it did not understand. The invalid card is skipped. Processing continues with the next SYSIN card.

Recommended Action Correct the input card on the given line number of SYSIN. Valid values for task registration cards are given in "Updating the Mainframe Application Software." All other lines must begin with an * to denote a comment line.

Error Message NSP009

Duplicate subtask         card on line number ignored

Explanation SNA View read a definition card from SYSIN for a subtask that has already been defined. The invalid card is skipped. Processing continues with the next SYSIN card.

Recommended Action Correct or remove the input card on the given line number of SYSIN. Refer to "Updating the Mainframe Application Software" for names of input parameter cards that may be defined multiple times.

Error Message NSP010

Maximum number of subtask         cards reached; ignoring line number

subtask is the type of subtask.

number is the line number of SYSIN.

Explanation SNA View has reached the maximum number of subtasks of the type named. The definition card on the named line will not be processed. If subtask is subtask, SNA View has reached the maximum number of total subtasks that can be defined, and all SYSIN parameter cards from line number forward will be ignored. The parameter card(s) are skipped and processing continues.

Recommended Action Decrease the number of SYSIN parameter cards of the type named.

Error Message NSP018

VTAM ACB generation for subtask         acb failed, RC = rcnumber

subtask is the type of subtask.

acb is the name of failing ACB.

rcnumber is the return code from Get VTAM ACB routine

Explanation An attempt by an initializing subtask to get a VTAM ACB failed. The SNA View subtask terminates.

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

Error Message NSP019

VTAM subtask         open for acb failed, RC = rcnumber, error = enumber

subtask is the type of subtask.

acb is the name of failing ACB.

rcnumber is the return code from Open VTAM ACB routine.

enumber is the error code within ACB.

Explanation An attempt by an initializing subtask to open a VTAM ACB failed. The SNA View subtask terminates with a condition code 8.

Recommended Action Verify that ACB is correctly defined and not already in use. See VTAM Programming manual for descriptions of the return code and error code.

Error Message NSP020

subtask         is currently in use

subtask is the type of subtask.

Explanation This message follows immediately after the NSP019 message if an exclusive subtask ACB is already in use by another program. The SNA View subtask terminates.

Recommended Action Verify that the ACB is not being taken by another program on the host, such as NetView or NET/MASTER.

Error Message NSP021

Unsolicited msgtype         data is unavailable

msgtype is the type of message.

Explanation This message follows the NSP019 message to alert the user that SNA View will not be able to receive unsolicited data because it was unable to access an ACB. The SNA View subtask terminates.

Recommended Action No user action required.

Error Message NSP026

Unexpected subtask         return code, RC = rcnumber

subtask is the type of subtask.

rcnumber is the return code from Receive routine.

Explanation The subtask Receive routine received an unexpected return code while attempting to receive messages. The SNA View subtask terminates.

Recommended Action Use the INIT command to reinitialize the subtask.

Error Message NSP033

SNA View COMMAND = commandtext

Explanation The command text issued via SNA View has been logged to SYSLOG. Processing continues.

Recommended Action No user action is required.

Error Message NSP034

Initialization of SPO name         failed in reqtype processing, RC1 = addr RC2 = 
size

name is the name of SPO subtask.

reqtype is the type of request being processed.

addr is the returned address from Get RPL routine.

size is the returned size from Get RPL routine.

Explanation The SPO subtask failed calling the VTAM RPL routine. The SNA View SPO subtask terminates.

Recommended Action Use the INIT command to reinitialize the subtask.

Error Message NSP035

SPO Warning:  Failure retrieving command responses

Explanation SNA View's Secondary Program Operator interface subtask encountered a failure while attempting to retrieve the command responses from an issued VTAM command. All responses were not retrieved. Processing continues.

Recommended Action Reissue the VTAM command. If the proper responses are still not returned, contact your technical support representative.

Error Message NSP038

VTAM command support unavailable

Explanation SNA View could not process the VTAM command because there are no active Secondary Program Operator subtasks. The command is discarded.

Recommended Action Restart SNA View with an SPO card in the SYSIN deck that identifies a valid VTAM APPL resource to be used as a SPO. Verify that the named VTAM resource is active.

Error Message NSP091

PPI initialization failed, step = stepnum         RC = rcnumber

stepnum is the step of initialization that failed:

1 = SSI not up
2 = Attempt to get ASCB value failed
3 = Attempt to register as a receiver failed

rcnumber is the return code from call to CNMNETV

Explanation An attempt by the PPI subtask to access the CNMNETV module failed. The SNA View PPI subtask terminates with a condition code 6.

Recommended Action If stepnum = 1, check the status of the SSI. If stepnum = 3, verify that no other application is attached to the NetView or Netmaster PPI.

Error Message NSP095

SNA View PPI buffer size error, RC = rcnumber

rcnumber is the return code from PPI call.

Explanation A Receive request for the PPI failed due to the length of the buffer size. The SNA View PPI subtask terminates.

Recommended Action Use the INIT command to reinitialize the subtask.

Error Message NSP096

SNA View PPI interface failed, ID = requestid        , RC = rcnumber

requestid is the ID of task request.

rcnumber is the return code from PPI call.

Explanation A Receive request for the PPI failed. The SNA View PPI subtask terminates.

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

Error Message NSP111

subtask         CNOS mode failed, RC = rcnum RCPRI = primaryrc RCSEC = secondaryrc

subtask is the name of subtask.

mode is the mode name.

rcnum is the return code from CNOS call.

primaryrc is the primary return code from CNOS request.

secondaryrc is the secondary return code from CNOS request.

Explanation The LU6.2 CNOS command for mode mode failed during the initialization of subtask subtask. The SNA View subtask terminates.

Recommended Action Consult VTAM Programming for LU6.2 for a translation of the RCPRI and RCSEC return codes.

Note The RCPRI and RCSEC codes are only valid if rcnum = B0000. Depending on the codes, a correction may be needed to a workstation profile or the mainframe VTAM definitions. A dump of the VTAM RPL control block will follow this message. Recycle SNA View to recover the subtask.

Error Message NSP112

subtask         CNOS for mode status (RCPRI=primaryrc RCSEC=secondaryrc)

subtask is the name of subtask.

mode is the mode name.

status is either "succeeded" or "failed."

primaryrc is the primary return code from CNOS request.

secondaryrc is the secondary return code from CNOS request.

Explanation The LU6.2 CNOS command for mode mode completed for subtask subtask. Processing continues.

Recommended Action If status is "failed," stop SNA View and check the output job log for more information. Consult VTAM Programming manual for LU6.2 for a translation of the RCPRI and RCSEC return codes.

Error Message NSP113

Unable to establish msgtype         LU6.2 communication with the workstation 
wsagent agent, RC = rcnumber

msgtype is the type of LU6.2 message:

outbound = Allocation from the mainframe to workstation
inbound = Allocation from the workstation to mainframe
Send = Message transmission from mainframe to workstation
Receive = Message transmission from workstation to mainframe

wsagent is the workstation agent:

command = workstation command agent
message = workstation message agent

rcnumber is the return code from LU6.2 call

Explanation Establishment of LU6.2 session(s) between the mainframe and workstation failed. The SNA View SERVER subtask terminates.

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

Error Message NSP114

Error in LU6.2 direction         workstation wsserver server, RC = rcnumber

direction is the direction of message:

"Send to" = From mainframe to workstation
"Receive from" = From workstation to mainframe

wsserver is the workstation server:

command = command server
HCI = HCI server

rcnumber is the return code from LU6.2 call.

Explanation An error occurred in the sending or receiving of an LU6.2 message between the mainframe and the workstation. The SNA View SERVER subtask terminates.

Recommended Action Verify the status of the LU6.2 session(s) between the mainframe and the workstation.

Error Message NSP115

Dumping subtask         direction action ctrlblk

subtask is the subtask name.

direction is the direction of message:

outbound = From mainframe to workstation
inbound = From workstation to mainframe

action is the attempted action:

allocate = Allocation of an LU6.2 conversation
receive = Sending a message over an established conversation

ctrlblk is the control block being dumped:

RPL = Request Parameter List
RPL6X = Request Parameter List Extension

Explanation SNA View subtask encountered an error in LU6.2 communications to the workstation. Following this message, a dump of the control block ctrlblk will be given to aid in problem determination. The SNA View SERVER subtask terminates.

Recommended Action Consult VTAM Programming manual for a mapping of the control block. Correct the error and use the INIT command to reinitialize the subtask.

Error Message NSP119

num         messages queued on subtask. Command rejected: command

num is the number of messages.

subtask is the subtask name.

command is the command entered.

Explanation Subtask subtask will not process the command issued from the workstation because there is a backlog of num messages that are waiting to be sent to the workstation. The command command is discarded. Processing continues on the remaining messages in the subtask's queue.

Recommended Action Wait until the existing backlog of messages has been processed and then re-issue the command. Use the SHOW TASK command to view the number of messages in the Output Queue of the subtask.

Error Message NSP121

MVS console name         could not obtain a migration ID

name is the name of console to be defined.

Explanation The MVS console being defined requested a one-byte migration ID, but the console initialization routine was unable to provide one. Initialization of the console continues.

Recommended Action No user action is required.

Error Message NSP122

MVS console name         initialization failed, RC = rcnumber

name is the name of console to be defined.

rcnumber is the return code from initialization routine.

Explanation The initialization of the MVS console failed. The SNA View MVS subtask terminates.

Recommended Action Record the return code and report it to your support representative.

Error Message NSP150

TCP/IP communications: function         for workstation component agent failed 
with errno value

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 communications error has occurred. The error could have taken place during TCP/IP communication establishment or during a send or receive between the mainframe and the agent specified. The SNA View TCP subtask terminates.

Recommended Action Verify the availability of TCP/IP communications between the workstation and the mainframe. Use the INIT command to reinitialize the subtask.

Error Message NSP151

SNA View failure in communication to TCP/IP

Explanation SNA View received an error while attempting to receive data from a TCP/IP socket or ECB. The TCP/IP subtask terminates.

Recommended Action Use the INIT command to reinitialize the subtask.

Error Message NSP160

Console command return code = rcnumber

rcnumber is the return code from command send subroutine.

Explanation An MVS command request completed with a non-zero return code. Processing continues.

Recommended Action If expected command response is not received, record the return code and contact your support representative.

Error Message NSP205

MVS console name         reached memory limit. Data lost

Explanation The extended console defined for SNA View has filled all of the available cells in the data space. The incoming message is not queued. Processing continues.

Recommended Action Check the status of the extended console with a DISPLAY CONSOLES, CN=name. If messages do not resume queuing to the extended console, recycle SNA View, making sure that the console comes down cleanly. A new console may need to be defined with a larger message data space.

Error Message NSP206

MVS console name         reached queue limit. Data lost

The extended console defined for SNA View has reached its maximum queue depth. The incoming message will not be queued. Processing continues.

Error Message NSP207

MVS console name         stopped by internal error

Explanation The extended console defined for SNA View received an error during the processing of its message queues. SNA View deactivates the MVS console.

Recommended Action Check the status of the extended console with a DISPLAY CONSOLES, CN=name. Recycle SNA View.

Error Message NSP208

MVS console name         reached alert percentage

Explanation The number of messages queued to the extended console for SNA View has reached a certain percentage of the maximum queue depth. Processing continues.

Recommended Action Verify that messages are being displayed on the MVS messages client on the workstation. Check the status of the extended console with the command DISPLAY CONSOLES, CN=name. If the queue shortage is note relieved shortly, recycle SNA View, making sure that the console comes down cleanly.

Error Message NSP209

MVS console name         suspended by request

Explanation A condition has developed in the extended console defined for SNA View such that MVS has requested the deactivation of the console. SNA View deactivates the console.

Recommended Action Check the condition of the console with the command DISPLAY CONSOLES, CN=name. Recycle SNA View.

Error Message NSP210

MVS console name         alert ECB posted for unknown reason

Explanation The extended console defined for SNA View was posted with an alert indicating a problem, but no error flags were set in the console's status area. Processing continues.

Recommended Action Check the condition of the console with the command DISPLAY CONSOLES, CN=name.

Error Message NSP302

name        : SNA View PPI TASK INITIALIZED