|
|
|
|
If the problem persists after you have completed all the basic checks listed in Basic Checks then this section provides further guidance on specific problems.
Continue your investigation by working through the sections that are most relevant to your problem.
If a Motif SNAP-IX program (such as the Motif 3270 emulation program, the 5250 emulation program, or the Motif administration program) fails to start then check the following:
Check that the Motif software (version 1.2 or later with X11R5 or later) is installed on your system.
Ensure that you are using a terminal with X-server support.
Check that your X-server has the required fonts installed. (Error messages will be produced if this is not the case.) Refer to SNAP-IX Installation for more information about installing fonts.
Check that address of your X-Server is configured on the X software on the Solaris system on which you are running the Motif administration program. You can set this in either of the following ways:
Set the my_PC
,
type the following:
export DISPLAY=my_PC:0
Specify the option when starting the Motif
program. For example, if you are starting the Motif administration program
to connect to an X-Server whose TCP/IP name is my_PC
, type
the following:
xsnaadmin -d my_PC:0
Some X-Servers (such as servers running Solaris) do not accept requests by default. If the Motif program reports that it is unable to connect, then you must configure it to accept requests. For example, if you are using X-Server running Solaris, type the following:
xhost +
This section describes what to do if you encounter problems with the 3270 emulation program.
If the SNAP-IX 3270 emulation program fails to start then you should check the following:
If you are using the character-based 3270
emulation program, ensure that the
export TERM=ansi
Ensure that the user who is trying to start the emulation program is configured with permission to start the emulation program. You can do this in either of the following ways:
If you wish to configure particular users with specific permissions then configure each user as an explicit 3270 user.
If you do not mind who runs the 3270 emulation program then configure a default 3270 user.
Refer to the SNAP-IX Administration Guide for more information about configuring 3270 users.
If you are using the Motif 3270 emulation program then also refer to Resolving Problems with Programs That Use Motif.
If the user is specifying a style file when starting the 3270 emulation program, try starting the program without using the style file, to return all settings to their default value.
This sections describes what you should do if you get a blank screen that does not display any welcome message from the host when you start the 3270 emulation program.
The first thing that you should do is ensure that the style file being used by the 3270 emulation program does not suppress the host screen when the session is started. This option is usually used when running HLLAPI applications that control the display using the DISPLAY_ON and DISPLAY_OFF verbs. Change this option by modifying the Host Screens Suppressed at Startup option in the Customize Display Parameters dialog.
If you have checked the style file, and this is not the source of the problem, then the blank screen indicates that the 3270 emulation program has not been able to establish a session to the host. You should check the following:
Ensure that you have tried to activate the session. You can activate the session either from the Control menu, or by using a 3270 style file with an initially active session. Refer to the SNAP-IX 3270 User's Guide for more information about using the Control menu, and about 3270 style files.
You can also check the status of the session from the Control menu.
Check the configuration of the 3270 user. It is possible to configure a 3270 user with no sessions. Check this in one of the following ways:
If you are using the Motif administration program, then zoom on the 3270 user to view the configuration. Refer to the Motif administration program online help for more information about this.
If you are using the command-line administration program then issue the snaadmin query_3270_user command to view the configuration.
If the user is configured without any sessions then configure the user with at least one session. Do this in one of the following ways:
If you are using the Motif administration program, then zoom on the 3270 user to modify configuration.
If you are using the command-line administration program then issue the snaadmin define_3270_user command to modify the configuration.
Check the 3270 status line, which is at the bottom of the session screen, for any COMM or PROG check errors. If there are, then refer to the SNAP-IX 3270 User's Guide for more information about these errors.
Check that the 3270 LU that is being used is active. Check
this using the 3270 emulation program Control
menu. If the status of the LU is shown as enabled
then check
that the link station over which the 3270 emulation program is communicating
to the host is active. See Check Communication with Other SNA Nodes for information about
this.
Check that the LU that the 3270 emulation program is communicating with at the host is active:
If you are using the Motif Administration program, zoom on the link station to see the LU.
The LU is shown as SSCP when the ACTLU has been received.
The LU is shown as ACTIVE when the BIND has been received.
If you are using the command-line administration program then issue the snaadmin status_dependent_lu command to view the configuration.
Check that the screen size configured for the LU matches the screen size used by the host for that LU. Do this in one of the following two ways:
If you are using the Motif administration program, then zoom on the 3270 LU to view its configuration.
If you are using the command-line administration program then issue the snaadmin query_lu_0_to_3 command to view the configuration.
If you are running the 3270 emulation program using ISO8859 (that is, using the character-based emulation program with the option, or using the Motif emulation program, or 3179G with no options) then check that you have the correct language selected.
If you are using 3270 emulation program using the option then check that you are using the correct translation table.
If you are unable to transfer files using the 3270 file transfer, then check the following:
Check that the host LU is configured for distributed function terminal (DFT) rather than control unit terminal (CUT) mode. (SNAP-IX does not support CUT mode file transfer.) You may be able to specify DFT mode using the logmode parameter at logon.
Check that the session is logged on and not running another
application. (You can usually only transfer files at the Ready
prompt.)
If command line or HLLAPI file transfer fails:
Check the session ID configured in the style file matches that used on the command line.
Check that there is an active 3270 emulation program running with the same Solaris user ID.
Try the menu-operated file transfer.
Check the write-structured field (WSF) size (try using the default of 2K).
Check that you have permission to access the Solaris directories that you are using.
Check whether the host file type you are specifying has to be created before you can transfer files.
Use the variable format and transfer the files using binary mode to maintain file integrity. (Fixed or default host formats pad files to create multiples of 80 characters.)
Ensure that you set the
If you are transferring text then limit the file's line length to 80 characters or less because text files may be truncated at 80 characters.
Check the translation tables. Some characters in ASCII are not available in standard EBCDIC (for example,[ and ]). Therefore, a file may not be transferred correctly in some languages (such as English).
Use the option to specify a private translation table.
If you are unable to print successfully with 3270 printing, then you should check the following:
If your 3270 printing produces no output then run the 3270 emulation program in the foreground. (This means that you must start the emulation program without using the option). This will allow you to check 3270 printing more easily. Once you have diagnosed and resolved the problem then you can run the emulation program in the background if you wish.
When you have started the emulation program in the foreground then check the following:
Check the status of the 3270 printer session using the Printer Session menu item of the Control menu.
If no sessions are displayed this means that no printer sessions have been configured for this user. Define a 3270 printer session for the user in either of the following ways:
If you are using the Motif emulation program then zoom on the 3270 user.
If you are using the command-line administration program then issue the snaadmin define_3270_user command.
If a 3270 printer session is displayed, but is marked as enabled, then check that the link station has been started (see Check Communication with Other SNA Nodes) and that the LU has been activated at the host.
Check that the printer command (lp) has been set up correctly in the Customize Printer Parameter menu.
If your 3270 printing produces extra line feeds then you might
need to set the
If RJE is not working then you should start by checking the status of the RJE workstation. Do this by issuing the following command:
snarjestat workstationname
Replace workstationname with the name of your RJE workstation.
The following sections describe what to do according to the output of the snarjestat.
If the snarjestat reports that the workstation and all its sessions are active then there is no problem with the SNAP-IX RJE workstation.
Use the snarjecon program to issue a command to the host to verify that the host subsystem (usually JES) is active. Refer to your IBM documentation for information about host commands. Refer to SNAP-IX RJE User's Guide for a list of relevant IBM manuals. For example, in JES2, a $S command may be required to activate the printer or punch.
If the snarjestat reports that the RJE workstation is active, but that the sessions are not, then you need to activate one or more sessions. You should check the following:
Check that the link station that the LUs are using is active. Refer to Check Communication with Other SNA Nodes for more information about how to do this.
Check that the workstation's configuration (specifying whether to issue logon or wait for Binds from the host) matches the configuration at the host.
Check that the logon command specified in the RJE style file is correct for the host that you are using. Set the display_sscp_messages parameter in the RJE style file to YES to enable you to examine error messages generated when logging on to the host.
If the snarjestat indicates that the workstation is not running, issue the following command to start the workstation:
snarjewks workstationname
(Replace workstationname with the name of your RJE workstation.)
If the workstation fails to start then look in the error log file. If the error log indicates that the workstation has not been configured then configure it. Refer to the SNAP-IX Administration Guide for more information about configuring RJE workstations.
If RJE cannot receive files, do the following:
Check that the RJE workstation has permission to write files for its user ID. (The RJE workstation is a setuid program.)
Check that the directories you specified exist.
If you are having problems with an APPC or CPI-C application, including a Java CPI-C application, do the following:
Check that the application is correctly installed.
For a Java CPI-C application, check
that the environment variables
Check that the mode, LUs and link required are correctly configured.
If a problem occurs when the application originates the conversation do the following:
Check that the link is active (this may happen on demand). Refer to Check Communication with Other SNA Nodes
Check that the relevant session is started (this may happen on demand)
If a problem occurs when the application receives an incoming conversation request, do the following:
Check that the link is active (this may happen on demand if the link is configured as incoming)
Check that the relevant session is started (this may happen on demand)
If the receiving application is dynamically loaded (invokable), also check that the TP configuration information has been configured correctly (refer to the SNAP-IX Administration Guide for more information about configuring TP information).
Verify that the session limit is sufficient for the number of applications required.
Check that you are not mixing single-session and parallel-session modes on an LU-LU pair.
The APPN architecture does not support independent LU 6.2 (parallel sessions) across a link station (typically SDLC) that is established without XID exchange (that is, with just SNRM and UA). Therefore, if the host does not send XIDs, independent LU 6.2 cannot be used.
Check the correct allocate type (for example, an immediate allocate needs a contention winner session).
For CPI-C applications, set the local LU name (using the snaadmin
define_cpic_side_info command or
For LUA or LU0, do the following to determine why the application is not working:
Check that the application is correctly installed and that you have permission to run it.
Use one of the following methods to ensure that the application is running:
If you are using the Motif administration program, check whether an application identifier or user name is displayed next to the LU.
If you are using the command-line administration program, issue the snaadmin query_lu_0_to_3, and check that the appl_conn_active parameter is set to YES.
You can also use the Solaris ps utility. See Other Information to Provide to Support Personnel, for information about using the ps utility.
Check that the application is using the correct LU.
Check that the host link is active.
Ensure that the host activates the relevant LU.
For HLLAPI applications, do the following to determine why the application is not working:
Observe the behavior of the application by running 3270 in the foreground.
Check the session ID used by the application has been configured in the 3270 style file.
Observe whether there are any changes on the host screen,
such as extra news
messages which the HLLAPI application may
not be able to handle.
Check that the application is waiting correctly for prompting text.
If a HLLAPI file transfer fails, refer to Unable to Transfer files Using 3270 File Transfer.
To determine why a Management Services (MS) application is not working, issue the snaadmin query_nmvt_application command. Refer to SNAP-IX Administration Command Reference for more information about this command.
This command returns the following information:
Name of the registered application
MS vector key accepted by the application
Use the REGISTER_NMVT_APPLICATION verb to set the correct MS vector key. For more information, refer to the SNAP-IX MS Programmer's Guide.
To determine why a Node Operator Facility (NOF) application is not working, obtain an API trace on the NOF interface. For more information about how to do this, see API Tracing.
Check that the application program has issued the SET_PROCESSING_MODE verb before issuing verbs that alter the configuration. Refer to the SNAP-IX NOF Programmer's Guide for more information about this verb.
To determine why 5250 emulation is not working, do the following:
Check that the QPCSUPP session is active. QPCSUPP is the mode name used for communication from the 5250 emulator to the AS/400 system.
Check the user ID and password are configured correctly in the 5250 style file. They are both used twice in establishing a 5250 connection; once in the Allocate and once at the logon screen. Refer to 5250 Style Files.
Try starting the 5250 emulator without using the style file to return all settings to their default value.
This section describes what to do if you encounter problems with TN Server.
If you cannot connect to the host using TN Server, then you should check the following:
Ensure that the node is started, and that the link
to the host is in active
or on demand
state.
Ensure that the configuration contains a suitable TN3270 access record for the TN3270 user. Make sure the access record specifies the TN3270 client's address correctly or is the default record. Also make sure that the LU specified in the record is a valid LU or LU pool defined on the link to the host.
Refer to the SNAP-IX Administration Guide for more information about configuring TN3270 users and LUs.
Ensure that the LU configured in the TN3270 access record is in SSCP state.
If the LU is inactive, you may be able to activate it by stopping and restarting the link. Ensure that no other users are using the link before you do this.
If the LU is already active, then it is in use by another user and cannot currently be used by this TN3270 client.
If the configuration specifies an LU pool rather than an individual LU, check that one or more LUs in the pool are in SSCP state. If all the LUs are active, this means that they are in use by other users and cannot currently be used by this TN3270 client.
To determine why NetView Distribution Manager Agent (NDMA) is not working, check the following:
NDMA uses a specific LU name (NDMA). This LU must be configured to match the mainframe configuration.
Check that the link station is active, that the LU is active and that the BIND has been sent from the host.
If you are using the Motif Administration program, zoom on the link station to see the LU. The LU is shown as ACTIVE when the BIND has been received.
If you are using the command-line administration program, then issue the snaadmin status_dependent_lu.
Check the paths in the ndmpath.dat file.
To determine why the network node is not routing sessions, do the following:
Issue the snaadmin query_isr_sessions to obtain current information about active sessions. Refer to SNAP-IX Administration Command Reference for more information about this command.
Check that the network IDs are the same on all machines in the network. SNAP-IX does not include border node support that is required to access machines with different network IDs.
Ensure that you are trying to route only independent APPC sessions using ISR (intermediate session routing). Other sessions can use PU concentration or DLUR.
To determine why PU concentration sessions do not connect, check the following:
Check that the upstream and downstream link stations are active.
If you are using Motif administration program, zoom on the link stations.
If you are using the command-line administration program, issue the snaadmin status_connectivity command.
Check that the LUs are attached in the configuration and that they are not being used by other applications.
If you are using Motif administration program, zoom on the link stations and LU pool.
If you are using the command-line administration program, issue the snaadmin query_downstream_lu command.
If you are using a pool, check whether there are LUs available in the pool using one of the following ways:
If you are using Motif administration program, zoom on the link station and the LU pool.
If you are using the command-line administration program, issue the snaadmin query_lu_0_to_3 command.
To determine why servers cannot administer one another, do the following:
Check that one server is a master server in the domain.
Issue the snaadmin query_sna_net command on each server to obtain information about the configuration of the topology.
Check that the servers are in the same domain.
Check the TCP/IP connections using the Solaris ping command.
|
|
|
 |
|