StarQuest Technical Documents

Adding Client Access License Manager to the Boot Process (AIX)

Last Update: December 2, 1997
Product: Client Access for UNIX
Operating System: AIX
Article ID: SQV00CA003


As of August 2005, all current shipping versions of CAUNIX use StarLicense licensing in place of Flex licensing. Although the details of starting the License Manager at reboot have changed, the concepts below still apply. Please contact StarQuest Support if you need assistance.

Client Access requires a Flex 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.


To get Client Access's license manager to restart on reboot, you need to copy the rc.ca400 file to the /etc directory and add an entry for it at the end of the inittab file.


Log in as super-user (root), or switch your effective user ID to super-user with the "su" (switch user) command:

$ su - root

root's Password:

% id

uid=0(root) gid=0(system)



If you have not already done so, you should create an "rc" script to restart the Client Access license manager at boot-time. This can be done (at the same time the product is licensed) by running the "lmadmin" (License Manager Administration) program. If you have already licensed Client Access, please move to STEP 3.

Set environment variable "CA400" to the full pathname of the directory in which Client Access is installed and configured. Also set "STARLM" to the full pathname of the directory in which you installed the "STARLM" license manager package. For example,

% CA400=/usr/lpp/ca400

% STARLM=/usr/lpp/starlm

% export CA400 STARLM

Run program "lmadmin" and respond to all prompts carefully. Before the program exits it will deposit a customized "rc" script for you in the file ${CA400}/etc/conf/rc.ca400

Following is the output of a sample session using "lmadmin":

% cd ${CA400}/etc

%< ./lmadmin/p>

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

Enter license key: abcd1234efgh4568ijkl

Enter license expiration date: 31-jan-1999

Enter number of users to be licensed: 8


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

Starting license manager daemon...

% cd ${CA400}/etc/conf

% cat rc.ca400



# @(#)Start daemons required by Client Access package







nohup ${LMGRD_PATH} -c ${LICENSE_FILE_PATH} 1>${LOG_PATH} 2>&1 &


Copy the script "${CA400}/etc/conf/rc.ca400" to directory "/etc" (where shell environment variable "CA400" contains the full path-name of the directory in which Client Access is installed and configured):

% CA400=/usr/lpp/ca400

% export CA400

% cp ${CA400}/etc/conf/rc.ca400 /etc

% cd /etc

% cat rc.ca400

Be certain the file mode allows read/write/execute access by super-user but READ-ONLY access for all other users:

% cd /etc

% chmod 0744 rc.ca400

% ls -l rc.ca400

-rwxr--r-- 1 root system 306 Jan 31 1997 rc.ca400


Copy the file "/etc/inittab" to a safe place. For example, if the current date is December 31, 1997, the following will do:

% cd /etc

% cp inittab inittab.971231


Add a new entry to the end of the "/etc/inittab" file using the "mkitab" command ( /usr/sbin/mkitab 'ca400:2:once:/etc/rc.ca400 1>/dev/null 2>&1' ). Verify the entry by displaying the last few lines of the file:

% /usr/sbin/mkitab 'ca400:2:once:/etc/rc.ca400 1>/dev/null 2>&1'

% tail inittab

cons:0123456789:respawn:/usr/sbin/getty /dev/console

infod:2:once:startsrc -s infod


rcncs:2:wait:sh /etc/rc.ncs > /dev/console 2>&1 Start NCS

netlsd:2:wait:sh /etc/rc.netls >/dev/console 2>&1 start netls

mount:2:wait:/etc/rc.mount > /dev/console 2>&1

tty0:2:respawn:/usr/sbin/getty /dev/tty0

startdb2:2:once:/etc/rc.db2 > /dev/console 2>&1 Start DB2

lpd:2:once:/usr/bin/startsrc -s lpd

ca400:2:once:/etc/rc.ca400 1>/dev/null 2>&1


If you logged in as super-user (in STEP 1), log out now. If you used the "su" command to switch your effective user ID to super-user, type "exit" to return to the parent shell (the shell you were using when you started STEP 1 above).

The system is now configured to restart any required Client Access daemons the next time a reboot occurs.


The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.