SAP Basis Tech Supports

Symptom

This SAP Note is valid for the following releases:
mySAP CRM 4.0 SR1 on Unix and Windows for IBM UDB for z/OSmySAP ERP 2004 SR1 on Unix and Windows for IBM UDB for z/OSSAP R3E 4.7 Extension Set 2 SR1 on Unix and Windows for IBM UDB for z/OSSAP SCM 4.1 on Unix and Windows for IBM UDB for z/OSmySAP SRM 4.0 SR1 on Unix and Windows for IBM UDB for z/OSSAP Solution Manager 3.2 SR1 on Unix and Windows for IBM UDB for z/OSSAP Netweaver 2004 SR1 on Unix and Windows for IBM UDB for z/OSOther terms

640PC 2008 Thin Client Installation DB2 MVS OS/390 Patch Collection PatchColl PatColl Edition May 2008 Export VCAT DB2DB6EKEY J2EE Schema Java R3ta MigMon Migration Monitor prepare STR File System Copy Database Build Error prep_build.log
Reason and Prerequisites

Problems discovered after publication of the installation guide.
Solution

***********************************************************************
* This SAP Note is valid for
* the 6.20/6.40 Patch Collection Installation
* Edition May 2008
*
***********************************************************************
This note has the following sections:
1. PRE-INSTALLATION
2. INSTALLATION PROCESS
3. POST-INSTALLATION
4. INSTALLATION DOCUMENTATION – CHANGES
5. NEWS – CHANGES in 6.40

1.0 Pre-Installation

1.1 Changes in Default Connectivity – Thin Client

Beginning with the new 640 Patch Collection we support both the Thin Client (CLI and JDBC Drivers) and Fat Client (DB2 Connect) for SAP NetWeaver 2004 (SAP Web AS 6.40).
All new installations support only the Thin Client, althoughLifecycle Management Taskssuch asExportorDropsupport systems using the DB2 Connect connectivity.

1.2 JDK Environment Variable on z/OS

Before you start the installation, you must set the environment variables depending on your IBM JDK Version.
If you use IBM JDK 1.4, enter the following (C shell):
setenv IBM_JAVA_OPTIONS “-Dfile.encoding=ISO8859-1
-Dconsole.encoding=IBM-1047″
setenv IBM_JVM_NOARGSCONVERSION ON
setenv IBM_JAVA_ENABLE_ASCII_FILETAG ON
If you use IBM JDK 1.5, you do not need to set the environment variables.

1.3 DB2DB6EKEY

You can no longer connect to the database if following is true for your system:
A dialog instance was installed on a central instance with aDB2DB6EKEYother than the default:The central instance is running with aDB2DB6EKEYthat is not the default (+)A dialog instance was installed on this central instance

To install a dialog instance with a changedDB2DB6EKEY, you must specify the environment variableDB2DB6EKEYin the environment that your are using to run the installation of the dialog instance.
If your dialog instance is already installed you will not be able to connect to the database with your central instance anymore.
In this case you have to do the following:logon as adm to the application server where your dialog instance is runningchange the value of theDB2DB6EKEYenvironment variable to the value you use for the central instanceexecute the following command:
dbdb2pwd -create You export a system with aDB2DB6EKEYother than the defaultLogon to your system with the user you use to run SAPinst. Note that this user must always have root (Unix) or Administrator (Windows) permissions.Set the environment variableDB2DB6EKEYto the value you use.Follow the steps described in 2.3 to download and exchange the control.xml file.

1.4 Obtaining the DVDs

To install the 6.20/6.40 Patch Collection Edition May 2008 you need the following DVDs:
SAP Installation Master (51033746_*). Choose the appropriate Installation Master DVD for your Application Server.NW04 6.40 AK Kernel DB2 for z/OS (51033849).DB2 Driver for ODBC and CLI V9 FP3 (51033060).SAP NW04 SR1 SAP J2EE Engine (51030724_*). Choose the appropriate DVD for your Application Server.

You can either order the DVDS directly from SAP, or you can search for them in theSAP Software Distribution Centeras follows:
a. Go tohttp://service.sap.com/swdc –> Download –> Installations and Upgrades –> Search for Installations and Upgrades
b. Enter thematerial number (e.g. 51033849 for the Kernel)as the search term.
Alternatively, you can download it from theSAP Software Distribution Centerat:
http://service.sap.com/swdc –> Download –> Installations and Upgrades –> Entry by Application Group –> SAP NetWeaver –> SAP NETWEAVER –> SAP NETWEAVER 04 –> Installation and Upgrade –> z/OS –> DB2/OS390.

2.0 Installation Process
2.1 Java Connect User and Java Schema

For Java installations, we now use a Java Connect User, which is alwaysSAPDBand the Java Schema.
The Java Connect User must exist on your database host before starting the installation. Its name cannot be changed.
The dialogJava System -> Database Schemais used to specify the Java Connect User, although it is described as being the Java Schema. Here you must enter the password of yourSAPDBuser.
Later in dialogIBM DB2 for z/OS -> J2EE Database Schema,you specify the schema which is then used to create the database objects.

2.2 Exporting or Dropping a System with changed connectivity type

You have to be aware of the following if you moved your connectivity from DB2 Connect (Fat Client) to Thin Client and you want to export or drop this system.
Forallapplication servers:
Make sure that the JDBC driver is located in
\sapmnt\\\db2\jdbc.
ForUnixApplication Servers:
You must check theLIBPATH(AIX) orLD_LIBRARY_PATH(Linux) variable in the following:
.dbenv_.sh.dbenv_.csh

Note that theLIBPATH(AIX) orLD_LIBRARY_PATH(Linux) value must not contain any other environment variable.
Example:
CLILIBPATH=/usr/sap///clidriver/lib
LIBPATH=$LIBPATH:$CLILIBPATH;export LIBPATH
Must be changed to:
LIBPATH=$LIBPATH:/usr/sap///clidriver/lib;export LIBPATH

2.3 Problems fixed by the attached control.xml files
You plan to export a system with a ABAP Schema other than the default schema SAPR3You plan to export a system with a DB2DB6EKEY other than the defaultYou plan to export a system with a VCAT other than the DBSIDLogon to your system with the user you use to run SAPinst. Note that this user must always have root (Unix) or Administrator (Windows) permissions.Set the environment variableVCATto the value you use.Follow the steps described below to download and exchange the control.xml file.You plan to import a system with the Migration MonitorYou plan to use the new fastload utilityYou plan to drop a system with a Java schema other than the default

Download one of the attached files:
Windows: controlWIN.SARUnix: controlUNIX.SAR

Then continue as follows:
o Start SAPinst
o Select the ABAP Database Content Export Service
o Select the Database Export Method and press Next
o Press Cancel to stop the SAPinst
o Go to the installation directory
o Extract the downloaded file using SAPCAR
- Windows:
\usr\sap\\SYS\exe\run\sapcar -xvf
controlWin.SAR
- Unix:
/usr/sap//SYS/exe/run/SAPCAR -xvf controlUnix.SAR
o Restart SAPinst
o Choose Continue old installation