I know there's a conflict. That's the issue: FTOPEN TEMP is reusing the same data set name in the same ISPF session. This conflict doesn't occur if the application generates its own data set name for file tailoring.
Yes, it is a personal preference. When I need more than 2 simultaneous then I do that, but most of the time I need to view something and return, so I can stack the browse/edit/view on top of what I'm doing. Over the last 30 years my company, team, and myself have created lots and lots of productivity commands that enable this. What I used to do when I had the situation I needed to view 3 or 4 things simultaneously is use the web server access to MVS data sets, to open the file in a web browser. But that doesn't work anymore because it uses basic authentication, which is no longer permitted in the web browser. How I Stack: - STACK command (I like it better than START for reasons) - BR command browses - ED command edits - VW command views - MBRLIST command does a member list - DSLIST command (comes with ISPF) - SDSF command, although normally I just STACK;S - CAVIEW command - EASE command stacks our development environment - AT command does edit/browse/view/any other TSO command using the data set at cursor - QA command does "quick action". I wrote it but don't use it. - DMB/E command browse or edits a member in the same concatenation as the current member - FINDPROC command browse/edit/versions etc. procs in the member being edited - PGMXREF does a program cross-reference - DSNXREF does a data set cross-reference - PROCXREF does a proc cross-reference - IMSXREF does an IMS cross-reference - WHEREIS searches, versions, browse, edit, etc. any member in any allocated DD - DDLIST ISPF's version of WHEREIS, sort of And several dozen more that I'm not remembering. Any of these commands results in a new, stacked command line, which means that there's now an opportunity for the user to enter ANY other command. What I've seen over the years is dialog developers don't account for this. If you display a panel, or do something that does, now you've give control back to the user, and they will MESS YOU UP. Even IBM has problems with this. For example, the DSLIST command comes with ISPF, but it doesn't set NEWAPPL. This means if you use it on top of an application whose command table / keylists are not ISPF standard, it leads to errors. For example, go to SDSF, then do DSLIST, then browse a data set from the list, then find something, then PF5 (RFIND). It won't work, because SDSF's PF5 is not RFIND; it is IFIND and there's no RFIND defined in ISFCMDS. I reported this to IBM YEARS ago but they haven't fixed it. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Sri h Kolusu Sent: Monday, September 18, 2023 12:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: I have an Idea for ISPF... >> the command line that eventually leads to another FTOPEN. This is like >> saying that "why are you making left turns? You can just make a bunch of >> right turns instead". The capability exists, it should work. Michael, In your case since you are EDITING the supec generated JCL in batch, it is opened in EXCLUSIVE mode and unless you close it, no one else can access it. That behavior is same across any operating system. The FTOPEN error is the result of Enqueue failure. >>(they don't know how to name their screens). SCRNAME has existed for a long time. With ZSTART parm, you can stack the commands to having multiple screens along with their names. And if someone forgot as to how many screens they have ,then they can use SWAPBAR ON and it shows ALL of the screens with their names and you can point to the screen of your choice using the mouse and click on it to get to the desired screen. https://www.ibm.com/docs/en/zos/2.5.0?topic=commands-scrname https://www.ibm.com/docs/en/zos/2.5.0?topic=commands-swapbar >> FWIW, I almost never create more than two ISPF screens. I do my work by >> stacking commands on top of each other. I know it is a personal preference but, aren't you limiting yourself when you need more than 2 screens ? For example Viewing a DUMP in 1 screen and the LISTING in 1 screen and Input/output files in another screen ? Also, just curious as to how you are keeping track of your stacked sessions? Let's say you stacked 8 layers and then when you need to get out of each session, how do you ensure that you accidentally don't close a session that you need to save? Thanks, Kolusu ---------------------------------------------------------------------- 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
