Copyright (c) 1996-2005 StarQuest Ventures, Inc. [081505-NLV]

README.NLV

STARQUEST CLIENT ACCESS FOR UNIX(R) OS
Version 1.04.4

NOTICE: This document applies only if you are using translated
versions of Setup and Help. The sections below specify the
information that has changed since the translations were done.
[Note: English language (LANG=C, POSIX, or en_US) users have
updated Setup and Help files.]

**LANG Users (Non-English): More Installation Setup Instructions
**LANG Users (Non-English): REQUIRED Licensing Instructions
**LANG Users (Non-English): More Help

NOTE: See README for information on
*Installation Instructions
*API Documentation (HTML files)
*Known Problems


IMPORTANT NOTE:

The procedures for installing and licensing Client Access for UNIX have
changed since this note was written. Please refer to the other readme
files for current information. Please contact StarQuest Support if
there are any questions.

In addition, the NLV files may contain old company contact information.
The current company information is:


StarQuest Ventures, Inc.
PO Box 1076
Point Reyes Station, CA 94956
Telephone: 415-669-9619
FAX: 415-669-9629
Sales & support: [email protected]
URL: http://www.starquest.com




####################################################
**LANG Users (Non-English): More Installation Setup Instructions

********************
Topic: About Install
REVISED PROCEDURE:
-----------
Stop License Manager (before an update or re-install of Client Access
for UNIX OS)

Enter the following command at the UNIX command line prompt:

$STARLM/bin/lmdown -c $CA400/etc/conf/license.dat

********************
Topic: AIX, Solaris, and HP-UX Install Instructions
REVISED PROCEDURES INCLUDING STARQUEST LICENSE MANAGER INSTALLATION:
----------------------
AIX
X Window Install
----------------------
Start the installation at this point in Step 3:
Select all of the following in sequence from the 'System Maintenance
Interface Tool'("SMIT"):
'Software Installation and Maintenance'.
'Install and Update Software'
'Install/Update Selectable Software (Custom Install)'
'Install Software Products at Latest Level'
'Install New Software Products at Latest Level'
Step 4:
(For example, /tmp/caunix/pkg).

Step 5:
Click on the 'List' button next to '*SOFTWARE' to install' field.
Select 'n.n.n.n ca400 ALL @@ca400' from the 'Multi-select List'
dialog.

Install License Manager
After Step 6, repeat from Step 4.

Step 5:
Select '@ n.n.n.n StarQuest License Manager' from the 'Multi-select
List' dialog.

----------------------
AIX
Character-oriented Terminal Install
----------------------

Start the installation at this point in Step 2:
Select all of the following in sequence from the 'System Maintenance
Interface Tool'("SMIT"):
'Software Installation and Maintenance'.
'Install and Update Software'
'Install/Update Selectable Software (Custom Install)'
'Install Software Products at Latest Level'
'Install New Software Products at Latest Level'

Step 3:
(For example, /tmp/caunix/pkg).

Step 4:
In the '*SOFTWARE to install' field, type "ALL @@ca400" or press
the F4 key for a listing of installable software and select
"n.n.n.n ca400 ALL @@ca400".

Step 5:
After this step, install the License Manager.

Install License Manager
Repeat from Step 3.

Step 4:
In the '*SOFTWARE to install' field, type "StarQuest License Manager".

----------------------
SOLARIS
X Window Install
----------------------
Start the installation at Step 4.

Step 6:
For 'Mount Point' entry field: enter
/tmp/caunix/pkg

Step 7:
Select the following in 'Admintool: Add Software' to install
StarQuest Client Access:

'Software' field: select 'Client Access n.n.n.n'.
Click the 'Add' button. Product information appears.

At field 'Enter path to package base directory [?,q]', enter the
directory path where you want Client Access for UNIX OS installed
(example: /usr/local). (Note that the program can be installed in
any directory.)

Install License Manager

Repeat Step 7:
Select the following in 'Admintool: Add Software' to install
the StarQuest License Manager:
'Software' field: select 'StarQuest License Manager'.
Click the 'Add' button.

At field 'Enter path to package base directory [?q]', enter the
directory path where you want the StarQuest License Manager installed.

