These control statements select the SMF data that you want to be:
These control statements select the SMF data that you want to be:
- Copied and processed by another program
- Printed in its original form
- Or both
If this product detects duplicate or overlapping SMF data, by default it does not allow any records to be extracted or printed from the history file data set causing this condition. To allow duplicate or overlapping SMF data to be extracted or printed, specify the PERMIT parameter on the EXEC JCL statement. To have overlapping data that is automatically discarded during the EXTRACT/PRINT process, specify the NODUPS parameter on the EXEC JCL statement.
When the PERMIT parameter has been coded on the EXEC statement, an overlap condition results in a warning message, and the step completes with a condition code 4.
For further information, see Systems Programming.
EXTRACT and PRINT take the same operands except the EXIT and TODD parameters, which pertain only to EXTRACT. You can include more than one EXTRACT or PRINT control statement in the same execution of CA SMF Director.
By default, EXTRACT and PRINT requests are satisfied from the primary pool of history files. You can use the SOURCE control statement to specify the Alternate pool.
Only those SMF records having a standard header section as defined in the IBM
z/OS Systems Management Facilities Manualare selected for processing.
Special Characteristics of the EXTRACT Control Statements
CA SMF Director honors user-defined record formats and truncates or pads records, as required. During extraction, a message is issued indicating the number of records that are truncated if the logical record length (LRECL) is not large enough to accommodate the largest record encountered. If the DD statement for the output file does not specify a block size, record length, or record format, CA SMF Director uses default values of LRECL=32760 and RECFM=VBS.
In addition, the EXTRACT statement can also create entries in a split file index to facilitate the automated application processing of SMF data. This data would typically have been saved to a split file during the dump process. See the SPLIT control statement for more information about split files and the index.
Special Characteristics of the PRINT Control Statements
Data is printed in standard dump format (character and hex), with a formatted heading of the information in the standard SMF record header. The record descriptor word (RDW) of the SMF record is not printed.
►►─┬─ EXTRACT ─┬─┬────────────────────────┬─────────────────────────────────────► └─ PRINT ───┘ ├─ SID(sid1 ... sidn) ───┤ ├─ XSID(sid1 ... sidn) ──┤ ├─ EXCLUDESID(sid1 ...) ─┤ └─ ALL ──────────────────┘ ►─┬──────────────────────────────────────────────┬─┬─────────────────┬─┬──────────────────────────────────┬──► ├─ FROM(date time)TO(date time) ───┤ └─ COUNT(nnnnnn) ─┘ └─ PROGRESSMSGS( ─┬─ NO ◄ ─┬─ )────┘ ├─ JFROM(date time)JTO(date time) ─┤ ├─YES────┤ ├─ FROMDAYSAGO(days time)TODAYSAGO(days time) ─┤ └─WTO────┘ ├─ SDAY(hhmm) ─────────────────────────────────┤ ├─ YEAR(yyyy) ─────────────────────────────────┤ ├─ MONTH(mmyy) ────────────────────────────────┤ ├─ WEEK(date) ─────────────────────────────────┤ ├─ DAY(date) ──────────────────────────────────┤ ├─ YESTERDAY ──────────────────────────────────┤ ├─ LWEEK/LASTWEEK──────────────────────────────┤ ├─ LMONTH/LASTMONTH────────────────────────────┤ ├─ TODAY ──────────────────────────────────────┤ └─ SCRT(nn)────────────────────────────────────┘ ►─┬────────────────────────────────────────────────────┬──────────────────────► └─ WHEN( ─┬─ component,test,value,test,value. ─┬─ ) ─┘ └─ aa,bb,cc. ────────────────────────┘ ►─┬─────────────────┬────────┬────────────────────────┬───────────────────────► ├─ SELECT(list) ──┤ ├─SIGNATURES(─┬─NO◄─┬ )┤ └─ EXCLUDE(list) ─┘ └─ YES ─┘ ►─┬─────────────────────────────────────┬────────────────────────────────────► └─ TAPEVOLCHG( ─┬─ NORELEASE ◄ ─┬─ ) ─┘ └─ RELEASE ─────┘ ►─┬───────────────────────────────────────────────────────────────┬──────────► └─ INDEXDSN(dsname) ─┬────────────────────┬─┬─────────────────┬─┘ └─ INDEXDUP(ddname) ─┘ └─ INDEXLIM(nnn) ─┘ └─ INDEXDAYS(nnn)─┘ ►─ EXIT(module) ─ TODD(ddname) ──────────────────────────────────────────────► ►─┬───────────────────────────────────────┬──────────────────────────────────► ├─ LSNAME( ─┬─ lsname lsname ... ─┬─ ) ─┤ │ └─ NONE ──────────────┘ │ └─ SUBNAME( ─┬ subname subname ... ─┬ ) ┘ └ NONE ────────────────┘ ►─┬────────────────────────────┬─┬─────────────────────────────┬─ ─────────►◄ └─ MANFILE( ─┬─ YES ◄ ─┬─ ) ─┘ └─ EXPAND110( ─┬─ NO ◄ ─┬─ ) ─┘ └─ EXPANDDB2( ─┬─ NO ◄ ─┬─ ) ─┘ └─ NO ────┘ └─ YES ──┘ └─ YES ──┘
Operands and Descriptions:
Specifies the identification of one or more (operating) systems for which data is extracted.
"(sid)" can identify up to 20 systems. You can code this part of the statement as follows: SID(sid1,sid2...). Either SID or ALL operand must be specified.
Causes data to be extracted for all the indexed systems, for which CA SMF Director has an entry, that falls within the specified time range. Either SID or ALL operand must be specified.
EXCLUDESID(sid1, sid2, …)
XSID(sid1, sid2, …)
The EXCLUDESID and XSID operands provide a way to indicate which systems the control statement does not apply to. One or more systems can be specified. Any configurations in the SCDS that have any of the named SIDs are not processed with the command. All other configured systems will be processed.
The EXCLUDESID and XSID operands are mutually exclusive synonyms of each other. These operands are also mutually exclusive with the SID operand and the ALL operand.
FROM (date time)
TO (date time)
Specifies the beginning and ending of the period for which SMF data is extracted. The SMF records whose timestamps exactly match the FROM specification are considered to be inside the time range. The SMF records whose timestamps exactly match the TO specification are considered to be outside the time range.
Date is in Gregorian (mmddyy) format. For example, July 1, 2008 would be 070108.
Time is coded in hour/minute (hhmm) format. For EXTRACT, time can be coded in hour/minute/second (hhmmss) format. The time portion of the operand values is optional. For the FROM operand, the default time value is 000000 and for the TO operand, the default time value is 240000.
Specifies the beginning date and time for the SMF records to be extracted or printed.
Date is in Julian date format (cyyddd)
C is 0 for 1960 through 1999 and 1 for 2000 and thereafter. For example, 098182 represents July 1, 1998, and 101001 represents January 1, 2001.
Time is optionally coded in hours, minutes, and seconds format (hhmmss or hhmm). Code either the JFROM keyword or the FROM keyword, but not both. The default value for the time if omitted is 000000.
Specifies the ending date and time for the SMF records to be extracted or printed.
Date is in the Julian format (cyyddd).
Time is optionally coded in hours, minutes, and seconds format (hhmmss or hhmm). Code either the JTO keyword or the TO keyword, but not both. The default value for the time if omitted is 240000.
The installation's logical day specification is ignored when an EXTRACT statement includes these parameters. At least one FROM, TO, JFROM, or a JTO parameter with a starting or an ending time that is explicitly coded. The logical day specification is the SDAY value that is defined on the OPTIONS statement. If only a starting time is coded, the ending time defaults to midnight at the end of the TO/JTO date. If only an ending time is coded, the starting time defaults to midnight at the beginning of the FROM/JFROM date.
- The SMF records whose timestamps exactly match the JFROM specification are considered to be inside the time range.
- The SMF records whose timestamps exactly match the JTO specification are considered to be outside the time range.
Specifies that SMF data is extracted or printed from the date range indicated by the number of days past.
Specifies the number of days to count back from the current day. The value can be any number of days from zero (meaning the current day) to 366.
Specifies an optional time value in HHMMSS format. The default is 000000 for FROMDAYSAGO and 240000 for TODAYSAGO.
Specifies an override TIME value for logical time ranges that override the configured SDAY value for the SMF data archive or configuration.
Specifies that the SMF data for an entire calendar year is processed. If "yy" is 59 or less, the year is treated as 20yy. If "yy" is 60 or greater, the year is treated as 19yy.
For example, YEAR(2000) requests an extraction of data beginning January 1 and ending December 31, 2000.
Specifies that the SMF data for an entire calendar month is processed. For example, "(0408)" specifies April 2008.
Specifies that the SMF data for an entire calendar week (168 continuous hours) beginning with the specified date, is processed.
"Date" is in Gregorian (mmddyy) format.
Specifies that the SMF data for one calendar day is processed.
"date" is in Gregorian (mmddyy) format.
Specifies processing of SMF data for yesterday's calendar day. "Yesterday" is the current logical date minus one, at the time the extract is run.
Specifies that SMF data is extracted or printed for the last calendar week, running Sunday through Saturday.
Specifies that SMF data is extracted or printed for the last calendar month. For example, if an EXTRACT LMONTH is run on July 2008, CA SMF Director extracts all data from June 2008.
Specifies that SMF data is extracted or printed for the last calendar year. .
Specifies that SMF data is extracted or printed for the current logical day.
The installation's system-wide SDAY option is used to determine the current day, week, or month is for processing the YESTERDAY, LWEEK, LMONTH, or TODAY parameters.
The installation's SDAY option is set to 0900 and an EXTRACT is run at 0800 on Sunday, July 1, 2008.
The result for the LMONTH operand is the extraction of all data between 0900 on May 1, 2008 and 0900 on June 1, 2008.
The result for the LWEEK operand is the extraction of all data between 0900 on Sunday, June 17 and 0900 on Sunday, June 24.
The result for the YESTERDAY operand is all data between 0900 on June 29 and 0900 on June 30 to be extracted.
The result for the TODAY operand is all data between 0900 on June 30 and 0900 on July 1 to be extracted.
These results are due to the logical date is Saturday, June 30. Running EXTRACT an hour later would change the results of all three of these operands. Because the logical date would become July 1 at 0900 on that date. Thus, the LMONTH, LWEEK, YESTERDAY, and TODAY operands would extract or print the data between:
- 0900 on June 1 and 0900 on July 1
- 0900 on Sunday, June 24 and 0900 on Sunday, July 1
- 0900 on June 30 and 0900 on July 1.
0900 on July 1 and 0900 on July 2.
For the SMF records whose timestamps exactly match the beginning of the specified interval are selected. For the SMF records whose timestamps exactly match the end of the specified interval are not selected.
SCRT(previous relative month)
Specifies that SMF data is extracted or printed for the SCRT reporting period relative to the date of execution, and adjusted by the previous month value. With a previous relative month specified as (1), the SCRT reporting period begins on the second day of the previous month and ends on the first day of the current month if the current day of the month is not the first. However, If the current day of month is the first, then the SCRT reporting period begins on the second day of the month 2 months ago, and ends on the first day of the previous month. The SCRT previous relative month value must be an integer value from 0 through 99 if specified.
Specifies whether signature records should be selected for processing in the output. The default value is NO. If signature records are required code SIGNATURES(YES). If only signature records are to be extracted, code SIGNATURES(NO) and SELECT(2) as operands on the EXTRACT or PRINT statement.
Specifies the maximum number of records to be extracted.
"(n)" must be a positive integer.
WHEN(aa,bb,cc,aa,bb,cc,…) or WHEN(component,test,value,test,value...)
Allows the specification of more selection criteria for the SMF records. The WHEN selection criteria can be based on either up to four offsets or up to five components, but not both.
A full description of component-based WHEN selection criteria can be found under the description of SPLIT statement. The rules for coding component-based WHEN criteria are identical for EXTRACT and SPLIT statements.
The offset-based WHEN selection criteria are described as follows.
Up to four “bb,cc” combinations can be coded following the offset that is described by “aa”. For an SMF record to be selected, it must meet ALL of the specified conditions. Only one WHEN operand specifying an offset can be coded.
If the WHEN condition check goes past the end of an SMF record, the record is not written to the output SMF file.
'aa' is the numeric offset within the SMF record relative to zero (column 1) that is to be checked. The offset can be any number up to 32767.
If you are looking at a listing from an IDCAMS dump or SMF display from an earlier PRINT command, remember that neither of these methods display the record descriptor word (RDW). Therefore, the WHEN offset must be coded as 4 greater than the apparent displacement of the field as shown in an IDCAMS dump or a CA SMF Director PRINT command listing.
'bb' is any one of the following two-character operators:
Less than or equal to
Greater than or equal to
'cc' is the character or hexadecimal constant up to 32 bytes in length. This parameter can be coded as a hexadecimal value in the format X'zz', where 'zz' is an even number of hexadecimal digits. For example:
EXTRACT ALL MONTH(0408)SELECT(14,15)WHEN(68,EQ,'SYS1')
Results in the extraction of all SMF record type 14 and 15 records that are generated during April 2008 for data sets whose names begin with SYS1.
This parameter cannot use wildcards. If this parameter contains any asterisks, the asterisks are interpreted literally.
Specifies selection of only certain record types for processing, or exclusion of certain record types for processing. If neither of these two operands are coded, this product processes all stored SMF records that fall within the specified date and time range.
'list' can include any valid SMF record types and subtypes. Where a subtype is specified, a decimal point separates the type from the subtype; for example, 30.1 signifies SMF record type 30, subtype 1. The valid numbers for SMF record types are 0 through 2047. The valid numbers for subtypes are 0 through 65535.
The type/subtype specifications can be expressed as individual record types/subtypes separated by commas or as a range separated by a colon, or both.
SELECT(30.1:30.5) results in the retrieval of SMF record type 30, subtypes 1 through 5.
EXCLUDE(99.20,99.100) causes the retrieval of all stored SMF records except for type 99, subtypes 20 and 100.
Some SMF records have subtypes of zero. To specify subtype zero, code a zero to the right of the decimal point. For example, SELECT(116) requests all type 116 records; SELECT(116.0) requests only type 116, subtype zero.
Specifies whether CA SMF Director can release the history file tape unit when it is about to call for the mount of a new history volume. The default is NORELEASE.
TAPEVOLCHG does not apply to history files that reside on DASD.
(For EXTRACT only.) Specifies the name of a split file index, where information about this extract is recorded. INDEXDSN is an optional parameter that is provided to facilitate processes that use the split file index to process data that CA SMF Director archived. The parameter can contain the data set name of the split file index that is used in the automated process. For more information about split file indexes, see the description of the SPLIT control statement. For more information about setting up a split file index, see Systems Programming
A single, specific SID must be coded when using INDEXDSN. ALL is not supported.
(For EXTRACT only.) Specifies the ddname in the extract JCL where a copy of the split file index is written. This operand is valid only if the INDEXDSN operand is present; otherwise it is ignored.
(For EXTRACT only.) Specifies the maximum number of entries that are kept in the split file index. This operand is valid only if the INDEXDSN operand is present; otherwise it is ignored.
(For EXTRACT only.)
This optional operand can only be coded if INDEXDSN is coded. This operand indicates the maximum number of complete days that entries are kept in the split file index that is indicated by INDEXDSN. If the creation date of an index record is less than the yesterday’s date minus the INDEXDAYS value, the record is dropped from the index.
If INDEXDAYS(1) is coded, then all index records with a creation date of today and yesterday are retained and all older records are discarded. This operand and the INDEXLIM operand are mutually exclusive. If both INDEXDAYS and INDEXLIM are omitted, the index file has no limit on the number of records. The index records are not large; an index file of one 3390 cylinder holds 4,350 index records at half-track blocking.
Even when entries are deleted from the Index, the associated data sets in the entries are not deleted.
(For EXTRACT only.) Specifies the module to be called as an exit to receive extracted SMF data for further processing. TODD must also be coded if this product is to write the extracted output file. If TODD is not coded, it assumes that the exit module processed the extracted data as desired.
"(module)" is the 1-character to 8-character name of a module to be dynamically loaded during the processing of this request. For more information, see Writing EXTRACT Exits in Extraction, Split User Exits, and Split File Time Processing.
(For EXTRACT only.) Specifies the name of the DD statement defining the file to which the extracted SMF records are to be written.
"(ddname)" must be a 1-character to 8-character ddname, corresponding to a DD statement in the execution JCL for the job.
More than one EXTRACT request can be coded for the same DD. If the TODD parameter is omitted, This product uses a default ddname of EXTRACT.
The default file attributes for an EXTRACT file are described Selective Processing of SMF Data.
Requests that CA SMF Director issue informational message CAF3107I whenever a history file is about to be opened during an EXTRACT.
(Default) Does not write the messages to SYSPRINT.
Writes the messages to SYSPRINT.
Writes the messages to both SYSPRINT and the operator console.
When there are multiple EXTRACT statements in one run, specification of PROGRESSMSGS(YES) in one EXTRACT statement causes progress messages to be issued for all EXTRACT statements that are processed in the run. Likewise, specification of PROGRESSMSGS(WTO) in one EXTRACT statement causes progress messages to be written to the operator console for all EXTRACT statements that are processed in the run.
LSNAME(NONE|lsname lsname ...)
Specifies a subset of logstream names that CA SMF Director includes in the search to satisfy an EXTRACT or PRINT request. If this operand is not included, all of the logstreams being managed are included in the requests. LSNAME(NONE) means that none of the logstreams are included when searching for records to satisfy a request.
SUBNAME(NONE|subname subname ...)
Specifies a subset of substream names that CA SMF Director includes in the search to satisfy an EXTRACT or PRINT request. If this operand is not included, all of the substreams being managed are included in the requests. SUBNAME(NONE) means that none of the substreams are included when searching for records to satisfy a request.
Specifies whether the MAN file archives are searched to find records to satisfy an EXTRACT or PRINT request.
(Default) YES includes the MAN files in the search.
NO limits the request to search only the logstreams and substreams.
Indicates whether a compressed SMF type 110 records can be expanded before they are either written to the extract file or printed.
For YES, CA SMF Director expands any compressed type 110 records that are to be written to the output file or printed.
(Default) NO means that no expansion of type 110 records are performed.
Indicates whether compressed SMF types 100 through 102 records should be expanded before they are either written to the extract file or printed.
For YES CA SMF Director expands any compressed types 100 through 102 records that are to be written to the output file or printed.
(Default) NO means that no expansion of types 100 through 102 records are performed.
Sample EXTRACT Statements:
Obtain the SMF records from systems XE21, XAE1, and XAE4 from December 16, 2008 at 8:00 a.m. to December 16, 2008 at 5:30 p.m. Exclude SMF record types: 14,15,70,71,72,73,74,75,76,77,78,79:
EXTRACT SID(XE21,XAE1,XAE4) FROM(121608 080000) TO(121608 173000) EXCLUDE(14:15,70:79).
Obtain the RMF records from all systems for the first quarter of the year 2008, January 1 2008 to March 31 2008:
EXTRACT SID(ALL) JFROM(108001 000000) JTO(108091 240000) SELECT(70:79).
Obtain all SMF records for system XE96 and XE74 from April 16, 2008 at 4:00 p.m. to September 27, 2008 at 12:30 p.m. Place all records in the data set referenced in the JCL by ddname SMFOUT:
EXTRACT SID(XE96,XE74) JFROM(108107 1600) JTO(108271 1230) TODD(SMFOUT).
Obtain the RMF records from 10 a.m. to 4 p.m. on January 17, 2008, but only include data from logstreams IFASMF.LSTRM1 and IFASMF.LSTRM2 and only from system XFF1:
EXTRACT SID(XFF1) FROM(011708 100000) TO(011708 160000) SELECT(70:79) MANFILE(NO) TODD(SMFOUT) LSNAME(IFASMF.LSTRM1 IFASMF.LSTRM2).
Extract any records from the last month on system XFF1 that were not captured in a logstream:
EXTRACT SID(XFF1) LMONTH TODD(SMFOUT) LSNAME(NONE).
The EXTRACT statement output:
CA HERNDON AUDIT TRAIL REPORT SMFD PAGE 1 CA SMF Director 12.7 SYSA 20 SEP yyyy 8:50:57 EXTRACT SID(XE96,XE74) JFROM(107100 1600) JTO(107270 1230) TODD(SMFOUT). CAF1010I REQUEST ACCEPTED CAF2218I SMF DATA USING CONFIGURATION XE96 IS BEING PROCESSED CAF2221I SMF DATA USING CONFIGURATION XE96 IS BEING PROCESSED WITH LOGSTREAM IFASMF.ALL CAF2221I SMF DATA USING CONFIGURATION XE96 IS BEING PROCESSED WITH LOGSTREAM IFASMF.RMF CAF2221I SMF DATA USING CONFIGURATION XE96 IS BEING PROCESSED WITH LOGSTREAM IFASMF.T30 CAF2218I SMF DATA USING CONFIGURATION XE74 IS BEING PROCESSED CAF2221I SMF DATA USING CONFIGURATION XE74 IS BEING PROCESSED WITH LOGSTREAM IFASMF.SMFDATA CAF2221I SMF DATA USING CONFIGURATION XE74 IS BEING PROCESSED WITH LOGSTREAM IFASMF.WHISTLE CAF3100I 15669 RECORDS WRITTEN TO SMFOUT FILE CAF3105I 6954 RECORDS PROCESSED FROM: 08/01/2008 9:33:37 TO: 09/19/2008 10:13:33 FOR SYSID XE96 CAF3105I 8715 RECORDS PROCESSED FROM: 07/23/2008 10:52:36 TO: 07/24/2008 11:14:03 FOR SYSID XE74 SUMMARY OF RECORDS EXTRACTED FROM: 07/23/2008 (107.204) 10:52:36.56 TO: 09/19/2008 (107.262) 10:13:33.83 TYPE AVGL MAXL TOTAL ................................ SUBTYPE COUNTS ................................ 0 60 60 1 4 238 319 71 5 148 154 33 8 624 624 1 14 359 632 356 15 333 344 134 17 100 100 20 19 72 72 1,425 20 95 101 35 22 302 302 1 23 134 134 24 26 443 451 52 30 1062 3773 2,418 1 - 104 2 - 1,485 3 - 128 4 - 127 5 - 64 6 - 510 32 399 548 14 1 - 4 2 - 3 3 - 4 4 - 3 34 700 703 3 35 154 154 3 40 219 546 84 41 136 212 104 1 - 2 3 - 102 42 472 20972 771 5 - 51 6 - 720 43 32 32 1 50 164 242 50 52 62 62 10 60 516 600 104 61 615 3648 11 62 188 188 92 64 458 458 88 65 316 381 12 80 256 256 1,851 88 222 308 109 1 - 55 11 - 54 89 2363 4478 100 1 - 50 2 - 50 90 326 596 32 92 213 276 1,245 1 - 9 10 - 26 11 - 1,210 99 907 2996 3,323 1 - 373 2 - 1,848 3 - 370 6 - 372 9 - 360 119 236 644 63 5 - 2 6 - 2 7 - 1 10 - 58 231 292 292 3 255 760 760 3,025 2 - 3,025 ALL 624 20972 15,669 CAF2900I RUN COMPLETE
The following list gives an explanation of the fields that are contained in the Summary of Records Extracted section of the report.
SMF record type (numeric value 0-2047).
Average record length of records for this type.
Maximum record length of records for this type.
Number of records for this type that is successfully written to output.
A list of SMF record subtypes and how many records for each subtype were successfully written. The first number that is shown is the numeric SMF record subtype, followed by the number of records. Counts for records with no subtype (zero) are not shown on the report. However, they are included in the total number of records.
Indicates the grand total line for all SMF record types written.
The sample PRINT Statement:
PRINT SID(XE44) FROM(041698 131500) TO(041698 132000) COUNT(5).
The PRINT statement output:
CA AUDIT TRAIL REPORT SMFD PAGE 1 CA SMF Director 12.7 SYSA 27 JUL yyyy 11:45:24 SOURCE PRIMARY. CAF2800I SOURCE OPTION SET PRINT SID(XE44) FROM(041698 131500) TO(041698 132000) COUNT(5) . CAF1010I REQUEST ACCEPTED CAF3200I SMF RECORD TYPE 21 BUFFER DATE 04/16/2008 ( 98/106) TIME 13:16:44 0000 1E150048 F1980098 106FE7C5 F4F40036 F3F0F5F0 F9F00752 78048081 00000033 *....1.....XE44..305090..........* 0020 00000000 00000000 00000000 00000000 00000000 00000100 00000000 00000000 *................................* 0040 00000000 *.... * CAF3200I SMF RECORD TYPE 21 BUFFER DATE 04/16/2008 ( 98/106) TIME 13:16:56 0000 1E150048 F6700098 106FE7C5 F4F40036 F3F0F3F3 F0F2074D 78048081 00000049 *....6.....XE44..303302..........* 0020 00000000 00000000 00000000 00000000 00000000 00037800 00000000 00000000 *................................* 0040 00000000 *.... * CAF3100I 2 RECORDS WRITTEN TO SYSPRINT FILE CAF2900I RUN COMPLETE