>Hi Chris, I read that. I know it's the TCPIP subsystem which starts >daemons specified in the AUTOLOG statement every x seconds, but I >don't know why SYSLOG complains there is another instance running, >that I don't see anywhere in the process list.
a) UNIX daemons usually fork() once or twice during startup. I don't know off hand if this applies to syslogd as well but would guess so. b) z/OS will slightly change a process' (MVS) jobname upon fork() (and non-local spawn()) when the original jobname is shorter than 8 characters: a digit between 1 and 9 will be appended. If both a) and b) apply, then the resulting syslogd process will run in a different address space with a *different* jobname than the one started by TCP/IP's autolog feature. It will then think the job died and will restart it. If this turns out to be your problem, try running syslogd with an 8 character jobname (i,e.PROC name). z/OS will then leave the jobname alone upon fork()/spawn(). -- Peter Hunkeler -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of IT Pro Sent: Montag, 8. Oktober 2012 13:43 To: [email protected] Subject: Re: syslogd: FSUM1229 syslogd is already active However, commenting out the line in the AUTOLOG stetament and starting SYSLOG from /etc/rc works like a charm. There must be something I'm missing, but I'm really flabbergasted anyways. On Mon, Oct 8, 2012 at 1:37 PM, Chris Mason <[email protected]> wrote: > 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 [email protected] with the message: INFO IBMTCP-L > > Chris Mason > > On Mon, 8 Oct 2012 11:31:17 +0200, IT Pro <[email protected]> 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 [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
