To create the object file of a UAP written in COBOL language, compile the source program with the COBOL compiler.

See the COBOL Language manual for details on how to compile UAPs.

To create the object file of a stub, compile the stub source file with the C compiler.

The following notes (#1 to #3) apply to files treated in (a) to (d) below.

#1:

The object file for transaction control is required to execute transactions that access the resource manager via the XA interface. Note that any resource manager provided by OpenTP1 is accessed by the XA interface. An object file for transaction control is created by using an OpenTP1 command (trnmkobj command). For details on the trnmkobj command, see the manual OpenTP1 Operation.

#2:

The object file provided by resource manager is required to access the resource manager. The following arguments can be specified in the linkage command to link object files provided by OpenTP1:

Arguments for using the message exchange facility: -lmcf and -lmnet

Argument for using the DAM access facility: -ldam

Argument for using the TAM access facility: -ltam

Arguments for using the ISAM facility: -lismb, -lisam, and -lrsort

Argument specified for using message queuing: -lmqacb

For details on how to link object files for a non-Hitachi resource manager, see the documentation for the resource manager.

#3:

The object file provided by online tester is required to use the CBLDCUTO('T-STATUS') function, which reports the user server test status. The following argument is specified to link the object file for the online tester:

Argument for reporting the user server test status: -luto

(a) Files to be linked to SPP and MHP

The executable file of an SPP or MHP is linked to the following files when it is created:

• UAP object file (main and service programs)
• Stub object file
• Object file for transaction control^#1
• Object file provided by resource manager^#2
• Object file provided by online tester^#3
• OpenTP1 library
• COBOL library (COBOL85 library if the UAP was created in the COBOL85 language)

(b) Files to be linked to SUP

The executable file of a UAP that handles offline work is linked to the following files when it is created:

• UAP object file (main program)
• Object file for transaction control^#1
• Object file provided by resource manager^#2
• Object file provided by online tester^#3
• OpenTP1 library
• COBOL library (COBOL85 library if the UAP was created in the COBOL85 language)

(c) Files to be linked to UAP that handles offline work

The executable file of a UAP that handles offline work is linked to the following files when it is created:

• UAP object file (main program)
• OpenTP1 library
• COBOL library (COBOL85 library if the UAP was created in the COBOL85 language)

(d) Files to be linked to an SPP or MHP that performs dynamic loading of service functions

The executable file of an SPP that dynamically loads service functions is linked to the following files when the file is created:

• UAP object file (main function)
• OpenTP1 library
• Object file for transaction control^#1
• Object file provided by resource manager^#2
• Object file provided by online tester^#3

In addition to the above files, the following files are required when the SPP also uses a service search that employs a stub:

• UAP object file (service function)
• Stub object file

If the OS is HP-UX, the bind mode for linkage must be specified as immediate. If an executable file created in another mode is used as an OpenTP1 UAP, the system operation is unpredictable. To check that the bind mode of the created UAP is immediate, use the chatr command of the OS.