install.script

Software Testing Automation Framework (STAF)的开发代码

:eul.
:li.You can now delete the temporary directory where you unzipped
the STAF installer file, if desired.
:xmp.
  rm -Rf /QIBM/stafinst
:exmp.  
:eol.
:p.
Follow these instructions to start STAFProc:
:p.
:ol.
:li.Change to the OS/400 PASE environment by typing the following
from the AS/400 command line.  Skip this step if you're already in
the OS/400 PASE environment from the above steps for installing STAF.
You must run STAF in the OS/400 PASE environment.
:xmp.
  CALL QP2TERM
:exmp.
:li.Change to the directory where you installed STAF and run STAFEnv.sh
to set the necessary environment variables to use STAF:
:xmp.
  cd /QIBM/staf
  . ./STAFEnv.sh
:exmp.
:p.Running STAFEnv.sh should set the following environment variables
needed to use STAF:
:ul compact.
:li.export PATH=/QIBM/staf/bin&colon.$PATH
:li.export LIBPATH=/QIBM/staf/lib&colon.$LIBPATH
:li.export CLASSPATH=/QIBM/staf/lib/JSTAF.jar&colon.$CLASSPATH
:li.export STAFCONVDIR=/QIBM/staf/codepage
:eul.
:li.Type "STAFProc &" to launch STAF in the background.
Note probably you'll want to start STAFProc using nohup so that when
you exit your connection to the OS/400 machine, STAFProc will still
be running.  When using nohup, the output from STAFProc (including
information on if an error occurred starting STAFProc) will be
redirected to file nohup.out in the current directory (or you can
specify to redirect the output to another file).
:xmp.
  nohup STAFProc &
:exmp.
:eol.
:p.
Note that the default shell for processes is /bin/sh.  If you need to use
the "qsh" shell for the OS/400 PASE environment, then you will either need
to specify :xmp.  SHELL "/QOpenSys/usr/bin/qsh -c %C":exmp. for PROCESS START
requests, or change the default shell by adding the following line to your
STAF.cfg file:
:xmp.
  SET DEFAULTSHELL "/QOpenSys/usr/bin/qsh -c %C"
:exmp.
You must shutdown and restart STAFProc for any changes to the STAF.cfg
file to take effect.

.*---------------------------------------------------------------------
:i2.z/OS
:h2 id=zosinst.z/OS installation
:h3.Setup instructions for STAF on z/OS
:p.Note: STAF will only run on z/OS V1.4 or newer.  STAF's Java support on
z/OS requires JDK 1.4.1 or newer.
:p.To install STAF on z/OS, you should follow the steps described in
:hdref refid=unixsti..
:p.It is critical that you remember to make set the _CEE_RUNOPTS environment variable.  Failure to set this variable will prevent STAF from working properly.
The proper setting should be
:xmp.
_CEE_RUNOPTS="posix(on)"
:exmp.
:p.If you did not install STAF in the default /usr/local/staf directory, 
STAFCONVDIR must be be set to the STAF codepage directory.

