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 [email protected] with the message: INFO IBM-MAIN
