HP NonStop Tuxedo 8.0 Supplement for H-Series RVUs Next Version and Copyright Information Published June 2005 Table of Contents What's New in This Supplement About This Supplement Who Should Read This Supplement Related Reading Notation Conventions Hypertext Links General Syntax Notation Notation for Messages 1. Introduction Overview Running in a Non-Standard Location 2. Installation Installing NonStop Tuxedo 3.
Portability Examples See Also buildserver Name Synopsis Description Environment Variables Portability Examples See Also Standards Conformance buildwsh Name Synopsis Description Portability 5.
What's New in This Supplement Prev Next What's New in This Supplement This is a new, supplemental manual. Information in this manual are changes to information in the NonStop Tuxedo 8.0 manual set that are specific to H-series releases. Prev HP NonStop Tuxedo 8.
About This Supplement Prev Next About This Supplement Who Should Read This Supplement Related Reading Notation Conventions Hypertext Links General Syntax Notation Notation for Messages This supplemental manual describes the changes made in NonStop Tuxedo 8.0 for H-series systems. Who Should Read This Supplement Readers of this supplemental manual include system administrators, application programmers, and analysts. Related Reading This supplemental manual should be used with the NonStop Tuxedo 8.
General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: FORCED lowercase italic letters Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times.
Notation for Messages This list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Object name does not exist lowercase italic letters Lowercase italic letters indicate variable items whose values are displayed or returned.
Chapter 1. Introduction Prev Next Chapter 1. Introduction Overview Running in a Non-Standard Location Overview The H-series runs on the new Itanium processor-based TNS/E NonStop servers. The Itanium processor is a member of the Intel Itanium Process Family of processors that implement the IA-64 architecture.
529410-001 Legal Notices
Chapter 2. Installation Prev Next Chapter 2. Installation Installing NonStop Tuxedo Installing NonStop Tuxedo The steps to install NonStop Tuxedo on TNS/E systems are listed in the Readme file for this independent product. This section contains information beyond the checklist items in the Readme file. A step when installing NonStop Tuxedo is running the shell script Install.sh after the product pax files are copied to the target system. This is necessary in TNS/R and TNS/E systems.
$SYSTEM.SYSTEM because SRLs are not used on TNS/E systems. Prev Chapter 1. Introduction 529410-001 Up Home Next Chapter 3.
Chapter 3. Dynamic Link Libraries Prev Next Chapter 3. Dynamic Link Libraries Use of the _RLD_LIB_PATH Environment Variable Floating-Point Considerations Simpapp Sample Application Bankapp Sample Application Use of the _RLD_LIB_PATH Environment Variable On TNS/E systems, NonStop Tuxedo uses dynamic link libraries (DLLs) instead of native user libraries with exported data (sometimes called the NonStop Tuxedo SRLs), that are used on TNS/R systems.
way. Simpapp Sample Application For the simpapp sample application to run on TNS/E systems, small changes have been made in two files. 1. The simpapp_env file has an additional line: export _RLD_LIB_PATH=$TUXDIR/lib This sets an environment variable to the path used to search for DLLs at the time a process starts. NonStop Tuxedo 8.0 executables are compiled with -Weld='-RLD_L /tuxedo8.0/lib', so when NonStop Tuxedo is installed in the default location /tuxedo8.
2. The bankapp.mk file has these additional lines: # # # Float type: This flag is used to set the floating point type to # be used while compiling the bankapp server and client programs. # FLOATTYPE = -WTandem_float CFLAGS= -DNOWHAT=1 I$(INCDIR) $(CGFLAG) $(DFML32) $(FLOATTYPE) The new macro, FLOATTYPE, defines the floating point type to be used. The value -WTandem_float sets the floating type to Tandem. The value -WIEEE_float sets the floating type to IEEE. 3.
Chapter 4. Reference Pages Prev Next Chapter 4. Reference Pages buildclient Name Synopsis Description Environment Variables Portability Examples See Also buildserver Name Synopsis Description Environment Variables Portability Examples See Also Standards Conformance buildwsh Name Synopsis Description Portability The following reference pages are modified to describe changes that are specific to H-series releases only.
Name buildclient - Constructs a NonStop Tuxedo client module. Synopsis buildclient [-C][-v][{-r rmname | -w}][-o name][-f firstfiles][-l lastfiles] Description buildclient is used to construct a NonStop Tuxedo System/T client module. The command combines the files supplied by the -f and -l options with the standard NonStop Tuxedo System/T libraries to form a load module. The load module is built by buildclient using the default C language compilation command defined for the operating system in use.
Environment Variables TUXDIR buildclient uses the environment variable TUXDIR to find the System/T libraries and include files to use during compilation of the client process. CC buildclient normally uses the default C language compilation command to produce the client executable. The default C language compilation command is defined as C89(1) for Open System Services. In order to allow for the specification of an alternate compiler, buildclient checks for the existence of an environment variable named CC.
If you compile object files separately from buildclient, and use buildclient to link them into the client, those object files should be compiled with the -WTandem_float option. Examples CC=/usr/bin/c89 CFLAGS="-I $APPDIR/include"; export CC CFLAGS buildclient -o empclient -f emp.c -f "userlib1.a userlib2.a" ALTCFLAGS="-Wcolumns=80 -Werrors=10 -Woptimize=1" _RLD_LIB_PATH=$COBDIR/coblib:$TUXDIR/lib export ALTCFLAGS _RLD_LIB_PATH buildclient -C -o empclient -f name.cbl -f "userlib1.a userlib2.
command to its standard output. -o outfile Specifies the name of the file the output load module is to have. If not supplied, the load module is named SERVER. -n maxdynam Specifies the maximum number of dynamic services the user may specify when the server is run. A dynamic service allows the user to specify, at run time, the function within the server that is to process the service. If -n is not specified, the maximum number of such services is set to 25.
builds the server with a function pqr, which can have a service association. tpadvertise() could be used to map a service name to the pqr function. A filename can be specified with the -s option by prefacing the filename with the '@' character. Each line of this file is treated as an argument to the -s option. You may put comments in this file. All comments must start with the '#' character. This file can be used to specify all the functions in the server that may have services mapped to them.
produce the server executable. In order to allow for the specification of an alternate compiler, buildserver checks for the existence of an environment variable named ALTCC. If ALTCC does not exist in buildserver's environment, or if it is the string " ", buildserver will use "ecobol". If ALTCC does exist in the environment, its value is taken to be the name of the compiler command to be executed.
-lfirst'"\ buildserver -v -s TOUPPER -o simpserv -f simpserv.c See Also ubbconfig, servopts Standards Conformance The following is a NonStop Tuxedo modification to BEA Tuxedo: The -t option does not apply because servers are not multithreaded in the NonStop Tuxedo environment. buildwsh Name Synopsis Description Portability Name buildwsh - Builds customized workstation handler process.
buildwsh normally uses the c89 command to produce the a.out. In order to allow for the specification of an alternate compiler, buildwsh checks for the existence of a shell variable named CC. If CC does not exist in buildwsh's environment, or if it is the string " ", buildwsh uses c89 as the compiler depending on your operating system. If CC does exist in the environment, its value is taken to be the name of the compiler to be executed.
Chapter 5. Messages Prev Next Chapter 5. Messages Error Message Error Message One new error message is added to NonStop Tuxedo. 1082 WARN: _RLD_LIB_PATH longer than 255 characters, ignored for server Description. When tmboot started server, the environment variable _RLD_LIB_PATH held a string longer than 255 characters. Instead of the user-supplied string, tmboot used "$TUXDIR/lib" when it started server. Action. Reduce the size of the string in_RLD_LIB_PATH before running tmboot to start the server.
Index Prev Index Symbols _RLD_LIB_PATH environment variable, Use of the _RLD_LIB_PATH Environment Variable B bankapp_env file, Bankapp Sample Application bankapp.
R rout_add script, Installing NonStop Tuxedo rout_check script, Installing NonStop Tuxedo S simpapp_env file, Simpapp Sample Application simpapp.mk file, Simpapp Sample Application Simpapp sample application, Simpapp Sample Application T tsmp3_check script, Installing NonStop Tuxedo Prev Chapter 5.
Legal Notice © Copyright 2004 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
OSF software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California.
Version and Copyright Information Document Title HP NonStop Tuxedo 8.0 Supplement for H-Series RVUs Abstract This supplemental manual documents changes required to migrate existing NonStop Tuxedo applications from a G-series system to an H-series system. Product Version NonStop Tuxedo 8.0 Supported Releases This supplemental manual supports H06.03 and all subsequent H-series releases until otherwise indicated in a new edition.
