Re: Input, update and output file in procedure

Just curious, but what release are you on? I was wondering why you

didn't use the RCDFMT clause on your CREATE TABLE.

V7R1 - Laziness for the test. The interactive SQL prompter doesn't ask for
it so I don't usually code it for quick tests. In production, we always
specify differently named RCDFMT. Makes it much easier to work with RPG
code.

Is using LIKEREC supported with the renamed record format when you

declare your data structure or do you have to use the original record
format name? Because I am gathering the data structure doesn't support any
subfields at this time.

The program compiled and ran correctly after coding separate *input and
*output DS. So I assume it likes the renamed format.


Other tests indicate that %fields can't be used to do the update as it
doesn't seem to like having the DS and %fields for the update. Guess I will
have to be careful coder...been getting used to just updating the fields
that need updating and not being concerned with what happened to the rest
of them. Of course, now the code will be tightly contained in a procedure,
the span of control is very tight.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.