|
You should be able to change the field in place to a length 22 numeric then use CPYF and MBROPT(*MAP) which maps field names, not positions. I normally do this by changing the DDS source, recompiling to a new physical file, doing the CPYF FMTOPT(*MAP), check and make sure everything is okay, then delete the original and rename the new file. There is some way, I understand, to change the file in place which basically does all of the above (with the exception of checking to make sure everything is okay) but I've never done it this way so am not positive how it's done. It's either some options under CHGPF or by recompiling the DDS over the existing file with some options there. Naturally if you do it this way you'd want to make a backup of the original first. HTH Regards, Jim Langston Programmer/Analyst Cels Enterprises, Inc. -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On Behalf Of Giri Gopal Sent: Wednesday, August 22, 2001 9:12 AM To: rpg400-l@midrange.com Subject: Advise on a Database Change Hi: A need has arrived to change the field size of a field. This field is 10th field in a 125 fields file. The field size is 9 numeric. Need to change this to 22 bye character field. The questions is Do I change the type and size at the same location (10th field) and recompile the file, or remove the field and add the column at the end of the file? Thanks for your advice in advance. GG _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@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.