.*---------------------------------------------------------------------
:ih1.installation
:i2.Environment Variable Settings
:h2 id=envvars.Environment Variable Settings
:p.STAF requires setting some environment variables to run.
If you performed an InstallShield install and selected an option to have
the install update the environment variables, these environment
variables should already be updated for STAF.  Otherwise, you must set
these environment variables yourself.  In most cases, you'll probably
want to set these environments for the system so that they are always
set even after logging out or rebooting.  However, if you are going
to be running two or more versions of STAF on the same machine, the
install creates STAFEnv script files that you can use to easily switch
environment settings for each version of STAF.
See section :hdref refid=multipleInstances. for more information on
using the STAFEnv script files when running multiple instances of STAF
on the same machine.
:p.  
Please verify that the following environment variables have been set as
follows before using STAF:
:ul.
:li.Windows:
:ul compact.
:li.PATH must contain the STAF bin directory in order to start STAFProc
or to communicate with STAF (e.g. C:\STAF\bin).
Also, if you're going to be communicating with STAF from Java
programs or registering STAF Java services, PATH should also contain
the Java bin directory (e.g. C:\j2sdk1.4.2_05\bin).
:li.CLASSPATH must contain the JSTAF.jar file (e.g. C:\STAF\bin\JSTAF.jar).
JSTAF.jar contains the STAF Java APIs to communicate with STAF from
Java programs and is also required to register STAF services written in Java.
:li.STAFCONVDIR must be be set to the STAF codepage directory if you did not
install STAF in the default C:\STAF directory.
:li.STAFCODEPAGE must be set on systems which don't return a valid value
from nl_langinfo(CODESET) (specifically if that call returns NULL or the
empty string).  The value of this variable should contain the codepage
being used by the system.  See codepage/alias.txt for valid values.
If you are unsure, use "LATIN_1".
:eul.
:p.
:li.Unix:
:ul compact.
:li.PATH must contain the STAF bin directory in order to start STAFProc
(e.g. /usr/local/staf/bin).
Other windows need only have the STAF bin directory in the PATH if you did not
allow softlinks to be created in the default system directories.
Also, if you're going to be communicating with STAF from Java
programs or registering STAF Java services, PATH should also contain
the Java bin directory (e.g. /opt/IBMJava2-142/bin).
:li.LD_LIBRARY_PATH (LIBPATH on AIX, OS/400, and z/OS systems, SHLIB_PATH on HP-UX
systems) must contain the STAF lib directory (e.g. /usr/local/staf/lib),
unless you allowed softlinks to be installed in the default system directories
:li.CLASSPATH must contain the JSTAF.jar file (e.g. /usr/local/staf/lib/JSTAF.jar).
JSTAF.jar contains the STAF Java APIs to communicate with STAF from
Java programs and is also required to register STAF services written in Java.
:li.STAFCONVDIR must be be set to the STAF codepage directory if you did not
install STAF in the default /usr/local/staf directory.
:li.STAFCODEPAGE must be set on systems which don't return a valid value
from nl_langinfo(CODESET) (specifically if that call returns NULL or the
empty string).  This is known to be true on Solaris 2.6.  The value of this
variable should contain the codepage being used by the system.  See
codepage/alias.txt for valid values.  If you are unsure, use "LATIN_1".
:li.:hp2.(z/OS only):ehp2. _CEE_RUNOPTS must be set to "posix(on)".
:eul.
:p.
:li.OS/400 (iSeries)
:ul compact.
:li.PATH must contain the STAF bin directory in order to start STAFProc
or to communicate with STAF (e.g. /QIBM/staf/bin).
Also, if you're going to be communicating with STAF from Java
programs or registering STAF Java services, PATH should also contain
the Java bin directory.
:li.LIBPATH must contain the STAF lib directory (e.g. /QIBM/staf/lib).
:li.CLASSPATH must contain the JSTAF.jar file
(e.g. /QIBM/staf/lib/JSTAF.jar).
JSTAF.jar contains the STAF Java APIs to communicate with STAF from
Java programs and is also required to register STAF services written in Java.
:li.STAFCONVDIR must be be set to the STAF codepage directory
(e.g. /QIBM/staf/codepage)
:li.STAFCODEPAGE must be set to LATIN_1.
:eul.
:eul.

.*---------------------------------------------------------------------
:ih1.installation
:i2.Installing Multiple Instances of STAF
:h2 id=instMultiple.Installing Multiple Instances of STAF
:p.
You can install different versions of STAF on the same machine in
different locations.  You can also run multiple instances of the
same or different versions of STAF at the same time on a single machine.
See section :hdref refid=multipleInstances. for more information on
running multiple instances of STAF on a single machine.

