INNOVATION TECHSUPPORT

Transcription

1 INNOVATION TECHSUPPORT VOLUME 3.1 Welcome to the third issue of INNOVATION TECH SUPPORT. TECHSUPPORT is intended as INNOVATION s communication vehicle to those responsible for the use of INNOVATION s products. Each issue will address one aspect of our product line in detail. This issue of TECHSUPPORT will discuss FDREPORT. FDREPORT is a program within the Automatic Backup & Recovery (ABR) system that generates reports on DASD data sets and volumes. You can customize these reports to your needs and the needs of your users. The objectives of TECHSUPPORT are to share with you the answers to common questions that users ask; also to bring you up to date on the products latest capabilities and to differentiate our products capabilities versus the competition. In particular, we have seen users purchase expensive reporting products without realizing that the facilities that they need are within the capabilities of FDREPORT. If you need a report and are not sure how to get it, use the attached reply card to describe what you need and we will send you sample control card examples. These reports will help you determine how your DASD is being used and by whom. Most data centers have started planning the conversion to a System Managed Storage (SMS) environment. FDREPORT can be used to help plan the migration to an SMS environment. What is FDREPORT? FDREPORT, which is a component of ABR, provides extensive customized reporting capabilities to suit many needs and purposes. Its sophisticated data set filtering and report formatting options allow you to select data sets based on more than 100 data set attributes, and to report on those attributes in a format you choose. However, FDREPORT is designed so that simple reports can be generated with very simple reports can be generated with very simple control statements, such as reporting on all online data sets belonging to a certain TSO userid or application prefix. End-users can use many FDREPORT functions without extensive training and can execute canned reports from TSO/ISPF. FDREPORT can be used by DASD Managers, Operations Analysts, System Programmers, etc. to create highly customized reports for management reporting, for space management and for identifying special data sets (such as uncataloged or overallocated data sets), to name just a few uses. FDREPORT s Sources of Information FDREPORT can report on data sets, on-line disk volumes or data sets which have been archived by ABR. It gets its primary input from the VTOCs of online volumes or the ABR Archive Control File and from these it will build lists of data sets to report on. However, if required it will get additional information about those data sets from: VVDS - for information about ICF VSAM clusters and SMS-managed data sets (including SMS class names) System catalog - for catalog status and information contained only in the catalog ABR catalog - for information about ABR backups of data sets ABR model DSCBs - for current backup information Generated information - not in any of the above, but calculated by FDREPORT from those sources (e.g. size in bytes). From all these sources, FDREPORT builds a record containing the data set s attributes. Normally FDREPORT uses that record to generate the requested report, but it can write the record to a data set for later reporting by FDREPORT or other programs. FEBRUARY, 1992 FDREPORT which is a component of ABR, provides extensive customized reporting capabilities to suit many needs and purposes. 1

2 How to Get that REPORT! Here are some examples of complete FDREPORT statements to get frequently used reports, with sample report outputs. Required JCL, additional examples and explanations of all statements and operands are found in Sections through in the FDR 5.1 Manual. WASTED SPACE REPORT Report on overallocated sequential and partitioned data sets on TSO volumes that have 40% or more unused space. Report will be sorted by volume serial and data sets with the most free space being reported first. TITLE LINE = WASTED SPACE ON TSO VOLUMES SELECT VOLG=TSO,DSORG=(PS,PO),%FREE=40 REPORT FIELD=(DSN,VOL,DSORG,%FREE,SIZE) SORT FIELD=(VOL,%FREE),SEQ=(A,D) SUM FIELD=(VOL,SIZEFREE,SIZE) PRINT WASTED SPACE ON TSO VOLUMES DATA SET NAME D/S VOLSER ORG %FR ALLOC 2 FDRSYS.DF.SKELETON TSOLB2 PO SYSP.SUE.REXX TSOLB2 PO FDRSYS.DF.ASM TSOLB2 PO IAMSYS.JFM.LIST TSOLB2 PS FINAL TOTALS -- SIZEFREE SIZE Wasted Space Total Tracks NOTE: COMPAKTOR TYPE = RLSE can be used to release the over-allocated space on these data sets in a very short period of time. POORLY ORGANIZED VSAM CLUSTERS Report on all VSAM files over 3 Megabytes in size with more than 5 CA splits or more than 20 CI splits, and all clusters with more than 16 extents, since all these might be candidates for reorganization. Clusters with the highest CA splits will be listed first: TITLE LINE= VSAM CLUSTERS IN NEED OF REORG XSELECT DSORG=EF,BYTES>3M,CASPLIT> 5,VOLG=IDP XSELECT DSORG=EF,BYTES>3M,CISPLIT> 20,VOLG=IDP XSELECT DSORG=EF,NO EXTENT> 16,VOLG=IDP REPORT FIELD=(CLUSTER,VOL,PRIALLOC,BYTES, BYTESUSE,CASPLIT,CISPLIT,NO EXTENT) SORT FIELD=(CASPLIT,CISPLIT),SEQUENCE=(D,D) PRINT SORT=COMBINE VSAM CLUSTERS IN NEED OF REORG CLUSTER NAME VOLSER PRALO MBYTES MBYUSED CASPL CISPL EXT IDP.MASTER.RECORDS IDPLB IDP.PERM.HISTORY IDPLB

