Discussion:
ISPF issue - new system
(too old to reply)
Vinoth M
2018-10-05 17:18:36 UTC
Permalink
Hi All,

We have build a new system and we are bringing this system without SMS
configuration.
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.

Thanks

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Chuck Kreiter
2018-10-05 17:44:36 UTC
Permalink
You will probably need to put something in VATLSTxx. Read the init and tuning guide for that parmlib member.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Vinoth M
Sent: Friday, October 5, 2018 1:18 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: ISPF issue - new system

Hi All,

We have build a new system and we are bringing this system without SMS configuration.
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.

Thanks

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
John Eells
2018-10-05 18:16:21 UTC
Permalink
And, if memory serves, likely mount the volume as Storage, associate it
with an esoteric name in HCD, activate the configuration, and put the
esoteric name you chose into the TSO user profiles. But it's been a
long, long time...
Post by Chuck Kreiter
You will probably need to put something in VATLSTxx. Read the init and tuning guide for that parmlib member.
-----Original Message-----
Sent: Friday, October 5, 2018 1:18 PM
Subject: ISPF issue - new system
Hi All,
We have build a new system and we are bringing this system without SMS configuration.
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.
Thanks
----------------------------------------------------------------------
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
--
John Eells
IBM Poughkeepsie
***@us.ibm.com

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Peter
2018-10-05 18:15:28 UTC
Permalink
Is this a cloned LPAR ? Seems you have cloned the Control dataset too and
it is expecting the same behaviour.

What does

D SMS, ACTIVE says
Post by Vinoth M
Hi All,
We have build a new system and we are bringing this system without SMS
configuration.
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.
Thanks
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lizette Koehler
2018-10-05 19:08:39 UTC
Permalink
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.

Lizette
Post by Chuck Kreiter
-----Original Message-----
Vinoth M
Sent: Friday, October 05, 2018 10:18 AM
Subject: ISPF issue - new system
Hi All,
We have build a new system and we are bringing this system without SMS
configuration.
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.
Thanks
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Steve Coalbran
2018-10-11 11:36:42 UTC
Permalink
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
To: IBM-***@LISTSERV.UA.EDU
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.

Lizette
Post by Chuck Kreiter
-----Original Message-----
Vinoth M
Sent: Friday, October 05, 2018 10:18 AM
Subject: ISPF issue - new system
Hi All,
We have build a new system and we are bringing this system without SMS
configuration.
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.
Thanks
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Feller, Paul
2018-10-05 21:28:48 UTC
Permalink
Without SMS you will need to have DASD volumes mounted as PRIVATE/PUBLIC/STORAGE. I believe without the PUBLIC or STORAGE volumes you will have a hard time allocating new dataset or temp datasets. I would think any datasets that are cataloged should get found through the proper catalog search.

Thanks..

Paul Feller
AGT Mainframe Technical Support
***@transamerica.com

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Vinoth M
Sent: Friday, October 05, 2018 12:18 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: ISPF issue - new system

Hi All,

We have build a new system and we are bringing this system without SMS configuration.
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.

Thanks

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Anthony Thompson
2018-10-08 04:00:52 UTC
Permalink
As Paul said, you will need volumes mounted as PUBLIC in your VALTLST to be able to satisfy non-specific volume allocation requests in a non-SMS environment (which is likely what your ISPF initial EXEC is doing to pre-allocate new ISPF datasets).

Ant.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Feller, Paul
Sent: Saturday, 6 October 2018 6:59 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: Re: ISPF issue - new system

Without SMS you will need to have DASD volumes mounted as PRIVATE/PUBLIC/STORAGE. I believe without the PUBLIC or STORAGE volumes you will have a hard time allocating new dataset or temp datasets. I would think any datasets that are cataloged should get found through the proper catalog search.

Thanks..

Paul Feller
AGT Mainframe Technical Support
***@transamerica.com

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Vinoth M
Sent: Friday, October 05, 2018 12:18 PM
To: IBM-***@LISTSERV.UA.EDU
Subject: ISPF issue - new system

Hi All,

We have build a new system and we are bringing this system without SMS configuration.
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.

Thanks

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
zos reader
2018-10-08 14:09:35 UTC
Permalink
Thank All for your valuable inputs.

