Digital Equipment Corp/Compaq Unix Servers

Installation and Mangement Guide

Pre Tru64 - 5.x OS Installation

Tru 64 - 5.x OS Installation

Upgrading the Operating System

Patches

Listing Patches on an Alpha System

Configuring Swap Space

Vendor Software Install Updates

C Compilers/Developers Toolkit

Licenses

Kernel Build Section

Logical Storage Manager - Logical Volumes

LSM Disk Mirroring

Adding disks controllers and disks to the system

Hard Disk Partitions

Adding Fibre Disks

Connecting to the HSZ Controller to configure RAID Disks

Restoring the primary and secondary bootstrap programs

File Systems

Network Configuration

NFS Configurations

Updating The Firmware

Using The ARC Utility

Configuring a Console

System Shutdown & Startup Procedures

Prom Level, Boot Commands

Decevent Installation

Diagnostic Tools

Utilities/Commands

Recovering the root password

Digital 4.0D Documentation

Digital 4.0E Documentation

Vendor Support

Installing a New Operating System for Pre-Tru64bit 5.x.

Additional products to be installed after the O/S installation is complete:

1. Install the latest version of Ladebug, ie: Version 67. This product version is in our reporisoty as /repos1/Dec/ladebug-all-4.x-4.0.67.tar. 
2. Install SVR4 (ESVF), you will find this product on the Associated Products CD #2.
   This will install 'truss'.  Make a link from /usr/opt/svr4/bin/truss to /bin/truss, ie:
   ln -s /usr/opt/svr4/bin/truss  /bin/truss
3. Install the latest O/S patch kit.
4. Install dupatch, this gets installed when you install an O/S patch kit.
5. Increase the per_proc_address_space is set to the value of max_per_proc_address_space.

-----------------------------------------------------------------------------------------------------

Refer to  the Digital Unix Installation Guide for further help with the installation.

Post Install Steps, gather important files from the system if it was a previously installed system:

/etc/fstab
/etc/sysconfigtab
/etc/resolv.conf
/etc/passwd
/etc/group
/etc/routes
/etc/hosts
/etc/rc.config
/etc/securettys
/etc/dbmap
/etc/usermap
/etc/asmap
/etc/patchmap
/etc/oratab
/etc/inftab
/etc/sybtab
/etc/auto_master
/etc/auto_direct
/etc/tnsnames.ora
/etc/listener.ora
/etc/interfaces.syb

Gather Logical Storage Manager configuration information:

volsave    (Creates a file in /usr/var/lsm/db/LSM.xxx.[sysname]
volprint -Aht > filename
voldisk list > filename
voldg list > filename
voldctl list > filename

Gather Disk Information to files on a disk other than the root disk and disks using LSM, ie:

disklabel dsk0 > /ds3/disk_label/disklabel_dsk0   (/dev/disk/dsk3c)
disklabel dsk1 > /ds3/disk_label/disklabel_dsk1

Gather System Information in a file on your workstation called sysinfo, file to gather are:

Results of the following commands

df -k
swapon -s
netstat -in
netstat -rn
disklabel dsk0 (and all the other dsk's on the system as well)
P00>>>sh dev

Make note of the CDROM device, it will be the first line of the output.

P00>>>sh  (Show all)

Make note of the Firmware Version, it will be the last line in the output

Also run the '/var/sbin/sys_check'  to gather more pertinent information about the system.

This information will get placed in /var/recovery/sys_check.

-----------------------------------------

Halt the system to get to the boot prompt "P00>>>"

shutdown -h now

Show the boot device, cdrom device and disk devices.

P00>>> sho dev

NOTE: At the boot prompt, make sure that the follwoing settings are:

OS Type = unix
ewa0_mode  = FastFD

*Other settings for ewa0_mode could be either Twister Pair (10 BaseT) or Full Duplex (100 BaseT)FastFD
*If the system has a ee0 nic card this should always be set to AutoNegotiate.

Change the settings if they are not set correctly.
The example below shows you how to do this.

Shows settings for ewa0_mode, os_type and console, etc....

P00>>> show  | more

For 100BaseT Full Duplex - Set to 'FastFD'.

On some systems (es-40's) 'FastFD' does not work, so you will have to use 'Auto-Negotiate'  instead, you will need to make sure that the switch port is set to Auto as well, and the same goes for the 'FastFD' setting, make sure the switch port matches 100 Full.

P00>>> set ewa0_mode FastFD

P00>>> set ewa0_mode Auto-Negotiate

 Make sure OS Type is set to 'unix'

P00>>> set os_type  unix
 

Make sure Console is set to 'serial'

P00>>> set console serial

Start the Installation

Insert the Digital Unix Operating System CD into the CDROM drive.
Boot the system from the CDROM device to start the installation. 

Example - Booting from the CDROM device dka500.

P00>>> boot dka500

Initializing system for Digital Unix Installation. Please Wait.
Performing CDROM Installation
 

Select option 3 - This option will exit to the unix shell so you can change the existing partition layouts if needed.  Type the following at the unix prompt.

# EDITOR=vi
# TERM=vt100

# disklabel -r dsk0  ( This will show you the layout of the partition table for /dev/dsk0, if the layout is the way you want the disk partitioned then continue with the installation, otherwise modify the partitions using the Hard Disk Partitions guide .

Type 'exit' to go back to the installation process.

After the disks have been partitioned, go on to the next step to finish the installation.
 

Select option #2 - Custom installation.

Enter root password:

Select Location: 36 for US 

Select time zone: 11 for Pacific

Enter the current date: 09-30-98

Enter the current time: 18:25

Select root disk. Example:  rz0.

The root file system will be placed on the "a" partition of this disk.

Choose which partition table to use.

Enter your choice: 2 (Existing table that you partitioned above).

Use this default disk layout (y/n) ?  n

Select UFS  for UNIX file system.

Select disk where the /usr file system will reside.

Select partition where /usr will reside.

Select UFS for Unix file system.

Select the disk where the first swapping area (swap1) will reside.

Select the disk where the second swapping area (swap2) will reside, optional.

Select disk where the /var file system will reside.

Select partition where /var will reside.

Select UFS for UNIX file system.

Sofware subsets to install:

Enter the Number(s) of each item to install on the input line,
press enter to continue and add more number selections at the end of the input line.

Press enter to continue through each screenfull of subsets including at the end.
 

Additional Terminfo databases

Logical Storage Manager Kernel Header and Common Files

Logical Storage Manager Kernel Modules

POLYCTR advfs Kernel Modules

All of the Reference Pages

Software Development Tools and Utilities

Standard Header Files

Standard Programmer Commands

Static Libraries

Logical Storage Manager

Logical Storage Manager GUI

Logical Volume Manager

XVFB

All of the Text Processing
 

Your choices will be displayed for review,  answer the question -

Are these the subsets that should be loaded? [y/n] 
(Answer yes if all the subsets are correct, no to go back and re-enter the subsets).

*** Kernel Configuration and Build Procedure Begins ***
 

System will now reboot

During reboot a message displays 'This system requires a driver for its graphics card.
Enter the driver where the kit can be found or <Return> to cancel:

Press <RETURN> to cancel and continue with the installation.
 

*** Kernel Option Selection ***  Select the following:
 

System V Devices

Logical Volume Manager (LVM)

Streams pckt module (PCKT)

X/Open Transport Interface  (XTISO, TIMOD, TIRDWR)

ISO 9660 Compact Disc File System (CDFS)

Logical Storage Manager (LSM)
 

The above Kernel Modules will now be loaded.
 

Do you want to edit the configuration file?
 
Answer NO, Unless you you need to add a eisa0 controller.
 
If you need to add a eisa0 contoller:

Answer YES and enter (as an example) the following line in the kernel configuration file:

 
controller ace0 at eis0 slot 10 vector aceintr 

NOTE:   The configuration file is /usr/sys/conf/[system-name] in caps. 

Example: /usr/sys/conf/RT-DEC06

The kernel is now being rebuilt. 
 

**** Performing Kernel Build ****

When the installation is complete there will be logfiles that contain a record of your installation in:
 

/var/adm/smlogs

The system will reboot when the installation has completed successfully. 

Now confiugre /tmp file system:

Boot from the O/S CD.

P00>>> boot dka400

Initializing system for Digital Unix Installation. Please Wait.
Performing CDROM Installation

Press the return key until you get to the following menu:

1) U.S. English Installation
2) Intallation with Worlwide Language Support
3) Exit Installation

