HP ALLBASE NET User Manual

900 Series HP 3000 Computer Systems

ALLBASE/NET

User's Guide

ABCDE

HP Part No. 36216-90031

Printed in U.S.A. 1994

Fourth Edition

E0494

The information contained in this document is sub ject to change

without notice.

Hewlett-Packard makes no warrantyofany kind with regard to this

material, including, but not limited to, the implied w

merchantability or tness for a particular purpose. Hewlett-P

shall not be liable for errors con

special, incidental or consequential damages in connection with the

furnishing or use of this material.

Hewlett-Packard assumes no responsibility for the use or reliability of

its software on equipment that is not furnished by Hewlett-Packard.

This document contains proprietary information which is protected

by copyright. All rights are reserved. Reproduction, adaptation, or

translation without prior written permission is prohibited, except as

allowed under the copyrightlaws.



Use, duplication, or disclosure by the U.S. Government is sub ject to

restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in

Technical Data and Computer Software clause at DFARS 252.227-7013

for DoD agencies, Computer Software Restricted Rights clause at FAR

52.227-19 for other agencies.

1988, 1990, 1992, 1993, 1994 by Hewlett-Packard Company

tained herein or for direct, indirect,

arranties of

ackard

Hewlett-Packard Company

3000 Hanover Street

Palo Alto, CA 94304 U.S.A.

Restricted Rights Legend

Printing History

The following table lists the prin

dates for each edition. The softw

at the time this documen

document. Therefore, do not expect a one-to-one corresp ondence bet

and document editions.

Edition Date Software Version

First Edition October 1988 30604A.12.05

Second Edition December 1990 30604A.30.00

Third Edition June 1992 36216-02A.F0.00

Fourth Edition April 1994 36216-02A.G0.00

twas issued. Many product releases do not require c

tings of this documen

are version indicates the version of the softw

t, together with the respectiv

ween product releases

e release

are product

hanges to the

iii

ALLBASE/SQL Manuals

Title Customer

Order Number

ALLBASE/NET User's Guide

ALLBASE/SQL Advanced Application Programming Guide

ALLBASE/SQL C Application Programming Guide

ALLBASE/SQL COBOL Application Programming Guide

ALLBASE/SQL Database Administration Guide

ALLBASE/SQL FORTRAN Application Programming Guide

ALLBASE/SQL Message Manual

ALLBASE Pascal Application Programming Guide

ALLBASE/SQL Performance and Monitoring Guidelines

ALLBASE/SQL Reference Manual

HP ALLBASE/QUERY User's Guide

HP PC API User's Guide for ALLBASE/SQL and IMA

GE/SQL

ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL

Up and Running with ALLBASE/SQL

Additional Resources

36216-90031

36216-90100

36216-90023

36216-90006

36216-90005

36216-90030

36216-90009

36216-90007

36216-90102

36216-90001

92534-90011

36216-90104

36216-90096

36389-90011

You may nd the following manuals helpful:

HP NewWave Oce: Information Access SQL/XL

HP NewWave Oce: Using Information Access PC

HP NewWave Access User's Guide

Getting Started with NS 3000/XL

HP AdvanceNet Specications Guide

HP 3000/iX Network Planning and Conguration Guide

NS 3000/XL Local Area Network Conguration Guide

NS 3000/XL Operations and MaintenanceReference Manual

NS 3000/XL Error Messages Reference Manual

Preface

The

ALLBASE/NET User's Guide

application on one MPE/iX or HP-UX system to access an ALLBASE/SQL DBEn

on another MPE/iX system or HP-UX system. This man

describes ALLBASE/NET, a product that allo

ual is written for the system

ws an

vironment

administrator who is using ALLBASE/NET on an MPE/iX system. He or she uses this guide

to understand how ALLBASE/NET works and to learn ho

maintain necessary les. In addition, portions of this guide will be of in

programmers and to users of ALLBASE/SQL DBEn

w to use the NETUtil utilit

yto

terest to application

vironments, particularly chapters 1, 3,

and 4.

In some HP documen

tation and in talking with HP 3000 users, y

ou will encounter references

to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All

programs written for MPE XL will run without c

to use MPE XL system documen

tation, although it may not refer to features added to the

operating system to support POSIX (for example, hierarc

hange under MPE/iX. You can continue

hical directories). This guide is

divided as follows:

Chapter 1, \Getting Started," pro

vides an overview of ALLBASE/NET and its componen

Chapter 2, \Setting Up ALLBASE/NET," contains step-by-step instructions for setting up

ALLBASE/NET on the client and the server.

Chapter 3, \Using ALLBASE/SQL Through ALLBASE/NET," describ es ho

w to use

ALLBASE/NET with various applications. It also discusses the ALLBASE preprocessors.

Chapter 4, \NETUtil Reference," describes the NETUtil commands and giv

es examples of

how they are used.

Appendix A is a list of ALLBASE/NET les.

The Glossary contains denitions of terms used in this man

ual.

ts.

What's New in this Release

The following table highlights the new or c

hanged functionality in this release, and sho

where each feature is documented.

New Features in ALLBASE/SQL Release G.0

Feature (Category) Description Documented in

Stored procedures

(Usability)

Provides additional stored

procedure functionality for

application programs. Allows

declaration of a procedure cursor

and fetching of multiple rows

within a procedure to applications.

ALLBASE/SQL Reference Manual

Statements" and \Using Procedures" in

\Constraints, Procedures and Rules;"

ALLBASE/SQL Advanced Application

Programming Guide

, \Using Procedures in

Application Programs."

New statement: ADVANCE.

Changed syntax: CLOSE,

CREATE PROCEDURE,

DECLARE CURSOR,

DESCRIBE, EXECUTE,

EXECUTE PROCEDURE,

FETCH, OPEN.

Case insensitivity

(Usability)

Adds an optional attribute to the

character and varchar type column

attributes of tables. Allows search

and compare of these columns in a

ALLBASE/SQL Reference Manual

\Comparison Predicate" in \Search

Conditions," CREATE TABLE in \SQL

Statements."

case insensitive manner. Four new

SQLCore data types are added.

Changed syntax: ALTER TABLE,

CREATE TABLE.

ws you

...

, \SQL

Support for 1023

columns

(Usability)

ISQL HELP

improvements

(Usability)

EXTRACT

command

(Usability)

Increases the maximum number of

columns per table or view to 1023.

