SYSMDUMP in DB2 SP WLM
We need to collect a SYSMDUMP from a DB2 SP WLM task. The SYSMDUMP DD needs to point to a disk data set. There can be multiple instances of the DB2 SP WLM task running concurrently, so there is a need to uniquely name the data set for the SYSMDUMP. GDGs don't work because there is an enqueue on the GDG base, so started tasks after the first wait. We've thought of using system symbols (since this is a started task), but there isn't enough granularity in the values of the symbols to assure uniqueness. Any thoughts on how to accomplish this? Don Imbriale -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSMDUMP in DB2 SP WLM
Search the archives for some details from Ed Jaffe regarding pointing the SYSMDUMP DD to a SYSOUT dataset, and then saving it to a dataset if and only if you need it. Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Don Imbriale Sent: Tuesday, September 11, 2007 11:08 AM To: IBM-MAIN@BAMA.UA.EDU Subject: SYSMDUMP in DB2 SP WLM We need to collect a SYSMDUMP from a DB2 SP WLM task. The SYSMDUMP DD needs to point to a disk data set. There can be multiple instances of the DB2 SP WLM task running concurrently, so there is a need to uniquely name the data set for the SYSMDUMP. GDGs don't work because there is an enqueue on the GDG base, so started tasks after the first wait. We've thought of using system symbols (since this is a started task), but there isn't enough granularity in the values of the symbols to assure uniqueness. Any thoughts on how to accomplish this? Don Imbriale -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSMDUMP in DB2 SP WLM
Thanks Wayne. I had searched the archives. My tests show that SYSMDUMP directed to SYSOUT, then copied to a dataset (via SDSF for example), results in a partially corrupted SYSMDUMP. Don Imbriale -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Driscoll Sent: Tuesday, September 11, 2007 12:24 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: SYSMDUMP in DB2 SP WLM Search the archives for some details from Ed Jaffe regarding pointing the SYSMDUMP DD to a SYSOUT dataset, and then saving it to a dataset if and only if you need it. *** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSMDUMP in DB2 SP WLM
Wayne Driscoll wrote: Search the archives for some details from Ed Jaffe regarding pointing the SYSMDUMP DD to a SYSOUT dataset, and then saving it to a dataset if and only if you need it. SYSMDUMP to sysout. The only way to fly! (Or, at least, the only way I fly.) ;-) http://bama.ua.edu/cgi-bin/wa?A2=ind0704&L=ibm-main&P=R59172&I=1&X=- http://bama.ua.edu/cgi-bin/wa?A2=ind0704&L=ibm-main&P=R59580&I=1&X=- -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSMDUMP in DB2 SP WLM
Imbriale, Donald wrote: Thanks Wayne. I had searched the archives. My tests show that SYSMDUMP directed to SYSOUT, then copied to a dataset (via SDSF for example), results in a partially corrupted SYSMDUMP. I look at many such dumps and have never experienced any corruption using this technique. The dump on spool will be byte-for-byte exactly correct. When copying to DASD for IPCS use, you need to use a tool that will not change the contents of the data. And, you must copy it to a RECFM=FBS data set. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSMDUMP in DB2 SP WLM
After further research I see that the 'corruption' is the insertion of carriage control characters. This is being done by SDSF when using line command XDC, even if the correct data set attributes are specified for the output data set. Instead, I created an appropriate data set, allocated it to some DD in my TSO session, then used SDSF's XFC line command and pointed to that DD. This copies it as is, without carriage control characters. Now it is usable. Thanks Wayne and Ed. Don Imbriale -- On Tue, 11 Sep 2007 09:47:45 -0700, Edward Jaffe <[EMAIL PROTECTED]> wrote: >Imbriale, Donald wrote: >> Thanks Wayne. I had searched the archives. My tests show that SYSMDUMP >> directed to SYSOUT, then copied to a dataset (via SDSF for example), >> results in a partially corrupted SYSMDUMP. >> > >I look at many such dumps and have never experienced any corruption >using this technique. The dump on spool will be byte-for-byte exactly >correct. When copying to DASD for IPCS use, you need to use a tool that >will not change the contents of the data. And, you must copy it to a >RECFM=FBS data set. > >-- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSMDUMP in DB2 SP WLM
(off-list to hide my ignorance) Hello Ed, Out of curiosity, in a situation where multiple abends occurred, how does SYSMDUMP processing handle this? Does it write multiple dumps to the dataset? (I'm guessing "yes" because of the nature of SYSOUT storage.) We just had a situation where, in a multi-TCB address space, the customer had only SYSUDUMP. The problem was SP 0 fragmentation below the line, and unfortunately we only got SP 0 storage associated with the two TCBs that RTM decided to dump, which you can guess made things difficult for me to track down. Luckily a couple of days ago we got another dump, from another customer, with the same below-the-line storage issues, but luckily the dumped SP 0 had a lot more info. A SYSMDUMP would have come in very handy in those environments. (Now I'm fighting an internal battle between SYSMDUMP and SYSABEND. One of our support reps has some REXX programs he's written to parse SYSUDUMP/ABEND, and I'm trying to bring them into the late 1990s with IPCS and re-writing the REXX programs to do the same thing.) Also, I'll ask just because, but does Phoenix have any openings? I like what I'm doing, but there are some issues within the company that are making me wonder if it was a good thing to take this position so quickly. Thanks and best regards, Ray Mullins -- M. Ray Mullins Roseville, CA, USA http://www.catherdersoftware.com/ http://www.mrmullins.big-bear-city.ca.us/ http://www.the-bus-stops-here.org/ German is essentially a form of assembly language consisting entirely of far calls heavily accented with throaty guttural sounds. ---ilvi French is essentially German with messed-up pronunciation and spelling. --Robert B Wilson English is essentially French converted to 7-bit ASCII. ---Christophe Pierret [for Alain LaBonté] > -Original Message- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Edward Jaffe > Sent: Tuesday, 11 September, 2007 09:36 > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: SYSMDUMP in DB2 SP WLM > > Wayne Driscoll wrote: > > Search the archives for some details from Ed Jaffe regarding pointing > > the SYSMDUMP DD to a SYSOUT dataset, and then saving it to a dataset > if > > and only if you need it. > > > > SYSMDUMP to sysout. The only way to fly! (Or, at least, the only way I > fly.) ;-) > > http://bama.ua.edu/cgi-bin/wa?A2=ind0704&L=ibm-main&P=R59172&I=1&X=- > http://bama.ua.edu/cgi-bin/wa?A2=ind0704&L=ibm-main&P=R59580&I=1&X=- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SYSMDUMP in DB2 SP WLM
>(off-list to hide my ignorance) No it wasn't! - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