3 IDENTIFY MULTI-VOLUME DATA SETS Find all multi-volume VSAM and non-vsam data sets which may require special handling during DASD conversions. Report will be sorted in data set name sequence. TITLE LINE= DATA SETS CATALOGED ON MULTIPLE VOLUMES DEFAULT SELTERR=NO REPORT FIELD=(DEFAULTS,CATVOLCT) XSELECT CATVOLCT>1,VOL=IDP* SORT FIELD=(DSN) PRINT DATA SETS CATALOGED ON MULTIPLE VOLUMES DATA SET NAME VOLSER D/S RECFM BKSIZE LRECL ALLOC FREE %FR CVC DF.MV IDPLB5 PS FB DF.MV IDPL31 PF FB IAMV.MARKVSAM.CLUSTER.DATA IDPLB4 EF U IAMV.MARKVSAM.CLUSTER.DATA IDPLB5 EF U IAMV.MARKVSAM.CLUSTER.INDEX IDPLB4 EF U REPORT ON DATA SETS LIKELY TO GET Sx37 ABENDS Report on data sets larger than 15 tracks with no secondary allocation and less than 5% freespace, and all data sets with 16 or more extents, since any of them might get Sx37 abends or the VSAM equivalent for lack of space. TITLE LINE= DATA SETS WHICH MAY RUN OUT OF SPACE IF EXTENDED REPORT FIELD=(DSN,DSORG,VOL,SECALLOC,%FREE,NOEXTENT,SIZE) XSELECT SECALLOC=0,%FREE<5,SIZE> 15 XSELECT NOEXTENT=> 15 SORT FIELD=(NOEXTENT,SIZE),SEQ=(D,D) PRINT ONLINE DATA SETS WHICH MAY RUN OUT OF SPACE IF EXTENDED D/S DATA SET NAME ORG VOLSER SCALO %FR EXT ALLOC IPOSAV.SMFDUMPW PS IDPLB IPOUSER.IDP.LABELS PO IDPLB SYSP.FDR.PTFONPC PO IDPLB BAB.CALL.LOG PO IDPLB INHSYS.JMK.ASM PO IDPLB NRN.TEST.ZZZZ.DATA EF IDPLB FDRSYS.REP.ASM LESS THAN 5% FREE PO IDPL REPORT ON POORLY BLOCKED DATA SETS This report will summarize disk data sets which make inefficient use of their assigned disk space. Data sets with small blocksizes (less than 2K) are wasteful because of the overhead of interblock gaps. Also, blocksizes which are greater than a half-track (23476 for 3380s) will waste the remainder of the track. RPTYPE=NONE produces only the summary, showing the blocksizes that were found and the number of data sets using each blocksize (omit RPTYPE to display the actual data sets). XSELECT VOL=IDP*,BLKSIZE< 2048 XSELECT VOL=IDP*,BLKSIZE> SUM FIELD=(DSN,BLKSIZE,VOL) PRINT RPTYPE=NONE FDR400 - FDRABR REPORT STANDARD SUMMARIES - FDREPORT VER 5.1/33P -- INNOVATION DATA PROCESSING - BLKSIZE ( 57) 5 ( 1) 12 ( 1) 80 ( 20) 100 ( 1) 111 ( 1) 121 ( 5) 129 ( 24) 160 ( 1) 264 ( 2) 600 ( 1) 629 ( 1) 670 ( 1) 720 ( 1) 800 ( 39) 1024 ( 3) 1104 ( 168) 1128 ( 1) ( 1) ( 1) ( 2) ( 132) 168 data sets with a blocksize of 1104

