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.
On Monday, October 8, 2018, Anthony Thompson <anthony.thomp...@nt.gov.au> wrote: > 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-MAIN@LISTSERV.UA.EDU] On > Behalf Of Feller, Paul > Sent: Saturday, 6 October 2018 6:59 AM > To: IBM-MAIN@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 > paul.fel...@transamerica.com > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Vinoth M > Sent: Friday, October 05, 2018 12:18 PM > To: IBM-MAIN@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 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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
