5675-DB2
Document Number GI10-8220-00
Printed in U.S.A.
| Note! |
|---|
|
Before using this information and the product it supports, be sure to read the general information under "Notices". |
A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1997, 2001. All rights reserved.
Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule contract with IBM Corp.
Program and Service Level Information
Installation Requirements and Considerations
References in this document to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility.
APAR numbers are provided in this document to assist in locating PTFs that may be required. Ongoing problem reporting may result in additional APARs being created. Therefore, the APAR lists in this document may not be complete. To obtain current service recommendations and to identify current product service requirements, always contact the IBM Customer Support Center or use S/390 SoftwareXcel to obtain the current "PSP Bucket".
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the
IBM Director of LicensingFor online versions of this book, we authorize you to:
You are responsible for payment of any taxes, including personal property taxes, resulting from this authorization.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you.
Your failure to comply with the terms above terminates this authorization. Upon termination, you must destroy your machine readable documentation.
The following terms are trademarks of the IBM Corporation in the
United States or other countries or both:
Language Environment OpenEdition DB2 AIX Net.Data
This program directory is intended for the system programmer responsible for program installation and maintenance. It contains information concerning the material and procedures associated with the installation of IBM Net.Data for OS/390 and z/OS Version 7.1. This publication refers to IBM Net.Data for OS/390 and z/OS Version 7.1 as Net.Data Version 7.1. You should read all of this program directory before installing the program and then keep it for future reference.
The program directory contains the following sections:
Before installing Net.Data Version 7.1, read "Preventive Service Planning". This section tells you how to find any updates to the information and procedures in this program directory.
Do not use this program directory if you are installing Net.Data Version 7.1 with a SystemPac or ServerPac. When using these offerings, use the jobs and documentation supplied with the offering. This documentation may point you to specific sections of the program directory as required.
If you are installing Net.Data Version 7.1 using the MVS Custom-Built Product Delivery Offering (CBPDO, 5751-CS3), a softcopy program directory is provided on the CBPDO tape which is identical to the printed copy shipped with your order. Your CBPDO contains a softcopy preventive service planning (PSP) upgrade for this product. All service and HOLDDATA for Net.Data Version 7.1 are included on the CBPDO tape.
Documentation is available in HTML at the Net.Data website. Please
see:
http://www.ibm.com/software/data/net.data/docs/index.html
For general information, see:
http://www.ibm.com/software/data/net.data/
With IBM's Net.Data product, you can create dynamic Web pages using data from both relational and non-relational database management systems (DBMSs), including DB2, IMS, and ODBC-enabled databases, and using applications written in programming languages such as Java, JavaScript, Perl, C, C++, REXX, and COBOL.
Net.Data is a macro processor that executes as middleware on a Web server machine. You can write Net.Data application programs, called macros, that Net.Data interprets to create dynamic Web pages with customized content based on input from the user, the current state of your databases, other data sources, existing business logic, and other factors that you design into your macro.
A request, in the form of a URL (uniform resource locator), flows from a browser, such as Netscape Navigator or Internet Explorer, to a Web server that forwards the request to Net.Data for execution. Net.Data locates and executes the macro and builds a Web page that it customizes based on functions that you write. These functions can:
Net.Data passes this Web page to the Web server, which in turn forwards the page over the network for display at the browser. Other members of the Net.Data family of products provide similar capabilities on machines executing the AIX, OS/2, OS/400, HP-UX, Sun Solaris, Linux, and Windows NT.
Net.Data can be used in server environments that are configured to use interfaces such as HyperText Transfer Protocol (HTTP) and Common Gateway Interface (CGI). HTTP is an industry-standard interface for interaction between a browser and Web server, and CGI is an industry-standard interface for Web server invocation of gateway applications like Net.Data. These interfaces allow you to select your favorite browser or Web server for use with Net.Data. Net.Data also supports a variety of Web server Application Programming Interfaces (Web server APIs) and FastCGI for improved performance, as well as a Servlet interface for integration into a WebSphere environment.
Net.Data Version 7 provides the following enhancements:
Net.Data Version 7.1 consists of the following FMIDs:
An IBM program is identified by a program number and a feature number. The program number for Net.Data Version 7.1 is 5675-DB2.
Basic Machine-Readable Materials are materials that are supplied under the base license and feature code, and are required for the use of the product. Optional Machine-Readable Materials are orderable under separate feature codes, and are not required for the product to function.
The program announcement material describes the features supported by Net.Data Version 7.1. Ask your IBM representative for this information if you have not already received a copy.
The distribution medium for this program is 9-track magnetic tape (written at 6250 BPI), 3480 cartridge, or 4mm cartridge. The tape or cartridge contains all the programs and data needed for installation. It is installed using SMP/E, and is in SMP/E RELFILE format. See "Installation Instructions" for more information about how to install the program.
Table 1
describes the tape or cartridge.
Table 1. Basic Material: Program Tape
| Medium | Feature Number | Physical Volume | External Label Identification | VOLSER |
|---|---|---|---|---|
| 6250 tape | 5891 | 1 of 1 | Net.Data Version 7 | 242710 |
| 3480 tape | 5892 | 1 of 1 | Net.Data Version 7 | 242710 |
| 4mm cartridge | 6009 | 1 of 1 | Net.Data Version 7 | 242710 |
No optional machine-readable materials are provided for Net.Data Version 7.1.
HTML, PostScript, and PDF versions of these books are available at the following url: http://www.ibm.com/software/data/net.data/docs/index.html
No optional publications are provided for Net.Data Version 7.1.
No program source materials or viewable program listings are provided for Net.Data Version 7.1.
Table 2. Publications Useful During Installation
| Publication Title | Form Number |
|---|---|
| SMP/E User's Guide | SC28-1740 |
| SMP/E Reference | SC28-1806 |
| SMP/E Messages and Codes | SC28-1738 |
| SMP/E Commands | SC28-1805 |
This section describes the IBM support available for Net.Data Version 7.1.
Contact your IBM representative for specific information about available program services.
Before installing Net.Data Version 7.1, you should review the current Preventive Service Planning (PSP) information. If you obtained Net.Data Version 7.1 as part of a CBPDO, there is HOLDDATA and PSP information included on the CBPDO tape.
If you obtained Net.Data Version 7.1 on a product tape, or if the CBPDO is more than two weeks old when you install it, you should contact the IBM Support Center or use S/390 SoftwareXcel to obtain the current "PSP Bucket".
PSP Buckets are identified by UPGRADEs, which specify product levels,
and SUBSETs, which specify the FMIDs for a product level. The UPGRADE
and SUBSET values for Net.Data Version 7.1 are:
Table 3. PSP Upgrade and Subset ID
| UPGRADE | SUBSET | Description |
|---|---|---|
| DB2710 | H242710 | Net.Data for OS/390 Version 7.1 |
Report any difficulties you have using this program to your IBM Support Center. If an APAR is required, the Support Center will provide the address to which any needed documentation can be sent.
Table 4 identifies the component IDs
(COMPID)
for Net.Data Version 7.1.
| FMID | COMPID | Component Name | RETAIN
Release |
|---|---|---|---|
| H242710 | 5655A2401 | Net.Data for OS/390 Version 7.1 | 710 |
This section identifies the program and any relevant service levels of Net.Data Version 7.1. The program level refers to the APAR fixes incorporated into the program. The service level refers to the PTFs integrated.
No APARs have been incorporated into Net.Data Version 7.1.
No PTFs against this release of Net.Data Version 7.1 have been incorporated into the product tape.
The following sections identify the system requirements for installing and activating Net.Data Version 7.1. The following terminology is used:
In many cases, the same system can be used as both a driving system and a target system. However, you may want to set up a clone of your system to use as a target system by making a separate IPL-able copy of the running system. The clone should include copies of all system libraries that SMP/E updates, copies of the SMP/E CSI data sets that describe the system libraries, and your PARMLIB and PROCLIB.
Some cases where two systems should be used include the following:
This section describes the environment of the driving system required to install Net.Data Version 7.1.
The driving system can run in any hardware environment that supports the required software.
Table 5. Driving System Software Requirements
| Program Number | Product Name and
Minimum VRM/Service Level |
|---|---|
| 5647-A01 | OS/390 Version 2 Release 7 base services or later |
This section describes the environment of the target system required to install and use Net.Data Version 7.1.
Net.Data Version 7.1 installs in the DBS (P115) SREL.
The target system can run in any hardware environment that supports the required software.
A mandatory requisite is defined as a product that is required
without exception; this product either will not install or
will not function unless this requisite is met. This
includes products that are specified as REQs or PREs.
| Program Number | Product Name and
Minimum VRM/Service Level |
|---|---|
| 5647-A01 | OS/390 Version 2 Release 7 base services or later |
A functional requisite is defined as a product that is not
required for the successful installation of this product or for the
basic function of the product, but is needed at run time for
a specific function of this product to work. This includes products
that are specified as IF REQs.
Table 7. Functional Requisites - DB2 Version 5 or higher features
| Program
Number | Product Name and
Minimum VRM/Service Level | Function |
|---|---|---|
| 5751-CS3 | JDK1.1.8 | Use of Net.Data Version 7.1 Servlets |
| Any one of the following: | ||
| 5655-DB2 | DB2 for OS/390 Version 5 or higher | To use the Net.Data provided support for ODBC or SQL language environments. |
| 5645-DB2 | DB2 for OS/390 Version 6 or higher | DB2 Large Objects (LOB) |
Note: For product information and download instructions for JDK1.1.8 see HTTP://www.s390.ibm.com/java/
A toleration/coexistence requisite is defined as a product which must
be present on a sharing system. These systems can be other systems in a
multisystem environment (not necessarily sysplex), a shared DASD
environment (such as test and production), or systems that reuse the
same DASD at different time intervals.
Table 8. Toleration/Coexistence Requisites
| Program Number | Product Name and
Minimum VRM/Service Level |
|---|---|
| Any one of the following: For access to heterogeneous data source through DataJoiner | |
| N/A | DataJoiner for AIX Version 1.2 with PTF U447593 |
| N/A | DataJoiner for HP-UX Version 1.1 |
A negative requisite identifies products which must not be installed on the same system as this product.
Net.Data Version 7.1 has no negative requisites.
Net.Data Version 7.1 libraries can reside on 3380 or 3390 DASD.
Table 9 lists the total space required for each type of
library.
Table 9. Total DASD Space Required by Net.Data Version 7.1
| Library Type | Total Space Required |
|---|---|
| Target | 170 blocks |
| Distribution | 2122 blocks |
| HFS | 26640 sectors (512 bytes per sector) |
Notes:
If you currently have a previous release of this product installed in these libraries, the installation of this release will delete the old one and reclaim the space used by the old release and any service that had been installed. You can determine whether or not these libraries have enough space by deleting the old release with a dummy function, compressing the libraries, and comparing the space requirements with the free space in the libraries.
For more information on the names and sizes of the required data sets, please refer to "Allocate SMP/E Target and Distribution Libraries and Paths".
The following figures describe the target and distribution libraries and HFS paths required to install Net.Data Version 7.1. The storage requirements of Net.Data Version 7.1 must be added to the storage required by other programs having data in the same library or path.
Note: The data in these tables should be used when determining which
libraries can be merged into common data sets. In addition, since some
ALIAS names may not be unique, ensure that no naming conflicts will be
introduced before merging libraries.
Table 10. Storage Requirements for Net.Data Version 7.1 Target Libraries
| Library
DDNAME | Member
Type | Target
Volume | T
Y P E | O
R G | R
E C F M | L
R E C L | No.
of 3390 Trks | No.
of DIR Blks |
|---|---|---|---|---|---|---|---|---|
| SDTWBASE | SAMPLE | any | U | PDS | FB | 80 | 6 | 5 |
| SDTWDBRM | SAMPLE | any | U | PDS | FB | 80 | 7 | 5 |
| SDTWSPUF | SAMPLE | any | U | PDS | FB | 80 | 2 | 5 |
| SDTWLEIH | MACRO | any | U | PDS | VB | 256 | 2 | 5 |
| SDTWLEID | MACRO | any | U | PDS | VB | 256 | 2 | 5 |
| SDTWLOAD | LMOD | any | U | PDS | U | 0 | 7 | 10 |
Table 11. Storage Requirements for Net.Data Version 7.1 Distribution Libraries
| Library
DDNAME | T
Y P E | O
R G | R
E C F M | L
R E C L | No.
of 3390 Trks | No.
of DIR Blks |
|---|---|---|---|---|---|---|
| ADTWBASE | U | PDS | FB | 80 | 6 | 5 |
| ADTWDBRM | U | PDS | FB | 80 | 7 | 5 |
| ADTWLOAD | U | PDS | U | 0 | 244 | 10 |
| ADTWSPUF | U | PDS | FB | 80 | 2 | 5 |
| ADTWHTML | U | PDS | VB | 256 | 2 | 5 |
| ADTWICON | U | PDS | VB | 256 | 6 | 5 |
| ADTWMACS | U | PDS | VB | 256 | 5 | 5 |
| ADTWCMD | U | PDS | VB | 256 | 2 | 5 |
| ADTWXML | U | PDS | VB | 256 | 2 | 5 |
Table 12. Net.Data Version 7.1 HFS Paths
| DDNAME | T
Y P E | Path Name |
|---|---|---|
| SDTWCMD | N | /usr/lpp/netdata/testcmd/IBM |
| SDTWHTML | N | /usr/lpp/netdata/pub/IBM |
| SDTWLOA3 | N | /usr/lpp/netdata/icapi-lib/IBM |
| SDTWLOA2 | N | /usr/lpp/netdata/cgi-bin/IBM |
| SDTWICON | N | /usr/lpp/netdata/icons/IBM |
| SDTWJAVA | N | /usr/lpp/netdata/java/IBM |
| SDTWMACS | N | /usr/lpp/netdata/macros/IBM |
| SDTWENUS | N | /usr/lpp/netdata/C/IBM |
| SDTWJAJP | N | /usr/lpp/netdata/Ja_JP/IBM |
| SDTWKOKR | N | /usr/lpp/netdata/Ko_KR/IBM |
| SDTWLOA4 | N | /usr/lpp/netdata/servlet-lib/IBM |
| SDTWXML | N | /usr/lpp/netdata/xml/IBM |
| SDTWLOA5 | N | /usr/lpp/netdata/fcgi-bin/IBM |
| SDTWLOGS | N | /usr/lpp/netdata/logs/IBM |
Installing Net.Data Version 7.1 may result in the deletion of other FMIDs. To see what FMIDs will be deleted, examine the ++VER statement in the product's SMPMCS.
If you do not wish to delete these FMIDs at this time, you must install Net.Data Version 7.1 into separate SMP/E target and distribution zones.
Note: These FMIDs will not automatically be deleted from the Global Zone. Consult the SMP/E manuals for instructions on how to do this.
Net.Data Version 7.1 has no special considerations for the target system.
This chapter describes the installation method and the step-by-step procedures to install and to activate the functions of Net.Data Version 7.1.
Please note the following:
This release of Net.Data Version 7.1 is installed using the SMP/E RECEIVE, APPLY, and ACCEPT commands. The SMP/E dialogs may be used to accomplish the SMP/E installation steps.
The recommended values for some SMP/E CSI subentries are shown in
Table 13. Use of values lower than these may result in
failures in the installation process. DSSPACE is a subentry in the
GLOBAL options entry. PEMAX is a subentry of the GENERAL entry in the
GLOBAL options entry. Refer to the SMP/E manuals for instructions on
updating the global zone.
Table 13. SMP/E Options Subentry Values
| SUB-ENTRY | Value | Comment |
|---|---|---|
| DSSPACE | (200,200,500) | 3390 DASD tracks |
| PEMAX | 5500 | The SMP/E default is larger that what can be specified here. |
Net.Data Version 7.1 uses the CALLLIBS function provided in SMP/E to resolve external references during installation. When Net.Data Version 7.1 is installed, ensure that the following DDDEFs entries exist and contain valid dataset names for your environment.
Note: The DDDEFs above are used only to resolve the link-edit for Net.Data Version 7.1 using CALLLIBS. These data sets are not updated during the installation of Net.Data Version 7.1. SCEELKED is used to reference LE libraries and SDSNLOAD is used to reference DB2 libraries.
The following sample installation jobs are provided on the
distribution tape to help you install Net.Data Version 7.1:
Table 14. Sample Installation Jobs
| Job Name | Job Type | Description | RELFILE |
|---|---|---|---|
| DTWRECEV | RECEIVE | Sample RECEIVE job | IBM.H242710.F2 |
| DTWALLOC | ALLOCATE | Sample job to allocate target and distribution libraries | IBM.H242710.F2 |
| DTWHFS (Optional) | ALLOCATE HFS | Sample job to allocate HFS libraries | IBM.H242710.F2 |
| DTWISMKD | MKDIR | Sample job to invoke the supplied DTWMKDIR EXEC to allocate HFS paths | IBM.H242710.F2 |
| DTWDDDEF | DDDEF | Sample job to define SMP/E DDDEFs | IBM.H242710.F2 |
| DTWAPPLY | APPLY | Sample APPLY job | IBM.H242710.F2 |
| DTWACCEP | ACCEPT | Sample ACCEPT job | IBM.H242710.F2 |
You may copy the jobs from the tape by submitting the job below. Add a job card and modify the parameters in boldface to uppercase values to meet your site's requirements before submitting.
//STEP1 EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//IN DD DSN=IBM.H242710.F2,UNIT=tunit,VOL=SER=242710,
// LABEL=(3,SL),DISP=(OLD,KEEP)
//OUT DD DSNAME=DTW710.INSTALL,
// DISP=(NEW,CATLG,DELETE),
// VOL=SER=dasdvol,UNIT=dunit,
// DCB=*.STEP1.IN,SPACE=(8800,(15,5,5))
//SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
//SYSIN DD *
COPY INDD=IN,OUTDD=OUT
SELECT MEMBER=(DTWACCEP,DTWALLOC,DTWAPPLY,DTWDDDEF)
SELECT MEMBER=(DTWISMKD,DTWMKDIR,DTWRECEV,DTWHFS)
/*
where tunit is the unit value matching the product tape or cartridge, DTW710.INSTALL is the name of the data set where the sample jobs will reside, dasdvol is the volume serial of the DASD device where the data set will reside, and dunit is the DASD unit type of the volume.
You can also access the sample installation jobs by performing an SMP/E RECEIVE for FMID H242710, and then copying the jobs from data set hlq.IBM.H242710.F2 to a work data set for editing and submission. Note: "hlq" is the high-level qualifier specified as teh DSPREFIX value in the SMPTLIB DDDEF or the Options entry of the global zone.
Edit and submit sample job DTWRECEV to perform the SMP/E RECEIVE for Net.Data Version 7.1. Consult the instructions in the sample job for more information.
NOTE: if you obtained Net.Data Version 7.1 as part of a CBPDO, you can use the RCVPDO job found in the CBPDO RIMLIB data set to RECEIVE the Net.Data Version 7.1 FMIDs as well as any service, HOLDDATA, or preventive service planning (PSP) information included on the CBPDO tape. For more information, refer to the documentation included with the CBPDO.
Expected Return Codes and Messages: This job should complete with a condition code of 0 or less.
Edit and submit sample job DTWALLOC to allocate the SMP/E target and distribution libraries for Net.Data Version 7.1. Consult the instructions in the sample job for more information.
Expected Return Codes and Messages: This job should complete with a condition code of 0.
If you plan to install your product into a separate HFS data set instead of installing into the root filesystem, edit and run the sample job, member name DTWHFS, in the data set defined by the DTW710.INSTALL job, to allocate an HFS data set.
Expected Return Codes and Messages: This job should complete with a condition code of 0.
Expected Return Codes and Messages: This job should complete with a condition code of 0.
If you plan to create a new HFS for this product, you should consider updating the BPXPRMxx PARMLIB member to mount the new HFS at IPL time. This may be helpful if an IPL occurs before the installation is complete.
Expected Return Codes and Messages: This job should complete with a condition code of 0.
Edit and submit sample job DTWAPPLY to perform an SMP/E APPLY CHECK for Net.Data Version 7.1. Consult the instructions in the sample job for more information.
To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the following on the APPLY CHECK: PRE, ID, REQ, and IFREQ. This is because the SMP/E root cause analysis identifies the cause only of ERRORS and not of WARNINGS (SYSMODs that are bypassed are treated as warnings, not errors, by SMP/E).
Once you have taken any actions indicated by the APPLY CHECK, remove the CHECK operand and run the job again to perform the APPLY.
Note: The GROUPEXTEND operand indicates that SMP/E apply all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions.
Expected Return Codes and Messages APPLY CHECK: This job should complete with a condition code of 0.
Expected Return Codes and Messages APPLY: This job should complete with a condition code of 0.
Note: The following can be expected during the LINK-EDIT processing for modules in the SMPLTS library: GIM23903I LINK-EDIT PROCESSING FOR SYSMOD H242710 WAS SUCCESSFUL FOR MODULE DTW..IN LMOD DTW.. IN THE SMPLTS LIBRARY.THE RETURN CODE WAS 04. The return code 4 is caused by not including Language Environment (LE) functions during LINK-EDIT processing for modules in the SMPLTS library. You can expect to see LINK-EDIT warning messages "IEW2454W 9203 SYMBOL xxxxxxx UNRESOLVED. NO AUTOCALL(NCAL) SPECIFIED" in the detailed Binder output for those LINK-EDIT processes for modules in the SMPLTS library. LINK-EDIT to libraries other that the SMPLTS must complete with a return code 0.
Edit and submit sample job DTWACCEP to perform an SMP/E ACCEPT CHECK for Net.Data Version 7.1. Consult the instructions in the sample job for more information.
To receive the full benefit of the SMP/E Causer SYSMOD Summary Report, do not bypass the following on the ACCEPT CHECK: PRE, ID, REQ, and IFREQ. This is because the SMP/E root cause analysis identifies the cause only of ERRORS and not of WARNINGS (SYSMODs that are bypassed are treated as warnings, not errors, by SMP/E).
Before using SMP/E to load new distribution libraries, it is recommended that you set the ACCJCLIN indicator in the distribution zone. This will cause entries produced from JCLIN to be saved in the distribution zone whenever a SYSMOD containing inline JCLIN is ACCEPTed. For more information on the ACCJCLIN indicator, see the description of inline JCLIN in the SMP/E manuals.
Once you have taken any actions indicated by the ACCEPT CHECK, remove the CHECK operand and run the job again to perform the ACCEPT.
Note: The GROUPEXTEND operand indicates that SMP/E apply all requisite SYSMODs. The requisite SYSMODS might be applicable to other functions.
Expected Return Codes and Messages ACCEPT CHECK: This job should complete with a condition code of 0.
Expected Return Codes and Messages ACCEPT: This job should complete with a condition code of 0.
The installation verification programs allows you to perform simple tests that verify the successful installation of Net.Data. If you are migrating from an earlier version of Net.Data, Net.Data may be already configured to run in your environment. You may or may not have to configure Net.Data to run the IVPs. Once you successfully complete the IVP, you may need to reconfigure Net.Data to operate to your specifications. Detailed description of how to configure Net.Data is provided in the Net.Data Administration and Programming Guide for OS/390.
Pass /netdata-java/* /usr/lpp/netdata/java/* Pass /netdata-xml/* /usr/lpp/netdata/xml/* Pass /netdata-icons/* /usr/lpp/netdata/icons/* |
Add /usr/lpp/netdata/%L/%N to the NLSPATH statement in the Web server's environment variables file (/etc/httpd.envvars). Your NLSPATH statement should be similar to the following:
NLSPATH=....:/usr/lpp/netdata/%L/%N |
English: LANG=C Japanese: LANG=Ja_JP Korean: LANG=Ko_KR |
Important: Only one method of execution can be specified in the webserver configuration.
Exec /netdata-cgi/* /usr/lpp/netdata/cgi-bin/* |
LIBPATH=/usr/lpp/internet/bin:/usr/lpp/netdata/cgi-bin |
LIBPATH=/usr/lpp/internet/bin:/usr/lpp/netdata/fcgi-bin |
Local { Exec /usr/lpp/netdata/fcgi-bin/db2www Role Responder URL /fcgi-bin/db2www BindPath /tmp/netdata_fcgi NumProcesses 100 User IBMUSER } |
| :dtw_init |
/usr/lpp/netdata/icapi-lib/db2www:dtw_icapi* |
Add a ServerTerm directive to the Web server's configuration file (/etc/httpd.conf) that tells the Web server how to terminate Net.Data. The default directory to use for the ServerTerm directive is:
| :dtw_term |
LIBPATH=/usr/lpp/internet/bin:/usr/lpp/netdata/icapi-lib |
CLASSPATH=...:/usr/lpp/netdata/servlet-lib/NetDataServlets.jar |
Add Net.Data servlet-lib directory to the LIBPATH statement of your Web server's environment variables file (/etc/httpd.envvars). The default Net.Data servlet-lib directory within the LIBPATH statement is similar to the following:
LIBPATH=/usr/lpp/internet/bin:/usr/lpp/netdata/servlet-lib |
DefaultFsCp IBM-1047 #(Latin 1/Open Systems) DefaultNetCp ISO8859-1 |
DefaultFsCp IBM-939 #(Japanese Latin Extended) DefaultNetCp IBM-932 |
DefaultFsCp IBM-933 DefaultNetCp IBM-949 |
//STEPLIB DD DISP=SHR,DSN=DSN710.SDSNLOAD |
The following example shows how to copy the Net.Data Initialization file to the web servers document root directory using default install directories. Execute the following shell command:
cp /usr/lpp/netdata/pub/db2www.ini /usr/lpp/internet/server_root/pub |
ENVIRONMENT (DTW_FILE) filedll () ENVIRONMENT (DTW_APPLET) appldll () |
DefaultDBCp IBM-930 |
Tip: You should not set this configuration variable if the code page of your database is the same as the code page of your macros. Doing so would lead to unnecessary code page conversions.
The Net.Data Error Log is used to record error conditions. The Net.Data error log name is "netdata.error.log" and it is written to HFS. You can specify the HFS directory and the type of messages to be logged. For IVP testing, ALL messages should be logged. The following is an example of configuring to log all messages to the web servers logs directory:
DTW_ERROR_LOG_DIR /usr/lpp/netdata/logs DTW_ERROR_LOG_LEVEL ALL |
After the IVP activity has completed it is recommended that the DTW_ERROR_LOG_LEVEL be set to INFORMATION.
The Net.Data Trace Log is used to provide information about macro execution. The trace file name is "netdata.trace" and it is written to HFS. You can specify the HFS directory and the level of tracing. For the IVP, SERVICE level tracing should be used. The following is an example of configuring to write service level trace messages to Net.Data logs directory:
DTW_TRACE_LOG_DIR /usr/lpp/netdata/logs DTW_TRACE_LOG_LEVEL SERVICE |
MACRO_PATH:
If your Net.Data macros directory path is different from the default /usr/lpp/netdata/macros, then update the MACRO_PATH statement accordingly.
EXEC_PATH:
If your Net.Data external program directory path is different from the default /usr/lpp/netdata/testcmd, then update the EXEC_PATH statement accordingly
ENVIRONMENT (DTW_SQL) dtwsql() |
ENVIRONMENT (DTW_SQL) dtwsqlv6() |
DB2SSID DBNC |
The DTW_ODBC environment statement is used to describe the ODBC environment. You specify the following in the Net.Data initialization file:
ENVIRONMENT (DTW_ODBC) odbcdll () |
DSNAOINI filename |
If you plan to use the ODBC and SQL language environments then you use the ODBC sample JCL to bind the Net.Data application. See Bind Net.Data for ODBC below. Sample JCL is provided in library "DTW710.SDTWBASE" that can be tailored to bind Net.Data to the database that will be used to run the IVP.
Important: If you are migrating from a previous release of Net.Data and your current configuration supports Web Page Caching or LOB management, you should bind using the jobs that marked for Caching or LOB management.
Tailor and execute one of the following sample JCL. Tailoring instructions are provided in the sample JCL:
Bind Net.Data for SQL Language Environment
Bind Net.Data for ODBC Language Environment
CGI or GWAPI URL: http://<your Web server address>/netdata-cgi/db2www/hello.dtw/report
|
CGI or GWAPI URL: http://<your Web server address>/netdata-cgi/db2www/tsql.dtw/input
|
CGI or GWAPI URL: http://<your Web server address>/netdata-cgi/db2www/todbc.dtw/input
|
CGI or GWAPI URL: http://<your Web server address>/netdata-cgi/db2www/tsystem.dtw/input
|
CGI or GWAPI URL: http://<your Web server address>/netdata-cgi/db2www/tperl.dtw/input
|
CGI or GWAPI URL: http://<your Web server address>/netdata-cgi/db2www/trexx.dtw/input
|
Look into the Net.Data log directory, default name is /u/lpp/netdata/logs, for an error log file named "netdata.error.log". If the file exists, review and correct any errors that are logged. If the file doesn't exist, then no error were recorded by Net.Data.
Look into the Net.Data log directory, default name is /u/lpp/netdata/logs, for a trace file named "netdata.trace". If the dataset doesn't exist then check the settings for "DTW_TRACE_LOG_DIR" and "DTW_TRACE_LOG_LEVEL" in the Net.Data initialization file db2www.ini. The IVP should be run with service level tracing
If the file does exist, then check the beginning of the file for trace data. The first set of records should contain configuration variable names and settings. For a detailed description of Net.Data trace records, see the Net.Data Messages and Codes for a description of trace messages.
You may now want to go back and configure Net.Data to fit your specific
environment. The Net.Data Administration and Programming Guide for OS/390
contains the information on how to configure Net.Data.
Program Directory for IBM Net.Data for OS/390 and z/OS Version 7.1 Service Level ????
You may use this form to comment about this document, its organization, or subject matter with the understanding that IBM may use or distribute whatever information you supply in any way it believes appropriate without incurring any obligation to you.
For each of the topics below please indicate your satisfaction level by circling your choice from the rating scale. If a statement does not apply, please circle N.
| RATING SCALE |
|---|
very very not
satisfied <=====================> dissatisfied applicable
1 2 3 4 5 N
|
| Satisfaction | ||||||
|---|---|---|---|---|---|---|
| Ease of product installation | 1 | 2 | 3 | 4 | 5 | N |
| Contents of program directory | 1 | 2 | 3 | 4 | 5 | N |
| Installation Verification Programs | 1 | 2 | 3 | 4 | 5 | N |
| Time to install the product | 1 | 2 | 3 | 4 | 5 | N |
| Readability and organization of program directory tasks | 1 | 2 | 3 | 4 | 5 | N |
| Necessity of all installation tasks | 1 | 2 | 3 | 4 | 5 | N |
| Accuracy of the definition of the installation tasks | 1 | 2 | 3 | 4 | 5 | N |
| Technical level of the installation tasks | 1 | 2 | 3 | 4 | 5 | N |
| Ease of getting the system into production after installation | 1 | 2 | 3 | 4 | 5 | N |
How did you order this product?
Is this the first time your organization has installed this product?
Were the people who did the installation experienced with the installation of MVS products?
If yes, how many years? __
If you have any comments to make about your ratings above, or any other aspect of the product installation, please list them below:
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
Please provide the following contact information:
Thank you for your participation.
Please send the completed form to (or give to your IBM representative who will forward it to the IBM Net.Data for OS/390 and z/OS Version 7.1 Development group):
IBM Corporation
FAX Number: (408) 463-2614
E-Mail: jfigone@us.ibm.com