Can't say how your EZAZSSI got started, but that task is as old as the hills. We start it at IPL time with System Automation. And before that with our predecessor automation product. It may not be necessary to start EZAZSSI explicitly; I'm not a network guy. But it's been SOP here for a long time.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mark Yuhas Sent: Monday, May 16, 2016 1:41 PM To: [email protected] Subject: (External):Questions about EZAZSSI I am preparing for the first IPL of z/OS 2.2. I was reviewing the COMMND00 PARMLIB member and found a start command for EZAZSSI. I am totally unfamiliar with this address space. I googled it and found that EZAZSSI starts the TNF & VMCF address spaces. I reviewed the log from Saturday night's IPL and found this associated message - 'EZY6043I TNF Start Initiated'. I looked up the message: Explanation: A TNF address space start was issued. System Action: EZAZSSI continues; start of TNF expected. Of course, a similar message was issued for VMCF. I check our PARMLIB concatenation and did not find a start command for EZAZSSI; and, I know the IPL procedure did not start EZAZSSI? So, how did EZAZSSI get started? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
