In a message dated 9/6/2006 8:23:53 A.M. Central Daylight Time, [EMAIL PROTECTED] writes:
>Yes Bill I agree, there is a huge amount of data and additional steps are >needed to get meaningful results from it. >If you needed to get Data Set level access information and had no OEM >software available, how would you proceed? As I said in my previous post, I would have to build my own tool. This would be approximately a six-month development effort to write an Assembler language program to read the GTF data, look for SSCH or I/O interrupt records, scan those records for the CCW that sends the beginning seek address to the controller, obtain that seek address, then pass that seek address plus the device number to another routine that would find the UCB with that device number, get its VOLSER, use that VOLSER to start accessing the VTOC for that device number, and read all the F1 and F3 DSCBs until I found the one containing the given seek address. This assumes that I would be able to find a machine-readable DSECT for the GTF data or, failing that, that I could successfully reverse-engineer the complex data found therein well enough to locate the data elements I mentioned above. I doubt that my management would sign off on this project. Either that or get a large notepad and begin a many-day process of doing the same thing by hand for a very small amount of data. Bill Fairchild ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
