On Monday, 11/09/2009 at 04:21 EST, "Gentry, Stephen" <stephen.gen...@lafayettelife.com> wrote: > " A spool file can span spool volumes, and we need a way to identify the > volume where each piece of the file is located." > > That explains why VM fussed about some specific spool entries and not > others. Those specific entries must span volumes. > Question: if I would have entered a "GO" instead of "STOP", VM would > have reformatted/initialized the spool. During this process is that when > VM makes the association between pointers and slots, etc? > If this is true, then with future IPL's I won't get these messages > (providing I don't move volumes and slots around)? > John, thanks for the explanation.
CP complains if he cannot successfully locate all the metadata and data of all spool files pointed to by the warmstart area. If you say GO, CP will throw away all spool files that can't be reconstructed. He will then rewrite the warmstart area (not the spool). And you're right, once you say GO, you won't get those messages again. Once CP reads SYSTEM CONFIG, he knows what slot numbers are valid and what devices they represent. Alan Altmark z/VM Development IBM Endicott
