No. Straight I-specs. Both Statment# and StmtDate are unreferenced in the
program.
* IxRPGsrcOR ns
I 19 19 column7
I 1 6 Statment#
I 7 12 StmtDate
I 13 100 SrcData *
Does DS I/O buy me something?
Even if it does, it doesn't help in the situation where you're debugging a
production application that doesn't use DS I/O. This is a Q&D one-off
program that I *could* throw in DS I/O, but my question is more for when a
production app craps out, and time is of the essence.
From the RPG reference, READ opcode: "If the data-structure operand is
specified, the record is read directly into the data structure." O.k.,
from that, I might gather that the entire record is "moved" to the data
structure, regardless of whether the data structure's subfields are
referenced elsewhere in the program. Nothing appears to be explicitly
defined about what happens to the record (or, more precisely, its
unreferenced fields) if there is no data-structure operand specified, and I
guess I understood that this was standard behavior eons ago, but I thought
the *UNREF option was supposed to make those unreferenced fields "visible".
I further tested this by putting a DUMP(A) after the first record is read,
and the dump had the same behavior as debug: The unreferenced fields were
shown as having blank values. Interestingly, the RPG reference for DUMP
includes the following text (which is new to the V7R1 manual):
# The DUMP operation provides a dump (all fields,
# all files, indicators, data structures, arrays, and
# tables defined) of the module.
- Dan
On Wed, Jun 17, 2015 at 11:43 AM, Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:
Are you using DS I/O?
Jon Paris
As an Amazon Associate we earn from qualifying purchases.