× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.