|
Are you just trying to get rid of the blank lines of code? How about DBU? -----Original Message----- From: rob@dekko.com [mailto:rob@dekko.com] Sent: Wednesday, November 27, 2002 11:41 AM To: rpg400-l@midrange.com Cc: code400-l@midrange.com Subject: QSYSINC/QRPGSRC,QUSRSPLA This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] I found 3 bugs in QSYSINC/QRPGSRC,QUSRSPLA. Basically OPM RPG has a real problem with blank lines in the source. I cannot fix this because editing and saving this member will not work in that file, in that library, (EDT0254). I tried CODE/400 (blows up and terminates server-nasty), and SEU (shudder) gives me the EDT0254 message. How do y'all handle this? - Copy the members from QSYSINC into your library and fix it? - Convert original program to RPGLE? (Strange but the copy in QRPGLESRC doesn't have the blank lines. Must be because RPGLE supports it and RPG doesn't and anything to discourage OPM RPG...) - Open a PMR and get a refreshed copy of QSYSINC? - Change file attribute (if possible) on QSYSINC/QRPGSRC to allow the save of the fixed member? (Copied to CODE400 list in case they want to fix that editor to handle the special case of QSYSINC/QRPGSRC.) Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ 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 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.