Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
DB2-WLM region

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2
View previous topic :: :: View next topic  
Author Message
ajeshrn

New User


Joined: 25 Mar 2009
Posts: 78
Location: India

PostPosted: Wed Oct 21, 2009 12:18 pm    Post subject: DB2-WLM region
Reply with quote

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?
Back to top
View user's profile Send private message

Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Wed Oct 21, 2009 5:54 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
ajeshrn

New User


Joined: 25 Mar 2009
Posts: 78
Location: India

PostPosted: Fri Oct 23, 2009 3:14 pm    Post subject:
Reply with quote

Hi Anuj,

I checked with my DBA, we are not using any tool called DELTAIMS..
icon_sad.gif icon_sad.gif
Back to top
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA

PostPosted: Sat Oct 24, 2009 9:13 am    Post subject:
Reply with quote

At one of my previous sites, the DISPLAYs included a prefix of the program name and timestamp which made them easy to find.
Back to top
View user's profile Send private message
ajeshrn

New User


Joined: 25 Mar 2009
Posts: 78
Location: India

PostPosted: Sat Oct 24, 2009 9:18 am    Post subject:
Reply with quote

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
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6968
Location: porcelain throne

PostPosted: Sat Oct 24, 2009 1:04 pm    Post subject:
Reply with quote

you could reduce the displays by only display when there is an error.
Back to top
View user's profile Send private message
ajeshrn

New User


Joined: 25 Mar 2009
Posts: 78
Location: India

PostPosted: Sun Oct 25, 2009 10:16 am    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA

PostPosted: Sun Oct 25, 2009 11:21 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
zdebug

New User


Joined: 11 Nov 2009
Posts: 2
Location: San Jose

PostPosted: Wed Nov 11, 2009 4:01 am    Post subject: Reply to: DB2-WLM region
Reply with quote

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? icon_smile.gif

Cheers,
zdebug
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> DB2 All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts IMS region inactive - User abend code... gthmrj IMS DB/DC 5 Tue Mar 07, 2017 12:29 pm
No new posts Determine Region with max bandwidth f... seahawk789 COBOL Programming 3 Mon Feb 27, 2017 8:26 pm
No new posts JCL to get submitted once dataset has... vinu78 JCL & VSAM 17 Thu Feb 16, 2017 7:32 am
No new posts INDEPENDENT CICS TS 4.1 MRO REGION UP... Kyle Carroll CICS 0 Wed Dec 14, 2016 6:55 pm
No new posts how to move view the remote file in o... mailtoashok CICS 2 Fri Feb 12, 2016 1:07 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us