Hi, Our NFS client comes up around 2 minutes after TCPIP is available, regardless of when it is started (it starts outside automation): TCPIP is available when we see the message EZAIN11I ALL TCPIP SERVICES FOR PROC TCPIP ARE AVAILABLE. I believe syslogd for us is a child of TCPIP as well, so syslogd up would be in a similar time position.
Best regards, David Tidy IS Technical Management/SAP-Mf Dow Benelux B.V. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of saurabh khandelwal Sent: 6 July 2012 10:08 To: [email protected] Subject: Re: NFS Client Start Delay Hello Walter, This might be a reason. I also feel that everything was waiting on the syslog daemon to start and due to a full file system (/usr/local/logs), as I mentioned in last email with logs. I am trying to read manual and checking in internet, if somebody else also have faced similar issue. Regards Saurabh On Fri, Jul 6, 2012 at 1:32 PM, Walter Marguccio <[email protected] > wrote: > Saurabh, > > I would investigate how long does it take for OMVS (or Unix System > Services) > to initialize and, if that takes too long, why. I would presume that the > NFS Client > cannot start if OMVS is not completely initialized. > > > 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 > -- Thanks & Regards Saurabh Khandelwal ---------------------------------------------------------------------- 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