Increases maximum sort columns

and parameters in a pro cedure to

1023.

Gives help for entire command

instead of only the verb.

Extracts modules from the

database and stores them in a

module le. Allows for creation of

a module le at any time based on

the current DBEnvironment

without preprocessing. New

command: EXTRACT. Changed

syntax: INSTALL.

ALLBASE/SQL Reference Manual

CREATE TABLE and CREATE VIEW in

\SQL Statements;"

Database Administration Guide

ALLBASE/SQL

\ALLBASE/SQL Limits" app endix.

ISQL Reference Manual for ALLBASE/SQL

and IMAGE/SQL

, HELP in \ISQL

Commands."

ISQL Reference Manual for ALLBASE/SQL

and IMAGE/SQL

, \Using Modules" in

\Using ISQL for Database Tasks,"

EXTRACT, INSTALL in \ISQL

Commands."

New Features in ALLBASE/SQL Release G.0 (continued)

Feature (Category) Description Documented in

New SQLGEN

GENERATE

parameters

(Usability)

Generates SQL statements

necessary to recreate modied

access plans for mo dule sections.

New syntax for GENERATE:

ALLBASE/SQL Database Administration

Guide

, \SQLGEN Commands" app endix.

DEFAULTSPACE,

MODOPTINFO, PARTITION,

PROCOPTINFO, SPACEAUTH.

Row level locking

(Usability)

Permits multiple transactions to

read and up date a table

concurrently because loc

king is

done at row level. Since the

transaction will obtain more loc

ALLBASE/SQL Reference Manual

\Concurrency Control through Locks and

Isolation Levels;"

Administration Guide

Row Level Lo cking" in \Physical Design."

ks,

ALLBASE/SQL Database

, \Eects of Page and

the benets must b e weighed

against the costs. (Previously

documented in an addendum after

F.0 release.)

Increased number

of users

(Usability)

Removes the limitation of 240

users supp orted by pseudotables.

(Maximum is system session

ALLBASE/SQL Database Administration

Guide

, \ALLBASE/SQL Limits" appendix.

limits: 2000 on HP-UX; 1700 on

MPE/iX.)

...

POSIX support

(Usability)

Application thread

support

(Performance,

Usability)

Improves application portability

across MPE/iX and HP-UX.

Enhances the ALLBASE/SQL

preprocessors to run under POSIX

(Portable Operating System

Interface) on MPE/iX.

Provides the use of threads in an

application. Allows

ALLBASE/SQL to be used in an

application threaded environment

on MPE/iX. Application threads

are light weight processes that

share some resources and last for

the duration of a transaction.

Threaded applications reduce the

overhead of context switching and

improve the performance of

OpenTP applications.

ALLBASE/SQL Advanced Application

Programming Guide

, \POSIX Preprocessor

Invocation" in \Using the Preprocessor."

ALLBASE/SQL Advanced Application

Programming Guide

, \Using the

Preprocessor."

vii

New Features in ALLBASE/SQL Release G.0 (continued)

Feature (Category) Description Documented in

High Availability Provides a collection of features to

keep systems available nonstop

including: Partial STORE and

RESTORE, Partial rollforward

recovery, DBEFiles in dierent

groups (MPE/iX), detaching and

ALLBASE/SQL Reference Manual

Statements;"

Administration Guide

ALLBASE/SQL Database

, \Maintaining a

Nonstop Production System" in

\Maintenance" chapter and \SQLUtil"

appendix.

attaching database ob jects,

CHECKPOINT host variable,

changing log les, console

messages logged to a le,

generating fewer log records by

using TRUNCATE TABLE to

delete rows, and new system

catalog information. See the

following features for new and

changed syntax.

Partial rollforward

recovery

(High Availability)

Supports partial rollforward

recovery through PARTIAL option

on SETUPRECOVERY. Used to

recover specic DBEFiles while

ALLBASE/SQL Database Administration

Guide

, \Backup and Recovery" chapter and

SETUPRECOVERYPARTIAL in

\SQLUtil" appendix.

allowing access to other DBEFiles.

Partial STORE

and RESTORE

(High Availability)

Gives more exibility in backup

and recovery strategies by allowing

partial store and restore of

ALLBASE/SQL Database Administration

Guide

, \Backup and Recovery" chapter and

\SQLUtil" appendix.

DBEFiles, DBEFileSets or

combinations of both. See \New

and changed SQLUtil commands

for increased availability" later in

this table.

...

, \SQL

DBEFile group

change on MPE/iX

(High Availability)

Detaching and

attaching database

objects

(High Availability)

viii

Manages DBEFiles so they can b e

placed in a particular group or on

a particular volume (MPE/iX).

Use either CREATE DBEFILE or

MOVEFILE.

Detaches or attaches a DBEFile or

DBEFileSet from the

DBEnvironment. This is useful for

data that is accessed infrequently

such as tables containing historical

data only. New SQLUtil

commands: DETACHFILE,

ATTACHFILE.

ALLBASE/SQL Reference Manual

CREATE DBEFile in \SQL Statements;"

ALLBASE/SQL Database Administration

Guide

, \Maintaining a Nonstop Production

System" in \Maintenance" chapter and

MOVEFILE in \SQLUtil" appendix.

ALLBASE/SQL Database Administration

Guide

, \Maintaining a Nonstop Production

System" in \Maintenance" chapter and

DETACHFILE, ATTACHFILE in

\SQLUtil" appendix.

New Features in ALLBASE/SQL Release G.0 (continued)

Feature (Category) Description Documented in

New and changed

SQLUtil

commands for

increased

availability

(High Availability)

Adds support for high a

vailability

and System Management

Intrinsics. Intended for non-stop,

continuously available operations.

New SQLUtil commands:

ATTACHFILE, CHANGELOG,

ALLBASE/SQL Database Administration

Guide

, \SQLUtil" app endix.

DETACHFILE, RESTORE

PARTIAL, STORE PARTIAL,

STOREINFO, STOREONLINE

PARTIAL, WRAPDBE.

Modied SQLUtil commands:

MOVEFILE, RESTORE,

RESTORELOG, SHOWDBE,

SETUPRECOVERY, STORE,

STORELOG, STOREONLINE.

List les on backup

device

(High Availability)

Log le

improvements

(High Availability)

Lists physical names of les stored

on backup device with new

SQLUtil command: STOREINFO.

Allows changing log les,

switching of console messages to a

