Knutson, Sam
2006-05-30 13:40:34 UTC
Hi,
I am looking at the new RMF III reports introduced in z/OS R7 to provide
information on SMS managed disk space:
SPACEG Storage space
SPACED Disk space
I cannot understand why in the world at least SPACEG is not being logged
to an SMF record were it would be useful! The data is good for our
storage team who like SMS pool utilization at this granularity. Looking
at it highlights again some frustrating limitations of RMF III.
SORT and FILTER options are not present on these and many other reports
when they should be available on all ISPF reports.
I am spoiled by MXI and TMON roster (GRF) screens which provide good
filtering and sorting options:-)
Any RMF III data should be optionally recorded in SMF instead of only
the VSAM data sets. MXG provides an assembler program ASMRMFV to
extract the contents of the VSAM files into a sequential file to process
with SAS/MXG. I don't think support has been added for the new internal
records that support SPACEG/SPACED yet but even when this is done it is
a kludge.
Disk space is yet another metric that makes sense to collect only once
in a Sysplex/SMSplex but no automated way to do that is provided and the
user has to know which system is recording the data to look at it. For
all vendors please automate the process of collecting data (if the
customer specifies) once within a sysplex providing for a preference
list of systems on which they prefer collection to take place. Please
automate reporting and query so that users don't care which systems were
active and which was recording the data so long as they can invoke the
query interface on any system in the Sysplex. Sysplex master gather was
at least the right concept.
If nothing else couldn't RMF provide the ONLYIF PARMLIB statement
support by DFSMShsm so that it would be easy to do this. The previous
recommended techniques of using an MVS Static symbol is pretty ugly when
you want to specify a couple dozen storage groups on one system and
NOSGSPACE on all the others. You can do it string them all together but
it's ugly and there is no supported interface to update a system symbol
dynamically while the storage team will certainly eventually add or
delete a storage group.
SGSPACE(ADD(DB2LOGS )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(DB2PROD )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(DB2QUERY)) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(EPOLICY )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(EPOLICY2)) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(G1 )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(G2 )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(G3 )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(IMAGECPY)) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(IMSLOGS )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(IMSPROD )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(OBJDATA )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(QA )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(QAB )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGDBA )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGDRP )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGIMS9 )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGOMVS )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGOMVSYS)) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGSYSTEM)) /* COLLECT SPACE INFORMATION */
While I am at it why or why didn't anyone with access to the IBM
internal documentation consider that since it's trivial for them to get
a list of all active storage groups maybe they should allow *ALL to be
specified by the customer and just go and locate all POOL type storage
groups.
My relationship with RMF data is always love/hate. The data is
generally very good if present and RMF is very reliable but the user
interface for the RMF ISPF interface continues to leave something to be
desired.
Just thinking out loud here but maybe someone else can shed some light
on the reasons behind these limitations or can say they really aren't as
limiting as it seems to me.
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:***@geico.com
(office) 301.986.3574
To define recursion, we must first define recursion.
][
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
I am looking at the new RMF III reports introduced in z/OS R7 to provide
information on SMS managed disk space:
SPACEG Storage space
SPACED Disk space
I cannot understand why in the world at least SPACEG is not being logged
to an SMF record were it would be useful! The data is good for our
storage team who like SMS pool utilization at this granularity. Looking
at it highlights again some frustrating limitations of RMF III.
SORT and FILTER options are not present on these and many other reports
when they should be available on all ISPF reports.
I am spoiled by MXI and TMON roster (GRF) screens which provide good
filtering and sorting options:-)
Any RMF III data should be optionally recorded in SMF instead of only
the VSAM data sets. MXG provides an assembler program ASMRMFV to
extract the contents of the VSAM files into a sequential file to process
with SAS/MXG. I don't think support has been added for the new internal
records that support SPACEG/SPACED yet but even when this is done it is
a kludge.
Disk space is yet another metric that makes sense to collect only once
in a Sysplex/SMSplex but no automated way to do that is provided and the
user has to know which system is recording the data to look at it. For
all vendors please automate the process of collecting data (if the
customer specifies) once within a sysplex providing for a preference
list of systems on which they prefer collection to take place. Please
automate reporting and query so that users don't care which systems were
active and which was recording the data so long as they can invoke the
query interface on any system in the Sysplex. Sysplex master gather was
at least the right concept.
If nothing else couldn't RMF provide the ONLYIF PARMLIB statement
support by DFSMShsm so that it would be easy to do this. The previous
recommended techniques of using an MVS Static symbol is pretty ugly when
you want to specify a couple dozen storage groups on one system and
NOSGSPACE on all the others. You can do it string them all together but
it's ugly and there is no supported interface to update a system symbol
dynamically while the storage team will certainly eventually add or
delete a storage group.
SGSPACE(ADD(DB2LOGS )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(DB2PROD )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(DB2QUERY)) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(EPOLICY )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(EPOLICY2)) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(G1 )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(G2 )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(G3 )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(IMAGECPY)) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(IMSLOGS )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(IMSPROD )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(OBJDATA )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(QA )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(QAB )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGDBA )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGDRP )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGIMS9 )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGOMVS )) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGOMVSYS)) /* COLLECT SPACE INFORMATION */
SGSPACE(ADD(SGSYSTEM)) /* COLLECT SPACE INFORMATION */
While I am at it why or why didn't anyone with access to the IBM
internal documentation consider that since it's trivial for them to get
a list of all active storage groups maybe they should allow *ALL to be
specified by the customer and just go and locate all POOL type storage
groups.
My relationship with RMF data is always love/hate. The data is
generally very good if present and RMF is very reliable but the user
interface for the RMF ISPF interface continues to leave something to be
desired.
Just thinking out loud here but maybe someone else can shed some light
on the reasons behind these limitations or can say they really aren't as
limiting as it seems to me.
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:***@geico.com
(office) 301.986.3574
To define recursion, we must first define recursion.
][
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html