Both 32-bit and 64-bit versions of the tools and utilities are provided. They are suffixed with either 32 or 64 as appropriate. The tools and utilities are also provided in unnumbered versions. You do not need to alter $PATH, $COBDIR, and $LD_LIBRARY_PATH or $LIBPATH in order to switch between working modes.
For example:
cob32 -i myprog.cbl cobrun32 myprog
compiles the program myprog.cbl to the 32-bit intermediate code file myprog.int, and then runs it.
cob64 -i myprog.cbl cobrun64 myprog
compiles the program myprog.cbl to the 64-bit intermediate code file myprog.int, and then runs it.
For development tools (such as the cob utility), the unnumbered versions always obey the current working mode.
For cobrun and anim (the trigger for Animator), the unnumbered versions locate the application named on the command line and automatically run it in the correct mode. If the named application cannot be located, these tools obey the current working mode.
For example:
cobrun64 myapp.int
runs myapp.int in 64-bit mode. If myapp.int is a 32-bit application then a run-time error occurs.
cobrun myapp.int
runs myapp.int in either 32-bit or 64-bit mode, as appropriate, depending on which mode myapp.int was compiled to.
anim myapp
runs Animator, using myapp, in either 32-bit or 64-bit mode, as appropriate, depending on which mode myapp.int was compiled to.
These examples are true for .int files, .gnt files and callable shared objects. However, system executable files are run in the same way for both 32-bit and 64-bit modes. For example, you can create and run 32-bit and 64-bit system executable files from the program myprog.cbl as follows:
cob32 -x myprog.cbl ./myprog
cob64 -x myprog.cbl ./myprog