--------------------------------------<snip>---------------------------------
Very occasionally.
In around 2007, I had an archive-to-CD prototype running. You gave it a
list of MVS datasets and it would offload them to a PC (after converting
to AWS format). The PC burned a pair of CDs and compared them to make
sure the CDs were readable and that they agreed. Then the PC submitted a
job back to the MVS system containing the offloaded data; the job
executed a test restore and compared the result with the original
dataset. Only then was the programmer notified that the offload was
complete and the archive was verified as valid and restorable.
It was written in a combination of REXX on the MVS side and bash script
on the PC side. Never got past the proof-of-concept stage, 'cause after
it worked my attention was directed elsewhere. I should probably
resurrect it one day.
Back on topic, I used IEBCOMPR to do the dataset verify. If all you want
to do is compare entire datasets then IEBCOMPR works rather well.
-----------------------------------<unsnip>--------------------------------
Dave, did you check this out with load module datasets? LMOD quite often
have imbedded TTR data.
Rick
----------------------------------------------------------------------
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