Re: Standard menu command length

I ended up writing an encapsulating command/cl program combo that prompts
the user. The CL looks like this:

PGM

? BB15 +
??PROCS(*N) +
?-PRINT(*YES) +
?-RAWPKGLST(*SAME/PKGLBLAL) +
?-MBR(*CURRENT) +
?-SUBMIT(*YES) +
?-LBLGRP(*STD) +
?-PRTORD(*ASCEND) +
?-HLDLBLS(*NO)

MONMSG MSGID(CPF6801)

ENDPGM

This shows only the first parm and the others are blocked and unseen.

Thanks.


On Thu, Jan 31, 2019 at 10:40 AM <dlclark@xxxxxxxxxxxxxxxx> wrote:

David L Clark/it/crp/WinWholesale wrote on 01/31/2019 10:24:17 AM:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 01/31/
2019 08:30:34 AM:

Is there a way to increase the command length on a standard SDA menu?

I'm

thinking not.

I have a command on a menu and I added a parm. Now it won't fit. Most

of

the parms are preceded by ?- because I don't want the user to be able

to

change them, the new parm included.

Is my only option to encapsulate it into another command?

I presume you are referring to the command length in the QQ member
for the commands behind the menu selections. Yes? If so then, no,
the longest command length in the QQ member is 115 characters as
entered from the STRSDA screens. However, after you've created the
members the first time, you *may* be able to edit the QQ member
directly and get up to 155 characters. This won't work if you still
use STRSDA to create your menu. I wrote my own REXX command to
create the message file from the QQ member and mine supports the 155
character length. I think I'll go post it on the midrange wiki as
sample code. give me half an hour and it will be there.

I misspoke. My command supports the full 132 characters that the
message file supports for the first-level message text.


Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331





*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.

*********************************************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com