|
If the save does continue, will it overwrite the existing files (I hope) or put them at the end? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 04/14/2004 12:24 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx> cc Subject RE: CPA4036 - File expiration dates out of sequence (C I R). Do the expiration dates for all parts of the save match? An Ignore on this should allow the save to continue, but if the expiration dates do not all match it is possible to initialize the tape before all files on it are expired. We have a test system that does five daily SAVCHGOBJ's to one tape and had the same problem. I now set the expiration date in a DTAARA on Monday and then retrieve it for each save that week. Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Wed, 14 Apr 2004 11:23:09 -0500 from: rob@xxxxxxxxx subject: CPA4036 - File expiration dates out of sequence (C I R). We are having an issue in which a save spans to a second tape. Been running fine for years. We only initialize the first tape every night. We changed the order of the save and now we are getting this error. I am concerned that if I add a reply list entry or some such animal then it will try to go to the end of the second tape to start it's backup. That's no good. I want it to start at the beginning. All the files on the second tape are expired. Is the workaround to initialize all tapes until the rotation is such that the sequence is back in line? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.