No Ravi, I made sure there was no address space, neither in the SDSF
DA display nor in the PS screen.
But I already found out the root cause which you may read in one of my
previous posts.
Kind regards,
Aitor.
On Fri, Oct 12, 2012 at 7:09 AM, Ravi Gaur gaur.ravi2...@gmail.com wrote:
Did you
The least I could do was post the solution here.
Regards.
On Thu, Oct 11, 2012 at 12:10 PM, IT Pro bilit...@gmail.com wrote:
I completely agree, Peter.
Thanks for your understanding.
Aitor.
On Wed, Oct 10, 2012 at 10:36 AM, Hunkeler Peter (KIUP 4)
peter.hunke...@credit-suisse.com wrote
Oh, well, I don't know whether this deserves opening an APAR. The
message is indeed quite misleading, but the thing is that once the
line in the section PORT of TCPIP's profile was corrected to match the
actual procedure name (that is, removing the leading 1), SYSLOG
started successfully and
obey (this doesn't mean IBM does not
deserve getting warned about this to correct the manual).
Regards,
Aitor.
On Wed, Oct 10, 2012 at 9:02 AM, IT Pro bilit...@gmail.com wrote:
Oh, well, I don't know whether this deserves opening an APAR. The
message is indeed quite misleading, but the thing
two different places. 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.
On Mon, Oct 8, 2012 at 5:49 PM, Mark Zelden m...@mzelden.com wrote:
On Mon, 8 Oct 2012 16:31:39 +0200, IT Pro bilit...@gmail.com 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
walter_marguc...@yahoo.com wrote:
From: IT Pro bilit...@gmail.com
To: IBM-MAIN@LISTSERV.UA.EDU
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 bilit...@gmail.com 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
to.
Thanks again for your support.
Regards,
Aitor.
On Tue, Oct 9, 2012 at 11:00 AM, IT Pro bilit...@gmail.com wrote:
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
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
Hi John, yes I've read there are several ways, but we want the syslog
be configured as a PROC so that it's easier for Operations to deal
with its management. They don't want anything dealing with Unix.
Anyways, I'll give that possibility a try.
Thanks a lot.
Aitor.
On Mon, Oct 8, 2012 at 11:50
in /etc/inetd.conf. You can comment that out by
putting a # to the left of the startup line.
Thanks.
John Eatherly
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of IT Pro
Sent: Monday, October 08, 2012 4:59 AM
To: IBM-MAIN
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
walter_marguc...@yahoo.com wrote:
From: IT Pro bilit...@gmail.com
Subject: Re: syslogd: FSUM1229 syslogd is already active
but I don't know why SYSLOG complains there is another instance running,
that I don't see anywhere in the process list.
what does command D A,SYSL* show ?
Walter Marguccio
Patrick, in the output of D OMVS,A=ALL does not appear anywhere syslogd
On Mon, Oct 8, 2012 at 2:55 PM, Patrick Loftus patrick.lof...@tnt.com wrote:
Do you have CA Common Services? That fires up SYSLOGD if it isn't already
running, but under a taskname of (by default) something like TNGEMSTR.
+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
@LISTSERV.UA.EDU]
On
Behalf Of IT Pro
Sent: Montag, 8. Oktober 2012 13:43
To: IBM-MAIN@LISTSERV.UA.EDU
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
16 matches
Mail list logo