le, and gives advance warning for

log full. Increased maximum size

of a single DBE log le to 4

gigabytes. A DBEnvironment can

have up to 34 log les congured.

ALLBASE/SQL Database Administration

Guide

, \Backup and Recovery" chapter and

STOREINFO in \SQLUtil" appendix.

ALLBASE/SQL Reference Manual

CHECKPOINT in \SQL Statements;"

ALLBASE/SQL Database Administration

Guide

, \Maintaining a Nonstop Production

System" in \Maintenance" chapter,

CHANGELOG in \SQLUtil" app endix, and

\ALLBASE/SQL Limits" app endix.

Changed syntax: CHECKPOINT.

New SQLUtil command:

CHANGELOG.

...

New SET

SESSION and SET

TRANSACTION

statements

(Standards,

Performance)

FIPS agger

(Standards)

Provides additional exibility and

improved performance. Allows

setting and changing transaction

and session attributes.

Meets Federal Information

Processing Standard (FIPS) 127.1

agger support. Flags

non-standard statementor

extension. Invoked with a agger

option in the preprocessor

command line or the SET

FLAGGER command in ISQL.

Updatability rules are dierent

when agger is invoked. New

syntax: DECLARE CURSOR,

WHENEVER. Changes to C and

COBOL host variable declaration.

ALLBASE/SQL Reference Manual

, SET

SESSION and SET TRANSACTION in

\SQL Statements."

ALLBASE/SQL Reference Manual

DECLARE CURSOR in \SQL Commands"

and \Standards Flagging Support"

appendix;

Application Programming Guide

ALLBASE/SQL Advanced

, \Flagging

Non-Standard SQL with the FIPS Flagger;"

ISQL Reference Manual for ALLBASE/SQL

and IMAGE/SQL

, SET in \ISQL

Commands."

New Features in ALLBASE/SQL Release G.0 (continued)

Feature (Category) Description Documented in

Optimizer

enhancement

(Performance)

Uses a more ecient algorithm

that signicantly reduces the time

to generate the access plan.

ALLBASE/SQL Performance and

Monitoring Guidelines

, \Optimization" in

\Basic Concepts in ALLBASE/SQL

Performance."

Access plan

modication

(Performance)

Syntax added to

disable access plan

optimization

(Performance,

Usability)

Application

Development

Concurrency

(Performance,

Usability)

Allows mo dication of access plans

for stored section to optimize

performance. View the plan with

SYSTEM.SETOPTINFO. New

statement: SETOPT.

Species that the optimization

information in the mo dule le is

not to be used. Changed syn

tax:

EXTRACT, INSTALL,

VALIDATE.

Provides enhancements to improve

preprocessing performance when

simultaneously accessed by

multiple users. Page or row level

locking on any system base table

and processing without storing

sections. See the related features

in this table.

New SQL parameter: SET

ALLBASE/SQL Reference Manual

SETOPT in \SQL Statements;"

ALLBASE/SQL Database Administration

Guide

, SYSTEM.SETOPINFO in \System

Catalog."

ALLBASE/SQL Reference Manual

VALIDATE in \SQL Statements;

Reference Manual for ALLBASE/SQL and

IMAGE/SQL

," EXTRACT, INSTALL in

\ISQL Commands."

ALLBASE/SQL Reference Manual

\Names" and \SQL Statements;"

ALLBASE/SQL Advanced Application

Programming Guide

Preprocessor;"

, \Using the

ISQL Reference Manual for

ALLBASE/SQL and IMAGE/SQL

Commands;"

Administration Guide

ALLBASE/SQL Database

, \Database Creation

and Security" and \System Catalog."

DEFAULT DBEFileSet. SQL

changed syntax: ALTER TABLE,

GRANT, REVOKE, UPDATE

STATISTICS. ISQL changed

syntax: INSTALL. Changed

SYSTEM and CATALOG view.

New STOREDSECT tables.

Special owners HPRDBSS and

STOREDSECT. Changed syntax

for Full Preprocessing Mo de.

...

ISQL

, \ISQL

System Catalog

tables

(Performance)

Preprocessors

(Performance)

Provides greater concurrency by

allowing users to specify table,

page, or row level locking of any

system table owned by

STOREDSECT through the

ALTER TABLE statement.

Allows optional specication of a

DBEFileSet for storage of sections.

Allows preprocessing without

storing sections in

DBEnvironment.

ALLBASE/SQL Reference Manual

\Names;"

Administration Guide

ALLBASE/SQL Database

, \System Catalog."

ALLBASE/SQL Advanced Application

Programming Guide

, \Using the

Preprocessor."

New Features in ALLBASE/SQL Release G.0 (continued)

Feature (Category) Description Documented in

I/O performance

improvement

(Performance)

Optimizes I/O for initial load,

index build, serial scans, internal

data restructuring, le activity,

ALLBASE/SQL Reference Manual

Statements."

pseudo mapped les and

temporary les. See the follo

wing

features for new and changed

syntax.

TRUNCATE

TABLE statement

(Performance)

Deletes all rows in a specied table

leaving its structure intact.

Indexes, views, default values,

ALLBASE/SQL Reference Manual

TRUNCATE TABLE in \SQL Statements."

constraints, rules dened on the

table, and all authorizations are

retained. TRUNCATE TABLE is

faster than the DELETE

statement and generates fewer

logs. New statement:

TRUNCATE TABLE.

New scans

(Performance)

Reads tables with a new parallel

sequential scan. The tables are

partitioned and les are read in a

ALLBASE/SQL Performance and

Monitoring Guidelines

, \Using Parallel Serial

Scans" in \Guidelines on Query Design."

round robin fashion to allow OS

prefetch to be more eective.

Allows the I/O for a serial scan to

spread across multiple disc drives.

...

, \SQL

Load performance

improvement

(Performance)

ISQL enhanced to

improve the

performance of

LOADs

(Performance)

Improves performance with new

SET and SET SESSION

attributes, a new binary search

algorithm, and deferred allo cation

of HASH pages. New attributes

for SET SESSION statement:

FILL, PARALLEL FILL.

Uses new parameters of the ISQL

SET command to set load buer

size and message rep orting.

Improves load performance.

Choose a procedure, command le,

or new ISQL command to set

constraints deferred, lo ck table

exclusively, and set row level DML

atomicity. Changed syntax: SET

(see the following feature).

ALLBASE/SQL Reference Manual

