File Name: /pd/$LOGNAME/doc/NewUserSetup


       Palladium              New User Setup              Palladium



       This sequence of New User Setup procedures has been authored
       by Sunil Sabat, Krasi Yalamov, Todd Poyner, Jeff Bralley, and
       Gary Kuo.



       1.  Shell Preference - C Shell (csh) or Korn Shell (ksh).

       1.1  Which shell are you running?

                 echo $SHELL

       1.2  Changing to the Korn shell

                 chsh $LOGNAME /bin/ksh


       2.  Your user ID

           When requesting accounts always use the same user ID.
       Get your User ID by typing:

                 id


       3.  Source code repository access

       3.1  Get an account

            The System Administrators have a service request script
       called job_req that prompts the user for all pertinent
       information.  The SA will quickly respond.

                 /usr/local/bin/job_req

       In the text body of the request put this information:

                 Please setup a new account.

                 Real name:
                 User name:
                 User ID:
                 Host: hpucsb2 (alias is ethelm)

                 Thanks in advance.









       PD/DPS                     - 1 -               July 18, 1995







       Palladium              New User Setup              Palladium



       3.2  HMS access (Source Code Control)

            HMS is the History Management System which manages RCS,
       SCCS, and BINARY files in a network.

       E-Mail Lillian Yao (lyao) and ask for HMS write access to
       Palladium Source code.  Lillian may also be reached by phone
       at 71195.

                 elm lyao

       Include:

                 Manager's Name:
                 Employee Type: Direct|Contract


       4.  Test/Development Access

           Accounts are needed on the following hosts:

                 hplptst1
                 hplptst2
                 hplptst4
                 hppddev1
                 hppddev2
                 hppddev4
                 hppddev7
                 hppddev8
                 hppddev9

       Ask a Palladium Team member with root access to setup your
       accounts.  Use the same User ID for all accounts.


       5.  HMS Initialization

           Login to hpucsb2 as <username> and run:

                 ninstall -vh ss-cmds.cup.hp.com fmrc

       NOTE: Execute ~/.hmssh or ~/.hmscsh in .profile or .cshrc
       upon login.


       6.  Create personal test directory

           On your designated test/development host type:

                 su root 
                 cd /pd
                 mkdir $LOGNAME
                 cd /pd/$LOGNAME
                 NEWDIRS='bin lib obj oids'
                 mkdir $NEWDIRS
		 chown $LOGNAME:users $NEWDIRS 
		 exit # su

	   P.S. All 'bin lib obj oids' directories should reside on
		your local development machine. Use symbolic links to
		point these directories on your machine.

       PD/DPS                     - 2 -               July 18, 1995







       Palladium              New User Setup              Palladium


       7.  On the SOURCE host (hpucsb2):

           Ensure you have personal account on hpucsb2.

           Login to hpucsb2 with your personal account.

           Ensure added the following line to .lssm:

               usehost ss-cmds.cup.hp.com /hpux/pd/hp

           Ensure added the following line to .hmssh or .hmscsh:

               sh,ksh: export FMRC="$HOME/.lssm $HOME/.mapdir"
               csh: setenv FMRC "$HOME/.lssm $HOME/.mapdir"

	   Execute:

	       . $HOME/.hmssh (or .hmscsh if you're using csh)
               cd /pd/$LOGNAME
               fco -MR -r R10DAV /hpux/pd/hp
		

	8.  On DEVELOPMENT host (e.g. hppddev4):

            Build a system initially by:

               cd /pd/$LOGNAME
               tools/mkbuild


       9.  Make the system

           Login to you designated test/development host with your
       personal account and type:

                 tools\buildFulcrum 
	         (only once for a /pd/$LOGNAME )

		 cd /pd/$LOGNAME
		 rm -f obj/* lib/* bin/* oids/*

           for non-shared library, you can do
                 tools/mk -ns -v prod
           or for shared library with debug option, you can do
                 tools/mk -g -v prod


** Before you do the item 10-12, please check the setting in the file of
   .mapdir in your home directory at SOURCE host (hpucsb2).
   The following entries should be existed in the .mapdir file:
   mapdir /pd/build /hpux/pd/hp
   mapdir /pd/$LOGNAME /hpux/pd/hp

       10.  Check-out files for editing

                 fco -r R10DAV -l <filename>


       11.  Check-in files

                 fci -r R10DAV -u <filename>


       12.  Update all files

            From hpucsb2 type:

                 fupdate -r R10DAV -R /hpux/pd/hp








       PD/DPS                     - 3 -               July 18, 1995
