Hello,
After spending more time on this issue, I have realized that
this delay is because of syslog was consuming all spaced allocated to that.
So, I have deleted syslog file from /usr/local/logs. This
resolved my issue.
Thanks for help.
Regards
Saurabh
On Fri, Jul 6, 2012 at 9:14 PM, Skip Robinson <[email protected]>wrote:
> Delay cause seems to be crucial here. I haven't seen anyone comment on
> what I consider to be OP's unusual configuration. If I understand the
> original post, two out of three 'sysplex' members are parallel while the
> other is not. If that's so, then two members have access to coupling
> facility structures while the other has only CTC connections to the other
> two.
>
> In reading over the paragraph above, I think I must have misunderstood.
> Can you even run that way? We have several parallel sysplexes, one basic
> (no CF) sysplex, and some monoplexes. They are and I think must be
> entirely separate plexes. I would have thought that any nonparallel
> system in a complex must not attempt to share resources with an adjacent
> parallel sysplex. If that's true, then this is a two-system problem; the
> third system is irrelevant.
>
> Or am I being naïve?
>
> .
> .
> JO.Skip Robinson
> SCE Infrastructure Technology Services
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 626-302-7535 Office
> 323-715-0595 Mobile
> [email protected]
>
>
>
> From: Doug Henry <[email protected]>
> To: [email protected]
> Date: 07/06/2012 07:47 AM
> Subject: Re: NFS Client Start Delay
> Sent by: IBM Mainframe Discussion List <[email protected]>
>
>
>
> On Fri, 6 Jul 2012 07:35:27 +0530, saurabh khandelwal
> <[email protected]> wrote:
>
> >I started NFS client at 23.35.45 but it actually started at 00.10.15e.
> So,
> >it took more then 30 min to start. Not sure, why this is happening.
> >Is there any thing to do with parallel sysplex or something else.
> >
> >1) D OMVS,W
> >
> >BPXO063I 00.07.36 DISPLAY OMVS 142
> >OMVS 000E ETC/INIT WAIT OMVS=(05,FS)
>
> Hi Saurabh,
> Maybe you already know this but the BPXO0631I message shows the problem.
> You haven't finished your OMVS INIT.
> See: z/OS V1R13.0 UNIX System Services Planning
>
> 13.7.8 Diagnosing hangs during z/OS UNIX initialization
>
> Doug
>
>
> ----------------------------------------------------------------------
> 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