, SET

SESSION in \SQL Statements."

ISQL Reference Manual for ALLBASE/SQL

and IMAGE/SQL

, SET in \ISQL

Commands."

New Features in ALLBASE/SQL Release G.0 (continued)

Feature (Category) Description Documented in

Modied SET

options

(Performance)

Provides b etter performance for

LOADs and UNLOADs. Specify

buer size, status reporting for

LOAD/UNLOAD or exclusivelock

for data table. AUTOSAVE row

limit increased to 2147483647.

ISQL Reference Manual for ALLBASE/SQL

and IMAGE/SQL

Commands;"

, SET in \ISQL

ALLBASE/SQL Performance

and Monitoring Guidelines

Loads" in \Guidelines on Logical and

Physical Design."

New and changed SET options:

LOAD BUFFER, LOAD ECHO,

AUTOLOCK, AUTOSAVE.

SQLMON

(Tools)

Monitors the activityof

ALLBASE/SQL DBEnvironment.

ALLBASE/SQL Performance and

Monitoring Guidelines

,chapters 6-9.

Provides information on le

capacity,locking, I/O, logging,

tables, and indexes. Summarizes

activity for entire DBEnvironment

or focuses on individual sessions,

programs, or database

components. Provides read-only

information.

Audit

(Tools)

Provides a series of features to set

up an audit DBEnvironment

which generates audit log records

that you can analyze with the new

SQLAudit utility for securityor

ALLBASE/SQL Reference Manual

Statements;"

Administration Guide

ALLBASE/SQL Database

, \DBEnvironment

Conguration and Security" chapter and

\SQLAudit" app endix.

administration. Includes the

ability to set up partitions. See

ALLBASE/SQL Database

Administration Guide

for

SQLAudit commands. Modied

statements: ALTER TABLE,

CREATE TABLE, START DBE

NEW, START DBE NEWLOG.

New statements: CREATE

PARTITION, DROP

PARTITION, DISABLE AUDIT

LOGGING, ENABLE AUDIT

LOGGING, LOG COMMENT.

...

, \Initial Table

, \SQL

Wrapper

DBEnvironments

(Tools)

HP PC API is now

bundled with

ALLBASE/SQL.

xii

Creates a DBEnvironment to wrap

around the log les orphaned after

a hard crash of DBEnvironment.

New SQLUtil command:

WRAPDBE.

PC API is an application

programming interface that allows

tools written with either the

GUPTA or the ODBC interface to

access ALLBASE/SQL and

IMAGE/SQL from a PC.

ALLBASE/SQL Reference Manual

\Wrapper DBEnvironments" in \Using

ALLBASE/SQL;"

Administration Guide

ALLBASE/SQL Database

, WRAPDBE in

\SQLUtil."

HP PC API User's Guide for

ALLBASE/SQL and IMAGE/SQL

New Features in ALLBASE/SQL Release G.0 (continued)

Feature (Category) Description Documented in

Increased memory

for MPE/iX

(HP-UX shared

memory allocation

is unchanged)

(Performance)

Increases memory up to 50,000

data buer pages and 2,000 run

time control block pages. Increases

the limits signicantly allowing

allocation of enough data buer

pages to keep the entire

ALLBASE/SQL Reference Manual

STARTDBE, STARTDBE NEW, and

START DBE NEWLOG in \SQL

Statements;"

Administration Guide

ALLBASE/SQL Database

, \ALLBASE/SQL

Limits" app endix.

DBEnvironment in memory if

desired for performance.

ALLBASE/NET

enhancements

(Connectivity,

Performance)

Improves performance of

ALLBASE/NET, allo ws more

client connections on server

system, and reduces number of

ALLBASE/NET User's Guide

ALLBASE/NET."

programs on MPE/iX.

ALLBASE/NET

commands and

options for

MPE/iX

(Connectivity,

Usability)

Adds option ARPA. Adds option

NUMSERVERS to check status of

listeners and number of network

connections. Changed syntax:

ANSTART, ANSTAT, ANSTOP.

Changed NETUtil commands:

ALLBASE/NET User's Guide

ALLBASE/NET" and \NETUtil Reference."

ADD ALIAS, CHANGE ALIAS.

ALLBASE/NET

and NetWare

(Connectivity)

ALLBASE/NET listener for

NetWare nowworks with the 3.11

version of Novell's NetWare for

ALLBASE/NET User's Guide

ALLBASE/NET."

UNIX (HP NetWare/iX).

...

, \Setting up

Changed

restrictions for

executing NETUtil

commands for

MPE/iX

(Connectivity,

Usability)

ARPA is only

TCP/IP interface

for data

communication

through

ALLBASE/NET

beginning with

HP-UX 10.0

(Connectivity)

Adds SM or AM (in the specied

account) to MANAGER.SYS for

adding, changing, or deleting users

for MPE/iX.

Remote database access

applications that specify NS will

not work if the client and/or

server machine is an HP 9000

Series 700/800 running HP-UX

10.0 or greater. Server Node Name

entry must be changed from NS

node name to ARPA host name.

For the NETUsers le, the \Client

Node Name" must be changed

from the NS node name to the

ARPA host name. New NETUtil

commands: MIGRATE USER,

MIGRATE ALIAS.

ALLBASE/NET User's Guide

, \Setting up

ALLBASE/NET."

ALLBASE/NET User's Guide

, \Setting up

ALLBASE/NET" and \NETUtil Reference."

xiii

Conventions

UPPERCASE

In a syntax statement, commands and keywords are shown in

uppercase characters. The characters must be entered in the order

shown; however, you can enter the characters in either uppercase or

lowercase. For example:

COMMAND

can be entered as any of the following:

command Command COMMAND

It cannot, however, be en

tered as:

comm com_mand comamnd

italics

In a syntax statement or an example, a w

ord in italics represents a

parameter or argument that you must replace with the actual v

In the follo wing example, y

ou must replace

lename

with the name

alue.

of the le:

COMMAND

lename

punctuation In a syntax statement, punctuation characters (other than brackets,

braces, vertical bars, and ellipses) must be entered exactly as shown.

In the following example, the parentheses and colon must be entered:

(

lename

):(

lename

)

underlining Within an example that contains interactive dialog, user input and

user responses to prompts are indicated b

y underlining. In the

following example, yes is the user's response to the prompt:

{ }

[ ]

Do you want to continue? >> yes

