OSI/TS Management Programming Manual

Naming Guidelines
SPI Programming Considerations for OSI/TS
056786 Tandem Computers Incorporated 3–3
Likewise, a management application written in C that sends commands to and
retrieves event messages issued by the OSI/TS subsystem would need the following
#include statements:
#include <zspidef.zspic>
#include <zspidef.zcomc>
#include <zspidef.zos4c>
#include <zspidef.zemsc>
#include <zspidef.zgrdc>
#include <zspidef.zfilc>
If your application manages other subsystems as well as OSI/TS, it also needs the
definition files required by the other subsystems. This manual and other Tandem
manuals use the word definition to refer to the data declarations within a definition file.
For further information about the SPI definitions, EMS definitions, data
communications definitions, and Guardian 90 and file-system definitions, refer to the
Distributed Systems Management (DSM) Programming Manual, the Event Management
Service (EMS) Manual, the Communications Management Programming Manual, and the
System Procedure Errors and Messages Manual, respectively. The OSI/TS definitions are
described in this manual.
Templates and Labels Event-message templates are provided with the OSI/TS product. These define the text
used for displays of event messages by the ViewPoint console application and other
console devices and applications. Both source code and object code for the templates
are provided, so that you can modify the templates if you wish to customize your
messages.
The name of the OSI/TS template object file is ZSPIDEF.ZOS4TMPL; the source file is
ZSPIDEF.SOS4TMPL. For general information about DSM templates and instructions
on how to use and modify them, refer to the DSM Template Services Manual.
The OSI/TS subsystem also provides labels for use in debugging, as described in the
DSM Template Services Manual.
Naming Guidelines By convention, Tandem uses names beginning with the letter Z for all definitions and
all component fields of structures in its definition files. To avoid present and future
conflicts with names defined by Tandem, do not begin any of your own names with
uppercase or lowercase Z.
Tokens that start with a ZX____ are for D-series systems only. They are either new
tokens or a replacement for a token similarly named (but without the "X") for C-series
systems. Information will be returned in the D-series token and also in the C-series
equivalent if the information fits (the field is otherwise left null).