Problem:

cobscan64 runs the Scan64 utility.

The Scan64 utility enables you to check programs for pointer violations.

You use Scan64 to help you migrate applications from 32-bit to 64-bit COBOL systems. If you have developed COBOL programs using the Server Express 32-bit development environment that you want to migrate to the Server Express 64-bit development enviroment, you should run Scan64 before compiling and running them with the 64-bit system development environment.

Resolution:

Note: Scan64 cannot detect invalidly-sized data items provided to prototyped CALL statements that require pointers.

You can only use Scan64 on applications that have been compiled to intermediate code.

The format of the command is:

cobscan64 [-v] [-m] [-ttfile [-ltlist]] filename

where the parameters are:

  -v         Internal addressing information is displayed. This can be useful to our support                                  representatives.

  -m        Include modifier information.

  -ttfile   The COBOL header file that contains COBOL call prototypes for entry points called within                  this program.

  -ltlist    The resulting template listing file with any diagnostics from parsing the COBOL header file.

               filename The intermediate code file to be analyzed. You can specify the filename with or                  without the .int filename extension. If you omit the filename extension, .int is assumed.

If you enter cobscan64 without parameters, the available options are listed.

For examples of using Scan64, these demos are stored in the directory $COBDIR/demos/scan64.

Ref:  for more detail information on this utility and these demos please read chapter 12 "Scan64" of the Utilities Guide