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
