|
That doesn't sound bad. Run it up the flagpole and see if anyone salutes. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Joe Lee" <LeeJD@xxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 10/11/2004 05:26 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To <rpg400-l@xxxxxxxxxxxx> cc Fax to Subject RE: Suggestion: File to use when compile Thanks for the URL, I'll try submitting a DCR, assuming I can find out what our IBM customer number is. As far as the precompile commands go, I'm not sure why they would be needed. If you mean that they would be used to handle the fake filenames, why couldn't the compiler just be told to use the compile time file name instead of the source code file name. So for example in the code below, assuming the new keyword is COMPILENAME, when the compiler ran instead of looking for file CUSMASTDDM, it would look for file CUSMAST and use it's properties. This would also be very useful for the new EXTFILE and EXTMBR keywords. FCUSMAST IF E K DISK FCUSMASTDDMIF E K DISK usropn COMPILENAME('CUSMAST') Joe Lee >>> rob@xxxxxxxxx 10/11/2004 14:38:32 >>> Some of those sound like simple options that could/should be easily added. Like a file level keyword for RSTDSP. Much like RPG's H-spec or SQL's SET OPTION. Don't know if a Design Change Request might get the ball rolling or not. But precompile commands, on separate objects might be a bit trickier. Like a CRTPF QTEMP/MYFILE... OVRDBF MYFILE QTEMP/MYFILE... At least, that should be a separate DCR. You might be tilting at windmills to try to get IBM to add this in to the commands but it sure can't hurt to try. https://www-912.ibm.com/r_dir/ReqDesChange.nsf/Request_for_Design_Change?OpenForm Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Joe Lee" <LeeJD@xxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 10/11/2004 03:49 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To <rpg400-l@xxxxxxxxxxxx> cc Fax to Subject RE: Suggestion: File to use when compile It seems to me that the length of this thread, and the number of methods that people use to work around this problem are a perfect demonstration of the need for a feature like this. Of course while requests of this nature are being made, I would love to be able to specify options for any of the create commands in the source files of the objects being created. For instance size(*NOMAX) in the source of a physical file, RSTDSP(*YES) DFRWRT(*YES) in the source of a display file, or various CRTSRVPGM/UPDSRVPGM options in a binder language source file. Joe Lee >>> Lim.Hock-Chai@xxxxxxxx 10/11/2004 09:04:11 >>> I would love to have them. Where/how can I get them? The CMS we are using have the ability to set up command to run on a object before compile. However, that command is printed on every request, which is pretty annoying. If I've 100 objects setup to run some commands before compiled, those 100 commands will be printed on every request (even those request the doesn't contain any of those 100 objects). -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Dan Bale Sent: Monday, October 11, 2004 8:36 AM To: RPG programming on the AS400 / iSeries Subject: RE: Suggestion: File to use when compile I would be happy to share my precompiler app with anyone who requests it. but Henrik's is much nicer in that you continue to use PDM option 14, and you can prompt the compiler command if you want to. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-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.