RE: Console revisted

Jim,

I'm a little confused.  Has this configuration ever worked?  Do you have
both twinaxial and Ops Console device descriptions lying around?

Perhaps if you closed your current console, verified that QAUTOCFG is
set on, vary off and delete any suspect console device descriptions,
then reconnect the console and see if it creates itself.  Assuming that
you've upgraded from V4Rx, then the console characteristics may have
changed.

I would also verify that the most recent Client Access service packs are
installed.

Regards,
Andy Nolen-Parkhouse

> On Behalf Of Jim Langston
> Sent: Monday, October 22, 2001 1:53 PM
> Subject: Console revisted
>
> V5R1 doesn't like me.
>
> I got the DST profile of QSECOFR set back to the default, and the Ops
> Console
> connects... and shows a black screen.  I tried a couple of times.
Okay,
> so
> I need
> to vary on the console.
>
> The device QCONSOLE doesn't vary on, details shows me QCTL vary on
failed.
> QCTL
> vary on failed because the IOP is already in use by CTL02 type *CTLD.
I
> vary off
> CTL02 which didn't have any active devices, just a DSP02 that wasn't
being
> used.
>
> I succeed in the command to vary on QCONSOLE, but the status shows me
as
> VARY ON PENDING, the same for QCTL.
>
> Still got a blank screen on the console.
>
> What magic do I need to do to get the console up now?
>
> Regards,
>
> Jim Langston