Xtract™ Release Features

Supported in version 4.3E (May 24, 2008)

  1. This beta version of Xtract was redesigned to avoid overflow problems occurring under certain conditions in preceding Xtract versions. It does not introduce new functionality. If you experience problems running this version of Xtract, you can get the previous version of Xtract from the Download previous version link for Lead Time.
  2. Version 4.3D is normally shipped with Lead Time.
  3. Xtgen had been updated to include controllers supported in latest Lead Time release.

Supported in version 4.3D (Oct 30, 2003)

  1. Xtract has now a Windows-based front end called Xtgen. It allows you to simply specify the controller (or controllers) you wish to treat, as well as specific LCUs and devices to be included in the data extraction. Xtgen supports most commonly used extraction scenarios, and generates a file with the necessary JCL to run Xtract. Xtgen frees you from having to learn the Xtract command language unless you are using GTF traces, working at dataset level, or using data sources other than RMF (and compatible) or IXFP.
  2. Xtract now processes information specific to Parallel Access Volumes.
  3. Controller types supported by Xtgen have been updated to conform with those in Lead Time.

Supported in version 4.3C (Mar 21, 2003)

  1. Xtract has now a Windows-based front end called Xtgen. It allows you to simply specify the controller (or controllers) you wish to treat, as well as specific LCUs and devices to be included in the data extraction. Xtgen supports most commonly used extraction scenarios, and generates a file with the necessary JCL to run Xtract. Xtgen frees you from having to learn the Xtract command language unless you are using GTF traces, working at dataset level, or using data sources other than RMF (and compatible) or IXFP.
  2. Controller types supported by Xtgen have been updated to conform with those in Lead Time.
  3. Known bugs have been corrected, in particular, problem occuring with large numbers of data sets open on a volume have been addressed.

Supported in version 4.3B (Jun. 14, 2002)

  1. Xtract has now a Windows-based front end called Xtgen. It allows you to simply specify the controller (or controllers) you wish to treat, as well as specific LCUs and devices to be included in the data extraction. Xtgen supports most commonly used extraction scenarios, and generates a file with the necessary JCL to run Xtract. Xtgen frees you from having to learn the Xtract command language unless you are using GTF traces, working at dataset level, or using data sources other than RMF (and compatible) or IXFP.
  2. Controller types supported by Xtgen have been updated to conform with those in Lead Time.
  3. Known bugs have been corrected, in particular, problem occuring with large numbers of data sets open on a volume have been addressed.

Supported in version 4.3A (Sep. 20, 2001)

  1. Xtract has now a Windows-based front end called Xtgen. It allows you to simply specify the controller (or controllers) you wish to treat, as well as specific LCUs and devices to be included in the data extraction. Xtgen supports most commonly used extraction scenarios, and generates a file with the necessary JCL to run Xtract. Xtgen frees you from having to learn the Xtract command language unless you are using GTF traces, working at dataset level, or using data sources other than RMF (and compatible) or IXFP.
  2. Xtract supports the Storage Technology V960 controller. If you are writing your own JCL and using the CNTRL statement, the corresponding keyword is STKV960.
  3. The bug causing OC4 under certain circumstances has been corrected.

Supported in version 4.2A

  1. Xtract now supports the extraction of multiple control units in a single run. Four new keywords have been added:CNTRL, TYPE, CLCUS and ID. For example:CNTRL TYPE=STKECLIPSE,CLCUS=(27,28,29,2A),ID=STK1The TYPE keyword allows you to specify one of many controller types supported by Lead Time, CLCUS associates LCUs with the given controller, and the optional ID field helps to manage your file names.
  2. Xtract supports SMF records created by the IXFP utility from Storage Technology. Specifying PROCESS=IXFP allows you to process these records alongside with RMF records normally processed by Xtract.
  3. The bug causing abend OC4 in Xtract 4.2 under certain circumstances when more than 2049 devices were specified had been corrected.

Supported in version 4.0

  1. The maximum number of devices and groups has been increased from 2048 to 9999. The default number of devices and groups is set to 2048.The maximum number of devices and groups is now specified in the JCL PARM field. For example:
    //STEP1 EXEC PGM=XTRACT,PARM=4096will allow for a maximum of 4096 devices and groups. If a JCL PARM field is not specified, the default of 2048 applies. In memory constrained environments, it is possible to decrease the default, also by using the JCL PARM field. For example: //STEP1 EXEC PGM=XTRACT,PARM=256

Supported in version 3.9

  1. Xtract now supports ASTEX 2.1 and 2.5 SMF records.
  2. The maximum number of devices and groups has been increased from 256 to 2048. The default number of data sets has also been increased to 2048. Note, that the latest release of Lead Time supports up to 4096 device groups (this translates to 4096 logical volumes for array control units), and up to 10,000 explicitly defined datasets.

Supported in version 3.8

  1. Xtract now supports RMF type 74 subtype 5 (replacing cache RMF reporter records). Xtract will automatically process 74-5 records if PROCESS=RMF is specified explicitly or by default. If other processing types are specified (DASDMON, ASTEX, GTF, CARMF, or CSIM), 74-5 records are ignored.
  2. In the case a group contains a single device (current Xtract default), the device numberis included in the .SMF file produced by Xtract. This allows Lead Time to order logical volume displays based on RMF device numbers.
  3. The bug existing in versions 3.6 and earlier when an empty LCU was present in a GTF run has been corrected.

Supported in version 3.6

  1. ASTEX 2.0 SMF record format is now supported.
  2. This version of Xtract supports merging of multiple GTF traces. Please refer to your Xtract User’s Guide for information on how to use this feature.
  3. The GPRATE keyword can be used to specify a threshold (in I/Os per second) such that devices whose I/O rate is higher or equal to this value are each assigned their own group (i.e.; they are alone in this group). All devices whose observed I/O rate was below this threshold value, are then placed in a single “catch all” group. The syntax is illustrated by the following example:GPRATE = 5specifies that each device with an I/O rate not below 5 I/O per second will be assigned its own group, all other devices will be grouped together in a single group. Clearly, the GPRATE specification should not be used together with another grouping specification (such as GROUPS = x).
  4. The NOMATCH keyword can be used to specify allowable mismatch between GTF and RMF data before Xtract issues a warning message. The syntax is illustrated by the following example:NOMATCH = 25specifies an allowable mismatch of 25% before warnings are issued. NOMATCH = 10 is the implied default.