|
I have been considering whether a home-grown utility I have that saves and restores spool files can be used to assist in supporting our Y2K testing for documentation purposes. The utility uses the spool file API's to save spool files into a series of user spaces stored in a library. A file is also generated in the same library that contains some key data that identifies the user spaces and holds the spool file attribute data. If we were to save reports generated as part of the Y2K testing using this utility, the possible problems I see are that: 1. The user spaces, library and file will all have creation dates in the "future" if restored to a system in the "present" 2. The spool file attributes will contain a spool file creation date in the "future" 3. Spool files may contain job numbers that will be in use during the restore Since using the API's to restore a spool file seems to ignore the creation date (i.e. the original creation date is not restored when doing the spool file create) and the job information also seems to be ignored, I feel I am pretty safe, but I thought I;d ask the question. Anyone got any thoughts on any possible implications ? Cheers, Evan Harris +--- | 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-2025 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.