I did some analysis and I could see the Catalog is pointing to the other
system where we cloned and it’s CPUX and that’s the reason we couldn’t get
ISPF Profiles.
And also we need to change the rexx exec Procs to not point SMS.
Post by Anthony Thompson
As Paul said, you will need volumes mounted as PUBLIC in your VALTLST to
be able to satisfy non-specific volume allocation requests in a non-SMS
environment (which is likely what your ISPF initial EXEC is doing to
pre-allocate new ISPF datasets).
Ant.
-----Original Message-----
Behalf Of Feller, Paul
Sent: Saturday, 6 October 2018 6:59 AM
Subject: Re: ISPF issue - new system
Without SMS you will need to have DASD volumes mounted as
PRIVATE/PUBLIC/STORAGE. I believe without the PUBLIC or STORAGE volumes
you will have a hard time allocating new dataset or temp datasets. I would
think any datasets that are cataloged should get found through the proper
catalog search.
Thanks..
Paul Feller
AGT Mainframe Technical Support
-----Original Message-----
Sent: Friday, October 05, 2018 12:18 PM
Subject: ISPF issue - new system
Hi All,
We have build a new system and we are bringing this system without SMS configuration.
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.
Thanks
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Edward Finnell
2018-10-05 21:59:41 UTC
Permalink
The default for Mounts is PRIVATE. This is controlled in VATLSTxx.
To test you can Mount a storage volume and a public volume with the MOUNT command===>M 225,vol=(SL,TSO225),USE=STORAGE             ===>M 235,vol=(SL,TEMP01),USE=PUBLIC


In a message dated 10/5/2018 4:28:57 PM Central Standard Time, ***@TRANSAMERICA.COM writes:
I would think any datasets that are cataloged should get found through the proper catalog search.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Seymour J Metz
2018-10-09 18:49:35 UTC
Permalink
You need to have unit names matching your STC and TSO JCL and you need to define public and storage volumes in VATLSTxx matching your JCL and unit names.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List <IBM-***@listserv.ua.edu> on behalf of Vinoth M <***@GMAIL.COM>
Sent: Friday, October 5, 2018 1:18 PM
To: IBM-***@listserv.ua.edu
Subject: ISPF issue - new system

Hi All,

We have build a new system and we are bringing this system without SMS
configuration.
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.

Thanks

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jesse 1 Robinson
2018-10-11 15:47:30 UTC
Permalink
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.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
***@sce.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Steve Coalbran
Sent: Thursday, October 11, 2018 4:36 AM
To: IBM-***@LISTSERV.UA.EDU
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
To: IBM-***@LISTSERV.UA.EDU
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.

Lizette
Post by Chuck Kreiter
-----Original Message-----
Behalf Of Vinoth M
Sent: Friday, October 05, 2018 10:18 AM
Subject: ISPF issue - new system
Hi All,
We have build a new system and we are bringing this system without SMS
configuration.
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.
Thanks
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Edward Finnell
2018-10-11 17:06:18 UTC
Permalink
Ummm, bit more subtle. The default is &sysuid.ispf.ispprof. If it doesn't exist the logon EXEC creates one on a Storage Volume and loads the profile from ISPTLIB. Considerations for Esoterics and Security come into play too. W/O SMS Temp DSNs are assigned to PUBLIC.

In a message dated 10/11/2018 10:47:39 AM Central Standard Time, ***@SCE.COM writes:
There is no required DSN naming convention for the profile, hence no native facility to find an existing one.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Jesse 1 Robinson
2018-10-11 18:27:09 UTC
Permalink
Not sure what you mean by 'the logon EXEC'. That must be created/supplied by your shop. It's not native to ISPF.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
***@sce.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Edward Finnell
Sent: Thursday, October 11, 2018 10:06 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: (External):Re: ISPF issue - new system

Ummm, bit more subtle. The default is &sysuid.ispf.ispprof. If it doesn't exist the logon EXEC creates one on a Storage Volume and loads the profile from ISPTLIB. Considerations for Esoterics and Security come into play too. W/O SMS Temp DSNs are assigned to PUBLIC.

In a message dated 10/11/2018 10:47:39 AM Central Standard Time, ***@SCE.COM writes:
There is no required DSN naming convention for the profile, hence no native facility to find an existing one.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Vinoth M
2018-10-12 15:44:36 UTC
Permalink
Thanks all for your suggestion, the problem was with Catalog, pointing to
wrong catalog. And did some changes on VATLST and all looks good.

Thanks
Post by Jesse 1 Robinson
Not sure what you mean by 'the logon EXEC'. That must be created/supplied
by your shop. It's not native to ISPF.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
-----Original Message-----
Behalf Of Edward Finnell
Sent: Thursday, October 11, 2018 10:06 AM
Subject: (External):Re: ISPF issue - new system
Ummm, bit more subtle. The default is &sysuid.ispf.ispprof. If it doesn't
exist the logon EXEC creates one on a Storage Volume and loads the profile
from ISPTLIB. Considerations for Esoterics and Security come into play too.
W/O SMS Temp DSNs are assigned to PUBLIC.
In a message dated 10/11/2018 10:47:39 AM Central Standard Time,
There is no required DSN naming convention for the profile, hence no
native facility to find an existing one.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Loading...