Lizette, Just one test, Can you add the IEFSSN entry dynamically and try starting TNF ? See if it comes up ?
On Thu 15 Nov, 2018, 9:48 PM Lizette Koehler <stars...@mindspring.com wrote: > Cross posted to TCPIP/IBMMAIN > > List - > > When I IPL z/OS V2.1 TNF comes up correctly. > > When I IPL z/OS V2.3 TNF fails to start. I get a message saying it is not > in > the IEFSSNxx - but it is the same IEFSSNxx member for 2.1 and 2.3. > > So has anyone run across this issue in 2.3? > > The message is: EZY6014E Node/Subsystem name in IEFSSNxx is not TNF > > The SEZALOAD is in the linklist (activated later in the IPL Process with > all of > our PDSE Linklst datasets) > > The TNF is in the IEFSSNxx member > > This is not making sense. With the exception of the level of z/OS it is > the > same at IPL time. > > Thanks > > > Lizette > A theory can never be proven, but it can be falsified. Karl Raimund Popper > > ---------------------------------------------------------------------- > 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