Enter your choice:  3

FSCK the root file system:

fsck /dev/rz0a

mkdir /tmp/r0
mount /dev/rz0a  /tmp/r0
cd /tmp/r0
rm -rf tmp
mkdir /tmp/r0/tmp
newfs /dev/rz0? (NEWFS the /tmp file system)
fsck /dev/rz0?  (FSCK the /tmp file system)
edit fstab - put an entry in for the /tmp filesystem, save and quit.

HALT the system, and at the P00> prompt and boot the system.

halt
P00> boot

Configuring Swap Space

List current swap space:

#swapon -s 

For 4.x and earlier versions of the O/S Enter swap space specification in /etc/fstab file by edititing the file:

Example of a swap  entry:

/dev/rz0b   swap2    ufs    sw    0    0

For 5.x Tru 64bit O/S enter the swap entry in the /etc/sysconfigtab file under the vm section as well as the deferred swap setting:

vm:

swapdevice=/dev/disk/dsk0b,/dev/disk/dsk1b

vm-swap-eager=0 (To set the system to use deferred mode)

Activate a newly added paging space in /etc/fstab:

#swapon -a /dev/rz1h

Add device /dev/rz1h as swap space.

#swapon /dev/rz1h

To make swap space permanent, you must specify the swap file entry in the
  /etc/fstab file.

Configure swap space as deferred swap space on all Dec installations:

 On Pre 5.x systems

cd /sbin

mv swapdefault swapdefault.org

On 5.x systems and above

Add the following entry to the /etc/syscnfigtab file under the vm: section

vm:

vm-swap-eager=0 (To set the system to use deferred mode)

(This will keep the kernel from using up all of the primary swap space,
if you want a further definition of eager swap do a man on swapon).

Changing the boot flags after the installation is complete:

Halt the system so that you can change the boot flags by issuing the following console commands to set your default bootpath variable and to boot your system disk to multiuser:
 

P00>>> set boot_osflags A

P00>>> set bootdef_dev dka0  --> 'dka0' is just an example of a default boot device.

P00>>> boot

Updating the /etc/securettys file so that root users can login via telnet:

Update '/etc/securettys' with a one line entry 'ptys' at the end of the file.

Save and exit the file.

Compilers Information:

Load the compilers at Customers request, and that you have verified this with the content manager, usually 'st-xxxxx' boxes only.

To install the compilers Go to the C Compilers/Developers Toolkit Section.

License and Register a subset package:

Execute the license script file provided by our Compaq on-site representative, otherwise see installing licenses for information on how to get and register licenses -->  Licenses,
 

 NOTE: The license database resides in  /var/adm/lmf/ldb, do not modify or remove this file.

Execute the license script file in the repository -   /repos1/Dec/lic-all-2001lmflic.csh

cd /repos1/Dec

./lic-all-2001lmflic.csh

To manually license and register a subset package, you will need the license packs to do this and issue the following commands.

lmf

select: [register, enter info, x, reset, list, exit]
 

lmf> register

A register form is displayed, place cursor at the first field, ie: Issuer:, append the line after the 'colon' of Issuer, enter the correct information here, DEC, then press the escape key, move to the next file and append the line in the same manner as before, and press escape again to exit the append mode, and move to next field, and so on. 

Once you have finished entering the field then save the file with 'x'.  If the checksum passes it will tell you and you will be placed at the lmf> prompt.

lmf> reset

lmf> list

lmf> exit

Load additional packages from the O/S Installation Media that you may have missed
at installation time.
 

mount CDROM device

Example: mount -r /dev/rz5c /cdrom

setld -l /cdrom/ALPHA/BASE
 

Choose the subsets that you want to install from the subsets listed on the screen.

Example:

Choices: 5-7 10-12 19-23 27-28 38 41 47-48 

Enter 'Y' to accept and load.
 

When the load is complete the screen will display subsets loaded successfully.

Finish building out the system per the Unix SysAdmin Checklist per Users request.

TRU 64 - 5.x O/S Installation

Additional products to be installed after the O/S installation is complete:

1. Install the latest version of Ladebug, ie: Version 67, per Carla Curtis Compaq's on-site support person.  This product version is in our reporisoty as /repos1/Dec/ladebug-all-5.x-4.0.67.tar.
   Go to the link below to go to Compaq's ladebug download site if you want a more current version than what is listed above:

http://www.compaq.com/products/software/ladebug/download-install-unix.html

2. Install SVR4 (ESVF), you will find this product on the Associated Products CD #2 under Extended_System_V/kit. Use setld -l to install this product and select option 3) All of the above.
   This will install 'truss'.  Make a link from /usr/opt/svr4/bin/truss to /bin/truss, ie:
   ln -s /usr/opt/svr4/bin/truss  /bin/truss
3. Install the latest O/S patch kit.
4. Install dupatch, this gets installed when you install an O/S patch kit.
5. Increase the per_proc_address_space is set to the value of max_per_proc_address_space, see kernel section for this setting.

----------------------------------------------------------------------------------------------------------------

Refer to  the Digital Unix Installation Guide for further help with the installation.

Tru64 - 5.1 - O/S patch in the repository1 as t64v51as0003-20010521.tar

Post Install Steps, gather important files from the system if it was a previously installed system:

/etc/fstab
/etc/sysconfigtab
/etc/resolv.conf
/etc/passwd
/etc/group
/etc/routes
/etc/hosts
/etc/rc.config
/etc/securettys
/etc/dbmap
/etc/usermap
/etc/asmap
/etc/patchmap
/etc/oratab
/etc/inftab
/etc/sybtab
/etc/auto_master
/etc/auto_direct
/etc/tnsnames.ora
/etc/listener.ora
/etc/interfaces.syb

Gather Logical Storage Manager configuration information:

