HP Advanced Communications Controllers (ACC) Guide de l'utilisateur

Naviguer en ligne ou télécharger Guide de l'utilisateur pour Non HP Advanced Communications Controllers (ACC). HP Advanced Communications Controllers (ACC) Reference Guide Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 328
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs

Résumé du contenu

Page 1 - Edition 1

ACC Programmer’s Reference GuideEdition 1HP 9000 NetworkingManufacturing Part Number : Z7345-90008E0204© Copyright 2004 Hewlett-Packard Company, All

Page 2

Contents10

Page 3 - Legal Notices

ZCOM Tables and Data StructuresResponse RecordsChapter 3100RPBUFQ - Response buffer queueWhen a response carries data in addition to just a status or

Page 4

ZCOM Tables and Data StructuresQueue HeaderChapter 3 101Queue HeaderThe queue header area contains the descriptor block for all the ZCOM subsystem que

Page 5 - Printing History

ZCOM Tables and Data StructuresQueue HeaderChapter 3102QNMSG - Number on queueCounter of the number of messages on the queue. When this is zero the qu

Page 6 - Related Documentation

ZCOM Tables and Data StructuresQueue HeaderChapter 3 103is initialized from the Queue-Limit parameter in the TTGEN configuration file when the queue i

Page 7

ZCOM Tables and Data StructuresQueue HeaderChapter 3104QFLAG - Queue flagsThis field contains some indicators which may affect the processing of a que

Page 8

ZCOM Tables and Data StructuresQueue HeaderChapter 3 105QFDATA - Queue function dataQFUNC - Queue functionThese two fields have valid data only when t

Page 9

ZCOM Tables and Data StructuresData Buffer PoolChapter 3106Data Buffer PoolThe data buffer pool is part of the ZCOM memory structure. The size of data

Page 10 - Contents

ZCOM Tables and Data StructuresData Buffer PoolChapter 3 107of blocks in the pool (initially 2), the total number of bytes in the pool, and the number

Page 11 - 1ZCOM Subsystem

ZCOM Tables and Data StructuresData Buffer PoolChapter 3108Figure 3-8 Buffer Pool Layout (when first initialized)List HeadBlockPointerList TailBlockPo

Page 12 - Introduction

ZCOM Tables and Data StructuresData Buffer PoolChapter 3 109Free Buffer Header Structure (zfbh_type)The buffer header contains information about the b

Page 13 - ZCOM Software Overview

Chapter 1 111ZCOM Subsystem

Page 14

ZCOM Tables and Data StructuresData Buffer PoolChapter 3110BFFLAG - Buffer flagsThe use of the memory pool is based around a buffer flag field that in

Page 15

ZCOM Tables and Data StructuresData Buffer PoolChapter 3 111These pointers are used to link all the free blocks within the memory pool, to form a circ

Page 16

ZCOM Tables and Data StructuresMessage HeaderChapter 3112Message HeaderIn the buffer header (i.e., BFDATA pointer), there is a message header that des

Page 17 - ZCOM Concepts

ZCOM Tables and Data StructuresMessage HeaderChapter 3 113Message ID Header (zmid_type)The Message ID Header contains information used for delivery of

Page 18

ZCOM Tables and Data StructuresMessage HeaderChapter 3114MSTYPE - Message typeThis field contains the message type. If bit 3 of the message type is se

Page 19 - Terminal ZLUs

ZCOM Tables and Data StructuresMessage HeaderChapter 3 115MSRESP- Response codeThe response code is used in two ways. Firstly, for message types 2, 4,

Page 20

ZCOM Tables and Data StructuresMessage HeaderChapter 3116MTAGW1, MTAGW2 - Message tag wordsThese are application defined tag words that are passed una

Page 21 - User Interface

ZCOM Tables and Data StructuresMessage HeaderChapter 3 117This field contains the request code sent to or received from the Mux firmware on the interf

Page 22 - References

ZCOM Tables and Data StructuresMessage HeaderChapter 3118This tag parameter is used to carry protocol specific information from the application progra

Page 23 - 2 ZCOM Message Handling

ZCOM Tables and Data StructuresMessage HeaderChapter 3 119System Event Message (zevent_type)A System Event Message (SEM) is a special message generate

Page 24 - Overview

ZCOM SubsystemIntroductionChapter 112IntroductionThe ZCOM Subsystem consists of software and firmware that provide the base set of features for the AC

Page 25

ZCOM Tables and Data StructuresMessage HeaderChapter 3120This field will contain the ZCOM node number of the system that generated the event message.

Page 26 - Mapped ZLUs

ZCOM Tables and Data StructuresMessage HeaderChapter 3 121This field contains a numeric value indicating the status change. If the value is zero, then

Page 27 - Message Queuing

ZCOM Tables and Data StructuresMessage HeaderChapter 3122This event is generated whenever there is a change in the state of an ACC interface card. Thi

Page 28

ZCOM Tables and Data StructuresMessage HeaderChapter 3 123ZcSE_CARD_FAIL_RESTART - the ACC card indicated by the iftno field is being restarted due to

Page 29 - Priorities

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3124ZCOM Kernel DataThis is a kernel data structure shared by the LDM and DAM. Unlike the ZCOM

Page 30 - Multiplexing

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3 125Note that for EISA ACC the slot number is assigned to PDA variable in the DAM.resrvd2 Rese

Page 31 - Outbound Multiplexing

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3126HPANO - HPA value of I/F card (zhpano_type)The HPA value is setup by the DAM when HP-UX cre

Page 32 - Inbound Multiplexing

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3 127HACTIVE - Number of active requestsThis field contains the number of pending inter-driver

Page 33 - APPLICATION

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3128SYSThe SYS structure (ZCOM system global information, zsys_type) contains software status i

Page 34

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3 129RESET state). If so, an error will be returned to the application program. This mechanism

Page 35 - Error Handling

ZCOM SubsystemZCOM Software OverviewChapter 1 13ZCOM Software Overview Figure 1-1 on page 14 presents an architectural overview of the ZCOM Subsystem.

Page 36 - Chapter 236

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3130DEBUG - Debug levelThis field is used by the LDM to produce driver debug logs for its proce

Page 37 - Structures

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3 131MEMPTR, MEMSIZE -Kernel memory size pointersThese are pointers to the size of kernel memor

Page 38

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3132ZSINFO - ZCOM system information bufferThis is a data structure set up by the LDM when ZCOM

Page 39 - Memory Organization

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3 133LINFOThe LINFO structure (Lock Information, struct zlinfo) contains the ZCOM locks used gl

Page 40

ZCOM Tables and Data StructuresZCOM Kernel DataChapter 3134ZC_SLOCK - Super IFT spinlockThis lock protects against deadlock situations while multiple

Page 41

Chapter 4 1354 ZCOM C I/F Library Routines

Page 42 - ZCOM Header Structure

ZCOM C I/F Library RoutinesIntroductionChapter 4136IntroductionThe ZCOM C interface library routines provide an application program interface to the Z

Page 43

ZCOM C I/F Library RoutinesIntroductionChapter 4 137The following is a list of ZCOM C interface library routines:Initialization callzinit -ZCOM librar

Page 44

ZCOM C I/F Library RoutinesIntroductionChapter 4138Interface configuration callsZLU configuration callsData storage allocation callsZLU data transfer

Page 45

