SOLVED! In the TCPIP profile there was a line in the PORT section that was reserving port number 514 for SYSLOG, so:
1) I removed (commented out) that line reserving port 514, and 2) Commented out the line in /etc/rc that starts SYSLOG from Unix, and 3) Added the line that I'd previously commented out in the AUTOLOG section of TCPIP's profile to automatically start SYSLOG as a started task using a PROC, and 4) Used -i command-line option for SYSLOG to force SYSLOG run in local-mode only I think the main reason was 1) above: it seemed that OMVS was preventing SYSLOG from using that port. I don't know why that line reserving the port was there. Many thanks to all. Best regards, Aitor. On Tue, Oct 9, 2012 at 10:24 AM, IT Pro <[email protected]> wrote: > No, it doesn't make any sense. That's why I was asking in this forum. > There must be something that I'm missing... I'm racking my brains! :-( > > On Tue, Oct 9, 2012 at 9:18 AM, Walter Marguccio > <[email protected]> wrote: >>> From: IT Pro <[email protected]> >> >>> To: [email protected] >> >>> The result is that starting it from /etc/rc works, but letting TCPIP >>> start it using the AUTOLOG feature ends with the message "already active". >> >> but that doesn't make sense, does it ? >> Just curious . >> >> >> Walter Marguccio >> z/OS Systems Programmer >> BELENUS LOB Informatic GmbH >> Munich - Germany ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
