|
|
This chapter contains the following major sections:
SNA View processes relay operating and error messages to several locations.
All SNA View errors are of the form SVXXXnnn message_text, where, XXX is a 2- or 3-letter message category, and nnn is a 3-digit numeric identifier. Here is an example:
SVSOK050 Socket connect failed, will retry momentarily.
This message is from the Socket Communications Messages (SOK) component and has a message identifier of 050. You can use the message ID to locate the message in this chapter.
This chapter provides a detailed description of each message and, if appropriate, a recommended user response.
SNA View contains a debugging facility that can be enabled to generate data about SNA View processes. SNA View is shipped with a default debugging parameter file in which debugging mode is turned OFF for all SNA View processes. There may be times when this debugging information is necessary, such as when you provide Cisco TAC personnel with problem reports of SNA View errors. You can generate detailed debugging data for any reproducible problem.
The SNA View debugging parameter file resides in the $SVHOME/parm directory under the filename svdebug.parm. Each line in this file contains a debugging identifier and a hexadecimal number representing a debugging level set for that process. A debugging level of 0 indicates no debugging data is generated. Table 6-1 lists and describes each debugging level.
| Debugging Level | Description |
|---|---|
| 0 | No debugging data is produced. |
| 1 | Function tracing statements are produced. |
| 1f | Function tracing statements and function details are produced. |
| ffff | Function traces, details, and hexadecimal dumps of all interprocess message flows are produced. |
To activate debugging for an SNA View process, locate the debugging identifier for that process in the svdebug.parm file and set the debugging level accordingly. Table 6-2 lists the debugging identifiers found in the svdebug.parm file and the SNA View processes affected by each.
This section details problems related to communications between the SNA View mainframe and workstation components in TCP/IP and LU 6.2 environments.
The SNA View Task Manager will verify that the mainframe component of SNA View is compatible with the workstation component. If the versions are not compatible, the connection to the mainframe is dropped. The Task Manager displays its version information in the top line of the Task Manager window. If the version is not displayed, it is a version prior to 1.1.
You can see the SNA View mainframe version by issuing the F NSPOPEN, SHOW VERSION command. If the mainframe component is at the current release, but the workstation is not, then the versions are not compatible. Upgrade the workstation to the current release.
If the Host Connection Interface or the Host Command Server will not initialize successfully, perhaps due to communications problems between the workstation and mainframe, perform the following procedures.
Step 1 Verify that the SVMF_AGENT_ADDR configuration parameter is set to the correct IP address or host name of the mainframe.
Step 2 Verify the network connection from the workstation to the mainframe by issuing a TCP/IP ping command.
Step 3 Verify that the SVMF_HCI_AGENT_PORT and the SVMF_CMDS_AGENT_PORT configuration parameters are set correctly on the workstation. These configuration parameter values must match the parameter card values for the TCP subtask on the mainframe.
Step 1 For IBM TCP/IP connections, verify that the TCP subtask for your requested ports is active. Issue the F NSPOPEN,SHOW TASK command and look for the desired ports to confirm that the TCP subtask's state is READY. If the TCP subtask's state is not READY, use the SNA View INIT command to activate the TCP subtask.
Step 2 Verify that another workstation is not connected to the TCP subtask. Issue the F NSPOPEN,SHOW CONN command to confirm that there is no connection for the relevant TCP subtask. If another workstation is connected, choose a different pair of port numbers and reconfigure SNA View.
The best source of information for debugging LU 6.2 problems is the job log of the SNA View mainframe component. It will contain error messages written by the SERVER subtask.
For LU 6.2 connections, verify that the associated SERVER subtask is active. Issue the F NSPOPEN,SHOW TASK command to confirm that the SERVER subtask's states are UP. See the CiscoWorks Blue SNA View Mainframe Installation and User Guide for more details on problems and solutions with the SERVER subtask and LU 6.2 communications.
This section discusses issues specific to the SNA stacks under which SNA View will run.
If HP SNAplus2 Link software is used, you can find helpful information for troubleshooting LU 6.2 connectivity problems in audit message logs, error message logs, and link traces.
SNAplus2 Link generates audit messages and error messages during operation and writes them to files specified during configuration of SNAplus2 Link. See the HP-UX SNAplus2 Administration Guide for more details on specifying log files and message severity levels.
When you start a link with tracing, tracing information is written to the trace files snafile1.trc and snafile2.trc in addition to the diagnostic messages written to the audit and error logs. Use the snapmanage command to start a link with tracing. Please see the
HP-UX SNAplus2 Administration Guide for more details.
The following situations can arise when you use IBM's Communication Server software for host connectivity.
When the SNA View mainframe component is started with a SERVER subtask, the Communications Server for AIX application running on the RS/6000 receives an FMH5 transmission from the host and launches the transaction programs specified in the LU 6.2 Transaction Program Profiles configured during SNA View installation. These transaction programs are named as follows:
svhci_server_DOMAIN1
svcommand_server_DOMAIN1
In this example, DOMAIN1 is the SNA View SNA domain to be managed. These executables reside in the $SVHOME/bin directory and should have been created by the SNA View workstation installation program. If these two files are not present for each domain to be managed via LU 6.2 communications, you can create them using the following commands, replacing DOMAIN1 with your domain name.
cd $SVHOME/bin
cp svhci_server svhci_server_DOMAIN1
chmod ugo+rwxs svhci_server_DOMAIN1
cp svcommand_server svcommand_server_DOMAIN1
chmod ugo+rwxs svcommand_server_DOMAIN1
The Communications Server for AIX application maintains error logs that detail SNA (and therefore LU 6.2) failures that occur. To generate SNA error reports, you can either see the appropriate Communications Server for AIX documentation, or you can use the following procedure:
Step 1 Start the SMIT utility by entering smit at an AIX command prompt.
Step 2 On the initial SMIT menu, click Communications Applications and Services.
Step 3 On the next menu, click Communication Server for AIX.
Step 4 On the next menu, click Problem Determination Aids.
Step 5 On the next menu, click Show SNA Logs and Traces.
Step 6 Select Show System Error Log to send the formatted log to standard output.
This section describes problems that can arise during typical operation of SNA View. The scenarios covered here are categorized according to the SNA View component or task that can experience a failure. Problems are sorted in categories that are described in the following sections:
SNA View's Task Manager process allows the user to control SNA View processes for all managed SNA domains. Occasionally, problems with starting and stopping SNA View processes may arise. This section documents some of the more common problems and describes the appropriate actions you can take to resolve them.
If you attempt to connect to a domain and the connection to the mainframe fails, try the following suggestions to resolve this problem.
If the domain uses LU 6.2 communication between the mainframe and the workstation, call your SNA View mainframe system administrator or network administrator to verify that the PU, specified on the SNA View SERVER parameter card, is active. Then ask your SNA View mainframe administrator to stop and restart the mainframe SERVER subtask, which will automatically start the Host Connection Interface and Host Command Server on the workstation. After the SERVER subtask has been restarted, verify that the Host Connection Interface and Host Command Server have started successfully.
If the domain uses TCP/IP communications between the mainframe and workstation, restart the Host Connection Interface and Host Command Server tasks. A message like the following will tell you that initialization is complete:
SVINI001 Host Connection Interface initialized successfully for domain [DOMAIN].
SVINI001 Command Server initialized successfully for domain [DOMAIN].
The VTAM Server is responsible for providing VTAM messages to all registered VTAM clients. If the VTAM Server will not initialize successfully, then review the error messages and see the "General Problems" section earlier in this chapter for possible solutions. In the "Configuration File Problems" subsection of "General Problems," pay special attention to the SVHCI_AGENT_ADDR and SVHCI_VTAM_PORT configuration parameters. Verify that they are set correctly and that the Host Connection Interface is active.
The MVS Server is responsible for providing MVS messages to all registered MVS clients. If the MVS Server will not initialize successfully, then review the error messages generated and see the "General Problems" section for details on possible solutions. In the "Configuration File Problems" subsection of "General Problems," pay special attention to the SVHCI_AGENT_ADDR and SVHCI_MVS_PORT configuration parameters. Verify that they are set correctly and that the Host Connection Interface is active.
The VTAM Message Log process registers as a client of the VTAM Server during initialization. If the VTAM Message Log encounters a problem prior to registration to the VTAM Server, or if it is unable to register to the VTAM Server, the process will not initialize. Review the error messages generated, and see the "General Problems" section earlier in this chapter for possible solutions. In the "Configuration File Problems" subsection of "General Problems," pay attention to the SVVTAM_AGENT_ADDR and SVVTAM_AGENT_PORT configuration parameters. Verify that they are set correctly and that the VTAM Server is active.
The MVS Message Log process registers as a client of the MVS Server during initialization. If the MVS Message Log encounters a problem prior to registration to the MVS Server, or if it is unable to register to the MVS Server, the process will not initialize. Review the error messages generated and see the "General Problems" section earlier in this chapter for possible solutions. In the "Configuration File Problems" subsection of "General Problems," pay special attention to the SVMVS_AGENT_ADDR and SVMVS_AGENT_PORT configuration parameters. Verify that they are set correctly and that the MVS Server is active.
If the Status/Discovery task will not initialize successfully, note the error messages generated and see the "General Problems" section earlier in this chapter for possible solutions. In the "Configuration File Problems" subsection of "General Problems," pay special attention to the SVHCI_AGENT_ADDR, SVHCI_STATUS_PORT, SVSTATUS_AGENT_ADDR, and SVSTATUS_AGENT_PORT configuration parameters. Verify that they are set correctly and that the Host Connection Interface is active.
Problems relating to discovery and status management are described in the following sections:
Discovery is a process that gathers the information on PUs and LUs for a specific domain and stores that information in the Sybase database.
To gather information for the Status/Discovery process, a connection to the domain must be established. Problems can occur with this connection. See the "Workstation-to-Mainframe Connectivity Problems" section for more detail.
The pu_status_manager process must be given a domain name on the command line as its first command argument. Otherwise, the following error message will appear:
SVINI011 Domain name must be passed to SNAView pu_status_manager.
If you started this process from the command line, verify that you entered the correct options. If you have entered the correct options, notify the Cisco TAC.
If you try to run the pu_status_manager process, after any other user runs it, the mainframe commands cannot write their output data to the necessary file. This problem occurs because the permissions for that file prevent other users from writing to it.
The System Administrator can fix this problem by changing the permissions for the files, which reside in the SVWORK_AREA directory.
The pu_status_manager process attempts to initiate a session with the Sybase application program interface (API). If this attempt fails, the program will exit with the following error messages:
The Sybase login failed: exiting.
SVEXE102 pu_status_manager process of domain [domain] has exited.
The pu_status_manager process gathers configuration variables from the configuration file for the specified domain. For details regarding errors that may occur during the collection of configuration variables, see the "Configuration File Problems" section in this chapter. The following error messages will be generated if an error occurs:
SVEXE000 pu_status_manager failed calling Get_config_vars.
SVEXE102 pu_status_manager process of domain [domain] has exited.
The pu_status_manager process logs information about how it populated the database in a file. If the pu_status_manager cannot open this log file, it will exit with the following error messages:
pu_status_manager - Could not open log file: exiting.
SVEXE102 pu_status_manager process of domain [domain] has exited.
The pu_status_manager process uses the debugging file $SVHOME/parm/svdebug.parm to determine what level of debugging to use. If the file does not exist, if it has incorrect permissions assigned, or if SVDISCOVER is not a valid debugging process name, the pu_status_manager process will exit with the following error messages:
SVINI040 Error setting debug value, unable to find module pu_status_manager in pu_status_manager.
SVEXE102 pu_status_manager process of domain [domain] has exited.
When LUs are not discovered, there is usually a problem in the configuration file. In the "Configuration File Problems" section of this chapter, review the information provided for the INCLUDE_LUS configuration parameter, which must be set to YES (or yes) in order to enable discovery of LUs. Call your SNA View mainframe system administrator or network administrator to verify that the SNA View LU_CONTROL parameter card is configured to send LU information to the workstation.
The Status/Discovery process updates the workstation database with the current status of resources known to VTAM. The Status/Discovery process can also keep the workstation management database updated with the appearance of new resources. There is a Status/Discovery process for each managed domain.
To receive information on status changes, a connection to the monitored domain must be established. Problems can occur with this connection. See the "Workstation-to-Mainframe Connectivity Problems" section in this chapter for details.
If connectivity does not exist when the Status/Discovery process is activated, the following messages will be displayed:
SVINI000 status Manager initialized successfully.
SVSOK001 server_connect_tcp_socket() failed calling connect(), reason: Connection refused
SVSOK051 socket connect failed, no retry will be attempted.
SVEXE100 sserver_connect_tcp_socket() process has exited.
The Status/Discovery process must receive a domain name as the first argument of the command; otherwise, the following error will appear:
SVINI011 Domain name must be passed to SNAView Pu_status_manager.
The Status/Discovery process attempts to initiate a session with the Sybase API. If this attempt fails, the program will exit with the following errors:
The Sybase login failed: exiting.
SVEXE102 PU_status_manager process of domain [domain] has exited.
The Status/Discovery process gathers configuration variables from the configuration file for the specified domain. For details regarding errors that may occur during the collection of configuration variables, see the "Configuration File Problems" section of this chapter. The following error messages will be generated if an error occurs:
SVEXE000 Pu_status_manager failed calling Get_config_vars
SVEXE102 Pu_status_manager process of domain [domain] has exited.
The Status/Discovery process uses the configuration parameter SVSOCKET_MODE to determine whether it should connect to the Host Connection Interface with a TCP or UNIX domain socket. If this variable is not set correctly, the Status/Discovery process will exit with the following error messages:
SVINI020 Pu_status_manager encountered invalid value for configuration parameter SVSOCKET_MODE.
SVEXE102 Pu_status_manager process of domain [domain] has exited.
Since the Status/Discovery process is a standard client, review the socket errors (SVSOKxxx) described in the section "SNA View Workstation Messages" later in this chapter.
The Status/Discovery process receives updated PU information from the mainframe when a status change occurs or when a new PU is discovered. If status updates are not being received at the SNA View workstation (that is, when the status of a PU changes but the change is not reflected when the PU information is displayed), messages may not be flowing from VTAM to SNA View on the mainframe. Ask your mainframe administrator to use the following commands:
This problem is described in the "Troubleshooting the SNA View Mainframe Application" chapter of the SNA View Mainframe Installation and User Guide.
The Status/Discovery process uses the debugging file $SVHOME/parm/svdebug.parm to determine the level of debugging to use. If the file does not exist, if it has incorrect permissions assigned, or if SVSTATUS is not a valid debugging process name, the pu_status_manager process will exit with the following errors:
SVINI040 Error setting debug value, unable to find module Pu_status_manager in Pu_status_manager.
SVEXE102 Pu_status_manager process of domain [domain] has exited.
Users can issue mainframe commands from the SNA View Mainframe Commands window, and SNA View can issue mainframe commands in response to menu items selected from CiscoWorks Blue Maps menus. This section discusses solutions to potential problems in the following sections:
If a mainframe command client is unable to register with the Host Command Server, the following error message is displayed in a popup window:
SVSRV050 Timed out waiting for registration response.
When SNA View issues the mainframe command, error messages are written to standard error (on the console where the management platform was launched) and to the Command Response Display window. These messages are shown below.
Console Example:
SVSRV050 Timed out waiting for server registration response.
SVSRV070 Verify that the HCI and Command Servers are active.
SVEXE102 svhost_cmd process of domain [domain name] has exited.
Command Response Display Example:
SVSRV055 Timed out waiting for command response from Command Server.
SVSRV071 Command not processed. Verify that the HCI and Command Servers are active.
There are three possible reasons why the mainframe command client cannot register with the Host Command Server.
To correct the problem, use the following procedure:
Step 1 Verify that the Host Command Server is active for the desired domain. If it is not, start the Host Connection Interface and Host Command Server for that domain.
Step 2 Verify the configuration parameters mentioned above. See the section "Configuration File Problems" for details on the SVCMDS_AGENT_ADDR and SVCMD_AGENT_PORT configuration parameters.
Step 3 If you determine that the Host Command Server is running and the configuration parameters are set correctly, but the command client will still not register successfully, stop and restart the Host Connection Interface and Host Command Server for this domain.
If, after entering your user ID and password and clicking OK on the Mainframe Logon window, you receive an "Invalid User ID" or an "Invalid Password" message, then verify your user ID and password and try to log in again. If you are still unable to log in, call your mainframe system administrator. There will be messages with ICH408I and IRR013I message IDs on the mainframe console. Those messages will help you diagnose the problems with your user ID and password.
If, after entering your user ID and password and clicking OK on the Mainframe Logon window, the response is a "Verifying...please wait" message that is displayed for an unusually long period, verify that the SEC subtask has been started on the mainframe. If the SEC subtask is not running, you will be unable to log in to issue mainframe commands. Restart the SEC subtask and then retry the Mainframe Commands window.
Commands issued through the SNA View menus rely on the SVCMD_TIMEOUT configuration parameter to specify the number of seconds that the workstation will wait for a response from the mainframe. If this time is exceeded, error messages will be written to standard error (the console where the network management was launched) and to the Command Response Display window. These error messages are shown below.
Console Example:
SVSRV055 Timed out waiting for command response from Command Server.
SVSRV070 Verify that the HCI and Command Servers are active.
SVEXE102 svhost_cmd process of domain [domain name] has exited.
Command Response Display Example:
SVSRV055 Timed out waiting for command response from Command Server.
SVSRV071 Command not processed. Verify that the HCI and Command Servers are active.
See the information about the SVCMD_TIMEOUT configuration parameter, in the section "Configuration File Problems," for details.
The Mainframe Command window will wait indefinitely for command responses from the mainframe. There is no timeout period, but if command responses are very slow, or if only partial command responses are returned, there may be a problem with the performance group setting for the mainframe task. See the SNA View Mainframe system administrator or installer to correct the performance group setting.
The following situation can arise when you issue VTAM commands from SNA View.
If the following message is received, VTAM did not recognize the mainframe command issued:
IST010I XXX COMMAND INVALID
Verify the syntax of the command that you are attempting to issue and try again. See IBM's VTAM Operations Guide for the syntax for specific commands.
The following situations can arise when you issue NetView commands.
If no command responses are returned for NetView commands issued, verify that the PPI subtask is active on the mainframe. The PPI subtask is responsible for processing NetView commands issued through SNA View. See the CiscoWorks Blue SNA View Mainframe Installation and User Guide or your system administrator for details on determining whether the PPI subtask is active.
The mainframe component will return an "SV315" message when the command operator specified by the SVCMD_OPERATOR configuration parameter is invalid.
For example, if SVCMD_OPERATOR was set to the value "OPERATOR1," but OPERATOR1 is not a valid NetView operator ID and is not currently logged in, then the SV315 message would be displayed as follows:
SV315 OPERATOR1 COMMAND EXECUTION FAILED
See the "Configuration File Problems" section in this chapter for details about the SVCMD_OPERATOR configuration parameter.
This section discusses potential problems that relate to the receipt of unsolicited mainframe messages; it contains the following sections:
You may experience the following problems when you try to receive unsolicited VTAM messages.
If the VTAM Messages Client window does not appear successfully, review the error messages issued by the process to standard error. Also, see the "General Problems" section for details and possible solutions.
If the VTAM Messages Client window appears, but times out while attempting to register with the VTAM Server, the following error message will appear in a Timeout Notification window:
SVSRV050 Timed out waiting for server registration response
If you receive this message, either the VTAM Server is not running properly or the SVVTAM_AGENT_ADDR and SVVTAM_AGENT_PORT configuration parameters are not set correctly. Verify that the VTAM Server is running on the proper machine. If it is, see the "Configuration File Problems" section in this chapter for details about the SVVTAM_AGENT_ADDR and SVVTAM_AGENT_PORT configuration parameters.
If the VTAM Message client is not receiving VTAM messages from the VTAM Server, verify that VTAM is currently generating messages at the mainframe.
When SNA View is running on the mainframe with NetView or SOLVE:Netmaster, the PPI subtask must be active for SNA View to receive unsolicited VTAM messages. If NetView or SOLVE:Netmaster is not running, the PPO subtask must be active to receive VTAM messages. To verify that the correct SNA View subtask is active on the mainframe, call your mainframe system administrator.
It is also possible that the mainframe, workstation server, or workstation client message filters are filtering out VTAM messages before they reach the VTAM Message client. The VTAM Server will forward to clients only the VTAM messages that are received from the mainframe and that are not eliminated by the message filters specified in the
$SVHOME/parm/svvtamsysfilter.tbl file. Verify that the contents of this file have not been set in such a way as to filter out the VTAM messages you are expecting. Similarly, client filters set up on the VTAM Messages window itself may be filtering out the messages you are expecting.
When either NetView or SOLVE:Netmaster is installed, SNA View receives VTAM messages from the network management system. Have the mainframe administrator verify that NetView or SOLVE:Netmaster has been configured properly to forward VTAM messages to SNA View.
Finally, verify that the SNA View MESSAGES parameter is set correctly on the mainframe.
You may experience the problems described below when you try to receive unsolicited MVS messages.
If the MVS Messages Client window does not appear successfully, review the error messages issued by the process to standard error. Also, see the section "General Problems" for details on possible solutions.
If the MVS Messages window appears but then times out while attempting to register to the MVS Server, the following error message will appear in a Timeout Notification popup window:
SVSRV050 Timed out waiting for server registration response
When this occurs, either the MVS Server is not running properly or the SVMVS_AGENT_ADDR or SVMVS_AGENT_PORT configuration parameters are not set correctly. Verify that the MVS Server is running on the correct machine and see the "Configuration File Problems" section for details about the SVMVS_AGENT_ADDR and SVMVS_AGENT_PORT configuration parameters.
When the MVS Message client is not receiving any MVS messages from the MVS Server verify that MVS is currently generating messages on the mainframe.
The MVS subtask of the SNA View mainframe program must be active to receive unsolicited MVS messages. Verify that the MVS subtask is active by calling your mainframe system administrator.
Message filters on the mainframe and on the workstation may be filtering out MVS messages before they reach the MVS Message client. The MVS Server will forward only MVS messages that are not filtered out by the message filters in the
$SVHOME/parm/svmvssysfilter.tbl file. Verify that the contents of this file have not been set in such a way as to filter out the MVS messages you are expecting. Similarly, message filters set in the MVS Client window itself may be filtering out the messages you are expecting.
Finally, verify that the SNA View MESSAGES parameter is set correctly on the mainframe.
This section highlights problems that are not specific to any single component of SNA View. This section contains the following sections:
File permission problems sometimes arise during the operation of SNA View. One such problem occurs when SNA View is initially run under the root user authority. SNA View processes open files with write permission for various reasons; log files and temporary work files are two of the most common. An example is the Status/Discovery process, which opens a file in SNA View's temporary work directory, specified by the configuration parameter SVWORK_AREA (the default value of SVWORK_AREA is
$CWBROOT/snaview/tmp).
If the Status/Discovery process is originally run under the root username, and later run under a different username, SNA View issues the following error message:
sh:/usr/cw-blue/snaview/tmp/discovery.domain: cannot create
In this example, the Status/Discovery process was unable to obtain write authority for the necessary file, so the process exited. Removing all files from the SVWORK_AREA directory would correct the problem.
Table 6-3 lists the files created by each process.
| Process | Files Created |
|---|---|
| Host Command Interface | version.domain |
| Status/Discovery | discovery.domain, pudata.domain |
As mentioned previously, many SNA View processes also open log files in the $SVHOME/log directory. Table 6-4 lists those processes and the names of the log files they open.
| Process | Associated Log File |
|---|---|
| VTAM Server | svvtam.log.domain |
| MVS Server | svmvs.log.domain |
| VTAM Message Log | svmessage_log.domain |
| MVS Message Log | svmvs_message_log.domain |
For an SNA View process to function as expected, all of the configuration parameters that it uses must be available and set correctly. Attempting to kill a process that was started by another user will also fail due to process permissions. Table 6-5 lists the parameter files referenced by each of the SNA View processes. All SNA View parameter files reside in the $SVHOME/parm directory unless otherwise specified in Table 6-5 to be in a subdirectory of $SVHOME/parm.
| Process | Parameter Files Referenced |
|---|---|
| All processes | /etc/svopen_config_domain |
| Host Connection Interface | svdebug.parm |
| Host Command Server | svdebug.parm |
| VTAM Server | svdebug.parm
svvtamsysfilter.tbl |
| MVS Server | svdebug.parm
svmvssysfilter.tbl |
| Status/Discovery process | svdebug.parm |
| Check Status Process | svdebug.parm |
| VTAM Message Log | svdebug.parm |
| MVS Message Log | svdebug.parm |
| Mainframe Commands Window | svdebug.parm |
| VTAM Messages Window | svdebug.parm |
| MVS Messages Window | svdebug.parm |
| Command Client Process | svdebug.parm |
Whether you start SNA View from the Maps Tools menu or with the runsnaview command, the SVHOME environment variable is set automatically to the SNA View home directory; for example, /usr/cw-blue/snaview. It is used by many SNA View processes to find the correct path to the SNA View parm, help, and log directories.
In general, if SNA View is unable to locate specific files that it requires, check the setting of the SVHOME environment variable first.
SNA View configuration file errors are common sources of SNA View failures. Each managed SNA View domain has a configuration file in the /etc directory. Each domain configuration filename is in the format svopen_config_ domain. These configuration files contain parameters that affect almost every aspect of SNA View functionality. Several configuration file parameters, if not set correctly, can keep SNA View processes from executing properly.
The following sections describe the configuration file parameters and the problems that can arise if they are not set correctly.
SVPATH is the path to the SNA View home directory (such as /usr/cw-blue/snaview).
If this variable is not properly set to SNA View's home directory, as defined during installation, workstation processes will not be able to locate necessary help, log, and parameter files. Most SNA View workstation processes will not initialize without a valid SVPATH parameter value.
For example, if the SVPATH variable is not set correctly, when the Status/Discovery process is started, the following error messages will be written to standard error (usually the display):
SVEXE010 Set_Debug_Flag2() failed to open file svpath/parm/svdebug.parm, reason: No such file or directory.
SVINI040 Error setting debug value, unable to find module
SVSTATUS in Status Manager.
SVEXE102 Status Manager process of domain [DOMAIN1] has exited.
To prevent this problem, set the SVPATH parameter to SNA View's home directory.
SVVTAM_AGENT_ADDR is the host name of the workstation running the VTAM Server.
If this variable is not properly set to the machine name of the workstation on which the VTAM Server will be running, the VTAM Message Log and VTAM Window clients will not be able to register to receive unsolicited VTAM messages.
For example, if the value of this variable is mickey, but mickey is not a valid machine in the network, the following error messages will be written to standard error:
SVEXE002 client_bind_udp_socket() failed calling gethostbyname(), reason: Error 0.
SVEXE031 Unable to obtain host TCP/IP address from host name: mickey
SVEXE100 client_bind_udp_socket() process has exited.
If, however, mickey is a valid machine name, but the VTAM Server is not currently running on that machine, the following error message will be generated either to standard error if running the VTAM Message Log, or in a Motif popup if starting the X VTAM Window:
SVSRV050 Timed out waiting for server registration response.
SVMVS_AGENT_ADDR is the device name of the workstation running the MVS Server.
If this configuration parameter is not properly set to the machine name of the workstation on which the MVS Server will be running, the MVS Message Log and MVS Window clients will not be able to receive unsolicited MVS messages.
For example, if the value of this configuration parameter is mickey, but mickey is not a valid machine in the network, the following error messages will be written to standard error:
SVEXE002 client_bind_udp_socket() failed calling gethostbyname(), reason: Error 0.
SVEXE031 Unable to obtain host TCP/IP address from host name: mickey
SVEXE100 client_bind_udp_socket() process has exited.
If, however, mickey is a valid machine name, but the MVS Server is not currently running on that machine, the following error message will be generated either on standard error or in a Motif popup window:
SVSRV050 Timed out waiting for server registration response.
SVCMDS_AGENT_ADDR is the machine name of the workstation running the Command Server.
If this configuration parameter is not properly set to the machine name of the workstation on which the Command Server will be running, the Command Window client and Host Command client processes will not be able to receive mainframe command support.
For example, if the value of this configuration parameter is mickey, but mickey is not a valid machine in the network, these error messages will be written to standard error:
SVEXE002 client_bind_udp_socket() failed calling gethostbyname(), reason: Error 0.
SVEXE031 Unable to obtain host TCP/IP address from host name: mickey
SVEXE100 client_bind_udp_socket() process has exited.
If, however, mickey is a valid machine name, but the Command Server is not currently running on that machine, the following error message will be generated either on standard error if running the Mainframe Command client, or in a Motif popup window if starting an X Command Window client:
SVSRV050 Timed out waiting for server registration response.
SVHCI_AGENT_ADDR is the machine name of the workstation running the Host Connection Interface.
If this configuration parameter is not properly set to the device name of the workstation on which the Host Connection Interface is running, the Host Command Server, VTAM and MVS Servers as well as the Status/Discovery process will be unable to establish socket communications with the Host Connection Interface.
For example, if the value of this configuration parameter is mickey, but mickey is not a valid machine on the network, the following error messages will be written to standard error when you attempt to start any of the processes named above:
SVEXE002 client_bind_udp_socket() failed calling gethostbyname(), reason: Error 0.
SVEXE031 Unable to obtain host TCP/IP address from host name: mickey
SVEXE100 client_bind_udp_socket() process has exited.
If, however, mickey is a valid machine name but the Host Connection Interface is not currently running on that machine, the following error messages are written to standard error:
SVSOK001 server_connect_tcp_socket() failed calling connect(), reason: Connection refused
SVSOK051 Socket connect failed, no retry will be attempted.
SVEXE100 server_connect_tcp_socket() process has exited.
SVMF_AGENT_ADDR is the machine name of the IBM mainframe running SNA View.
If this configuration parameter is not properly set to the machine name of the IBM mainframe running SNA View, the Host Connection Interface and the Host Command Server will not successfully initialize when using TCP/IP for communications between mainframe and workstation.
For example, if the value of this configuration parameter is mickey, but mickey is not a valid machine on the network, you will get the following error messages written to standard error when you attempt to start the Host Connection Interface or Host Command Server:
SVEXE002 client_bind_udp_socket() failed calling gethostbyname(), reason: Error 0.
SVEXE031 Unable to obtain host TCP/IP address from host name: mickey
SVEXE100 client_bind_udp_socket() process has exited.
If, however, mickey is a valid machine name, but the TCP subtask of the mainframe component is not currently running, you will receive these error messages on standard error:
SVSOK001 server_connect_tcp_socket() failed calling connect(), reason: Connection refused
SVSOK051 Socket connect failed, no retry will be attempted.
SVEXE100 server_connect_tcp_socket() process has exited.
Similar error messages will also be generated if the SVMF_HCI_AGENT_PORT and SVMF_CMDS_AGENT_PORT values are not set properly. These configuration parameters must match the ports defined on the SNA View mainframe program's TCP parameter card. See the CiscoWorks Blue SNA View Mainframe Installation and User Guide for more details.
SVCMD_TIMEOUT is the timeout period, in seconds, for mainframe commands.
If this configuration parameter is set too low, then mainframe commands issued from the workstation can time out. Try to increase this parameter value.
The default value of this configuration parameter is 30 seconds. In most cases this value is sufficient. However, when the workstation-to-mainframe connection is very slow, you might need to increase this value. If this configuration parameter is set too low, the following error messages will be issued to standard error:
SVSRV055 Timed out waiting for command response from Command Server.
SVSRV071 Command not processed. Verify that the HCI and Command Servers are active.
If increasing this configuration parameter does not prevent commands from timing out, ensure that the Host Connection Interface and Host Command Server are active. If they are inactive, activate them. If they are active, check the SNA View mainframe performance group, which may be set too low. See your mainframe system administrator or see the CiscoWorks Blue SNA View Mainframe Installation and User Guide for assistance.
SVCMD_OPERATOR is a valid NetView operator ID.
If this configuration parameter is not set to a valid NetView operator ID, NetView commands issued from the Command Client window will fail.
SVWORK_AREA is a valid system directory where SNA View will store work files.
If this configuration parameter is not set to a valid system directory, various SNA View processes will not initialize successfully or run properly. SNA View processes utilize this temporary directory to store various files necessary during normal operation. These files and the processes that create them are described in greater detail in the "Authority and Access Problems (Permissions)" section of this chapter.
The SNA View server and client processes use these port values for socket communications. Ensure that the port is not used twice, and that it is not used by some other process.
The Host Connection Interface communicates with the VTAM and MVS Servers, and the Status/Discovery process, over these defined ports. Ensure that the port is not used twice, and that it is not used by some other process.
These configuration parameters define the port values used for TCP/IP communications between the workstation and mainframe components of SNA View. The Host Connection Interface and Host Command Server use these port values to establish socket communications with the TCP subtask on the mainframe. The port values specified in the configuration file on the workstation must match those defined on the TCP subtask parameter card in the mainframe component's SYSIN parameter card file. See the CiscoWorks Blue SNA View Mainframe Installation and User Guide for more information on the TCP subtask and SYSIN parameter card file.
If these configuration parameters do not match those defined on the mainframe, SNA View will generate the following error messages on standard error when starting the Host Connection Interface and Host Command Server:
SVSOK001 server_connect_tcp_socket() failed calling connect(), reason: Connection refused.
SVSOK051 Socket connect failed, no retry will be attempted.
SVEXE100 server_connect_tcp_socket() process has exited.
This section explains the messages generated by the SNA View workstation program.
The messages in this section are organized in the following sections:
Explanation An SNA View server process detected an out of sequence message from a client process and issued this notification.
Recommended Action No user action is required.
Error Message SVCLI020 client received invalid RACF return: rcnumberclient is the SNA View client.
rcnumber is the integer return code.
Explanation An SNA View client that requires a mainframe RACF login, supplied by the user, submitted a username and password that failed to pass RACF. The SNA View client must exit.
Recommended Action Ensure that the username and password are valid for RACF on the mainframe for the domain in which the client was running.
Error Message SVCLI030 Invalid command form specified, valid values are 1, 2 or 3.Explanation An SNA View command client was provided an invalid command form. Command client process will terminate.
Recommended Action Specify one of the valid command form values specified below:
process is the SNA View process or function.
function is the function.
Explanation An SNA View process or function has failed in its call to a function. In most cases the SNA View process or function will terminate.
Recommended Action Normally, more detailed SNA View error messages will accompany this message. Review all SNA View generated error messages in an effort to resolve the error.
Error Message SVEXE001 process failed calling function with rc: rcnumberprocess is the SNA View process or function.
function is the function.
rcnumber is the integer return code.
Explanation An SNA View process or function has failed in its call to a function and received a return code. In most cases, the SNA View process or function will terminate.
Recommended Action Normally, more detailed SNA View error messages will accompany this message. Review all SNA View generated error messages in an effort to resolve the error.
Error Message SVEXE002 process failed calling function, reason: messageprocess is the SNA View process or function.
function is the function.
message is the text of the error message.
Explanation An SNA View process or function has failed in its call to a function and received an error message. Usually, the SNA View process or function will terminate.
Recommended Action Normally, more detailed SNA View error messages will accompany this message. Review all SNA View generated error messages.
Error Message SVEXE010 process failed to open file path, reason: messageprocess is the SNA View process or function.
path is the full file path, including the filename.
message is the text of the error message.
Explanation An SNA View process or function has failed to open a file and received an error message. The SNA View process that detected the error will terminate.
Recommended Action Check file permissions to ensure that the process has the ability to read and write to the file.
Error Message SVEXE015 process failed to obtain file statistics for file name, reason: failure.process is the SNA View process.
name is the filename.
failure is the text describing the failure.
Explanation An SNA View process attempted to query statistical information for a file. The query failed, and text describing the failure was returned. In most cases the process will terminate.
Recommended Action Use text describing the failure to determine cause of the failure and correct the problem.
Error Message SVEXE020 Memory allocation failure, check available memory.Explanation An SNA View process attempted to obtain more memory from the operating system and failed. The SNA View process that detected the error will terminate.
Recommended Action Verify that available memory requirements on the workstation have not been exceeded.
Error Message SVEXE031 Unable to obtain host TCP/IP address from host name: host.host is the TCP/IP host name.
Explanation An SNA View process attempted to get the TCP/IP address for the TCP/IP host machine and failed. The SNA View process that detected the error will terminate.
Recommended Action If the machine uses the /etc/hosts file to resolve TCP/IP addresses, make certain that the specified host name has an entry. If the machine uses a name server to resolve addresses, verify that the name server knows the host name.
Error Message SVEXE100 process_name process has exited.process_name is the SNA View process that exited.
Explanation An SNA View process has terminated.
Recommended Action Review any SNA View generated error messages to determine the cause of the process termination if the termination was abnormal.
Error Message SVEXE102 process_name process of domain name has exited.process_name is the SNA View process that exited.
name is the SNA View defined domain name.
Explanation An SNA View process of a domain has terminated.
Recommended Action Review any SNA View generated error messages to determine the cause of the process termination if the termination was abnormal.
Error Message SVEXE110 process_name popen failed calling name: exiting.process_name is the SNA View process.
name is the program launched by the popen() system call.
Explanation An SNA View process attempted to issue the popen() system call to launch a program and failed. The SNA View process will fail.
Recommended Action Ensure that the program exists in the specified path and that its permissions allow the process to execute it.
Error Message SVEXE130 Invalid buffer received from status process by GUI.Explanation The SNA View Task Manager received an invalid response from the SNA View Status/Discover process.
Recommended Action Call the Cisco TAC for instructions.
Error Message SVEXE140 Status and/or Discover task not active on mainframe.Explanation The Status and/or Discovery subtasks on the mainframe are not running. No SNA correlation information is being sent to the workstation.
Recommended Action Ensure that the SNA View mainframe STATUS and DISCOVERY subtasks are configured and active.
number is the line number in the system message filter table file where the error was detected.
type is VTAM or MVS.
Explanation The VTAM Message Server or MVS Message Server encountered a problem with the system filter table file at the specified line number. The SNA View process that detected the error will terminate.
Recommended Action Edit the appropriate system filter table file located in
$SVHOME/parm and make the appropriate corrections.
number is the line number where the error was detected.
Explanation The VTAM Message Server or MVS Message Server encountered a problem with a filter table, requested by the client, at the specified line number.
The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Correct the client filter table and reissue the filter request.
Error Message SVFIL010 Filter Format: statement.statement is the correct format of the filter statement.
Explanation The VTAM Message Server or MVS Message Server detected a problem with the format of a filter statement. The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Correct the format of the filter statement and reissue the filter request.
Error Message SVFIL011 First character of filter entry must be an 'I' or 'X'.Explanation The VTAM Message Server or MVS Message Server detected that the first character of a client filter statement is not an I or X. The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Correct the format of the filter statement and reissue the filter request. Filter statements must begin with an I for Include or an X for eXclude.
Error Message SVFIL012 Invalid token position encountered (must be in range 1 to 99): position.position is the invalid token position.
Explanation The VTAM Message Server or MVS Message Server detected an invalid token position within a requested filter statement. The largest valid token position is 99; the smallest is 1. The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Select a valid token position, correct the filter statement, and reissue the filter request.
Error Message SVFIL013 Incomplete comparison token pair.Explanation The VTAM Message Server or MVS Message Server detected an incomplete comparison token pair within a requested filter statement. The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Correct the format of the filter statement and reissue the filter request.
Error Message SVFIL014 Invalid DEFAULT entry.Explanation The VTAM Message Server or MVS Message Server detected an invalid DEFAULT filter entry. The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Correct the format of the DEFAULT filter statement and reissue the filter request.
Error Message SVFIL015 Filter entry must not contain over 19 tokens.Explanation The VTAM Message Server or MVS Message Server detected that a filter statement contains more that the maximum of 19 tokens. The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Correct the format of the filter statement and reissue the filter request.
Error Message SVFIL016 Invalid number of comparison tokens in relation to operators.Explanation The VTAM Message Server or MVS Message Server detected that a filter statement contained an invalid number of comparison tokens in relation to logical operators. The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Correct the format of the filter statement and reissue the filter request.
Error Message SVFIL017 Filter entries have a maximum length of 80 characters.Explanation The VTAM Message Server or MVS Message Server detected that a filter statement exceeded the maximum length of 80 characters. The detecting SNA View server process will return an error message to the client process and continue execution.
Recommended Action Correct the format of the filter statement and reissue the filter request.
process_name is the SNA View process.
name is the SNA View defined domain name.
Explanation An SNA View process has initialized successfully for the domain. The SNA View process will continue with execution.
Recommended Action No user action is required.
Error Message SVINI010 process_name started with invalid argument count.process_name is the SNA View process.
Explanation An SNA View process was started without the incorrect number of command line arguments. The SNA View process will terminate.
Recommended Action If you started this process from the command line, verify that you entered the correct options. If you have entered the correct options, notify the Cisco TAC.
Error Message SVINI011 Domain name must be passed in to the process_name.process_name is an SNA View process.
Explanation An SNA View process was started without the domain name passed as an argument. The SNA View process requires the domain name argument to determine the proper configuration file to use. The SNA View process will terminate.
Recommended Action If you started this process from the command line, verify that you entered the correct options. If you have entered the correct options, notify the Cisco TAC.
Error Message SVINI012 Invalid transaction program name executable used to startExplanation The Host Command Interface was started with an invalid transaction program name. The transaction program name did not have the domain name (for which the servers are being started) appended to the executable name. The SNA View process that detected this failure will terminate.
Recommended Action When communication between the mainframe and the workstation is via LU 6.2, the configuration profiles on the workstation must be defined so that the transaction program executable paths for the Host Command Interface server and Host Command server have the proper domain name appended. The Host Command Interface server and Host Command server use this appended domain name to access the appropriate SNA View configuration files.
Error Message SVINI013 Resource name with domain extension must be passed in to the process.process is the SNA View process.
Explanation The SNA View process requires that a resource name with a proper domain extension be passed in on the command line. The SNA View process that detected this failure will terminate.
Recommended Action Restart the SNA View process using the complete resource name.
Error Message SVINI020 process encountered invalid value for configuration parameter parameter_nameprocess is the SNA View process.
parameter_name is the SNA View configuration parameter.
Explanation An SNA View process was started but the specified configuration parameter is set incorrectly. The specified configuration parameter is critical to the operation of the process. The SNA View process that detected this failure will terminate.
Recommended Action Set the configuration parameter with the proper value and restart the process.
Error Message SVINI030 process needs the variable environment variable set properly.process is the SNA View process.
variable is the SNA View environment variable.
Explanation An SNA View process was started without the environment variable set. The specified environment variable is critical to the operation of the process. The SNA View process that detected this failure will terminate.
Recommended Action Set the environment variable with the proper value and restart the process.
Error Message SVINI040 Error setting debug value, unable to find module name in file.name is the SNA View debugging module name.
file is the debugging parameter file.
Explanation An SNA View process was unable to determine the value of its debugging flag because the module name was not found in the debugging parameter file. The SNA View process that detected the error will exit.
Recommended Action Add the SNA View module name to the debugging parameter file $SVHOME/parm/sv-debug.parm.
process_name is the SNA View process or routine.
name is the LU 6.2 system routine name.
re_number is the error return.
Explanation The SNA View process or routine failed calling the LU 6.2 system routine and returned an error code. The SNA View process that detected the error will terminate.
Recommended Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
Error Message SVLUX010 Failure opening direction LU 6.2 conversation.direction is inbound or outbound.
Explanation The Host Command Interface or the Host Command Server failed to open the LU 6.2 conversation with the mainframe system. The SNA View process that detected the error will terminate.
Recommended Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
Error Message SVLUX020 Failure allocating direction LU 6.2 conversation.direction is inbound or outbound.
Explanation The Host Command Interface or the Host Command Server failed to allocate the LU 6.2 conversation with the mainframe. The SNA View process that detected the error will terminate.
Recommended Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
Error Message SVLUX030 Failure reading over direction LU 6.2 conversation.direction is inbound or outbound.
Explanation The Host Command Interface or the Host Command Server failed to read from the LU 6.2 connection that exists between it and the mainframe code. The SNA View process that detected the error will terminate.
Recommended Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
Error Message SVLUX035 Control received value from mainframe signals termination.Explanation The Host Connection Interface or Host Command Server process received a code format value from the mainframe, indicating that termination was necessary. The detecting SNA View server process will terminate.
Recommended Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
Error Message SVLUX040 Failure confirming conversation LU 6.2 conversation read.conversation is the inbound or outbound conversation.
Explanation The Host Command Interface or the Host Command Server failed to confirm that the conversation was read as requested by the mainframe program. The SNA View process that detected this failure will terminate.
Recommended Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 communications are configured properly.
Error Message SVLUX050 Failure sending over conversation LU 6.2 conversation.conversation is the inbound or outbound conversation.
Explanation The Host Command Interface or the Host Command Server detected a failure while attempting to send over the LU 6.2 conversation with the mainframe. The SNA View process that detected this failure will terminate.
Recommended Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 SNA profiles are configured properly.
Error Message SVLUX060 Failure closing conversation LU 6.2 conversation.conversation is the inbound or outbound conversation.
Explanation The Host Command Interface or the Host Command Server detected a failure while attempting to close the LU 6.2 conversation with the mainframe. The SNA View process that detected this failure will terminate.
Recommended Action Review any LU 6.2 communication errors generated in the mainframe's system log or the workstation's SNA stack error logs. Verify that your LU 6.2 SNA profiles are configured properly.
process is the SNA View process or routine.
function is the system socket function.
explanation is the text that explains the error.
Explanation An SNA View process has called a system function and that function has failed. The reason is given in the explanation field. In most cases, a system function that is essential to the process is missing. Without it, the process cannot continue and will exit with an error.
Recommended Action If the explanation is not clear, check to make sure the configuration file for that particular domain is defined correctly. In some cases, the error may be due to the system load, and the process will run properly if restarted.
Error Message SVSOK010 Unable to open protocol method socket.protocol is the socket protocol.
method is either the stream or datagram method.
Explanation An SNA View process was unable to open a socket type with the indicated communication method. The SNA View process that attempted to open the socket will terminate.
Recommended Action In some cases, the error is due to the system load, and the process will run properly if restarted.
Error Message SVSOK020 Unable to bind socket.Explanation An SNA View process was unable to bind an open socket. The SNA View process that attempted to bind the socket will terminate.
Recommended Action In some cases, the error is due to the system load, and the process will run properly if you restart it.
Error Message SVSOK030 Unable to set socket to non-blocking mode.Explanation An SNA View process was unable to set the mode of a socket to nonblocking. Processing continues.
Recommended Action No user action is required.
Error Message SVSOK040 Error on listen for socket connection.Explanation An SNA View process was unable to activate a socket for connection. The SNA View process that attempted to listen for the socket connection will terminate.
Recommended Action In some cases, the error is due to the system load, and the process will run properly if restarted.
Error Message SVSOK050 Socket connect failed, will retry momentarily.Explanation An SNA View process attempted to connect to another SNA View process via socket communications and failed. In most cases, the other SNA View process has not had enough time to initialize and establish the socket properly. The process will wait momentarily and then reissue the connection attempt.
Recommended Action No user action is required.
Error Message SVSOK051 Socket connect failed, no retry will be attempted.Explanation An SNA View process attempted to connect to another SNA View process via socket communications and failed. The SNA View process that detected the error will terminate.
Recommended Action Make sure that both processes involved in the connection are executing. Make sure the configuration file for that particular domain is correctly defined. In some cases, the error is due to the system load, and the process will run properly if restarted.
Error Message SVSOK070 Unable to get socket option: socket.socket is the specific socket option.
Explanation An SNA View process attempted to obtain the socket option and failed. The SNA View process that detected the error will terminate.
Recommended Action Attempt to restart the failing process.
Error Message SVSOK071 Unable to set socket option: socket.socket is the specific socket option.
Explanation An SNA View process attempted to set the socket option and failed. The SNA View process that detected the error will terminate.
Recommended Action Attempt to restart the failing process.
Error Message SVSOK080 process_name failed reading HCI socket, reason: explanation.process_name is the SNA View server process.
explanation is text that explains the error.
Explanation An SNA View server attempted to read from the Host Command Interface and failed. The SNA View server will notify its clients and then terminate.
Recommended Action Verify that the Host Command Interface server is active. In some cases, the error is due to the system load, and the process will run properly if restarted.
Error Message SVSOK081 Failure reading process_name client UDP socket.process_name is the SNA View client process name.
Explanation SNA View server process failed while reading a client's socket. The SNA View server process will terminate.
Recommended Action In some cases, the error is due to the system load, and the process will run properly if restarted.
Error Message SVSOK082 Failure reading process_name server UDP socket, number bytes returned is zero.process_name is the SNA View server process.
Explanation An SNA View client process attempted to read from an SNA View server process and received 0 bytes of data. The detecting SNA View client process will terminate.
Recommended Action Verify that the client's server process is still active and functioning properly. In some cases, the error is due to the system load, and the process will run properly if restarted.
Error Message SVSOK083 Failure reading process_name server UDP socket, entire message not received.process_name is the SNA View server process.
Explanation An SNA View client process attempted to read from an SNA View server process and received only a partial message. The detecting SNA View client process will terminate.
Recommended Action Verify that the client's server process is still active and functioning properly. In some cases, the error is due to the system load, and the process will run properly if restarted.
Error Message SVSOK090 Failure writing to process_name client UDP socket.process_name is the SNA View client process.
Explanation An SNA View server process failed while writing data to an SNA View client process. A server process will continue processing if a write to a client process fails.
Recommended Action Verify that the client process is still active and, if not, restart the client process repeating the desired action.
Error Message SVSOK092 Failure writing to process_name client UDP socket, entire message not sent.process_name is the SNA View client process.
Explanation An SNA View server process failed to send the entire data buffer to an SNA View client process. A server process will continue processing if a write to a client process fails.
Recommended Action Verify that the client process is still active and, if not, restart the client process.
Error Message SVSOK199 Failure reading SView/Open Mainframe Message Server, reason: explanation.explanation is text that explains the error.
Explanation The SNA View Host Connection Interface failed while attempting to read from its socket connection with the SNA View Mainframe Message Server. The Host Connection Interface server will exit, causing the termination of the majority of all SNA View processes.
Recommended Action Review text explanation of the error and verify TCP/IP support between the workstation and the mainframe in question.
Error Message SVSOK200 Lost connection with SView/Open Mainframe Message Server.Explanation The SNA View Host Connection Interface lost connection with the SNA View Mainframe Message Server. This message indicates that some vital process or processes on the mainframe have terminated or become unavailable. The Host Connection Interface server will exit, causing the termination of the majority of the SNA View processes.
Recommended Action Verify the status of SNA View on the mainframe and the TCP/IP support.
Error Message SVSOK201 process_name has exited due to read failure on HCI connection.process_name is the SNA View server process.
Explanation An SNA View server process exited because it received an error return code when it attempted to read from the Host Connection Interface socket. SNA View server process will terminate.
Recommended Action Verify that the Host Connection Interface for that domain is active.
Error Message SVSOK202 process_name has exited due to loss of connection with the HCI.process_name is the SNA View server process.
Explanation An SNA View server process exited because it lost connection with the Host Connection Interface. This indicates that the Host Connection Interface process has terminated and is no longer available. SNA View server process will terminate.
Recommended Action Verify that the Host Connection Interface for that domain is active.
Error Message SVSOK203 process_name has exited due to loss of connection with the Command Server.process_name is the SNA View command client process.
Explanation The SNA View command client process has been forced to terminate because it lost connection with its Host Command Server process. The process will terminate.
Recommended Action Review any accompanying SNA View error messages for the exact cause of the loss of connection. Verify that the Host Command Server for the client process is still active and functioning properly.
Error Message SVSOK220 HCI failed sending command response to the Command Server.Explanation The Host Connection Interface could not send the response, to a mainframe command, back to the Host Command Server.
Recommended Action Ensure that the Host Command Server process is active on the workstation. If it is not active, start it. If it is active, stop it and restart it.
process1 is an SNA View process.
process2 is an SNA View process.
type is the message type.
Explanation An SNA View process received an invalid message type from another SNA View process. The invalid message will be ignored, and processing will continue.
Recommended Action If message persists, note message contents and contact the Cisco TAC.
Error Message SVSRV010 process has exited due to kill/term signal.process is the SNA View server process.
Explanation An SNA View server process has been terminated by a KILL command.
The SNA View server process will notify any registered clients of its termination.
Recommended Action Restart the server process when ready.
Error Message SVSRV020 Client is not currently registered, filter request rejected.Explanation A client process attempted to send a filter request to an SNA View server process to which the client process was not properly registered. The filter request was rejected for this reason by the server. The server process will reject the client process's filter request.
Recommended Action No user action is required.
Error Message SVSRV021 Client is not currently registered, command not submitted to mainframe.Explanation A client process attempted to send a mainframe command to the SNA View Host Command Server process to which the client process was not properly registered. Host Command Server will reject the client's mainframe command request.
Recommended Action No user action is required.
Error Message SVSRV030 Maximum number of clients already registered, request rejected.Explanation An SNA View client process attempted to register with an SNA View server process, but the server process already had the maximum number of 100 clients it was permitted to serve. The SNA View server process rejected the client's request. The server process will reject the client's register request.
Recommended Action No user action is required.
Error Message SVSRV050 Timed out waiting for server registration response.Explanation An SNA View client process issued a registration request to its server process and no registration response has been received by the client in the provided time. SNA View client will either continue to wait or exit depending upon the user action chosen.
Recommended Action You can continue waiting for the registration response or exit the SNA View client process. Verify that the proper SNA View server process is active and that the SNA View configuration parameters for the appropriate domain are correct.
Error Message SVSRV055 Timed out waiting for command response from Command Server.Explanation An SNA View client process issued a registration request to the Host Command Server process and no registration response has been received by the client in the provided time. SNA View client will either continue to wait or exit depending upon the user action chosen.
Recommended Action Verify that the Host Command Server (HCS) process on the workstation is active. If it is not active, start it. If it is active, re-issue the failing command.
Error Message SVSRV060 process_name error message: message.process_name is the SNA View server process that detected the error.
message is the text of the error message.
Explanation SNA View server process detected a critical error and notified the client of the error.
Recommended Action Review the error message to determine the cause of the error and correct the problem.
Error Message SVSRV070 Verify that the HCI and Command Servers are active.Explanation SNA View process has detected a possible problem with connection to the mainframe, indicating that the Host Command Interface and Host Command Server may have terminated.
Recommended Action Ensure that the Host Command Interface and Host Command Server are active and functioning properly. If they are not active, review all SNA View error messages and restart them once any problems have been corrected. If they are still active, attempt to rerun the failing process.
Error Message SVSRV071 Command not processed. Verify that the HCI and Command Servers are active.Explanation A mainframe command was issued but SNA View was unable to process it. The Host Command Interface, Host Command Server, or both may no longer be active and functioning properly. No further processing for the issued command will take place.
Recommended Action Verify that the Host Command Interface and Host Command Server are up and functioning properly. If they are not active, restart them or contact the Cisco TAC.
Explanation SNA View could not log in to the Sybase database using the Sybase ID and password defined during configuration. Either Sybase is not running, or the Sybase ID and password are invalid.
Recommended Action Determine whether Sybase is running on the SNA View workstation. Determine whether the Sybase ID and password, defined during SNA View workstation configuration, are correct.
|
|