Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Facilidade de uso
Cross-System
Connectivity
With
ALLBASE/NET,
dissimilar
HP
systems
can
b e
connected.
This
is
called
cross-system
connectivity
.
The
clien
t
and
serv
er
can
b e
an
y
com
bination
of
HP
3000
Series
900s,
or
HP
9000
Series
700s/800s.
Ho
w
ev
er,
the
G.0
v
ersion
of
ALLBASE/SQL
do es
not
supp ort
the
HP
9000
Series
300/400
as
a
serv
er;
it
can
b e
used
as
a
clien
t.
If
y
ou
are
dev
eloping
applications
that
do
dynamic
queries,
do
not
assume
that
y
ou
kno
w
the
format
of
fetc
hed
data.
The
format
array
,
as
describ ed
in
the
applicable
ALLBASE/SQL
application
programmer's
guide,
should
alw
a
ys
b e
used
to
parse
dynamically
fetc
hed
data
buers
to
a
v
oid
erroneous
assumptions
ab out
data
alignmen
t
on
remote
systems.
MPE/iX
and
HP-UX
Syntax
Differences
There
are
some
dierences
in
the
syn
tax
of
DBEn
vironmen
t
names
and
login
names
b et
w
een
MPE/iX
and
HP-UX
systems.
These
dierences
are
discussed
in
the
\Setting
Up
ALLBASE/NET"
and
\NETUtil
Reference"
c
hapters.
Client
and
Serv
er
Login
Names
ALLBASE/NET
do es
not
require
that
clien
t
and
serv
er
login
names
m
ust
b e
iden
tical.
Ho
w
ev
er,
under
certain
circumstances,
iden
tical
clien
t
and
serv
er
login
names
are
recommended.
The
following
guidelines
for
handling
these
names
are
divided
in
to
four
parts
to
address
the
needs
of
the
sp ecic
users
of
ALLBASE/NET
and
ALLBASE/SQL.
ALLBASE/NET
System
Administrators
As
system
administrator
on
the
serv
er,
y
ou
are
resp onsible
for
assigning
a
v
alid
serv
er
login
name
to
the
clien
t
who
will
b e
accessing
the
DBEn
vironmen
t.
That
clien
t's
login
name
is
then
mapp ed
to
the
serv
er
login
name
in
the
NETUsers
le.
When
p ossible,
it
is
recommended
that
the
clien
t
and
serv
er
login
names
b e
the
same.
This
is
a
precautionary
measure
to
a
v
oid
authorization
and
o
wnership
problems
that
arise
during
prepro cessing
and
execution
of
certain
application
programs
(suc
h
as
ALLBASE/Query).
Suc
h
programs
make
the
erroneous
assumption
that
the
DBEUserID
is
based
on
the
clien
t
login
name.
This
assumption
is
true
in
a
lo
cal
en
vironmen
t,
but
in
a
remote
en
vironmen
t,
the
DBEUserID
is
dened
b
y
the
serv
er
login
name
sp ecied
in
the
NETUsers
le.
If
the
serv
er
login
name
is
dieren
t
from
the
clien
t
login
name,
y
ou
may
receiv
e
an
error
message
ab out
an
in
v
alid
authorization
or
a
nonexisten
t
ob
ject.
In
some
cases,
suc
h
as
in
HP-UX
to
MPE/iX
connections,
it
is
imp ossible
to
ha
v
e
iden
tical
clien
t
and
serv
er
login
names.
In
this
case,
y
ou
should
make
sure
that
the
database
administrator
is
a
w
are
of
the
dierence
in
the
clien
t
and
serv
er
login
names.
(In
man
y
cases,
y
ou
are
also
the
database
administrator.
If
so,
see
the
recommendations
b elow
for
database
administrators.)
ALLBASE/SQL
Database
Administrators
As
database
administrator
on
the
serv
er,
y
ou
need
to
b e
a
w
are
that
some
of
y
our
remote
clien
t
users
may
ha
v
e
clien
t
login
names
that
are
mapp ed
to
dieren
t
serv
er
login
names.
In
suc
h
cases,
y
ou
might
w
an
t
to
take
some
precautionary
measures
to
a
v
oid
problems
with
ALLBASE/SQL
ob
ject
o
wnership
and
authorizations.
1-6
Getting
Started
... Este manual também é adequado para os modelos :
Software - MPE/iX 6.5 Operating System (329.65 kb)
Software - MPE/iX 7.0 Operating System (329.65 kb)
Software - MPE/iX 7.5 Operating System (329.65 kb)