You see a series of messages "Processing...., Installing...." and then

Installation of was successful.
press to continue.

Select 'File' from the Menu Bar and then 'Exit'.

----------------------
SOLARIS
Character-oriented Terminal Install
----------------------
Step 1:
Enter this command and press Return:
pkgadd -d /tmp/caunix/pkg

NOTE: See man page for pkgadd for more information.

A list of available packages is displayed. Enter the number by
"CA400 Client Access nnnn" and press Return.

Step 2:
Messages appear and then "Enter path to package base directory[?, q]".
Enter the path where you want Client Access installed and
press Return.

Step 3:
You see a series of messages "Processing...., Installing...."
and then

Installation of was successful.
The following packages are available:
. . .
. . .

A list of available packages is displayed.

Install License Manager:
Step 4:
From the list of packages, enter the number by "StarQuest License
Manager" and press Return.

Step 5:
Messages appear and then "Enter path to package base directory
[?, q]".
Enter the path to the StarQuest License Manager and press Return.

Step 6:
You see a series of messages "Processing...., Installing...."
and then

Installation of was successful.
The following packages are available:
. . .
. . .

A list of available packages is displayed.

Enter "q" to quit and press Return.

Platform Install Complete

The platform installation is now complete. See the file
${CA400}/etc/base.tab for a list of files included in a complete
installation on your system.

----------------------
HP-UX
XWindow Install
----------------------
Start installation at Step 4:
Enter this source depot pathname: /tmp/caunix/pkg/CA400

Step 6: Complete this step but do not select Exit from the File Menu.

Install License Manager
Return to Step 4:
Select 'Actions' on menu bar and then 'Change source...'
In the 'Source Depot Path...' field enter this source depot
pathname:
/tmp/caunix/pkg/STARLM

Step 5:
Select 'STARLM'

Complete Steps 5, 6, and 7. The license manager is in directory
/opt/starlm.

----------------------
HP-UX
Character-oriented Install
----------------------
Start installation at Step 3:
Enter this source depot pathname: /tmp/caunix/pkg/CA400

Step 4:
Tab to the 'CA400...AS/400 Client Access' line and press
the Spacebar to highlight.

Step 5:
After you complete Step 5, install the License Manager.

Install License Manager
Return to Step 3:
Enter this source depot pathname: /tmp/caunix/pkg/STARLM

Step 4:
In the 'SD Install - Software Selection' window, tab to the
'StarQuest License Manager' line and press the Spacebar to
highlight.

Complete the installation through Step 6.
The License Manager is installed in /opt/STARLM.


********************
Topic: AIX, Solaris, and HP-UX Install Instructions
ADDED:
IMPORTANT!
-----------
Start Host Servers

The AS/400 host servers for all Client Access products that access AS/400
systems MUST BE RUNNING in order to run Client Access for UNIX OS.

After you install Client Access and anytime the AS/400 host servers are
disconnected, enter the following command on the AS/400 command line to
start the AS/400 host servers:

strhostsvr *all

See the "Required AS/400 Host Socket Servers" section of Troubleshooting
for more information.

********************
Topic: Set Environment Variables
CHANGED:
-----------
CA400
CA400 specifies the path to a fully-installed and configured Client Access
for UNIX OS software distribution.
AIX Example:
CA400= /usr/lpp/ca400
export CA400

Solaris and HP-UX Example:
CA400= /opt/ca400
export CA400

********************
Topic: Set Environment Variables
ADDED:
-----------
STARLM
Sets the path to a fully-installed StarQuest License Management package
which is required before Client Access for UNIX OS can run. Example:
STARLM=/opt/local/starlm
export STARLM

********************
Topic: Set Environment Variables
REVISED:
-----------
SHELL
SHELL defines ...
Example:
SHELL=/bin/sh [/bin/csh for C-Shell]
export SHELL

********************
Topic: Running the Program
ADDED:
-----------
NOTE: If you just installed the product and you are using the temporary
installation browser, exit from this temporary copy of the browser
(select 'Exit' from the browser 'File' menu) before running the Client
Access program.

Run StarQuest Client Access for UNIX OS using the following commands.

X Window: xcamenu

Character-oriented terminals: camenu

