Along those same lines, the TCPIP dependency on VTAM for startup should also be looked at.
<snip> Mark, You gave me just too good an opening for me not to exploit it... :-) I happen to be working on a project to reduce start-up times on z/OS and one of the things I've been looking at is the degree to which the JES impedes the start-up of other software. (And I am looking at USS and other system components that also get in the way). It seems to me that the problem is stated in reverse: what is really needed is for the JES to get out of the way of other software start-up to the extent possible. It seems silly for software to wait for the completion of all of JES start-up when it may only require a minor JES service that is up well before the completion of all of JES start-up. For that matter, some of the services offered by the JES (for historical reasons) perhaps ought to be operating system services which can be enabled earlier than JES start-up. And the start- up of various services -- which for various reasons have been serial -- perhaps ought to made parallel to the extent possible. >From what we can tell, we have ample resources (CPU, memory, channels) to come up much more quickly than we do but we're getting tied-up in various ways. I suspect that I've just thrown meat to the lions, and I look forward to further discussion on this topic. W. Kevin Kelley IBM POK Lab -- z/OS Core Technical Development </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