volsave    (Creates a file in /usr/var/lsm/db/LSM.xxx.[sysname]
volprint -Aht > filename
voldisk list > filename
voldg list > filename
voldctl list > filename

Gather Disk Information to files on a disk other than the root disk and disks using LSM, ie:

disklabel dsk0 > /ds3/disk_label/disklabel_dsk0   (/dev/disk/dsk3c)
disklabel dsk1 > /ds3/disk_label/disklabel_dsk1

Gather System Information in a file on your workstation called sysinfo, file to gather are:

Results of the following commands

df -k
swapon -s
netstat -in
netstat -rn
disklabel dsk0 (and all the other dsk's on the system as well)
P00>>>sh dev

Make note of the CDROM device, it will be the first line of the output.

P00>>>sh  (Show all)

Make note of the Firmware Version, it will be the last line in the output

Also run the '/var/sbin/sys_check'  to gather more pertinent information about the system.

This information will get placed in /var/recovery/sys_check.

------------------------------------

Halt the system to get to the boot prompt "P00>>>"

shutdown -h now

Show the boot device and cdrom device.

P00>>> sho dev

NOTE: At the boot prompt, make sure that the follwoing settings are:

OS Type = unix
ewa0_mode  = FastFD

*Other settings for ewa0_mode could be either Twister Pair (10 BaseT) or Full Duplex (100 BaseT)FastFD
*ee0 Nic card should alwasy be set to Augo Negotiate.

Change the settings if they are not set correctly.
The example below shows you how to do this.

Show settings for ewa0_mode, os_type and console, etc....

P00>>> show  | more

100BaseT Full Duplex - Set this to 'FastFD'.

On some systems (es-40's) 'FastFD' does not work, so you will have to use 'Auto-Negotiate'  instead, you will need to make sure that the switch port is set to Auto as well, and the same goes for the 'FastFD' setting, make sure the switch port matches 100 Full.

P00>>> set ewa0_mode FastFD

Start the Installation

Insert the Digital Unix Operating System CD into the CDROM drive.
Boot the system from the CDROM device to start the installation. 

Now confiugre /tmp file system:

Boot from the O/S CD.

P00>>> boot dka500

Initializing system for Digital Unix Installation. Please Wait.
Performing CDROM Installation

Press the return key until you get to the following menu:

1) U.S. English Installation
2) Intallation with Worlwide Language Support
3) Exit Installation

Enter your choice:  3

FSCK the root file system:

fsck /dev/disk/dsk0a

mkdir /tmp/r0
mount /dev/disk/dsk0a  /tmp/r0
cd /tmp/r0
rm -rf tmp
mkdir /tmp/r0/tmp
newfs /dev/rz0? (NEWFS the /tmp file system)
fsck /dev/dsk0?  (FSCK the /tmp file system)
edit fstab - put an entry in for the /tmp filesystem, save and quit.

HALT the system, and at the 'P00>>>' prompt boot the system.

halt
P00>>> boot

Updating the /etc/securettys file so that root users can login via telnet:

Update '/etc/securettys' with a one line entry 'ptys' at the end of the file.

Save and exit the file.

Compilers Information:

Load the compilers at Customers request, and that you have verified this with the content manager, usually 'st-xxxxx' boxes only.

To install the compilers Go to the C Compilers/Developers Toolkit Section.

License and Register a subset package:

See installing licenses for information on how to get and register licenses -->  Licenses,
   

Load additional packages from the O/S Installation Media that you may have missed
at installation time.
 

mount CDROM device

Example: mount -r /dev/rz5c /cdrom

setld -l /cdrom/ALPHA/BASE
 

Choose the subsets that you want to install from the subsets listed on the screen.

Example:

Choices: 5-7 10-12 19-23 27-28 38 41 47-48 

Enter 'Y' to accept and load.
 

When the load is complete the screen will display subsets loaded successfully.

Kernel Build Section

Note: The dflssiz parameter is not used in Tru64 V5.x Unix.
You do not need to edit the /sys/conf/{hostname} file.  All Admin controlled parameters now reside in /etc/sysconfigtab. If you are not familiar with 'vi' editor then follow the directions below for changing the parameters in the sysconfigtab file.

Pre Tru64 V5.x Unix dflssiz setting when running the doconfig utility:

Modify the Kernel to increase the dflssiz (Default stack size limit) to 9097152 and increase maxusers to 512. 

The default stack size needs to be increased so that the Informix 'onspaces' command can be used from the command line.

Re-Build the kernel:

  Set Environment Variables:

EDITOR=vi; export EDITOR

TERM=vt100; export TERM

Backup the existing kernel file and start the kernel configuration utility:

cp /vmunix /vmunix.sav

doconfig   (This is the kernel configuration utility)

A configuration file with the name [SYSTEM-NAME] already exists.
Do you want to replace it?  (y/n) [n]:  Y

Select the following kernel options if they are present: 

Tru64 Unix - kernel parameter settings:

Configuring Shared memory parameters in the /etc/sysconfigtab file:
 

Enter the shared memory parameters in the file /etc/sysconfigtab.

cp /etc/sysconfigtab /etc/sysconfigtab.sav

vi /etc/sysconfigtab 

proc:
    maxusers = 1024
    max_proc_per_user = 8192
    max_threads_per_user = 20000
    per_proc_data_size = 4589934592
    max_per_proc_data_size = 4589934592
    max_per_proc_address_space = 4589934592
    per_proc_address_space = 4589934592
    per_proc-data_size = 4589934592
    per_proc_stack_size = 1073741824

ipc:
msg-max = 8192
msg-mnb = 16384
msg-mni = 10000
msg-tql = 500
shm-max = 2147483647
shm-min = 1
shm-mni=500
shm-seg=250
sem-mni=2000
sem-msl = 3200
sem-opm = 800
sem-ume = 2000
sem-vme = 2000
sem-vmx = 65534
sem-aem = 32768
ssm-threshold=0
num-of-sems = 2048
max-kernel-ports = 22487

 
Write, save and quit the editor.

Shutdown and reboot the system.

/usr/sbin/shutdown -r now 
(This will reboot the system and come back up in Multi-User Mode).

You can update the memory copy of the sysconfigdb database if you want to do a quick test on these new parameters.

To update a kernel parameter in a particular subsystem:

Example in updating enhanced_core_name and enhanced_core_max_versions in the proc subsystem:

/sbin/sysconfig -r proc enhanced_core_name=1

/sbin/sysconfig -r proc enhanced_core_max_versions=4

List the updated kernel values in the proc subsystem:

/sbin/sysconfig -q proc | grep enhanced

To update the memory copy of the sysconfigdb database.

/sbin/sysconfigdb -s

List the entire sysconfigdb database

/sbin/sysconfigdb -l  

List just the shared memory parameters:

/sbin/sysconfigdb -l ipc

Query attribute information which includes the attribute type, the operations supported, and the minimum and maximum values allowed for the attribute. Note:  The minimum and maximum values means length and size for attributes of char and binary types, respectively.  If you omit the attribute list, information about all attributes in the specified subsystem is displayed:

To list information for proc and attribute open_max_soft

#/sbin/sysconfig -Q proc open_max_soft

proc:
open_max_soft -        type=INT  op=CQ   min_val=0  max_val=4096

To list infomation for all attributes:

#/sbin/sysconfig -Q proc

If you are not familiar with the editor utility 'vi' then use the sysconfigdb utility instead of directly editing the sysconfitab file.

Using the sysconfigdb command to modify the /etc/sysconfigtab database automatically updates the in-memory copy of the database. This ensures that the kernel has immediate access to any changes. The file is also automatically merged during an update installation and changes will be merged into the new system.

cd /etc

Create a file called memory_params.stanza and populate the file with the following information in stanza format (label left flush, parameters indented):

vi /etc/memory_params.stanza

proc:
   
    max-threads-per-user = 1024
    max-proc-per-user = 600
    maxusers = 1024
   
ipc:
    msg-max = 8192
    msg-mnb = 16384
    msg-mni = 10000
    msg-tql = 500
    shm-max = 2147483647
    shm-min = 1
    shm-mni = 500
    shm-seg = 250
    sem-mni = 2000
    sem-msl = 3200
    sem-opm = 800
   sem-ume = 2000
    sem-vme = 2000
    sem-vmx = 65534
    sem-aem = 32768
    ssm-threshold = 0
    num-of-sems = 2048
    aio-max-num = 128
    max-kernel-ports = 22487
    port-hash-max-num = 1124350
    port-reserved-max-num = 22487
    set-max-num = 1029

