Re: virtual optical not usable

[Jim Franz <franz9000@xxxxxxxxx>]

this has been resolved.
We don't know why the optical device (created by vendor) had a type = *OPT
I renamed their device to PERVRTOPTX and created a new one using *VRT  so
the system would determine it.

PERVRTOPT   632B          new created
PERVRTOPTX  *OPT        Virtual optical device - the original

was able to then load the catalog.

This message gave me the clue, with the Recovery statement

Message ID . . . . . . :   CPDBC13       Severity . . . . . . . :   40

Message type . . . . . :   Diagnostic

Date sent  . . . . . . :   01/02/20      Time sent  . . . . . . :
19:23:47


Message . . . . :   Device PERVRTOPT is not a virtual optical device.

Cause . . . . . :   The device you specified on the DEV parameter either
does
  not exist or is not a virtual optical device.  Only virtual optical
devices
  of type 632B are supported.

Recovery  . . . :   Either change the value specified on the DEV parameter
or
  use the CRTDEVOPT command specifying a value of *VRT for the RSRCNAME

  parameter, and then try the request again.



Jim

On Thu, Jan 2, 2020 at 6:32 PM midrange <franz9000@xxxxxxxxx> wrote:

> Trying to use image catalog.
>
> I can see OPTVRT03 resource name exists and is "Active". But attempts to
> use
>
> Result in vary on
>
> Message ID . . . . . . :   CPD26D6       Severity . . . . . . . :
> 40
>
>  Message type . . . . . :
> Diagnostic
>
>  Date sent  . . . . . . :   01/02/20      Time sent  . . . . . . :
> 18:29:41
>
>
>
>
>  Message . . . . :   Device resource name OPTVRT03 not
> found.
>
>  Cause . . . . . :   Device PERVRTOPT was not varied on because resource
> name
>
>    OPTVRT03 is not a valid resource name for device description PERVRTOPT
> in
>
>    the system resource manager data base.
>
>
>
> All are "Active"
>
>
>
> Device      Type
>
>  OPTVRT01    632B
>
>  OPTVRT03    632B
>
>  OPT01       632A
>
>
>
> V7R3  and recent ptfs
>
>
>
> Any ideas
>
>
>
> Jim