> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Mark Zelden > Sent: Monday, May 19, 2008 11:32 AM > To: [email protected] > Subject: Re: SMP/E question. > > On Mon, 19 May 2008 11:23:59 -0500, McKown, John > <[EMAIL PROTECTED]> wrote: > > > >> > >> BTW, I don't allocate SMPWKDIR. I just have a large > SMPNTS. And I > >> know mainframe dasd is not cheap compared to the sata drive in your > >> workstation, but in the total scheme of your mainframe dasd, how > >> much of a pain would it be to get a little more to support > >> this the way > >> it was meant to work? > >> > >> Mark > > > >Well, I blew an entire 3390-3 trying to do a receive. Around > here, DASD > >is again considered a "premium" resource. The new CIO firmly believes > >that we are just wasting space left and right and wants __strong__ > >justification for DASD. To the point were we may start getting Sx37 > >abends again due to lack of space. I know, that what I can do? I've > >suffered the pain, he has not. > > > > What were you trying to receive? ALL maintenance, recommended, HIPERs, > a product? How far behind current are you if it is regular > maintenance? > And if it is regular maintenance, perhaps you can split it up by doing > recommended first or just HIPERs etc. Then if you keep more current > it doesn't have to be so big. Of course the problem will then move to > your SMPPTS if you never apply / accept and clean up anything. > > Mark
It wasn't all that much. On my Linux system, it takes up 621,444KiB of space. I was able to create a 19,890 track zFS dataset on one of my "UNIX" volumes. That got me 1,909,440 blocks (512 bytes) or 954,720KiB of space. This order had 1,018 PTFs, but many of them were "NOT RECEIVED". Some were already APPLIED and some had NO APPLICABLE ++VER. I think that I must have goofed up and didn't subset the order correctly on ShopzSeries. Once unwound on Linux, the SMPHOLD was 1.9M and SMPPTFIN was 1.5G. Well, that blew my single volume right there. Especially having the smpwkdir and smpnts being in the that same filesystem. Requesing another volume here is, to me, very painful due to our backup methodology. It is a very good vendor product, but basically you need to initialize the volume then update the product's inventory. This cannot be done while the product is actually doing backups. And our DASD backups sometimes run into the middle of the day. I know, fuzzy backups are bad. But they have been "risk accepted" by management, so there is 0 that I can do. After all, we do need to do productive work on occassion <VBG>. Our general maintenance philosophy is basically "do nothing unless something breaks". We do a complete system replacement about every other year / release. We do vendor products this same way, unless something bites us. <shrug> We don't have enough staff do to otherwise (common experience). -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- 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
