>I can't explain why you need "DIALOG;;;4" rather than "DIALOG;;4" which I
>would have expected.
My CLIST test works with two or more delimiters. Anything more than 2 is
ignored.
Enter TSO commands below:
===> dand;;;;;;;;;;;;;;;u.1.1
Regards,
John K
ISPEXEC CONTROL ERRORS RETURN
ISPEXEC CONTROL NONDISPL ENTER NOSETMSG
ISPEXEC DISPLAY PANEL(DAND)
ISPEXEC SELECT PANEL(TRI@PRIM)
ISPEXEC CONTROL ERRORS CANCEL
From: Walt Farrell <wfarr...@us.ibm.com>
To: IBM-MAIN@bama.ua.edu
Date: 06/21/2011 09:14 AM
Subject: Re: Maintaining ISPF's command stack
On Tue, 21 Jun 2011 09:40:39 -0400, DanD <mvs-j...@sympatico.ca> wrote:
>The )BODY section of the USERINFO panel does contain CMD().
>As it is never displayed it only contains a single line of blanks with an
>attribute byte as the 1st character. You get an error when you have a
>null )BODY section.
>
>Are you saying that the ";4" is returned with the display of he USERINFO
>panel, even though the user will never actually see this panel? That
>doesn't sound logical to me.
Yes, that's what I'm suggesting has happened. As for not being logical, you
may be right. But note that even without your code, in "DIALOG;4" the user
never sees the first panel the dialog would display, but the "4" is used as
though he had seen it. To me, this is very similar. In both cases, the "4"
is used (I think) in response to the first display the dialog performs, and
in both cases the user is not seeing that first-displayed panel.
>
>When I zap the code to branch around the call to the module that
>CONTROL,NONDISPL/DISPLAY's the USERINFO panel the "DIALOG;4" works as I
>would expect...option 4 is selected from the first DISPLAYed panel. When
>the CONTROL,NONDISPL/DISPLAY code is invoked, to get the same results I
have
>to enter "DIALOG;;;4" (why 2 extra simicolons?).
I can't explain why you need "DIALOG;;;4" rather than "DIALOG;;4" which I
would have expected.
>Does this sound like a bug to you? Is a PMR suggested?
Perhaps a Q&A type of PMR, if you have a support contract that allows you
to
ask questions. As I'm not part of the ISPF team here at IBM I'm not
suggesting you've found an ISPF bug.
I would start by trying to work around this (or researching it further) by
defining a command field on your non-display panel, and seeing what you get
when the user enters "DIALOG;4". If you get the 4, then you can perhaps
pass
that back to your dialog for it to operate on, and you have an immediate
workaround for your problem.
Whether you should need to do that, or not, I really can't say. Someone
from
ISPF may know, but I don't. And perhaps this is more appropriate for the
ISPF-L list than for IBM-MAIN.
--
Walt
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
