Why not always imbed the MOUNT in a PIPE? I've got lots of code like this
'PIPE COMMAND CMDCALL someSFScmd',
'|VAR EMSG |DROP', /* take emsg/remove header */
'|...analyze the response ....
if rc<>0 then do
inform enduser 'Command xyz failed:' emsg
.....
The CMDCALL is typical for CMS commands, it assures an errormessage is
generated, even when executing the command in "address command" mode.
2009/3/30 Schuh, Richard <[email protected]>:
> Is there documentation, in one place, of the possible non-zero return codes
> from a VMTAPE MOUNT command, or is it necessary to use a PIPE to trap the
> return code and message? I have a service machine that needs to mount tapes
> and perform functions for many users. It would be nice for the server to be
> able to tell a user that a request failed because an input tape could not be
> mounted, and be able to say why the mount failed.
>
> The VM:Tape Messages and Codes manual appears to have the information,
> however, the user messages are intermingled with the system and operator
> messages. Furthermore, the message numbers do not match the return codes.
> For example, if a MOUNT command is entered with an invalid virtual address,
> the message number is 44, but the return code is 24.
>
> The mount requests will succeed most of the time. I suppose that I could
> request the mount using a simple command and, if the return code is
> non-zero, reissue it in a pipe to trap the response. However, that seems a
> bit hokey.
>
>
> Regards,
> Richard Schuh
>
--
Kris Buelens,
IBM Belgium, VM customer support
