![IBM System i Manual Download Page 67](http://html.mh-extra.com/html/ibm/system-i/system-i_manual_607100067.webp)
If
no
device
is
acting
as
the
console
the
next
time
a
connection
is
made,
either
through
Operations
Console
or
the
emulator,
this
PC
will
become
the
console.
It
is
up
to
the
users
to
determine
whether
or
not
this
method
is
the
correct
way
to
manage
console
activities.
Multiple
remote
consoles
through
dial-up
support
connecting
to
the
same
local
console
directly
attached
to
the
system
In
this
environment,
only
one
remote
console
is
allowed
to
connect
to
the
local
console
at
a
time.
The
users
are
left
to
work
out
an
arrangement
in
which
another
remote
console
can
access
the
local
console.
If
this
is
needed
on
a
regular
basis
it
might
be
as
easy
as
assigning
a
time
period
in
which
each
remote
console
would
access
the
local
console.
When
the
time
is
up
for
the
first
remote,
it
would
release
control
and
disconnect.
The
next
remote
would
then
connect
at
its
assigned
time
and
request
control.
This
assumes
that
the
local
console
did
not
have
control
when
the
first
remote
got
control.
Switching
from
one
console
type
to
another
when
a
console
is
currently
available
If
you
know
in
advance
that
you
will
need
a
different
console
type,
you
can
use
the
current
console
to
make
the
changes
necessary
for
use
with
a
different
console.
If
the
hardware
resources
for
the
targeted
console
type
have
already
been
specified
and
configured
for
use
as
a
console,
making
the
change
may
be
as
simple
as
specifying
the
new
console
type
and
activating
the
associated
hardware
resource.
However,
if
hardware
used
for
the
targeted
console
type
will
require
allocation
or
configuration,
you
will
need
to
use
the
appropriate
information
in
Change
from
one
console
type
to
another
.
An
example
would
be
the
planned
loss
of
the
network
used
by
your
LAN-connected
console.
You
will
be
doing
some
infrastructure
changes
requiring
more
than
a
day.
You
also
have
the
console
cable
already
installed
between
the
server’s
asynchronous
communications
adapter
and
the
PC.
You
can
use
either
DST
or
SST
to
change
the
console
type
to
a
2
for
Operations
Console
(direct).
The
asynchronous
communications
adapter
will
not
be
active
at
this
time
since
the
console
type
is
set
for
LAN
so
you
would
have
to
manually
start
the
asynchronous
card
with
a
function
66
on
the
control
panel
or
remote
control
panel.
Once
the
communications
line
is
active
you
can
disconnect
the
LAN-connected
console
and
create
a
configuration
for
the
directly
attached
local
console,
if
a
configuration
doesn’t
already
exist,
and
start
a
connection.
To
switch
back
to
the
LAN-connected
console
you
would
only
have
to
use
the
directly
attached
console
to
enter
either
DST
or
SST
and
change
the
console
type
to
a
3,
disconnect
the
existing
console
and
restart
the
LAN-connected
console.
Since
the
hardware
resource
configuration
didn’t
change,
there
isn’t
a
need
for
further
changes.
You
could
deactivate
the
asynchronous
communications
adapter
manually
or
just
wait
until
the
next
IPL.
The
IPL
will
not
start
the
asynchronous
communications
adapter
because
the
console
type
is
now
set
for
LAN.
Note:
To
activate
the
new
console
without
an
IPL,
you
could
perform
the
console
service
function
of
65+21+21.
Once
the
console
type
has
been
updated,
performing
the
console
service
function
will
disconnect
the
current
console
and
restart
the
console
type
you
just
specified.
Related
tasks
These
instructions
apply
only
to
local
console
directly
attached
and
local
console
directly
attached
with
remote-support-enabled
configurations.
Use
these
instructions
to
manually
activate
the
asynchronous
communications
line
on
the
system.
These
instructions
apply
only
to
local
consoles
directly
attached
and
local
consoles
directly
attached
with
remote
support
enabled.
Use
these
instructions
to
manually
deactivate
the
asynchronous
communications
line
on
the
system.
Related
reference
Depending
on
how
your
console
connection
is
set
up,
you
can
change
to
a
different
console
type.
Operations
Console
59
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Summary of Contents for System i
Page 1: ...System i Connecting to System i Operations Console Version 5 Release 4 ...
Page 2: ......
Page 3: ...System i Connecting to System i Operations Console Version 5 Release 4 ...
Page 8: ...vi System i Connecting to System i Operations Console ...
Page 120: ...112 System i Connecting to System i Operations Console ...
Page 124: ...116 System i Connecting to System i Operations Console ...
Page 125: ......
Page 126: ... Printed in USA ...