|
Traditionally, when this question comes up it is because someone created their file with SQL and that doesn't allow them to specify a record format name. Then they try to use it 'natively' in a HLL program, and they don't want to use a F spec keyword to rename the record format. (Although there's been some talk about relaxing that constraint.) What is often recommended is that they create the file with SQL as the same name as the desired record format name. Then rename the created file to the name that they want for the physical file. For example In SQL: create table mylib/myrecfmt ... At command line: RNMOBJ OBJ(MYLIB/MYRECFMT) OBJTYPE(*FILE) NEWOBJ(MYFILE) Other than that, I suppose your MI fiends can figure out a way to get into SST and patch that portion of the object. Given enough time, money and chemical inspiration, anything can be done. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Malchow, Grizzly" <GMalchow@xxxxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 04/08/2004 03:07 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <midrange-l@xxxxxxxxxxxx> cc Subject Rename a record format in a PF Is it possible to rename a record format in a physical file without having to recompile the physical file? _______________________________________________ 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-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.