Cutting Down An ACUCOBOL-GT Application To Submit For Troubleshooting

0 Likes

When reporting an error or bad behavior in an ACUCOBOL-GT application the Customer Care engineer may request a test case in order to troubleshoot the issue.  Should a small stand-alone program not demonstrate the behavior, the application itself may need to be submitted.  However DO NOT send the entire application, instead send only the programs and data files that are actually used in demonstrating the issue. 

 Here's how to do that:

 1. Start the application with a Runtime trace as described here:

http://community.microfocus.com/microfocus/cobol/extend_and_acucobol/w/knowledge_base/27977.acucobol-gt-trace-files-for-troubleshooting.aspx#Runtime

 2. Exercise only the steps necessary to demonstrate the bad behavior, and then exit (if the Runtime hasn't already terminated from the bad behavior).

 3. Parse the runtime log file for the programs loaded and for the files opened.  Linux has grep and related commands which will do nicely, and are also available on Windows in the Cygwin utility package. I highly recommend installing Cygwin on your Windows PC.  Here are commands that can provide the information needed:

 a. List all programs loaded:

      grep loaded runtime.log | sort | uniq > programs.lst

The programs.lst file will contain the names of all libraries and COBOL programs loaded by the Runtime. 

 b. List all data files opened:

     grep ': open ' runtime.log | sed 's/open.*//' | sort | uniq > files.lst

The files.lst file will contain the names of the files as known by the program. For each of those examine the runtime.log to see if there is a line following the open noting "translated name".  If the disk file has a different name then this line gives that name.

 4. Zip up all of the following and attach to the support incident:

- The COBOL program object files, compiled for debug

- The COBOL program source files (To avoid having to provide a myriad of copybooks, compile with "-lpo @.src" to produce a single complete source file with all copybooks expanded.)

- Any libraries loaded by the application (.so, .sl, .dll) that aren't provided with the OS

- The data files

- The Runtime configuration file

 5. Update the support incident with the compile command line and instructions for running the application to produce the bad behavior.

 

Comment List
Related
Recommended