MicroFocus COBOL
| Forum | Topics | Posts | Last post |
|---|
Compile program for Animation with ../region/tools/dfcn -a full/directory/path/program.csm
Define shell variable COBAIF.
export COBAIF=$PASSPORT/region/$REGIONDEV/dbin
cd ../region
BATCHANIM region script
This should break within Animator at the top of the program executed by the script. No script changes should be necessary. Animator works very well for batch jobs and there should be no data mapping issues.
PP ver 10.x Animating batch on Unix
ppjobvars' DBINDIR entry chains through PassPort's libint directory, then the development region's dbin directory, then the bin directory, then the int directory, then the test region's dbin directory and so on through the baseline directories.
| 0 | 0 | n/a |
Need to set up Unix shell for running Animator and a PassPort session to debug.
Unix shell
Create a script defined to override region directory path to pick up the modules created by the compile for Animate.
Script used in Unix shell to start Animation executes ppjobvars which in turn executes both ../tools/dforavars and ../tools/dfcobvars. dfcobvars defines LD_LIBRARY_PATH which chains through ../region where libpparch.so exists.
export term=vt100
Start Animator in shell: cd /home/directory/user
/home/directory/user/animate-script region port
In PassPort
go to a panel one level before the one you're interested in Animating. Define the port that will allow PassPort to communicate with the shell in File, Preferences, Diagnostics, Port. Now navigate to the panel you're interested in.
Animate running in the shell should by now have given some indication that it's communicating with the PassPort region.
Notes:
1. Around the time of PassPort ver 9.x or 10.x, or perhaps it's because of MicroFocus Server Express, it has become difficult to view the values of some variables. Animator displays bogus data. Two ideas: a) National Language Support and the introduction of PIC I (eye) variables (PIC I is not COBOL) which are converted by the Indus precompiler depending upon how many bytes are needed to support a character, b) change in paragraph 1000- to use pointers. It's leaning towards the PIC I's. The load module works fine, but the mapped over program being stepped through is misaligned.
2. Animating a .csm program called by a .ccp program requires Animating the calling .ccp program and stepping into the .csm program THE FIRST TIME ITS CALLED. Set a break at the top of both the .ccp and the .csm programs and you should be OK to Zoom through the .ccp and break in the .csm upon subsequent calls. This all comes into play when Animating a .csm that first opens a cursor and then fetches from it.
| 2 | 3 | by Anonymous |
MicroFocus COBOL and Oracle LOB data
| 1 | 1 | by webmaster |
Quirky things about MicroFocus COBOL and Sun Java
| 3 | 3 | by webmaster |
Compile listings are helpful when using Animator (MicroFocus debugger), checking STACK-ARG length <= 128 (old architecture restriction still needed), just how many bytes does a PIC 9(9) COMP use, figuring out what all the -COM variables passed along in linkage do, seeing Indus pre-compiler CICS and SQL output, etc.
COBOL compile listings end up in dbin directory as *.lst.
| 2 | 3 | by Anonymous |
|
| 0 | 0 | n/a |
|
| 0 | 0 | n/a |
|