× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 23/03/2006, at 5:18 AM, Captain Jerry wrote:

I've got a QRPGLESRC file that someone, in their infinite wisdom, created at a record length of 92. I've been tasked with converting (copying?) this
into a standard 112 long source file.

A standard source file *IS* 92 bytes. It is only RPG IV that uses a non-standard 112 byte record length--and even it doesn't *REQUIRE* it. Other languages will also often tolerate a larger record length but for most it makes no sense. RPG IV will work quite happily in 92 bytes so why are you doing this silly task?

In fact I would suggest that using 92-byte source records for RPG IV is better than 112 because it stops the right-hand comment section from being used. This is a good thing! because I've rarely seen right-hand comments do anything more than reiterate what the code does. For example:

        C                                               ADD  1                  
        X                       Increment X

Well, Duh! I knew that. What I need to know is WHY and explaining why will take more than 20 bytes so provide proper block comments for each code block and forget the right-hand comment section exists.

Even IBMs CVTRPGSRC command will allow you to convert into a 92 byte source record. It will issue a warning but quite happily truncate the nearly useless comment section.

The only time a wider record length makes sense is with a free-form language and even RPG IV has a stupid restriction on the width of a line in free-form. The RPG parser stops reading at byte 92 and ignores anything following. As far as I know that defect still hasn't been corrected.

Easy task, but the problem is that the Member Last Changed Date is being updated to the current date. Is there any way to accomplish this conversion,
yet retain the original changed date?

I would have expected the job-date trick suggested by Cozzi to have worked but since you say it doesn't ...

You can 'fix' the date using SST if you have access to it. You can also fix it with a system-state program (or could the last time I tried). If I recall correctly there is an example of either this very task or something similar in the MI list archives or in the iSeries Network site.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.