DB2-WLM region

ajeshrn · New User Joined: 25 Mar 2009 Posts: 78 Location: India

Hi,

Am working on COBOL-DB2 stored procedures.In order to check the flow of the program, I have kept some DISPLAY statements as and when required.Once I execute the procedure though front end, the values DISPLAYed are getting populated in the WLM region.Since the WLM region is a common place where all the Stored Procedures execute, I am able to see the other SP's displays also.I need to manually open all the jobs in DB2WLM region and check their SYSOUT's and find where my Display is. Is there a way I can route all the displays for my SP alone to a dataset from WLM region?

Anuj Dhawan · Posted: Wed Oct 21, 2009 5:54 pm

This is a site-specific question. At my previous shop there was a tool DELTAIMS which would tell you the name of the Job number and name for your inputs at Front-end and then you chek a single SYSOUT instead of many. Suggest you get in touch with DBA at your shop, he must be knowing if such a tool is available there already.

ajeshrn · New User Joined: 25 Mar 2009 Posts: 78 Location: India

Hi Anuj,

I checked with my DBA, we are not using any tool called DELTAIMS..

Terry Heinze · Posted: Sat Oct 24, 2009 9:13 am

At one of my previous sites, the DISPLAYs included a prefix of the program name and timestamp which made them easy to find.

ajeshrn · New User Joined: 25 Mar 2009 Posts: 78 Location: India

Thanks Terry,

Here what we do is put a display in the Stored Procedure and will keep my name or some identified and used to open all the SYSOUTS in the DB2WLM region and check them manually.If there are too many jobs then its a bit difficult to find these. I need to check in each and every job.

DISPLAY " <MY NAME> VAR1" VAR1

dbzTHEdinosauer · Posted: Sat Oct 24, 2009 1:04 pm

you could reduce the displays by only display when there is an error.

ajeshrn · New User Joined: 25 Mar 2009 Posts: 78 Location: India

Thats true, and we put display only when we need to debug the code. So only in the flow where we are debugging we put display.Once we fix it, we remove all the DISPLAY statments.

Terry Heinze · Posted: Sun Oct 25, 2009 11:21 pm

If you are either commenting out or actually deleting the DISPLAY statements, please read about the WITH DEBUGGING MODE option of the SOURCE-COMPUTER paragraph.

zdebug · New User Joined: 11 Nov 2009 Posts: 2 Location: San Jose

How about using Debug Tool to debug DB2 (main) stored procedures? You can debug the DB2 COBOL stored procedure using a VTAM terminal or a workstation tool like RDz. RDz's debug console will show the output of the DISPLAY statements in the debug console and you wouldn't have to open any WLM region output.

Well, if you can debug the COBOL code, would you need the DISPLAY statements to start with?

Cheers,
zdebug