(a) Languages

UAPs that support the 64-bit mode can be created in C or C++. COBOL and OOCOBOL cannot be used.

(b) Facilities

UAPs that support the 64-bit mode cannot use the XA interface. However, they can basically use all other facilities. In 64-bit mode, the multi-connection facility provides real threads instead of pseudo threads.

Before a HiRDB client can be converted from 32-bit mode to 64-bit mode, the HiRDB client must be upgraded to a 64-bit mode version. (Install the 64-bit mode HiRDB client and set up the client environment.) For details about how to set up the client environment, see 6. Client Environment Setup.

When the 64-bit mode HiRDB client is installed, files for 64-bit mode are created. For details about the files that are created when the 64-bit mode HiRDB client is installed, see 6.4 Organization of directories and files for a HiRDB client.

After the client environment setup is completed, convert the UAP to 64-bit mode support according to the following procedure.

Procedure

1. If long type is used in the declaration of an embedded variable, change the location to int type
2. Execute UAP preprocessing. When executing UAP preprocessing, specify the -h64 option for creating a 64-bit mode post source.
3. Execute UAP compilation. When executing UAP compilation, specify the option for creating 64-bit mode objects.
4. Execute UAP linkage. When executing UAP linkage, specify a 64-bit mode client library as the client library to be linked.

Note

For details about UAP preprocessing, compilation, and linkage, see 8.2 Preprocessing and 8.3 Compiling and linking.