What size SYSRES do most shops use these days?
We have settled on Mod-27 as our "standard" volume for almost
everything. We also have some Mod-9s and Mod-216s for special purposes.
No Mod-1s, Mod-2s, Mod-3s, Mod-54s, or any other "oddball" sizes. Just
the three described above...
On 10/4/2018 8:26 AM, Jesse 1 Robinson wrote:
I sympathize with IBM's predicament in reading the future maintenance tea
leaves. The 'fix rate' for a product might be subject to guesstimation from
past experience. But the effects of future enhancements like SPEs and customer
requirements are a bundle of uncertainties wrapped in unknowns. The change from
six month to two year release cycles further clouded space predictions.
I think customers are best off expecting data set expansions. A few like
LINKLIB and LPALIB can be deliberately oversized as likely candidates for
increase in a variety of components. But the migratable sysres volume is
limited to whatever size installation has settled on. Secondary extents, in my
view, allow for unpredictable expansion with acceptable risk.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John Eells
Sent: Thursday, October 04, 2018 4:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: S106 abends after copying into LINKLIST
Elardus Engelbrecht wrote:
This is why you see in Program Directories the required space for each
dataset/OMVS files needed for each product you ordered.
Let's just be clear about what those space numbers represent.
They are:
- a fixed percentage larger (10 or 15%, I forget right now) than the amount of
space consumed by each data set at a particular point in time
- are measured at the specified block sizes when the FMIDs represented by that
program directory were submitted to software manufacturing and never updated
- provide information for only that product and no others that might share the
data set.
So if PTFs cause the space required to grow by more than the fixed percentage,
or you use different block sizes than we specify (which is not to your
advantage in general), or fail to add the space required by all products
sharing a data set together, you will be in x37 City before you know it.
ServerPac production is smart enough to adjust space on the fly, BTW, so the
free space allocated by default stays at a fixed percentage even as PTFs
consume more space in the data sets for the products included. For CBPDO, you
get to guess yourself.
--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com
--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
