OSI/AS Programming Manual

Naming Conventions
APS Procedures Programming Concepts
2–2 056783 Tandem Computers Incorporated
A functional unit is a set of one or more related services. For example, the activity
management functional unit consists of the activity start service, the activity resume
service, the activity end service, the activity interrupt service, and the activity discard
service. All the services within a functional unit are provided as a group—that is, if a
user requests the activity start service, the user can use all the other services in the
activity management functional unit.
Naming Conventions Conventions govern the names of the procedures and data items you use with the API
to OSI/AS. Procedure names start with “APS_”; for more information about
procedure names, see “Procedure Names” in Section 3.
As part of the OSI/AS product, Tandem provides data declarations for the structures
and values of fields used by the APS procedures. These declarations, which reside by
default in $SYSTEM.ZOSIAS (your system manager may install them in another
volume and subvolume), are provided in three files:
In the TAL source file ZAPSTAL, to be sourced into TAL programs
In the C source file ZAPSC, to be included in C programs
In the Data Definition Language (DDL) source file ZAPSDDL, from which the
ZAPSTAL and ZAPSC files are derived
In this manual, all data names are given in DDL format, just as they appear in the
ZAPSDDL source file.
All data names in these declarations start with the letter Z, followed by the identifier
“APS”. The portions of DDL data names are separated by hyphens. Data structure
names start with “ZAPS-DDL-”; data value names start with “ZAPS-VAL-”; error
value names start with “ZAPS-ERR-”. In TAL format, the hyphens are replaced by
circumflex symbols (^), and “^DEF” is appended at the end of all DDL DEFs. In C
format, the hyphens are replaced by underscore characters (_), and “_def” is appended
at the end of all DDL DEFs.
Here are three examples of DDL names:
ZAPS-DDL-AE-TITLE-DEF
ZAPS-VAL-EVT-CONNECT-IND
ZAPS-ERR-L5-TOKEN-STATE
They correspond to the following names in TAL:
ZAPS^DDL^AE^TITLE^DEF
ZAPS^VAL^EVT^CONNECT^IND
ZAPS^ERR^L5^TOKEN^STATE
The three DDL names correspond to the following names in C:
ZAPS_DDL_AE_TITLE_DEF
ZAPS_VAL_EVT_CONNECT_IND
ZAPS_ERR_L5_TOKEN_STATE