In a syntax statement, braces enclose required elements. When

several elements are stacked within braces, you must select one. In

the following example, you must select eitherONor





COMMAND

OFF

In a syntax statement, brackets enclose optional elements. In the

following example,

COMMAND

OPTION

lename

can be omitted:

[OPTION]

When several elements are stacked within brackets, you can select

one or none of the elements. In the following example, you can select

OPTIONorparameter

COMMAND

lename

or neither. The elements cannot be repeated.





OPTION

parameter

xiv

Conventions (continued)

[

...

]

In a syntax statement, horizontal ellipses enclosed in brackets

indicate that you can repeatedly select the elemen

within the immediately preceding pair of brac

example b elow, you can select

instance of

parameter

][...]

parameter

must b e preceded b

t(s) that appear

kets or braces. In the

zero or more times. Eac

y a comma:

In the example b elo

parameter

[

...

In a syntax statement, horizontal ellipses enclosed in v

is repeated; no comma is used before the rst occurrence

parameter

indicate that you can select more than one elemen

w, you only use the comma as a delimiter if

][,...]

ertical bars

t within the

immediately preceding pair of brackets or braces. However, each

particular element can only be selected once. In the follo

example, you must select

A, AB, BA

,orB. The elements cannot be

wing

repeated.





...

... In an example, horizontal or vertical ellipses indicate where portions

of an example have been omitted.

In a syntax statement, the space symbol1shows a required blank.

In the following example,

parameter

and

parameter

must be

separated with a blank:

(

4 5

parameter

The symbol

RETURN

)1(

parameter

4 5

indicates a key on the keyboard. For example,

represents the carriage return key or

)

represents the

Shift

shift key.

CTRL

character

CTRL

character

indicates a control character. For example,

CTRL

means that you press the control key and the Y key simultaneously.

1. Getting Started

How ALLBASE/NET Works . . . . . . . . . . . . . . . . . . . . . . 1-2

ALLBASE/NET Congurations . . . . . . . . . . . . . . . . . . . . 1-3

Hardware and Software Requirements . . . . . . . . . . . . . . . . . . 1-3

The NETUtil Utility . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

The AliasDB and NETUsers Files .

Creating the AliasDB and NETUsers Files .

The Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Cross-System Connectivity . . . . . . . . . . . . . . . . . . . . . . . 1-6

MPE/iX and HP-UX Syntax Dierences . . . . . . . . . . . . . . . . 1-6

Client and Server Login Names . . . . . . . . . . . . . . . . . . . . 1-6

ALLBASE/NET System Administrators . . . . . . . . . . . . . . . 1-6

ALLBASE/SQL Database Administrators . . . . . . . . . . . . . . 1-6

ALLBASE/SQL Application Programmers . . . . . . . . . . . . . . 1-7

ALLBASE/SQL Application Users . . . . . . . . . . . . . . . . . 1-7

Native Language Support . . . . . . . . . . . . . . . . . . . . . . . 1-8

Gathering Your Data . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

2. Setting Up ALLBASE/NET

Using NETUtil to Migrate Proles Before Installing HP-UX 10.0

Migration Log File . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Server List File . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Using NETUtil . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Invoking NETUtil . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Special Control Characters . . . . . . . . . . . . . . . . . . . . . . 2-4

Setting Up ALLBASE/NET on the Client . . . . . . . . . . . . . . . . 2-4

Adding an Alias Prole . . . . . . . . . . . . . . . . . . . . . . . 2-5

Changing an Alias Prole . . . . . . . . . . . . . . . . . . . . . . 2-6

Deleting an Alias Prole . . . . . . . . . . . . . . . . . . . . . . . 2-6

Displaying an Alias Prole . . . . . . . . . . . . . . . . . . . . . . 2-7

Checking the Services File on the Client . . . . . . . . . . . . . . . . 2-7

Setting Up ALLBASE/NET on the Server . . . . . . . . . . . . . . . . 2-8

Maintaining the Listener on an MPE/iX Server . . . . . . . . . . . . . 2-8

Starting the Listener . . . . . . . . . . . . . . . . . . . . . . . 2-8

Stopping the Listener . . . . . . . . . . . . . . . . . . . . . . . 2-9

Checking the Status of the Listener . . . . . . . . . . . . . . . . . 2-10

Checking the Number of Processes For Each Listener . . . . . . . . . 2-12

Checking the Listener Log File . . . . . . . . . . . . . . . . . . . 2-12

Assigning a Server Login . . . . . . . . . . . . . . . . . . . . . . . 2-13

Session Names . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

. . . . . . . . . . . . . . . . . . 1-4

. . . . . . . . . . . . . . 1-5

. . . . . . 2-1

Contents-1

Adding a User Prole . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Changing a User Prole . . . . . . . . . . . . . . . . . . . . . . . 2-15

Deleting a User Prole .

Displaying a User Prole .

Checking the Services File on the Serv

Examples of Setting Up ALLBASE/NET

. . . . . . . . . . . . . . . . . . . . . . . 2-16

. . . . . . . . . . . . . . . . . . . . . . 2-16

er . . . . . . . . . . . . . . . . 2-17

. . . . . . . . . . . . . . . . 2-18

3. Using ALLBASE/SQL Through ALLBASE/NET

Using ALLBASE/ISQL . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Using the Prepro cessor . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Running an Application Program .

. . . . . . . . . . . . . . . . . . . 3-3

Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Using ALLBASE/Query . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Using ALLBASE/4GL . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Using Information Access SQL/XL . . . . . . . . . . . . . . . . . . . 3-4

Using PC-based Application Soft

Conditions for Connecting to a Remote DBEn

ware . . . . . . . . . . . . . . . . . . 3-5

vironment. . . . . . . . . . 3-5

4. NETUtil Reference

Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

ADD ALIAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

ADD USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

CHANGE ALIAS . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

CHANGE USER . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

DELETE ALIAS . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

DELETE USER . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

MIGRATE ALIAS . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

MIGRATE ALIAS BACKWARD . . . . . . . . . . . . . . . . . . . 4-23

MIGRATE USER . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

MIGRATE USER BACKWARD . . . . . . . . . . . . . . . . . . . 4-26

QUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

SET ECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28

SHOW ALIAS . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

SHOW USER . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

A. ALLBASE/NET File Names

Glossary

Index

Contents-2

Figures

1-1. Node as Client and Server . . . . . . . . . . . . . . . . . . . . . . 1-2

