TMF Management Programming Manual (H06.06+, J06.03+)
Table Of Contents
- HP NonStop TMF Management Programming Manual
- Legal Notices
- Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to TMF
- 2 Communicating With the TMFSERVE Process
- 3 SPI Programming Considerations for TMF
- 4 Common Definitions
- 5 Commands and Responses
- Command Summary
- Command Descriptions
- ABORT TRANSACTION
- ADD AUDITTRAIL
- ADD DATAVOLS
- ADD DUMPS
- ADD MEDIA
- ADD RESOURCEMANAGER
- ALTER AUDITDUMP
- ALTER AUDITTRAIL
- ALTER BEGINTRANS
- ALTER CATALOG
- ALTER DATAVOLS
- ALTER DUMPS
- ALTER MEDIA
- ALTER PROCESS
- ALTER TMF
- CANCEL OPERATION
- CLOSE RESOURCEMANAGER
- DELETE CATALOG
- DELETE DATAVOLS
- DELETE DUMPS
- DELETE MEDIA
- DELETE RESOURCEMANAGER
- DELETE TMF
- DELETE TRANSACTION
- DISABLE AUDITDUMP
- DISABLE BEGINTRANS
- DISABLE DATAVOLS
- DUMP FILES
- ENABLE AUDITDUMP
- ENABLE BEGINTRANS
- ENABLE DATAVOLS
- INFO ATDUMPDM
- INFO ATVOLUME
- INFO AUDITDUMP
- INFO AUDITTRAIL
- INFO BEGINTRANS
- INFO CATALOG
- INFO DATAVOLS
- INFO DUMPS
- INFO MEDIA
- INFO PROCESS
- INFO RESOURCEMANAGER
- INFO TMF
- LIST AUDITTRAIL
- NEXT AUDITTRAIL
- RECOVER FILES
- RELOCATE DISKDUMPS
- RESOLVE TRANSACTION
- START TMF
- STATUS ATFILE
- STATUS AUDITDUMP
- STATUS AUDITTRAIL
- STATUS BEGINTRANS
- STATUS CATALOG
- STATUS DATAVOLS
- STATUS OPERATION
- STATUS RESOURCEMANAGER
- STATUS RMTRANSBRANCHES
- STATUS TMF
- STATUS TMFSERVER
- STATUS TRANSACTION
- STATUS TRANSACTIONCHILDREN
- STOP TMF
- 6 Event Messages
- 7 Error and Warning Messages
- A TMF Configuration Limits and Defaults
- Index
SPI Programming Considerations for TMF
HP NonStop TMF Management Programming Manual—540140-010
3-2
Definition Files
of structures in the definition file. TAL programs can source either the entire definition
file or just the sections they need. The TACL command interpreter always loads the
entire definition file. For further information about how definition files are used by an
application, see the SPI Programming Manual.
Definition files are named according to the following convention:
subsys
is a three-character code identifying the subsystem or other software component to
which these definitions belong. This code is TMF for the TMF product.
The last characters of each file name denote the language in which the definitions in
this file are coded.
The files are located on the disk volume chosen by your site. The default disk volume
used by the INSTALL program is $SYSTEM.
An application that sends DSM commands to and receives responses from TMF needs
the following definition files in the appropriate programming language:
The SPI (ZSPI) definition file
The TMF (ZTMF) definition file
An application that retrieves event messages issued by TMF needs all the definition
files listed above, plus the following:
The EMS (ZEMS) definition file
For example, a management application written in TAL that sends commands to and
retrieves event messages issued by TMF would need the following SOURCE
statements:
?SOURCE ZSPIDEF.ZSPITAL
?SOURCE ZSPIDEF.ZTMFTAL
?SOURCE ZSPIDEF.ZEMSTAL
If your application manages other subsystems besides TMF, it also needs the definition
files required by those subsystems. For instance, you might want your TMF
management application to manage an associated Pathway system as well. If you
were writing the TAL management application mentioned above and also wanted to
manage Pathway, you would need the following additional SOURCE statement:
?SOURCE ZSPIDEF.ZPWYTAL
ZSPIDEF.ZsubsysC
ZSPIDEF.ZsubsysCOB
ZSPIDEF.ZsubsysDDL
ZSPIDEF.ZsubsysPAS
ZSPIDEF.ZsubsysTACL
ZSPIDEF.ZsubsysTAL