At the risk of being called a cynic: Yeah, I’m sure the hundreds of ISPF developers will get right on that.
I’m guessing you’re about 30 years late. Which doesn’t make it a bad idea, just… From: ispf-l-l...@nd.edu [mailto:ispf-l-l...@nd.edu] On Behalf Of John McKown Sent: Tuesday, June 05, 2018 2:51 PM To: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu>; ISPF discussion list <isp...@listserv.nd.edu> Subject: [ISPF-L] Weird thought for ISPF enhancement I'm short of sleep ... again. When I came to work this morning, my Chrome browser was "dead". When I restarted it, it prompted me with a message asking if I wanted to restore all the pages I had been on. So, what occurred to me was, "Wouldn't it be nice if ISPF could do something like that." Now, ISPF doesn't really die often. But I think it would be a nice feature if there were a new ISPF command, perhaps called something like "SAVELEAVE" or HIBERNATE or whatever. This facility would let you logoff for the day, optionally SAVEing any changes if you're in EDIT or one or more screens. When you come in the next day, ISPF would give you an option to restore all your screens. Yes, there are problems about restarting an ISPF application, but basically you could only issue the above command at certain times, just like you can only SWAP or SPLIT, when you're in an DISPLAY verb. What I envision for an ISPF application is that it would get a special RC from the ISPF DISPLAY verb which would indicate "user wants to leave, checkpoint or abandon your processing". The application could then only do something like ISPF CHECKPOINT which would basically return to ISPF and ISPF would terminate the application. The application would need to save its non-ISPF environment (close files, etc) before it issued the CHECKPOINT. When the user gets back into ISPF, the application is restarted at the next instruction after the CHECKPOINT. At this point, the application would be responsible to restore its internal, non-ISPF maintained, status (open files, reload important variable, etc). This would occur for each active screen which did the ISPF CHECKPOINT. Well, that's likely getting too detailed for a general, initial, discussion. So, what are your thoughts? -- Once a government places vague notions of public safety and security above the preservation of freedom, a general loss of liberty is sure to follow. GCS Griffin -- Pelaran Alliance -- TFS Guardian (book) Maranatha! <>< John McKown -- You received this message because you are subscribed to the Google Groups "ISPF discussion list" group. To unsubscribe from this group and stop receiving emails from it, send an email to ispf-l-list+unsubscr...@nd.edu <mailto:ispf-l-list+unsubscr...@nd.edu> . To post to this group, send email to ispf-l-l...@nd.edu <mailto:ispf-l-l...@nd.edu> . ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
