TMF Application Programmer's Guide (G06.24+)

TMF ARLIB2 Audit-Reading Procedures
HP NonStop TMF Application Programmer’s Guide—522419-004
5-95
How to Include Audit Reading in an Application
How to Include Audit Reading in an
Application
The TMF audit-reading procedures are contained in a set of files that are delivered with
the TMF product. Table 5-4 summarizes the audit-reading procedure files.
Because TMFARLB2 is a native object file, NLD must be used to build the executable
object file. If SQL/MX is installed, then the following parameter must be part of the
NLD command:
-l ZCLIPSRL
If SQL/MX is not installed, then the -l ZCLIPSRL parameter is not required.
If the executable object contains C/C++ or Cobol code or uses the CRE, then the
program must be run by the local SUPER.SUPER user ID. Using FUP LICENSE or
FUP PROGID will not allow any user other than SUPER.SUPER to run the program.
This is a Guardian restriction.
If the executable object is only pTAL, then using FUP LICENSE and FUP PROGID to a
Super group user will allow users other than SUPER.SUPER users to run the program
based on Guardian file security.
Use of AWAITIOX
AWAITIOX will not complete nowaited I/O calls started by TMFARLB2.
Table 5-4. Files Supplied With TMFARLB2 (T2781)
File Name Content
ARDECS2 External declarations (in TAL) for the audit-reading procedures.
ARDECSC2 External declarations (in C) for the audit-reading procedures.
ARDDL2, ARC2,
ARCOBOL2,
ARTACL2, ARTAL2
DDL source and corresponding data-definition files for C,
COBOL85, TACL, and TAL programs, respectively, that are going to
call the audit-reading procedures. These files each contain the
following sections:
•
FILESPEC and ARRECORD define the record formats.
•
ARTYPE-LITERALS contains the literals for record types.
•
ARVALUE-LITERALS contains the literals for special values of
certain fields and returned parameters.
•
AR-RETURN-CODES contains the literals for the return codes.
TMFARLB2 Object file containing the ARLIB2 audit-reading procedures.