Re: RPG File Input/Output Specs

Kurt Anderson wrote:

... But once I introduce a procedure into the program, it creates the
=O specs for NewFile, which then causes a conflict because some
fields share names between the files, but do not share the same
definitions.

Is there a reason for this? All I know to do is to change the
procedure to be a subroutine (shudder) and continue on my way. ...

The RPG compiler is a one-pass compiler, which means that it only reads the source once. It creates the listing and generates the =O specs while it's reading the source.

When it sees the first P spec, it has to generate all the =O specs so that they will be available in case one of the later procedures is going to do a WRITE or an UPDATE opcode.

One way to get around this would be to code PREFIX on the F spec for NewFile, say PREFIX(N). That will cause the O specs to get different names. If that might cause a new conflict, you could code PREFIX('N.') and define a qualified data structure N with LIKEREC(NewFileF:*OUTPUT).

Aside: I see you're on V5R4, but if you were on V6R1, you could code QUALIFIED on the F spec for NewFile, and you won't get any =O specs generated.
Then you'd have to qualify the record format:
Write NewFile.CdrMstF ds_New;