Hi, Ian.
'cp-owned' volumes are simply the DASD volumes in a VM system that contain CP-manged data
areas: page, spool, t-disk, warm start, checkpoint, and directory (I may have missed one
or two....). CP uses these areas for it's own purposes, hence, 'cp-owned'.
Ian S. Worthington wrote:
I'm slightly confused by the difference between a volume being cp_owned (which
I think it needs to be if its page, spool, disk, ...), and in the user_volume
list, which seems to be where it needs to be if its perm -- at least if I want
the system to attach it for me.
What's the difference I'm missing here?
i
--
DJ
V/Soft
z/VM and mainframe Linux expertise, training,
consulting, and software development
www.vsoft-software.com
