The place that process our (not his) microfiche (later CD-ROMS) wanted the same DSN name so they only had to type in the volser, and they would pick up the date and time from the data. So HLQ.Jobname8.Dyymmdd.Thhmm.FIXED.LAST.NAME17 they would see as the same.
On Mon, Sep 21, 2020 at 5:43 PM Paul Gilmartin <[email protected]> wrote: > > On Sun, 20 Sep 2020 00:06:01 -0500, Brian Westerman wrote: > > >They are mifrofiche tapes, and they are not sent out for processing any > >more. They exist only on the off chance that "someday" they might be needed > >to recreate something. When they are needed, they use the DSN=,VOL= to use > >them. > > > I read your more recent ply, but I'm curious about the history. > > "Sent out" seems to imply they're physical tapes to go in a courier pouch. > I had imagined virtual. And RETPD must be comfortably beyond the > "someday they might be needed." > > Does/did the process depend on the DSN's being precisely > hlq.FICHE.TAPE, perhaps to trigger an exit or operator > action? > > I don't see that cataloguing unique DSNs would help much -- it leaves > the chore of associating DSN rather than VOL=SER with a particular > job to be retrieved. It would enable a DSLIST of all such tapes. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