4 4 FDREPORT and System Managed Storage FDREPORT Version 5.1 and higher supports reporting on the SMS fields. FDREPORT is able to report on SMS Storage Class, Management Class, Data Class and Storage Group on which the data set resides. Users planning the movement to SMS can use FDREPORT to identify those data sets that are and are not eligible to be SMS managed. How can I prepare for SMS conversion with FDREPORT? FDREPORT can be used to identify data sets that are not supported by SMS such as ISAM, non-icf VSAM, unmovable and uncataloged data sets. The following example shows how to identify these data sets to ease the conversion to SMS; the report also shows the catalog status of each dataset and the volume to which it is cataloged. TITLE LINE= DATA SETS NOT ELIGIBLE FOR SMS ON TSO VOLUMES XSELECT DSORG=(U,IS,AM),DSORG.NE.(EF),VOLG=TSO XSELECT CATALOG=ERR BOLG=TSO XSELECT CATALOG=NO,VOLG=TSO UNSUPPORTED DSORG CATALOGED TO ANOTHER VOL UNCATALOGED REPORT FIELD=(DEFAULTS,CATALOG,CATVOL) PRINT Can FDREPORT help me manage my SMS data sets? FDREPORT can report and summarize based on SMS classes and select based on SMS storage groups so a variety of reports can be generated on SMS-managed data sets and volumes. The example below selects all SMS-managed data sets (data sets that have an SMS storage class assigned) and sorts by storage class name, reporting all data sets which are assigned to each unique storage class, and summarizing based on storage class giving the total occurrences of each class and the total number of tracks of the data sets with that class. You could also report on management class or data class names by changing the field name in the SORT and SUMMARY statements to MGMTCLAS or DATACLAS. TITLE LINE= ALL SMS DATA SETS BY STORAGE CLASS NAME XSELECT STORCLAS.NE.' ' *SEE NOTE 1 SORT FIELD=(STORCLAS,DSN),BREAK=(Y,N) SUMMARIZE ON CLASS NAME SUMMARY FIELD=(STORCLAS,SIZE) REPORT FIELD=(DEFAULTS,SMSCLASS) PRINT ONLINE,INFOMSG=NO NOTE 1: STORCLAS.NE. will select all data sets whose storage class is not blank (all SMS data sets have a storage class). Report by Storage Group This report will identify the largest allocated data sets within a storage group. In addition, if PDSE s are on these volumes, FDREPORT will identify the % used within each PDSE (5.1 Level 32 or higher). FDREPORT will provide the % used information for the PDSE data sets without changing the last reference date as ISPF 3.4 would. TITLE LINE= DATASET LISTING BY STORAGE GROUP AND SIZE REPORT FIELD=(SPLDSNVOL,DSORG,STORGRP,RECFM, LRECL,BLKSIZE,CRDATE,LRDATE, CISPLIT,CASPLIT,SIZE, SECALLOC,MEMBERS,%USED,NOEXTENT) SORT FIELD=(STORGRP,SIZE,DSN),SEQUENCE=(A,D,A,) PRINT ONLINE,SORT=COMBINE,INFOMSF=NO DATA SET NAME DATASET LISTING BY STORAGE GROUP AND SIZE D/S VOLSER ORG STORGRP RECFM LRECL BKSIZE CRDATE LRDATE CISPL CASPL ALLOC SCALO MEMBER %US EXT DEVLJDR.MP.BACKUP M90006 PS STRTSO U DEVLMXS.APDPRFF.ONE.DATA M90017 EF STRTSO U DEVLMXS.USER.GLLIB M90006 POE STRTSO FB DEVLMXS.USER.JCLLIB M90006 POE STRTSO FB DEVLMXS.USER.LIB M90006 POE STRTSO FB

