Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
ACC Installation and Configuration Guide > Chapter 3 Protocol Configuration

Firmware Related Files

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The ACC product provides the following firmware related files:

Figure 3-1 Firmware Related Files

Firmware Related Files

The following sections describe the firmware related files and directories. Refer to these before creating any custom downloadable firmware files or custom ttgen configuration files.

Files in /opt/acc/cfg

This directory is where the ttgen configuration files are normally located, plus files that are necessary in creating the configuration files.

ttgendefine

The ttgen configuration files include this file by putting the following statement at the top of the file:

#include "/opt/acc/cfg/ttgendefine" 

This file contains symbolic definitions for a variety of configuration parameters that may be used in the ttgen configuration file.

zcomdevice.txt and zcomdevice

The device definition file zcomdevice.txt is an ASCII editable file containing default protocol configuration information. This file provides users with the convenience of an editable file for changing operational details of existing terminals or adding new terminals.

The binary file zcomdevice is the result of running the zdgen utility on the zcomdevice.txt file. After zdgen compiles the binary device file, it is available for use by ttgen. (Note that the zdgen and ttgen utilities expect these files to be in the /opt/acc/cfg directory.) Refer to the “ZDGEN - ZCOM Device Table Generator” chapter of the ACC Utilities Reference Guide for more information on the contents and use of these files.

sample_header

This file is provided for use by the acc_bld_lpbk script. It provides the “Configuration Parameters” section of the ttgen configuration files that are produced when acc_bld_lpbk is run.

loopback.answ

The ACC installation process automatically installs and configures the file loopback.answ when the product is installed. This file can also be created manually to reflect the currently installed hardware by running:

% cd /opt/acc/cfg
% /opt/acc/lbin/acc_bld_lpbk -t sample_header -o loopback.answ

This file configures the loopback protocol for each port on each mux that was installed in the system at the time the script was run.

Refer to Appendix A “Files, Utilities, and Daemons” for more information on using acc_bld_lpbk.

Refer to the “TTGEN - ZCOM System Table Generator” chapter of the ACC Utilities Reference Guide for more information on the .answ configuration file format.

loopback.tmem

This file is produced when the ttgen utility is run on the loopback.answ file. This file is automatically created during the ACC installation process. The loopback .tmem file must be recreated whenever the loopback.answ file is changed.

The file can be created/recreated by running:

% ttgen -o /opt/acc/cfg/loopback.answ /opt/acc/cfg/loopback.tmem

Refer to the “TTGEN - ZCOM System Table Generator” chapter of the ACC Utilities Reference Guide for more information on running ttgen.

Files in /opt/acc/protocol

This directory is where the protocol-specific relocatable firmware files are located. The ACC product provides the files as shown in Figure 3-1 “Firmware Related Files”.

The monitor.zrel protocol module is provided to be used in conjunction with the watch program. If the watch mux shutdown program is to be used on the system, the monitor.zrel relocatable must be included in the .zlnk file. Refer to the section watch Feature” for information on the watch program.

The testprot.zrel file provides the test loopback protocol module. It is suggested but not required that this file be referred to in all .zlnk files.

The other sys/*.zrel files provided with the ACC base product must be referenced in the .zlnk file, which is used to create the downloadable firmware file. These files may differ between ACC hardware platforms. Refer to the sample loopback.zlnk file provided with your software product.

Other relocatable protocol module files are also placed into this directory with the base product (such as the X.25 protocol and the HDLC protocols). They are provided for building the firmware download file. But the protocol modules are not enabled unless the ACC Protocols for Application Developers is also installed.

Files in /opt/acc/msg

This directory contains message files and help files which are used by the ZCOM utilities that are provided by the ACC product family. These files must be in this directory, and they should not be altered.

If an application program also makes use of the zmlog utility for logging its messages, its text file should also be placed in this directory.

Files in /opt/acc/sys

This directory contains all relocatable (zrel) files related to the ACC mux kernel software for the various ACC interface cards. These files must be in this directory, and they should not be altered.

Files in /opt/acc/<card-type>/

The directories /opt/acc/<card-type> contain the zabs, zlnk, and zmap files specific to the type of card as indicated by the directory name. The valid directory names are:

  • /opt/acc/z7200a/

  • /opt/acc/z7300a/

  • /opt/acc/z7340a/

  • /opt/acc/z7350a/

  • /opt/acc/z7400a/

The ACC base product ships the files loopback.zabs, loopback.zlnk, and loopback.zmap in these directories. A description of each file follows.

The loopback.zabs file is created when the zlink utility is run on the /opt/acc/<card-type>/loopback.zlnk file. This file is the downloadable firmware file which contains just the loopback protocol, and is the file that is referred to in the ttgen configuration file. The what utility can be used to identify what protocols are contained in this file.

When new protocol accessory products are installed on the system, new .zlnk files can be created to include these protocols. These new .zlnk files should have the .zabs files be created in this directory (see “Creating a Downloadable Firmware File” for information on creating a .zabs file).

The loopback.zlnk file is provided with the ACC product. It includes just the testprot.zrel loopback and monitor.zrel monitor protocols. The zlink utility can be used on this file to create a downloadable firmware file.

This file can be used as a template .zlnk file. When new protocol module products are installed, a new .zlnk file should be created (see “Creating a Downloadable Firmware File” to create a new .zlnk file).

The loopback.zmap file is created as a result of running the zlink utility on /opt/acc/<card-type>/loopback.zlnk. This file provides revision information about the core system relocatable files and protocol relocatable files which were linked together to produce a downloadable file.

Files in /var/opt/acc/log and /var/opt/acc/dmp

The /var/opt/acc/log directory is created during the installation process.

When the zmlog logging daemon is run, it creates text log files in this directory. This information is usually also logged to the system console, depending on how zmlog is run.

Refer to the ACC Error Guide, for information on interpreting the log messages. Refer to the “ZMLOG - Diagnostic Message Logging” chapter of the ACC Utilities Reference Guide for more information on zmlog.

The /var/opt/acc/dmp/ directory is used to store Mux interface card memory dumps. By default, this directory is not created during installation. This prevents card memory dumps from being uploaded should the card hardware/firmware fail. You should create this directory if you wish to have Mux memory dumps saved for HP analysis. The dump files could be over 15 Mbytes in size, depending on the type of ACC card. By default, if the "gzip" tool is accessible to zmon, the dump files will be created in compressed format (.gz files)

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2000 Hewlett-Packard Development Company, L.P.