×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Using comments for the mod marks is what one has to do with CL - we do that here. For RPG, using the first 5 positions has been successful, perhaps a happy accident - seems I have seen in RDi that with RPG type, the first 5 position actually consist of 2 values - at least, there are 2 colors - I checked the color syntax stuff in RDi - for RPG source type, the 1st 2 positions are a page number, positions 3-5 are a line number, the former is set with black text, the latter is gray text.

In IleRPG code, that area is given the syntax of a comment in RDi.

I just looked at the QUSLOBJ copy member in QSYSINC - IBM has modifications in the comment header, where the flag is $A0, for example - in the body, these might be marked in the right-hand comment area with @A0A for the first change, say.

I don't know if there are any fully-free copy members in QSYSINC, so I don't know what those would look like - I checked a recent one, last changed in 2018  - still fixed format, and no comments in the body, just the header.

Ramblings shall cease - back to work!

Regards
Vern

On 10/2/2019 8:30 AM, Jim Hawkins wrote:
You can't do that with full free (**Free in column 1 row 1)

I do it this way:

// Setll (System:'C ') clients; //d kc01
Setll (System:Client) clients; //a kc01


I have always put comments at the top of the program with the mod mark and
then in positions 1-4 put the mod mark. For >example
kc01 // Kerwin Crawford P#2196 kc01
kc01 // The program stopped working when xxx
.
.
.
kc01 // Setll (System:'C ') clients;
kc01 Setll (System:Client) clients;

Note I do not have any sort of CMS.

Jim Hawkins
Programmer Analyst
Interkal LLC
Kalamazoo, MI





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-2026 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.