Re: IPL times

[Colin Allinson]

I was not very clear. My timings are from pressing PF10 on the SAPL panel to the first line of the IPL sequence appearing on the console - so this excludes any time taken by spool initialisation.

The fact that you have a large config also and are not experiencing this problem gives me some hope of a resolution.

I am not sure how improperly terminated channels works with ESCON & FICON as there is no chaining involved but I will certainly check this out.

I will also try to search for a previous thread on this. Any ideas for a keyword?

Colin Allinson

Richard Schuh wrote:

> There was a thread about this problem not too long ago. We have a large
> number of dasd devices, too and do not have your problem. The 6 minute
> figure is about normal for us. A good deal of that time is during
> initialization after the ipl - spool (we have several thousand files in
> spool at any given time), SFS and VTAM are major offenders. I have
> configured many devices that are  z/OS only Offline_at_ipl, but none are
> ignored. I have specified 0000-FFFF as sensed and a large number of
> Offline_at_ipl ranges. There are many more offline than are online, but
> all are sensed.

> What you are describing as hangs could be the system waiting for channel
> time-out caused by improperly terminated channels. I don't know the
> timeout interval for the newer systems, but it used to be 7 seconds per
> device. The timeout would only occur for devices that are not present on
> a channel. If you check the prior thread, there are other suggestions.
> Probably you will find the answer there.