1-2. System Administrators Using NETUtil

2-1. Sample Proles in AliasDB and NETUsers Files

3-1. Connecting to a DBEn

vironment . . . . . . . . . . . . . . . . . . . 3-6

. . . . . . . . . . . . . . . . 1-4

. . . . . . . . . . . . 2-18

Tables

4-1. NETUtil Commands . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Contents-3

Getting Started

ALLBASE/NET is a database access product that pro

vides access to remote data as though it

were stored lo cally. It allows the user of an application on one MPE/iX or HP-UX system to

query and up date a database in an ALLBASE/SQL DBEn

HP-UX system. The remote DBEn

vironmentmust reside on either a HP 3000 Series 900 or a

HP 9000 Series 700/800. ALLBASE/SQL on the HP 3000 m

ALLBASE/SQL on the HP 9000 m

ust be Version A.03.00, or later.

vironment on another MPE/iX or

ust be Version A.12.0, or later.

The following applications can be used with ALLBASE/NET to access a remote

ALLBASE/SQL DBEnvironment:

ALLBASE/ISQL and ALLBASE Prepro cessors

HP 3000 Series 900, Version A.12.00 or later

HP 9000 Series 300/400, Version A.02.00 or later (client only)

HP 9000 Series 700/800, Version A.03.00 or later

User-written application programs developed with the following releases of ALLBASE/SQL:

HP 3000 Series 900, Version A.12.00 or later

HP 9000 Series 300/400, Version A.02.00 or later (client only)

HP 9000 Series 700/800, Version A.03.00 or later

ALLBASE/Query

Version B.01 or HP Visor, Version A.01.03 or later

ALLBASE/4GL

HP 3000 Series 900, Version B.00.00 or later

HP 9000 Series 300/400 (client only) and 700/800, Version B.01.00 or later

HP Information Access

Version A.05.01 or later

HP PC API, Version A.01.00 or later

Note

To determine the version of ALLBASE/SQL and ALLBASE/NET you are

using, type the

SQLVER.PUB.SYS

command at the system prompt.

Getting Started 1-1

ALLBASE/NET gives users the same SQL functionality pro

ALLBASE/SQL, with the following exceptions:

vided by the equivalentversion of

DBEnvironments cannot be created remotely

New log les cannot b e created remotely

Long column data types cannot be used remotely

The ALLBASE/SQL database administration utilities SQLUtil, SQLGEN, and SQLMigrate

cannot access a remote DBEn

How ALLBASE/NET Works

ALLBASE/NET uses a client/server architecture. The application runs on the clien

and the ALLBASE/SQL DBEnvironment resides on the server node. The clien

are connected by a LAN (Local Area Net

A server node for one application can also b e a clien

accesses another DBEnvironment. In the illustration below, No de B is the server no de for the

application on No de A, and it is also a clien

vironment.

tnode

t and server

work) or a WAN (Wide Area Network).

t node for another application that

t node when accessing Node C.

1-2 Getting Started

Figure 1-1. Node as Client and Server

ALLBASE/NET Configurations

The client and server systems can b e either an HP 3000 Series 900s running MPE/iX or an

HP 9000 Series 700s/800s running HP-UX. F

and MPE/iX platforms, ALLBASE/SQL m

systems. This conguration allows the user to create and main

develop programs on the clien

taswell as to access DBEn

or full client/server functionality on both HP-UX

ust be installed on both the clien

t and server

tain DBEnvironments and

vironments on the server.

Note

The ALLBASE/SQL server version must b e as new or new

er than the

ALLBASE/SQL clientversion.

Hardware and Software Requirements

ALLBASE/NET clients and servers must be connected by a LAN or a W

LAN or WAN provides all the necessary hardw

are and link softw

are to allow comm

AN (via X.25). The

unication

between machines.

(Network Services) and

ARPA services

(Advanced Research Pro jects Agency) are the

software interfaces that enable communication between machines on the same network using

the TCP/IP proto col.

Note

If you are using NS, the following products m

The HP-UX 10.0 release does not support NS.

ust be installed on your HP 3000 Series 900

system before you install ALLBASE/NET:

NS3000/XL Network Services

ThinLAN 3000/XL Link

DTC/X.25 XL Network Link

Note

If you are connecting to an HP 9000 system, refer to \Hardw

Requirements" in the \Getting Started" chapter of the

Systems ALLBASE/NET User's Guide.

are and Software

HP 9000 Computer

Getting Started 1-3

The NETUtil Utility

ALLBASE/NET provides the

and NETUsers les that are discussed belo

commands, their syntax, and how they are used, refer to the \NETUtil Reference" c

NETUtil

utility for creating and main

taining the AliasDB

w. For complete descriptions of all the NETUtil

hapter.

The AliasDB and NETUsers Files

For a user to connect to a remote DBEn

vironment, two les must exist: the AliasDB le and

the NETUsers le.

The

AliasDB le

remote DBEs) are contained in this le. The AliasDB le has an

alias name that corresponds to a DBEn

resides on the client. The names of the serv

vironment. The alias prole con

er's DBEnvironments (the

alias prole

for each

tains the following

information:

Alias name

Type of database managemen

that corresponds to a DBEn

t system being used on the serv

vironment on the server

er (ALLBASE/SQL)

Fully qualied le name of the DBEnvironment on the server

Node name of the server where the DBEnvironment is lo cated

Machine type of the server

Type of data communication interface used

The

NETUsers le

resides on the server. It contains a

user prole

for each user on the client

that has access to a DBEnvironment on the server. The user prole contains the follo wing

information:

Client node name

Client login name

Server login name for the client

You use the NETUtil utility on b oth the clien

t and the server to add proles to and maintain

the AliasDB and NETUsers les. Additionally, users of DBEnvironments can use NETUtil

to display the contents of the AliasDB le so that alias names of DBEn

vironments can be

checked or conrmed.

Figure 1-2. System Administrators Using NETUtil

1-4 Getting Started

Creating the AliasDB and NETUsers Files

After ALLBASE/SQL has been installed on both the clien

NETUsers les m

NETUsers le automatically creates the respectiv

ust be created using NETUtil. Adding the rst prole to the AliasDB or

e le. These proles allow specied users on

t and the serv

er, the AliasDB and

the client to access particular DBEnvironments on the server.

As system administrator on the clien

