MVSFORUMS.com

[haqshaik]

Hello Gurus,

I have got a task working on the Stored Procedures. I have been through the postings related to the stored procedures. They have all given a very good insight and been through the red books as well. I am thinking to debug the stored procedure by putting display statements. When I looked into the assocaited WLM job, there is no DD name for SYSOUT. The available DD names are UTPRINT and SYSPRINT, DSSPRINT. There are couple of DD names to log the dumps, like CEEDUMP and SYSDUMP.
I know the user displayed messages will not go into UTPRINT and SYSPRINT. The DSSPRINT dd name is new to me. I am not sure whether the display statements will go in the DSSPRINT or not.I do not thik so it will contain the user displayed messages. What this DSSPRINT dd name will contain? Can I request my DBA to add SYSOUT dd name as well in the WLM proc. I do not see any reson for not adding SYSOUT name in the WLM proce.I might be wrong. Once the Debugging is over we can take off the display statements. I could see the SYSOUT dd name in the WLM esblished address space in the RED book SG24-7083-00 on Page 190 chpater 14 - Debugging.

Any thoughts will be helpful.

Thanks,
Salauddin

[kolusu]

haqshaik,

If you are running SP in WLM , then any displays can be seen in the WLM started task. If your stored procedure is running in the DB2 stored procedure address space (SPAS), the displays can be seen in the output from that task.

Check with your DBA for the naming conventions of the started tasks.

DSSPRINT : You need to add it to JCL along with UTPRINT, SYSIN and SYSPRINT if you are modifying the WLM-established address space in which DSNUTILS runs. You must allocate SYSIN and SYSPRINT in the procedure to temporarily store utility input statements and utility output messages.

Hope this helps...

Cheers

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

[haqshaik]

Thanks Kolusu for your inputs. I was on vacatiaon and could chek the message today only.
Thanks,
Salauddin