If you have a very small machine (under 20MSU) you are likely better off with
the old method. If you are larger then it doesn't really matter as they are
fairly equal in use.Whether or not you are running a monoplex is not really
relevant to whether one way is better than the other, but
Have you tried DELVOL OSSYB1 PRIMARY? (assuming it was a primary volume)
Brian
On Sun, 8 May 2022 at 02:39, Jake Anderson wrote:
> Hello Group
>
> We used to have a volume named OSSYB1 in ARCMDxx which I have removed
> already and DFHSM comes up successfully. After sometime DFHSM complains
>
Hello Group
We used to have a volume named OSSYB1 in ARCMDxx which I have removed
already and DFHSM comes up successfully. After sometime DFHSM complains
that the volume OSSYB1 is offline and it throws a WTOR to reply with a
valid device number to make it online.
Not sure why DFHSM doesn't say
On Sat, 7 May 2022 14:07:48 -0400, Phil Smith III wrote:
>...
>subcom mvs
> COMMAND SUBCOM NOT FOUND
>READY
>
Have you tried creating such a command processor?
copying IEFTR14 to STEPLIB(SUBCOM) or creating
a trivial SYSEXEC(SUBCOM) might suffice.
--
gil
Alan Altmark wrote, in part:
>I'm curious if you can issue EXECIO or SUBCOM at the TSO command line.
Well, of course you can issue it, but:
READY
subcom mvs
COMMAND SUBCOM NOT FOUND
READY
