Re: I have an Idea for ISPF...
On Fri, 29 Sep 2023 16:16:32 -0700, Ed Jaffe wrote: >On 9/18/2023 1:22 PM, Tom Marchant wrote: >> I have been unable to convince my site to increase the maximum number of >> split screens, so I created my own ISPCFIGU that allows 32 and placed it in >> ISPLLIB. I've shown a few other people how to do it. I often use more than >> 8, and sometimes more than 16. > >Why on earth would anyone resist raising the number of allowable split >screens? > Delusional resources? A throwback to when admins restricted use of TSO (and more recently, OMVS.) >Why doesn't IBM simply raise the default unilaterally? > Compatibility phobia. (If it don't work, don't fix it.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
On 9/18/2023 1:22 PM, Tom Marchant wrote: I have been unable to convince my site to increase the maximum number of split screens, so I created my own ISPCFIGU that allows 32 and placed it in ISPLLIB. I've shown a few other people how to do it. I often use more than 8, and sometimes more than 16. Why on earth would anyone resist raising the number of allowable split screens? Why doesn't IBM simply raise the default unilaterally? -- Phoenix Software International Edward E. Jaffe Chief Technology Officer 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
It is done with the TSO ISPCCONF command from within ISPF. Option 7 will convert the configuration table that is currently loaded to source that you can edit. After making your changes, option 4 will build the table load module. The table load module is placed in a data set in your ISPLLIB concatenation -- Tom Marchant On Mon, 18 Sep 2023 13:38:38 -0700, M. Ray Mullins wrote: >I have done this, too. Since I’m on vacation, I couldn’t remember all the >steps to do this, so I didn’t want to mention it. > >Sent from my iPad > >> On Sep 18, 2023, at 13:22, Tom Marchant >> <000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote: >> >> I have been unable to convince my site to increase the maximum number of >> split screens, so I created my own ISPCFIGU that allows 32 and placed it in >> ISPLLIB. I've shown a few other people how to do it. I often use more than >> 8, and sometimes more than 16. >> >> -- >> Tom Marchant >> >>> On Mon, 18 Sep 2023 13:11:23 -0700, M. Ray Mullins >>> wrote: >>> >>> Just a correction: the default number of screens in ISPF is 8, but you can >>> configure up to 32. My site uses 16. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
Huh. I remember the default limit of eight, but don't think about it much; I think my usual max is four or five. At three or four I start using SCRNAME and closing down unused screens. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* How much better for us if all humans died in costly nursing homes amid doctors who lie, nurses who lie, friends who lie, as we have trained them, promising life to the dying, encouraging the belief that sickness excuses every indulgence, and even, if our workers know their job, withholding all suggestion of a priest lest it should betray to the sick man his true condition! -musings of a tempter, from The Screwtape Letters by C S Lewis */ -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Marchant Sent: Monday, September 18, 2023 16:23 I have been unable to convince my site to increase the maximum number of split screens, so I created my own ISPCFIGU that allows 32 and placed it in ISPLLIB. I've shown a few other people how to do it. I often use more than 8, and sometimes more than 16. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
I have done this, too. Since I’m on vacation, I couldn’t remember all the steps to do this, so I didn’t want to mention it. Sent from my iPad > On Sep 18, 2023, at 13:22, Tom Marchant > <000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote: > > I have been unable to convince my site to increase the maximum number of > split screens, so I created my own ISPCFIGU that allows 32 and placed it in > ISPLLIB. I've shown a few other people how to do it. I often use more than 8, > and sometimes more than 16. > > -- > Tom Marchant > >> On Mon, 18 Sep 2023 13:11:23 -0700, M. Ray Mullins >> wrote: >> >> Just a correction: the default number of screens in ISPF is 8, but you can >> configure up to 32. My site uses 16. > > -- > 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
Re: I have an Idea for ISPF...
I have been unable to convince my site to increase the maximum number of split screens, so I created my own ISPCFIGU that allows 32 and placed it in ISPLLIB. I've shown a few other people how to do it. I often use more than 8, and sometimes more than 16. -- Tom Marchant On Mon, 18 Sep 2023 13:11:23 -0700, M. Ray Mullins wrote: >Just a correction: the default number of screens in ISPF is 8, but you can >configure up to 32. My site uses 16. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
Just a correction: the default number of screens in ISPF is 8, but you can configure up to 32. My site uses 16. Sent from my iPad > On Sep 18, 2023, at 12:06, Schmitt, Michael wrote: > > Same problem occurs with any other application that doesn't use the same > RFIND as ISPF. DSLIST entered from that command can lead to errors. I just > used SDSF because it is an example of an IBM application, so they can't blame > it on some other company. > > The root cause here is that ANY command that can lead to ISPF Edit or Browse > or View needs to switch to the ISPF applid, or else that application must > define the commands as ISPF expects. The DSLIST command can lead to ISPF > Edit/Browse/View, but it doesn't switch the APPLID. It should. > > My company has corrected the problem internally but that doesn't help anyone > else. > > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Sri h Kolusu > Sent: Monday, September 18, 2023 1:38 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: I have an Idea for ISPF... > >>> 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. > > https://www.mail-archive.com/ibm-main@bama.ua.edu/msg06759.html > > 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
Same problem occurs with any other application that doesn't use the same RFIND as ISPF. DSLIST entered from that command can lead to errors. I just used SDSF because it is an example of an IBM application, so they can't blame it on some other company. The root cause here is that ANY command that can lead to ISPF Edit or Browse or View needs to switch to the ISPF applid, or else that application must define the commands as ISPF expects. The DSLIST command can lead to ISPF Edit/Browse/View, but it doesn't switch the APPLID. It should. My company has corrected the problem internally but that doesn't help anyone else. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Sri h Kolusu Sent: Monday, September 18, 2023 1:38 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: I have an Idea for ISPF... >> 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. https://www.mail-archive.com/ibm-main@bama.ua.edu/msg06759.html 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
Re: I have an Idea for ISPF...
>> 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. https://www.mail-archive.com/ibm-main@bama.ua.edu/msg06759.html Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
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 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
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
Re: I have an Idea for ISPF...
The underlying problem is at risk anytime a user enters a command on 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. When *I* create ISPF dialogs and commands, I code them so that they don't get data set name, DD name, table name, or LIBDEF name conflicts *regardless* of what the user does, where they do it, or how many times they do it in the same second. Which is why *I* don't use FTOPEN TEMP. But ISPF does, hence the problem. FWIW, I almost never create more than two ISPF screens. I do my work by stacking commands on top of each other. I find it makes it easier to keep track. I see other people creating so many screens that they spend half their time trying to find which screen is the right one (they don't know how to name their screens). And I'm not the only one who stacks sessions. Remember that the SuperC conflict was reported to me by another user. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Sri h Kolusu Sent: Monday, September 18, 2023 11:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: I have an Idea for ISPF... >> Then in that Edit session, I enter DSLIST and a pattern that leads to a >> library. From the DSLIST, I browse the library, and enter SRCHFOR something. >> That creates a second FTOPEN TEMP to build the input to the search, on top >> of the previous one, all within the same ISPF session. What would the data >> set name be? Michael, You are using the same Screen and if you issued the SRCHFOR on the DSLIST panel when it brings up the list you would have gotten the exact error message "ENQUEUE failed" at the top right corner. And if you pressed PF1, then you would have got this message. --- | Data set SPFCNTLX in use, ENQUEUE failed. | --- This is the reason for the Allocation error Since ISPF provides you up to 8 screens, why NOT issue the SRCHFOR in another screen ? By doing so , the respective screen LIST/work datasets will be opened. 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
Re: I have an Idea for ISPF...
>> Then in that Edit session, I enter DSLIST and a pattern that leads to a >> library. From the DSLIST, I browse the library, and enter SRCHFOR something. >> That creates a second FTOPEN TEMP to build the input to the search, on top >> of the previous one, all within the same ISPF session. What would the data >> set name be? Michael, You are using the same Screen and if you issued the SRCHFOR on the DSLIST panel when it brings up the list you would have gotten the exact error message "ENQUEUE failed" at the top right corner. And if you pressed PF1, then you would have got this message. --- | Data set SPFCNTLX in use, ENQUEUE failed. | --- This is the reason for the Allocation error Since ISPF provides you up to 8 screens, why NOT issue the SRCHFOR in another screen ? By doing so , the respective screen LIST/work datasets will be opened. Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
I'm not following this. Let's say I have pre-allocated work DDs, and I start ISPF. Then I go to SuperC, request a batch compare, and that I want to edit the generated batch JCL. That's one FTOPEN TEMP. What would the data set name be? Then in that Edit session, I enter DSLIST and a pattern that leads to a library. From the DSLIST, I browse the library, and enter SRCHFOR something. That creates a second FTOPEN TEMP to build the input to the search, on top of the previous one, all within the same ISPF session. What would the data set name be? (I gave the above example because it can be tested using purely standard out-of-the-box ISPF functions.) -Original Message- From: IBM Mainframe Discussion List On Behalf Of Sri h Kolusu Sent: Monday, September 18, 2023 10:52 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: I have an Idea for ISPF... >>- Not sure how this would help. Would it change the data set name generated >>by FTOPEN TEMP? And in a way that would create a different data set in a >>stacked session? Michael, If they are pre-allocated, then you would have Individual list/work datasets for each stacked session. So, it would open the respective session dataset and there by avoid allocating the same TEMP dataset and will not have the error that you are encountering. 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
Re: I have an Idea for ISPF...
>>- Not sure how this would help. Would it change the data set name generated >>by FTOPEN TEMP? And in a way that would create a different data set in a >>stacked session? Michael, If they are pre-allocated, then you would have Individual list/work datasets for each stacked session. So, it would open the respective session dataset and there by avoid allocating the same TEMP dataset and will not have the error that you are encountering. Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
- I don't have authority to create or modify the login prompt (but I can change the DDs before ISPF starts) - Wouldn't fix the root cause for anyone else - Not sure how this would help. Would it change the data set name generated by FTOPEN TEMP? And in a way that would create a different data set in a stacked session? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Sri h Kolusu Sent: Friday, September 15, 2023 5:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: I have an Idea for ISPF... >> The reason is because FTOPEN TEMP creates the file name using an ISPF "CNTL" >> file, which follows a certain naming format. For example: >> userid.lpar.SPFTEMPn.CNTL, where "n" is the logical session number. In a >> stacked session it is still the same session number, hence there's a naming >> conflict. Michael, How about pre-allocating the ISPF work datasets? You can add the following to your LOGON proc and they would be allocated by default. You can increase the allocations if you want more. //ISPCTL0 DD UNIT=SYSVIO,SPACE=(CYL,(10,2)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=800) //ISPCTL1 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=800) //ISPCTL2 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=800) //ISPWRK1 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FB,LRECL=256,BLKSIZE=2560) //ISPWRK2 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FB,LRECL=256,BLKSIZE=2560) //ISPLST1 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FBA,LRECL=121,BLKSIZE=1210) //ISPLST2 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FBA,LRECL=121,BLKSIZE=1210) Thanks, Kolusu DFSORT Development IBM Corporation -- 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
Re: SDB (was: I have an Idea for ISPF...)
On Fri, 15 Sep 2023 23:52:23 +, Sri h Kolusu wrote: >>> What's the default DSORG? Does SDB not respect that? I've long trusted >>> SDB. > >SDB is supported foD DSORGs of PS and PO for DASD and tape datasets. > Also for UNIX and JES. I know because at the advent of SDB REXX removed its OPEN exit to allow SDB to operate. That broke my ALLOC SYSPRINT PATH(...) LRECL(137) because SDB defaulted to BLKSIZE(80) for unknown devtype. Fixed promptly by an available PTF. Tier 1 advised me, "*Always* specify BLKSIZE," which I regarded as an ironic consequence of SDB; I ignored it. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDB (was: I have an Idea for ISPF...)
>> What's the default DSORG? Does SDB not respect that? I've long trusted SDB. Gil, SDB is supported for DSORGs of PS and PO for DASD and tape datasets. Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SDB (was: I have an Idea for ISPF...)
On Fri, 15 Sep 2023 23:25:02 +, Sri h Kolusu wrote: >>> Is there reason not to use BLKSIZE=0, which has been preferred for over a >>> decade (but may not work with COBOL.) > >You can use BLKSIZE=0, but also code DSORG=PS , so that SMS calculates the >Optimum Blksize based on the LRECL > What's the default DSORG? Does SDB not respect that? I've long trusted SDB. I assume SDB operates *after* the DCB OPEN exit, for compatibility with ancient code. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
>> Is there reason not to use BLKSIZE=0, which has been preferred for over a >> decade (but may not work with COBOL.) Gil, You can use BLKSIZE=0, but also code DSORG=PS , so that SMS calculates the Optimum Blksize based on the LRECL Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
Still recommended for z/OS 2.3. https://www.ibm.com/docs/en/zos/2.3.0?topic=performance-preallocate-ispf-temporary-data-sets-vio On Fri, Sep 15, 2023 at 6:11 PM Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > > On Fri, 15 Sep 2023 22:47:49 +, Sri h Kolusu wrote: > > > >//ISPCTL0 DD UNIT=SYSVIO,SPACE=(CYL,(10,2)), > >// DCB=(RECFM=FB,LRECL=80,BLKSIZE=800) > > > Is there reason not to use BLKSIZE=0, which has been preferred > for over a decade (but may not work with COBOL.) > > (At times I've published JCL/REXX allocating a temp DSN as profile > because I wanted my scripts to control the ISPF environment.) > > -- > gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
On Fri, 15 Sep 2023 22:47:49 +, Sri h Kolusu wrote: > >//ISPCTL0 DD UNIT=SYSVIO,SPACE=(CYL,(10,2)), >// DCB=(RECFM=FB,LRECL=80,BLKSIZE=800) > Is there reason not to use BLKSIZE=0, which has been preferred for over a decade (but may not work with COBOL.) (At times I've published JCL/REXX allocating a temp DSN as profile because I wanted my scripts to control the ISPF environment.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: I have an Idea for ISPF...
>> The reason is because FTOPEN TEMP creates the file name using an ISPF "CNTL" >> file, which follows a certain naming format. For example: >> userid.lpar.SPFTEMPn.CNTL, where "n" is the logical session number. In a >> stacked session it is still the same session number, hence there's a naming >> conflict. Michael, How about pre-allocating the ISPF work datasets? You can add the following to your LOGON proc and they would be allocated by default. You can increase the allocations if you want more. //ISPCTL0 DD UNIT=SYSVIO,SPACE=(CYL,(10,2)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=800) //ISPCTL1 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=800) //ISPCTL2 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=800) //ISPWRK1 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FB,LRECL=256,BLKSIZE=2560) //ISPWRK2 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FB,LRECL=256,BLKSIZE=2560) //ISPLST1 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FBA,LRECL=121,BLKSIZE=1210) //ISPLST2 DD UNIT=SYSVIO,SPACE=(CYL,(1,1)), // DCB=(RECFM=FBA,LRECL=121,BLKSIZE=1210) Thanks, Kolusu DFSORT Development IBM Corporation -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
I have an Idea for ISPF...
Some years ago I reported a problem in ISPF to IBM: in certain cases, the ISPF member list SRCHFOR command would fail with a cryptic error: Message id: ISRS083 Short message: Allocation error Long message: Allocation error on "statements/profile" data set. This was just one case of a problem with the FTOPEN TEMP service, which generates a temporary file. If *any* other function attempts to do a 2nd FTOPEN TEMP in a *stacked* ISPF session, it will generate the error. The reason is because FTOPEN TEMP creates the file name using an ISPF "CNTL" file, which follows a certain naming format. For example: userid.lpar.SPFTEMPn.CNTL, where "n" is the logical session number. In a stacked session it is still the same session number, hence there's a naming conflict. IBM said I'd need an enhancement request to address the underlying issue, so I created one. Now I've learned that the scope of the problem is much larger than I thought. A user was trying to use an application that drives SuperC, and they hit another cryptic error: Message id: ISPD230 Short message: Recursion error Long message: Recursive execution of an ISPF function is not allowed But this doesn't just mean you can't run SuperC on SuperC. ISPF has a black list of any ISPF application that uses FTOPEN TEMP. This includes: ISRFPR - ISPF option 4 (Foreground) ISRJB1 - ISPF option 5 (Batch) ISRUHC - ISPF option 3.6 (Hardcopy Utility) ISRUOLP - ISPF option 3.8 (Outlist Utility) ISRSSM - ISPF option 3.12 (SuperC Standard Dialog) ISRSEPRM - ISPF option 3.13 (SuperC Extended Dialog) ISRSFM - ISPF option 3.14 (SuperC Search-for Dialog) And ISPF compress from 3.1 or 3.4 If *any* if these functions is active, you can't do *any* of these other functions in the same session. This is all because of the underlying FTOPEN TEMP issue. Again, IBM said an enhancement request is required. I updated my previous Idea with the increase in scope of the issue. It is at: https://ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-1690 If you think this is a good Idea, you know what to do... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