.*---------------------------------------------------------------------
:ih1.installation
:i2.Installation Problems
:h2 id=instproblems.Installation Problems
:p.If you have a problem while installing STAF, please check the
.*b2h html <A HREF="http://staf.sourceforge.net/current/STAFFAQ.htm#d0e1393">STAF V3 FAQ</A>,
particularly section 3.2 "STAF Install Questions" under 
section 3 "Debugging STAF".
:p.If you have a problem starting STAFProc, please be sure that the
necessary environment variables have been set for STAF
(see section :hdref refid=envvars.).  Also, check the
.*b2h html <A HREF="http://staf.sourceforge.net/current/STAFFAQ.htm">STAF V3 FAQ</A>.
:p.If you are getting an error such as "Error while loading shared libraries:
libstdc++.so.6: cannot open shared object file: No such file or directory"
when starting STAFProc on Linux, then see :hdref refid=oscompatibility..

.*---------------------------------------------------------------------
:ih1.installation
:i2.Operating System Library Compatability (Linux)
:h2 id=oscompatibility.Operating System Library Compatability (Linux)
:p.Some platforms (such as Linux) on which we build and provide STAF
are linked to C++/GCC operating system libraries.  In previous versions of STAF,
these operating system library files were packaged/installed with STAF.  However,
these library files could cause some incompatibility issues with the operating
system and other native applications.  Starting in STAF V3.2.0, these library
files will no longer be packaged/installed with STAF.  However, in order to run
STAF on these platforms, you will need these library files or compatible
library files.
:p.As a STAF user, what this means is that you may need to make some one-time
setup/configuration changes on your test machine(s) in order to get STAF V3.2.0
or later working correctly.  There are several possible user scenarios:
:ul.
:li.STAFProc starts successfully on your platform.  This means that the
operating system currently has compatible C++/GCC library support.
:li.When attempting to start "STAFProc" or "staf", you receive a message such as:
"Error while loading shared libraries: libstdc++.so.6: cannot open shared
object file: No such file or directory".  This means that the operating system
does not have compatible C++/GCC libraries.  There are several ways to resolve
this problem:
:ul.
:li.Install the compatability libraries for your operating system.  The steps to
install these libraries will vary depending upon the operating system and level.
For example, on RHEL4, using the install media, under "Package Group Selection",
select "Development" and then select "Legacy Software Development".
:li.Build STAF on your operating system.  Follow the instructions in the
"STAF V3 Developer's Guide" (http://staf.sourceforge.net/current/stafdg.html).
:li.Use the library files from our STAF build machines in the table below.  It
is up to the user to decide how to install the files on their operating system(s).
In previous versions of STAF, these files were installed in
/STAF/Config/STAFRoot}/lib (and the files were accessible due to this directory
being included in the LD_LIBRARY_PATH environment variable).
:eul.
:li.When attempting to start "STAFProc" or "staf", you receive a message such
as: "/lib64/libgcc_s.so1: version `GCC_4.2.0` not found (required by
/usr/local/staf/lib/libstdc++.so.6)". This means that the operating system
has incompatible C++/GCC libraries in the library path. There are several ways
to resolve this problem: e.g. Remove the /usr/local/staf/lib/... libraries if
present.
:eul.
:p.Here are the affected operating systems and details about the specifc platforms
on which we build STAF:
:table cols='* * 2* *'.
:tcap.Operating Systems
:thd.
:c.OS Name
:c.STAF Installers
:c.OS Details
:c.Library file(s)
:ethd.
:row.
:c.Linux IA32
:c.STAF32x-setup-linux.bin
STAF32x-setup-linux.jar
STAF32x-linux.tar.gz
:c.Red Hat Linux release 8.0 (Psyche)
:p.gcc version 3.4.0, GNU Make version 3.79.1
:p.Linux 2.4.20-28.8 #1 Thu Dec 18 12:53:39 EST 2003 i686 i686 i386 GNU/Linux
:p.GNU C Library stable release version 2.3.2
Compiled by GNU CC version 3.2 20020903 (Red Hat Linux 8.0 3.2-7).
Compiled on a Linux 2.4.9-9 system on 2003-11-05.
:c.
.*b2h html <A HREF="http://staf.sourceforge.net/oslibs/linux-ia32/libstdc++.so.6">libstdc++.so.6</A>
:p.
.*b2h html <A HREF="http://staf.sourceforge.net/oslibs/linux-ia32/libgcc_s.so.1">libgcc_s.so.1</A>
:row.
:c.Linux AMD64
:c.STAF32x-linux-amd64.tar.gz
:c.Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
:p.gcc version 3.4.6 20060404 (Red Hat 3.4.6-3), GNU Make 3.80
:p.Linux 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
:p.GNU C Library stable release version 2.3.4
Compiled by GNU CC version 3.4.6 20060404 (Red Hat 3.4.6-2).
Compiled on a Linux 2.4.20 system on 2006-07-04.
:c.
.*b2h html <A HREF="http://staf.sourceforge.net/oslibs/linux-amd64/libstdc++.so.6">libstdc++.so.6</A>
:row.
:c.Linux IA64
:c.STAF32x-linux-ia64.tar.gz
:c.Red Hat Enterprise Linux AS release 3 (Taroon Update 6)
:p.gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-53)
:p.Linux 2.4.21-20.EL #1 SMP Wed Aug 18 20:30:22 EDT 2004 ia64 ia64 ia64 GNU/Linux
:p.GNU C Library stable release version 2.3.2
Compiled by GNU CC version 3.2.3 20030502 (Red Hat Linux 3.2.3-53).
Compiled on a Linux 2.4.20 system on 2005-09-16.
:c.
.*b2h html <A HREF="http://staf.sourceforge.net/oslibs/linux-ia64/libstdc++.so.5">libstdc++.so.5</A>
:row.
:c.Linux PPC64 (32-bit Java support)
:c.STAF32x-linux-ppc64-32.tar.gz
:c.SuSE SLES-8 (PPC) VERSION = 8.1
:p.gcc version 3.2.2
:p.Linux 2.4.21-309-pseries64 #1 SMP Tue May 16 22:59:04 UTC 2006 ppc64 unknown
:p.GNU C Library stable release version 2.2.5
Compiled by GNU CC version 3.2.2.
Compiled on a Linux 2.4.19 system on 2006-01-26.
:c.
.*b2h html <A HREF="http://staf.sourceforge.net/oslibs/linux-ppc64-32/libstdc++.so.5">libstdc++.so.5</A>
:p.
.*b2h html <A HREF="http://staf.sourceforge.net/oslibs/linux-ppc64-32/libgcc_s.so.1">libgcc_s.so.1</A>
:row.
:c.Linux PPC64 (64-bit Java support)
:c.STAF32x-linux-ppc64-64.tar.gz
:c.SUSE LINUX Enterprise Server 9 (ppc) VERSION = 9 PATCHLEVEL = 2
:p.gcc version 3.3.3 (SuSE Linux)
:p.Linux 2.6.5-7.191-pseries64 #1 SMP Tue Jun 28 14:58:56 UTC 2005 ppc64 ppc64 ppc64 GNU/Linux
:p.GNU C Library stable release version 2.3.3 (20040412)
Configured for ppc-suse-linux.
Compiled by GNU CC version 3.3.3 (SuSE Linux).
Compiled on a Linux 2.6.5 system on 2005-06-05.
:c.
.*b2h html <A HREF="http://staf.sourceforge.net/oslibs/linux-ppc64-64/libstdc++.so.5">libstdc++.so.5</A>
:p.
.*b2h html <A HREF="http://staf.sourceforge.net/oslibs/linux-ppc64-64/libgcc_s.so.1">libgcc_s.so.1</A>
:etable.