How about not using ==> ? On Tue, 6 Dec 2011 17:28:20 -0600 Chuck Arney <[email protected]> wrote:
:>I need some pointers on programming with the ISPF Jump command. :> :>I'll provide some background details first to hopefully prevent suggestions :>for things I have already tried. I am working on an assembler ISPF :>application that does not use the ISPF Select service nor ZSEL in panel :>definitions. It is a single load module that uses the ISPF Display service :>to display menus and data panels. It performs all its own processing of :>menus. :> :>I am in the process of adding support for fast path commands. Without using :>the Select service, the Dialog Manager does not seem to handle multi-level :>menu selections (eg. 8.3) at all, so I have implemented code to support :>that. :> :>The problem I have is with the ISPF Jump (=) command. I would like for the :>application to operate as any standard ISPF application using the normal :>Jump command which users will expect. I would like to either find a way for :>the Dialog Manager to handle the multi-level menu commands or to completely :>disable it. So far I have not found a way to prevent ISPF from handling the :>= command. Whenever an =x.x style command is entered, ISPF processes the :>Jump command (generating return code 8 and ZVERB RETURN for each panel :>display back to the Primary Menu) but I don't get the remainder of the :>command (the x.x part). ZCMD is blanks and ZVERB is RETURN. I attempted to :>use the .trail function to get the remaining command into a variable, with :>no success. Either that is handled by Select, which I don't issue, or I :>have not found the right combination to get it set. :> :>At this point I would like to stop ISPF from handling the = command at all, :>so that I receive it along with the rest of the command string but I have :>not found a way to do that. Using the nojump(on) parameter on the field :>attribute panel definition does not help because that simply creates an ISPF :>error message if the = command is used and the command input is not provided :>to the program. :> :>Is there a way to stop, via a program call or panel definition, ISPF from :>processing the = command? Or a way to change Jump to another character so I :>could use =? Or, am I missing something obvious and going about this in the :>wrong way? :> :>I currently have the needed support implemented by using a different :>character as my Jump command, but that's not intuitive to a typical ISPF :>user. Surly there is something I have not been able to find in the :>documentation, to do this. :> :>Thanks for any suggestions. :> :>Chuck Arney :>Arney Computer Systems :> :> :> :>---------------------------------------------------------------------- :>For IBM-MAIN subscribe / signoff / archive access instructions, :>send email to [email protected] with the message: GET IBM-MAIN INFO :>Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
