For both 2.1 and 2.3 we have SUBSYS SUBNAME(TNF) /* IBM TCP/IP */
No problems on our side. I am curious about your SEZALOAD. You say that it's added to link list *after* NIP. Like all other PDSE libraries, we have it in PROGxx. That's particularly important for a subsystem that names an initialization routine; apparently not true in this case, but we did have some issues with startup of other tasks in 2.3 that we had not seen before. . . 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 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jake Anderson Sent: Thursday, November 15, 2018 10:34 AM To: [email protected] Subject: (External):Re: Question on TNF start up in V2R3 z/OS 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 <[email protected] 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 [email protected] with the message: INFO IBM-MAIN
