Re: Batch Formatting of CL Code

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Another option might be the API, which would give you a string in the right 
order, again without affecting the original source. You could analyze the 
resulting command string and go to the next one.

HTH

Vern

At 01:55 PM 5/7/2003 -0500, you wrote:
> Yeah, well....I disagree with you Rob, but each to their own. By the way,
> who cares about "valuable real estate" in an OS/400 source member?  It's not
> like you're likely to run out of memory any time soon because you happened
> to code a full-syntax DCL statement, is it?
>
> However, I need to have some consistency in our CL code so that I can write
> a program to analyze it and extract the variables used in the PGM PARM list,
> and then get those variable types and lengths, which I'm then storing in a
> database for another application to use.
>
> If I don't have consistency, then it's hard to figure out where a variable
> definition begins and ends. Especially considering that you can have the
> variable definition run across multiple source lines, if a programmer had
> coded it that way (it happens).  If I know that each DCL statement has the
> same format (i.e., DCL VAR() TYPE() LEN() ) then it's a lot easier to find
> the information I need, regardless of how many actual source lines it may
> span.
>
> Of course...if I had the option of coding this source analyzer in another
> language besides RPGIV, say VB, then this wouldn't be near the chore it is
> at the moment.
>
> But since this has to be code that the "old fogeys" ha! in our shop can read
> and understand also....I'm forced into trying to fit a square peg into a
> round hole on this by using RPG.
>
>
>
> Shannon O'Donnell