command to add an alias prole to the AliasDB le. ADD ALIAS prompts y

about the specic DBEn

vironment to be accessed. Use ADD ALIAS to add more alias proles

t, you invoke NETUtil and use the ADD ALIAS

ou for details

to the AliasDB le as needed.

As system administrator on the serv

command to add a user prole to the NETUsers le. ADD USER prompts y

about the specic user who will be accessing the remote DBEn

er, you invoke NETUtil and use the ADD USER

ou for details

vironment. Use ADD USER to

add more user proles to the NETUsers le as needed.

For step-by-step instructions to create the AliasDB and NETUsers les, refer to the \Setting

Up ALLBASE/NET" chapter.

The Listener

The listener on the server provides three functions:

It listens for connection requests.

It validates the server login name.

It sets up a direct communication line between the client and server.

The listener monitors a sp ecied datacomm port for an

it receives a request, it validates the server login name for the user on the clien

creates a database process for that user. The listener redirects comm

y incoming connection requests. When

t and then

unications so that the

user and the database process communicate directly with one another over the network. It

then resumes listening for more connection requests.

You manually start the listener on the server after ALLBASE/SQL has been installed. When

you stop running the listener, no further connection requests are accepted. Ho

wever, any

remote database activity that is already in progress will not be aected and will terminate

normally.

Listener and network status and errors are recorded in a listener log le

(HPDANSLG.PUB.SYS) that you can check in the event of problems with remote

access. The listener must not be running for this to work.

For instructions on starting and using the listener and an example of a listener log le, refer

to \Setting Up ALLBASE/NET on an MPE/iX Server" in the \Setting Up ALLBASE/NET"

chapter.

Getting Started 1-5

Cross-System Connectivity

With ALLBASE/NET, dissimilar HP systems can b e connected. This is called cross-system

connectivity.

The client and server can be an

y combination of HP 3000 Series 900s, or HP 9000 Series

700s/800s. However, the G.0 version of ALLBASE/SQL do es not support the HP 9000 Series

300/400 as a server; it can be used as a clien

If you are developing applications that do dynamic queries, do not assume that y

format of fetched data. The format array

application programmer's guide, should alw

buers to avoid erroneous assumptions about data alignmen

ou know the

, as described in the applicable ALLBASE/SQL

ays be used to parse dynamically fetc

hed data

t on remote systems.

MPE/iX and HP-UX Syntax Differences

There are some dierences in the syn

tax of DBEnvironment names and login names

between MPE/iX and HP-UX systems. These dierences are discussed in the \Setting Up

ALLBASE/NET" and \NETUtil Reference" c

hapters.

Client and Server Login Names

ALLBASE/NET does not require that client and server login names must be identical.

However, under certain circumstances, identical client and server login names are

recommended. The following guidelines for handling these names are divided into four parts

to address the needs of the specic users of ALLBASE/NET and ALLBASE/SQL.

ALLBASE/NET System Administrators

As system administrator on the server, you are resp onsible for assigning a v

alid server login

name to the client who will be accessing the DBEnvironment. That client's login name is then

mapped to the server login name in the NETUsers le.

When possible, it is recommended that the clien

t and server login names b e the same. This

is a precautionary measure to avoid authorization and ownership problems that arise during

preprocessing and execution of certain application programs (such as ALLBASE/Query).

Such programs make the erroneous assumption that the

vironment, but in a remote environment, the

DBEUserID is dened by the server login name specied in the NETUsers le. If the serv

DBEUserID

is based on the client

invalid authorization or a nonexistent ob ject.

In some cases, such as in HP-UX to MPE/iX connections, it is imp ossible to have identical

client and server login names. In this case, you should make sure that the database

administrator is aware of the dierence in the client and server login names. (In many cases,

you are also the database administrator. If so, see the recommendations below for database

administrators.)

ALLBASE/SQL Database Administrators

As database administrator on the server, you need to be aware that some of your remote

client users mayhave client login names that are mapped to dierent server login names.

In such cases, you mightwant to take some precautionary measures to avoid problems with

ALLBASE/SQL ob ject ownership and authorizations.

1-6 Getting Started

One recommendation is to create an authorization group and add the serv

(DBEUserID) to the group. Be sure to gran

Give the name of the group to the application users and dev

Encourage them to use this group as the o

ob jects that they o

wn.

t all the desired authorizations to this group.

elopers on the remote clien

wnership qualier when accessing and creating SQL

ALLBASE/SQL Application Programmers

er login name

If you are an application programmer on the clien

the data they are accessing can be mo

ved to a remote node without causing c

t, you should design your programs so that

hanges to the

programs. Here are some programming recommendations:

Do not assume that the DBEUserID is based on the clien

conguration using ALLBASE/NET, the DBEUserID is based on the serv

The server login name need not be the same as the clien

fully qualify an unqualied ob ject's o

an end user types the command

wner with the client's login name. For example, if

select * from tablename

to ALLBASE/SQL without prexing the table name with the clien

ALLBASE/SQL resolves unqualied ob ject o

wners.

t login name. In a remote access

er login name.

t login name. Therefore, do not

, pass the

tablename

directly

t's login name.

When preprocessing programs remotely, qualify the module owner to be the server login name

(DBEUserID) or a group name to which the server login name belongs. This is done b

the -o option in the preprocessor command. F

or example:

y using

psqlpas sampledb -i sample.sql -o serverlogin -d

ALLBASE/SQL Application Users

If you are a user of an application program, do not assume that the DBEUserID is based

on the client login name. In a remote access conguration using ALLBASE/NET, the

DBEUserID is based on the server login name. The server login name need not be the same

as the client login name. Therefore, do not fully qualify an unqualied ob ject's o

wner with

the client's login name. Talk to your database administrator about possibly creating a group

with your server login as a member. The group can be used to fully qualify ALLBASE/SQL

ob jects.

Some existing programs, such as ALLBASE/Query,may incorrectly assume that the client

and server login names are the same. If that is the case, remote access using ALLBASE/NET

mayhave restricted functionality unless the server login name can b e made the same as the

client login name, or the application is rewritten using the recommendations made abo

ve for

application programmers.

Getting Started 1-7

Native Language Support

ALLBASE/NET is lo calizable to a v

and 16-bit character sets. In MPE/iX, the default language is called

supported languages can be found b

The ALLBASE/NET utility, NETUtil, has native language supp ort for the follo

ariety of other languages, including languages using 8-bit

