Bob, just food for thought. In our environment we place the IPL text for the SAD program on our DLIB volume. As an example for our z/OS 2.3 lpars we end up with three DLIB volumes. One for our sand box lpars, one for our test lpars and one for our production lpars. We build the IPL text on each. This way if we have to rebuild the program because of maintenance we do it as we move up maintenance from sand box to test to production.
Thanks.. Paul Feller GTS Mainframe Technical Support -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Richards, Robert B. (CTR) Sent: Thursday, April 1, 2021 12:20 PM To: [email protected] Subject: Re: Stand Alone Dump questions [EXTERNAL] Jim, My foot thanks you! 😊 I'll find a smallish volume (3390-1) and assemble the IPL text there. As for the datasets, I'll consult with my storage admin guy to see which size DASD he wants me to consume. 😊 Bob -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jim Mulder Sent: Thursday, April 1, 2021 12:16 PM To: [email protected] Subject: Re: Stand Alone Dump questions As stated in the manual: Do not place a data set that is intended to contain a stand-alone dump on a volume that also contains a page data set that the stand-alone dump program you might need to dump. When stand-alone dump initializes a page volume for virtual dump processing, it checks to see if the output dump data set also exists on this volume. If it does, the stand-alone dump program issues message AMD100I and does not retrieve any data from page data sets on this volume. Thus, the dump might not contain all of the data that you requested. This lack of data can impair subsequent diagnosis. The dump data set cannot be defined on the same volume that contains the IPL text of stand-alone dump. The maximum size of a single-volume DASD dump data set depends on the type of data set. Conventional sequential (DSNTYPE=BASIC) data sets can span 65,535 tracks per volume, and can hold approximately 3 GB per volume. Extended format (DSNTYPE=EXTREQ) data sets are supported by z/OS® V1R6 and later releases. Extended format sequential data can hold 4,294,967,295 blocks per volume. The maximum size for extended format sequential is approximately 98,304 GB per volume. You cannot use striping or compression options for extended format sequential data sets. You must use the guaranteed free space option to require DFSMS to reserve space at the time that the data set is created. Large format data sets are supported by z/OS V1R7 and later releases. Large format (DSNTYPE=LARGE) data sets can span 16,777,215 tracks per volume. The maximum size for large format data sets is 768 GB per volume. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" <[email protected]<mailto:[email protected]>> wrote on 04/01/2021 10:12:52 AM: > From: "Richards, Robert B. (CTR)" <000001c91f408b9e-dmarc- > [email protected]<mailto:[email protected]>> > To: [email protected]<mailto:[email protected]> > Date: 04/01/2021 12:05 PM > Subject: Stand Alone Dump questions > Sent by: "IBM Mainframe Discussion List" > <[email protected]<mailto:[email protected]>> > > It has been a long time since I messed around with modifying this > stuff and, yes, I should RTFM, but I'm asking here so others can > benefit from the questions (that's my story and I'm sticking with it!@ <grin>) > > Is there any reason *not* to use Mod-27 or -54s volumes? > > Is there any reason against placing the SADMP text on the first of the > SA dump volumes? > > Are there any size restrictions on the datasets? > > Thanks for any and all answers, > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- Please note: This message originated outside your organization. Please use caution when opening links or attachments. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
