I had a similar problem with an exec when I went to 5.2. Apparently this
STORAGE info was dropped as it was
considered sort of meaningless or incorrect. No one, at that time, made a
recommendation
as to what to use instead, so I just removed the code. We used it for
display purposes and
STORAGE has always been bogus. They finally took it out.
The biggest conversion problem I've had, so far, in upgrading from
z/.VM 5.1 to z/VM 5.2 is the changes that were made to the IND command.
Not a show stopper. But it is going to take a while to rework the ind
user exp output. I
Not to imply that the STORAGE value is meaningful, but for that LOCATE
stage as-coded you really want STRLOCATE, not LOCATE.
E.g.
'PIPE CP IND LOAD',
'| STRlocate /STORAGE-/',
'| xlate - blank % blank',
'| specs w2 1',
'| var PctStorage'
You might want also to download PIPEDEMO
VDISKs reside in dataspaces owned by CP. So don't be surprized nothing is
reported by IND SPACE MAINT
Find a user with real dataspaces, such as DB2 or SFS
Kris,
IBM Belgium, VM customer support
