Bob, As I wrote to Gadi, if you enter ISPF with TEST operand, all panels will be fetched from the dataset, not from storage copy. see below:
In TEST mode, ISPF operates differently from normal mode in these ways: - Panel and message definitions are fetched again from the panel and message files when a panel name or message ID is specified in an ISPF service. In normal mode, the most recently accessed panel definitions are retained in virtual storage. If you have modified the panel or message file, use of TEST mode ensures that the latest version of each panel or message is accessed during a test run. Using an editor to modify a panel, message, or skeleton can result in an additional DASD extent being required for the associated data set. DASD rarely (if ever) gains new extents as the result of the execution of software (with the possible exception of DASD formatting software). It can also be caused by link-editing a module. When a new extent is allocated, you can access the modification only by first terminating and then invoking ISPF again. ITschak *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* On Thu, Jul 30, 2020 at 3:25 PM Bob Bridges <robhbrid...@gmail.com> wrote: > This is WAD. ISPF normally keeps a copy of each panel as it reads it, and > uses that copy the next time it's invoked, I suppose to save time. There's > supposed to be an option you can invoke, when you're developing panels, > that'll read the member afresh each time it's needed, but I never got > around > to learning it. You don't have to log off all the way, just exit ISPF and > go back in, which is what I normally do. That is, go back to the READY > prompt, then type ISPF from there to return to the PDF menu. Still a pain, > but not nearly as much of one. > > There are shops that automatically log a user off upon exiting ISPF, so you > never see the READY prompt. If you're at one of those installations, you > can probably get someone to modify the logon proc to add you to the list of > exceptions (there are always exceptions, sysprogs at the very least) so > that > you won't be logged off as you leave ISPF. That requires one extra LOGOFF > command to leave TSO, but I'm an old user and prefer having the option. > > If I wrote in ISPF more often, no doubt I'd finally force myself to learn > about that method of reloading the panel every time. > > --- > Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 > > /* re-cur-sive (ri: 'kr sIv), from "re-" + Lat. "cursire" (to say "Oh, > hell, > not AGAIN!"): See "recursive". */ > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Gadi Ben-Avi > Sent: Thursday, July 30, 2020 02:14 > > I was told to develop an ISPF application. > It's been a long time since I did this, so I'm having some issues. > > Whenever I change a panel definition, I have to logoff and logon for the > updated definition to show. > Is there a way to have ISPF use the updated definition without logging off > and on. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
