On Mon, 23 Feb 2009 19:31:09 -0500, Thompson, Steve wrote: > >Bruce Black probably would have known; we all miss him; >I for some volunteer research he did when I asked another >stupid question years ago. > In fact, some years ago Mr. Black recommended FATAR et. al. to me. He even looked us up in his customer list, and assured me in this forum we were fully licensed and authorized to use FAT* in the manner I needed. Alas, our sysadmins have the (mis)understanding that we are licensed only for product development and testing and denied me access. I didn't challenge it, and continue to use SAS TAPECOPY.
>I don't know if you want to go this far, but if your tape utility is >also going to have some part(s) that are not fully "attached" (that is, >must be linked to your main routines), you could "put" them into the >"system" Label Exit (DFP/DFSMS part of the system?). I know it exists, >but I don't know the name. I know you can use it to handle things for AL >tapes (that's how I stumbled upon its existence about 8 months ago). > Can this be done in a way that's nondisruptive; transparent to users other than me? >During the pass to the exit of the label(s), you could verify that they >match the VOL1 contents. I don't know when or how that exit point is >invoked for trailer labels. > Can this be written in Rexx? IANASP. IANAHLASMP. >Otherwise, you will probably have to satisfy yourself with the DCB label >exit point -- unless you want to do EXCP and BLP :-) . > Currently, I'm using BLP, RECFM=U, and LMGET. That's how I noticed the discrepancy between the VOL1 and HDR1 volsers. Further thought: How about validating SDWs? Continuation bits valid, and continuation allowed only when RECFM=VBS? Etc. (Relentlessly pedantic.) -- gil ---------------------------------------------------------------------- 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
