On HP-UX PA-RISC, the ANSI C compiler is required in order to build an executable, in other words, each time "cob -x" is used. This includes linking the Oracle libraries. The ANSI C Compiler is separately purchasable from HP.
HP-UX parisc supports two distinct run-time environments for C++ Applications: the Classic C++ run-time and the Standard C++ run-time. These two C++ run-times provide similar but not identical interfaces and functionality. The Classic C++ run-time is provided to support the large number of C++ applications that were developed before the final standard for the C++ was developed and published; while the Standard C++ run-time is necessary for building and running portable and standard-conforming applications.
From Server Express 5.0 and later, cob compiles C++ code to run in the Standard C++ run-time environment, by passing the HP C++ compiler option -AA. This is a change from Server Express 4.0 where the Classic C++ run-time environment was used.
When migrating a C++ application to run with Server Express 5.0 and later, all C++ code will need to be recompiled using either cob or an updated build script, to ensure it is compiled with -AA.
For more details, see the HP technical resource titled "C++ runtime environments (-AA and -AP) on HP-UX" http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,55 20,00.html
Use of the Compiler directives HOSTNUMCOMPARE(1) and HOSTNUMMOVE(1) is deprecated. Support for these directives will be removed in a future release.
If you use Net Express Publisher to deploy applications built using Net Express to Server Express, you need the Net Express 3.1 FixPacks: ide07n31.exe IDE component Fixpack v3.1.007 (or later) unx05n31.exe Unix Option FixPack v3.1.005 (or later) These correct a problem with Net Express not copying certain files across to UNIX correctly.
On HP-UX PA-RISC 32/64-bit, to access shared libraries you need to include $COBDIR/lib on both SHLIB_PATH and LD_LIBRARY_PATH.
When you debug a program on your UNIX system from Net Express, you must transfer the .idy files from Server Express to a local drive on the PC where Net Express is running (or map a network drive to the UNIX directory), and delete all idy files from the project debug directory. Then in Animate > Settings > Location of debug information files (.idy) for local access enter the path of the .idy files transferred from the UNIX machine or on the mapped network drive.
Once you have entered a debuggable program (either because you inserted a call to CBL_DEBUGBREAK at the beginning of the procedural code or because it is running in a server started with the command cassi /a), if you hit Zoom, you cannot then break into the program using the keyboard. So, if you want to use Zoom so that you can focus on a subset of your code, you will need to set breakpoints or insert "CALL CBL_DEBUGBREAK" statements. If you wish to store breakpoints during a debugging session, follow the procedure described in the section "Debugging COBOL Services" in your Debugging Guide, and in addition, before you run the client program:
If you single-step through your code, when you step a GOBACK statement, the Animator stops on the next debuggable instruction encountered.