|
Anshu, In a message dated 97-05-08 06:07:23 EDT, you write: > I am a trainee programmer on RPG/400, I have a small problem.... > I created physical file and used UPDDTA to enter data into it. Later on I > changed the physical file fields. I also based a logical on this physical > file with a key . > > But now when I want to enter the data in the new physical file it gives me > the old fields. Obviously , I have not deleted the data/physical file. In > the DDS listing I can't see any mention of the old physical file , the new > physical with the new fields is there. > > Does it sound confusing........? Sounds VERY confusing! I can only imagine four scenarios: 1. You created the file in a library that your CPYF command didn't have access to when you restored the data. 2. You didn't re-compile your logical file, and it is still pointing at your "old" physical file. 3. You compiled the file without replacing it. 4. You are running in the S/36 environment, and you did not perform an IDDULINK UNLINK followed by an IDDULINK LINK when compiling the file. Some suggestions, and I probably missed something... HTH, Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA E-Mail: DAsmussen@AOL.COM "A study of economics usually reveals that the best time to buy anything is last year." -- Marty Allen * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. 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.