Aitor > The start of the syslog is specified in the "AUTOLOG" of the TCPIP > configuration.
Try reading in z/OS Communications Server IP Configuration Reference what the AUTOLOG statement in the PROFILE of the IP component of z/OS Communications Server does: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/2.8 <quote> 2.8 AUTOLOG statement Use the AUTOLOG statement to provide a list of MVS started procedures to be started by the Autolog task when TCP/IP is started. ... </quote> Yes I know this is the V1R13 manual but AUTOLOG hasn't changed since its invention in the early 1990s. Incidentally it is likely that the greatest concentration of specialists with in fact both the SNA (VTAM) as well as the IP components of z/OS Communications Server can be found here: For IBMTCP-L subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO IBMTCP-L Chris Mason On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro <bilit...@gmail.com> wrote: >Hello, > >We upgraded from z/OS 1.9 to z/OS 1.12 a few months ago. > >We have configured SYSLOGD daemon to be started as a started task from >a PROC, but when started we see in the MVS log "syslogd: FSUM1229 >syslogd is already active", and the procedure ends. The start of the >syslog is specified in the "AUTOLOG" of the TCPIP configuration. > >S SYSLOGT >$HASP100 SYSLOGT ON STCINRDR >$HASP373 SYSLOGT STARTED >IEF403I SYSLOGT - STARTED - TIME=11.27.08 >BPXF024I (USRFWKT) Oct 8 11:27:08 BOLSAWBD/USRFWKT SYSLOGT syslogd: >FSUM1229 syslogd is already active >IEF404I SYSLOGT - ENDED - TIME=11.27.08 >$HASP395 SYSLOGT ENDED > >Could anybody give me a hint on this? I'm stuck at this. >Thanks, >Aitor. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