NATIVE-3000

. A list of

y running NLUTIL.PUB.SYS.

wing:

The alias name in the AliasDB le

The DBEnvironment name in the AliasDB le (HP-UX DBEn

vironments only)

Messages and prompts

Yes/no responses

Time and date formats

With the exception of the alias name, HP-UX DBEn

all NETUtil commands and responses m

ust be typed as ASCII c

vironment name, and yes/no responses,

haracters. All language sets

have ASCII as a subset.

The DBEnvironment name in the AliasDB le can contain 8-bit or 16-bit characters if the

DBEnvironment it denes resides on an HP-UX system. This is independen

system of the client system where the AliasDB le resides. F

or example, a NETUtil user

t of the op erating

on an MPE/iX system can enter a 16-bit character string for the DBEnvironment name if

the DBEnvironment being accessed resides on an HP-UX serv

on MPE/iX are restricted to ASCII c

haracters because MPE/iX does not support names

er. DBEnvironment names

containing 8-bit and 16-bit characters, whereas HP-UX does.

NETUtil does not prohibit users from en

tering 16-bit characters in node names, login

names, or DBEnvironment names. However, when the user attempts to connect to a remote

DBEnvironment from an ALLBASE/SQL application, the connection fails if the operating

system doesn't support 16-bit characters in node names.

To get localized messages, prompts, and y

es/no responses for NETUtil, you must have the

appropriate ALLBASE/SQL message catalog installed for the desired language. On MPE/iX,

set the job control word \NLUSERLANG" to the desired language number.

ALLBASE/NET has no eect on ALLBASE/SQL native language support. The server

process inherits the native language of its remote client process. The language of the

DBEnvironment itself is determined at create time b

y the \LANG"= option of the START

DBE NEW command, whichmust always be invoked lo cal to the server machine. The user's

native language and the language of the DBEnvironment should b e the same. For additional

information about ALLBASE/SQL native language support, refer to the

Reference Manual

ALLBASE/SQL

1-8 Getting Started

Gathering Your Data

Before you set up ALLBASE/NET, you need to gather the information about the clien

and/or server that y

If you are the system administrator on both the clien

ou will b e entering in the AliasDB and NETUsers les.

t and server, all the information y

need is readily available to you.

If you are the system administrator on

administrator on the other serv

er or client to obtain specic information. Y

provide that system administrator with information specic to y

As system administrator on the clien

only

the client or the server, contact the system

ou also need to

our client or server.

t, you need the follo wing information ab out the serv

er to

put in the AliasDB le:

Type of database managemen

Fully qualied lename of the DBEn

Node name of the serv

er where the DBEnvironment is located.

Machine type of the serv

t system being used on the serv

vironment on the server.

er.

Type of data communication used.

As system administrator or account manager of the account where the remote user will log on

to on the server, you need the following information about the client to put in the NETUsers

le and for assigning a server login to the client:

Client node name.

Client login name.

To obtain the host name used by the ARPAinterface, check the HOSTS.NET.SYS

le on MPE/iX. If the hosts le does not exist, c

RESLVCNF.NET.SYS. This le contains the names of the systems that ha

heck the domain name service le,

ve hosts les. To

obtain the no de name used by the NS interface, type the MPE/iX command NETCONTROL

STATUS. You need NM (Node Manager) capability to use this command. Node names are

dened through NMMGR on MPE/iX or through SAM on HP-UX.

Getting Started 1-9

If you specify ARPA as the datacomm t

set or change the local domain name, do the follo

1. Run the NMGR program:

:RUN NMMGR.PUB.SYS

2. Open the conguration le:

ype, the ARPA domain name must be sp ecied. T

wing:

OPEN CONFIG

3. Go to the NS screen:

[NS]

4. Type in the local domain name and sa

LocalDomainName

[SAVE DATA]

5. Exit:

[PRIOR SCREEN] [PRIOR SCREEN] [EXIT]

When you have obtained all the needed information, set up ALLBASE/NET using the

step-by-step instructions in the \Setting Up ALLBASE/NET" chapter.

ve it:

1-10 Getting Started

Setting Up ALLBASE/NET

This chapter provides you with pro cedures for setting up ALLBASE/NET on both the clien

and server. It explains how to:

Use NETUtil to migrate proles

before

HP-UX 10.0 is installed on a serv

er system.

Invoke and use NETUtil.

Set up ALLBASE/NET on the clien

Set up ALLBASE/NET on the serv

Before you begin setting up ALLBASE/NET, mak

running. To do this, type

NSCONTROL STATUS

er.

e sure your networking software is up and

at the system prompt. For more information on

this and other listener commands, refer to the section \Setting Up ALLBASE/NET on the

Server" in this chapter.

Using NETUtil to Migrate Profiles Before Installing HP-UX 10.0

If you are installing NETUtil for the rst time on y

our system or have no MPE/iX to

HP-UX ALLBASE/NET connections, you can skip this section, and go to the section \Using

NETUtil."

Warning

Cross-System Users: Do not upgrade to HP-UX 10.0 until G.0 is installed on

your MPE/iX system.

Beginning with HP-UX 10.0, ARPA Services will be the only v

and existing applications that run on the HP 9000 S700 or S800 clien

ALLBASE/NET. Therefore, you

must

change the alias proles in the AliasDB le on the

client and the user proles in the NETUsers le on the HP-UX serv

alid datacomm type for new

t and/or server through

er. You can use the

migration commands MIGRATE ALIAS and MIGRATE USER to change proles where the

client and/or server is an HP9000 S700 or S800 and the datacomm type is NS. You must have

SM capability or log on as MANAGER.SYS to use the migration commands.

The MIGRATE ALIAS command can be executed with either the automatic or manual

option. The automatic option changes

all

the alias proles. The manual option prompts you

for changes to each alias prole. Listed below are the requirements for executing MIGRATE

ALIAS for automatic migration on the HP 9000 S700 and S800. If the requirements are not

met, you can use the manual migration option of the MIGRATE ALIAS command.

1. Automatic migration must o ccur b efore HP-UX 10.0 is installed on client and/or server

machines. The implementation of the MIGRATE ALIAS command for the HP 9000 S700

and S800 will use NetIPC calls, and will require a connection to the server. If HP-UX 10.0

is installed on either client or server, the NetIPC calls won't exist.

Setting Up ALLBASE/NET 2-1

+ 65 hidden pages