Select 'Help' from the Main Menu for on-line Help.

********************
Topic: Running the Program
CHANGED:
-----------
C shell (csh) users:

Step 1 Example:

DELETE:
setenv env_variable value

********************
Topic: AIX, Solaris, and HP-UX Deinstall Instructions
ADDED:
-----------
Deinstall StarQuest License Manager from your UNIX system.
(applies to X Window and Char.-oriented terminals)

1
Sign on as root:

Stop License Manager

Enter the following command to stop the License Manager daemon:

$STARLM/bin/lmdown -c $CA400/etc/conf/license.dat

NOTE: After the Deinstall is completed, any new installation requires
reinstalling the License Manager as described in 'Licensing Procedure'.

Remove Client Access for UNIX OS .signon File

Next, remove old .signon file from ${HOME}/.ca400 directory. Use this
UNIX command:

rm ${HOME}/.ca400/.signon

NOTE: To remove the License Manager file, repeat the steps above, selecting
the StarLM License Manager package.

********************
Topic: Troubleshooting
REVISED:
-----------
Stop License Managers and Remove .ca400 Directory

Before you install a new version or reinstall Client Access for UNIX OS, you
should stop the old license managers (lmgrd) and remove the .ca400 directory
from the ${HOME}directory.

Stop Old License Managers

Enter this command at the UNIX command line:
$STARLM/bin/lmdown -c $CA400/etc/conf/license.dat

********************
Topic: Troubleshooting
ADDED:
-----------
Restart the License Manager Daemon

You must restart the License Manager daemon after an Update or if your
system shuts down for any reason, the License Manager daemon will stop
running and must be restarted. See Licensing Procedure for information.

Required AS/400 Host Socket Servers

All required As/400 host socket servers must be connected and available to
successfully run Client Access for UNIX OS. Use the Client Access Shell
(CASH) command pingserver to verify that the eight necessary AS/400 host
socket servers are connected and available.

Command syntax:

pingserver file|central|netprt|signon||rmtcmd|dtaq|database|
Port Mapper host_server_name

If the host_server_name is not provided, the default is used. The default
server is the one last connected. Example: pingserver 449 myhost.ibm.com

These Host Socket Server numbers and/or names can be used with the
pingserver command:

Socket # Server Name
449 Port Mapper
8470 central
8471 database
8472 dtaq
8473 file
8474 netprt
8475 rmtcmd
8476 signon

####################################################
**LANG Users (Non-English): Required Licensing Instructions

You must complete the StarQuest License Manager installation described in
your platform installation section before proceeding.

Follow the instructions below to license your Client Access for UNIX OS
product:

About Licensing

Initial Product Licensing

Restarting the License Daemon

Changing your License

Technical Information

After you complete the licensing procedure, you will be able to run Client
Access for UNIX OS as described in "Running the Program".

ABOUT LICENSING

You must have a valid license issued by StarQuest in order to run StarQuest
Client Access for UNIX OS. StarQuest uses the FLEXlm license management
system to issue a valid "License Key" based on your purchase agreement. You
may use StarQuest Client Access for UNIX OS licensed software only in
accordance with the License Agreement provided with this product.

Client Access for UNIX OS can be installed on a server or on as many clients
as needed. Client Access will not run without the License Manager daemon.

The License Manager daemon allows 20 or more concurrent connections
depending on the license you have purchased. You may request a temporary
license for a 30-day trial period.

Direct inquiries about the product and license agreement to StarQuest
Sales at email: [email protected]

StarQuest License Manager is an installable package that runs the licensing
of your Client Access program by allowing 20 or more concurrent connections.

The License Manager user interface, StarQuest License Administration (lmadmin
in the $CA400/etc directory), displays your machine's Host ID number, lets
you license your program, and starts or restarts the License Manager daemon.

NOTE: Licensing your product enables you to run the License Manager
daemon. The License Manager daemon must be running in order to use
StarQuest Client Access for UNIX OS. If your system shuts down for
any reason, the daemon will stop running and must be restarted.

INITIAL PRODUCT LICENSING

The instructions below for initial licensing of your product apply to
purchased licenses and temporary licenses.

The licensing procedures described in this document assume the following:

* The Client Access package is completely installed on your system.

* You have completed unpackaging the StarQuest License Manager files.
(Selection 2 on the CLIENT ACCESS INSTALLATION MENU)

* You have root authority

Follow these steps to license Client Access for UNIX OS:

STEP 1: Make sure you have set STARLM License Manager
environment variable

STEP 2: Run StarQuest License Administration

STEP 3: Contact StarQuest with your machine's Host ID number

STEP 4: Obtain a License Key from StarQuest

STEP 5: License your Client Access package

STEP 6: Start the license daemon

#STEP 1: Make sure you have set STARLM License Manager
environment variable

You must set the StarQuest License Manager environment variable
(STARLM) as described in the "Set Environment Variables" section
of SETUP.

#STEP 2: Run StarQuest License Administration

At the UNIX prompt, change your directory:

$CA400/etc

Start StarQuest License Administration:

./lmadmin

Your StarQuest License Administration screen display:
__________________________________________________
StarQuest License Administration

Your machine's host ID is: 80327959

Call (510) 528-2900 to register by telephone.

Dial (510) 528-2986 to register via fax (facsimile device).

Use Internet address "[email protected]" to register via e-mail.

Do you wish to license the Client Access package (y/n)?

Do you wish to start the license manager daemon (y/n)?
___________________________________________________

#STEP 3: Contact StarQuest with your machine's Host ID number

The StarQuest License Administration screen displays your machine's Host
ID number.

StarQuest requires the following information:

Company name:

Contact name:

Contact information: (phone, FAX, email, address)

Host ID number: (displayed on License Administration screen)

Product name: "Client Access for UNIX OS"

Platform and version: (Solaris, AIX, or HP-UX)

License information: (number of concurrent connections)

NOTE: If you are not licensing your program at this time, you may exit
from License Administration by entering 'n' for both questions displayed
on the screen.

Report this information to StarQuest Customer Support as described in Step 4.

#STEP 4: Obtain a License Key from StarQuest

StarQuest issues you a License Key (20 digits) and a License expiration date
by phone, FAX, or email. Contact StarQuest Customer Support via email: [email protected]

>Temporary License Key by E-mail

To obtain a temporary License Key for a 30-day trial of Client Access
for UNIX with 20 concurrent connections, send e-mail to
[email protected] \

The format of the subject line:

subject:hostid: product: caunix

where host_id is the Host ID value displayed when you run the Client
Access for UNIX License Management application (./lmadmin).
In addition, please supply the following information in the body of
the message:
Company Name:
Contact Name:
Phone Number:
Operating System: (e.g., AIX 4.1.4,Solaris 2.5, 2.5.1;
HP-UX 10.10, 10.20)

Example: mail [email protected]
Subject: hostid: 80327959 product: caunix

Company Name: Sprockets Inc
Contact Name: John Doe
Phone Number: 510-555-1234
Operating System: AIX 4.1

When you receive your permanent or temporary License Key and License
expiration date from StarQuest, complete the licensing of your Client Access
for UNIX product.

NOTE: If necessary, rerun the License Manager as described above to
display the License Administration screen.

#STEP 5: License your Client Access Package

On the License Administration screen (see STEP 1), enter 'y' to this
question:

Do you wish to license the Client Access package (y/n)?

Enter your 20 digit License Key issued by StarQuest at this prompt:

Enter license key:

Enter the license expiration date in the format issued by StarQuest at this
prompt:

Enter the expiration date of your license:

#STEP 6: Start the license daemon

The license daemon must be running in order to run StarQuest Client Access
for UNIX.

Enter 'y' at the following prompt:

Do you wish to start the license manager daemon (y/n)?

This message appears on your screen and you are exited from License
Administration and returned to your UNIX prompt:

StarQuest license manager daemon started.

You are now ready to use Client Access. If you need to restart the License
Manager daemon or change your StarQuest license, continue to the next
sections.

*RESTARTING THE LICENSE DAEMON

When you Update or Deinstall Client Access, you must stop the License
Manager daemon. Also, if your system shuts down for any reason, the daemon
will stop running and must be restarted. You can use the command rc.ca400
to restart the license daemon or follow this procedure:

Start StarQuest License Administration (see STEP 1 above).

Enter 'n' to this question:

Do you wish to license the Client Access package (y/n)?

Enter 'y' to this question:

Do you wish to start the license manager daemon (y/n)?

This message appears on your screen and you are exited from License
Administration and returned to your UNIX prompt:

StarQuest license manager daemon started.

*CHANGING YOUR LICENSE

You may want to change your license from temporary to permanent or change
the number of concurrent connections allowed. When you change your license
for any reason, you must obtain a new License Key and License expiration
date, stop the current License Manager daemon, and then repeat the licensing
procedure described in "Initial Product Licensing" above.

Stop the License Manager daemon

Enter the following command at the UNIX command line prompt:

$STARLM/bin/lmdown -c $CA400/etc/conf/license.dat

Follow the Steps in "Initial Product Licensing" above.

Contact StarQuest with your current License Key value. StarQuest will
provide you with a new License Key and License expiration date. Contact
StarQuest Sales at email: [email protected]

*TECHNICAL INFORMATION

Technical information about licensing is available in the license man pages.

To view the UNIX-style manual pages, set this environment variable:

MANPATH=$STARLM/man
export MANPATH

For License Management utility functions and references to other license
management options, enter:

man lmutil

*LICENSING COMPLETED

When you have completed the steps above see Running the Program in Setup.


####################################################
**LANG Users (Non-English): More Help

********************
TOPIC NAME: Running the Program
-----------
Browser
Moving within a Topic:
Ctrl f - scroll forward
Ctrl b - scroll backward

********************
TOPIC NAME: Environment Variables
-----------
CA400
CA400 specifies the path to a fully-installed and configured Client Access
for UNIX OS software distribution.
AIX Example:
CA400=/usr/lpp/ca400
export CA400

Solaris and HP-UX Example:
CA400=/opt/ca400
export CA400

-----------
BROWSER
Specify the name of the browser you want to use to access on-line Help and
Setup. NOTE: Client Access for UNIX OS supplies a local browser
("cabrowser" for character-oriented terminals, "xcabrowser" for X
Window). However, you can specify any browser that reads .HTML files.

Local browser example (xcabrowser for X Window and cabrowser for
Character-oriented terminals):
BROWSER=browsername
export BROWSER

Commercial browser example:
BROWSER=browsername (example: BROWSER=netscape)
export BROWSER

********************
TOPIC NAME: Command Line Access
-----------
Server Manager
Character-oriented terminals:
casm

********************
TOPIC NAME: How to Print
-----------
Refer to the IBM AS/400 Service and Support web page "Remote Printing
with TCP/IP" for more information:

http://www.as400.ibm.com/service/400tcp/lpr.htm

********************
TOPIC NAME: Manual Pages
-----------
A complete list of the Client Access for UNIX OS man pages is in
${CA400}/man/cat1.

********************
TOPIC NAME: File Transfer User Interface
-----------
Binary or Text
The file is copied in binary or text
format.

********************
TOPIC NAME: File Transfer User Interface
-----------
Main Menu
View
- X Window: By Name, By Time, Reversed, Hidden Files

- char.-oriented terminals: Filter, Refresh, By Name, By
Time, Reversed, Hidden Files

Options
- X Window: - End of Line Characters, Text Conversion,
Tab Character Conversion

- char.-oriented terminals: Prompting, Binary transfer,
Text transfer, Strip newlines, Strip carriage returns,
Expand tabs.

********************
TOPIC NAME: File Transfer User Interface
-----------
Tool Bar (X Window only]
Filter - Select the directories and files to view in the list
box. For example, enter "*.doc" to see only .doc files.
After you make your selection, the filter label next to File:
indicates the filter applied to the current directories and files.
The default is all directories and files (*).

Info - (UNIX side only) Display a message box with file information
(similar to the UNIX command ls -l).

Rename - (UNIX side only) Rename a file or directory.

********************
TOPIC NAME: File Transfer User Interface
-----------
Binary or Text

You can specify binary or text for the format of the file being
transferred.

********************
TOPIC NAME: File Transfer User Interface
-----------
Prompting
If selected, the system checks if a file the same name as the source
file exists on the target system and prompts you with a message. If
Prompting is not selected, the target file is given the same name as
the source file.

********************
TOPIC NAME: File Transfer Menu Commands
-----------
Exit - exits File Transfer.

View - View the files in the selected directory By Name, By Time, in
Reverse order, or show Hidden files.

Server - Server..., [List of Servers]

Server... (X Window) opens the Server Manager dialog box for
managing servers.

********************
TOPIC NAME: File Transfer Menu Commands
-----------
Options - Select options for text conversion.

X Window only: [NO CHANGE]

Character-oriented terminals only:

Prompting - Select Prompting to rename a file that is being
copied. A dialog box allows you to specify the new filename.

Binary transfer
Text transfer
Strip newlines
Strip carriage returns
Expand tabs

********************
TOPIC NAME: File Transfer Toolbar
-----------
Toolbar
Create Dir - Create a new directory (and path).

Filter - Select the directory and files to view in list box.
For example, enter "*.doc* to see only .doc files. The default
without a filter selected is a listing of all directories and
files (*).

Info - (UNIX side only) Display a message box with file
information (like the UNIX ls -l command).

Rename - (UNIX side only) Rename a selected file or directory.

********************
TOPIC NAME: File Transfer List Boxes
-----------
NOTE: Be sure to specify both local and remote directories and files
before you use transfer any file.

Current directory path - This field shows the directory path and
current location.

X Window: You can change the directory path by selecting this
field and then selecting Change Dir on the Tool Bar and entering
a new path.

Character-oriented terminals: Tab to the directory command line,
enter a directory path, press Return.

Directories - This listbox shows all of the directories below the
current directory. Use the scroll bars to see more directories.

X Window: Click on a directory to select it. Double click on a
directory to change to that directory.

Character-oriented terminals: Tab to list box, use Arrow keys to
scroll to a directory name, press Return to select.

Files - This listbox shows all of the files in the selected
directory.

X Window: Use the scroll bars to see more files. Select the file
you want to copy to the AS/400.

Character-oriented terminals: Tab to listbox, use Arrow keys to
scroll to a file name, press Return to select.

Copy - Select to copy the selected file to the target system.
(Character-oriented terminals: Tab to Copy at bottom of screen
and press Return.)

Binary, Text - You can transfer a file in either binary format or
text format. (Character-oriented terminals: Binary and Text
transfer are in the Options Menu.)

Prompting - If checked, the system checks if a file by the same name
as the source file exists on the target system and prompts you
with a message. If Prompting is not checked, the target file is
given the same name as the source file. (Character-oriented
terminals: Prompting is in the Options Menu.)

********************
TOPIC NAME: [NEW TOPIC] File
-----------
Transfer Technical Information

This section contains important technical details about Client
Access for UNIX OS file transfers that you should review. Refer to the IBM
AS/400 reference manuals for definitions of technical terms and detailed
information. File Transfer utilizes two file systems:

QSYS File System

QDLS and QOPENSYS File Systems

Each system is described below.

QSYS File System

File Transfer supports the upload and download of the following types of
files: Source Physical Files (SPF) and Database (DB) Files. These files are
converted from ASCII to EBCDIC when uploaded and from EBCDIC to
ASCII when downloaded, with one exception.

Client Access for UNIX uses Database APIs for uploading and
downloading files in the QSYS file system.

Source Physical files on the AS/400

Typically contain 3 fields per record: Line [sequence number]
number, Date, and Data.

The files can have multiple members. Any of these members may be
accessed for file transfer.

Database files on the AS/400

Can contain single or multiple fields. Database files can contain
multiple members unless the file is an SQL table. SQL Tables contain
only one member.

File uploads to multiple-field DB file members of the same member
name are not supported by File Transfer.

Download of Source Physical Files from the Host

Source Physical file members are downloaded to the client as a single data
field (line numbers and dates are stripped). Records are delimited by a
newline.

Download of Database Files from the Host

Database file members are downloaded to the client with field delimiters
(space) and single quotes encapsulating the field data. Records are delimited
by a newline.

Upload Files to the Host in the QSYS file system

A file uploaded to QSYS is written as a single alphanumeric field.

Records are delimited by a newline. A newline on the UNIX system will
cause a new record to be created. If the [length of a line is greater than the
record length of the target file, the text is wrapped.

If any kind of file is uploaded to a directory ('library') in QSYS where a
file of the same name does not exist, a new Source Physical file and member
of the same name is created by default.

If a file is uploaded to QSYS and a file of the same name exists, File
Transfer checks to see if it is a Database file or a Source Physical file.

UPLOADING SOURCE PHYSICAL FILES IN QSYS

Sequence numbers and date fields get updated by the AS/400 for
uploaded Source Physical files.

Uploading a SPF to a library where a file of the same name does not exist:

A new SPF and member of the same name is created.

Uploading a SPF when the same file name exists in the specified library:

An '..overwrite?' prompt appears within the file transfer applications.

If 'OK' is selected, the first file member is cleared. A new file member
of the same name as the file is then inserted. The new data is inserted
as a single field in the member. Other members within that file are not
changed.

UPLOADING DATABASE FILES IN QSYS

If uploading to a Database file that is an SQL table, the default member
(usually of the same name) is the only member where data can be inserted.

When uploading to a Database file with the same file name, file transfer
checks the default member for more than one field.

If the Database file member contains one field, an '..overwrite?'
prompt appears within the file transfer applications.

If 'OK' is selected, the member gets 'cleared', and the new data is
inserted as a single field.

If the Database file member contains more than one field, the upload
function is not supported by file transfer and displays an error
message.

If a file is a single column SQL table and the source file name is the same as
the target table name, the table is overwritten. Otherwise the appropriate
error message is returned: "Request not supported" or "CPFXXXX Unable
to add member...".

QDLS and QOPENSYS File Systems

Client Access for UNIX uses bytestream (bit for bit) for uploading to and
downloading from these file systems.

Types of files transferred using QDLS and QOPENSYS: binary and text
files.

NOTE: Text file transfer uses iconv converters on the client for uploading
and downloading files. See your System Administrator for information about
iconv converters or see the UNIX man page 'iconv'.

Download binary files from the Host

The file is transferred bit for bit to the client in the same format as it
exists on the host.

Downloading a binary file to a directory containing a file with the same name
displays an '..overwrite?' prompt in the File Transfer application. Selecting
'OK' overwrites the file.

Download text files from the Host

The iconv converters on the client convert the EBCDIC text from the host
to text corresponding to the ASCII code page selected for the client. (This
text conversion is determined by the lang setting as described in
Localization.)

Downloading a text file to a directory containing a file with the same name
displays an '..overwrite?' prompt in the File Transfer application. Selecting
'OK' overwrites the file.

Upload binary files to the Host

The file is transferred bit for bit to the host in the same format as it
exists on the client.

Uploading a binary file to a directory containing a file with the same name
displays an '..overwrite?' prompt in the File Transfer application. Selecting
'OK' overwrites the file.

Upload text files to the Host

The iconv converters on the client convert the ASCII text from the client to
the EBCDIC code page selected for the host. (This text conversion is
determined by the lang setting as described in Localization.)

Uploading a text file to a directory containing a file with the same name
displays an '..overwrite?' prompt in the File Transfer application. Selecting
'OK' overwrites the file.

See also
About Transferring Files
File Transfer User Interface
File Transfer Menu Commands
File Transfer Toolbar
File Transfer List Boxes

********************
TOPIC NAME: Remote Command
-----------
About the Profile File: Profile files store the Remote Command
preferences listed below. A Profile file is used when you select
'Default' or 'Open...

********************
TOPIC NAME: Client Access Shell (CASH)
-----------
CASH Commands
deletefile filename - Removes a remote file. If you are in the QSYS
system, you must enter the fully-qualified pathname of the file. Example: To
delete myfile, enter this command: deletefile /QSYS.LIB/test.lib/myfile.file

getdbfile libraryname filename membername [localfilename] - Transfers a
database file from the remote AS/400 to your UNIX machine. NOTE:
getdbfile is used only for downloading database files in the QSYS file
system on the AS/400. Example: To get
"/QSYS.LIB/test.lib/myfile.file/myfile.mbr", enter the command, library
name (test) and the file name (myfile) and the member name (myfile.mbr):
getdbfile test myfile myfile localfilename

get remotefile localfile - Copies a remote file to a local file. Example:
get/QDLS/testlib/test /tmp/test

pingserver file|central|netprt|signon||rmtcmd|dtaq|database|Port
Mapper host_server_name - Verifies that a server at the host is available.
If the host_server_name is not provided, the default is used. The default
server is the server last connected. Example: pingserver 449
myhost.ibm.com
NOTE: pingserver is useful for verifying the status of the AS/400 servers.
See Troubleshooting for more information.

put localfile remotefile - Copies a local file to a remote file. Example:
put /tmp/test /QDLS/testlib/test

For a file upload to the QSYS file system, the target member name
must be specified.
Example: put /tmp/test /QSYS.lib/testlib.lib/test.file/test.mbr

WARNING: If a file or member of the same name exists, it will be
overwritten without warning.

********************
TOPIC NAME: 5250 User Interface
-----------
5250 Status Line
The following status indicators are only true when red (X Window) or
displayed (character-oriented terminals):

********************
TOPIC NAME: 5250 Emulator Key Mapping
-----------
Note: man pages xca5250(1) and ca5250(1) contain information and
default key mapping.

********************
TOPIC NAME: About Setting Servers
-----------
When you open File Transfer, Remote Command, or the 5250 Emulator,
the server in the .signon file is the current server. Before you begin using
Client Access UNIX for OS for the first time, it is a good idea set a server.

WARNING

DO NOT DIRECTLY EDIT THE .signon FILE. The .signon file can
be updated only by server changes (Add, Modify, Delete servers)
made through the Server Manager, File Transfer, 5250 Emulator, and
Remote Command applications, as listed below.

Required AS/400 Servers

All required AS/400 servers must be connected and available in order
to successfully run Client Access for UNIX OS. Use the Cash
Access Shell (CASH) command 'pingserver' to verify that the eight
necessary AS/400 servers are connected and available. (See the
"Client Access Shell" topic for command syntax and
"Troubleshooting" for details.)

********************
TOPIC NAME: About Setting Servers
-----------
Access to Set Servers (Character-oriented terminals)

[ONLY] Client Access Shell (CASH) setserver command

********************
TOPIC NAME: About Setting Servers
-----------
Set Server: Character-oriented Terminal

To add a server:
1. Enter 'casm' at the UNIX command line.

2. Tab to 'Add' at the bottom of the screen and press Return.

3. In the Server window, enter the Host Name, User ID, and
Password.

4. Tab to 'OK' and press Return.

This updates your .signon file (${HOME}/.ca400/.signon) and the server
is ready to connect.

To modify a server:

1. Enter 'casm' at the UNIX command line.

2. Tab to 'Modify' at the bottom of the screen and press Return.

3. In the Server window, select server name and enter new User ID,
and Password.

4. Tab to 'OK' and press Return.

This updates your .signon file (${HOME}/.ca400/.signon) and the server
is ready to connect.

To delete a server:

1. Enter 'casm' at the UNIX command line.

2. In the Server window, select server name.

3. Tab to 'Delete' at the bottom of the screen and press Return.
A Confirm window appears.

4. Tab to 'Yes' and press Return.

********************
TOPIC NAME: Troubleshooting
-----------
Required AS/400 Host Socket Servers

All required AS/400 servers must be connected and available in order to
successfully run Client Access for UNIX OS.

Use the Cash Access Shell (CASH) command 'pingserver' to verify that the
eight necessary AS/400 servers are connected and available. The servers
are: central, database, dataquery, file, netprt, remote command, signon, and
Port Mapper. (See the Client Access Shell (CASH) for command syntax.)
The table shows the Socket numbers or names to use with the pingserver
command (example: pingserver 449 myhost.ibm.com).

Socket # Server Name
449 Port Mapper
8470 central
8471 database
8472 dtaq
8473 file
8474 netprt
8475 rmtcmd
8476 signon

----------
Solaris Security Error
If a Solaris system user receives a security error, check with your
System Administrator to make sure that the post-installation script was
run as described in Setup.

*********************************************************************
*********************************************************************
***END OF FILE***
'README.NLV'
STARQUEST CLIENT ACCESS FOR UNIX(R) OS [070897-NLV]
Version 1.02