Page 1 November 1993 This document explains how to solve problems that could arise in the day- to-day use of the DECnet SNA Gateway for Synchronous Transport and its related OpenVMS products. This manual also discusses diagnostic tools and describes how to report problems with the DECnet SNA Gateway products.
Page 2 November 1993 Information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such a license.
Page 3: Table Of Contents
........... . . 1 Solving DECnet SNA Gateway for Synchronous Transport Problems Hardware Problems .
Page 4 2.3.4.6 Remote Modem Testing ......2–16 2.3.4.7 Start the System Software ......2–16 Additional Procedures .
Page 5 B Log File of a Gateway Load C The DEC MicroServer Display Panel Power-Up Sequence ........C–2 Normal Power-Up Sequence Without Retry .
Page 6 Figures DECnet SNA Gateway for Synchronous Transport Manuals .........
Page 7: Preface
Preface The DECnet SNA Gateway for Synchronous Transport (called the DECnet SNA Gateway-ST or Gateway-ST in this manual) is a hardware and software system that provides an interface between IBM and Digital Equipment Corporation networks that use SDLC lines and circuits. By handling the...
Page 8 Digital and IBM systems they will be using. Document Structure This document has the following chapters: • Chapter 1, Solving DECnet SNA Gateway for Synchronous Transport Problems This chapter is divided into four sections. Each section discusses a certain category of problems: Section 1.1, Hardware Problems...
Page 9 • Appendix C, The DEC MicroServer Display Panel, describes the DEC MicroServer display values during power-up and dump sequences. It also describes the values that display when you halt the software or receive error codes. • Appendix D, DEC MicroServer Facilities for Problem Solving, describes how to connect to the DEC MicroServer as a remote console.
Page 10 Installing the DEC MicroServer-SP • DEC MicroServer-SP Systems Conﬁguration Card DECnet SNA Gateway for Synchronous Transport Software Manuals The following manuals are part of the DECnet SNA Gateway for Synchronous Transport documentation kit: • DECnet SNA Gateway-ST Guide to IBM Parameters •...
Page 11: Decnet Sna Gateway For Synchronous Transport Manuals
Figure 1 DECnet SNA Gateway for Synchronous Transport Manuals Planning DECnet SNA Gateway−ST DECnet SNA Gateway−ST Installation (OpenVMS) Guide to IBM Parameters (Chapter 1) Installing and Configuring Installing the DECnet SNA Gateway−ST Installing the DEC MicroServer DEC MicroServer−SP Installation (OpenVMS) (Chapters 2−4)
Page 12 In addition to the Gateway-ST base communication systems, Digital Equipment Corporation provides the following access routine products that run on OpenVMS and can use the Gateway-ST to access IBM systems: • Bulk Data Transfer DECnet SNA Data Transfer Facility for OpenVMS DECnet SNA Remote Job Entry for OpenVMS DECnet SNA Printer Emulator for OpenVMS •...
Page 13 You may ﬁnd the following IBM documents useful: • ACF/VTAM Diagnosis Reference (IBM Order No. SC27-0621) • ACF/SNA System Problem Determination Guide, Vol 1 (IBM Order No. GG24-1514) • ACF/SNA System Problem Determination Guide, Vol 2 (IBM Order No. GG24-1523) •...
Page 14 Conventions The following conventions are used throughout this manual: Convention Meaning UPPERCASE This typeface is used in the running text for commands, options, arguments, pathnames, ﬁles, and directories. SNACP> SET LINE line-id This typeface is used for command syntax and command examples.
Page 15 The following conventions are used for SNANCP and NCP commands: Convention Meaning circuit-id A string of characters whose exact syntax is that for a DECnet or SNA circuit identiﬁcation. On DECnet nodes, circuit identiﬁcation takes one of the following formats: dev-c A device name.
Page 16 Convention Meaning node-address A numeric value in the range of 1.1 to 63.1023, composed of an area number to the left of the period followed by a node number to the right of the period. If the area number is not supplied, the area number of the executor node is used.
Page 17 LU6.2 Logical unit type 6.2 IBM’s Multiple Virtual Storage operating system MR/S VAX Message Router/S Gateway MR/P VAX Message Router/P Gateway Network Control Language Network Control Program. This manual uses NCP Digital product and IBM NCP to refer to the IBM product. Primary logical unit DECnet SNA Printer Emulator for OpenVMS Physical unit...
Page 19: Solving Decnet Sna Gateway For Synchronous Transport Problems
Synchronous Transport Problems This chapter discusses problems that might occur when you are using the DECnet SNA Gateway for Synchronous Transport and its related products. Each section begins with a list of problems; subsequent pages give possible solutions for each problem. The sections are as follows: •...
Page 20 Problem Number Symptom The Gateway-ST loads, but the circuit remains in the on-starting state. 1–2 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 21 3. Determine whether the DEC MicroServer’s circuit breaker has been tripped. If it has, reset the circuit breaker (shown in Figure 1–1), and power up the unit again. NOTE Figure 1–1 shows the control panel of the four-port DEC MicroServer. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–3...
Page 22: Setting The Voltage Selector
If necessary, change the setting on the voltage selector, and try to power up the unit again. • If the selector is correctly set but the breaker still trips, unplug the unit and call Digital service representative. 1–4 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 23: Checking The Voltage Selector
Figure 1–2 Checking the Voltage Selector LKG-4905-93I Solving DECnet SNA Gateway for Synchronous Transport Problems 1–5...
Page 24 Customer Service to replace the unit as soon as possible. If the system does not boot, there is a problem with the DEC MicroServer. Contact Digital service representative for a replacement. 1–6 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 25 If the modem appears to be faulty, have it repaired. If the link appears to be faulty, contact the remote site to request further fault diagnosis. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–7...
Page 26 Chapter 2. One faulty port on the DEC MicroServer does not necessarily prevent you from using the DECnet SNA Gateway for Synchronous Transport system. For example, if you have a DEC MicroServer and you are using two lines only at speeds less than 64K bits per second (bps), you can simply use one of the two free ports instead of the faulty one.
Page 27 If you experience a problem on a dial-up line (for example, you get the carrier-detect signal but still cannot pass data through the modem), make sure you have similar modems in the link. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–9...
Page 28 V.24 cables. See Installing the DEC MicroServer for information about the RS-232-C adapter. • Replace any defective cables, and reload the system. 6. If you cannot access the IBM system, refer to Section 1.4, Session Problems. 1–10 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 29 3. If the counter shows Receive overrun errors, several possible hardware problems could cause this error. These hardware problems can cause the number of Receive failures in the communications device to become signiﬁcantly larger than the number of data blocks received. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–11...
Page 30 Monitor the problem line. Regularly clear the counters, and look at them again approximately an hour later. If the overrun is consistently high, there might be a problem in the DEC MicroServer. Contact service representative. 1–12 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 31 IBM NCP LINE macro is the same as the NRZI setting in the Gateway-ST conﬁguration ﬁle. The following table equates Gateway-ST and IBM NCP NRZI settings: Gateway-ST IBM NCP SIGNALLING NRZI NRZI=YES SIGNALLING NORMAL NRZI=NO Solving DECnet SNA Gateway for Synchronous Transport Problems 1–13...
Page 32 Make sure the modems are powered on and working properly. • Make sure the modems have passed any self-test. • Use the DEC MicroServer’s loopback tests to check the modems. Section 2.2 describes modem loopback tests. 1–14 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 33: Initialization Problems
You receive an error message when you try to use a component or access name that you deﬁned by editing the conﬁguration ﬁle. Event logging reports that the SNAINI object is unknown at the remote node. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–15...
Page 34 Log in to a load host. • Enter the following command: NCP> LOOP NODE node-name where node-name is the name of a remote node on the same Ethernet as the DEC MicroServer (see Figure 1-3). 1–16 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 35: Loop Between Nodes On Either Side Of The Dec Microserver
7. Check that each load host has a database entry for the DEC MicroServer. Identify the load hosts, and perform the following actions: • Enter the following command (for Phase IV): NCP TELL load-host-name SHOW NODE gateway-node-name _CHARACTERISTICS Solving DECnet SNA Gateway for Synchronous Transport Problems 1–17...
Page 36 If the line state is OFF, change the state to ON with the following NCP command: NCP> SET LINE line-id STATE ON The value of the line-id must be the same as the value of the service circuit previously displayed. 1–18 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 37 UAF SHOW/PROXY gateway-node-name ::SNA$GO A message appears saying that the local proxy is SNA$CSC. The following message appears: Default proxies are flagged with (D) gateway-node-name ::SNA$GO SNA$CSV (D) Solving DECnet SNA Gateway for Synchronous Transport Problems 1–19...
Page 38 Check that the software load ﬁle (SNACTSnnn.SYS) located in SYS$COMMON:[SNA$CSV] has the correct protection code (S:RWED, O,RWED, G, W). 13. If the conﬁguration ﬁle has become corrupted, redo it. 14. Reload the DEC MicroServer. 1–20 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 39 DEC MicroServer by deleting the loading information from its DECnet database. Enter the following command to delete the information: NCP> CLEAR NODE gateway-node-name LOAD FILE Reload the DEC MicroServer. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–21...
Page 40 See the solutions for Initialization Problem 1. If you receive these event messages and your Gateway-ST is booted, the events are the result of other systems’ requests for services from your load host. These messages have no bearing on the Gateway-ST. 1–22 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 41 Load ﬁle speciﬁcation To check these entries issue the following command: NCP> SHOW NODE gateway-node-name CHARACTERISTICS Check that the service circuit is enabled with the following command: NCP> SHOW CIRCUIT circuit-id CHARACTERISTICS Solving DECnet SNA Gateway for Synchronous Transport Problems 1–23...
Page 42 3. Make sure the executor node has all the necessary load ﬁles in the correct directories. Check the DECnet SNA Gateway-ST Installation for a list of the Gateway-ST ﬁles and their locations. 1–24 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 43 Check the DECnet logging state. Invoke NCP and enter: NCP> SHOW KNOWN LOGGING If this command shows that some events are being ﬁltered, disable ﬁltering. Invoke NCP and enter: NCP> SET LOGGING MONITOR KNOWN EVENTS Solving DECnet SNA Gateway for Synchronous Transport Problems 1–25...
Page 44 If you still do not receive event messages, check whether you have screened out OPCOM messages with the following DCL command: $ SHOW BROADCAST If necessary, issue the following DCL command to set broadcasting for OPCOM messages ON: $ SET BROADCASE=OPCOM 1–26 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 45 See Hardware Problem 6, Section 1.1. For information about the correct syntax of the SNANCP SET LINE command, see the DECnet SNA Gateway-CT and ST Management book. 3. Check for SNAEVL event messages that indicate a problem with the conﬁguration ﬁle. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–27...
Page 46 5. Check the DEC MicroServer’s synchronous port(s) by using the procedure described in Hardware Problem 3. 6. This problem might also be caused by incorrect circuit parameters. See Initialization Problem 7. 1–28 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 47 SNANCP> SET CIRCUIT circuit-id STATE ON 6. If the SNANCP SHOW command shows that the circuit state is OFF, use the following command to set the circuit state ON: SNANCP> SET CIRCUIT circuit-id STATE ON Solving DECnet SNA Gateway for Synchronous Transport Problems 1–29...
Page 48 DECnet SNA Gateway-CT and ST Management book. Also, check that the PU segment size and line buffer size are the same and that these sizes match the value of the IBM NCP PU deﬁnition statement MAXDATA parameter. 1–30 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 49 If the PU is not assigned to a circuit, use the following command to assign it. SNANCP> SET PU pu-id CIRCUIT circuit-id 6. Ask the VTAM operator to verify that your PU has been activated and is in the active state. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–31...
Page 50 If you cannot ﬁnd this ﬁle, execute Part 1 of SNACST$CONFIGURE. • Check the proxy account created during the Gateway-ST conﬁguration. Invoke the VMS AUTHORIZE utility, and issue the following command: UAF SHOW SNA$CSV 1–32 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 51 When the Gateway-ST was initialized, the command procedure could not read or encountered errors in the SNA conﬁguration ﬁle. Event messages from SNAINI tell you where the initialization command procedure met a problem. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–33...
Page 52 NCP> SET NODE node-address NAME DECnet-node-name To ensure that a node outside the area is deﬁned the next time the Gateway-ST loaded, edit the node conﬁguration ﬁle on the load host: SYS$COMMON:[SNA$CSV]SNAGATEWAY_gateway-node-name_DNA.COM 1–34 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 53 SNA conﬁguration ﬁle. Correct any errors. To ensure that the components and access names are deﬁned next time the Gateway-ST is loaded, correct the problem by editing the following ﬁle: SNAGATEWAY_gateway-node-name_SNA.COM Solving DECnet SNA Gateway for Synchronous Transport Problems 1–35...
Page 54 Event logging reports that the SNAINI object is unknown at the remote node. Solution: You might have purged your network object database. Redeﬁne the object on Phase IV, by executing: $ @SYS$COMMON:[SNA$CSV]DEFINE_ gateway-node-name _ON_ load-host-node-name .COM and on Phase V, by executing: @SYS$STARTUP:NET$APPLICATION_STARTUP_NCL 1–36 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 55: Decnet Problems
The Gateway-ST boots and comes up but does not initialize completely. NOTE To access the Gateway-ST, you must be licensed to use DECnet. If DECnet is not enabled, you cannot set the lines and circuits to the ON state. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–37...
Page 56 3. If error messages suggest the problem is with the Gateway-ST node (the DEC MicroServer), refer to the problems described in Section 1.1, Hardware Problems and Section 1.2, Initialization Problems. 1–38 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 57 6. Run DECnet NCP loopback tests to test the communications hardware and software from the DECnet Management node to the Gateway-ST. For more information see the DECnet SNA Gateway-CT and Gateway-ST Management book. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–39...
Page 58 DECnet SNA event 266.0, Gateway initialization From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.cc SNA gateway management, Severity = informational Completed Normal successful completion Check the messages in the SYS$COMMON:[SNA$CSV]NETSERVER.LOG ﬁle and correct any problems. 1–40 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 59: Session Problems
The session hangs while in progress. Sessions terminate abnormally. An excessive number of line errors occur. An excessive number of circuit errors occur. Response time or ﬁle transfer time increases signiﬁcantly. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–41...
Page 60 DECnet SNA Gateway-CT and ST Management book. To ensure that the Gateway-ST is initialized with the correct access names next time it is loaded, edit the SNA conﬁguration ﬁle on the load host: SYS$COMMON:[SNA$CSV]SNAGATEWAY_gateway-node-name_SNA.COM 1–42 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 61 DECnet SNA Gateway-CT and ST Management book. To ensure that the Gateway-ST is initialized with this PU next time it is loaded, edit the SNA conﬁguration ﬁle on the load host: SYS$COMMON:[SNA$CSV]SNAGATEWAY_gateway-node-name_SNA.COM Solving DECnet SNA Gateway for Synchronous Transport Problems 1–43...
Page 62 DECnet SNA Gateway-CT and ST Management book. To ensure that the Gateway-ST is initialized with these LUs next time it is loaded, edit the SNA conﬁguration ﬁle on the load host: SYS$COMMON:[SNA$CSV]SNAGATEWAY_gateway-node-name_SNA.COM 1–44 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 63 Section 1.2, Initialization Problems 6 and 7. 6. If the lines and circuits are active, check that the PU is conﬁgured correctly and activated. See Section 1.2, Initialization Problem 8. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–45...
Page 64 PUs, and LUs are functioning normally.) For some sample IBM sense codes, refer to Appendix A. IBM’s Systems Network Architecture Formats manual contains a complete list of sense codes. 1–46 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 65 There may be a problem with the IBM system. The IBM system may be busy, or there may be an IBM conﬁguration problem either with VTAM or with the application with which you are trying to communicate. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–47...
Page 66 2. DECnet problems may be occurring between the load host and the Gateway-ST. See Section 1.3, DECnet Problems. 3. The IBM host might not be working properly or might be overloaded (see Session Problem 5 in this section). 1–48 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 67 DECnet SNA Gateway-CT and ST Management book for information on using this command. To ensure that the correct buffer size is used next time the Gateway-ST is loaded, edit the SNA conﬁguration ﬁle on the load host: SYS$COMMON:[SNA$CSV]SNAGATEWAY_gateway-node-name_SNA.COM Solving DECnet SNA Gateway for Synchronous Transport Problems 1–49...
Page 68 If line errors occur on only one circuit, try moving the line to one of the other ports, if available. If the problem remains, replace the cable. For additional information on line problems, refer to Hardware Problem 6. 1–50 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 69 In addition, Frame retransmits error messages can occur because of problems in the communications equipment or because of a noisy line. See Section 1.1, Hardware Problem 5 for a description of how to solve these problems. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–51...
Page 70 SNATRACE circuit-level trace being run • Line speed of DECnet lines to Gateway-ST • Decrease in IBM response time due to system load or a program’s priority (for example, heavy RJE activity). (See Session Problem 1–52 Solving DECnet SNA Gateway for Synchronous Transport Problems...
Page 71 Gateway-ST node to the SNA network. See Section 1.1, Problems 5 and 6 for more information. If the problem persists, ask your Digital service representative to check this device. Solving DECnet SNA Gateway for Synchronous Transport Problems 1–53...
Page 73: Using Loopback Tests
Using Loopback Tests Loopback tests send test messages over a particular communications path and then loop them back to the originating node. This operation checks the communications links and helps you isolate the cause of any faults. If the originating node successfully receives the test messages, you can assume all components along the test path are working properly.
Page 74: Loopback Tests
Figure 2–1 shows which parts of the network the loopback tests check. Figure 2–1 Loopback Tests DECnet Host Tests DECnet SNA GWY−ST (DEMSA or DEMSB) SNANCP Tests Network LKG−2948−89R 2–2 Using Loopback Tests...
Page 75 Figures 2–2 and 2–3 show the suggested order to run loopback tests to isolate a problem. Start with the loopback tests shown in Figure 2–2. If the ﬁrst set of tests are successful, run the tests shown in Figure 2–3. Run the tests in the order shown in the ﬁgures unless you know that the problem is in a particular area.
Page 76: Running Ncp Tests
Figure 2–2 Running ncp Tests Invoke NCP Run remote loopback test Run executor loopback test DECnet problem on See Figure 2−3 node running loopback test Run circuit level loopback test Fault in DECnet SNA Gateway−ST communications Contact your Digital representative LKG−5036−93R 2–4 Using Loopback Tests...
Page 77: Running Snancp Tests
Figure 2–3 Running snancp Tests Invoke SNANCP Run controller loopback test Faulty synchronous port Run cable test Fault in cable Run local modem test Fault in local modem Run remote modem test Fault in remote modem Run SNATRACE Contact your or IBM traces Digital representative LKG−5037−93R...
Page 78: Ncp Loopback Tests
2.1 NCP Loopback Tests Before running the NCP loopback tests, verify that the Gateway-ST node is on the same DECnet network as the node from which you want to run the tests. Then invoke NCP with the following command: $ NCP Once you have invoked the Network Control Program (NCP), you can use the loopback tests to check the software and the hardware between the Gateway-ST and any DECnet node on the same network.
Page 79: Remote Loopback Test
2.1.1 Remote Loopback Test The remote loopback test checks the ability to create logical links between the DECnet host and the Gateway-ST regardless of the physical route taken by the test data. Start with this test if you are unsure of the location of the problem. To run the remote loopback test, you must know the Gateway-ST privileged username and password.
Page 80: Circuit Level Loopback Test
To run the executor loopback test, enter the following command at the NCP prompt: NCP> LOOP EXECUTOR [ parameter ] [...]) For example, NCP> LOOP EXECUTOR If this test fails, there is a problem with the DECnet software in your local node.
Page 81: Controller Loopback Test
Checks the cable from the Gateway-ST to the local modem. • Modem loopback tests: Check the communications link either to the modem at the Gateway-ST end or to the modem at the IBM end. Use a digital loopback test on the local modem and an analog loopback test on the remote modem.
Page 82: Cable Loopback Test
2.3 DEC MicroServer Loopback Tests There might be times when you cannot use the test facilities offered by the DECnet SNA Gateway for Synchronous Transport software. In these cases, you can use the loopback facilities that the DEC MicroServer hardware offers.
Page 83: Loopback Points
2.3.1 Loopback Points A DEC MicroServer synchronous link has a number of components, as Figure 2–4 shows. The communication connections between different DEC MicroServer components are used as loopback points. Figure 2–4 Parts of a Synchronous Communications Link Communications Adapter Modem cable cable...
Page 84: General Test Procedure
2.3.2 General Test Procedure Test one line at a time, starting from the synchronous port on the DEC MicroServer and working towards the remote modem. Use the tests in the following order: 1. Synchronous port on the DEC MicroServer or the DEC MicroServer–SP 2.
Page 85: Connect To The Dec Microserver
>>> 2.3.4.2 Stop the System Software The loopback tests need exclusive use of the synchronous port(s), so you must stop the DECnet SNA Gateway for Synchronous Transport software before you start the tests. Enter the following remote console command: HALT Once the DEC MicroServer has been halted, the only way to restore normal Gateway-ST operations is to load the Gateway.
Page 86: Adapter Cable And Modem Cable Testing
2.3.4.4 Adapter Cable and Modem Cable Testing The adapter cable and modem cable loopback test use the same remote console command (TEST) on different loopback points. Run the adapter cable loopback test ﬁrst. To run the test, perform the following steps: 1.
Page 87: Modems That Recognize Local Loop
2.3.4.5.1 Modems That Recognize Local Loop If your modem recognizes the loopback signal, perform the following steps: TEST DATA_LOOPBACK/CH n /LOCAL Replace n with the number of the port (0, 1, 2, or 3). If the test fails, go to Section 2.3.5.
Page 88: Faults Indicated By Loopback Testing
2.3.4.6 Remote Modem Testing Remote modem tests check both the communications link and the remote modem. Before running this test, contact the remote site to check that it is convenient to do the test. Then, run the remote modem test by performing the following steps: 1.
Page 89 Table 2–1 (Cont.) Faults Indicated by Loopback Testing Test that failed What to do Local modem Call the modem’s supplier to service the unit, or replace the modem. Remote modem Either the remote modem or the intervening communica- tions link is faulty. To isolate the problem, ask the remote site to test the modem.
Page 91 Traces Two types of traces can isolate a DECnet SNA Gateway for Synchronous Transport problem: • Gateway Management traces • IBM traces Section 3.1 describes the Gateway Management traces and Section 3.2 describes the IBM traces. Each section lists documents that provide additional information about a particular type of trace.
Page 92 3.1.1.1 Circuit Level Traces The Gateway Management software provides an SDLC circuit level trace. Run an SDLC circuit level trace if any of the following symptoms occur: • You suspect that a line is not being polled. • The line to IBM does not initialize properly. •...
Page 93 • Virtual Machine/System Product: System Programmer’s Guide, Release 4 3.2.1 Types of Traces Six types of IBM traces can be useful for isolating problems in the DECnet SNA network: • VTAM buffer contents trace • VTAM I/O trace • Generalized PIU trace •...
Page 94 • When the line between the Gateway-ST and IBM can be activated but the PU (Gateway-ST) cannot be activated. Request a trace of all messages that reach the Gateway-ST through VTAM buffers. • When the circuit from the Gateway-ST to IBM is active but you are not sure whether you are communicating with the IBM host.
Page 95 3.2.1.6 VTAM Internal Trace A VTAM internal trace (TYPE=VTAM) provides a record of events within VTAM when VTAM is setting up a session. This trace can help determine the ﬂow of commands when you establish and terminate a session. When you ask the system programmer for a VTAM internal trace, you have the choice of three options: •...
Page 97 Up-Line Dumps If you report a problem to Digital Equipment Corporation (see Chapter 5) you could be asked to include an up-line dump or crash dump ﬁle. If a Gateway-ST node crashes, it writes the contents of its memory into a dump ﬁle on any available load host.
Page 98 • Entries in the DECnet conﬁguration database of each node on the Ethernet determine whether that node recognizes the Gateway-ST and whether the necessary service is enabled. Any node that can perform the load sends a message back to the Gateway-ST. •...
Page 99 Reporting Your Problems To report a problem, you must complete a Digital Software Performance Report (SPR). You can report a problem to Digital Equipment Corporation on an SPR form if your company has purchased support services for the Gateway-ST products or if the Gateway-ST products are still under warranty. Your operations manager can tell you if you have this service.
Page 100: Documenting A Problem
The following legend explains the symbols used in Table 5–1 : Symbol Meaning Always send this documentation, if your problem is in the indicated area. Send this documentation only if it is relevant. Send one item of documentation that is relevant. Table 5–1 Documenting a Problem Gateway Documentation...
Page 101 Table 5–1 (Cont.) Documenting a Problem Gateway Documentation Gateway-ST Management host host A description of your system’s activity before the fatal error An IBM VTAM buffer contents trace An IBM generalized PIU trace An IBM VTAM line trace An IBM VTAM internal trace An IBM VTAM I/O trace An SDAID trace Listing of VTAM deﬁnitions...
Page 102 5.2 Reporting Problems to Digital Equipment Corporation After you have isolated your Gateway-ST problem, report it to Digital Equipment Corporation. (For information on known problems, refer to the release notes for the speciﬁc product.) Your software distribution kit includes an SPR form. Use this form to report a software problem.
Page 103 Interpreting System Messages Gateway-ST events are logged by the Gateway-ST event logger. They are deﬁned according to class and type. The class identiﬁes the layer or resource to which the event applies. The type describes an event within a particular class. Event classes are deﬁned in Section A.1.1, and event types are deﬁned in Section A.1.2.
Page 104 You may also receive IBM sense codes. Most of the error messages are in the standard OpenVMS message format. Section A.2 describes the format of the error messages and refers you to documentation where the meaning of the error messages is provided. A.1 Interpreting Event Messages Event messages logged by OPCOM have the following format: DECnet SNA event nnn.nn event-text...
Page 105: Event Classes And Location
A.1.1 Event Classes Gateway-ST event messages specify a class and a type (see Section A.1.2) for an event. The class code number identiﬁes the location where the Gateway-ST event occurred. Table A–1 lists the event classes and their location. Table A–1 Event Classes and Location Event Class Location of Event Line...
Page 106 The Gateway-ST logs the following event types: • Line Line state change Device or driver error • Circuit Circuit state change • PU state change • Session LU state change Session protocol error Access denied • Counter Automatic counters Counters zeroed Counter overﬂow •...
Page 107 A.2 Interpreting Error Messages Most of the error messages you receive are in the standard format for OpenVMS messages. The format is as follows: FACILITY-L-IDENT, TEXT where FACILITY Is the name of the program that generates the message. Is a severity indicator with one or more of the following values: Code Meaning Success...
Page 108: Sample Ibm Sense Codes
If you receive a Gateway-ST error message that is not described in DECnet SNA Gateway-CT and ST Management, refer to the documentation for the access routine you are using. The individual documentation set lists the error messages that can appear when you are using a speciﬁc DECnet SNA product through a Gateway-ST.
Page 109 Log File of a Gateway Load The LOAD command down-line loads software to the DEC MicroServer. The Gateway-ST uses the speciﬁed circuit or the circuit obtained from the DECnet database on the host. During a software load to the DEC MicroServer, the load host’s console displays the following event messages: %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on nodename...
Page 110 %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on nodename DECnet SNA event 266.0, Gateway initialization From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.cc SNA gateway management, Severity = informational Setting gateway SNA configuration %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on nodename DECnet SNA event 256.0, Line state change From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.cc Line SYN- n , Severity = informational...
Page 111 The DEC MicroServer Display Panel Each time you power up the DEC MicroServer, it runs an internal test and then loads the Gateway-ST software. The unit uses a seven-segment display on the control panel to show how this test and load sequence is progressing. The DEC MicroServer also uses this display to: •...
Page 112: Dec Microserver Display Panel
Figure C–1 DEC MicroServer Display Panel LINE 0 LINE 1 LINE 2 LINE 3 DUMP LKG−2953−89R C.1 Power-Up Sequence On power up, the DEC MicroServer performs the following actions: • Lights the decimal point of the display. • Tests the display. •...
Page 113: Power-Up Display Values
The DEC MicroServer displays different values on the LED to show these actions. Table C–1 explains the values that can appear during the power-up sequence. Table C–1 Power-Up Display Values Display Value Meaning Power applied; tests are beginning. Ripple pattern (one Display being tested.
Page 114: Dump Display Values
C.2 Dump Sequence During a dump sequence, the DEC MicroServer: 1. Sends a dump request on the Ethernet and waits for a host node to reply. 2. Sends the contents of memory (including the internal error log) to the host node that answers the dump request.
Page 115: Error Code Values
For detailed information about resolving the problems indicated by each of these codes, refer to the DECnet SNA Gateway for Synchronous Transport problem-solving information in Chapter 1. Table C–3 Error Code Values...
Page 117: Summary Of Remote Console Commands
DEC MicroServer Facilities for Problem Solving The DEC MicroServer does not have a port dedicated to a console. Instead, it accepts connections over the DECnet console carrier. This means that a terminal connected to a load host can communicate with the DEC MicroServer as if it were a console terminal.
Page 118 Table D–1 (Cont.) Summary of Remote Console Commands Command Parameter Qualiﬁer HELP TEST None None PASSWORD hex-password None SHOW STATE None None TEST CABLE_TYPE None /ALL DATA_LOOPBACK /CHn MODEM_SIGNAL /INTERNAL /LOCAL /MANUAL /REMOTE TEST CONTINUOUS None None D.2 Connecting to the DEC MicroServer Before you can use the remote console commands for problem solving, you must create the logical connection between your terminal and the DEC MicroServer.
Page 119 D.3 Detaching the Console After you ﬁnish using the remote console, press to detach the console. Ctrl/D The NCP prompt appears on your terminal: NCP> D.4 Halting the Software The remote console HALT command stops the communications software. HALT can also be used to stop a software load or a system dump. The format of the command is: >>>HALT Use this command before you issue any of the following remote console...
Page 120 channel Deﬁnes the synchronous lines on which the test should run. You can use one or more of the following to test the DEC MicroServer: /CH0 /CH1 /CH2 /CH3 /ALL Note that you can only use /CH0 with the DEC MicroServer-SP. /qualiﬁer Speciﬁes the type of test you want to perform.
Page 121: Loopback Point Command Qualifiers
Figure D–1 Loopback Point Command Qualiﬁers Adapter Modem Communications cable cable link Local Remote Remote modem system modem MicroServer Loopback points Command /INTERNAL No qualifier* /LOCAL /REMOTE qualifier /MANUAL * Functions performed with a loopback connector. LKG−8352−93R For example, to loop back through the local modem on channel 1, you use either: TEST DATA_LOOPBACK/CH1/LOCAL TEST DATA_LOOPBACK/CH1/MANUAL...
Page 122: Loopback Points For The Modem Signal Test
Figure D–2 Loopback Points for the Modem Signal Test Communications Adapter Modem cable cable link Modem DEC MicroServer Loopback points LKG−4912−93R To use a modem signal test, perform the following steps: 1. Attach a loopback connector to one of the loop points. 2.
Page 123 D.5.3 Cable Type Tests A range of adapter cables available for the DEC MicroServer provide easy connection to various interface standards. Each type of cable contains a unique identiﬁer. To determine which cable is attached to a particular line, verify that there is no loopback connector on the port, and then issue the following command: TEST CABLE_TYPE/CH n To determine which cables are attached to the DEC MicroServer, verify that...
Page 124 D.6 Monitoring the DEC MicroServer Status The DEC MicroServer retains some internal information on its own status. You can display this information by using the SHOW command. The command has the following format: SHOW topic The topic parameter can be one of the following: PASSWORD Displays the current service password as a 16-digit hexadecimal number.
Page 125 D.7 Reloading the System Use the remote console command BOOT to reload the system. The BOOT command instructs the system to initiate the following actions: 1. Execute the internal test to check the major components in the DEC MicroServer. 2. Issue a load request on the Ethernet. 3.
Page 126 D.9.1 Setting a Password A service password is a hexadecimal number that users must specify to perform the following: • Use the NCP CONNECT command to attach a terminal as a remote console. • Use the NCP TRIGGER or LOAD command to down-line load the Gateway- ST software from a load host.
Page 127 2. Insert the power cord. 3. Release the DUMP switch when the display shows the following value: Once you have performed these three steps, you can set a new password by using the SET PASSWORD remote console command. D.10 Getting Help To get a listing of the commands and their formats, use the HELP command: >>>HELP This command produces a display similar to the following:...
Page 129: The Dec Microserver-Sp Port
DEC MicroServer Conﬁguration Guidelines The number of DEC MicroServer ports available for use depends on the maximum data speed you want to run on any line. However, if you have the DEC MicroServer-SP, you have only one port to use. The following sections contain guidelines for using the synchronous ports.
Page 130: Dec Microserver Ports
Table E–2 DEC MicroServer Ports Maximum Data Speed Band Number (in bits per second) of Lines Port(s) From 2.4K 0, 1, 2, 3 up to 64K Above 64K 0 and 1 up to 128K Above 128K 0 only up to 256K Use the information in Table E–2 in the following way: 1.
Page 131 Adapter Cable Pin Signals This appendix describes the pin signals used with the following adapter cables: • V.35 adapter cable • V.24/RS-232-D adapter cable • V.24/RS-232-C adapter Tables F–1 through F–3 list the signal names. (A) or (B) after a signal name refers to wires A and B of a twisted pair.
Page 132: V.24/Rs-232-D 25-Way D-Type Adapter Cable (Male
Table F–2 V.24/RS-232-D 25-Way D-Type Adapter Cable (Male) Signal Name Signal Name TX DATA RX CLOCK RX DATA LOCAL LOOP REM.LOOP GROUND SPEED SELECT CLOCK TX CLOCK TEST INDICATE Table F–3 V.24/RS-232-C 25-Way D-Type Adapter (Male and Female) Signal Name Signal Name TX DATA TX CLOCK...
Page 133 Index DEC MicroServer (cont’d) dump display, C–4 dump sequence, C–4 Access names, 1–42 normal dump display for, C–4 problems with, 1–35 retry dump display for, C–4 error codes, C–5 halt codes, C–5 power up BIND request, 1–47 normal load display for, C–3 retry load display for, C–3 power up sequence, C–2 DEC MicroServer loopback tests, 2–10...
Page 134 Hardware problems (cont’d) Gateway-ST loads, but some lines do not come up, 1–13 Error messages, A–5 line counter Receive failures, 1–11 DEC MicroServer, C–5 remote modem connection failure, 1–7 Help Errors BIND request, 1–47 at remote console, D–11 CRC, 1–11, 1–52 Frame too long, 1–12 Receive overrun, 1–11 IBM parameters, 1–27, 1–29...
Page 135 load command, parameters for, 1–23 Load host problems abnormal event logged, 1–38 Physical unit level traces, 3–2 Ethernet connection, 1–18 Power up failure, 1–3 load ﬁle, 1–18 Problems, reporting, 5–1 no event messages, 1–25 Loopback points, 2–11 in adapter cable testing, 2–14 in DEC MicroServer I/O port testing, Receive failures 2–13...
Page 136 Session problems (cont’d) event, 1–40 in connecting to CICS, 1–47 IBM sense codes, 1–46, A–6 LU names not recognized, 1–44 PU names not recognized, 1–43 terminating abnormally, 1–49 when circuit not available, 1–47 Traces, 3–1 to 3–5 when error messages received, 1–45 Circuit level, 3–1 when Gateway-ST unreachable, 1–47 Gateway Management, 3–1...

This manual is also suitable for:

Decnet sna gateway-st

Compaq DECnet SNA Gateway for Synchronous Transport Problem Solving

Preface

1 Solving Decnet SNA Gateway for Synchronous Transport Problems

2 Using Loopback Tests

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Compaq DECnet SNA Gateway for Synchronous Transport

This manual is also suitable for:

Table of Contents