5 Extract Files If you want reports in more than one format from the same group of data sets, then the job will probably run faster if you create an intermediate extract file. For example, consider the two reports on VSAM splits and extents. If these reports were run independently, each one would have to read all of the disk VTOCs to select the desired data sets. But by scanning the VTOCs once and creating an extract file containing only the VSAM data sets, FDREPORT can reprocess the information and produce any number of reports requiring the same data with a minimum of overhead. 5 //REPORT EXEC PGM=FDREPORT //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //ABRMAP DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSUT2 DD DSN=ICF1.FDREPORT.EXTRACT,DISP=(,CATLG), // UNIT=SYSDA,SPACE=(CYL,(1,1)) //SYSIN DD * DEFAULT RESETSEL=YES -PRINT command is to reset selection criteria SELECT DSORG=EF -select all VSAM data sets PRINT ONLINE,RPTYPE=DATA -create extract file REPORT FIELD=(SPLCLS,SPLDSN,VOL,SECAFLAG,PRIALLOC,SECALLOC,SIZE, SIZEUSED,SIZEFREE,BYTESUSE,BYTES,%FREE, CASPLIT,CISPLIT,NOEXTENT) XSELECT BYTES>3M,CASPLIT>=5 -selection for first report SORT FIELD=(CASPLIT,CISPLIT),SEQUENCE=(D,D) PRINT SORT=COMBINE,DATATYPE=EXTRACT -input from extract file SELECT NOEXTENT=16 -selection for second report SORT FIELD=NOEXTENT,SEQUENCE=D -replaces first SORT criteria PRINT SORT=COMBINE,DATATYPE=EXTRACT -input from extract file In this example, the extract file saved as a nontemporary data set so that it can be used for later reports in separate jobs. Another example of using an extract file is example H on page 867 in the manual. Another way you can use extract files is as history files, saving information about the data sets that existed at different times. Extract files can by used as input to programs other than FDREPORT. You can write programs yourself, or you can use software packages such as SAS to read the extract files and do statistical analysis of your DASD. The format of the extract files is available from INNOVATION on request. Report Format and Identification FDREPORT has a default set of attributes it will report on, but you can add to or override that list with the REPORT statement, on which you can list the attributes you want to see. FDREPORT will automatically place those attributes in columns on the report, in the order you specified (if the report would exceed the page width, FDREPORT s AUTOSTACK option can be used to place related attributes one above the other to save space). You can control the spacing between columns, page length, line width, and other formatting options, if you like. Since the users of the reports generated by FDREPORT should be able to identify their contents and purpose quickly, FDREPORT allows you to put titles and headings on the reports. The TITLE statement places a title line at the top of every page, e.g., TITLE LINE= UNCATALOGED DATA SETS ON TSO VOLUMES FDREPORT automatically generates heading above the data columns on the report, with 1- or 2-line descriptions. If the default names provided by FDREPORT are not meaningful to the report users, the headings can be changed with the HEADING command (but you must line up your headings with the FDREPORT columns). You may want to print column headings in a local language. For example, you can have the heading for Data Set Name appear as Nom Du Fichier for French speaking users.

6 Device-Independent Sizes When allocating data sets, users have traditionally had to be concerned with the characteristics and geometry of the disk type chosen for the data set, e.g., bytes per track and tracks per cylinder, translating the projected size of the data set into a number of tracks or cylinders and learning new rules for each new device type. Under SMS, IBM now allows data sets to be allocated in device-independent units of records, with the system selecting the physical blocksize and calculating the space. In addition to reporting on the traditional data set sizes (e.g., SIZE, SIZEUSED, SIZEFREE in tracks), it can report or select based on sizes in bytes, kilobytes or megabytes (e.g., BYTES, BYTESUSE, BYTESFRE). Since SMS or DASD pooling software may remove the choice of disk type from the users control, these device-independent values may be used to allocate equivalent sized data sets on whatever device they are allocated. For conversion planning (e.g., 3380 to 3390), they can be used to estimate the amount of space required on the new devices for a certain set of data sets. The following control statements will report on all on-line data sets whose hi-level index is PAYROLL, showing allocated tracks, allocation in KB, used space in KB, blocksize and logical record length: 6 TITLE LINE= SPACE ESTIMATE FOR PAYROLL FILES IN KILOBYTES SELECT DSG=PAYROLL. REPORT FIELD=(DSN,VOL,LRECL,BLKSIZE,SIZE,BYTES,BYTESUSE) PRINT ONLINE,SORT=COMBINE Selecting Data Sets Data sets may be selected for inclusion in the report based on most of the data set attributes that FDREPORT can report on. The selection can be: simple, such as all data sets starting with certain indexes on certain volumes: SELECT DSG=GL.APR90,VOLG=PROD complex, such as sequential data sets with 80-byte fixed length records, 20 tracks or more in size with at least 50% unused space: SELECT DSORG=PS,LRECL=80,RECFM=FB,SIZE=20,%FREE=50 sophisticated, such as DB2 files created in the last 30 days, over 30 Megabytes in size, located on 3390 disks: XSELECT XDSN=*.DSNDBC.*.*.I0001.A+++,DEVTYPE=3390,CRDAYS<31,BYTES>30M FDREPORT has two selection control statements, SELECT and XSELECT. They are similar, and accept most of the same selection operands, but XSELECT is much more sophisticated. SELECT only accepts an equal sign (=) after an operand; depending on the operand it may imply a test for EQUAL (e.g., DSORG=PO) or GREATER THAN EQUAL (e.g., SIZE=50). With XSELECT you can specify the comparison to be done (equal, less than, etc.) giving much greater flexibility (e.g., SIZE.GE.50,SIZE.LE.100 will select data sets from 50 to 100 tracks in size). XSELECT also supports the XDSN=operand, which allows data set name masking (as shown in the DB2 example above). Multiple SELECT and/or XSELECT statements may be used in one FDREPORT run so that data sets meeting various criteria can be included on one report. CORPORATE HEADQUARTERS: 275 Paterson Avenue, Little Falls, New Jersey (201) Fax: (201) @compuserve.com EUROPEAN FRANCE GERMANY NETHERLANDS UNITED KINGDOM NORDIC COUNTRIES OFFICES: