That's what I feared. I could deal with some configuration of the pseudo-volser, but our product doesn't run under TSO, so a "command" interface isn't convenient. I was hoping that somehow these products worked with application code written to the DFHSM macros. ARCHDEL is the most important.
On Thu, Feb 20, 2020 at 11:16 AM Tom Conley <[email protected]> wrote: > On 2/19/2020 2:25 PM, Kirk Wolf wrote: > > I'm asking this from the point of view of an architect who wants to add > > DFHSM-ish integration to a ISV product. > > > > If I were only worried about DFHSM, my requirements for basic integration > > are pretty simple, and would be these: > > > > - VOL=SER=MIGRAT means migrated data set > > - ARCHMIG, ARCHRCAL, ARCHDEL macros could be used for basic interfaces > > > > What about alternative vendor DFHSM products? Can these same interfaces > be > > used in a SAF-esque sort of way? > > > > Thanks in advance, > > > > Kirk Wolf > > Dovetailed Technologies > > http://dovetail.com > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > Kirk, > > You need to know the pseudo-volser that each HSM-like product > (FDR/ABR, CA-Disk, etc.) uses in the catalog to delineate a migrated > dataset (MIGRAT, ARCHIV, and ARCIVE are the ones I've seen). You will > also need to issue the product-specific commands under the covers. > > Regards, > Tom Conley > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
