Thompson, Steve wrote:
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of John Eells
Sent: Tuesday, September 11, 2007 11:47 AM
To: [email protected]
Subject: Re: ServerPac Installs and dataset allocations
<SNIP>
Without the APAR numbers, it's a bit hard to say (smile), but in any
case, I was talking about the current code, not history.
<SNIP>
;-) RETAIN is your friend.
The keywords, severpac volser [and/or] sms, return some interesting
PUBLIC APARs. I wonder if it will return the "internal" development
APARs to you, being you are internal.
<snip>
Oddly enough I'd looked already. I wrote the SMS support spec for
ServerPac and I'd have been acutely aware of defects related to the
design or its execution. Even now, as you see, I retain some degree of
professional interest.
In any event, searching for ServerPac, volser, and SMS return one hit in
RETAIN, OW54994, which has nothing to do with primary or secondary space
allocation specification. ServerPac and SMS return 21 hits (most are
even for ServerPac ;-), none of which have to do with space allocation
specification either. Dialog defects, incorrectly built JCL and such,
sure, but I found nothing that says the code that processes the space
allocation amounts is broken.
So far as I know, all the ServerPac APARs are public, by the way. It's
hard to imagine a valid reason to restrict any of them (which is not to
say that it has *never* happened or never could, of course).
--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
[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
