Although I know little about TCP/IP, I'd like represent the automation viewpoint. Although a task can be started in various ways, including (for some) an option in SSN or (for most) a command in SYS1.PARMLIB, only a task started by 'automation' (SA, for example), can be managed by automation for the life of the IPL. Starting a task is the easy part. Restarting it in the case of task failure or stopping it at system shutdown requires TLC from automation.
In theory an automation product could take ownership of task started outside of the product, but I have not seen one that does. So if you have an automation product, be wary of starting a task any other way. . . . 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 Mike Stayton Sent: Tuesday, May 17, 2016 3:59 AM To: [email protected] Subject: (External):Re: Questions about EZAZSSI From the IP Configuration Reference Step 3: Configure VMCF and TNF The Pascal socket interface uses the IUCV/VMCF services for a limited set of inter-address space communication flows. As a result, if you are using any applications (provided by IBM or others) that use the Pascal socket API, you must ensure that the Virtual Machine Communication Facility (VMCF) and Termination Notification Facility (TNF) subsystems are active before the applications are started. TCP/IP provides the following applications and commands that use the Pascal socket interface: o SMTP and LPD servers o TSO HOMETEST, LPQ, LPR, LPRM, LPRSET, TELNET, and TESTSITE commands Check the IEFSSNxx for statements starting the TNF and VMCF subsystems. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
