Stand alone Dump with ICC cards
Is anyone out there using ICC for a z/OS console. We are switching over from our 3174's and started to use ICC consoles so I thought id ask our operator to do a SAD from it. The first problem I had was I didn't change the SAD to use the new console (address 1300) I changed it had them we do it but we get a xwait on the emulator, like it cant find the console. Here is what I have coded job ran with zero's, No wait state just sits there the system AMDSADMP IPL=D3390,VOLSER=AVE3EC, X MINASID=ALL, X DDSPROMPT=YES,X OUTPUT=T1511,X REUSEDS=CHOICE,X CONSOLE=((1300,3278),(1310,3278)) END Is there anything that needs to be coded for a ICC type of console to do a SAD? Thanks in advance. Andy Internet: Mailto:[EMAIL PROTECTED] The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- 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: Stand alone Dump with ICC cards
It is probably waiting for an interrupt from the device. Hit RESET/ENTER and it should wake up.. Is anyone out there using ICC for a z/OS console. We are switching over from our 3174's and started to use ICC consoles so I thought id ask our operator to do a SAD from it. The first problem I had was I didn't change the SAD to use the new console (address 1300) I changed it had them we do it but we get a xwait on the emulator, like it cant find the console. Here is what I have coded job ran with zero's, No wait state just sits there the system AMDSADMP IPL=D3390,VOLSER=AVE3EC, X MINASID=ALL, X DDSPROMPT=YES,X OUTPUT=T1511,X REUSEDS=CHOICE,X CONSOLE=((1300,3278),(1310,3278)) END Is there anything that needs to be coded for a ICC type of console to do a SAD? Thanks in advance. -- 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: Stand alone Dump with ICC cards
Thanks we tried that a few times just got a xwait... Do you code in the macro below the 4 digit console that way? Thats what im wondering. Andy Internet: Mailto:[EMAIL PROTECTED] "IBM Mainframe Discussion List" wrote on 03/20/2008 10:28:36 AM: > It is probably waiting for an interrupt from the device. Hit RESET/ENTER > and it should wake up.. > > > Is anyone out there using ICC for a z/OS console. We are switching over > from our 3174's and started to use ICC consoles so I thought id ask our > operator to do a SAD from it. The first problem I had was I didn't > change > the SAD to use the new console (address 1300) I changed it had them we > do > it but we get a xwait on the emulator, like it cant find the console. > > Here is what I have coded job ran with zero's, No wait state just sits > there the system > > AMDSADMP IPL=D3390,VOLSER=AVE3EC, > X >MINASID=ALL, X >DDSPROMPT=YES,X >OUTPUT=T1511,X >REUSEDS=CHOICE,X >CONSOLE=((1300,3278),(1310,3278)) > END > > Is there anything that needs to be coded for a ICC type of console to do > a > SAD? Thanks in advance. > > The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- 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: Stand alone Dump with ICC cards
Andy, We use the ICC controllers for consoles and have not had a problem doing SA dumps. Here is our console piece of the AMDSADMP macro. CONSOLE=((200,3278),(201,3278),(300,3278),(301,3278)) here is the ICC/OSA setup Number Name IP Addr Type DHD RSP RTO 200 UTM10001 10.10.10.11 Console Enable 600 Enable 10 Sec 201 UTM10002 10.10.10.13 Console Enable 600 Enable 10 Sec 300 UTM10009 10.10.10.11 Console Enable 600 Enable 10 Sec 301 UTM10010 10.10.10.42 Console Enable 600 Enable 10 Sec Cliff McNeill MD Anderson Cancer Center _ Connect and share in new ways with Windows Live. http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008 -- 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: Stand alone Dump with ICC cards
The coding for the SAD looks good to me. If all else fails, the HCM can be used to control the SAD... > It is probably waiting for an interrupt from the device. Hit RESET/ENTER > and it should wake up.. > > > Is anyone out there using ICC for a z/OS console. We are switching over > from our 3174's and started to use ICC consoles so I thought id ask our > operator to do a SAD from it. The first problem I had was I didn't > change > the SAD to use the new console (address 1300) I changed it had them we > do > it but we get a xwait on the emulator, like it cant find the console. > > Here is what I have coded job ran with zero's, No wait state just sits > there the system > > AMDSADMP IPL=D3390,VOLSER=AVE3EC, > X >MINASID=ALL, X >DDSPROMPT=YES,X >OUTPUT=T1511,X >REUSEDS=CHOICE,X >CONSOLE=((1300,3278),(1310,3278)) > END > > Is there anything that needs to be coded for a ICC type of console to do > a > SAD? Thanks in advance. > > The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- 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: Stand alone Dump with ICC cards
Don't know but why bother? I always use the SYSCONS (HMC operating system messages) for standalone dump console - works great for me anyway. Dick >>> "Andy White" <[EMAIL PROTECTED]> 3/20/2008 9:49:38 AM >>> Is anyone out there using ICC for a z/OS console. We are switching over from our 3174's and started to use ICC consoles so I thought id ask our operator to do a SAD from it. The first problem I had was I didn't change the SAD to use the new console (address 1300) I changed it had them we do it but we get a xwait on the emulator, like it cant find the console. Here is what I have coded job ran with zero's, No wait state just sits there the system AMDSADMP IPL=D3390,VOLSER=AVE3EC, X MINASID=ALL, X DDSPROMPT=YES,X OUTPUT=T1511,X REUSEDS=CHOICE,X CONSOLE=((1300,3278),(1310,3278)) END Is there anything that needs to be coded for a ICC type of console to do a SAD? Thanks in advance. Andy Internet: Mailto:[EMAIL PROTECTED] The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. -- 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 == CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy Policy and Henry Ford My Health at www.henryford.com for more detailed information. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us. ==
Re: Stand alone Dump with ICC cards
HMC--defined to MVS as SYSCONS--works great on several levels. You don't have to worry about... -- Altered console configurations -- Flaky tubes/PCs/controllers -- Updating SAD procedures We don't take many standalone dumps, but three changes in the past several years have greatly improved reliability: 1, Use only SYSCONS (no more MCS consoles) 2. Use only DASD (no more tapes) 3. Set up LOAD profiles on the HMC exclusively for standalone dump. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] Richard Bond <[EMAIL PROTECTED]> Sent by: IBM To Mainframe IBM-MAIN@bama.ua.edu Discussion Listcc <[EMAIL PROTECTED] .edu> Subject Re: Stand alone Dump with ICC cards 03/20/2008 12:59 PM Please respond to IBM Mainframe Discussion List <[EMAIL PROTECTED] .edu> Don't know but why bother? I always use the SYSCONS (HMC operating system messages) for standalone dump console - works great for me anyway. Dick >>> "Andy White" <[EMAIL PROTECTED]> 3/20/2008 9:49:38 AM >>> Is anyone out there using ICC for a z/OS console. We are switching over from our 3174's and started to use ICC consoles so I thought id ask our operator to do a SAD from it. The first problem I had was I didn't change the SAD to use the new console (address 1300) I changed it had them we do it but we get a xwait on the emulator, like it cant find the console. Here is what I have coded job ran with zero's, No wait state just sits there the system AMDSADMP IPL=D3390,VOLSER=AVE3EC, X MINASID=ALL, X DDSPROMPT=YES,X OUTPUT=T1511,X REUSEDS=CHOICE,X CONSOLE=((1300,3278),(1310,3278)) END Is there anything that needs to be coded for a ICC type of console to do a SAD? Thanks in advance. Andy Internet: Mailto:[EMAIL PROTECTED] -- 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: Stand alone Dump with ICC cards
On Thu, 20 Mar 2008 13:41:26 -0700, Skip Robinson <[EMAIL PROTECTED]> wrote: >HMC--defined to MVS as SYSCONS--works great on several levels. You don't >have to worry about... > >-- Altered console configurations > >-- Flaky tubes/PCs/controllers > >-- Updating SAD procedures > >We don't take many standalone dumps, but three changes in the past several >years have greatly improved reliability: > >1, Use only SYSCONS (no more MCS consoles) > >2. Use only DASD (no more tapes) > >3. Set up LOAD profiles on the HMC exclusively for standalone dump. > >. Exactly what we do. Along with the option to automatically overwrite the sadump data set if it is not empty and no operator reply. Unfortunately I had the pleasure of testing it myself about a month ago during prime time. One our critical LPARs went into a spin loop. I knew right away because I logon to our vtam session manager from that LPAR and my session hung. I then opened my remote console application (AFREMOTE) and couldn't get a console response. At this point I knew it was disabled wait or spin loop. I logged on to the HMC and saw the spin loop and immediately initiated the SADUMP. The total time of the outage from hang to CICS regions up an functional was 34 minutes which I know is a local record (not one that I am anxious to try and beat!). :-) Not bad considering this LPAR had 22G of real storage. The SADUMP performance with striping is amazing! Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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: Stand alone Dump with ICC cards
Hello Andy, I also use only the HMC for SAD support our basic operator instructions: 1. logon to HMC as OPERATOR 2. logon to MVS Console on SYSPLEX partner system 3. Select SAD_sysname HMC Icon. 4. Perform RESET-NORMAL, Answer YES and OK. 5. On MVS Console, reply to IXC402D or IXC102A messages, or issue V XCF,sysname,OFFLINE (reply is SYSNAME=sysname) Actions 3-5 expedite sysplex system recovery actions. 6. Perform ACTIVATE SAD_sysname HMC ICON, Answer Yes and OK. 7. Start Operating System Messages (double-click with SAD_sysname Icon highlighted) 8. Enter a NULL command, by clicking on SEND COMMAND and then clicking on SEND button. 9+++ now answer SAD prompts as required. Regards Bruce Hewson -- 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: Stand alone Dump with ICC cards
IBM Mainframe Discussion List wrote on 03/23/2008 12:29:20 AM: > I also use only the HMC for SAD support > > our basic operator instructions: > 1. logon to HMC as OPERATOR > 2. logon to MVS Console on SYSPLEX partner system > 3. Select SAD_sysname HMC Icon. > 4. Perform RESET-NORMAL, Answer YES and OK. > 5. On MVS Console, reply to IXC402D or IXC102A messages, or issue V > XCF,sysname,OFFLINE (reply is SYSNAME=sysname) > > Actions 3-5 expedite sysplex system recovery actions. > > 6. Perform ACTIVATE SAD_sysname HMC ICON, Answer Yes and OK. > 7. Start Operating System Messages (double-click with SAD_sysname Icon > highlighted) > 8. Enter a NULL command, by clicking on SEND COMMAND and then clicking on > SEND button. > > 9+++ now answer SAD prompts as required. You can avoid step 8 by specifying SCSYSC as the Load Parameter in the profile that you are using to IPL SAD. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- 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: Stand alone Dump with ICC cards
Here's the job step that creates our standalone dump. Remember that the page dump data set is now on the SAD IPL volume as SYS1.PAGEDUMP.Vvolser My job includes a preceding step to delete/purge the old one if any and a succeeding step to catalog the new one. Cataloging is not required. The DUMP= parameters have accumulated values over the years from various suggestions or problems. SAD as set up here--along with the SCSYSC load parm recommend by Jim Mulder--will dump straight to DASD with no operator intervention after the load. A default title is generated. //SADCREATE EXEC PGM=AMDSAOSG,REGION=20M //SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB // DD DISP=SHR,DSN=SYS1.MODGEN //GENPRINT DD SYSOUT=* //GENPARMS DD * AMDSADMP VOLSER=sad-ipl-volser, * CONSOLE=SYSC, USE HMC AS CONSOLE* REUSEDS=ALWAYS, ALWAYS OVERWRITE DATA SET * MINASID=PHYSIN, GET AT LEAST SWAPPED IN GUYS * DUMP=('SP(ALL) IN ASID(1,'JES2','JESXCF') * ALSO DATASPACES OF ASID(1,'DUMPSRV','JESXCF','APPC','SMS* VSAM','CONSOLE','SMSPDSE','SMSPDSE1') * ALSO PAGETABLES OF DATASPACES'),* OUTPUT=D SADUMP TO 1st VOL OF SYS1.SADMP END . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] Jim Mulder <[EMAIL PROTECTED] OM>To Sent by: IBM IBM-MAIN@bama.ua.edu Mainframe cc Discussion List <[EMAIL PROTECTED] Subject .edu> Re: Stand alone Dump with ICC cards 03/22/2008 10:28 PM Please respond to IBM Mainframe Discussion List <[EMAIL PROTECTED] .edu> IBM Mainframe Discussion List wrote on 03/23/2008 12:29:20 AM: > I also use only the HMC for SAD support > > our basic operator instructions: > 1. logon to HMC as OPERATOR > 2. logon to MVS Console on SYSPLEX partner system > 3. Select SAD_sysname HMC Icon. > 4. Perform RESET-NORMAL, Answer YES and OK. > 5. On MVS Console, reply to IXC402D or IXC102A messages, or issue V > XCF,sysname,OFFLINE (reply is SYSNAME=sysname) > > Actions 3-5 expedite sysplex system recovery actions. > > 6. Perform ACTIVATE SAD_sysname HMC ICON, Answer Yes and OK. > 7. Start Operating System Messages (double-click with SAD_sysname Icon > highlighted) > 8. Enter a NULL command, by clicking on SEND COMMAND and then clicking on > SEND button. > > 9+++ now answer SAD prompts as required. You can avoid step 8 by specifying SCSYSC as the Load Parameter in the profile that you are using to IPL SAD. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- 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: Stand alone Dump with ICC cards
I dug into the doc once again for more info on Mark's reference to 'striping'. I find this comment in Diagnosis: Tools and Service Aids: "Extended format data sets are supported by z/OS V1R6 and later releases. Extended format sequential data sets can hold 16,777,215 blocks. If you use a maximum block size, 29120 bytes, approximately 488 GB can fit. 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." On the other hand: "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. If you use a maximum block size, 29120 bytes, approximately 768 GB can fit. " I have two Mod-9 volumes with SYS1.SADMP spanning both as DSNTYPE=LARGE for a total of 20,032 cylinders. I use the AMDSADDD REXX utility to enable SAD to write data to both volumes in a way I understood as 'logical striping' (my term). Is there a better option? Mark Zelden <[EMAIL PROTECTED] CHNA.COM> To Sent by: IBM IBM-MAIN@bama.ua.edu Mainframe cc Discussion List <[EMAIL PROTECTED] Subject .edu> Re: Stand alone Dump with ICC cards 03/21/2008 05:47 AM Please respond to IBM Mainframe Discussion List <[EMAIL PROTECTED] .edu> On Thu, 20 Mar 2008 13:41:26 -0700, Skip Robinson <[EMAIL PROTECTED]> wrote: The SADUMP performance with striping is amazing! Mark -- Mark Zelden -- 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: Stand alone Dump with ICC cards
Hello Rick, StandAlone Dump dasd striping is not the same as DFSMS dataset striping. To build the SAD datasets onto multiple volumes you run something like this:- //STEP1EXEC PGM=IKJEFT01 //SYSPROCDD DISP=SHR,DSN=SYS1.SAMPLIB //SYSTSPRT DD SYSOUT=* //SYSTSINDD * %AMDSADDD DEFINE + (SBXDM2,SBXDM3,SBXDM4,SBXDM5,SBXDM6)(SYS1.SADMP) + 3390 3335 N /* // SAD will then run 6 separate data streams to write to the six volumes in parallel. IPCS will merge and sort the records from all six datasets/volumes into a coherent image when you access or copy the SADump. Regards Bruce Hewson -- 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: Stand alone Dump with ICC cards
IBM Mainframe Discussion List wrote on 03/24/2008 07:41:38 PM: > I dug into the doc once again for more info on Mark's reference to > 'striping'. I find this comment in Diagnosis: Tools and Service Aids: > > "Extended format data sets are supported by z/OS V1R6 and later releases. > Extended format sequential data sets can hold 16,777,215 blocks. If you use > a maximum block size, 29120 bytes, approximately 488 GB can fit. 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." > > On the other hand: > > "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. If you > use a maximum block size, 29120 bytes, approximately 768 GB can fit. " > > I have two Mod-9 volumes with SYS1.SADMP spanning both as DSNTYPE=LARGE for > a total of 20,032 cylinders. I use the AMDSADDD REXX utility to enable SAD > to write data to both volumes in a way I understood as 'logical striping' > (my term). > > Is there a better option? SADMP uses a blocksize of 24960 for 3390 geometry, not 29120. So that works out to about 383 GB for Extended Sequential, and 766 GB for DSNTYPE=LARGE (assuming the quoted number of blocks and number of tracks limits are correct). We avoid using the term 'Striping' for SADMP data sets, because the way SADMP dumps in parallel to a multi-volume data set is different than what DFSMS does with an Extended Format Sequential data set which has more than one stripe. You can use multi-volume with Extended Format, DSNTYPE=LARGE, or ordinary sequential. SADMP performance-wise, it shouldn't make any significant difference. If you are trying to optimize the dumping speed, for a DS8000 with Ficon channels on a z9 processor, I would use more than two volumes. Using z/OS 1.9 on a z9 with 3 volumes (spread across 3 different DS8000s, although I don't know how relevant that is), I was able to get a data rate of a bit over 300MB per second while dumping real storage, at which point the dumping process became CPU bound. z/OS 1.10 may be a little better - I removed some unnecessary zeroing of I/O buffers in that release - but I haven't gotten around to measuring it yet. A z10 processor should also be better, but I haven't measured that yet either. For slower DASD or channels, a larger number of volumes might be beneficial. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- 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: Stand alone Dump with ICC cards
IBM Mainframe Discussion List wrote on 03/25/2008 01:29:43 AM: > IPCS will merge and sort the records from all six datasets/volumes into a > coherent image when you access or copy the SADump. IPCS COPYDUMP will merge the data from the multiple volumes, which is why we recommend that you copy a multivolume data set with COPYDUMP before reading it in any other fashion. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- 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: Stand alone Dump with ICC cards
On Mon, 24 Mar 2008 16:41:38 -0700, Skip Robinson <[EMAIL PROTECTED]> wrote: >I dug into the doc once again for more info on Mark's reference to >'striping'. I find this comment in Diagnosis: Tools and Service Aids: > >"Extended format data sets are supported by z/OS V1R6 and later releases. >Extended format sequential data sets can hold 16,777,215 blocks. If you use >a maximum block size, 29120 bytes, approximately 488 GB can fit. 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." > >On the other hand: > >"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. If you >use a maximum block size, 29120 bytes, approximately 768 GB can fit. " > >I have two Mod-9 volumes with SYS1.SADMP spanning both as DSNTYPE=LARGE for >a total of 20,032 cylinders. I use the AMDSADDD REXX utility to enable SAD >to write data to both volumes in a way I understood as 'logical striping' >(my term). > >Is there a better option? > > FYI... the SADUMP striping has been available since z/OS 1.2. As far as "whats best", there was a good SHARE session from July 2001 given by Greg Dyck - "When the Big Crash Occurs Standalone Dump" Session number 2823. There is still a lot of good information in that and does include the z/OS 1.2 changes. For something more current, there is this: z/OS Best Practices: Large Stand-Alone Dump Handling - Version 2 http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD103286 Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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: Stand alone Dump with ICC cards
Mark, >The total time of the outage from hang to CICS regions up an functional >was 34 minutes which I know is a local record (not one that I am anxious >to try and beat!). :-) >Not bad considering this LPAR had 22G of real storage. The SADUMP >performance with striping is amazing! Can you provide a number how long dumping of real storage took? (Which options?) I was able to test sadump on a 6GB real lpar, and the outage time from IPLing sadump to IPLing MVS again was less than 10 minutes (dsntype=large to two volumes): 8:18:50 IPL sadump 8:21:29 AMD095I VIRTUAL DUMP 15% COMPLETED. TOTAL MEGABYTES DUMPED: 8:25:02 End of sadump 8:28:08 Re-IPL 'Specify System parms' (and this only took so long because it took me a while to recognize the end of sadump). I keep getting postponed to test sadump on the big production lpar (well, 10G is big for us) including their IMS/DB2 recovery. I want some numbers in case we ever need an sadump in production to say: 'it'll only be 15 minutes longer, but we'll have a dump to provide IBM'. On a smaller lpar where I recently took several sadumps the actual dumping process appeared shorter than when I took an svcdump (2.5GB real, the svcdump always had to include OMVS and all dataspaces and the SMSPDSE/1 stuff). The capture phase lasted 'forever'. We also found out the hard way that when you need any OMVS stuff in the sadump (like file information for open files), you'd better specify ALSO DATASPACES OF ASID('OMVS') Traditionally, we also dump all of RASPs dataspaces. Regards, Barbara Nitz -- 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: Stand alone Dump with ICC cards
> I was able to test sadump on a 6GB real lpar, and the outage time > from IPLing sadump to IPLing MVS again was less than 10 minutes > (dsntype=large to two volumes): > 8:18:50 IPL sadump > 8:21:29 AMD095I VIRTUAL DUMP 15% COMPLETED. TOTAL MEGABYTES > DUMPED: 8:25:02 End of sadump > 8:28:08 Re-IPL 'Specify System parms' (and this only took so long > because it took me a while to recognize the end of sadump). In z/OS 1.10, you can set things up so that if SADMP completes successfully, it will initiate the IPL of MVS automatically. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- 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