OSI/AS Management Programming Manual

Naming Guidelines for Applications
SPI Programming Considerations for OSI/AS
056785 Tandem Computers Incorporated 3–3
Likewise, a management application written in C that sends commands to and
retrieves event messages issued by the OSI/AS subsystem would need the following
include statements:
#include "zspidef.zspic"
#include "zspidef.zcomc"
#include "zspidef.zosic"
#include "zspidef.zemsc"
#include "zspidef.zgrdc"
#include "zspidef.zfilc"
If your application manages other subsystems besides OSI/AS, it also needs the
definition files required by those subsystems. For instance, you might want your
OSI/AS management application to manage the underlying subsystems, OSI/TS and
either X25AM or TLAM, as well. If you were writing the TAL management
application mentioned above and also wanted to manage OSI/TS and TLAM, you
would need the following additional SOURCE statements:
?SOURCE ZSPIDEF.ZOS4C
?SOURCE ZSPIDEF.ZLAMC
In C, you would need the following additional include statements:
#include "zspidef.zos4c"
#include "zspidef.zlamc"
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/AS definitions are described in this manual.
Templates and Labels Event-message templates are provided with the OSI/AS product. These define the
text used for displays of event messages by the ViewPoint console application and
other console devices and applications. Both source and compiled templates are
provided. You can modify the source templates and recompile them if you wish to
customize your messages.
The name of the OSI/AS template object file is ZTEMPL.ZOSITMPL; the source file is
ZTEMPL.SOSITMPL. For general information about DSM templates and instructions
on how to use and modify them, refer to the DSM Template Services Manual.
The OSI/AS subsystem also provides labels for use in debugging, as described in the
DSM Template Services Manual.
Naming Guidelines for
Applications
By convention, Tandem uses names beginning with the letter Z (lowercase z 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 with uppercase or lowercase Z.