Re: Vendor call returns up to 200 varying parms back, looking for easy way to scan it all.

True, I didn't understand what you meant.

You're right, then, that in 80 column mode there's not enough space on the screen.

However, CL programs can pass literals (vs variables) the same way (and are governed by the same rules.) In that case, you could have a longer (scrollable) command line.

Likewise, APIs like QCMDEXC or QCAPCMD can support much longer command strings, so it'd be possible to do this from a command string that's built in a program on-the-fly, or by a programatically-created command line.

But, you're point is valid -- it'd be extremely difficult with parameters this large to pass them from the command line.


On 7/2/2014 4:21 PM, John Yeung wrote:

Re: CALL QCMD, then F11

Perhaps people didn't get what I meant by "in 80-column mode, the
whole screen doesn't have enough room".

If we have a 999-character variable-length parameter, then as Scott
said, that's 1998 hex characters, just for the data alone, never mind
the leading 'x' or surrounding single-quotes, or 2-byte length
specifier.

An 80-column screen has 24 lines. That's 80 * 24 = 1920 total cells
for the entire drawable portion of the display. If you could somehow
write to the status row, you'd have a nice, round 2000 cells, which
still isn't enough to enclose your parameter properly.

The only chance is if the input area is scrollable, but I'm trying it
right now, and it's not moving.

John Y.