NetBatch Management Programming Manual
SPI Programming Considerations for the NetBatch
Subsystem
NetBatch Management Programming Manual—522462-003
3-3
Event-Message Template
For example, a management application written in TAL that sends commands to the
NetBatch subsystem and retrieves event messages issued by that subsystem requires
these SOURCE statements:
Likewise, a management application written in the C programming language that sends
commands to the NetBatch subsystem and retrieves event messages issued by that
subsystem requires these include statements:
If your application manages other subsystems besides the NetBatch subsystem, it also
requires the definition files required by those subsystems.
In NonStop manuals, definition refers to the data declarations in a definition file. For
more information on SPI and EMS definitions, see the SPI Programming Manual and
the EMS Manual. For more information on NetBatch definitions, see Section 4,
Common Definitions.
Event-Message Template
The NetBatch subsystem comes with a DSM format template. This template lets the
Guardian procedure EMSTEXT display scheduler event-message text in DSM display
format. The template specifies which tokens of each message the procedure displays
and the message text. Source and object files for the template are provide. You can
change the source and recompile it if you want to customize your messages.
The names of the source and object files for the NetBatch template are, respectively,
$vol.ZTEMPL.SBATTMPL and $vol.ZTEMPL.ZBATTMPL.
For more information on DSM format templates and instructions on how to use and
change them, see the DSM Template Services Manual. For information specific to the
NetBatch template, see Section 6, Event Messages.
Naming Guidelines for Applications
HP uses names beginning with the letter Z for definitions and component fields of
structures in its definition files. To avoid having names you define conflict with names
defined by HP, do not begin your names with a Z.
?SOURCE $vol.ZSPIDEF.ZBATTAL
?SOURCE $vol.ZSPIDEF.ZEMSTAL
?SOURCE $vol.ZSPIDEF.ZSPITAL
#include "$vol.zspidef.zbatc"
#include "$vol.zspidef.zemsc"
#include "$vol.zspidef.zspic"