ISPF itself does not allocate any data sets at all. It's common practice in most shops to run an 'initialization' script during logon processing to allocate the user's previously created profile data set with the required DDNAME ISPPROF. The profile does not need to have any data contents at all. It just has to be an FB-80 PDS. The first time ISPF uses it, it will 'seed' an empty profile with the minimum necessary members.
There is no required DSN naming convention for the profile, hence no native facility to find an existing one.
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-543-6132 Office ⇐=== NEW
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Steve Coalbran
Sent: Thursday, October 11, 2018 4:36 AM
Subject: (External):Re: ISPF issue - new system
I think that the ISPF startup will automativally allocate a clean ISPF profile if none exists? It does here.
So rename your ISPF profile at the READY prompt, then start ISPF and copy+replace back from the original (if needs be)?
From: IBM Mainframe Discussion List <IBM-***@LISTSERV.UA.EDU> on behalf of Lizette Koehler <***@MINDSPRING.COM>
Sent: 05 October 2018 19:08
Subject: Re: ISPF issue - new system
How do you create your ISPF Profile Dataset?
Do you have a REXX/CLIST for your TSO Logon proc that allocates the files needed for TSO/ISPF?
You might be able to tailor that to not use SMS.
Post by Chuck Kreiter
Behalf Of Vinoth M
Sent: Friday, October 05, 2018 10:18 AM
Subject: ISPF issue - new system
We have build a new system and we are bringing this system without SMS
We got the VTAM, TSO, TCPIP up and we are ready to login TSO, when we
login to TSO, the ISPF profiles are not getting allocated, since it’s
pointing to SMS dataset but we have disabled SMS.
May I know, where to change the SMS stuffs to NON-SMS volume, do I no
to change in parmlibs or any other procs, please let me know.
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN