|
Martin, Is this . a physical file with a key in it, wher you changed the key. . a physical file without a key, with 1 logical, where you added another logical . a physical file with a key, where you added a logical A physical file with a key in itself does not seem a good idea for me. If key is corrupted, the object is corrupted. With your cpyf, don't you simply copy the file in relative record access order, which by now still corresponds (or corresponds at a high degree) with the first key sequence. If you use a logical file and use that logical file as fromfile in the CPYF cmd, surely will resolve the problem. You might also do a reorganize on the file, but normally for that you indicate a logical file as reorganize sequence. I don't know if this works with a phiscal-keyed-file, but I imagine it should. Luc -----Oorspronkelijk bericht----- Van: boothm@ibm.net <boothm@ibm.net> Aan: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> Datum: dinsdag 20 oktober 1998 1:05 Onderwerp: re: cpyf to qtemp >Today was a *duh* sort of day. Perhaps someone can explain this to me: > >I have a physical file with one key in a library. I have for some time used a CL program to CPYF to copy it into QTEMP, OVRDBF, and then populate, use, and discard it. > >For design reasons the users would like the file presented in another order which would mean 3 keys on the file. No big deal, right? > >For some reason it will only give me the old 1-key variety when I CPYF it from the CL. I did a WRKOBJ *ALL/fil* *ALL and deleted everything i could find with a name even remotely like it. I've recompiled the files and the programs. I even copied the CL to another name and deleted all of the extra lines. Everything works the way I expect excepting the one CL program that I really do want to use. > >What I really don't understand is where on earth it is getting the instruction to copy the file with just one key, since all those instances are deleted. > >----------------------------------------------------------- >boothm@ibm.net >Booth Martin >----------------------------------------------------------- +--- | 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.