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 On Thursday, October 11, 2018, Jesse 1 Robinson <jesse1.robin...@sce.com> wrote: > 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 > robin...@sce.com > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Edward Finnell > Sent: Thursday, October 11, 2018 10:06 AM > To: IBM-MAIN@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, > jesse1.robin...@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 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