ZCOM C I/F Library RoutinesIntroductionChapter 4 139ZLU information callsUtility routineszsend -Send data buffer to ZLUltfind -Find specific logical t

Page 46

ZCOM SubsystemZCOM Software OverviewChapter 114Subsystem as separate products. The Protocol User’s Guides provided with these products must be used in

Page 47

ZCOM C I/F Library RoutinesIntroductionChapter 4140ZLU DefinitionThe zlu field of a <zaddr_type> parameter specifies the ZLU address. The checks

Page 48

ZCOM C I/F Library RoutinesMan PagesChapter 4 141Man PagesThe C-I/F man pages are provided in this section. They are in alphabetical order in similar

Page 49

ZCOM C I/F Library RoutinesGETDEVICE (3X)Chapter 4142GETDEVICE (3X)NAME getdevice – Read ZCOM device definitionsSYNOPSIS#include <zcom/zcomsys.h&g

Page 50

ZCOM C I/F Library RoutinesGETDEVICE (3X)Chapter 4 143See the NOTES section below for more information on using this routine in a multi-threaded appli

Page 51

ZCOM C I/F Library RoutinesGETDEVICE (3X)Chapter 4144PAR AMETER SRETURN VALUE Routine getdevice, when successful, returns a non-negative value, indica

Page 52 - Table 3-2 Queue Label Table

ZCOM C I/F Library RoutinesGETDEVICE (3X)Chapter 4 145 char dpname[8]; /* Protocol module name */} zdev_type;EXAMPLE #include <z

Page 53 - Table 3-3 Storage Label Table

ZCOM C I/F Library RoutinesGETDEVICE (3X)Chapter 4146SEE ALSO zdgen(1), malloc(3C)/opt/acc/cfg/zcomdevice Binary ZCOM device file created by ZDGEN, u

Page 54

ZCOM C I/F Library RoutinesLTFIND (3X)Chapter 4 147LTFIND (3X)NAME ltfind – Find specific logical terminal in a groupSYNOPSIS#include <zcom

Page 55 - Node Entries Table

ZCOM C I/F Library RoutinesLTFIND (3X)Chapter 4148Threads ConsiderationsThis routine may be called from a multi-threaded application using the POSIX

Page 56

