Re: Some questions on using ISPF Dialog Test
What you might want to try is getting into ISPF in TEST mode. If you look it up, I think the Syntax is ISPF TEST. This might give you a more pertinent dump. The other option is to use ISPVCALL to trace the ISPF application. Lizette > Dave Day Wrote > > I have an ISPF application where a clist performs some allocations, > then does the LIBDEF function for the allocations. The clist then > invokes the application with > > ISPEXEC SELECT PGM(APISPF) PARM(&PRM) NEWAPPL(APF1) PASSLIB > > > ISPF is giving me an abend 0c4 in a call to display a panel. The > call to display the panel is preceded by a CONTROL LOCK call. The > panel is used to display the status of an on-going function. After the > display, a CONTROL LINE is executed. The manuals don't really tell you > when, in a sequence of calls, the CONTROL LINE should be done, just > that after a CONTROL LOCK, a CONTROL LINE should be executed. So that > is question #1. Which is proper? > > CONTROL LOCK > DISPLAY > CONTROL LINE > > or > > CONTROL LOCK > CONTROL LINE > DISPLAY > >I don't think this is causing my 0c4. I beleive I have a storage > overlay problem. But I thought I would try this under dialog test. > When I tried to use dialog test to invoke the program, it got an > 806...module not found. This is after I executed another clist that > allocated the libraries and did the LIBDEFs for ISPLLIB, ISPPLIB, and > ISPMLIB. What do I have to do to get the dialog test to find my > program? Looks like LIBDEF does not work for dialog test. > -- 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
Re: Some questions on using ISPF Dialog Test
SNIP I think if you read the docs more carefully, you will find there are no "CONTROL LOCK" nor "CONTROL LINE" commands. The command you want is perhaps: CONTROL DISPLAY LOCK which locks the keyboard while the next panel is DISPLAYed So you could issue CONTROL DISPLAY LOCK DISPLAY process process process DISPLAY <- this will unlock the keyboard Alternatively, you could bound a standard DISPLAY using: CONTROL DISPLAY SAVE display, tbdispl, browse, view, or edit CONTROL DISPLAY RESTORE it all depends on what you are trying to accomplish. As far as working under test, it's hard to tell from your post. You might try getting to READY prompt and bringing up ISPF in TRACE mode: ISPF TRACEX then you should start out in trace mode. HTH. END SNIP Steve, Thanks for the response. typo on my part. The ISPF call that I am exeuting from my program is CONTROL DISPLAY LOCK and CONTROl DISPLAY LINE. I was not aware you could start ISPF with traceing turned on. I will give that a shot. Thanks. --Dave -- 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
Re: Some questions on using ISPF Dialog Test
Dave Day wrote: I have an ISPF application where a clist performs some allocations, then does the LIBDEF function for the allocations. The clist then invokes the application with ISPEXEC SELECT PGM(APISPF) PARM(&PRM) NEWAPPL(APF1) PASSLIB ISPF is giving me an abend 0c4 in a call to display a panel. The call to display the panel is preceded by a CONTROL LOCK call. The panel is used to display the status of an on-going function. After the display, a CONTROL LINE is executed. The manuals don't really tell you when, in a sequence of calls, the CONTROL LINE should be done, just that after a CONTROL LOCK, a CONTROL LINE should be executed. So that is question #1. Which is proper? CONTROL LOCK DISPLAY CONTROL LINE or CONTROL LOCK CONTROL LINE DISPLAY I don't think this is causing my 0c4. I beleive I have a storage overlay problem. But I thought I would try this under dialog test. When I tried to use dialog test to invoke the program, it got an 806...module not found. This is after I executed another clist that allocated the libraries and did the LIBDEFs for ISPLLIB, ISPPLIB, and ISPMLIB. What do I have to do to get the dialog test to find my program? Looks like LIBDEF does not work for dialog test. --Dave Day I think if you read the docs more carefully, you will find there are no "CONTROL LOCK" nor "CONTROL LINE" commands. The command you want is perhaps: CONTROL DISPLAY LOCK which locks the keyboard while the next panel is DISPLAYed So you could issue CONTROL DISPLAY LOCK DISPLAY process process process DISPLAY <- this will unlock the keyboard Alternatively, you could bound a standard DISPLAY using: CONTROL DISPLAY SAVE display, tbdispl, browse, view, or edit CONTROL DISPLAY RESTORE it all depends on what you are trying to accomplish. As far as working under test, it's hard to tell from your post. You might try getting to READY prompt and bringing up ISPF in TRACE mode: ISPF TRACEX then you should start out in trace mode. HTH. All this, and lots more, is covered in our five day class "Developing Dialog Manager Applications in z/OS". Check out: http://www.trainersfriend.com/TSO_Clist_REXX_Dialog_Mgr/a810descrpt.htm -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 http://www.trainersfriend.com * z/OS application programmer training + Instructor-led on-site classroom based classes + Course materials licensing + Remote contact training + Roadshows + Course development -- 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