advfs:
    AdvfsCacheMaxPercent = 7
    AdvfsMinFragGrps = 16
    AdvfsMaxFragGrps = 48
    AdvfsAccessMaxPercent = 25
    AdvfsMinFreeAccess = 128
    AdvfsSyncMmapPages = 1
    AdvfsDomainPanicLevel = 1
    AdvfsCacheHashSize = 1024

vfs:
    io-throttle-shift = 1
    io-throttle-maxmzthruput = 1

To add a subsystem (ie advfs) to the sysconfigtab file use this syntax:

# sysconfigdb -a -f {filename} {subsystem}

This will place a new subsystem with it's related parameters at the bottom of the /etc/sysconfigtab file. 

Example:

# sysconfigdb -a -f memory_params.stanza advfs

To update an existing subsystem (ie proc) in the sysconfigtab file you need to edit the memory_params.stanza file and place the changes under the desired label.  Then use this syntax:

# sysconfigdb -m -f {filename} {subsystem}

Example:

# sysconfigdb -m -f memory_params.stanza proc

Using this Compaq/Dec approved method for making these changes will also cause the operating system to look for the file that contained the added/updated information and merge it's contents into the sysconfigtab after OS upgrades and /or Kernel rebuilds. Do a man on sysconfigdb for more options.

Upgrading the Operating System.

Pre-5.x

Review "Performing Update Installation" chapter in the Digital Installation Guide.

Save data from /, /usr, /var, /opt. 
 

If room on the server in a filesystem unaffected by the upgrade (such as /data1/oldsys),
copy critical directories/files there.  The followin is a list of file to save:

/etc/fstab
/etc/sysconfigtab
/etc/resolv.conf
/etc/passwd
/etc/group
/etc/routes
/etc/hosts
/etc/rc.config
/etc/securettys
/etc/dbmap
/etc/usermap
/etc/asmap
/etc/patchmap
/etc/oratab
/etc/inftab
/etc/sybtab
/etc/auto_master
/etc/auto_direct
/etc/tnsnames.ora
/etc/listener.ora
/etc/interfaces.syb

Gather Logical Storage Manager configuration information:

