|
Gottcha ! Thanks Rob (people know what database normalization is now days ? <BG>) Chuck Rob Berendt wrote: > Because the expiration date of the tape is 'header' information. And it was >probably determined that the information wanted in the output file would be >'detail' information. People tend to strive for database normalization while >printouts tend to be more readable. > > CLEWIS@IQUEST.NET on 10/06/98 09:06:53 AM > Please respond to MIDRANGE-L@midrange.com@Internet > To: MIDRANGE-L@midrange.com@Internet > cc: > Subject: "Cataloging" Tapes - something "weird" (???) > > Hi Folks ! > > I have a routine that runs RIGHT after our daily backups that works > something like this - we have a file that contains ALL libraries on the > system. A program does a DSPOBJD for all libraries in QSYS to a file and > produces a COMPLETE library listing with Save "status's". It then does a > compare of libraries in the QSYS file to the ones in our "library file" > and prints a listing of any discrepancies. Finally, produces a listing > of what we consider "daily save" libraries. What this does is provide us > with several "key" reports on a daily basis for D/R. There a formatted a > little better than a DSPTAP listing... > > What's up: > > I would like to get the tape's Expiration Date. I know how to list it to > a spool file and then CPYSPLF to a date base file and "extract" this > info, but that takes a while to get all of that setup. I thought it > would be NICE to use the *OUTFILE option on the DSPTAP command so I did > this using *LABELS. USUALLY an *OUTFILE contains whatever is shown via a > DSPxxx command to screen. NOT this one. Among the stuff missing are the > Expiration Date and Date Created ! I thought maybe it would show using > DSPTAP with *SAVRST - but THIS isn't allowed to *OUTFILE !!! > > My question(s): > > 1) Doesn't it seem "strange" that Exp Date and Create Date, etc. would > NOT be included in a DSPTAP *LABELS *OUTFILE ?? > > 2) WHY wouldn't DSPTAP *LABELS *OUTFILE be allowed ? > > Thanks ! > > Chuck > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.