Richard Corak wrote:
Not exactly. Changing the contents of the CP_OWNED statement, including
deletion, affects only that statement. But that's not as simple as it
might appear.
Spool files can span CP_OWNED volumes, so if CP needs to fetch the next
record for the spool file by going to the volume at slot 'n', and there
isn't a slot 'n', or it's a different volume so the needed record isn't
there, you lose the spool file.
Deleting the statement for slot 'n' doesn't automatically affect any
other CP_OWNED volume, but can affect all your spool files, and could
mean that you have no object directory.
Richard Corak
This is generally considered a Bad Thing (tm, M. Stewart). Which is why I always like to
keep a copy of the USER DIRECT file someplace other than the VM system it applies too.
Makes recovering after an accident a bit easier.
--
DJ
V/Soft
z/VM and mainframe Linux expertise, training,
consulting, and software development
www.vsoft-software.com
