Xtract™ Support

Important: for faster turn around on Technical Support, please direct Xtract related questions and problems directly to Xtract support email at: xtsupport@pallas-international.com  fax: (408)923-5509

Known Problems (updated 03/05/2008)

1. The mainframe data extractor Xtract limits the number of digits for values such as average IOSQ time, service time, response time, pending time etc. to three (3) before the decimal point. Since these values are expressed in milliseconds, values of one second or above are truncated. As a result, an average IOSQ time of 1300 ms would be reported by Xtract as 300 ms. This behavior is normally not a problem since values of IOSQ or other components of the response time exceeding 1 second are normally not expected to occur. In rare circumstances, possibly when there is a problem with a device, such values can occur and be misreported by Xtract.
The following ZAP can be applied to Xtract 4.2 through 4.3A to expand the response time and the IOSQ time fields by one digit:


//SYSLIB DD DISP=SHR,DSN=the.extract.load.library
VER 1172 DE06,7461,7259
VER 11B2 DE06,7461,7259
VER 2860 7AB4,7AB6,7AB8,7ABA
VER 2868 7ABC,7ABE,7AC0,7AC2
VER 2870 7AC4,7AC6,7AC8
REP 1172 45A0,7AB4,0700
REP 11B2 45A0,7AB4,0700
REP 2860 92F0,7461,DE06,7461
REP 2869 7259,D200,7461,7258
REP 2870 96F0,7461,07FA //


Note that in some installations, the authority to run the program AMASPZAP is restricted to some users, so an authorized user must submit this Job. Note also that values fetched from Xtract can be edited in Lead Time through the Model Access menu.
2. In Xtract 4.3, abend S0C4 may occur in module XTRACT4 if LCU 0 is specified. The problem is compounded by the fact that Xtgen 1.0 generates JCL with LCU 0 by default if the user does not specify other LCU numbers. Additionally, an incorrect keyword is generated for the ending date of a period. This keyword should be NDDATE (and not NDATE). This can be corrected manually in the JCL before submitting to Xtract.
3. In Xtract 4.2, under certain circumstances, abend S0C4 may occur in module XTRACT3 if more than 2049 devices are defined. Xtract 4.2A corrects the problem. Otherwise, please apply the following ZAP to Xtract 4.2:


file://XTZAP JOB …
file://SYSLIB DD DISP=SHR,DSN=The.library.where.you.link.edited.XTRACT
file://SYSIN DD *
REP 02DA 4C00,B728


4. In some cases, with Xtract version lower than 3.9A, spurious characters are introduced in the informational lines Xtract generates at the top of the .SMF files. These characters, when present in the file, prevent Lead Time from correctly Fetching the monitor file. Xtract release 3.9A available for download as a separate self-extracting archive should fix the problem. For lower Xtract versions, the solution is to remove the offending comment lines from the .SMF file under a text editor such as Edit. The lines to be removed are comment lines (starting with the symbol #) at the top of the file which include “unreadable” characters. Please note that you should only attempt to edit the monitor files if Lead Time cannot correctly read them.

5.  There is a potential problem with Xtract versions lower than 3.8 while handling GTF data. For the problem to occur, a combination of unlikely events must happen:

a.) The user specifies a range of devices.
b.) Some of the devices not only don’t have any GTF data, but they don’t have any RMF records either (those devices were not generated or have been offline since MVS IPL).
c.) As XTRACT doesn’t have any LCU information for those devices, it puts them in LCU zero. Xtract runs and completes normally, but issues warning messages:


• Output data set cannot be opened, and
• GTFnnn data set cannot be opened.This is because XTRACT creates an output data set and a GTF data set for each LCU.


d.) The user adds DD statements for GTFnnn and OUTnnn, and reruns XTRACT.
e.) XTRACT Abends U0005 in module XTRACT5.The temporary solution is to remove the devices that don’t have GTF nor RMF data.