IBM Mainframe Forum

Hello Experts,

We use CICS Explorer to debug COBOL programs at our shop.The ones that we normally do are the Enterprise COBOL programs.

Currently I'm working with OS VS COBOL programs and I feel that if I could get these programs tested via the debugger it would be faster than my manual testing.

I referenced the below document and was able to generate the EQALANGX file for my OS VS COBOL program.
https://www.ibm.com/support/knowledgece ... 1/osvs.htm

After generating the EQALANGX file,I referenced the below document and looked at some other notes too and made modifications to the run jcl as shown below and ran it,

http://www-01.ibm.com/support/docview.w ... 089&aid=13





The program popped up on the debugger (CICS Explorer) but it was in Assembler format as shown below.

Debugger part

Can someone familiar with this process please tell what am I doing wrong here ? I have sent an email to my system programmer (who usually setup debug profiles) but he is out today and will be back on Monday.But I'm not sure if he is familiar with OS VS COBOL debugging.

Thanks,
Ram Kumar

Are you aware of the method by which the executing program is linked to the LANGX member you created? (I'm not, I'm just suggesting...)

Why, if you need to test the programs anyway, don't you just convert/compile as Enterprise COBOL?

Thanks BillyBoyo. I'm not familiar with linking langx file and the executing module.I was trying the method below that I found in the document below.I tweaked it a bit to give my IP Address and port # .

http://www-01.ibm.com/support/docview.w ... 089&aid=13

4. Run your program.
Start the program according to the program type as follows:

Program Type
Non-Language Environment
JCL EXEC


We have OS VS COBOL programs calling HLASM programs.These HLASM programs were converted to Enterprise COBOL and it seems to be working fine except for this particular step (the job has over 30 steps).We would convert all OS VS COBOL programs to Enterprise COBOL eventually but right now,I was trying to find out the issue with that particular step.

Thanks,
Ram Kumar

Hello,
I checked with my system programmer and was finally able to debug the OS VS COBOL programs through CICS explorer.

I had to make two changes.
1)I had to rename my LANGX file from myid.ADLAB.EQALANGX to myID.EQALANGX
2)I had to enter "LDD myprog" in the debug console This command to tells the Debug Tool that a compile
unit is a LangX COBOL compile unit and to load the debug information associated with that compile unit.



But I do have some issues..The values in the variables look to be in hexadecimal format.I'm looking into that now.


Thanks,
Ram Kumar

I'd consider the suggestion by BillyBoyo concerning recompiling due to the following:
http://www.ibm.com/support/knowledgecen ... ch205.html

Will do Terry..Thank you..