Installation Verification

Loopback Configuration Requirements

The ACC product provides a loopback protocol module which can be used to run a loopback test to exercise the ACC multiplexer card, any attached panel, and the specified port. The loopback test is run using the loopback test feature of the zmntr utility. (Refer to the ACC Utilities Reference Guide.)

The test requires the following:

Loopback Configuration File

A loopback configuration file /opt/acc/cfg/loopback.answ is automatically created when the ACC Base Software was installed. It reflects the location of any ACC cards installed at the time swinstall was run. The ttgen utility is also automatically run on this file to create /opt/acc/cfg/loopback.tmem. Refer to ACC Installation and Configuration Guide, Chapter 2, if the ACC Mux cards have been moved within the system, or if additional cards have been added to the system.

Your ACC .answ file should look like the following:

#include "/opt/acc/cfg/ttgendefine"
ttgen
   Configuration
      system-name    "SNA/ACC Interface sample ttgen input file"
      program-zlu     100
      terminal-zlu    800
      logical-term    400
      physical-term   400
      buffer-pool     3000000
      logical-size    256
      queue-Limit     200
      transmit-limit  100
      unack-limit     5000
      port-limit      20000
      E1T1-Port-Limit 100000
      node-entry      1
 
 
Interface-Definition
   <card-type>  0    <bus:slot>  /opt/acc/<card-type>/loopback.zabs
 
 
  Port-Definition
      Port 0:0 RS232 57600 Int SDLC X1 NRZ
      Port 0:1 RS232 57600 Ext SDLC X1 NRZ
      Port 0:2 RS232 57600 Int SDLC X1 NRZ
      Port 0:3 RS232 57600 Ext SDLC X1 NRZ
      Port 0:4 RS232 57600 Int SDLC X1 NRZ
      Port 0:5 RS232 57600 Ext SDLC X1 NRZ
      Port 0:6 RS232 57600 Int SDLC X1 NRZ
      Port 0:7 RS232 57600 Ext SDLC X1 NRZ
 
 Terminal-Definition 
      Term 600 0:0 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS device"
      Term 601 0:1 HDLC.FRAME 0000h 0000h 41 0 0 0 0 "SNAPLUS device"
*          ^^^ ^^^            ^^^^^       ^^
*  ZLU _____|   |               |          |
*  mux:port_____|               |          |
*  poll word; use 0000h for     |          |
*    2-wire or 0080h for 4-wire_|          |
*  application number; 41 for SNAplus2_____|
 
 Node-Definition
      Local-Node     123
 
End$

	NOTE: Versions of SNA/ACC prior to B02.40 dynamically handled the creating of terminal definitions. Versions of SNA/ACC for 3.02 and above require the user to define terminals statically in the .answ files as illustrated in the example .answ file. You must add the Term entries to your .answ file and modify them appropriately for your configuration requirements.

Bringing Up ZCOM

Before any of the features of the ZCOM Mux Subsystem can be accessed, it must be started up by running zmasterd (located in /opt/acc/bin) with an appropriate .tmem file. The /opt/acc/cfg/loopback.tmem file should be used. Invoke zmasterd as follows:

% zmasterd cold /opt/acc/cfg/loopback.tmem

Messages indicating whether or not the ZCOM Mux subsystem was started successfully will be logged to the file /var/opt/acc/log/XXX.tlog, where XXX represents the day of the week, for example, mon.tlog and tue.tlog.

If any error is reported during the start up procedure, it may be necessary to stop the ZCOM subsystem by running:

% zmasterd stop

The error should then be addressed, and then the ZCOM subsystem should be restarted. Refer to the ACC Error Guide for detailed information about messages reported by zmlog.

SNA/ACC Software Verification

When it is determined that the ACC Multiplexer hardware and ACC Base Software are fully operational with no problems, the peer-to-peer test procedures in this section should be run to verify that the SNA/ACC installation is correct and the SNAplus2 software can work with it.

The SNAplus2 GUI, shown below (Figure 2-2), is convenient for this verification phase. If the SNAplus2 software is not running, issue the following command to manually start SNAplus2:

% /opt/sna/bin/snap start