ZCOM C I/F Library RoutinesLTFIND (3X)Chapter 4 149struct { zltt_type sys; char ext[ZCOM_MAXLSIZE]; /* Max allowable extension */ltt;Fo

Page 57

ZCOM SubsystemZCOM Software OverviewChapter 1 15Figure 1-2 presents another view of the ZCOM Subsystem which includes the relationships between the va

Page 58

ZCOM C I/F Library RoutinesLTFIND (3X)Chapter 4150FILESSEE ALSO zdgen(1), malloc(3C)/opt/acc/include/zcom/zcomsys.h ZCOM subsystem general include fi

Page 59 - ZLU Tables

ZCOM C I/F Library RoutinesLTQDGET (3X)Chapter 4 151LTQDGET (3X)NAME ltqdget – Retrieve data buffer in terminal data queueSYNOPSIS#include <z

Page 60 - Table 3-8 ZLU Type Values

ZCOM C I/F Library RoutinesLTQDGET (3X)Chapter 4152async-cancel unsafe The calling thread’s cancelability type must be PTHREAD_CANCEL_DEFERRED if canc

Page 61

ZCOM C I/F Library RoutinesLTQDGET (3X)Chapter 4 153PAR AMETER SNOTES Normally, the data queue number used should be allocated by ZMON (see the zltque

Page 62 - Logical Terminal Tables

ZCOM C I/F Library RoutinesLTQDGET (3X)Chapter 4154 /* error return code */}else { /* good return code */}FILESSEE ALSO ltqdput(3X), zltqueu

Page 63

ZCOM C I/F Library RoutinesLTQDPUT (3X)Chapter 4 155LTQDPUT (3X)NAME ltqdput – Store data buffer in terminal data queueSYNOPSIS#include <zcom/zcoms

Page 64

ZCOM C I/F Library RoutinesLTQDPUT (3X)Chapter 4156async-signal unsafe It cannot be called from a signal handler.fork unsafe It cannot be called by a

Page 65

ZCOM C I/F Library RoutinesLTQDPUT (3X)Chapter 4 157PAR AMETER SNOTES Normally, the data queue number used should be allocated by ZMON (see the man pa

Page 66

ZCOM C I/F Library RoutinesLTQDPUT (3X)Chapter 4158FILESSEE ALSO ltqdget(3X), zltqueue(3X), zltstore(3X), zltup(3X)/opt/acc/include/zcom/zcomsys.hZCOM

Page 67

ZCOM C I/F Library RoutinesMAKEZLUNAME (3X)Chapter 4 159MAKEZLUNAME (3X)NAME makezluname – Make a ZLU name with TTY name suffixSYNOPSIS#include <zc

Page 68 - Physical Terminal Tables

ZCOM SubsystemZCOM Software OverviewChapter 116The zmlog program is used to log error messages generated by the programs and daemons of the ZCOM Subsy

Page 69

ZCOM C I/F Library RoutinesMAKEZLUNAME (3X)Chapter 4160The libraries libzcom_c.a and libpthread.a must be linked into the calling program by giving th

Page 70 - PTUSER) (Continued)

ZCOM C I/F Library RoutinesMAKEZLUNAME (3X)Chapter 4 161For multi-threaded application, since all threads will be from the same TTY, if the threads us

Page 71

ZCOM C I/F Library RoutinesPTFIND (3X)Chapter 4162PTFIND (3X)NAME ptfind – Find a physical terminal within a groupSYNOPSIS#include <zcom/zc

Page 72

ZCOM C I/F Library RoutinesPTFIND (3X)Chapter 4 163Method 2: Retrieve the next terminal whose table has a sequence of matching bytes.This method compa

Page 73

ZCOM C I/F Library RoutinesPTFIND (3X)Chapter 4164Method 3: Retrieve the next terminal whose table has a sequence of matching bit patterns. This mode

Page 74

ZCOM C I/F Library RoutinesPTFIND (3X)Chapter 4 165PAR AMETER SRETURN VALUE Routine ptfind returns 0 if successful. Otherwise, if the physical termina

Page 75

ZCOM C I/F Library RoutinesPTFIND (3X)Chapter 4166else { /* good return code */}

Page 76

ZCOM C I/F Library RoutinesPTFIND (3X)Chapter 4 167FILES/opt/acc/include/zcom/zcomsys.h ZCOM system general include file, containing data types, data

Page 77 - Interface Table

ZCOM C I/F Library RoutinesZCLOS (3X)Chapter 4168ZCLOS (3X)NAME zclos - Delete program input ZLU SYNOPSIS#include <zcom/zcomsys.h>#include <

Page 78

ZCOM C I/F Library RoutinesZCLOS (3X)Chapter 4 169PAR AMETER SRETURN VALUE Routine zclos returns 0 if successful. Otherwise, a non-zero error code is

Page 79

ZCOM SubsystemZCOM ConceptsChapter 1 17ZCOM ConceptsThroughout this manual, references are made to terminal ZLU or just terminal. This does not mean a

Page 80

ZCOM C I/F Library RoutinesZCNTL (3X)Chapter 4170ZCNTL (3X)NAME zcntl – Send control message to terminal ZLUSYNOPSIS#include <zcom/zcomsys.h> #

Page 81

ZCOM C I/F Library RoutinesZCNTL (3X)Chapter 4 171Threads ConsiderationsThis routine may be called from a multi-threaded application using the POSIX (

Page 82

ZCOM C I/F Library RoutinesZCNTL (3X)Chapter 4172Modes 5 and 7 are only meaningful when rcode is 3. Some bits (when set) in the mode parameter can cau

Page 83

ZCOM C I/F Library RoutinesZCNTL (3X)Chapter 4 173NOTES 1. File /opt/acc/include/zcom/zcomsys.h contains the symbolic names for rcode (not all of them

Page 84

ZCOM C I/F Library RoutinesZCNTL (3X)Chapter 41746 Terminal Option Word

Page 85 - Table 3-16 CARD.MMP Structure

ZCOM C I/F Library RoutinesZCNTL (3X)Chapter 4 175For any i960 4-channel ACC card:Data structure: ztrq2_typeMust set RTYP bit = 1. This usually means

Page 86 - Table 3-17 CARD.BSP Structure

ZCOM C I/F Library RoutinesZCNTL (3X)Chapter 4176EXAMPLE#include <zcom/zcomsys.h>#include <zcom/zcomcall.h> int32 ierr;za

Page 87

ZCOM C I/F Library RoutinesZCNTL (3X)Chapter 4 177SEE ALSO zcomstatus(3X), zconfig(3X), zread(3X), zsend(3X), zopen(3X)./opt/acc/include/zcom/zcomcall

Page 88

ZCOM C I/F Library RoutinesZCOMERROR (3X)Chapter 4178ZCOMERROR (3X)NAME zcomerror – Return a formatted ZCOM error messageSYNOPSIS#include <zcom/zc

Page 89

ZCOM C I/F Library RoutinesZCOMERROR (3X)Chapter 4 179PAR AMETER SNOTES This routine reads a message file for the error message text. It uses the file

Page 90 - Chapter 390

ZCOM SubsystemZCOM ConceptsChapter 118Figure 1-3 on page 18 shows a sample set of program and terminal ZLUs, and their interaction with each other and

Page 91

ZCOM C I/F Library RoutinesZCOMERROR (3X)Chapter 4180EXAMPLE#include <zcom/zcomsys.h>#include <zcom/zcomcall.h>char *errmsg;

Page 92

ZCOM C I/F Library RoutinesZCOMLNAME (3X)Chapter 4 181ZCOMLNAME (3X)NAME zcomlname – Set up originator name for log messagesSYNOPSIS#include <zcom

Page 93

ZCOM C I/F Library RoutinesZCOMLNAME (3X)Chapter 4182PAR AMETER SRETURN VALUE Routine zcomlname has no return value.NOTES In a multi-threaded applicat

Page 94

ZCOM C I/F Library RoutinesZCOMLOG (3X)Chapter 4 183ZCOMLOG (3X)NAME zcomlog – Add a message to the ZCOM log fileSYNOPSIS#include <zcom/zcomsys.h&

Page 95

ZCOM C I/F Library RoutinesZCOMLOG (3X)Chapter 4184See the NOTES section for more information on using this routine in a multi-threaded application.as

Page 96

ZCOM C I/F Library RoutinesZCOMLOG (3X)Chapter 4 185PAR AMETER SRETURN VALUE Routine zcomlog has no return value.NOTES 1. The ZMLOG program retrieves

Page 97

ZCOM C I/F Library RoutinesZCOMLOG (3X)Chapter 41863. In a multi-threaded application, zcomlname is to be called only once by any one of the threads.

Page 98 - Response Records

ZCOM C I/F Library RoutinesZCOMLOG (3X)Chapter 4 187EXAMPLE#include <zcom/zcomsys.h>#include <zcom/zcomcall.h> uint32 error;int

Page 99

ZCOM C I/F Library RoutinesZCOMSTATUS (3X)Chapter 4188ZCOMSTATUS (3X)NAME zcomstatus – Return a formatted ZCOM status or error messageSYNOPSIS#include

Page 100

ZCOM C I/F Library RoutinesZCOMSTATUS (3X)Chapter 4 189PAR AMETER SNOTES This routine reads a message file for the status message text. It uses the fi

Page 101 - Queue Header

ZCOM SubsystemZCOM ConceptsChapter 1 19are maintained automatically by the ZCOM Subsystem. When a message is sent to a ZLU, the data is moved to a sys

Page 102

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4190ZCONFIG (3X)NAME zconfig – ZCOM Dynamic System Configuration (DSC)SYNOPSIS#include <zcom/zcoms

Page 103

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 191Threads ConsiderationsThis routine may be called from multi-threaded application using the POSIX (

Page 104 - Table 3-29 Queue Flag Format

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4192This is the node number of the remote (or local) ZCOM system where the configuration is to take pla

Page 105

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 193 uint16 card_addr; /* Card address of new hardware */ uint16 i

Page 106 - Data Buffer Pool

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4194Field header.config specifies the type of configuration. The interpretation of the header.action an

Page 107

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 195 } portret; struct { zaddr_type zaddr; /* Terminal ZLU */

Page 108 - Chapter 3108

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4196Configuration Dataheader.configZCOM_ZCONFIG_CNTL (DSC Control)header.actionheader.tag1, header.tag2

Page 109

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 197data.setctl.cfg_class Caller supplied type of reconfiguration. There is one predefined configurati

Page 110

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4198header.tag1,header.tag2Any values.data.setsys.sysnameNew runtime ZCOM system name. This field is us

Page 111

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 199Action ZcDSC_CREATE_IFT (2) allocates the internal data structures required for a new interface ca

Page 113 - Message ID Header (zmid_type)

ZCOM SubsystemZCOM ConceptsChapter 120level of priority. The Express Queue is used for extremely high-priority protocol dependent requests. The High-P

Page 114

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4200Configuration Dataheader.configZCOM_ZCONFIG_CARD (interface configuration)header.actionheader.tag1,

Page 115

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 201Response Datadata.cardret.iftnoThis is the interface card number as in the configuration data. It

Page 116

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4202Configuration Dataheader.configZCOM_ZCONFIG_PORT (port configuration)header.actionheader.tag1,heade

Page 117

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 203Unused spare field. For data alignment.data.setport.cnfgConfiguration data (32 bits). This field i

Page 118

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4204The baud rate is split between two 4-bit parameters (for compatibility reasons). If the Baud 1 para

Page 119

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 2050001 300 1001 38,4000010 600 1010 48,0000011 1,200 1011 57,6000100 2,400 1100 76,8000101 4,800 110

Page 120

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4206For the Z7300A (E1/T1) card:0 0 0 1 V.35 (Z7340A and Z7350A only)0 0 1 0 RS-449 (Z7340A and Z7350A

Page 121 - (ZCOM_SETYPE_RECONFIG)

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 2070110 Transparent (voice) modeFsync Value Other port for clock synchronization0 0 Port 00 1 Port 11

Page 122

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4208...0100 Reserved0101 E1 twisted pair DB9 120 ohm0110 E1 coax BNC 75 ohm0111 T1 twisted pair RJ45 10

Page 123

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 209data.setport.qlimitNew port limit (in bytes). This field is for action ZcDSC_SET_XMIT_LIMIT only.R

Page 124 - ZCOM Kernel Data

ZCOM SubsystemUser InterfaceChapter 1 21User InterfaceThe interface between the application programs and the ZCOM Subsystem is through the ZCOM ‘C’ Ap

Page 125

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4210data.portret.iftnodata.portret.portnoThese are the interface and port numbers as supplied in the or

Page 126

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 211Port Subchannel ConfigurationThe port subchannel configuration is only valid for the E1/T1 interfa

Page 127

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4212Action ZcDSC_DISABLE_SUBC disables a subchannel putting it into an inoperative state. All linked te

Page 128

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 213Configuration Dataheader.configZCOM_ZCONFIG_PORTSC (port and subchannel configuration)header.actio

Page 129

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4214data.setportsc.rcodeThis field is used for actions ZcDSC_ALL_PARMS, ZcDSC_CFG_MODE, ZcDSC_BAUD_RATE

Page 130

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 215A RTI (Receive Timeslot Inhibit) bit value of ‘1’ causes all data received in this timeslot to be

Page 131

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4216data.setportsc.ptcfg->ptinfo.subchb.spec[ ]Subchannel specification data: used for actions ZcDSC

Page 132

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 217Response Datadata.portscret.iftno,data.portscret.portno,data.portscret.subchnoThese are the interf

Page 133

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4218The error or status message text may be fetched using zcomstatus (3X) with req = ZCOM_MRQCODE_PORT

Page 134

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 219Terminal ConfigurationThere are 5 terminal configuration actions. They are for altering various in

Page 135 - 4 ZCOM C I/F Library Routines

ZCOM SubsystemReferencesChapter 122ReferencesThe following manuals should be referred to when using the ZCOM application interface:• ACC Installation

Page 136

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4220header.actionheader.tag1,header.tag2Any values.ZcDSC_CREATE_LTT_PTT (1) - Create a new terminal (LT

Page 137 - Initialization call

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 221data.setterm.zaddrZLU of the related terminal. The “node” field is not used. For action 1 and 2, i

Page 138 - ZLU data transfer calls

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4222Logical terminal information. This contains the logical terminal information of the newly created t

Page 139 - Utility routines

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 223Response Datadata.termret.zaddrThis is the terminal ZLU which has been successfully created or mod

Page 140 - ZLU Definition

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4224 unsigned int set0_2 : 4; /* Reserved, must be 0 */ unsigned int pmode : 4;

Page 141 - Man Pages

ZCOM C I/F Library RoutinesZCONFIG (3X)Chapter 4 225FILES /opt/acc/include/zcom/zcomsys.h ZCOM subsystem general include file, containing data types,

Page 142 - GETDEVICE (3X)

ZCOM C I/F Library RoutinesZEVENT_RCVR (3X)Chapter 4226ZEVENT_RCVR (3X)NAME zevent_rcvr – Set up a program ZLU to receive ZCOM alarms and eventsSYNOPS

Page 143 - Chapter 4 143

ZCOM C I/F Library RoutinesZEVENT_RCVR (3X)Chapter 4 227async-cancel unsafe The calling thread’s cancelability type must be PTHREAD_CANCEL_DEFERRED if

Page 144

ZCOM C I/F Library RoutinesZEVENT_RCVR (3X)Chapter 4228PAR AMETER Srzap ZCOM address of the receiver program (required).action Type of action to perfo

Page 145

ZCOM C I/F Library RoutinesZEVENT_RCVR (3X)Chapter 4 229einfop This data structure contains any event class specific information needed to carry out t

Page 146

Chapter 2 232 ZCOM Message Handling

Page 147 - LTFIND (3X)

ZCOM C I/F Library RoutinesZEVENT_RCVR (3X)Chapter 4230NOTES When an Application program issues a zread call, it can differentiate the type of informa

Page 148

ZCOM C I/F Library RoutinesZEVENT_RCVR (3X)Chapter 4 231RETURN VALUE Routine zevent_rcvr returns 0 if successful. Otherwise, a non-zero error code is

Page 149

ZCOM C I/F Library RoutinesZEVENT_RCVR (3X)Chapter 4232EXAMPLE#include <zcom/zcomsys.h>#include <zcom/zcomcall.h>int ierr;zaddr_

Page 150

ZCOM C I/F Library RoutinesZGET_SHRCVR_LIST (3X)Chapter 4 233ZGET_SHRCVR_LIST (3X)NAME zget_shrcvr_list – Get list of current shared receiversSYNOPSIS

Page 151 - LTQDGET (3X)

ZCOM C I/F Library RoutinesZGET_SHRCVR_LIST (3X)Chapter 4234PAR AMETER Sfork unsafe It cannot be called by a child process after fork(2) but before ex

Page 152

ZCOM C I/F Library RoutinesZGET_SHRCVR_LIST (3X)Chapter 4 235RETURN VALUE Routine zget_shrcvrs_list returns 0 if successful. Otherwise, a non-zero err

Page 153

ZCOM C I/F Library RoutinesZINFO (3X)Chapter 4236ZINFO (3X)NAME zinfo – Get ZCOM table informationSYNOPSIS#include <zcom/zcomsys.h>#include &l

Page 154 - /* good return code */

ZCOM C I/F Library RoutinesZINFO (3X)Chapter 4 237PAR AMETER Szap ZCOM address pointer. The node field is used to indicate from which node to retrieve

Page 155

ZCOM C I/F Library RoutinesZINFO (3X)Chapter 4238NOTES The returned logical terminal table (mode = ZcLTT_TBL) consists of the basic table and the logi

Page 156

ZCOM C I/F Library RoutinesZINFO (3X)Chapter 4 239/opt/acc/include/zcom/zcomcall.h ZCOM routine function prototypes (requires ANSI C compilation).

Page 157

ZCOM Message HandlingOverviewChapter 224OverviewZCOM message handling is achieved through logical constructs called ZLUs which maintain queues for mes

Page 158

ZCOM C I/F Library RoutinesZINIT (3X)Chapter 4240ZINIT (3X)NAME zinit – ZCOM routine initializationSYNOPSIS#include <zcom/zcomsys.h>#include &

Page 159 - MAKEZLUNAME (3X)

ZCOM C I/F Library RoutinesZINIT (3X)Chapter 4 241PAR AMETER S sip (Return Param) ZCOM system information data structure containing the following fiel

Page 160

ZCOM C I/F Library RoutinesZINIT (3X)Chapter 42424. In a multi-threaded application, if this routine is called the second time by a thread while some

Page 161

ZCOM C I/F Library RoutinesZLTMG (3X)Chapter 4 243ZLTMG (3X)NAME zltmg – Move a logical terminal between groupsSYNOPSIS#include <zcom/zcomsys.h>

Page 162 - PTFIND (3X)

ZCOM C I/F Library RoutinesZLTMG (3X)Chapter 4244PAR AMETER SNOTES In the ZCOM subsystem, a group of logical terminals may be defined to link to a sin

Page 163

ZCOM C I/F Library RoutinesZLTMX (3X)Chapter 4 245ZLTMX (3X)NAME zltmx – Control logical terminal multiplexingSYNOPSIS#include <zcom/zcomsys.h>

Page 164

ZCOM C I/F Library RoutinesZLTMX (3X)Chapter 4246PAR AMETER SNOTES For a more detailed description of the multiplexing facilities available under ZCOM

Page 165

ZCOM C I/F Library RoutinesZLTMX (3X)Chapter 4 247FILES/opt/acc/include/zcom/zcomsys.h ZCOM system general include file, containing data types, data s

Page 166 - Chapter 4166

ZCOM C I/F Library RoutinesZLTQUEUE (3X)Chapter 4248ZLTQUEUE (3X)NAME zltqueue – Logical data queue allocationSYNOPSIS#include <zcom/zcomsys.h>

Page 167

ZCOM C I/F Library RoutinesZLTQUEUE (3X)Chapter 4 249PAR AMETER SNOTES The data queue returned should only be used for terminals within the specified

Page 168 - ZCLOS (3X)

ZCOM Message HandlingZLU DefinitionChapter 2 25ZLU DefinitionThere are three types of ZLUs. These are: •Program• Terminal (or remote device via a comm

Page 169

ZCOM C I/F Library RoutinesZLTQUEUE (3X)Chapter 4250Queues 1, 3, and 4 are allocated for application 30, and queue 2 is allocated for global usage in

Page 170 - ZCNTL (3X)

ZCOM C I/F Library RoutinesZLTQUEUE (3X)Chapter 4 251EXAMPLE#include <zcom/zcomsys.h>#include <zcom/zcomcall.h>int32 ierr

Page 171

ZCOM C I/F Library RoutinesZLTSTORE (3X)Chapter 4252ZLTSTORE (3X)NAME zltstore – Logical data storage allocationSYNOPSIS#include <zcom/zcomsys.h&g

Page 172

ZCOM C I/F Library RoutinesZLTSTORE (3X)Chapter 4 253fork unsafe It cannot be called by a child process after fork(2) but before exec(2).

Page 173

ZCOM C I/F Library RoutinesZLTSTORE (3X)Chapter 4254PAR AMETER SNOTES The returned offset indicates the start of the usable data area, with a size as

Page 174 - 6 Terminal Option Word

ZCOM C I/F Library RoutinesZLTSTORE (3X)Chapter 4 255RETURN VALUE Routine zltstore returns 0 if successful. Otherwise, a non-zero error code is return

Page 175 - Data structure: ztrq2_type

ZCOM C I/F Library RoutinesZLTSTORE (3X)Chapter 4256EXAMPLE#include <zcom/zcomsys.h>#include <zcom/zcomcall.h>int32 ierr;uint32

Page 176

ZCOM C I/F Library RoutinesZLTUP (3X)Chapter 4 257ZLTUP (3X)NAME zltup – Update logical terminal table SYNOPSIS#include <zcom/zcomsys.h>#includ

Page 177

ZCOM C I/F Library RoutinesZLTUP (3X)Chapter 4258PAR AMETER SNOTES The offset returned by zltstore may be passed to zltup to update the allocated stor

Page 178 - ZCOMERROR (3X)

ZCOM C I/F Library RoutinesZLTUP (3X)Chapter 4 259int32 len;int32 offset;if (ierr = zltup (&zaddr, ibuf, len, offset)) {

Page 179

ZCOM Message HandlingZLU DefinitionChapter 226Mapped ZLUsAll messages addressed to a particular ZLU will be redirected to the alternate ZLU specified

Page 180

ZCOM C I/F Library RoutinesZLUOPEN (3X)Chapter 4260ZLUOPEN (3X)NAME zluopen – Open a ZLU fileSYNOPSIS#include <zcom/zcomsys.h>#include <zco

Page 181 - ZCOMLNAME (3X)

ZCOM C I/F Library RoutinesZLUOPEN (3X)Chapter 4 261Threads ConsiderationsThis routine may be called from a multi-threaded application using the POSIX

Page 182

ZCOM C I/F Library RoutinesZLUOPEN (3X)Chapter 4262 /* good return code */}NOTES The ZLU associated device files are kept in the /dev/zcom direc

Page 183 - ZCOMLOG (3X)

ZCOM C I/F Library RoutinesZLUOPEN (3X)Chapter 4 263FILESSEE ALSO select(2), close(2). /opt/acc/include/zcom/zcomsys.h ZCOM subsystem general include

Page 184

ZCOM C I/F Library RoutinesZMAPR (3X)Chapter 4264ZMAPR (3X)NAME zmapr – Set up ZLU mapping configurationSYNOPSIS#include <zcom/zcomsys.h>#inclu

Page 185

ZCOM C I/F Library RoutinesZMAPR (3X)Chapter 4 265PAR AMETER SNOTES On a successful return from zmapr, accessing the source ZLU is actually directed t

Page 186

ZCOM C I/F Library RoutinesZNAME (3X)Chapter 4266ZNAME (3X)NAME zname – Find ZLU number from ZLU nameSYNOPSIS#include <zcom/zcomsys.h>#include

Page 187

ZCOM C I/F Library RoutinesZNAME (3X)Chapter 4 267async-signal unsafe It cannot be called from a signal handler.fork unsafe It cannot be called by a c

Page 188 - ZCOMSTATUS (3X)

ZCOM C I/F Library RoutinesZNAME (3X)Chapter 4268PAR AMETER SRETURN VALUE Routine zname returns 0 if successful. Otherwise, a non-zero error code is r

Page 189

ZCOM C I/F Library RoutinesZNAME (3X)Chapter 4 269FILESSEE ALSO zopen(3X), makezluname(3X)/opt/acc/include/zcom/zcomsys.h ZCOM subsystem general incl

Page 190 - ZCONFIG (3X)

ZCOM Message HandlingMessage QueuingChapter 2 27Message QueuingEach program ZLU (either primary or auxiliary) has a single input queue on which messag

Page 191

ZCOM C I/F Library RoutinesZOPEN (3X)Chapter 4270ZOPEN (3X)NAME zopen – Create ZLU program input queueSYNOPSIS#include <zcom/zcomsys.h>#include

Page 192

ZCOM C I/F Library RoutinesZOPEN (3X)Chapter 4 271The libraries libzcom_c.a and libpthread.a must be linked into the calling program by giving the opt

Page 193

ZCOM C I/F Library RoutinesZOPEN (3X)Chapter 4272Threads ConsiderationsThis routine may be called from a multi-threaded application using the POSIX (1

Page 194

ZCOM C I/F Library RoutinesZOPEN (3X)Chapter 4 273NOTES The first zopen call that a program makes will define the primary ZLU irrespective of the valu

Page 195

ZCOM C I/F Library RoutinesZPEEK (3X)Chapter 4274ZPEEK (3X)NAME zpeek – Read data from ZLU without disturbing input queueSYNOPSIS#include <zcom/zc

Page 196 - Any values

ZCOM C I/F Library RoutinesZPEEK (3X)Chapter 4 275Threads ConsiderationsThis routine may be called from a multi-threaded application using the POSIX (

Page 197

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4276ZPORT (3X)NAME zport – ACC interface card port configurationSYNOPSIS#include <zcom/zcomsys.h>

Page 198

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4 277Threads Considerations This routine may be called from multi-threaded application using the POSIX (1

Page 199

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4278PAR AMETER S iftno ACC MUX interface number.portno Port number in the ACC interface card:rcode Requ

Page 200

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4 279The status message text may be fetched using zcomstatus(3X) (req = ZCOM_MRQCODE_PORT, or 11).cnfg C

Page 201

ZCOM Message HandlingMessage QueuingChapter 228Queues for terminal ZLUs are located in the physical terminal tables in the ZCOM memory area as shown i

Page 202

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4280Ecode Value Operating mode0 0 Sync mode0 1 Async 1 stop1 0 Async 1.5 stop bits1 1 Async 2 stop bitsPa

Page 203

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4 281The baud rate is split between two 4-bit parameters (for compatibility reasons). If the Baud 1 param

Page 204

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4282The Z7300A or Z7330A E1/T1 card uses the following configuration:0 0 0 0 RS232 Mode0 1 0 0 RS422 Mode

Page 205

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4 2830011 T1: F72 - Remote Switch Mode0100 E1: DF - Doubleframe0101 E1: MF - CRC Multiframe0110 Tr

Page 206 - For the Z7300A (E1/T1) card:

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4284NOTES 1. Notice that it is possible to change only one byte of the configuration word by using an ap

Page 207

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4 285When zport returns a zero error code, the return status stat indicates the completion status: zero m

Page 208

ZCOM C I/F Library RoutinesZPORT (3X)Chapter 4286EXAMPLE This example puts an E1/T1 port into “loopback” (tristate) mode.#include <zcom/zcomsys

Page 209

ZCOM C I/F Library RoutinesZPTUP (3X)Chapter 4 287ZPTUP (3X)NAME zptup - Update physical terminal table user areaSYNOPSIS#include <zcom/zcomsys.h&

Page 210

ZCOM C I/F Library RoutinesZPTUP (3X)Chapter 4288PAR AMETER SRETURN VALUE Routine zptup returns 0 if successful. Otherwise, a non-zero error code is r

Page 211

ZCOM C I/F Library RoutinesZQMVE (3X)Chapter 4 289ZQMVE (3X)NAME zqmve – Move message from one ZLU to anotherSYNOPSIS#include <zcom/zcomsys.h>#

Page 212

ZCOM Message HandlingPrioritiesChapter 2 29PrioritiesPriorities only apply to messages that are destined for terminals. Messages to program ZLUs are s

Page 213

ZCOM C I/F Library RoutinesZQMVE (3X)Chapter 4290PAR AMETER SRETURN VALUE Routine zqmve returns 0 if successful. Otherwise, a non-zero error code is r

Page 214

ZCOM C I/F Library RoutinesZQMVE (3X)Chapter 4 291EXAMPLEExample 1:#include <zcom/zcomsys.h>#include <zcom/zcomcall.h>int32

Page 215 - Chapter 4 215

ZCOM C I/F Library RoutinesZQSZE (3X)Chapter 4292ZQSZE (3X)NAME zqsze – Read ZLU input queue sizeSYNOPSIS#include <zcom/zcomsys.h>#include <

Page 216

ZCOM C I/F Library RoutinesZQSZE (3X)Chapter 4 293PAR AMETER SzapZCOM addresszqhdp (Return param)ZCOM queue header data structure. This structure has

Page 217

ZCOM C I/F Library RoutinesZQSZE (3X)Chapter 4294RETURN VALUE Routine zqsze returns 0 if successful. Otherwise, a non-zero error code is returned. See

Page 218 - Chapter 4218

ZCOM C I/F Library RoutinesZQSZE (3X)Chapter 4 295EXAMPLE#include <zcom/zcomsys.h>#include <zcom/zcomcall.h> int32 ierr;z

Page 219

ZCOM C I/F Library RoutinesZREAD (3X)Chapter 4296ZREAD (3X)NAME zread – Read from ZLUSYNOPSIS#include <zcom/zcomsys.h>#include <zcom/zcomca

Page 220

ZCOM C I/F Library RoutinesZREAD (3X)Chapter 4 297fork unsafe It cannot be called by a child process after fork(2) but before exec(2).

Page 221

ZCOM C I/F Library RoutinesZREAD (3X)Chapter 4298PAR AMETER Szap Pointer to program ZCOM address. Source to get input messages.mode ZcREAD_W_WAIT (0)

Page 222 - Chapter 4222

ZCOM C I/F Library RoutinesZREAD (3X)Chapter 4 299NOTES 1. If zsend(3X) was used to send data using modes 1, 2, 5, or 7, then the input ZLU queue may

Page 223

3Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to th

Page 224

ZCOM Message HandlingMultiplexingChapter 230MultiplexingThe multiplexing feature of ZCOM allows more than one logical terminal to be mapped to a singl

Page 225

ZCOM C I/F Library RoutinesZREAD (3X)Chapter 43003. A System Event Message (SEM) is generated by the ZCOM subsystem in response to special events that

Page 226 - ZEVENT_RCVR (3X)

ZCOM C I/F Library RoutinesZREAD (3X)Chapter 4 3015. The type of message received is returned in mhp->mid.mstype. Its values are as follows (define

Page 227

ZCOM C I/F Library RoutinesZREAD (3X)Chapter 4302 /* error return code */}else { /* good return code */}NOTE Check zmhd.mid.mstype to de

Page 228

ZCOM C I/F Library RoutinesZREAD (3X)Chapter 4 303FILESSEE ALSO zevent_rcvr(3X), zpeek(3X), zset_rcvr(3X), zsend(3X), ztimr(3X), zcomstatus(3X)./opt/a

Page 229

ZCOM C I/F Library RoutinesZRNTIMER (3X)Chapter 4304ZRNTIMER (3X)NAME zrntimer – Set timeout for remote node accessSYNOPSIS#include <zcom/zcomsys.

Page 230

ZCOM C I/F Library RoutinesZRNTIMER (3X)Chapter 4 305See the NOTES section below for more information on using this routine in a multi-threaded applic

Page 231

ZCOM C I/F Library RoutinesZRNTIMER (3X)Chapter 4306 /* good return code */}FILES/opt/acc/include/zcom/zcomsys.h ZCOM system general include fil

Page 232

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4 307ZSEND (3X)NAME zsend – Send data buffer to a ZLUSYNOPSIS#include <zcom/zcomsys.h> #include &

Page 233 - ZGET_SHRCVR_LIST (3X)

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4308cancellation point Thread cancellation can occur when a thread calls this routine.async-cancel unsafe

Page 234

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4 309PAR AMETER Szap Pointer to ZCOM address. The destination to where the data is sent.mode Completion c

Page 235

ZCOM Message HandlingMultiplexingChapter 2 31Outbound MultiplexingThe multiplexing program uses the zread call to determine the origin of the message,

Page 236 - ZINFO (3X)

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4310NOTES If mhp is specified (i.e., a non-NULL pointer), some header fields must be set up by the caller

Page 237

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4 311If Bit ZCOM_ZSEND_NOMX (0x4000) of mode is set and the request is to a outbound-multiplexed terminal

Page 238

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4312Apart from the special bits, the mode value indicates the requested completion status of the write: *

Page 239 - Chapter 4 239

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4 313The following data structures are used for the zsend call. See /opt/acc/include/zcom/zcomsys.h for f

Page 240 - ZINIT (3X)

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4314 #define ZCOM_MSTYPE_RSLT 6 /* Response from local terminal */ #define ZCOM_MSTYPE_

Page 241

ZCOM C I/F Library RoutinesZSEND (3X)Chapter 4 315RETURN VALUE Routine zsend returns 0 if successful. Otherwise, a non-zero error code is returned. Se

Page 242

ZCOM C I/F Library RoutinesZSETQL (3X)Chapter 4316ZSETQL (3X)NAME zsetql – Set buffer queue limitSYNOPSIS#include <zcom/zcomsys.h>#include <

Page 243 - ZLTMG (3X)

ZCOM C I/F Library RoutinesZSETQL (3X)Chapter 4 317PAR AMETER Szap ZCOM address.mode Type of queue:ZcPROGRAM_Q (0) - Program input queueZcLOGICAL_TERM

Page 244

ZCOM C I/F Library RoutinesZSETQL (3X)Chapter 4318RETURN VALUE Routine zsetql returns 0 if successful. Otherwise, a non-zero error code is returned. S

Page 245 - ZLTMX (3X)

ZCOM C I/F Library RoutinesZSETQL (3X)Chapter 4 319NOTES 1. Queue limit does not affect data messages that are already in a queue. If the new limit is

Page 246

ZCOM Message HandlingMultiplexingChapter 232If the ZCOM_LTFLAG_OMX bit is set in the LTFLAG word of the logical terminal table, then a logical termina

Page 247

ZCOM C I/F Library RoutinesZSETQL (3X)Chapter 4320FILES/opt/acc/include/zcom/zcomsys.h ZCOM subsystem general include file, containing data types, da

Page 248 - ZLTQUEUE (3X)

ZCOM C I/F Library RoutinesZSET_RCVR (3X)Chapter 4 321ZSET_RCVR (3X)NAME zset_rcvr – Set up program ZLU as message receiver for a terminal ZLUSYNOPSIS

Page 249

ZCOM C I/F Library RoutinesZSET_RCVR (3X)Chapter 4322receiver of the incoming messages. Use of this feature does not require that a primary receiver b

Page 250

ZCOM C I/F Library RoutinesZSET_RCVR (3X)Chapter 4 323Threads ConsiderationsThis routine may be called from a multi-threaded application using the POS

Page 251

ZCOM C I/F Library RoutinesZSET_RCVR (3X)Chapter 4324NOTES Usually, an application uses only mode ZcNORMAL to set up itself as the receiver for normal

Page 252 - ZLTSTORE (3X)

ZCOM C I/F Library RoutinesZSET_RCVR (3X)Chapter 4 325EXAMPLE#include <zcom/zcomsys.h>#include <zcom/zcomcall.h>int32 ierr;

Page 253 - Chapter 4 253

ZCOM C I/F Library RoutinesZTIMR (3X)Chapter 4326ZTIMR (3X)NAME ztimr – Enable/disable ZLU timerSYNOPSIS#include <zcom/zcomsys.h>#include <

Page 254

ZCOM C I/F Library RoutinesZTIMR (3X)Chapter 4 327RETURN VALUE Routine ztimr returns 0 if successful. Otherwise, a non-zero error code is returned. Se

Page 255

ZCOM C I/F Library RoutinesZTIMR (3X)Chapter 4328NOTES A timer value of zero will cancel the timer processing on the specified ZLU. The ztimr call cau

Page 256

ZCOM Message HandlingMultiplexingChapter 2 33The inbound multiplexing program has the task of receiving all messages from the physical terminal. It de

Page 257 - ZLTUP (3X)

ZCOM Message HandlingTerminal StateChapter 234Terminal StateWithin the ZCOM subsystem, the terminal state may be either enabled or disabled, activated

Page 258

ZCOM Message HandlingError HandlingChapter 2 35Error HandlingIn the normal functioning of ZCOM, transmission errors on messages to terminal ZLUs are h

Page 259

ZCOM Message HandlingError HandlingChapter 236

Page 260 - ZLUOPEN (3X)

Chapter 3 373ZCOM Tables and Data Structures

Page 261

ZCOM Tables and Data StructuresIntroductionChapter 338IntroductionThis chapter gives a detailed description of the ZCOM subsystem memory organization

Page 262 - /* good return code */

ZCOM Tables and Data StructuresMemory OrganizationChapter 3 39Memory Organization The ZCOM Logical Device Manager (LDM driver) reserves a contiguous b

Page 263

4This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. ©copyrigh

Page 264 - ZMAPR (3X)

ZCOM Tables and Data StructuresDifferences in 32-bit and 64-bit Data StructuresChapter 340Differences in 32-bit and 64-bit Data StructuresHP-UX suppor

Page 265

ZCOM Tables and Data StructuresDifferences in 32-bit and 64-bit Data StructuresChapter 3 41NOTE The following sections document the data structures us

Page 266 - ZNAME (3X)

ZCOM Tables and Data StructuresZCOM Header StructureChapter 342ZCOM Header StructureThe ZCOM Header structure holds the system parameters and pointers

Page 267

ZCOM Tables and Data StructuresZCOM Header StructureChapter 3 43HNCARD Number of interface tables uns.short 2HNRESP Number of response records uns.sho

Page 268

ZCOM Tables and Data StructuresZCOM Header StructureChapter 344HNDPID ZNODE Process ID int 4HNDSIG ZNODE required signal int 4HNIDLE ZNODE idle timer

Page 269

ZCOM Tables and Data StructuresZCOM Header StructureChapter 3 45HLABEL - ZMON identifier labelThe identifier label contains the word ‘ZMON’ and provid

Page 270 - ZOPEN (3X)

ZCOM Tables and Data StructuresZCOM Header StructureChapter 346This pointer contains the starting physical kernel memory address of the ZCOM subsystem

Page 271

ZCOM Tables and Data StructuresZCOM Header StructureChapter 3 47HLTDSZE - Logical terminal table LDATA buffer sizeThis specifies the size of the LDATA

Page 272

ZCOM Tables and Data StructuresZCOM Header StructureChapter 348HPNTBL - Node Table pointer (znode_type *)This is a pointer to the first entry in the N

Page 273

ZCOM Tables and Data StructuresZCOM Header StructureChapter 3 49file. The default limit may be overridden during a zopen() by specifying a non-zero va

Page 274 - ZPEEK (3X)

5Printing HistoryThe manual publishing date and part number indicate its current edition. The publishing date will change when a new edition is publ

Page 275

ZCOM Tables and Data StructuresZCOM Header StructureChapter 350HCTOTAL - Total number of Dynamic System Configuration (DSC) requestsThis field contain

Page 276 - ZPORT (3X)

ZCOM Tables and Data StructuresZCOM Header StructureChapter 3 51HNDSIG - ZNODE signal numberContains the type of signal to use when informing ZNODE of

Page 277

ZCOM Tables and Data StructuresZCOM Header StructureChapter 352HLCLND - Local node numberThe node number of the local ZCOM subsystem. If the Node-Defi

Page 278

ZCOM Tables and Data StructuresZCOM Header StructureChapter 3 53HLTSTB - Storage label tableThe storage label entry indicates the ownership of an appl

Page 279

ZCOM Tables and Data StructuresZCOM Header StructureChapter 354issues a transmit request to the E1/T1 card and the card does not have enough free buff

Page 280

ZCOM Tables and Data StructuresNode Entries TableChapter 3 55Node Entries TableThe Node Entries table contains information about the remote ZCOM syste

Page 281

ZCOM Tables and Data StructuresNode Entries TableChapter 356FLAGS - Node status and internal flagsThis bit-field structure contains bits to maintain s

Page 282

ZCOM Tables and Data StructuresNode Entries TableChapter 3 57be sent to each program in this linked list. That is, those applications that have issued

Page 283

ZCOM Tables and Data StructuresNode Entries TableChapter 358this link is currently up or not. If the link is down (status = 0), the ZNODE daemon will

Page 284

ZCOM Tables and Data StructuresZLU TablesChapter 3 59ZLU TablesThe ZCOM logical unit table relates a terminal device or a program queue with a number

Page 285

6Related DocumentationThe documentation available for the Multiprotocol ACC family of products includes the following hardware and software manuals:Ha

Page 286

ZCOM Tables and Data StructuresZLU TablesChapter 360ZCKSUM - ZLU checksumThe checksum is used as an integrity check to ensure that a ZLU has not been

Page 287 - ZPTUP (3X)

ZCOM Tables and Data StructuresZLU TablesChapter 3 61If the ZLU is not type 3, ZMPZCS is set to zero. Otherwise, this contains the checksum of the map

Page 288

ZCOM Tables and Data StructuresLogical Terminal TablesChapter 362Logical Terminal TablesThe Logical Terminal Table (LTT) pages contain the logical con

Page 289 - ZQMVE (3X)

ZCOM Tables and Data StructuresLogical Terminal TablesChapter 3 63This is followed by LTUSER - the user maintainable area - which consists of the fiel

Page 290

ZCOM Tables and Data StructuresLogical Terminal TablesChapter 364LTZLU - Terminal ZLU numberThis is the ZLU number of the owning terminal.LTZCS - Own

Page 291

ZCOM Tables and Data StructuresLogical Terminal TablesChapter 3 65LTTYPE - Logical terminal typeThe logical terminal type is used to describe the mess

Page 292 - ZQSZE (3X)

ZCOM Tables and Data StructuresLogical Terminal TablesChapter 366LTZSH RC VRS - Pointer to a linked list of indirect shared receiversThis field contai

Page 293

ZCOM Tables and Data StructuresLogical Terminal TablesChapter 3 67LTSTAT - Logical statusContains the status of the logical terminal. This entry is ma

Page 294

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 368Physical Terminal TablesThe physical terminal table (zptt_type) contains information

Page 295

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 3 69PTTXLA Pointer to next PTT on high priority listpointer 8PTTXQA High priority trans

Page 296 - ZREAD (3X)

7Contents1. ZCOM SubsystemIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page 297 - Chapter 4 297

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 370PTZLU - Owning terminal ZLU numberPTZCS - Owning terminal ZLU checksumThe terminal Z

Page 298

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 3 71This field contains the firmware terminal number this terminal ZLU is associated wi

Page 299

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 372setting bit 1 of the input message tag byte. If there are no shared control receiver

Page 300

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 3 73This queue contains the high priority transmit requests waiting to be sent. It also

Page 301

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 374The content of this field is as follows:Figure 3-4 Terminal Status Field PTDRSTThe I

Page 302

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 3 75PTTYPE - Terminal type (physical)Protocol module terminal type. It is initially set

Page 303

ZCOM Tables and Data StructuresPhysical Terminal TablesChapter 376PTCWCT - Terminal control write counterThis counter is incremented by the driver eve

Page 304 - ZRNTIMER (3X)

ZCOM Tables and Data StructuresInterface TableChapter 3 77Interface TableThe interface table shown in Table 3-13 is a structure that has one instance

Page 305

ZCOM Tables and Data StructuresInterface TableChapter 378imaxterms Max. # of terminals per card uns.short 2ifname Firmware download file name char [25

Page 306

ZCOM Tables and Data StructuresInterface TableChapter 3 79In the following definitions of the different fields, there are references to $PORT, $FIRQ a

Page 307

Contents8Queue Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Data Buffer

Page 308

ZCOM Tables and Data StructuresInterface TableChapter 380This field contains the I/O card address representing the I/O slot number that the MUX interf

Page 309

ZCOM Tables and Data StructuresInterface TableChapter 3 81IFSTAT - interface card statusThis word indicates the current status of the Mux card. It is

Page 310

ZCOM Tables and Data StructuresInterface TableChapter 382Figure 3-6 Scheduler Event Flags ISCHDLITCNTR - Interface terminal counterThe terminal counte

Page 311

ZCOM Tables and Data StructuresInterface TableChapter 3 83This field contains the maximum number of ports supported by this specific ACC interface car

Page 312

ZCOM Tables and Data StructuresInterface TableChapter 384This is a 16-bit field refreshed by the DAM once every 10 seconds with the runtime informatio

Page 313

ZCOM Tables and Data StructuresInterface TableChapter 3 85These fields are used internally by the ZCOM subsystem.CARD - Interface card specific data s

Page 314 - Chapter 4314

ZCOM Tables and Data StructuresInterface TableChapter 386CARD.BSP has the following fields shown in Table 3-17.The fields for both the card.mmp and ca

Page 315

ZCOM Tables and Data StructuresInterface TableChapter 3 87port. For the 4-port E1/T1 ACC cards, these arrays are indexed by a combination of port and

Page 316 - ZSETQL (3X)

ZCOM Tables and Data StructuresInterface TableChapter 388ITXLSTX - Express transmit list headers (zptl_type)This field is an array of list headers for

Page 317

ZCOM Tables and Data StructuresInterface TableChapter 3 89The list headers in this array function identically to ITXLSTA only for the low priority tra

Page 318

9ContentsZCOMLOG (3X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183ZCOMSTATUS (3X

Page 319

ZCOM Tables and Data StructuresInterface TableChapter 390ZCOM_IPSTAT_UND:The undefined bit. Being undefined is synonymous with being not configured.Fo

Page 320

ZCOM Tables and Data StructuresInterface TableChapter 3 91The out-of-transmit-buffers (XPS queue) bit.For a non-4-port card, indicates the status of p

Page 321 - ZSET_RCVR (3X)

ZCOM Tables and Data StructuresInterface TableChapter 392The layout for the 4-channel E1/T1 ACC card is as follows:Table 3-20 4-Channel E1/T1 ACC Card

Page 322

ZCOM Tables and Data StructuresInterface TableChapter 3 93ISUBCH_BUF - Port subchannel configuration buffer (subchbuf_def) This array contains the sub

Page 323

ZCOM Tables and Data StructuresInterface TableChapter 394Each element of the subchannel specification array has the following structure:IFIRQBP, IRESP

Page 324

ZCOM Tables and Data StructuresInterface TableChapter 3 95Mux card firmware. The Status buffer contains the data returned from a $STDT transaction. Th

Page 325

ZCOM Tables and Data StructuresInterface TableChapter 396IFPLOOK - Physical terminal table lookupThis table is used by the DAM during FIRQ processing

Page 326 - ZTIMR (3X)

ZCOM Tables and Data StructuresInterface TableChapter 3 97bquotaQuota of buffers allowed for each subchanneluns.int 4tracesize Firmware trace buffer s

Page 327

ZCOM Tables and Data StructuresResponse RecordsChapter 398Response RecordsResponse records are used to keep track of the issue-and-wait operations in

Page 328

ZCOM Tables and Data StructuresResponse RecordsChapter 3 99RPTYPE - Expected response typeThis field contains the type of response the waiter is expec

Commentaires sur ces manuels

Pas de commentaire