File IPLIST will contain several sets of information similar to the following. First is a list of all SMF records process, the count of records and their data sizes:
AZS153I TYPE RECORDS VOLUME MB %AGE
AZS154I 002 10 0.000 0.0
AZS154I 003 10 0.000 0.0
AZS154I 004 532 0.123 0.0
AZS154I 014 77,147 34.356 1.7
AZS154I 015 2,809 1.248 0.0
AZS154I 017 237 0.024 0.0
AZS154I 020 6,814 0.667 0.0
AZS154I 022 1,948 0.117 0.0
AZS154I 023 1 0.005 0.0
AZS154I 026 4 0.002 0.0
AZS154I 030 96,964 126.956 6.4
… etc
AZS154I 118 11,060 1.419 0.0
AZS154I 119 434,188 119.690 6.0
AZS154I 128 5,427 2.668 0.1
AZS154I 200 40,834 24.072 1.2
AZS154I 207 85 0.071 0.0
AZS182I TOT 1,818,181 1,969.099 MB READ
Following this is a grid of system ids and record counts like this:
AZS137I SUMMARY OF RECORDS USED BY ACQUIRE FOR EACH SYSTEM ID
ZOS1 ZOS3 JB0 JPNA FIF2
----- ----- ------- ------- -------
0 0 0 0 0 0
7 0 0 0 0 0
30.1 11300 0 6814 0 0
30.2 16023 0 1110 0 0
30.3 12462 0 8557 0 0
30.4 12536 0 8568 0 0
30.5 11320 0 6826 0 0
30.6 1420 0 28 0 0
70.1 24 66 6 3343 33
… etc After this is be a summary of environmental details:
AZS220I LIST OF OPERATING SYSTEM LEVELS FROM TYPE 70S
AZS221I SID OPERATING SYSTEM MACHINE /SER P-MSU/S-MSU GCP AAP IIP IFL CF
AZS222I ZOS1 z/OS V2.1.0 2964-702/BB77 394/ 395 2 0 4 0 0
AZS222I ZOS3 z/OS V2.3.0 2964-702/BB77 394/ 395 2 0 4 0 0
AZS222I JB0 z/OS V2.2.0 2964-796/4EF0 4891/ 9787 96 0 20 12 7
AZS222I JPN7 z/OS V2.1.0 2964-607/214B 777/ 777 7 0 3 12 1
AZS222I YBQ2* z/OS V1.13.0 2098-Z03/C054 221/ 221 3 0 0 0 0
AZS226W XXXX* ARE SYSTEM(S) OLDER THAN MINIMUM LEVEL OF V2.1 This summary shows the SMF IDs, operating system levels, machine types and serial numbers. It also shows the partition (P-MSU) and system (S-MSU) capacity limits. If the partition does not have a defined capacity limit it will be the same the system rating. Here you can see that system JBO is the only one with a defined limit. You can also see the count of processors by type on the machine CP, zAAP, zIIP, IFL and ICF.
Any line in this section that has an * after the system ID (like YBQ2) is too old for this version of Acquire, and would have all data ignored in a COLLECT run. Message AZS226W will also be printed.
After this is a summary of the date and time ranges of all SMF data processed, by system ID. This does not mean there is RMF data in the whole of these date/time ranges, only that some SMF data was detected for each one. For exact details of all the RMF intervals, see the listing in the //SCLIST output.
AZS230I SUMMARY OF DATE/TIME RANGES FOUND
AZS231I SID EARLIEST LATEST
AZS232I ZOS1 21FEB18 10:17:42.62 29AUG18 04:00:02.29
AZS232I ZOS3 18FEB18 10:37:00.00 19FEB18 19:51:01.52
AZS232I JB0 14DEC15 17:00:00.00 14DEC15 19:04:03.40
AZS232I JPN7 26FEB18 02:14:58.02 27APR18 05:11:17.96
AZS232I YBQ2 09SEP13 00:45:00.04 09SEP13 08:45:02.16
Following this, if any CICS systems were detected you will see a list of the CICS APPLID values and the level of CICS they are running. If dictionaries were found, they will have been examined to see if they provide an exact map with the internal default dictionary, and if so, will be marked as suitable for use with the CICSDICT=N parameter. If no dictionary records or transaction records are found, but CICS statistics records are being written, you will see the list of CICS APPLIDs but the dictionary evaluation flags will be meaningless, and the counts of records in the summary will be zeros.
The same kind of information is also printed for data from DB2 subsystems.
AZS210I CICS APPLIDS FOUND
AZS211I SMFID APPLID VERSION TRANSACTIONS
AZS212I ZOS1 CICSCDC x0000 40
AZS212I ZOS3 CICSTS54 TS 5.4 112
AZS212I ZOS3 CICSTS53 TS 5.3 152
AZS212I *TOTAL* 304
AZS213I SMFID DB2 NAME VERSION TRANSACTIONS
AZS214I ZOS1 DBBJ V11.1 3836
AZS214I ZOS1 DBBG V11.1 3836
AZS214I JB0 DBWF V11.1 300
AZS214I JB0 DBS6 V11.1 420
AZS214I JB0 DBW2 V11.1 300
AZS214I JB0 DBT1 V11.1 240
AZS214I JB0 DBS2 V11.1 420
AZS214I *TOTAL* 9352
Next an estimate of the //WORK01 file size needed to run through a COLLECT process is displayed:
AZS227I ESTIMATED SIZE FOR WORK01 FILE
AZS228I RECORDS SIZE:MB SIZE:CYL
AZS230I 2048967 609 711
Finally a summary of the record types of interest to Syncsort™ Capacity Management will be printed:
AZS160I RECORD TYPE COUNT
AZS161I TYPE 0 (IPL) 0
AZS161I TYPE 7 (LOST SMF DATA) 0
AZS161I TYPE 30.1 (JOB SUBMIT) 18114
AZS161I TYPE 30.2 (JOB INTERVAL) 17133
AZS161I TYPE 30.3 (JOB LAST INTERVAL) 21019
AZS161I TYPE 30.4 (JOB STEP END) 21104
AZS161I TYPE 30.5 (JOB END) 18146
AZS161I TYPE 30.6 (SYSTEM JOB) 1448
AZS161I TYPE 70.1 (RMF CPU/LPAR) 3472
AZS161I TYPE 70.2 (RMF CRYPTO) 92
AZS161I TYPE 71 (RMF MEMORY) 67
AZS161I TYPE 72.3 (RMF WORKLOADS) 765002
AZS161I TYPE 73 (RMF CHANNELS) 67
AZS161I TYPE 74.1 (RMF DASD) 1214
AZS161I TYPE 74.4 (RMF CPL. FACILITY) 282
AZS161I TYPE 75 (RMF PAGE DATASETS) 1035
AZS161I TYPE 78 (RMF I/O, HIPERPAV) 138
AZS161I TYPE 89.1 (PRODUCT USAGE) 2270
AZS161I TYPE 90.7 (SYSTEM SHUTDOWN) 0
AZS161I TYPE 100 (DB2 IFCID 1) 2218
AZS161I TYPE 100 (DB2 IFCID 2) 2458
AZS161I TYPE 101 (DB2 ACCOUNTING) 0
AZS161I TYPE 110 (CICS TRANSACTIONS) 38
AZS161I TYPE 110 (CICS DICTIONARIES) 2
AZS161I TMON/CICS TRANSACTIONS 0
AZS161I TYPE 113.1 (CPUMF / HIS) 88
AZS161I TYPE 115.1 (MQ SYSTEM) 8
AZS161I TYPE 115.2 (MQ BUFFERS ETC) 8
AZS161I TYPE 115.215 (MQ BUFFERS) 8
AZS161I TYPE 119.6 (TCP/IP INTERFACE) 24
AZS161I TYPE 120.3 (WAS SYS. INTERVAL) 0
AZS161I TYPE 120.6 (WAS J2EE INTERVAL) 0
AZS161I TYPE 120.8 (WAS BEAN INTERVAL) 0
AZS161I ACQUIRE/DASD 0The SCLIST file (if present, or the IPLIST DD if not) will detail every RMF interval found for every system in the input SMF data, similar to this. A blank line is be printed between intervals that are not contiguous:
INTERVAL START INT LEN INTERVAL END
SMF ID DATE HH:MM MM.SS.THT DATE HH:MM
ZOS1 27AUG18 0:00 30:00.017 27AUG18 0:31
ZOS1 27AUG18 0:30 29:59.979 27AUG18 1:00
ZOS1 27AUG18 1:00 29:59.997 27AUG18 1:30
ZOS1 27AUG18 1:30 30:00.003 27AUG18 2:01
ZOS1 27AUG18 2:00 30:00.000 27AUG18 2:31
ZOS1 27AUG18 2:30 29:59.999 27AUG18 3:00
ZOS1 27AUG18 3:00 29:59.998 27AUG18 3:30
ZOS1 27AUG18 23:30 29:59.985 28AUG18 0:30
ZOS1 28AUG18 0:00 30:00.003 28AUG18 0:31
ZOS1 28AUG18 0:30 30:00.009 28AUG18 1:01
ZOS1 28AUG18 1:00 29:59.994 28AUG18 1:30
ZOS1 28AUG18 1:30 29:59.991 28AUG18 2:00
ZOS1 28AUG18 2:00 30:00.001 28AUG18 2:31
ZOS1 28AUG18 2:30 29:59.999 28AUG18 3:00
ZOS1 28AUG18 3:00 30:00.007 28AUG18 3:31
ZOS3 18FEB18 10:32 30:00.000 18FEB18 11:03
ZOS3 18FEB18 11:02 29:59.999 18FEB18 11:32
ZOS3 18FEB18 11:32 30:00.001 18FEB18 12:03
ZOS3 18FEB18 12:02 29:59.997 18FEB18 12:32
ZOS3 18FEB18 12:32 30:00.001 18FEB18 13:03
ZOS3 18FEB18 13:02 29:59.999 18FEB18 13:32
… etc
Use these listings to confirm that the SMF dataset contains suitable records. With data from z/OS, there should be the same number of TYPE70, TYPE71, TYPE74 and TYPE78 records (one each per SMF ID per RMF interval). There should be many TYPE72 and TYPE75 records and many Type 30 records of various subtypes. Ideally there should be many Type 30 Subtype 2 and 3 (Interval Accounting) records, but these are optional and Syncsort™ Capacity Management can work without them. CICS records (type 110-T and 110-D) are also optional.