PAM Management Programming Manual

SPI Programming Considerations for the PAM
Subsystem
PAM Management Programming Manual—142481
3-3
Naming Guidelines for Applications
For example, a management application written in TAL that sends commands to the
PAM subsystem and retrieves event messages issued by the PAM subsystem would need
the following SOURCE statements:
?SOURCE ZSPIDEF.ZSPITAL
?SOURCE ZSPIDEF.ZCOMTAL
?SOURCE ZSPIDEF.ZPAMTAL
?SOURCE ZSPIDEF.ZEMSTAL
?SOURCE ZSPIDEF.ZGRDTAL
?SOURCE ZSPIDEF.ZFILTAL
For more information about the SPI definitions, EMS definitions, data communications
definitions, and Guardian file-system definitions, refer to the following manuals:
•
SPI Programming Manual
•
EMS Manual
•
SPI Common Extensions Manual
•
Guardian Procedure Errors and Messages Manual
The PAM subsystem definitions are described throughout this manual.
Naming Guidelines for Applications
Tandem uses names beginning with the letter Z (lowercase in C) for all definitions and
all component fields of structures in its definition files. To avoid present and future
conflicts with names defined by Tandem, it is best not to begin any of your own names
(names you define in your application) with uppercase or lowercase Z.
Message Elements for the PAM Subsystem
The following subsections provide subsystem-specific information about elements of
commands, responses, and event messages. For more complete information about these
elements, refer to the SPI Common Extensions Manual.
Subsystem ID (SSID)
ZSPI-TKN-SSID is a header token whose value is set using SSINIT. It contains the
value ZPAM-VAL-SSID, which is the PAM subsystem ID (SSID).