Gadi Find the name of the started task procedure which starts the IOASRV program as specified in the AUTOLOG statement list.
Now find the PORT statement list entry which refers to that name and locate the port number. Enter NETSTAT CONN and check the last number in the "Local Socket" column and the "State" column in the output. If this is an UDP port, does the port number show as state "UDP"? If this is a TCP port, does the port number show as state "listen"? If the port number does not show at all or, in the case of TCP, is not "listen", then you need to find out why the IOASRV program is failing to initialise or failing to stay active. If there are still problems, please post again and post the information I described above. Note that it is only because the procedure name is in the AUTOLOG statement list that the address space starts initially. It is because the relevant port is not found to be in the correct state that the address space is cancelled and restarted subsequently. Chris Mason On Sun, 15 Mar 2009 14:19:33 +0200, גדי &#1489;ן אבי <gad...@malam.com> wrote: >HI, > >We just cut over to z/OS 1.9. > >Since the cutover, the TCP/IP Started task keeps cancelling OSA/SFs Started task IOASRV. > >Since IOASRV is in TCP/IPs AUTOLOG section, it is restarted each time. > >This happens about every five minutes. > >Ive reviewd the OSA/SF installation procedure, I cannot find anything Ive missed. > >Can anyone help? > >Gadi ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