volsave    (Creates a file in /usr/var/lsm/db/LSM.xxx.[sysname]
volprint -Aht > filename
voldisk list > filename
voldg list > filename
voldctl list > filename

Gather Disk Information to files on a disk other than the root disk and disks using LSM, ie:

disklabel dsk0 > /ds3/disk_label/disklabel_dsk0   (/dev/disk/dsk3c)
disklabel dsk1 > /ds3/disk_label/disklabel_dsk1

Gather System Information in a file on your workstation called sysinfo, file to gather are:

Results of the following commands

df -k
swapon -s
netstat -in
netstat -rn
disklabel dsk0 (and all the other dsk's on the system as well)
P00>>>sh dev

Make note of the CDROM device, it will be the first line of the output.

P00>>>sh  (Show all)

Make note of the Firmware Version, it will be the last line in the output

Have a full OpenVision backup made of the server before starting.
 

Make sure you have enough space in the root filesystem for the upgrade (at least 20Meg).

Shutdown databases and other software, such as tuxedo, apache, etc....

If you are unable to clear out all processes, then reboot the system.
 

Bring the server down to the prom level and check the current firmware version.

sync; sync

halt 

At the [P00>>>] prompt, type "show version".

Check this version against the minimum requirement needed for the operating system
you are upgrading (found in the Install Manual or release notes).

Reboot the server and check the installed products:

At the [P00>>>] prompt, type "boot". 

Once booted, type "setld -i | pg" to get listing of installed products. 
Make note of any non-standard products.
 

Check for the correct device name for the CDROM:

While the system is running:

cd /dev 

file rrz*c | grep RRD - File type RRD45 is the cdrom device. 

Example:

file rrz*c | grep RRD
/dev/rz6c:  character special (8/6146) SCSI #0 RRD45 disk #48 .....

From the boot prompt "P00>>>"

At the [P00>>>] prompt, type "show device"

This will list the devices on the system, the CDROM device will have type of "RRD##", and the boot device name to use would be in the format of DKA###, this will be on the same line. 

Example:

dka500.5.0.1.1     DKA500          RRD45   0436

Shutdown system again and check for the boot drive name:

sync 

sync 

halt 

To get the name of boot drive - usually DKA0.0.0.1.0.

At the boot prompt [P00>>>], type "show | more"
 

Check the setting of ewa0_mode

This tells you if the system is set to Twisted Pair(10 BaseT),
FastFD(100 BaseT - Full Duplex), or Auto-Negotiate:

At the boot prompt [P00>>>], type:

sho ewa0_mode
 

To change the ewa0_mode to 100 BaseT

P00>>>set ewa0_mode FastFd 

To change ewa0_mode to auto-negotiate, the preferred setting.

P00>>>set ewa0_mode auto-negotiate
 

At the boot prompt check what the boot_dev is and then boot to single user mode.

P00>>> sho boot_dev

dka0.0.0.1.0

P00>>> boot -flag s dka0.0.0.1.0  or

P00>>> boot -fl s dka0

Check and mount filesystems once the system is up in single-user mode.

/sbin/bcheckrc  

Now insert the Operating System CD into the cdrom drive.
 

Run installupdate to upgrade the Operating System.
 
NOTE2: rz6c is used here as an example of a CDROM device.

Set environment variables:

EDITOR=vi; export EDITOR

TERM=vt100; export TERM

Start the update:

Unmount /tmp and /home if they are mounted.

/sbin/installupdate -i /dev/rz6c

The following messages will appear:

recommending that a backup be done...do you want to continue? y 

checking current state of system...may take up to 10 minutes... 

xxx subsets will be installed....
Base System
....copying from /updmnt/ALPHA/BASE/....

Merge completed successfully (repeated several times) 

Exiting Update Installation.....
Server will automatically reboot.

After the reboot....configuration begins.

The following messages will appear:
 

Configuring "Base System" 

Merge completed successfully.... 

Configuring....(goes through all the subsets)
 

Next, the Kernal Option Selection menu will appear.

Select the following:

System V Devices 

Logical Volume Manager (LVM)....if it's a selection 

STREAMS pckt module (PCKT) 

X/Open Transport Interface (XTISO, TIMOD, TIRDWR) 

ISO 9660 Compact Disc File System (CDFS) 

Logical Storage Manager (LSM) 

Next you will be prompted to edit the configuration file, answer no.

NOTE: If adding a eisa0 controller then answer yes and make sure the following line is included in the file, the slot number may be different:

Write, save and quit the editor.

The kernel is then built and the server will automatically reboot itself. 

Now perform post-installation tasks:
 

Review logs:
cd /var/adm/smlogs

Check the following log files:

update.log 

it.log 

upd_custom_files 

upd_mergefail_files 

upd_obsolete_files 

Check differences on known files (and ones in upd_custom_files).

cd /sbin 

diff /sbin/nfsmount nsfmount.PreUPD 

If the differences are for the automouter to start then -
"mv nfsmount.PreUPD nfsmount". Otherwise update the new file. 

Review the config file:

cd /sys/conf 

diff <hostname> <hostname>.bck 

Most likely the only change will be "maxusers".

Now rebuild the kernel and reboot the server:
 

cp /vmunix /vmunix.save 

doconfig -c <hostname> or just doconfig (You will be prompted for hostname).

Note: hostname is in all caps with no dashes, ie SPDEC04. 

Do not edit the config file
Display will say "performing kernel build"...
 

When the kernel build is complete:

shutdown -r now

5.x Upgrade

Review "Performing Update Installation" chapter in the Digital Installation Guide.

Save data from /, /usr, /var, /opt. 
 

If room on the server in a filesystem unaffected by the upgrade (such as /data1/oldsys),
copy critical directories/files there.  The followin is a list of file to save:

/etc/fstab
/etc/sysconfigtab
/etc/resolv.conf
/etc/passwd
/etc/group
/etc/routes
/etc/hosts
/etc/rc.config
/etc/securettys
/etc/dbmap
/etc/usermap
/etc/asmap
/etc/patchmap
/etc/oratab
/etc/inftab
/etc/sybtab
/etc/auto_master
/etc/auto_direct
/etc/tnsnames.ora
/etc/listener.ora
/etc/interfaces.syb

Gather Logical Storage Manager configuration information:

volsave    (Creates a file in /usr/var/lsm/db/LSM.xxx.[sysname]
volprint -Aht > filename
voldisk list > filename
voldg list > filename
voldctl list > filename

Gather Disk Information to files on a disk other than the root disk and disks using LSM, ie:

disklabel dsk0 > /ds3/disk_label/disklabel_dsk0   (/dev/disk/dsk3c)
disklabel dsk1 > /ds3/disk_label/disklabel_dsk1

Gather System Information in a file on your workstation called sysinfo, file to gather are:

Results of the following commands

df -k
swapon -s
netstat -in
netstat -rn
disklabel dsk0 (and all the other dsk's on the system as well)
P00>>>sh dev

Make note of the CDROM device, it will be the first line of the output.

P00>>>sh  (Show all)

Make note of the Firmware Version, it will be the last line in the output

Have a full OpenVision backup made of the server before starting.
 

Make sure you have enough space in the root filesystem for the upgrade (at least 20Meg).

Shutdown databases and other software, such as tuxedo, apache, etc....

If you are unable to clear out all processes, then reboot the system.
 

Bring the server down to the prom level and check the current firmware version.

sync; sync

halt 

At the [P00>>>] prompt, type "show version".

Check this version against the minimum requirement needed for the operating system
you are upgrading (found in the Install Manual or release notes).

Reboot the server and check the installed products:

At the [P00>>>] prompt, type "boot". 

Once booted, type "setld -i | pg" to get listing of installed products. 
Make note of any non-standard products.
 

Check for the correct device name for the CDROM:

cd /dev 

file rrz*c | grep RRD - File type RRD45 is the cdrom device. 

Example:

file rrz*c | grep RRD
/dev/rz6c:  character special (8/6146) SCSI #0 RRD45 disk #48 .....
 

Shutdown system again and check for the boot drive name:

sync 

sync 

halt 

At the [P00>>>] prompt, type "show | more"
To get the name of boot drive - usually DKA0.0.0.1.0. 

Check the setting of ewa0_mode

This tells you if the system is set to Twisted Pair(10 BaseT),
FastFD(100 BaseT - Full Duplex), or Auto-Negotiate:

At the boot prompt [P00>>>], type:

sho ewa0_mode
 

To change the ewa0_mode to 100 BaseT

P00>>>set ewa0_mode FastFd 

To change ewa0_mode to auto-negotiate, the preferred setting.

P00>>>set ewa0_mode auto-negotiate
 

Now boot into single user mode:

At the boot prompt check what the boot_dev is and then boot to single user mode.

P00>>> sho boot_dev

P00>>> boot -flag s dka0.0.0.1.0  or

P00>>> boot -fl s dka0

Check and mount filesystems.

/sbin/bcheckrc  

Now insert the Operating System CD into the cdrom drive.
 

Run installupdate to upgrade the Operating System.
 
NOTE2: rz6c is used here as an example of a CDROM device.

Set environment variables:

EDITOR=vi; export EDITOR

TERM=vt100; export TERM

Start the update:

/sbin/installupdate -i /dev/disk/cdrom0c

The following messages will appear:

Initializing new version information (OSF) ... done

Update Installation has detected the following update installable products on your system:

Tru64 UNIX V5.0A Operating System ( Rev 1094 )

These products will be updated to the following versions:

Tru64 UNIX V5.1 Operating System ( Rev 732 )

It is recommended that you update your system firmware and perform a complete system backup before proceeding.  A log of this update installation can be found at /var/adm/smlogs/update.log

Do you want to continue the Update Installation? (y/n) []: y

Do you want to select optional kernel components? (y/n) [n]: y

Do you want to archive obsolete files? (y/n) [n]: n

*** Checking for conflicting software ***

You may receive the following message about the C++ Compiler if it was previously installed on the system, only st-xxxxx systems should have the C++ Compiler installed.

The following software my require reinstallation after the Update Installation is completed:

Compaq C++ Version 6.2 for Tru64 UNIX Sstems
Ladebug Debugger Version 4.0-48, for Digital UNIX

Do you want to continue the Update Installation? (y/n) [y]: y

*** Determining installed Operating System software ***

Working ...

*** Determining kernel components ***

 

 

*** KERNEL OPTION SELECTION ***

Selection Kernel Option

--------------------------------------------------------------

1 System V Devices
2 NTP V3 Kernel Phase Lock Loop (NTP_TIME)
3 Kernel Breakpoint Debugger (KDEBUG)
4 Packetfilter driver (PACKETFILTER)
5 IP-in-IP Tunneling (IPTUNNEL)
6 IP Version 6 (IPV6)
7 Point-to-Point Protocol (PPP)
8 STREAMS pckt module (PCKT)
9 Data Link Bridge (DLPI V2.0 Service Class 1)
10 X/Open Transport Interface (XTISO, TIMOD, TIRDWR)
11 Digital Versatile Disk File System (DVDFS)
12 ISO 9660 Compact Disc File System (CDFS)
13 Audit Subsystem
14 ATM UNI 3.0/3.1 ILMI (ATMILMI3X)
15 IP Switching over ATM (ATMIFMP)
16 LAN Emulation over ATM (LANE)
17 Classical IP over ATM (ATMIP)

--- MORE TO FOLLOW ---

Enter your choices or press <Return> to display the next screen.

Choices (for example, 1 2 4-6): 1 8 10 12

 
18 ATM UNI 3.0/3.1 Signalling for SVCs (UNI3X)
19 Asynchronous Transfer Mode (ATM)
20 Advanced File System (ADVFS)

The following choices override your previous selections:

21 All of the above
22 None of the above
23 Help
24 Display all options again

--------------------------------------------------------------

 Enter your choices, choose an overriding action or press <Return> to confirm previous selections.

Choices (for example, 1 2 4-6): 1 8 10 12 20

You selected the following kernel options:

System V Devices
STREAMS pckt module (PCKT)
X/Open Transport Interface (XTISO, TIMOD, TIRDWR)
ISO 9660 Compact Disc File System (CDFS)
Advanced File System (ADVFS)
Is that correct? (y/n) [y]: y

*** Checking for file type conflicts ***

Working....Wed Aug 8 11:15:15 PDT 2001

The following directories on this system conflict with assigned file types originally shipped in the operating system. This can be caused, for example, if a symbolic link is replaced with a real directory. These conflicts must be resolved before an update installation can be performed on this system. The original file status information can be found in the subset inventory files located in the /usr/.smdb. directory. For later review, this message is also logged in /var/adm/smlogs/update.log The update procedure will exit and return the system to its original state.

./home must be Directory

Returning system to Pre-Update state...done.

Exiting Update Installation...

Removing temporary update installation files...done.

A log of the Update Installation has been recorded in the file

/var/adm/smlogs/update.log.

 Exiting the installupdate process.

Do you want to return to multi-user mode (y/n) [n]:

:$ pwd

/

:$ ls -ld /home

lrwxrwxrwx 1 root system 7 May 24 2000 /home -> /pswork

:$ rm /home 

Restart the update:

:$/sbin/installupdate -i /dev/disk/cdrom0c

You will be prompted again for Kernel Options, enter those again as you did above in the section KERNEL OPTION SELECTION.

The following files on this system conflict with assigned file types originally shipped in the operating system. This can be caused, for example, if a symbolic link is changed to a file. These conflicts must be resolved in order for Update Installation to preserve your customizations. You can preserve these customizations by exiting the update and resolving the file type conflicts before restarting the Update Installation. If you continue with the update, any customizations made to these files will be lost. The original file status information can be found in subset inventory files located in the /usr/.smdb. directory. For later review, this message is also logged in /var/adm/smlogs/update.log. ./usr/ccs/lib/cmplrs/cxx/_main.o should be Symbolic Link to ../../_main.o

/tmp is a filesystem

Do you want to continue the Update Installation? (y/n) [n]: n

:$unmount /tmp

:$/sbin/installupdate -i /dev/disk/cdrom0c

You will be prompted again for Kernel Options, enter those again as you did above in the section KERNEL OPTION SELECTION.

*** Checking for obsolete files ***

 *** Checking file system space ***

ils: cannot stat /.profile (No such file or directory)

ils: cannot stat /.profile (No such file or directory)

ils: cannot stat /.profile (No such file or directory)

Update Installation is now ready to begin software load. Please check the /var/adm/smlogs/update.log file for errors after the installation is complete.

 *** Load Tru64 UNIX V5.1 Operating System ( Rev 732 ) Software Subsets ***

 checking current state of system...may take up to 10 minutes... 

xxx subsets will be installed....
Base System
....copying from /updmnt/ALPHA/BASE/....

Merge completed successfully (repeated several times) 

Exiting Update Installation.....
Server will automatically reboot.

After the reboot....configuration begins.

The following messages will appear:
 

Configuring "Base System" 

Merge completed successfully.... 

Configuring....(goes through all the subsets)
 

Now perform post-installation tasks:
 

Review logs:
cd /var/adm/smlogs

Check differences on known files (and ones in upd_custom_files).

cd /sbin 

diff /sbin/nfsmount nsfmount.PreUPD 

If the differences are for the automouter to start then -
"mv nfsmount.PreUPD nfsmount". Otherwise update the new file. 

Review the sysconfigtab and kernel config file, you should not have to make any changes everything that was there before should still be the same except for possible added items.

cd /etc/sys 

diff <hostname> <hostname>.bck 

Most likely the only change will be "maxusers".

cd /etc

diff sysconfigtab sysconfigtab.bck

Now rebuild the kernel and reboot the server:
 

cp /vmunix /vmunix.save 

doconfig -c <hostname> or just doconfig (You will be prompted for hostname).

Note: hostname is in all caps with no dashes, ie SPDEC04. 

Do not edit the config file
Display will say "performing kernel build"...
 

When the kernel build is complete:

shutdown -r now

Test out the upgrade...

Try multiple telnets from another system to ensure you can have more than three logins at
the same time. This will make sure there is no user license problems.

Startup any database servers available to be sure they come up successfully.

Once the system have been up and running and used by the user for a while, remove the root
files backed up to /data#/oldsys.
You will also need to clean up the *PreUPD files created by the upgrade process.
This can be done by running the "setup" program and selecting "Update Administration Utility"
and then "Unprotected Customized File Administration".

Adding a disk controller and disks to a Digital system.

You should have already added the controller hardware to the system.

In order to make sure the firmware can see the new controller,
stop the boot process by pushing the halt button in on the system then power up the system.

At the P00> prompt, check for the new device.

P00>show device

Note: the bus id of the new device, for example pkc0 is bus id C and DKC100 is the drive on bus C and its lun is 1.

Adding a controller with disk drives to the system:

Login as root. Save backup copies of the kernel and configuration file. SYSNAME is typically
the name of the system in caps, ie: SPDEC04 cp /vmunix /vmunix.bak cp /usr/sys/conf/SYSNAME /usr/sys/conf/SYSNAME.bak shutdown -h now

Boot genvmunix.

This kernel has all available drivers loaded. It will recognize the new hardware.
You should see the new device during boot.

Login as root and create a new configuration file.

The output of the sizer command is a configuration file that contains the statements for the
new device. It is put in /tmp with the name you specified on the command line.

sizer -n SYSNAME

diff /usr/sys/conf/SYSNAME /tmp/SYSNAME|more

Find the statements that contain the new device information and edit /usr/sys/conf/SYSNAME to add the statements.

Create the new kernel. /usr/sbin/doconfig -c SYSNAME Once successfully completed, move the new kernel into place. mv /usr/sys/SYSNAME/vmunix /vmunix shutdown -r now You should see the new device during the boot process. 

Build the device files for the disks.

Digital uses a formula to calculate the device number. You will need the bus id and the lun of
the drive.
The bus letter signifies a digit. Bus A=0, B=1, C=2 etc.
The formula is: bus id * 8 + lun.
The lun is the scsi id on the disk, in the following example, it is 1 and this disk is a RZ29B.
For example disk DKC100 would be: (bus id C=2) 2 * 8 + 1 = 17. cd /dev ./MAKEDEV rz17 There will be a device file for each partition of the disk. You can now label the disk and newfs the partition you want  to use.

Partition disks using the disklabel command.

At the type of installation selection:

Default Installation

Custom Installation

Unix shell

Select Option 3 - Unix Shell 

At the unix "#" prompt, type:
 

TERM=vt100; export TERM 

EDITOR=vi; export EDITOR 

Disk Partition and File System Layout guidlines for the Operating System with  2 - 2GB disks and 1024MB of memory.

Disk Partition and File System Layout guidelines for the Operating System with 2 - 4GB disks and 1024MB of memory.

disklabel -r /dev/rz0

This reads the disk label informatin.
You may not have device rz0, it could be rz8 etc....., rz0 is just an example but in
most cases you will have rz0.

If you receive an error then the disk is unlabeled, do the following to label the disk:

cd /dev

./MAKEDEV rz0  (For Tru64 5.0 and above you will not have to issue this command)

disklabel -z rz0  ( This will mark all file system types as unused )

disklabel -wr -t ufs rz0 RZ1CB-CA (Label the disk with default partitions, to find the type of disk do the following)

# cd /dev/rdisk

# file dsk?   You should see the type of disk, ie: RZ1CB-CA

disklabel -e rz0 (This will put you in the editor mode to change partition sizes, if you plan to use the whole disk, ie: the 'C' partition you won't need to run this command to partition the disk, just newfs /dev/rdisk/dsk?c) 

Example of a modified Partition Table:

The sizes and offsets are in 512byte blocks.

Partition Sizes and File System Mount Points as per the partition layout below:

     1024 byte block                 512 byte block

Calculate the size, ie:  128*2048 = 262144

a = 134,217,728 MB       /             262144*512     (128*2048=262122)

b = 805,306,368 MB     swap         1572864*512     (768*2048=1572864)

c = 4,290,600,960 GB                   8380080*512        Entire disk

e = 2,122,317,824 GB   /ds1         4145152*512    (2024*2048=4145152)

f = 256,901,120 MB      /tmp         501760*512    (245*2048=501760)

g = 717,225,984 MB     /usr           1400832*512     (684*2048=1400832)

h = 254,631,936 MB     /var           497328*512    (left over)

	Click on Volumes from the left box
	Click on New from the Tool Bar
	The following is already selected: Disk Group Name - Volume Name
	Click on Maxsize if you want to use the entire volume size otherwise enter the size you want the file system to be.
	Click on Concatenated if non-raid.
	Click on Assign Disks Click on the disks you want to use from the display and press OK.
	Click on Add File System and enter Mount Point
	Click on ufs
	Click OK
	Click OK to start the creation

LSM Disk Mirroring:

Initialize the Volumes:

/usr/sbin/volsetup   (If you need to re-initialize the volumes you will need to use the -o force option, ie:  /usr/sbin/volsetup -o force)

Enter the disk(s) to add into the rootdg disk group.
NOTE:  Enter a blank line to end the list of disks. 

Examples below -  Using dsk14 and dsk15:

dsk14
dsk15

Initialize vold and the root disk group:
Add disk dsk14 to the root disk group as dsk14:
Addition of disk dsk14 as dsk14 succeeded.
Add disk dsk15 to the root disk group as dsk15:
Addition of disk dsk15 as dsk15 succeeded.
Initialization of vold and the root disk group was successful.

Create the volmirror leaving enough space for logging, ie: subtract the size of logging from the total size of the volumes.  Issue the following comand to see the size of the volumes.

/sbin/volprint -h

Disk group: rootdg

TY   NAME              ASSOC           KSTATE       LENGTH    PLOFFS    STATE   TUTILO  PUTILO
dg   rootdg             rootdg

dm  dsk14              dsk14                             286745376
dm  dsk15              dsk15                             286745276

You will need to subtract the logsize from the LENGTH of the volume above to reserver space for the logs.  To use 2 blocks the calculation is:

512*2048=1048576
286745376-1048576=285696800

The minimum DRL length is 65 blocks for a cluster environment, and 2
blocks for a non-cluster environment. By default, LSM configures a
larger log subdisk for the DRL than needed. This allows you to use the
volume if the system becomes a Tru64 UNIX cluster member. If you con-
figure a DRL size less than 65 blocks for a non-cluster environment,
DRL is disabled for that volume if you later migrate it to a cluster
environment.

Create the volumes for the mirror:

Add the logs for the mirrored volumes:

Print mirror information:

Now create a file system using the newly created volume.

Perform a full listing of the volumes:

	Compaq C Compiler
	Visual Threads
	Ladebug
	Graphical Program Analysis Tools
	Program Analysis Tools

1. Uncompress and unpack the downloaded tar file:
   # gunzip -dc xxxnnn.tar.gz | tar xvf -
   This creates a unique subdirectory in your scratch directory, for each component.
2. See Preinstallation Requirements and the component-specific installation and release notes and perform any
   action required prior to the component's installation.
3. Check for the presence of any currently installed subsets for the component and delete all of them:
   # /usr/sbin/setld -i
   # /usr/sbin/setld -d currently-installed-subset

Some components have multiple subsets. The following example shows how to list any installed subsets whose
names include "GPA":
# /usr/sbin/setld -i | grep GPA | grep installed

4. Install the new version from the component's kit subdirectory. For example:
   # /usr/sbin/setld -l Component_Directory/kit
   See Directory Structure for the component directory name.
5. Repeat steps 4 through 8 for each component to be installed.
6. When finished installing, you can delete the scratch directory, if desired.

It contains the indicated versions of the following components:

	Compaq C (V6.1-110), formerly DEC C, is a standards-compliant, multidialect, and feature rich implementation of the C language. It contains a highly optimizing code generator specifically designed to exploit the 64-bit Alpha architecture. It is particularly well-suited and contains extended support for systems programming, parallel programming, and mathematical computing.
	Visual Threads (V1.1-015) lets you analyze and debug multithreaded applications for problems such as deadlock, protection of shared data, and thread usage errors. It can also be used to monitor the thread-related performance of the application.
	Ladebug (V4.0-54) debugger is a powerful fully symbolic source-level debugger that helps you locate run-time errors (bugs) in your code.
	Graphical Program Analysis Tools (V2.0-7) make it easy to analyze a program for efficiency, memory bugs, and the use of shared resources.
	Program Analysis Tools (V1.0) help profile and debug applications through new commands that speed learning and use. They offer new defaults and options, improved support for pthread applications, and new reference pages and tutorials.

The software and documentation for each component are contained in a compressed tar file that can be downloaded
from this site (no printed documentation is provided with this Supplement).

This new version of Compaq C provides:

	A proven and reliable compiler that incorporates many important bug fixes from previous versions.
	An improved code generator/optimizer that exploits the latest Alpha hardware technology.
	A significantly improved diagnostic facility: better messages, more messages (including uninitialized variable detection, run-time array bounds checking, and unused header file detection), and improved command-line and #pragma diagnostic controls (including lint-style message groups).
	A full implementation of the OpenMP Parallel Programming API for shared memory multi-processing.
	New features from C9X (the proposed revision to the ANSI/ISO C Standard), including restricted pointers, variable length arrays, interspersed declarations and statements, and initializers with designators.

Installation

Visual Threads lets you analyze and debug multi-threaded applications. It can be used to:

	Automatically diagnose common problems such as deadlock, protection of shared data, and thread usage errors.
	Monitor the thread-related performance of the application, helping you identify bottlenecks or locking granularity problems.

It is a unique debugging tool because it can be used to identify problem areas even if an application does not show
any specific problem symptoms. Visual Threads provides the following:

	Event Collection: Collects detailed information about the significant thread state changes that occur during the running of a multithreaded application.
	Event Display: At any time, you can view the dynamic display of events as they occur, with options to filter for specific types of events.
	Automatic Rule-based Analysis: Detects violation conditions by evaluating the events against a set of enabled rules. Several predefined rules look for data protection errors, deadlock conditions, and programming errors.
	Rule Customization: Lets you use templates to define your own rules to specify criteria for violation conditions. In particular, you can specify rules to monitor or identify performance problems.
	Customized Actions: Suspends execution of the application when it detects violation conditions. You can choose from several options at this point, including invoking the debugger in the appropriate context for the application.
	Playback: Records events to a trace file so you can play back and analyze them later. This is especially useful if you want to analyze a trace file iteratively, perhaps using different rules each time as you discover more information.
	Statistics: Provides easy access to object-level statistics and current state information, including use of resources (for example, the mutexes held by a particular thread). You can use this information to look for performance problems and to fine tune the application.
	Thread and Event Visualization: Graphically and continuously displays the state of the program threads and the frequency of thread related events.

New features for this version of Visual Threads include many user interface enhancements, and:

	The ability to specify application environment variables from within the Visual Threads GUI.
	The command vttrace can be used to create a trace file outside the Visual Threads GUI.
	A new statistic for monitoring cumulative locked and wait time on locks.
	Control panel additions: scrolling capability, lines or tickmarks to show the number of CPUs (and compare to active threads), and multiple colors to distinguish blocked threads.

Installation

The Ladebug debugger is a powerful fully symbolic debugger that helps you locate run-time errors (bugs) in your code.
Key features allow you to:

	Perform source-level debugging
	Attach to a running process
	Debug programs with shared libraries
	Debug multithreaded applications
	Debug multiprocess applications, including programs that fork/exec
	Perform remote client/server debugging
	Perform kernel debugging
	Provide internationalization support for local language characters

The Graphical Program Analysis Tools make it easy to analyze the run-time behavior of a program for efficiency,
memory bugs, and use of shared resources. The tools include:

	Process Viewer: Graphically displays performance information about processes and child processes running on specified (local or remote) Tru64 UNIX systems.
	Memory Profiler: Graphically displays how your application uses memory over the course of its execution, for example, showing how much is allocated for various purposes and how frequently your application is allocating and deallocating memory. This tool helps you understand if an application uses memory inefficiently, for example, fragmented memory allocations.
	Performance Profiler: Gathers and analyzes, in graphical form, run-time statistics on your application, such as CPU usage by function or line and test coverage.
	Heap Analyzer: Finds and displays in graphical form memory errors and memory leaks in your application.
	Man Page Browser: Used for searching, navigating, and printing manpages in a graphical, scrollable hypertext window.

Installation

The Program Analysis Tools help profile and debug applications through shell commands. The tools in this version
provide new commands that speed learning and use. They offer new defaults and options, improved support for
pthread applications, and new reference pages and tutorials. The tools include:

	Hiprof: A call-graph profiler that collects information on the cpu-time that a program uses. It instruments the program, executes it, and displays the profile using an improved gprof. A new profiling style provides an enhanced alternative to traditional cc -pg profiling, allowing shared libraries to be profiled and per-source-line cpu-time to be displayed.
	Pixie: An instrumenting instruction-count profiler, primarily for use in profile-directed optimization (with the cc command's -feedback, -cord, and -om options) and test coverage analysis. This version of pixie supports recent compiler releases and provides per-thread profiles. A new prof command allows the display of per-source-line profiles for the cc -p and uprofile profilers.
	Third Degree: A memory-access checker. It instruments a program, executes it, and displays a log of memory-related errors that it detected. By default, the third command unintrusively checks for memory leaks and malloc/free errors. Optionally, it can also report accessing invalid addresses and reading uninitialized heap and stack. The new -g option allows the instrumented program to be debugged while running checks.
	Atom: A framework for writing new program analysis tools. Atom provides a high level API to its instrumentation services, so that a new tool's instrumentation and run-time analysis code can be implemented in a few lines of C. The API is compatible with the prerequisite Tru64 UNIX header files, and the new -g and -w options help debug and productize tools.

Installation

	Preinstallation Requirements
	Installation Instructions
	Component-Specific Installation and Release Notes

	The Developers' Toolkit Supplement, Version 4.0F can be installed on any of the following operating systems:
	DIGITAL UNIX Version 4.0D
	DIGITAL UNIX Version 4.0E
	Tru64 UNIX Version 4.0F

Additional preinstallation requirements for each component follow:

	Compaq C
	Visual Threads
	Ladebug
	Graphical Program Analysis Tools
	Program Analysis Tools

Before installing this new version of Compaq C:

	Delete any earlier versions of this kit:
	# /usr/sbin/setld -d DTKCMPLR410 DTKCMPDOC410 # /usr/sbin/setld -d DTCCMPLR100 DTCCMPDOC100
	Delete any Developers' Toolkit Supplement driver patch kits:
	# /usr/sbin/setld -i | grep DTAPATCH # /usr/sbin/setld -d subset-name

Preinstallation requirements for Visual Threads are as follows:

	Tru64 UNIX subsets OSFBASE425 or higher and OSFPGMR425 or higher are required. Subset OSFLIBA425 or higher is optional but is required for instrumentation rules such as race detection.
	Java Run-time Environment (JRE) Version 1.1.7B-2 (subset JAVJRE117) or any higher version of JRE Version 1.1 is required. However, JRE Version 1.2 is not supported (from any Java subset).

If no acceptable JRE subset is installed, Visual threads tries to validate that /usr/bin/java (provided by
either an OSFJAVA or JAVA11 subset) is an acceptable version to use.

You can download Java from Compaq's Web site for Java on Tru64 UNIX.

	The Atom instrumentation toolkit provided with the Program Analysis Tools V1.0 (included in this Developers' Toolkit Supplement) is required.
	The Help system support, GPABASE207 (provided with the Graphical Program Analysis Tools included in this Developers' Toolkit Supplement), is required.
	The Ladebug debugger included in this Developers' Toolkit Supplement is recommended, although not required.

Preinstallation requirements for the Program Analysis Tools are as follows:

	If an Atom Advanced Development Kit (ATMBASE400 subset) is installed, it must be deleted before installing any required operating system patch kit or the Program Analysis Tools included in this Developers' Toolkit Supplement.
	Using a version of the Graphical Program Analysis Tools other than the one included in this Developers' Toolkit Supplement is not recommended when this Program Analysis Tools component is installed.

	Compaq C Compiler
	Visual Threads
	Ladebug
	Graphical Program Analysis Tools
	Program Analysis Tools

1. Uncompress and unpack the downloaded tar file:
   # gunzip -dc xxxnnn.tar.gz | tar xvf -
   This creates a unique subdirectory in your scratch directory, for each component.
2. See Preinstallation Requirements and the component-specific installation and release notes and perform any
   action required prior to the component's installation.
3. Check for the presence of any currently installed subsets for the component and delete all of them:
   # /usr/sbin/setld -i
   # /usr/sbin/setld -d currently-installed-subset

Some components have multiple subsets. The following example shows how to list any installed subsets whose
names include "GPA":
# /usr/sbin/setld -i | grep GPA | grep installed

4. Install the new version from the component's kit subdirectory.
   For example:
   # /usr/sbin/setld -l Component_Directory/kit
   See Directory Structure for the component directory name.
5. Repeat steps 4 through 8 for each component to be installed.
6. When finished installing, you can delete the scratch directory, if desired.

Before installing any component, please read the following component-specific documents in addition to the
Preinstallation Requirements:

	Compaq C installation
	Compaq C release notes
	Visual Threads installation
	Visual Threads release notes
	Ladebug release notes
	Ladebug internationalization notes
	Graphical Program Analysis Tools installation
	Graphical Program Analysis Tools release notes
	Program Analysis Tools release notes

Boot the system in single user mode, you will not be asked for a password, change the password and reboot the system.

boot -flags s

Gather System Information.

Run the following command to gather system information:

# /usr/sbin/sys_check

The system information will be placed in /var/recovery/sys_check

Display current swap space configured on system.

swapon -s

Update the memory copy of the sysconfigdb database and list entries in the /etc/sysconfigtab database after modifying the /etc/sysconfigtab file.

Update the memory copy of the sysconfigdb database, you don't need to reboot when this command is used.

/sbin/sysconfigdb -s

List the whole sysconfigdb database

/sbin/sysconfigdb -l

List just the shared memory parameters

/sbin/sysconfigdb -l ipc

Display Firmware Level, CPU's, Disks, Hardware/Software Detected
problems, and other usefull information.

From the console prompt [P00>>>], boot to single user mode, you will not be asked for a password when booting to single user mode.

boot -fl s

Recovering the root password

If you have forgotten the root password and cannot sudo into the system here is how to reset the root password. Shutdown the system, you will probabally have to halt the system by pressing the halt button on the front of the system, then press the reset button to reboot the system.   It will boot up to the boot prompt, here you can boot to single user mode. P00>>>boot -flag s When the system is up at the root prompt '#' do the following. mount -u /  (Sets the root volume to writable) bcheckrc  -  (Checks and mounts file systems) passwd root  ( Set the root password, once set reboot the system) Press the halt button on the front of the system so the system will boot multi-user. shutdown -r now

Creating and Administering the UNIX File System