Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
manual abstract
Job
or
Session?
Ho
w
ev
er,
there
are
commands
and
some
sp ecial
programs
that
require
considerable
time
to
nish
executing.
During
the
time
that
a
command
or
program
is
executing,
y
our
terminal
is
una
v
ailable
to
y
ou.
It
could
b e
una
v
ailable
for
seconds,
or
ev
en
for
hours.
That
can
happ en
during
some
complex
system
administration
tasks,
suc
h
as
bac
king
up
y
our
les.
It
can
happ en,
to
o,
if
the
computer
is
using
all
of
its
resources
to
satisfy
the
needs
of
man
y
users.
A
t
suc
h
times,
it
is
only
natural
to
w
an
t
for
a
w
a
y
of
recapturing
the
use
of
y
our
terminal,
or
to
defer
the
execution
of
some
task
un
til
the
computer
is
able
to
dev
ote
a
larger
p ortion
of
its
resources
to
y
our
w
ork.
Jobs
answ
er
b oth
requiremen
ts
b
y
running
in
the
b
ackgr
ound
,
more
or
less
out
of
sight.
Indeed,
when
it
do es
execute,
y
our
job
will
claim
none
of
y
our
time,
nor
will
it
\steal"
y
our
terminal
from
y
ou.
While
a
job
is
running,
y
our
terminal
is
free
for
whatev
er
other
w
ork
y
ou
might
w
an
t
to
do.
Y
ou
can
ev
en
tell
a
job
when
to
run:
hours,
da
ys,
w
eeks,
mon
ths,
ev
en
as
m
uc
h
as
a
y
ear
from
no
w.
Y
ou
do
not
ha
v
e
to
b e
at
y
our
terminal
while
a
job
runs.
There
is
a
dra
wbac
k,
ho
w
ev
er.
A
session
is
called
\interactiv
e"
b ecause
y
ou
and
the
computer
are
engaged
in
a
\dialogue"|a
con
v
ersation
of
sorts|
during
whic
h
y
ou
can
issue
an
y
v
alid
command
and
see
the
results
almost
immediately
.
Y
ou
are
free
to
c
hange
y
our
mind,
mo
dify
a
command,
and
try
it
again.
If
the
command
or
program
that
y
ou
are
running
prompts
y
ou
to
pro
vide
more
information,
y
ou
can
en
ter
the
correct
resp onse
then
and
there.
Errors
that
o ccur
give
rise
to
error
messages
on
y
our
video
terminal
and
p ermit
y
ou
to
analyze
them
and
correct
an
y
mistak
es.
Jobs,
b
y
con
trast,
are
not
in
teractiv
e.
When
y
ou
send
a
job
to
the
computer
for
pro cessing,
y
our
abilit
y
to
in uence
the
job
is
usually
conned
to
susp ending
the
execution
of
the
job
( BREAKJOB
jobnumb
er
),
resuming
its
execution
( RESUMEJOB
jobnumb
er
),
or
terminating
the
job
( ABORTJOB
jobnumb
er
).
There
are
tec
hniques
for
designing
a
job
in
suc
h
a
w
a
y
that
the
job
will
stop
to
prompt
y
ou
for
more
information.
A
job
of
that
sort,
ho
w
ev
er,
requires
y
our
presence
at
the
terminal.
8-4
Command
Files
and
Jobs
...Other models in this manual:
Software - MPE/iX 6.5 Operating System (551.28 kb)