Compile and link procedures

Overview

The compiling and linking procedures are provided as examples and can be adapted according to the machine options. They can be used to compile the exits that you have developed and to link them with the product.

Depending on the session type you have installed, you must use a specific procedure.

These procedures contain the elements required to compile all exits (C and COBOL).

Two methods are available where scripts are:

• Either adapted so as to compile only the required modules
• Or executed as they have been delivered and all modules are recompiled

It is recommended to use the second method.

MVS implementation

The CLEXIT procedure enables you to compile and link to both C and COBOL exits.

Run the procedure

To use the available exits in COBOL and C:

1. Update the variables :
   • COBLIB: Name of system COBOL compiler library
   • VERLGC: Version of system C compiler (current by default)
   • LKDLIB: Name of system linker library
   • MQC370: Name of system MQSeries compiler library
   • MQLOAD: Name of system MQSeries linker library
2. Remove the comment marks on the corresponding compilation and printing instructions in the procedure.
3. Modify the execution library name in the RDJEXP JCL (located in the &RDJEXEC..JCLLIB library) to use the exits during the transformation process.

Example:

//STEPLIB   DD DSN= &RDJEXEC..EXELIB,DISP=SHR
// …...     DD DSN= &RDJHOME..EXELIB,DISP=SHR

• OLCDLL variable with the NODLL value in the ZCPLGC procedure of the C exits.
• OCBDLL variable with NODLL value in the ZCPLGC procedure of the COBOL exits.

Results

Exit modules are built in the &RDJEXEC..EXELIB library. Executables are DLLs.

UNIX implementation

Run the procedure

Set the environment variables in the $RDJ_EXEC/script directory:

• Execute the script: rdjenv
• If COBOL cobolit execute the script: cobol-it-setup-Axway.sh

Run the makefile in the $RDJ_EXEC/exit directory to:

• Delete the executable and exit objects: make -f exitxxx.mak clean
• Compile the exits and build the executable: make -f exitxxx.mak <Target>

Where:

• xxx is set to:
  • • fic to indicate File mode.
    • mqs to indicate MQSeries mode.
    • jms to indicate JMS mode.
• Target is set to one of the values listed in the table.

The exitfic.mak, exitjms.mak and exitmqs.mak makefiles include targets that call sub-targets for each exit and build the executables.

When you select a target, all exits in C and COBOL language relating to the xxx mode are built. However, the ITR501 external call is built according to the target.

Results

Exit modules are built in the $RDJ_EXEC/exit directory. Executables are shared libraries whose suffix suff (sl, so), set in the CONFIG.MACHINE delivered file, depends on the operating system.

Windows implementation

Prerequisites

• Microsoft Visual Studio 2010
• Visual Cobol 2.1

You can use either the graphical method or the manual method.

Graphical method

1. Double-click the DLL_FIC.sln, , DLL_JMS.sln or DLL_MQS.sln file in the %RDJ_EXEC%\exit directory.
   Visual Studio displays the project exit modules.
2. Check the compilation settings in Solutions Configurations and Solutions Platforms tabs.
3. Select the module to compile in the list of available modules.
4. Execute the Build (or Re-Build).

Manual method

Run the corresponding makefile located in the %RDJ_EXEC%exit directory for the File, JMS or MQSeries mode.

Both procedures are common to all uses and do not have to be modified.

You can compile the exit in:

• Debug mode to test it

msbuild DLL_FIC.sln /p:Configuration=Debug /p:Platform=x64

msbuild DLL_MQS.sln /p:Configuration=Debug /p:Platform=x64

msbuild DLL_JMS.sln /p:Configuration=Debug /p:Platform=x64

• Normal mode

msbuild DLL_FIC.sln /p:Configuration=Release /p:Platform=x64

msbuild DLL_MQS.sln /p:Configuration=Release /p:Platform=x64

msbuild DLL_JMS.sln /p:Configuration=Release /p:Platform=x64

Results

Exit modules are built in the %RDJ_EXEC%\exit directory. Executables are DLLs.

Migrate to a DLL version

Restrictions: This migration is only available for customers with:

• Latin encoding
• Previous versions that the ones specified by platform in the following sections

Migration procedure

This procedure applies to all platforms.

COBOL exits

Source names have not changed.

1. Copy the exit sources from the current to the new environment without changing the names.
2. Build the exit sources in the new environment.

C exits

The name of sources and functions have changed as indicated in the OS-specific tables.

1. Copy the content of functions of exit sources from the current environment into the corresponding functions of exit sources in the new environment.
2. Build the exit sources in the new environment.

Migration  to a DLL version on MVS

Restriction: Rule Engine V1.1.0 and previous

Cross-reference table for C exit sources

Migration  to a DLL version on Windows,  shared libraries on UNIX

Restrictions:

• Windows : Rule Engine V1.1.0 and previous
• UNIX : Rule Engine V1.3.0 and previous

Cross-reference table for C exit sources