Client Access for UNIX Technical Documents
- Client Access for UNIX Quick Start Guide
- Article # SQV00CA001
This document is a guide for installing and configuring Client Access for UNIX. - Client Access FAQs
- Article # SQV00CA002
The FAQ provides answers to common questions regarding Client Access for UNIX.
- Adding Client Access License Manager to the Boot Process (AIX)
- Article # SQV00CA003
(obsolete) Client Access requires a license for the applications to work. After licensing the software for the first time, it is not added to the boot process under AIX. The following steps outline how to ensure that the license manager daemon will come up on each reboot.
- Adding Client Access License Manager to the Boot Process (SunOS, HP-UX)
- Article # SQV00CA004
(obsolete) Client Access requires a license for the applications to work. After licensing the software for the first time, it is not added to the boot process. The following steps outline how to ensure that the license manager daemon will come up on each reboot. - Cash (Client Access Shell) Date Fix
- Article # SQV00CA005
There is a known problem when using caftp, xcaftp, or cash to download an AS/400 file containing dates outside the range 1940-2039. A patch is available to resolve this problem when using an older version of CAUNIX. This fix is now included in current versions of CAUNIX. - How to Create a Shell Script with CASH
- Article # SQV00CA006
Client Access for UNIX OS comes with the command line utility cash. You can choose to script this application to execute repetitive tasks. - How to View the AS/400 Joblog for Client Access Security Errors
- Article # SQV00CA007
When first connecting to the AS/400 using Client Access For UNIX OS, you may get a Security Error message if there are problems relating to the host socket servers. This document shows how to view the joblog for the host socket servers on the AS/400. - Security Problem with Client Access for UNIX OS
- Article # SQV00CA008
When initially trying to connect to an AS/400 host after installing Client Access for UNIX OS, you may receive an error 216: Security Problem. This can be caused by several problems. The host socket servers on the AS/400 are typically involved. - Creating a Keyboard Map File for Client Access for UNIX OS (Character Oriented Terminals)
- Article # SQV00CA009
Client Access for UNIX OS comes with a default keyboard map file. When executing the ca5250 emulator for the first time, the keyboard map file called ca5250_keymap is created in the .ca400 directory of the users $HOME directory. This document will explain how to change the default 5250 emulator keymap file. - Setting a Default Font Size for the Client Access for UNIX 5250 Emulator
- Article #SQV00CA010
Some users find the default fontsize of the 5250 Emulator xca5250 difficult to read. This behavior can be changed by editing one file in the Client Access for UNIX installation. - "Unable to contact host" Error Using Client Access for UNIX OS
- Article # SQV00CA011
The license management software implemented in Client Access for UNIX communicates over TCP/IP. A common licensing error which occurs reads 'Unable to contact host'. This occurs due to incorrect or incomplete entries in the /etc/hosts file. - Linux Prerequisites for CAUNIX & StarLicense
- Article # SQV00CA012
This technical document describes how to identify and install Linux prerequisites for Client Access for UNIX and StarLicense.