Installing C++ version 3.0 (on AIX PS/2)
----------------------------------------
Note:  You must have the following lpps available on your system:
	AIX PS/2 Operating System Extensions Version 1.3
	AIX PS/2 Application Development Toolkit Version 1.3
	AIX PS/2 Extended C Language (Version 1.2.1, I believe)
	 
The installation process consists of:
 
1. extracting the translator, libraries, man pages, and
   include files from a tarfile
2. creating a symbolic link named /bin/CC which points to the installed
   translator
3. installing the man pages onto your system.
4. printing off the manuals.
 
 
The installation process creates the following directory structure:
 
                               /usr/bin/c++
         +---------------------------+--------+
         |                                    |
        2.0                                  3.0
<reserved for 2.0>                            |
                                        +-----+-----+------+
                                        |     |     |      |
                                       bin include lib    man
 
 
Proceed as follows:
0. un-terse the file on VM: terse aixrsc++ ps30tar a = tar = (unpack
1. ftp the tarfile to "/tmp/c++30ps.tar" using "binary" transfer mode
2. "su root"
3. "cd /usr/bin"  (or some other directory)
4. "tar xf /tmp/c++30ps.tar"
5. "cd c++/3.0"
6. "./UseNewCC"
7. determine where your man pages are installed (usually /usr/man)
8. "install_man /usr/man" (replace /usr/man with the correct
   path if necessary)
9. See the README PS-30 file on VM for instructions on printing off the
   USL manuals.
 
Notes:
1. If you wish to place the translator in some other directory, be sure
   to read and follow the comments in the "CC" shell script.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                     MORTHANC Notes:
                     ~~~~~~~~~~~~~~~
You may want to issue TOOLS SUBSCRIBE commands to automatically be sent
updates to the C++ 3.0 package.  Here is a list of useful commands to help
you set up the SUBSCRIBE for your needs:
 
1) To determine all of the SUBSCRIBEs that you have currently set, issue:
   TOOLS SENDTO TOROLAB6 MORTHANC IBMC++UG QUERY INFORM
2) To add a SUBSCRIBE for <fn> <ft>, issue:
   TOOLS SENDTO TOROLAB6 MORTHANC IBMC++UG SUBSCRIBE <fn> <ft>
3) To cancel a SUBSCRIBE for <fn> <ft>, issue:
   TOOLS SENDTO TOROLAB6 MORTHANC IBMC++UG UNSUBSCRIBE <fn> <ft>
4) This file is part of the C++ 3.0 package.  If you have upgraded to C++ 3.0
   and no longer require updates to C++ 2.0, you should consider (a) getting
   a list of all your subsciptions, (b) unsubscribing from all the PSTRSTAR
   files, and (c) subscribing to the PS30TAR files.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Change History:
~~~~~~~~~~~~~~~
------------------------------------------------------------------------
09 Oct 1992, Martin Lansche, Level 3.0.1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Welcome to C++ 3.0!
   In addition to the enhancement of the language by Unix Software Lab
(USL), the following enhancement has been made to internal packaging:
   - "man" pages are included in the tar image.
   - the USL documentation is available via the MORTHANC mechanism
      - softcopy images (PostScript format) are shipped to your VM id.
      - each licensee is entitled to make ONE and only ONE hardcopy
        from these PostScript images.
      - the Documentation shipped:
        - C++ Language System Release 3.0 Selected Readings
        - C++ Language System Release 3.0 Release Notes
        - C++ Language System Release 3.0 Product Reference Manual
        - C++ Language System Release 3.0 Library Manual
Notes:
   - the Selected Reading Document contains excellent chapters for using
     templates.
   - This has been ported using AIX PS/2 1.3.  I have no idea if it will
     work on AIX 1.2, or 1.2.1.  At the very least, the header files
     will be grossly out of sync.
   - The AIX system, and compiler header files contained virtually no
     function prototypes.  Therefore, I have not followed my usual AIX
     practice of 'wrapper' files which include the system files.  Instead
     I have shipped entire replacement header files, with the contents 
     corrected.  This will cause great grief whence PTFs are applied to
     the system header files, as there is no way to incorporate my fixes
     into the system header files.
   - I have made my best guess at prototypes for system functions.  I know
     that I will have made errors.  Prototypes may be incorrect.  I may
     have coded prototypes for functions which do no exist in any system
     library. And I will surely have missed many function prototypes.
     Please send corrections to the C++CFRNT FORUM, and manually change
     your header files.  Periodically, I will refresh the package, and
     fix as many header file problems at once (instead of many small
     changes via many refreshes).
 
(MRL) 09 Oct 92
