> -----Original Message-----
> From: IBM Mainframe Discussion List 
> [mailto:[EMAIL PROTECTED] On Behalf Of Craddock, Chris
> Sent: Monday, May 19, 2008 11:42 AM
> To: [email protected]
> Subject: Re: SMP/E question.
> 
> > Well, I blew an entire 3390-3 trying to do a receive. Around here,
> DASD
> > is again considered a "premium" resource.
> 
> Woo hoo! A whole 2.5 GiB? John, you're a wild man :-) 
> 
> This is one of the primary reasons we mainframers are a bit of an
> endangered species. We don't really have any understanding of what's
> "big" anymore.
> 
> CC

I do understand. Our current CIO thinks that we are lazy <elided> who
just don't want to bother with doing DASD management. After all, surely
we can manage with less that a 20% "head room" on DASD for "unexpected
demand". This is in the test pool. He would actually like the
programmers to tell DASD management how big a file is likely to be! Can
you imagine? Our programmers couldn't figure that out in 2.73E+100
years! When we had asked them in the past, their general response has
been along the lines of "how should we know? That's your job" (no, it's
not).

--
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

Reply via email to