SAP System Installation: IBM

AS/400

Release 4.6C

®
SAP AG • Neurottstr. 16 • D-69190 Walldorf
51 009 979
SAP System Installation: IBM AS/400 SAP AG

Copyright
©Copyright 2000 SAP AG. All rights reserved.

No part of this brochure may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of
Microsoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX®-OnLine for SAP and Informix® Dynamic Server are registered trademarks of
Informix Software Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide
Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of
Technology, 545 Technology Square, Cambridge, MA 02139.

JAVA® is a registered trademark of Sun Microssystems, Inc. , 901 San Antonio Road, Palo Alto,
CA 94303 USA.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
ADABAS® is a registered trademark of Software AG.
SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com
Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP
Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management
Cockpit, SEM, SAP DB are trademarks or registered trademarks of SAP AG in Germany and in
several other countries all over the world. All other products mentioned are trademarks or
registered trademarks of their respective companies.

Ordering Information
To order additional copies of this documentation, use the product number 51 009 979.

2 May 2000
SAP AG SAP System Installation: IBM AS/400

Typographic Conventions

Type Style Represents

Interface Text Words or characters that appear on the screen. This
includes system messages, field names, screen titles,
pushbuttons, menu names, and menu options.
Document Title Cross-references to other documentation
User Entry Exact user entry. These are words and characters that
you enter exactly as they appear in the documentation.
File Name File names, batch files, paths or directories, and
screen messages
<Variable User Variable user entry. Pointed brackets indicate that you
Entry> replace these words and characters with appropriate
entries.
NAME Names of elements in the SAP System. These include
report names, program names, transaction codes,
table names, and ABAP language elements.
KEY Keys on your keyboard. These include function keys
(for example, F2) and the ENTER key.

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

Tip

May 2000 3
SAP System Installation: IBM AS/400 SAP AG

Contents

SAP System Installation: IBM AS/400 ............................................ 6

1 Installation Planning .......................................................................... 7
1.1 Hardware and Software Requirements Check ...................................................................8
1.2 SAP Directory Structure......................................................................................................9
1.3 Multiple SAP Systems on a Single AS/400 System .........................................................10
1.4 Installation Check List .......................................................................................................12
1.5 Installing the Qshell...........................................................................................................15
2 Installation Preparations ................................................................. 16
2.1 Checking and Adjusting AS/400 System Values ..............................................................17
2.2 Adjusting Startup Program QSTRUP................................................................................20
2.3 Adding a User ASP ...........................................................................................................22
2.4 Configuring TCP/IP ...........................................................................................................24
2.5 Obtaining the Necessary Documentation .........................................................................27
2.5.1 Obtaining the Notes.....................................................................................................27
2.5.2 Accessing SAP Documentation ..................................................................................28
2.5.3 Accessing IBM Documentation ...................................................................................29
3 The SAP System Installation........................................................... 30
3.1 Preparing to Use INSTGUI ...............................................................................................31
3.2 Starting INSTGUI ..............................................................................................................31
3.3 Loading the Objects Required for Installation...................................................................32
3.4 Copying the Command Files from CD ..............................................................................33
3.5 Starting R3SETUP ............................................................................................................34
3.6 Central or Standalone DB System installation..................................................................34
3.7 Installing a Central Instance with Database .....................................................................36
3.8 Installing a Database Instance..........................................................................................40
3.9 Installing a Central, Dialog, or Gateway Instance.............................................................44
3.10 Installing the SAP Frontend Software.............................................................................46
4 Post-Installation Activities .............................................................. 47
4.1 Actions Necessary on Preloaded SAP Systems ..............................................................49
4.2 Granting Authorizations for Operating System Collector Programs .................................49
4.3 Installing and Using the SAP License...............................................................................50
4.4 Starting and Stopping the SAP System ............................................................................51
4.5 Starting SAP Presentation ................................................................................................52
4.6 Logging on to the SAP System.........................................................................................53
4.7 Changing Passwords for User Profiles .............................................................................54
4.8 Deleting the R3SETUP Library and Installation Directory ................................................54
4.9 Accessing a Remote Database ........................................................................................55
4.10 Configuring SAProuter and SAPNet - R/3 Frontend.......................................................56
4.10.1 Example of How to Configure a TCP/IP Connection ................................................57
4.11 Performing a Full Backup ...............................................................................................59

4 May 2000
SAP AG SAP System Installation: IBM AS/400

5 The R3SETUP Tool ........................................................................... 61

5.1 INSTGUI.........................................................................................................................64
5.2 R3SETUP Command Files ............................................................................................65
5.3 R3SETUP Messages .....................................................................................................66
5.4 Using R3SETUP Online Help.........................................................................................67
5.4.1 Configuring Your AS/400 as an HTTP Server ............................................................68
5.5 Continuing an Interrupted Installation ............................................................................70
6 Error Handling .................................................................................. 71
6.1 Log File <service>.log ....................................................................................................72
6.2 Handling Problems During the Database Load..............................................................73
6.3 Correcting Errors in RFC Steps .....................................................................................74
6.4 Fax Form for Reporting Installation Problems ...............................................................75
7 Additional Information ..................................................................... 78
7.1 AS/400 Library Structure ................................................................................................79
7.2 OS/400 Integrated File System ......................................................................................80
7.3 Code Page Tables..........................................................................................................82
7.4 Restoring a Backup ........................................................................................................86
7.5 Editing Stream Files .......................................................................................................88

May 2000 5
SAP System Installation: IBM AS/400 SAP AG

SAP System Installation: IBM AS/400

Purpose
This documentation explains how to install one or more SAP Systems on IBM AS/400. You
perform the various installation steps in the given sequence, using the SAP installation tool
R3SETUP. You can install the following types of SAP Systems:
• Central system, in which the SAP central instance and the database instance are on the
same host machine.
• Standalone database system, in which the SAP central instance and the database instance
are on different host machines.
You can also install dialog and gateway instances and additional components. The installation of
frontends for the SAP System is described separately in the documentation Installing SAP
Frontend Software for PCs.

Integration
For information about:
• Support for new OS/400 operating system releases
• Support for SAP Systems with different operating system releases
• Release planning
refer to the SAP on AS/400 release strategy documentation in the SAP Library. To access this
documentation, choose BC - Basis Components → Operating System Platforms (BC-OP) → R/3
on IBM AS/400 → R/3 on AS/400 Release Strategy.

Features
For a standard SAP System installation, SAP provides the R3SETUP tool. This has a graphical
user interface (GUI) called INSTGUI that allows you to watch the progress of the installation and
see all messages issued by R3SETUP. You can call online help from the INSTGUI while you
perform the installation. You can start INSTGUI on a remote computer if you want, since it
functions as a client to the R3SETUP server.
For more information, see The R3SETUP Tool [Page 61] and INSTGUI [Page 63].

Constraints
This documentation only applies if you are installing your SAP System on IBM AS/400.

6 May 2000
SAP AG 1 Installation Planning

1 Installation Planning
Purpose
Before you begin with the practical installation tasks, it is essential to have a planning phase in
which you make a number of fundamental decisions that influence the subsequent installation
procedure. Careful planning is a prerequisite for the successful installation of the system.

Process Flow
When you plan the installation, you have to:
• Decide on the optimal configuration for the system
• Make sure that you can meet the hardware and software requirements specified by SAP

System Configuration
The configuration of the system is generally planned well in advance of the installation together
with the hardware vendor. Configuration planning involves deciding whether a central system or
standalone database system is to be installed, and how many dialog instances and frontends are
required.
The configuration is worked out with the hardware partner on the basis of sizing information that
reflects the system workload. Details such as the set of applications that are to be deployed, how
intensively these are to be used, and the number of users enable the hardware vendor to
recommend a configuration that performs well. SAP provides a Quick Sizer tool that helps to
determine the right combination of resources such as CPU, disk space, and memory making it
easier to plan an appropriate hardware infrastructure.

Checking SAP Hardware and Software Requirements

SAP specifies minimum hardware and software requirements for different system configurations
to ensure that a newly installed system performs well. In the planning stage, it is essential that
you look at these requirements to make sure that they can be met.
For more information, see Hardware and Software Requirements Check [Page 8].

May 2000 7
1 Installation Planning SAP AG

1.1 Hardware and Software Requirements Check

Hardware Requirements
Before installing an SAP System on AS/400, you should have obtained detailed sizing
information from your IBM representative.

Space Requirements
The amount of space required for an SAP System on IBM AS/400 is dependent on many
variables, such as:
• Size of the database
• Number of work processes
• Number of users
Sizing recommendations are made by the IBM Competency Center. However, approximately 25
GB DASD are required to start an SAP System. We recommend that ASP (auxiliary storage pool)
usage in SAP production systems should not exceed 70%.

Frontend Requirements
R/3 on AS/400 supports the following frontend products:
• Windows 95
• Windows 98
• Windows NT
• IBM Network Station with WinCenter
• OS/2 Warp
To connect frontends, you require a Token Ring or Ethernet LAN adapter.
For details of frontend hardware and software requirements, see Check List - Installation
requirements: Frontends.

Requirements for the SAP Online Documentation

To install the SAP HTML documentation, you require IBM product DG1 for the Web server (as of
OS/400 Release V4R3 or R/3 Release 4.0B).

Operating System Requirements

R/3 Release 4.6C is released for OS/400 V4R4M0.

For information about which OS/400 versions have been released for R/3 on IBM
AS/400, see SAP Note 156557.
For the latest information on CUM package release levels and OS/400 corrections related to
Release 4.6C of R/3 on IBM AS/400, refer to IBM Information APAR II11832:
To load an APAR onto your AS/400 system via the IBM ECS link, enter the command:
SNDPTFORD PTFID((<Info APAR ID>))

8 May 2000
SAP AG

To load the IBM Info APAR for V4R4, enter SNDPTFORD PTFID((II11832))
SAP Note 83292 gives an overview of releases and PTFs for R/3 on IBM AS/400 and gives the
URL of the IBM website containing the Info APARs.

DB2 for OS/400

The DB2/400 database is fully integrated into the OS/400 operating system. No separate
installation phase is required for the database code and database tools.
Only homogeneous environments are supported.

1.2 SAP Directory Structure

The graphic shows part of the SAP directory structure. The directories in the shaded box are
located by default on the database server.

USR Qfile Svr.400 QSYS.LIB

<hostname> R3<REL>OPT.LIB
sap
sapmnt
trans DW.PGM
trans R3transdb.4.PGM
<SID> <SID>
TPOS4DB4.PGM

inst SYS profile global exe

data log work profile global exe

run

Disp+work
Key
soft link
R3trans
hard link tp

To display the directory structure:

1. Enter WRKLNK and choose F4 to display possible entries.
2. Change the value entered for parameter Detail from *PRV to *EXTENDED.
3. Change the value entered for parameter Display option from *PRV to *ALL.
(You only have to change these values once. The system remembers the values last used.)
These parameters control how much information is displayed in the Work with Object Links
list.

May 2000 9
SAP AG

Important SAP File Systems

/usr/sap/trans
Used for SAP network-wide data, such as for transports between SAP Systems.
/usr/sap/<SID>/<role><instance>/log
Contains system log entries.
/sapmnt
Accessed remotely via QFileSvr.400.
/sapmnt/<SID>/profile
Contains all startup, instance, and default profiles.
/tmp/<SID>
By default /tmp/<SID> contains all your installation files.

1.3 Multiple SAP Systems on a Single AS/400

System
R/3 on AS/400 allows installation of multiple SAP Systems on a single AS/400 machine (provided
space exists). However, we recommend that you isolate your SAP production system as far as
possible from your test and development systems. The degree of isolation you opt for can range
from running each SAP System on a separate AS/400 to having all the environments on a single
machine.
If you decide to implement multiple SAP Systems on a single AS/400 system, you need to be
aware of the risks involved.

Importance of an Independent Testing Environment

If you have both your production and development/test systems on the same machine, you will
not be able to test PTFs (IBM program temporary fixes) and cumulative packages in an
independent testing environment without immediately affecting the production system.
The same applies to operating system (OS/400) upgrades. If these initially take place in an
independent test environment, it allows you to identify any customer-specific problems (such as
problems resulting from any modifications you might have made to the standard system) away
from the live environment.
If you have more than one SAP System on a single AS/400 machine, you can test SAP upgrades
independently. However, if you test an SAP upgrade on a separate AS/400 machine, it has the
advantage that a test SAP upgrade will not take away resources from the production system.

Possibilities for Resource Distribution

• Memory: Running SAP Instances in Separate Subsystems
Each SAP System with its associated database can have multiple instances. Each instance
runs in a separate OS/400 "subsystem". (A subsystem is an operating environment in which
the system coordinates processing and resources.) The subsystem definition allows you to
define and allocate individual memory pools to the subsystem. These memory pools cannot

10 May 2000
SAP AG 1 Installation Planning

be accessed by users from any other SAP instance. They can be tuned to allow dynamic
allocation to occur on memory pool activity.
• Disks: Separate ASPs for Each SAP System
On AS/400 systems the installed disk capacity can be segmented to provide a separate
auxiliary storage pool (ASP) for each SAP System. You can then allocate specific disk drives
to each user ASP created. This helps to minimize the impact of disk activity of one SAP
environment on other SAP environments.
• Processors: Long-Running Tasks Can Slow Down the Production Environment
Regardless of the number of processors involved, the AS/400 system manages them all as a
single entity. It dispatches tasks to its processors and ensures that usage is balanced. A
long-running program or other task encountered during development or testing can have an
impact on production activity if these SAP Systems are running on the same machine. You
can minimize the potential impact of this by running development and test systems at a lower
priority than the production system.

Using a Shared Kernel Library

You can opt to run SAP Systems with either shared or separate kernel libraries. If you are
installing a second production system, you may decide to share the kernel library to save space.
If you have a production system and are now installing a test system, it is advisable to use
separate kernel libraries.
The installation does not currently support sharing of a kernel library at installation time. You
always have to load the kernel that is on the SAP kernel CD.
If you want to share a kernel after the installation, run the commands:
RMVR3KRN <SAP_SYSTEM_ID>
DLTKRNLIB(*YES)
APYR3KRN <SAP_SYSTEM_ID>
KRNLIB<kernel_library_name>
DLTSQLPKG(*YES)

May 2000 11
1 Installation Planning SAP AG

1.4 Installation Check List

Definition
The installation check list is a summarized version of the installation procedure

The name of the SAP System is abbreviated in this documentation to SID or

<SID> (SAP system ID). An example of an SAP system ID might be “C11”.
Use
Perform the installation steps in the order given.

Installation Preparations
Activity
Update code page-specific entries (see note 15023).
Check that the hardware and software requirements [Page 8] have been met.
Obtain the notes: 300097 (4.6C Installation Note), 83292 (Information on PTFs and Info
APARs)
Read the Notes carefully.
Check that you have all the necessary documentation listed in Obtaining the Necessary
Documentation [Page 26].
Check that all necessary PTFs have been installed (see note 83292).
Check and adjust AS/400 system values. [Page 16]
Check that a user ASP has been installed.
Add a user ASP [Page 22] if this has not already been done.
Check the device description for the optical device.
Enter AS/400 command WRKDEVD and check OPT01.
Configure TCP/IP [Page 24].
Check that TCP/IP has been configured correctly and is active.
Check the status of TCP/IP with AS/400 command WRKACTJOB, subsystem QSYSWRK,
job QTCPIP.
Start TCP/IP with AS/400 command STRTCP.
Start subsystem QSERVER and subsystem job QPWFSERVSD on each AS/400 system.
Use ping to database server and the reverse. Start subsystem QSERVER with AS/400
command STRSBS QSERVER.
Check that the database monitor is switched off.

12 May 2000
SAP AG 1 Installation Planning

The SAP System Installation

Activity
Copy INSTGUI.EXE from the AS/400 kernel CD to directory <INSTGUIDIR>.
Unpack the R3SETUP online help.
Change the location of /usr/sap/trans (3-tier systems and systems where 2 AS/400
machines share a common transport directory).
Insert the SAP kernel CD into the CD drive on your AS/400 machine.
To load the objects required for installation and configuration from CD, enter AS/400
command LODRUN *OPT DIR(‘/OS400/AS400/INSTALL’) or LODRUN
<CD_device_description_name> DIR(‘/OS400/AS400/INSTALL’).
Type /QOPT at CD path prompt.
Copy all the installation templates from CD:
CPYR3S
Start R3SETUP, specifying the command file for the installation service you require:
R3SETUP ‘-f <installation_service.r3s>’
For example: R3SETUP option 1. For R3SETUP parameter list, enter:
R3SETUP ‘-f dialog.r3s’
Enter or confirm the information required for installation. The information required varies
according to the installation service you have selected.
Non-Latin-1 installations only: Adjust code page setting in table TCPDB. For
instructions, see notes 99792 and 15023.
Install frontends as described in the guide Installing Frontend Software for PCs.

Post-Installation Activities
Activity
Fax the form “Request Fax License Key/Installation Report” to SAP
Install the permanent SAP license
R3SETUP option 3 (Work with SAP license information)
Install optional components
R3SETUP option 5 (Load RFC SDK library) or option 6 (Load CPI-C SDK library).
Change the password for supplied profile <SID>OFR with AS/400 commands CHGPWD
(to change your own password) or CHGUSRPRF (to change someone else’s password).
Make sure you do this on all AS/400 systems. Passwords must be identical on all
systems.
Ensure that there are no active jobs with:
WRKACTJOB SBS(R3_<instance_number>)

May 2000 13
1 Installation Planning SAP AG

Start SAP presentation [Page 52].

Check the Workbench Organizer.
Delete library R3SETUP.
Delete directory /tmp/R3SETUP
Delete installation logs (if no longer needed):
Enter RRM ‘/tmp/C11’
Verify system/instance configuration profiles.
Verify that the batch scheduler has been started.
Verify that the system language defaults correctly at sign-on.
Verify any additional languages.
View the system log for errors and warnings.
Verify that the SAP operating system performance monitor has been started.
Verify that AS/400 and SAP times correspond.
Perform a language import (if required).
Set up and test (1) printer.
Set up the central system log.
Connect to the SAP Service Network.
Test system integrity using transaction SICK.
Copy client 001.
Perform a full backup [Page 59].

14 May 2000
SAP AG 1 Installation Planning

1.5 Installing the Qshell

Use
We recommend that you install the Qshell on your AS/400.
This gives you a greater flexibility in dealing with stream files because you can use a large set of
utilities that are common on UNIX systems, for example grep , tail , or ls .
In addition, Qshell is compatible with ksh scripts in UNIX.

Procedure
1. Install the Qshell Utilities for AS/400 (product 5799-XEH).
2. Install option 30 of the Qshell Interpreter (product 5769SS1).
For more information on Qshell and installing the Qshell Utilities for AS/400 and the Qshell
Interpreter, see the following Internet URL:
http://www.ibm.com/as400/developer/qshell

May 2000 15
2 Installation Preparations SAP AG

2 Installation Preparations
Purpose
Before you start the installation, you must prepare the operating system and the SAP System.

Prerequisites
You have completed the planning phase.

Process Flow
1. Check and adjust AS/400 system values [Page 16]
2. Adjust startup program QSTRUP [Page 20]
3. Add a user ASP [Page 22] (if necessary)
4. Configure TCP/IP [Page 24]
5. Obtain the necessary documentation [Page 26]

Result
You can now start the SAP SYSTEM installation.

16 May 2000
SAP AG 2 Installation Preparations

2.1 Checking and Adjusting AS/400 System

Values
Use
To allow the SAP System to run optimally on AS/400, you have to adjust a number of AS/400
system values.

Prerequisites
• You have entered the following command to switch on work control block compression:
CHGIPLA CPRJOBTBL(*ALL)
This allows work control block space to be reused.
• The recommendations given below for system values QACTJOB, QTOTJOB, QADLACTJ, and
QADLTOTJ assume that only the SAP System is running on the AS/400. If you are also
running other applications, you might need to preallocate more jobs. The values QACTJOB
and QTOTJOB are used for initial space allocation at IPL (initial program load) time for the
number of active jobs and the total number of jobs that will be in the system at any one time.
If or when the allocated number of either type is reached, the system values QADLACTJ and
QADLTOTJ determine how many additional jobs of that type are to have space allocated.

Procedure
• To display all system values, enter:
WRKSYSVAL SYSVAL(*ALL) OUTPUT(*PRINT)
• To display or change individual system values, enter:
WRKSYSVAL SYSVAL(<system_value_name>)
and choose option 5 (Display) or option 2 (Change).
After changing a system value, select option 5 (Display) to check your changes.

To avoid having to run an IPL (initial program load) several times, we recommend
that you delay the IPL until you have made all the necessary changes to the
system values (and added a user ASP, if necessary).

System Recommended Explanation

Value Value
QACTJOB Set system value QACTJOB to a value close to the
number of jobs usually on your system. (To find out
the number of jobs, use the command
WRKACTJOB. For a 2-tier system, this is normally
about 50.

May 2000 17
2 Installation Preparations SAP AG

QTOTJOB 500 To begin with set system value QTOTJOB to 500.

When you have worked with the SAP System for a
while, adjust this value to the value you usually see
in the field Jobs in system on the WRKSYSSTS
command.
QADLACTJ 20 Set both system values to 20. This allocates space
and for 20 additional jobs whenever the current
QADLTOTJ maximum number of jobs is reached.
QSECURITY 30 or 40 System value QSECURITY controls the level of
security enforced on your system. Set QSECURITY
to at least 30 to ensure object security for the SAP
objects to be installed.
Security levels 10 and 20 are theoretically
possible. However, we do not recommend that you
use either of these values. Security level 10
provides neither password nor object protection.
Security level 20 provides no object protection.
To activate this system value, you must perform an
IPL (initial program load).
QCTLSBSD QBASE or QCTL When you start your AS/400 system, the program
specified in system value QSTRUPPGM(QSTRUP) is
called. This startup program is responsible for
starting the subsystems.
When this startup program runs, system value
QCTLSBSD is queried. The specifications made for
this value decide whether subsystem QBASE or
subsystems QCTL, QINTER, QBATCH, QSPL, QCMN,
and QSERVER are started.
Two settings are possible for system value
QCTLSBSD (controlling subsystem).
• QBASE
The controlling subsystem is QBASE.
Subsystem QBASE is started.
• QCTL
The controlling subsystem is QCTL.
Subsystems QCTL, QINTER, QBATCH, QSPL,
QCMN, QSERVER are started. Your change is
activated the next time the AS/400 is started. To
activate the subsystems, you have to restart the
AS/400 system.

18 May 2000
SAP AG 2 Installation Preparations

QDATE Check the system date and adjust if necessary.

(The date format is determined by system value
QDATFMT.)
QTIME Check the system time and adjust if necessary.
QJOBMSGQF System value QJOBMSGQFL allows you to specify
L how you wish the job message queue to be
handled if it overflows. The default value is
*NOWRAP. If this value is set, the AS/400 system
sends a message when the queue is full and ends
the job that is currently running. When an SAP
System is installed, a large amount of information
is sent to the job message queue. For this reason,
system value QJOBMSGQFL is automatically
changed to *WRAP during installation. If the queue
becomes full, the oldest entries will be deleted and
the current job will not be interrupted. Once
installation is complete, the system value is
automatically returned to its original value.
QPFRADJ If you have adjusted the size of the AS/400 pools
as described in Note 49201, you have to set
system value QPFRADJ to 0 to deactivate
automatic performance adjustment to prevent your
settings from being lost after an IPL.
QSTRUPPGM To cause your adjusted startup program to be
started after an IPL (initial program load), change
Startup program to QSTRUP and Library to QGPL.
QAUTOCFG 1 Set system value QAUTOCFG to 1 to allow device
descriptions to be configured automatically.
QBASACTLV Use the following QBASACTLVL is the base storage pool activity level.
L formulas: This value indicates how many system and user
threads can compete at the same time for storage in
Database-server:
the base storage pool. This pool is specified in the
(number of R/3 work
subsystem descriptions as *BASE. QBASACTLVL
processes on
depends on the types of jobs being run in this
DBServer + number
storage pool. The lower limit for QBASACTLVL is 1.
of R/3 work
processes on each The Query Optimizer uses that value to determine a
remote application "fair share" of memory to use when calculating the
server ) * 1.20. best way to optimize a query. It takes the amount of
memory in the Pool and divides by QBASACTLVL
Application server:
and will not pick an optimization that would use more
(number of R/3 work
than this value.
processes on
application server ) * QBASACTLVL should therefore be set as low as
1.20. possible. It must be larger than the total number of
work processes, but not much larger.
Database-server
and Application Be aware that this value does not affect only SAP-

May 2000 19
SAP AG

server : (number of work processes but also processes which belong to

R/3 work processes ) other applications running on your system.
* 1.20.

After changing all the system values, perform an IPL to activate all your changes. You have to do
this before starting the SAP System. (If you need to add a user ASP (auxiliary storage pool), wait
until you have done this before performing the IPL.)

Result
You have made the necessary adjustments to AS/400 system values to enable the SAP System
to run correctly on AS/400.

2.2 Adjusting Startup Program QSTRUP

Use
Starting TCP/IP Automatically
To run the SAP System on AS/400 you require TCP/IP. Since it would be inconvenient to have to
start TCP/IP automatically after each IPL (initial program load), we recommend that you insert
the command for start TCP/IP into your startup program.

Starting the Job QXDAEDRSQL Automatically

The job QXDAEDRSQL is a prerequisite for working with the SAP System. It is required for the
following tasks:
• Calling APIs from the ABAP Dictionary and from CCMS (Computing Center Management
System)
• Transports between different AS/400 systems

If you have other SAP Systems with earlier R/3 releases, you also require the job
QXDAEDRSQL in your startup program QSTRUP. The procedure for including
QXDAEDRSQL in your startup program is described in the installation guides for
releases prior to 46B.
To cause the job QXDAEDRSQL to be started automatically after each IPL, enter the following
code into program QSTRUP:
STRTCPSVR SERVER(*EDRSQL)
MONMSG MSGID(CPF0000)

Enabling the Use of OfficeVision/400

If you use OfficeVision/400, you can insert a command in your startup program to start
subsystem QSNADS automatically. The IBM default is for this subsystem not to be started.

20 May 2000
SAP AG 2 Installation Preparations

Prerequisites
To edit startup program QSTRUP, you require either system editor SEU or command EDTF.

Procedure
1. As no source statements are provided for startup program QSTRUP, you have to retrieve the
CL (control language) source statements from CL program QSTRUP. (This is possible if
parameter RTVCLSRC (*YES) was specified when the program was created.) To retrieve
the CL source statements, enter:
RTVCLSRC PGM(QSYS/QSTRUP) SRCFILE(QGPL/QCLSRC) SRCMBR(QSTRUP)
If the source statements are retrieved successfully, this message is displayed:
CL source retrieved for program QSTRUP in QSYS.
2. If you are editing the program with SEU, enter:
STRSEU SRCFILE(QGPL/QCLSRC) SRCMBR(QSTRUP)
3. To start TCP/IP automatically, enter the command:
STRTCP

Start TCP/IP before you start subsystem QSERVER. The parameter DLYJOB
DLY(30) gives TCP/IP time to start before the subsystem is started.
If you decide not to or are unable to edit program QSTRUP, you can start TCP/IP
manually. At this point, QSERVER is normally already running. Before starting
TCP/IP, shut down the subsystem with command ENDSBS.
4. To start the job QXDAEDRSQL automatically, enter the following into program QSTRUP:
STRTCPSVR SERVER(*EDRSQL)
MONMSG MSGID(CPF0000)
5. For users with OfficeVision/400: To start subsystem QSNADS, enter:
STRSBS SBSD(QSNADS)

Here is an example of how the program modifications might look:

/* */
/* START ADDITIONAL PROGRAM */
/* */
STARTTCP: /* INSERT */
QSYS/STRTCP /* INSERT */
MONMSG MSGID(CPF0000) /* INSERT */
/* START TCP/IP BEFORE QSERVER SO THAT ALL JOBS IN QSERVER */
/* ARE UP AND RUNNING */
DLYJOB DLY(30) /* INSERT */
QSYS/STRSBS SBSD(QSERVER)
MONMSG MSGID(CPF0000)
QSYS/STRSBS SBSD(QSNADS) /* INSERT IF OFFICE */
MONMSGMSGID(CPF0000) /* VISION IN USE */
STRTCPSVR SERVER(*EDRSQL) /* INSERT */
MONMSGID MSGID(CPF0000) /* INSERT */
/* */
6. To leave the editor, choose F3.
7. After you have made your changes to the source statements in program QSTRUP, you have
to create the CL program from the source code.

May 2000 21
SAP AG

Do not change the original QSTRUP program supplied by IBM. Instead, create a
modified version of QSTRUP in library QGPL. If you do this, the program will not be
overwritten when an IBM system upgrade is performed.
To do so, enter:
CRTCLPGM PGM(QGPL/QSTRUP) SRCFILE(QGPL/QCLSRC) SRCMBR(QSTRUP)
If the program is created successfully, you receive this message:
Program QSTRUP created in library QGPL.
8. To make sure that your adjusted startup program (and not the default startup program) is
started after an IPL, adjust system value QSTRUPPGM. See Checking and Adjusting AS/400
System Values [Page 16].

Result
The programs and jobs you have included in your startup program are started automatically
when you perform an IPL (initial program load) of your AS/400 system. To check if TCP/IP is
running, enter WRKACTJOB. Look for subsystem QSYSWRK, job QTCPIP. If the job is running, the
entry in the status column is normally DEQW.

2.3 Adding a User ASP

Use
We strongly recommend that you keep your journal receivers in a separate user ASP (auxiliary
storage pool). (A user ASP will normally have been set up on your AS/400 when you receive it.)
We recommend that you allow 4 GB (the minimum size) for your user ASP. If you have a very
busy system, you can allow more disk unit (up to 8 GB). However, we recommend that you select
the minimum size and increase the size later if you find that journal receiver switches are taking
place too frequently or your user ASP is being filled up too quickly. The procedure consists of two
stages:
1. Checking that a user ASP has been set up and, if so, that it has been assigned sufficient
space (see the recommendations above).
2. Adding a user ASP (if required).

Checking the User ASP

1. Enter STRSST (Start System Service Tools)
2. Select option 3 (Work with disk units)
3. Select option 2 (Work with disk configuration)
4. Select option 1 (Display disk configuration)

22 May 2000
SAP AG 2 Installation Preparations

5. Select option 2 (Display disk configuration capacity). You can see whether a user ASP exists
and, if so, make sure that it still contains enough space (see the recommended values given
above).

You will encounter problems during installation if you have an existing user ASP
that contains journal receivers or save files belonging to libraries that are located
in another ASP. In this case, you will not be able to create additional libraries in
this user ASP and the installation will fail.
If you have sufficient disk space, we recommend that you work around this
problem by adding a second user ASP (for example, ASP 3). The alternative
would be to leave the journal receivers in the system ASP. However, we do not
recommend this for security and performance reasons.
For detailed information, see the IBM documentation OS/400 Backup and
Recovery Version 4 (SC41-5304).
Adding a User ASP
1. Perform a manual IPL (Initial Program Load) of your AS/400.
− Set the mode to “manual” on the control panel
− Enter the AS/400 command:
PWRDWNSYS *IMMED RESTART(*YES)
2. Select option 3 (Use Dedicated Service Tools (DST)) from the menu that appears.
3. Sign on by entering your DST user and password.
4. Select option 4 (Work with disk units)
5. Select option 1 (Work with disk configuration).
6. Select option 3 (Work with ASP configuration).
7. Select option 6 (Move units from one ASP to another).
8. Specify the ASP to which you wish to move specific units by entering the number of the ASP
next to the relevant unit in the column New ASP.
9. Choose ENTER.
10. In the next screen, choose ENTER to confirm that you wish to continue.
11. The Confirm Move of Units display appears. To confirm your choices, choose ENTER. Moving
units will take several minutes.
12. Continue the procedure and complete the IPL.
13. Switch back to normal mode.

May 2000 23
2 Installation Preparations SAP AG

2.4 Configuring TCP/IP

Use
Follow this procedure to integrate the AS/400 machine into your TCP/IP network.

Prerequisites
Before configuring TCP/IP, do the following:
• Make sure you have the following information:
− The protocol of the Local Area Network to which your AS/400 machine is attached (that
is, whether it is Token Ring or Ethernet)
− The IP addresses of your AS/400, subnet mask, and router or gateway
− The local domain name
− The AS/400 host name
• Decide on your AS/400 host name. The host name cannot be longer than 8 characters. If you
have already specified a name longer than this, change the name to one that does not
exceed eight characters.

The TCP/IP configuration on AS/400 is case sensitive. Do not enter your host
name once in uppercase and then in lowercase. It is important that you enclose
your host name entry in single quotation marks. Otherwise the AS/400 will read
the characters as upper case characters.
Procedure

An “IP address” is a unique address in a TCP/IP network for a particular AS/400

system.
A “subnet mask” is a mask used to divide a single network address into multiple
logical networks.
1. To call the TCP/IP Configuration Menu, enter:
GO CFGTCP or CFGTCP.

24 May 2000
SAP AG 2 Installation Preparations

2. Choose option 1 (Work with TCP/IP interfaces):

You need two entries: one for the loopback entry and one for the IP address of your AS/400
system.
The loopback address always has the IP address 127.0.0.1, subnet mask 255.0.0.0
and line description *LOOPBACK.
To add an entry, type option 1 (ADD) and choose ENTER.
Add entries for the first three fields and accept the default values for the other fields.
3. If the route to the remote host, in this case the PC workstation, is through a gateway, or the
remote host resides in a different network or subnetwork to the local host, it will be necessary
to configure a route.
Choose option 2 from the Configure TCP/IP menu to work with TCP/IP routes and add an
entry containing your router’s IP address.
4. The local host table on the AS/400 system contains a list of the Internet addresses and
associated host names for this network. If you are not using a name server, you will have to
add an entry here for the local system and each remote system (PC).
You will need to create a loopback entry and add an additional host name underneath called
LOCALHOST.
5. Select option 12 (Change local domain and host names):
6. Check that you have entries under “Local Domain Name” and “Local Host Name”.
7. To check your local host name, choose option 10 “Work with TCP/IP host table entries”. Your
host name must take the form:
‘<host_name>.<domain_name>’
that is, it combines the two entries found under option 12.

May 2000 25
2 Installation Preparations SAP AG

For example, ‘as0008.wdf.sap-ag.de’

where as0008 is the host name, wdf.sap-ag.de the domain
name.
Remember to use lowercase for these entries.
If the domain name is empty (and your AS/400 is not in a domain), enter your host name a
second time in place of the domain name
(that is, ‘<host_name>.<host_name>’):
For example: ‘as0008.as0008’

It is important that you enclose your host name entry in single quotation marks. If
you do not, the AS/400 will read the characters as uppercase characters.
8. Select option 13 “Change remote name server”:
If you have a remote name server or remote name servers, you will need to define the IP
address here.

Result
The AS/400 machine is integrated into your TCP/IP network.

Testing the TCP/IP Connection

Before proceeding with the kernel installation (that is, the installation of the executable
programs), check that this TCP/IP connection has been set up correctly. To do so, enter the ping
(Verify TCP/IP Connection) command specifying your own system as Remote system. Do this
twice, once specifying only <host_name>, and once <host_name.domain_name>).

In this example it is assumed that the host name is “as0008” and the domain
name “wdf.sap-ag.de”. In this case, your entries would be as follows:
ping ‘as0008’
ping ‘as0008.wdf.sap-ag.de’
After installing the SAP System kernel, check the TCP/IP connection again with the command:
WRKLNK ‘/QFileSvr.400/<host_name>’
Your host name should be displayed under Object link, for example, as0008 for the host in the
example given above.
For more information about TCP/IP configuration, see the IBM documentation TCP/IP
Configuration and Reference.

26 May 2000
SAP AG 2 Installation Preparations

2.5 Obtaining the Necessary Documentation

Before starting installation, make sure you have access to the following information:
• IBM Information APAR II11832 (for V4R4).
These Information APARs contain the latest information on CUM package release levels and
OS/400 corrections related to R/3 on IBM AS/400. You are recommended to load the PTF
release level recommended by IBM in the Information APAR for your OS/400 release level.
• Note 300097
This note contains the latest installation information for Release 4.6C.
See also: Obtaining the Notes [Page 27]

To make sure that you have the most recent versions, obtain the notes
immediately before you start to install.
• Check list - Installation requirements: Frontends
This check list gives the minimum requirements for installing an SAP frontend.
• Installing SAP Frontend Software for PCs
This documentation describes the installation of presentation servers.
• SAP-Supported Network Products
• SAP Language Transport
(if required)

2.5.1 Obtaining the Notes

Make sure you have all the notes required for installing this release of R/3 on IBM AS/400.
Note Number Subject Area Short Text
300097 Installation INST: 4.6C SAP System Installation on IBM AS/400
300103 Installation INST: AS/400: Installing 3-tier systems Rel. 4.6C
83292 Installation Releases and PTFs for R/3 on AS/400
49023 Installation AS/400 client copy
156557 Rel. planning Operating system releases for R/3 4.6x AS/400
99792 NLS NLS on the AS/400
15023 NLS Initializing Table TCPDB
300105 Performance AS/400 Latest News: Rel. 4.6C

May 2000 27
2 Installation Preparations SAP AG

49201 Performance AS/400: Performance settings for the SAP System

47144 Administration AS/400 equivalents to UNIX commands
68732 Administration AS/400: IBM tools EDTF, DSPSTMF, SQLUTIL...
93316 Administration Starting/stopping all instances
84685 Add-ons AS/400: RFC SDK in Release 4.0
88080 Add-ons Archiving with different code pages

2.5.2 Accessing SAP Documentation

Once you have installed the SAP documentation CD, you can access the SAP library by
choosing Help → SAP library in any SAP screen.
The following is a list of documentation from the SAP library referred to in the SAP System
installation documentation:
BC Computing Center Management System
BC SAP High Availability
BC - Printing Guide
BC - Change and Transport Organizer
Client Copy and Transport
BC The SAP Communications Server
BC - SAPconnect
BC SAProuter
BC - SAP License
SAP Internet Applications

Documentation Available in SAPNet

Remote Connection
BC Security Guide (see note 39267 for details)

Printed Guides
Some of these printed guides are included as part of the delivery. You can order additional
copies from SAP.
Title Material Number
Installing Frontend Software for PCs, 51009695
Release 4.6B
SAP Language Transport, Release 4.6B 51009452
R/3 Homogeneous System Copy, Release 51009474
4.6B

28 May 2000
SAP AG 2 Installation Preparations

2.5.3 Accessing IBM Documentation

SAP R/3 Implementation for AS/400 (SG24-4672)
This IBM book is intended to complement the SAP guides and online reference documentation,
placing an emphasis on tasks and usability.
Target readership: SAP customers, Basis consultants, BPs and IBM technical professionals.

AS/400 Softcopy CD Library

Title Document Number
OS/400 Backup and Recovery - Basic SC41-4304
OS/400 Backup and Recovery - Advanced SC41-4305
OS/400 Security - Basic SC41-3301
OS/400 Security - Reference SC41-4302
OS/400 Work Management SC41-4306
OS/400 TCP/IP Configuration and Reference SC41-3420
Performance Tools/400 SC41-4340
DB2 for OS/400 SQL Programming SC41-4611
OptiConnect for OS/400 SC41-4414
OS/400 Network File System Support SC41-4714

AS/400 Redbook Softcopy Library

Title Document Number
IBM AS/400 Printing I GG24-3704
IBM AS/400 Printing II GG24-4028
IBM AS/400 Printing III GG24-4389
The document listed below is included as part of the IBM delivery package.
SAP R/3 AFP: Printing on the AS/400 S544-5412

AS/400 Documentation on the Web

The AS/400 documentation is also viewable using a web browser. The web address for the
AS/400 Online library is:
http://AS400bks.rochester.ibm.com

May 2000 29
SAP AG

3 The SAP System Installation

Purpose
Once you have planned and prepared the installation, you can begin with the actual installation
steps. In this core part of the installation process, you set up the main components that enable
the operation of an SAP System. These are:
• The central instance
• The database instance
• The SAP frontends
• If required, one or more dialog instances
• If required, a standalone gateway instance

Process Flow
1. You install the central instance and database in one of the following ways:
− On a single host as a central system
− On two different hosts as a standalone database system
2. If required, you install one or more dialog instances on additional hosts in the system.
3. You install the SAP frontends.
See the documentation Installation of the SAP Frontend Software for PCs. This is included in
the installation package.
4. If required, you install a standalone gateway instance.

30 May 2000
SAP AG 3 The SAP System Installation

3.1 Preparing to Use INSTGUI

Use
You do this before starting the actual SAP System installation.

Prerequisites
Your PC is connected to the TCP/IP network.

Procedure
1. Insert the AS/400 Kernel CD into your PC CD-ROM drive.
2. Create an installation directory <INSTGUIDIR> on your PC. It should be possible for any
user to access this directory. To do so, enter:
MKDIR <INSTGUIDIR>
3. Change to directory <INSTGUIDIR>:
CD <INSTGUIDIR>
4. Copy the program INSTGUI.EXE from the AS/400 kernel CD to directory <INSTGUIDIR>.
(Make sure that you copy the correct INSTGUI for your hardware platform.):
copy <CD_drive>:\NT\<processor_type>\INSTGUI*.*
5. To unpack the R3SETUP online help on your PC (making sure that you use the CAR
appropriate for your hardware platform), enter:
<CD_drive>:\NT\<processor_type>\SAPCAR -xgvf <CD_drive>:\Docu\R3s_doc.scar

Result
The program INSTGUI.EXE is copied to your directory <INSTGUIDIR>.
A subdirectory doc is created on your PC. The R3SETUP online help files are copied into this
directory.

3.2 Starting INSTGUI

Use
You must start INSTGUI before starting R3SETUP. When R3SETUP is started, it attempts to
establish a connection to INSTGUI. For this to be possible, INSTGUI must already have been
started.

Procedure
1. Start your Windows NT 4.0 or Windows 95 Explorer.
2. Enter <INSTGUIDIR>\INSTGUI

May 2000 31
SAP AG

If you have stored the R3SETUP online help files in a directory other than
<instguidir>\doc, start INSTGUI with the option -docupath <path>.
To start INSTGUI if you have configured your AS/400 as an HTTP server (see Configuring
Your AS/400 as an HTTP Server), enter:
<INSTGUIDIR>\INSTGUI -docupath http://<your_AS400>/r3setup

Procedure if Communications Port 61312 is Occupied

If INSTGUI reports that the default communications port 61312 is already occupied:
1. Exit INSTGUI.
2. Start INSTGUI on the local computer with a different port:
<INSTGUIDIR>/INSTGUI -port <port>
3. Start R3SETUP on the AS/400 on which the SAP System is to be installed:
cd <instdir>
R3SETUP ‘-f <command file> -g <INSTGUI_hostname:port>’
Use the same port you used with INSTGUI.

Result
INSTGUI is started. You can now start R3SETUP.

3.3 Loading the Objects Required for Installation

Prerequisites
• You are signed on to your AS/400 machine as user QSECOFR .
• The SAP kernel CD is in the CD drive of your AS/400 machine.

Procedure
To load the objects required for installation and configuration from the CD:
1. Execute the LODRUN (Load and Run) command by entering:
LODRUN *OPT DIR(‘/OS400/AS400/INSTALL’) or LODRUN
<CD_device_description_name> DIR(‘/OS400/AS400/INSTALL’)
2. Enter /QOPT at the CD path prompt.

Result
The R3SETUP library is created on your AS/400. The R3SETUP main menu appears.

32 May 2000
SAP AG 3 The SAP System Installation

3.4 Copying the Command Files from CD

Use
A number of command files are required by R3SETUP for the installation. You copy these files
from CD as described here.

Prerequisites
The user profile for the user performing the installation has special authority *ALLOBJ and/or the
user class is *SECOFR.

Procedure
1. Add the R3SETUP library to your library list:
ADDLIBLE R3SETUP
2. Enter Go R3SETUP.
3. Select option 1 (Copy Installation Files from CD).
4. Enter the SAP system ID, for example “C11”.

The following combinations are not allowed as SAP system IDs:

SAP EPS COM ADD ALL AND ANY ASC FOR NOT UID SID KEY INT END
RAW ROW SET OFF MON SGA SHG VAR DBA GID LOG BIN B20 OMS BCO
B30 P30
5. Enter the CD mount point where the template files for R3SETUP reside (on the installation
kernel CD, for example):
/QOPT/<CD_label>/OS400/AS400

Result
The following template files are copied to the installation directory /tmp/<SID>:
CENTRDB.R3S
CENTRAL.R3S
DATABASE.R3S
DIALOG.R3S
GATEWAY.R3S
DBR3CP.R3S
DBEXPORT.R3S

May 2000 33
3 The SAP System Installation SAP AG

3.5 Starting R3SETUP

Prerequisites
Before you start R3SETUP, make sure you:
• Have started INSTGUI if you intend to use it.
• Are signed on as user QSECOFR.
• Are located in the installation directory.
If you are installing an SAP System on an AS/400 machine on which another SAP System is
running: The database monitor is switched off. To switch off the database monitor, enter:
ENDDBMON *ALL

Procedure
To start R3SETUP, enter the command:
CD <INSTDIR>
ADDLIBLE R3SETUP
R3SETUP ‘-f <command file>’
The name of the command file is <SERVICE>.R3S. For example, the name of the command file
for the installation of a central instance is CENTRAL.R3S.
When you call R3SETUP, you specify the service you wish to install. For example, to install a
dialog instance, you enter R3SETUP ‘-f dialog.r3s’.

Result
After it has been started, R3SETUP performs all installation steps that are defined in the
command file. It writes error messages, warnings and other information to the log file
<INSTDIR>/<SERVICE>.log. Important messages are also written to the console or INSTGUI.
When the last installation step is completed, R3SETUP sends the message “R3SETUP finished.”
If R3SETUP encounters a problem that it cannot handle, it stops with an error message.

3.6 Central or Standalone DB System Installation

Purpose
When a large SAP System with a heavy workload and many concurrent users is set up, the
central instance and database frequently need to be installed on two different hosts. This type of
configuration is referred to as a standalone database system. When a small to medium-sized
SAP System is set up, the central instance and database are generally installed on a single
machine. This type of configuration is referred to as a central system installation.

34 May 2000
SAP AG 3 The SAP System Installation

Which of these two approaches is best for your environment depends on various
factors such as the type of applications you intend to deploy, the size of the
anticipated workload, and the number of concurrent users expected. The most
commonly implemented configuration for an average-size system is a central
system. A standalone database system is usually implemented for larger systems
with a high throughput.
Prerequisites
In a sizing phase, well in advance of the actual installation procedure, you have to decide
whether a central system or standalone database system best meets your business
requirements. The SAP hardware partners provide support for this task. On the basis of
information about your present and future business requirements and with the help of the SAP
Quick Sizer tool, the partners can recommend a technical infrastructure that is suitable for your
workload. They assess the right combination of resources such as CPU, disk space, and memory
and propose an appropriate configuration.

Process Flow
1. Before creating your SAP System and instances, decide whether you want to change the
location of your /usr/sap/trans directory. If you decide to use the local directory, the
default entry for the directory is correct. However, you may choose to share the directory
across AS/400 systems, since using a shared /usr/sap/trans directory makes it easier to
maintain your SAP System and instance configuration data.
To change the location of the /usr/sap/trans directory:
a. Select option 4 (Change the location of the /usr/sap/trans directory) in the R3SETUP
main menu.
b. For New host system name, enter the name of the AS/400 system containing the
/sapmnt/trans directory you want to link to.
2. When installing a 3-tier system, that is a system where the central instance and database
instance are on different hosts, you must install the central instance before installing the
database instance.
a. Installing the Central Instance
You run R3SETUP on the central instance host using template CENTRAL.R3S. You must
take care to make the correct entries for the database instance host and central instance
host. You should use the same library name for the kernel on both the central instance
host and the database host.
Running the CENTRAL.R3S template is a prerequisite for completing the installation on
the database host. At this point, it is not possible to start the SAP System, as installation
is not yet complete. You start job QXDAEDRSQL on the central instance host as described
in Accessing a Remote Database [Page 55].
b. Installing the Database Instance
You run R3SETUP on the database host using template DATABASE.R3S. Once again,
you must take care to specify the central instance host name and database host name
correctly. You must specify the same instance number as you specified during the

May 2000 35
SAP AG

installation of the central instance. Take into account that during installation the library
name of the kernels on both instances must be the same.
When you run R3SETUP using the template DATABASE.R3S, the following happens:
After loading the database, the installation tries to create the central instance remotely by
running command CRTR3INST. This creates all the profiles and objects needed for the
central instance on the central instance host.
The SAP System is started and some database-specific installation steps are starting via
RFC by running program RADDBDIF. The first time a connection is made between the
database and central instance, this is done using TCP/IP. If you wish to activate
communications using Opticonnect, you will need to change the instance profile
accordingly.

Result
After you have completed the installation, you have to decide where your transport directory is to
reside. We recommend that you locate your transport directory on the database host, since you
can save it together with the database system using the SAVR3SYS command. To change the
location of your /usr/sap/trans directory, use command CHGR3SHLOC.
If you decide to share the /usr/sap/trans directory with the R/3 command CHGR3SHLOC,
make sure that the user profiles of <SID>OFR or QSECOFR who run this command also exist on
the specified host with the same passwords. This is a requirement of QfileSvr.400.

3.7 Installing a Central Instance with Database

Prerequisites
• You are signed on as user QSECOFR.
• You have loaded the objects required for installation.
• You have copied the command files from CD.
• Your current directory is the installation directory (for example, /TMP/<SID>).
• You have switched off the database monitor.
• INSTGUI has been started if you are using it.

Procedure
1. Start R3SETUP with the specify command file option, specifying the command file for
installing a dialog instance:
R3SETUP ‘-f centrdb.r3s’
2. Alternatively, if you started INSTGUI as described in Starting INSTGUI, enter:
R3SETUP ‘-f centrdb.r3s -g <instgui_hostname>:port’

36 May 2000
SAP AG 3 The SAP System Installation

The following combinations are not allowed as SAP system IDs:

SAP EPS COM ADD ALL AND ANY ASC FOR NOT UID SID KEY INT END
RAW ROW SET OFF MON SGA SHG VAR DBA GID LOG BIN B20 OMS BCO
B30 P30
3. In the Requesting installation details step (CENTRDBINSTANCE_IND_DB4), you are
prompted to enter/confirm:
− Your SAP system ID, for example C11.
− The instance number, for example 46.

Do not use instance numbers 98 and 99. These instance numbers are reserved
for internal purposes.
Make sure that you specify an instance number (SAPSYSNR) that does not
already exist on this host.
− The name of the central instance host, for example as0070.
− The name of the database server, for example as0070.
− The name of the SAP kernel library, for example R346BOPT.

R3SETUP does not currently support the use of an existing kernel. To apply an
existing kernel after installation, use the APYR3KRN command.
− The OS/400 release on which the kernel was compiled, for example V4R4.

This OS/400 release might not be the same as the OS/400 release of your
AS/400 system!
− The number of the ASP (auxiliary storage pool) for the database. The default value is 1.
− The number of the ASP for the journal receivers. The default value is the number of
ASPs on your AS/400.
4. Enter the directory path where the SAP kernel CD can be accessed.
Example: /QOPT/CD12345678
5. Enter the directory path where the database export CD 1 can be accessed.
Example: /QOPT/CD12345678
6. Enter the directory to which you want the contents of database export CD 1 to be copied.
Example: /tmp/C11/db1
7. Enter the directory path where the database export CD 2 can be accessed.
Example: /QOPT/CD12345678
8. Enter the directory to which you want the contents of database export CD 2 to be copied.

May 2000 37
3 The SAP System Installation SAP AG

Example: /tmp/C11/db2
9. Enter the directory path where the database export CD 3 can be accessed.
Example: /QOPT/CD12345678
10. Enter the number of parallel R3load processes you require.
Example: 15
11. Enter or confirm the platform for the loads to be imported. Accept the default value AS4.
R3SETUP prompts you to insert the installation CDs as required. At this time, the CDs must be
inserted. The CDs are required in the following order:
1. Database export CD 1
2. Database export CD 2
3. SAP kernel CD
4. Database export CD3
After the CDs have been inserted, R3SETUP stops at the step EXITMNLS_IND_IND and
prompts you to make code page-specific entries for your SAP System. Refer to Note 15023.
R3SETUP now runs through the following remaining installation steps without requiring further
user entries:

Remaining Installation Steps

Step Description Technical Name

Requesting installation details CENTRDBINSTANCE_IND_DB4
Checking the PTF level PTFCHK_IND_DB4
Checking the space available for the instance CENTRDBSPACECHECK_IND_DB4
Requesting information on CDs CDSERVER_IND_DB4
Loading the SAP SYSTEM kernel LODR3KRN_IND_DB4
Creating the SAP System objects CRTR3SYS_IND_DB4
Creating the instance objects CRTR3INST_IND_DB4
Copying the PTF Check File CPYPTFFILE_IND_DB4
Checking if the DB Export CD is available CHECKEXPORTCDINCDROM_IND_IND
Creating a link for R3load R3LOADLINK_IND_DB4
Creating the database library DBCREATEDB_IND_DB4
Creating the command files for the DB load DBR3LOADCMD_IND_IND
Preparing to load the ABAP Dictionary tables DBR3LOADDDICDUMMY_IND_DB4
Loading the ABAP Dictionary tables DBR3LOADDDIC_IND_DB4
Preparing to start R3load DBR3LOADEXECDUMMY_IND_IND

38 May 2000
SAP AG 3 The SAP System Installation

Loading the database DBR3LOADEXEC_IND_DB4

Preparing to load the database views DBR3LOADVIEWDUMMY_IND_IND
Loading the database views DBR3LOADVIEW_IND_DB4
Deleting ASCII loads DELETELOADS_IND_DB4
Creating the journal CREATEJOURNAL_IND_DB4
Starting journaling STARTJOURNAL_IND_DB4
Creating a temporary SAP license DBR3LICENSECREATE_IND_DB4
Ensuring ABAP Dictionary consistency DIPGNTAB_IND_DB4
Deleting the SQL packages DELETE_PACKAGE_IND_DB4
Updating MNLS tables EXITMNLS_IND_IND
Starting the SAP System DBR3START_IND_DB4
Initializing the Workbench Organizer via RFC RFCRSWBOINI_IND_IND
Creating database-specific objects via RFC RFCRADDBDIF_IND_DB4

Result
R3SETUP ends with the message R3SETUP finished. If problems occur, a dialog box appears
with the message Your system is not installed correctly.
The table below shows the runtime of the most important installation steps expressed as a
percentage of the runtime of all the installation steps.

The values given in the table do not correspond to the values displayed by
INSTGUI during the installation. (The INSTGUI values indicate the proportion of
installation steps processed and do not give any information about the proportion
of the total runtime completed.)

May 2000 39
SAP AG

Installation Step % of the

complete
runtime
LODR3KRN_IND_DB4 5
CDSERVER_IND_DB4 12
DBR3LOADDDIC_IND_DB4 4
DBR3LOADEXEC_IND_DB4 55
DBR3LOADVIEW_IND_DB4 6
STARTJOURNAL_IND_DB4 8
DIPGNTAB_IND_DB4 2
RFCRSWBOINI_IND_IND 0
RFCRADDBDIF_IND_DB4 6
Total 98

3.8 Installing a Database Instance

Use
If you are planning a standalone database system installation it is important to install the central
instance on the application server before you install the database on the database server. For
more information on how to install a standalone database system, see Central or Standalone DB
System Installation [Page 34].

Prerequisites
• You are signed on as user QSECOFR.
• You have loaded the objects required for installation.
• You have copied the command files from CD.
• Your current directory is the installation directory (for example, /TMP/<SID>).
• You have switched off the database monitor.
• INSTGUI has been started if you are using it.

Procedure
1. Start R3SETUP with the specify command file option, specifying the command file for
installing a dialog instance:
R3SETUP ‘-f database.r3s’

40 May 2000
SAP AG 3 The SAP System Installation

Alternatively, if you started INSTGUI as described in Starting INSTGUI, enter:

R3SETUP ‘-f database.r3s -g <instgui_hostname>:port’
2. In the Requesting installation details step (CENTRDBINSTANCE_IND_DB4), you are
prompted to enter/confirm:
− Your SAP system ID, for example C11.
− The SAP instance number, for example 46.

Do not use instance numbers 98 and 99. These instance numbers are reserved
for internal purposes.
Make sure that you specify an instance number (SAPSYSNR) that does not
already exist on this host.
− The name of the central instance host, for example as0070.
− The name of the database server, for example as0071.
− The name of the SAP kernel library, for example R346BOPT.

R3SETUP does not currently support use of an existing kernel. To apply an

existing kernel after installation, use the APYR3KRN command.
− The OS/400 release on which the kernel was compiled, for example V4R4.

This OS/400 release might not be the same as the OS/400 release of your
AS/400 system!
− The number of the ASP (auxiliary storage pool) for the database. The default value is 1.
− The number of the ASP for the journal receivers. The default value is 2.
3. Enter the directory path where the SAP kernel CD can be accessed.
Example: /QOPT/CD12345678
4. Enter the directory path where the database export CD 1 can be accessed.
Example: /QOPT/CD12345678
5. Enter the directory to which you want the contents of database export CD 1 to be copied.
Example: /tmp/C11/db1
6. Enter the directory path where the database export CD 2 can be accessed.
Example: /QOPT/CD12345678
7. Enter the directory to which you want the contents of database export CD 2 to be copied.
Example: /tmp/C11/db2
8. Enter the directory path where the database export CD 3 can be accessed.
Example: /QOPT/CD12345678

May 2000 41
3 The SAP System Installation SAP AG

9. Enter the number of parallel R3load processes you require.

Example: 15
10. Enter/confirm the platform for the loads to be imported. Accept the default value AS4.
R3SETUP prompts you to insert the installation CDs as required. At this time, the CDs must be
inserted. The CDs are required in the following order:
1. Database export CD 1
2. Database export CD 2
3. SAP kernel CD
4. Database export CD 3
After the CDs have been inserted, R3SETUP stops at the step EXITMNLS_IND_IND and
prompts you to make code page-specific entries for your SAP System. Refer to Note 15023.
R3SETUP now runs through the following remaining installation steps without requiring further
user entries:

Remaining Installation Steps

Step Description Technical Name

Requesting installation details DATABASEINSTANCE_IND_DB4
Checking the PTF level PTFCHK_IND_DB4
Checking the space available for the SAP DBSPACECHECK_IND_DB4
instance
Requesting information on CDs CDSERVER_IND_DB4
Loading the SAP kernel LODR3KRN_IND_DB4
Creating the SAP System objects CRTR3SYS_IND_DB4
Copying the PTF Check File CPYPTFFILE_IND_DB4
Checking if the DB Export CD is available CHECKEXPORTCDINCDROM_IND_IND
Creating a link for R3load R3LOADLINK_IND_DB4
Creating the database library DBCREATEDB_IND_DB4
Creating the command files for the DB load DBR3LOADCMD_IND_IND
Preparing to load the ABAP Dictionary tables DBR3LOADDDICDUMMY_IND_DB4
Loading the ABAP Dictionary tables DBR3LOADDDIC_IND_DB4
Preparing to start R3load DBR3LOADEXECDUMMY_IND_IND
Loading the database DBR3LOADEXEC_IND_DB4
Preparing to load the database views DBR3LOADVIEWDUMMY_IND_IND
Loading the database views DBR3LOADVIEW_IND_DB4
Deleting ASCII loads DELETELOADS_IND_DB4
Creating the journal CREATEJOURNAL_IND_DB4

42 May 2000
SAP AG 3 The SAP System Installation

Starting journaling STARTJOURNAL_IND_DB4

Creating a temporary SAP license DBR3LICENSECREATE_IND_DB4
Ensuring ABAP Dictionary consistency DIPGNTAB_IND_DB4
Deleting the SQL packages DELETE_PACKAGE_IND_DB4
Creating SAP Instance Objects Remotely RMTCRTR3INST_IND_DB4
Updating MNLS tables EXITMNLS_IND_IND
Starting the SAP System Remotely RMTDBR3START_IND_DB4
Initializing the Workbench Organizer via RFC RFCRSWBOINI_IND_IND
Creating database-specific objects via RFC RFCRADDBDIF_IND_DB4

Result
When the installation has finished, R3SETUP ends with the message R3SETUP finished. If
problems occur, a dialog box appears with the message Your system is not installed correctly.

May 2000 43
3 The SAP System Installation SAP AG

3.9 Installing a Central, Dialog, or Gateway

Instance
Use
You want to install a central, dialog, or gateway instance.

If you are planning to do a standalone database system installation, install the

central instance on the application server before you install the database on the
database server. For more information on how to install a standalone database
system, see Central or Standalone DB System Installation [Page 34].
Prerequisites
• You are signed on as user QSECOFR.
• You have loaded the objects required for installation.
• You have copied the command files from CD.
• Your current directory is the installation directory (for example, /TMP/<SID>).
• INSTGUI has been started if you are using it.

Procedure

If you want to install a remote dialog instance (a dialog instance running on an

AS/400 which is not the R/3 database). Create a user profile
SID><instance_number> for the dialog instance on the database host as follows:
1. Log on as QSECOFR on the database host.
Enter the command:
ADDLIBLE <kernel_library>
(where <kernel_library> is the name of your SAP System kernel library)
2. Enter the command:
CRTSAPUSR USER(*SIDINST) SID(<SID>) INSTANCE(<instance_number>)
(Where <SID> is your SAP System ID and <instance_number> is the number
of your dialog instance.)

1. Start R3SETUP with the desired command file option, specifying one of the command files
for installing a central, dialog, or gateway instance:
R3SETUP ‘-f central.r3s’
R3SETUP ‘-f dialog.r3s’
R3SETUP ‘-f gateway.r3s’
Alternatively, if you started INSTGUI as described in Starting INSTGUI, enter one of the
following:
R3SETUP ‘-f central.r3s -g <instgui_hostname>:port’
R3SETUP ‘-f dialog.r3s -g <instgui_hostname>:port’

44 May 2000
SAP AG 3 The SAP System Installation

R3SETUP ‘-f gateway.r3s -g <instgui_hostname>:port’

The following combinations are not allowed as SAP system IDs:

SAP EPS COM ADD ALL AND ANY ASC FOR NOT UID SID KEY INT END
RAW ROW SET OFF MON SGA SHG VAR DBA GID LOG BIN B20 OMS BCO
B30 P30
2. You are prompted to enter or confirm:
− Your SAP system ID, for example C11.
− The number of the central instance you are currently installing, for example 46.

Do not use instance numbers 98 and 99. These instance numbers are reserved
for internal purposes.
Make sure that you specify an instance number (SAPSYSNR) that does not
already exist on this host.
− The name of the central instance host, for example as0070.
− The name of the database host, for example as0071.
− The name of the SAP kernel library, for example R346BOPT.
− Your OS/400 release.
3. Insert the SAP kernel CD.
4. You are prompted to enter or confirm the path to the SAP kernel CD, for example
/QOPT/<CD_label_name> (You are asked to make this entry twice.)
R3SETUP now runs through the following remaining installation steps without requiring further
user entries:

Remaining Installation Steps

Step Description Technical Name

Requesting installation details CENTRALINSTANCE_IND_DB4 or
DIALOGINSTANCE_IND_DB4 or
GATEWAYINSTANCE_IND_DB4
Requesting information on CDs CDSERVERKERNEL_IND_DB4
Loading the SAP kernel LODR3KRN_IND_DB4
Creating the SAP System objects CRTR3SYS_IND_DB4
Creating the instance objects CRTR3INST_IND_DB4
Starting the SAP System R3START_DIALOG_IND_DB4 or
R3START_GATEWAY_IND_DB4

May 2000 45
SAP AG

The last two steps apply only to dialog and gateway instances.
Result
When the installation has finished, R3SETUP ends with the message R3SETUP finished. If
problems occur, a dialog box appears with the message Your system is not installed correctly.

3.10 Installing the SAP Frontend Software

Prerequisites
You have obtained the documentation listed below:
• SAP Supported Network Products
• Check list - Installation requirements: Frontends
The check list gives the minimum requirements for installing an SAP frontend.
• Installing SAP Frontend Software for PCs
This guide describes the procedure for installing the SAP frontend software.
• SAP R/3 Implementation on AS/400 (SG24-4672)
This IBM guide describes the procedure for installing the SAP frontend software on the IBM
Network Station.
• The current Note relevant for installing SAP frontend software for PCs. This Note contains
information that became available only after the installation guide was produced. The Note
number is quoted in the section “Requirements” in the documentation Installing SAP
Frontend Software for PCs. You can request this Note using the SAPNet – R/3 Frontend or, if
you do not have a SAPNet – R/3 Frontend link, using the fax request form provided in the
software package.

Procedure
To install the frontend software, follow the procedure described in Installing SAP Frontend
Software for PCs (or, in the case of the IBM Network Station) in SAP R/3 Implementation on
AS/400.

46 May 2000
SAP AG 4 Post-Installation Activities

4 Post-Installation Activities
Purpose
This section describes how you complete and check the installation of the SAP System.

Many of the steps in this process are documented in detail in the System
Administration Assistant. You can use this Assistant to execute the step and call
up the documentation.
Prerequisites
You have completed the SAP System installation on all the hosts of your SAP System, including
setting up at least one frontend (for example, on the central instance host).
You install the frontend software on at least one host machine in your system environment. To
simplify administration of your SAP System, we recommend that you do this on the central
instance host.
For more information on installing the frontend software, see the separate documentation:
• Installing SAP Frontend Software for PCs (English version)
• SAP-Frontend-Software für PCs installieren (German version)

Process Flow
1. If you have a preloaded SAP System, you perform any actions necessary for preloaded
systems [Page 48].
2. You update your code page-specific entries.
Proceed as described in Note 15023.
3. You grant authorizations for the operating system [Page 49].
4. You install the permanent SAP license key [Page 50].
5. You check that you can start and stop the SAP System [Page 51].
6. You check that you can log on to the SAP System [Page 52] with the SAP frontend.
7. You change the passwords for the user profiles [Page 53].
8. You delete the R3SETUP library and installation directory [Page 54].
9. You configure SAProuter and the SAPNet − R/3 Frontend [Page 56].
10. You import any additional languages your require. For instructions, refer to the separate
documentation SAP Language Transport. For information about how to import non-Latin-1
languages, see Note 99792 and Code Page Tables [Page 82].
11. If you are planning to use SAP Retail, see Note 138360.
12. You set up a printer. For instructions, see BC Printing Guide. To access this documentation,
choose Help → SAP Library → BC Basis Components → Computing Center Management
System (BC-CCM) → BC Printing Guide.
13. You perform a full backup [Page 59].

May 2000 47
4 Post-Installation Activities SAP AG

Result
You have completed and checked the SAP System installation.
You now need to prepare the SAP System for using business applications. This process includes
customizing the Basis System and the various business components. The procedure for
implementing the business processes and organizational structure of your SAP System is not
described in this documentation.

48 May 2000
SAP AG 4 Post-Installation Activities

4.1 Actions Necessary on Preloaded SAP

Systems
Purpose
IBM offers an SAP Preload option where the SAP software is preloaded onto a customer's
AS/400 before leaving manufacturing. When you receive a preloaded SAP System, you still have
to complete the steps listed below.

Prerequisites
You have a preloaded SAP System on your AS/400.

Process Flow
You have to perform the following actions:
• Install and test SAP GUI on your PCs.
• Set up and log on to the SAPNet – R/3 Frontend.
• Configure SAP users, printers, and the central system log.
• Make client copies (if required).
• Transport a further language (if required).
• Request programmer license keys (using the SAPNet – R/3 Frontend).

Result
Your preloaded SAP System is ready for use. If you have any questions related to the SAP
Preload, contact your SAP R/3 on AS/400 IBM Country Focal Point.

4.2 Granting Authorizations for Operating System

Collector Programs
Use
As of OS/400 Release V4R4, you have to run some commands before using the newly installed
SAP System to grant authorizations to some programs used by the operating system collector
(saposcol) to retrieve performance data from OS/400.

Procedure
Enter the commands:
GRTOBJAUT OBJ(QSYS/QPMLPFRD) OBJTYPE(*PGM) USER(<SID>OWNER) AUT(*USE)
GRTOBJAUT OBJ(QSYS/QPMWKCOL) OBJTYPE(*PGM) USER(<SID>OWNER) AUT(*USE)

You also have the option of granting authorization to USER(*PUBLIC).

May 2000 49
4 Post-Installation Activities SAP AG

4.3 Installing and Using the SAP License

Use
To work with the SAP System, you need an SAP license. After the installation of the central
instance, a temporary license is active for four weeks only. During this period, you must install a
permanent license.
You can install several licenses, one for each host running the message server. You must
perform this procedure on each host running the message server. The SAP System then
searches for the current license.

Prerequisites
You need to install a new permanent license if you are:
• Performing a new SAP System installation
• Renaming your SAP system ID (that is, <SID>)
• Changing the message server host (that is, the central instance)
• Changing an existing hardware configuration
To see online help for the license installation, enter the following command:
saplicense '-help'
For more information about the license, see the SAP online documentation (BC Basis → Kernel
Components → BC SAP License).

Procedure
1. To find the hardware key (that is, the customer key) needed for the license request, enter the
following command on the host where the message server is running:
saplicense '-get'
The system displays an 11-character hardware key, for example, D1903055560.
2. Using the fax form in the installation package, send a fax with the following information to
SAP:
− Hardware key from previous step
− Name of the installed R/3 System (that is, the value of <SID>)
− The date when you installed the database
3. After you have received your license key from SAP, install it as follows, making sure you
enter the license key exactly as shown in the SAP reply to your fax:
saplicense '-install'
− If the license installation is successful, you see the following message:
license successfully installed
You now have a permanent license for your SAP System
− If the license installation is not successful, you see the following message:
check failed, no license installed

50 May 2000
SAP AG

4. For more information, see SAP online documentation (BC Basis → Kernel Components →
BC SAP License).

4.4 Starting and Stopping the SAP System

Use
The procedures below explain how to start and stop the SAP System after the installation.

Prerequisites
• You have performed an IPL (initial program load) of your AS/400 system.
• You have checked that there are no active jobs for the instance that you have just installed.
To do so, enter:
WRKACTJOB SBS(R3_<instance_number>)
If a job is displayed, stop it with the command:
ENDSBS SBS(R3_<instance_number>)
Make sure that default option *IMMED is set.

Procedure
Starting the SAP System
1. Log on to your AS/400 system as <SID>OPR or <SID>OFR.
2. Enter STARTSAP and choose F4 to prompt for parameters.
3. Enter the SAP System ID (for example, “C11”) and instance number (for example “90”). We
recommend that you retain the default value *ENV for both SAP System ID and the instance
number. *ENV will be replaced by the correct value for the SAP system ID. In the case of the
instance number, the value *ENV represents the central instance number. A subsystem
R3_nn will be started (where “nn” is the instance number), along with all the associated SAP
services (such as dispatcher, work processes, spool). Specify WAIT(*YES) to make sure
that the system is up and running on termination of STARTSAP.
4. To check whether your SAP System started successfully, enter:
WRKACTJOB SBS(R3_nn)
5. On the next screen, check the entry in the first line of the Status column on the right of the
screen. If your SAP System started correctly, this field should contain the value RUN
(running), SELW (select wait) or DEQW (waiting for the completion of a dequeue operation). It
may take several minutes for the file system to reach this state.

Stopping the SAP System

1. Log on to the AS/400 system as <SID>OFR or <SID>OPR.
2. From the SAP Main Menu, choose option 1 General R/3 Tasks. The General R/3 Tasks
menu appears.

May 2000 51
SAP AG

3. Choose option 3 Stop R/3 System.

Alternatively, enter the AS/400 command STOPSAP and choose F4 to prompt for parameters.
4. For R/3 instance, enter the number of the instance to be stopped, for example 90.
5. To make sure that the system has been shut down on termination of STOPSAP, specify
WAIT(*YES).

4.5 Starting SAP Presentation

1. This step is required for users with OS/2 only:
Set parameter abap/no_sapgui_rfc = 1 in the instance profile and restart the SAP
System to activate the parameter.
(Remove this parameter after initial signon since it suppresses messages in the status line.)
2. Call the SAP Logon screen.
3. Choose New.
4. Enter a description for your application server, for example C11. This text will appear in the
SAP Logon screen.
5. Enter the host name of the application server, for example as0001.
6. Enter the system or instance number, for example 90.
7. When you have entered all this information, select OK. If the information is valid, a new entry
is added to the displayed list on the SAP Logon screen. If you have defined several systems,
they will be displayed in alphabetical order.

52 May 2000
SAP AG 4 Post-Installation Activities

4.6 Logging on to the SAP System

Use
Each SAP System contains the users SAP* and DDIC. They have the following initial passwords:
User Initial password
SAP* 06071992
DDIC 19920706

For security reasons you are strongly recommended to change these SAP
System passwords as soon as possible. See Changing the Initial Passwords.
Procedure
Log on as user SAP* (password: 06071992) and test the following:
1. Enter a new password and confirm it in the text boxes.
2. Call transaction SM50.
The services available for the instance should now be displayed, that is, dialog, update,
enqueue, background, and spool.
If the display is empty, check whether the message server is running using AS/400 command
WRKACTJOB (Work with Active Jobs). The process name is MSG_SERVER. If the process is
not running, /usr/sap/<SID>/DVEBMGS<no.>/work/dev_ms contains more information.
3. Check the system log using transaction SM21.

May 2000 53
4 Post-Installation Activities SAP AG

4.7 Changing Passwords for User Profiles

Use
For security reasons, you should change the passwords of the user profiles supplied with your
SAP System. The user profiles are as follows:
User Profile Initial Password
<SID>OFR SAPOFR
<SID>OPR SAPOPR
<SID><nn> SAPnnPWD ("nn" is the instance number.)

In 3-tier systems, these three users and the AS/400 superuser QSECOFR must
have the same password on all AS/400 systems.
Procedure
To change passwords at OS/400 level, use the command CHGPWD or CHGUSRPRF.

4.8 Deleting the R3SETUP Library and Installation

Directory
Use
• R3SETUP is a library created during installation. It contains all the objects required for
installation. R3SETUP is included in the library list.
• The contents of the installation CDs are copied to directory /tmp/<SID>. You can gain disk
space if you delete the directory and its subdirectories after installation.

Prerequisites
• You have completed SAP System installation.
• The SAP System is up and running.

Procedure

Do not delete the log files unless you are sure that you will not need them again.
Do not delete log files other than those in the paths given here.
1. Delete library R3SETUP.
2. Delete directory /tmp/<SID> recursively with the command:
rrm '/tmp/<SID>'

54 May 2000
SAP AG 4 Post-Installation Activities

4.9 Accessing a Remote Database

Use
We recommend the use of TCP/IP connections to a remote database only for small test
environments or in certain special circumstances. For production environments, we strongly
recommend that you use OptiConnect for OS/400.

Procedure
Configuring the AS/400 System for OptiConnect
By default, the SAP System installation will use OptiConnect to access a remote database. To
use TCP/IP instead, you have to change the instance profile of each SAP instance and the
TPPARAM file as follows:
1. To edit the instance profile, enter the command:
EDTF ‘/usr/sap/<SID>/SYS/profile/<SID>_<ROLE>nn’
and insert the line:
dbs/db4/opticonnect = 0
2. To edit the TPPARAM file, enter the command:
EDTF ‘/usr/sap/trans/bin/TPPARAM’
and insert the line:
<SID>/opticonnect = 0
To switch back to OptiConnect, remove these lines.
For information about how to set up and start OptiConnect, refer to the IBM manual OptiConnect
for OS/400.

Accessing a Remote Database via TCP/IP Sockets

If you have both an SAP System with Release 4.6C and SAP Systems with lower
releases than 4.6A running on a single AS/400 system, you should note the
following:
In R/3 Release 4.6C the command STARTSAP *DB does not start the database
server job R3RMTDB, which is required for releases prior to 4.6A. To start these
SAP Systems, you should continue to use the command STARTSAP *DB from
the older R/3 release.
QXDAEDRSQL, the job necessary for accessing a remote database, is normally started
automatically. It runs in subsystem QSYSWRK. If it is not running, you can start it with the AS/400
command STARTSAP *DB.
When a work process connects to the QXDAEDRSQL job, the job spawns a second “shadow” job.
This shadow job is switched to run under the user profile running on the local system.

May 2000 55
SAP AG

If <SID>00 connects to the QXDAEDRSQL job, the job will spawn another job
under user profile QUSER. This new job is switched immediately to run under user
profile <SID>00.

4.10 Configuring SAProuter and SAPNet - R/3

Frontend
Use
SAProuter increases network security and simplifies network configuration. SAProuter allows you
to make indirect network connections. The SAProuter software is included in the standard SAP
System. No additional installation is required. The network administrator normally configures
SAProuter.
If you are using any of the following, you require SAProuter:
• SAPNet – R/3 Frontend
SAPNet – R/3 Frontend is the SAP-based service system and provides the technical link
between SAP customers and SAP. SAPNet – R/3 Frontend was formerly known as the
Online Service System (OSS).
For more information on setting up and using SAPNet – R/3 Frontend, see the alias sapnet-
guide in SAPNet – Web Frontend, and the SAP online documentation.
• EarlyWatch
For more information, use the alias earlywatch in SAPNet – Web Frontend.
• Remote Consulting
For more information, use the alias remoteconsulting in SAPNet – Web Frontend.

Procedure
To get a complete list of SAProuter parameters, enter the following at the command line prompt:
saprouter
For more information see the SAP online documentation. For information on installing SAProuter
as a Windows NT service, see SAP Note 41054.

56 May 2000
SAP AG 4 Post-Installation Activities

4.10.1 Example of How to Configure a TCP/IP

Connection
This example shows how the configuration of the TCP/IP connection between the customer
SAProuter and the SAP Support Server might look for an X.25 connection. In the example we
assume you are trying to connect to the SAP Support Server for Europe (sapserv3).
In the example, SAProuter is running on the AS/400 on which your SAP System is also running.
You require a communications adapter on your AS/400 machine.
Before starting, you need to know two Internet addresses:
• The address of SAP Support Server sapserv3
• The address of the X.25 Server in Walldorf
1. Enter the Internet address for the SAP Support Server (in this case sapserv3).
a. Call the TCP/IP configuration menu with CFGTCP.
b. Choose option 10 Work with TCP/IP host table entries.
c. Choose option 1 = Add.
You can now add the Internet address.

2. Enter the Internet address for the X.25 server in Walldorf.

a. Choose option 1 = Add again in the Work with TCP/IP host table entries.
b. Add the address of the X.25 server.

3. Define the route your system is to take to connect to the relevant SAP Support Server.
a. In the TCP/IP Configuration Menu take option 2 Work with TCP/IP routes.
b. Choose option 1 = Add.

May 2000 57
4 Post-Installation Activities SAP AG

c. Enter the Route destination (that is, the Internet address of the SAP Support Server) and
the Next hop (the router via which your system reaches its destination).
In this example, this is an X.25 server in Walldorf (for Foster City (sapserv4) the address
would be 204.79.199.2, for Sydney (sapserv6) 147.204.96.8).

4. Enter TCP/IP interface information.

a. In the TCP/IP Configuration Menu, choose option 1 Work with TCP/IP interfaces
b. Choose option 1 = Add.
c. For Internet address enter the SAPNet – R/3 Frontend TCP/IP address supplied to you
by SAP.

5. Enter the remote system information.

a. Choose option 5 Work with TCP/IP Remote System Information.
b. Choose option 1 = Add.
c. For Internet address, enter the Internet address you entered under Next hop in the Add
TCP/IP Route screen. That is, you need to enter the Internet address of the X.25 server
in Walldorf, not of the sapserv3 Support Server.
d. For Network address, enter the X.25 address associated with the Internet address.

58 May 2000
SAP AG 4 Post-Installation Activities

4.11 Performing a Full Backup

Use
You can use this procedure to make a full backup of your SAP System.

During the backup, your SAP System is unavailable to other users.

Prerequisites
You have finished installing your SAP System.

Procedure
1. Log on to the AS/400 system from the console as user QSECOFR or as a user with *SAVSYS
rights and authorization to start and end subsystems.
To find the name of the console, look at system value QCONSOLE. To display this system
value, enter DSPSYSVAL QCONSOLE.
2. To shut down the AS/400 system, enter:
ENDSBS SBS(*ALL) OPTION(*IMMED) or ENDSYS.
3. Wait for the AS/400 system to go into restricted state. This could take a few minutes. To find
out whether the system has entered this state, enter:
DSPMSG QSYSOPR
4. Execute the SAVSYS (Save System) command. This command saves a copy of the Licensed
Internal Code and the QSYS library.
5. Enter the SAVLIB (Save Library) command specifying parameter *NONSYS. This command
saves all user-created libraries, the QPGL and QUSRSYS libraries, and IBM libraries.
6. Enter the SAVDLO (Save Document Library Object) command.
7. Using SAV commands, save the remaining objects. For an overview of the SAP directories
relevant for backups, see “R/3 Directories Relevant for Saving” in the documentation BC -
R/3 Database Guide: DB2/400.
Enter:
Name ‘/’
Include or omit *INCLUDE
Directory subtree *ALL
For detailed information, see the IBM backup and recovery documentation.
8. To start the controlling subsystem, enter the command STRSBS (Start Subsystem). To find
the name of the controlling subsystem, check system value QCTLSBSD. You can do this with
command DSPSYSVAL QCTLSBSD.

May 2000 59
4 Post-Installation Activities SAP AG

How to Back Up Your System

Parts of the System Command

Model- or Feature-Unique
Licensed Internal Code
Licensed Internal Code
SAVSYS
OS/400 Objects in QSYS

User Profiles
SAVSECDTA
Private Authorities

Configuration Objects SAVCFG

OS/400 Optional Libraries

SAVLIB SAVLIB
(*IBM)
Licensed Program Libraries

SAVLIB
IBM Libraries With User Data
(*ALLUSR)
SAVOBJ
User Libraries
SAVCHGOBJ

Filed Documents and Folders

SAVDLO
Distribution Objects

Objects in Directories SAV

Result
See also: Restoring a Backup [Page 86]

60 May 2000
SAP AG 5 The R3SETUP Tool

5 The R3SETUP Tool

Use
R3SETUP is the SAP tool to automate installation of the SAP System. It installs the different
components of an SAP System.

Integration
You can use INSTGUI, the graphical user interface for R3SETUP, to monitor the progress of the
installation.

Prerequisites
R3SETUP does not support the following steps, which you must do before installation:
• UNIX
− Setup of file systems and raw devices
− Configuration of UNIX kernel parameters and swap space
• NT
− Installation of the Microsoft Management Console (MMC)
− Adjustment of virtual memory and file cache
• AS/400
− Configuration of AS/400 system values
− Addition of user auxiliary storage pools (ASPs)
− Configuration of TCP/IP
− Checking and adjusting memory pools
• OS/390
− Configuration of OS/390 UNIX System Services
− Setup of file systems
− Creation of OS/390 groups and users

Features
The R3SETUP tool supports the installation of:
• The central instance
• The database
• A dialog instance
• The SAP software development kits (UNIX)
• A standalone gateway
R3SETUP does this by:
• Creating operating system users and groups (UNIX and NT)

May 2000 61
5 The R3SETUP Tool SAP AG

• Creating user profiles (AS/400)

• Defining services at operating system level
• Creating and modifying files and directories
• Unpacking (restoring) and copying software
• Creating the database and loading it with data
• Configuring essential database and operating system objects for the SAP System

Create a new installation directory every time you start R3SETUP with another
service (that is, with another command file identified by the ending .R3S).
Otherwise, old log and command files are overwritten.
When you start R3SETUP, the following options are available:
Option Meaning
-f <command file> Specify the service you want to install
(required)
-l <log file> Specify log file, default: <service>.log
-t trace Include detailed trace messages in log file
-g <gui_host>:<gui_port> Specify host and port for INSTGUI
-m Create file with messages for INSTGUI
-h List R3SETUP options
After it is started, R3SETUP shows the following properties:
• It performs all installation steps that are defined in the command file
• It writes error messages, warnings and other information to the log file
• Important messages are also written to the console.
• When the last installation step is completed, R3SETUP finishes with the message R3SETUP
finished.
• If R3SETUP encounters a problem that it cannot handle, it stops with an error message.

Activities
You can:
• Run R3SETUP unattended
You determine how R3SETUP performs the installation by making entries in a command file
during the input phase. This allows you to provide all the necessary information before the
actual installation starts. R3SETUP then goes into the processing phase to automatically
perform the installation in unattended mode, without prompting you for any further
information.
If necessary you can re-use the command file to perform another identical installation or to
restart the installation in the event of failure.

62 May 2000
SAP AG 5 The R3SETUP Tool

• Restart R3SETUP
The installation consists of a number of independent installation steps. If a step fails,
R3SETUP stops. When the problem has been solved, you can restart R3SETUP. Since
R3SETUP records the installation progress in the command file, it can continue the
installation from the failed step, without repeating previous steps.

May 2000 63
5 The R3SETUP Tool SAP AG

5.1 INSTGUI
Use
You use INSTGUI, the graphical user interface (GUI) for R3SETUP, during the:
• Input phase to enter information for later use by R3SETUP
• Processing phase to:
− Monitor progress of the installation steps
− View log messages
You can also use INSTGUI to get online help on R3SETUP.

Integration
Depending on your operating system platform, you start INSTGUI:
• Independently of R3SETUP as a separate process, on non-Windows platforms
• Simultaneously with R3SETUP, on Windows platforms
For a remote installation on Windows platforms, you also have to start INSTGUI as a separate
process on the host from which you supervise the installation.
If you use INSTGUI, it is closely integrated with R3SETUP to exchange information about the
progress of the installation.

Prerequisites
INSTGUI is available for X Windows (on UNIX operating systems) and for Windows NT 4.0 and
Windows 95 or 98.

Features
You can start INSTGUI with these options:
Options Meaning
-port <number> Port for communication with R3SETUP,
default: 59595
-docupath <path> Path to the R3SETUP online help files,
default: ./doc
-fontsize <size> Font size for INSTGUI (8 to 14), default: 8
-help List INSTGUI options

Activities
When using INSTGUI, you can switch between the following views:
• Step View
When you start R3SETUP, it goes into step view. You can:
− See which installation step is currently being performed and what it does

64 May 2000
SAP AG

− Get online help on the installation step that is currently being performed
− Switch to the log view
• Log View
This shows all R3SETUP messages as they are recorded in the log file. You can:
− Display the next or previous information, warning, or error message
− Get online help on the installation step that created a message
− Switch back to the step view

5.2 R3SETUP Command Files

Definition
The R3SETUP command files determine how R3SETUP performs the installation of the SAP.
The main command files are listed below:
Command File Installs
CENTRAL.R3S The central instance
DATABASE.R3S The database
CENTRDB.R3S The central instance with database
DIALOG.R3S A dialog instance
CDINST.R3S (UNIX and NT The R3SETUP tool from CD-ROM
only)

Use
During the input phase of the installation, you enter information into the R3SETUP command file,
which is then used by the R3SETUP program during the unattended processing phase of the
installation.
An installation step can run in one of two different modes, SKIP or DO. The default mode before
the installation is DO. After the step has run successfully, the default mode is SKIP. This means
the step is skipped if you restart R3SETUP.
You can force a step to run even if installation results already exist by adding the key
ACTION=FORCEDDO to the step's section in the command file. If you want to skip a step although
it has not yet run, add the key ACTION=SKIP.

If you modify the command file, you must save your changes before you start
R3SETUP. Otherwise, your changes have no effect.

May 2000 65
SAP AG

Structure
The command file consists of several sections. The beginning of a section is always indicated by
the section name in brackets. Each section contains a set of keys and their values. There are the
following types of section:
• The [EXE] section
This is the installation roadmap. Steps are listed in numerical order of execution, as shown in
the following example:

[EXE]
10=GATEWAYINSTANCE_IND_IND
20=R3GATEWAYPORT_IND_IND
30=R3GATEWAYSECURITYPORT_IND_IND
40=OSGROUPSAPLOCAL_NT_IND
50=OSUSERSIDADM_NT_ORA
60=R3DIRECTORIES_NT_IND
• Step sections
These describe in detail a step named in the [EXE] section. After execution, step sections
are updated with the status OK or ERROR.
• List section
These contain additional information for the installation, such as a list of directories to be
created. The names of list sections start with[Z…].
Keys enclosed in @ characters, for example @SAPSYSNR@, are variables that are replaced by
suitable values during the installation.

5.3 R3SETUP Messages

Definition
R3SETUP records all information about the installation process in the relevant log file:
• AS/400: <INSTDIR>/<COMMAND_FILE_NAME>.log (or
<COMMAND_FILE_NAME>.log<NR> if R3SETUP was started several times)

Use
Since the log file can contain up to several hundred messages, we recommend you use the
R3SETUP frontend to navigate through the messages. See Using R3SETUP Online Help [Page
67].

66 May 2000
SAP AG

Structure
Every message in the log file contains:
• Message type (INFO, WARNING, or ERROR)
• Date and time
• Installation step (that is, the name of the section in the command file)
• Message and text

INFO 1997-12-09 13:52:20 R3LINKS_IND_IND ColdKeyCheck:0

Phase successful

5.4 Using R3SETUP Online Help

Use
You can display R3SETUP online help for information on the R3SETUP installation steps.

Prerequisites
You need an HTML browser to view the online help for the R3SETUP installation steps:
• UNIX
Netscape Navigator 3.0 or higher
The HTML help files are stored in a SAR archive on the SAP Kernel CD. They are
unpacked and stored in the directory <INSTDIR>/doc by the shell script when INSTGUI is
copied from the CD to the hard disk.
• Windows
Windows NT 4.0 and Windows 95
Netscape Navigator 3.0 or higher (32-bit version), and Microsoft Internet Explorer 3.0 or
higher (32-bit version). Internet Explorer is shipped with the SAP System on the Online
Documentation CD. See the README.TXT file on this CD.
The HTML help files are stored in a SAR archive on the SAP Kernel CD. They are
unpacked and stored in the directory <instguidir>/doc on your PC.
• AS/400
Netscape Navigator 3.0 or higher (32-bit version), and Microsoft Internet Explorer 3.0 or
higher (32-bit version). Internet Explorer is shipped with the SAP System on the Online
Documentation CD. See the README.TXT file on this CD.
The HTML help files are stored in a SAR archive on the SAP Kernel CD. You can do one of
the following:

May 2000 67
5 The R3SETUP Tool SAP AG

− Unpack the HTML files and store them in the directory <instguidir>/doc on your PC.
− Configure your AS/400 as an HTTP server and unpack and store the HTML files on your
AS/400.

Procedure
You can access the R3SETUP online help in the following ways:
• You can display context-sensitive help on installation steps and log messages by choosing
Help in INSTGUI.
• You can browse the help by opening the file <INSTDIR>/doc/_START.HTM (AS/400:
<instguidir>/doc/START.HTM) on your PC with your web browser.
• AS/400: If you configured your AS/400 as an HTTP server, you can also start INSTGUI with
the option instgui -docupath http://<your_AS400>/r3setup/

5.4.1 Configuring Your AS/400 as an HTTP Server

Use
You can optionally configure your AS/400 machine as an HTTP server. Using the command
CPYR3S, you can unpack the HTML help files in the installation directory on your AS/400. The
files are unpacked into the subdirectory doc.

Procedure
For information about how to proceed, see the IBM documentation HTTP Server for AS/400
Webmaster's Guide (available on the IBM Softcopy Library CD) (document number GC41-5434-
03)
1. Install the product:
5769DG1 IBM HTTP Server for AS/400
2. To start the Administration Server instance, enter:
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
3. Direct a Web browser to the following location:
http://<your.server.name>:2001/
(where <your.server.name> is the name of your AS/400 system)
4. Choose Configuration and Administration → Global server parameters.
5. Set AUTOSTART to *YES.
6. Choose Configuration and Administration → Configurations → Request processing →
Request routing.
7. Select Insert after.
8. For Action, choose Pass.

68 May 2000
SAP AG 5 The R3SETUP Tool

9. For URL template, enter /r3setup/*

10. For Replacement file path, enter:
/tmp/<inst_dir_on_AS400>/doc/*
Example for Making an Entry for Action Pass

11. To save your entries, choose Apply. Your entry now appears in the table as shown below.
Example of a Pass Entry

12. To restart the HTTP server, enter:

STRTCPSVR SERVER(*HTTP) RESTART(*HTTP)

Result
Your AS/400 is now configured as an HTTP server. To start INSTGUI, use the following option:
instgui -docupath http://<your.server.name>/r3setup

May 2000 69
5 The R3SETUP Tool SAP AG

5.5 Continuing an Interrupted Installation

Use
You can continue an installation that has failed from the point of failure, without repeating steps
that have already successfully completed.

Prerequisites
If an installation step fails, R3SETUP stops with an error message.

Procedure
1. Look at the log file [Page 72] to find out exactly what happened.
2. If necessary, see the R3SETUP online help [Page 67].
3. When you have solved the problem, restart R3SETUP.
Since R3SETUP records installation progress in the command file, it can continue the installation
from the point of failure.

70 May 2000
SAP AG 6 Error Handling

6 Error Handling
Errors can occur in a number of different situations. You can check the following:
• To find out which phase failed and which function could not be performed, look at the log file
<service>.log [Page 71] in the installation directory on your AS/400.
• To find out if an AS/400 escape message was sent by the operating system, look at the job
log of the job that was running R3SETUP. Enter:
DSPJOBLOG
• If an error occurs during the database load, refer to Handling Problems During the Database
Load. [Page 72]
• If an error occurs during an RFC step, refer to Correcting Errors in RFC Steps [Page 74].
• To check that the correct user profile is being used, examine the job that is running
R3SETUP. To do so:
a. Enter DSPJOB.
b. Choose option 1 Display job status attributes.
c. Make sure that the user profile entered for Current user profile is the one that started
R3SETUP.
This problem can occur if the user switch from <SID>OFR to QSECOFR or the reverse
could not be performed.
d. If your current user profile is <SID>OFR, log off from your AS/400 session and log on
again as QSECOFR. Then restart R3SETUP.

Displaying Import Jobs

During installation several jobs are started on the AS/400 to import the database in parallel.
• To display these jobs, enter the command:
WRKUSRJOB <QSECOFR_user> *ACTIVE
where <QSECOFR_user> is the user who started the R3SETUP job.
• To see the jobs that have already finished, enter:
DSPMSG <SID>OFR
Since the user switches from QSECOFR to <SID>OFR during some steps of the installation, the
message queue of <SID>OFR is used during the database load.

May 2000 71
6 Error Handling SAP AG

6.1 Log File <service>.log

Definition
The log file <service>.log in the installation directory contains information about the progress
of an installation. It contains more detailed information than is provided by INSTGUI.

Use
To display the log file, enter:
DSPSTMF '/tmp/<SID>/<SERVICE>.log

To display the log for the installation service Central Instance with Database
Installation, enter:
DSPSTMF '/tmp/C11/CENTRDB.log'

Example
The following is an example of the file <service>.log. In this example, the SAP System being
installed is called C11.
...
INFO 1998-10-20 13:20:37 CDSERVER_IND_DB4 CheckCopyDirectoryForCD:0
The directory to which you want to copy the contents of the CD is
not empty. You cannot copy to a directory that is not empty. If the
directory already contains the CD, this is not an error.
WARNING 1998-10-20 13:20:37 CDSERVER_IND_DB4 CheckCopyDirectoryForCD:0
The CD EXPORT2 has already been copied to /tmp/C11/db2. It cannot
be copied again. Check directory /tmp/C11/db2.
...
The step CDSERVER_IND_DB4 performs the function CheckCopyDirectoryForCD.
This function issues a warning because the directory /tmp/C11/db2 already exists. This
warning can be ignored because the directory had already been created and does not need to be
created again.

72 May 2000
SAP AG 6 Error Handling

6.2 Handling Problems During the Database Load

Use
The database load is divided into several sections, which are performed in parallel. Each section
writes a log file to your installation directory. The names of these files are listed in the following
table:
Log Files Log Files
SAPSDIC.log SAPSDOCU.log
SAPSSDEF.log SAPSLDEF.log
SAPAPPL2.log SAPSLOAD.log
SAPAPPL0.log SAPSPROT.log
SAPSLEXC.log SAPSSEXC.log
EX000.log SAPSSRC.log
SAPAPPL1.log SAPVIEW.log
SAPCLUST.log EXAS4000.log
SAPPOOL.log

Procedure
1. If a section fails, look at the log file for the section in question. To do so, enter:
DSPSTMF ‘/tmp/<SID>/<log_file>.log’

DSPSTMF ‘/tmp/C11/SAPSDIC.log’
The log file contains additional information about the status of the job and the corresponding
AS/400 job.
2. Scroll to the bottom of this file and check the error message.
The start of each import attempt is logged to this file and looks like this:
#START OF LOG: 19981019164134
# R3load version @(#)R3load.c 20.78.17.1 SAP 98/10/08
# Jobno/Jobuser/Jobname: "102345/QSECOFR/SAPSDIC"
# R3C1145A/R3LOADDB4 -i SAPSDIC.cmd -p SAPSDIC.log -o J -C
...
3. Using this information, you can check the AS/400 job by issuing:
WRKJOB <job_no.>/<job_user>/<job_name>

For the example given above, you enter:

WRKJOB 102345/QSECOFR/SAPSDIC

May 2000 73
SAP AG

4. To check the spool file of this job, choose option 4 (Work with spooled files).
5. Examine the spool files to find out if any escape messages were sent during the database
operations.

No Journaling During the Database Load

Bear in mind that the new tables are not journaled during the database load. Therefore, you
receive the following message:
SQL7905 Information 20 10/21/98 17:18:38 QSQCRTT QSYS 1013 QSQCRTT
Message . . . . : Table <table_name> in R3<SID>DATA created but
could not be journaled.

You can ignore this message. Journaling is switched on in step STARTJOURNAL_IND_DB4. This
step is executed when all sections of the load have been imported successfully into the
database.

6.3 Correcting Errors in RFC Steps

Use

RFC steps have step names starting with "RFC", for example,
RFCADDBDIF_IND_DB4.
RFC steps can fail for several reasons:
• The SAP System has not been started up correctly.
• The DDIC user has the wrong password.
• The jobs started by user DDIC cannot be executed.
• The SAP job cannot be started or executed in the SAP System.

Procedure
Errors in RFC Steps and Required User Actions

Cause of the Error User Actions

The SAP System has not To check if the SAP work processes are running, enter:
been started up correctly
WRKACTJOB SBS(R3_<nn>)
(This is indicated by error
messages in the files
dev_w* and dev_disp.
These files are located in the
work directory.)

74 May 2000
SAP AG

The DDIC user has the Check whether you can log on to the SAP System as user
wrong password DDIC.
Check whether the password for DDIC is the default password
(19920706).
The jobs started by user To monitor the jobs started by user DDIC (paying particular
DDIC cannot be executed attention to the job RADDBDIF), use transaction SM37.
To look at the system log for detailed information, use
transaction SM21.
The SAP job cannot be Check whether user <SID><nn> has write permissions for
started or executed in the directories /usr/sap/trans and /usr/sap/trans/tmp.
SAP System.
If directory /usr/sap/trans is located on another AS/400 and
is shared via QFileSvr.400, make sure that users <SID><nn>
and <SID>OFR exist on the remote system and have the same
passwords on both systems.

Step RFCRADDBDIF_IND_DB4 also writes log file

/usr/sap/trans/tmp/RADDBDIF.<SID>, which contains additional
information about the status of the executed reports.

6.4 Fax Form for Reporting Installation Problems

Use
To help us to assist you in completing your installation, migration or database copy as quickly as
possible, we have created a fax template. You can use it as the basis for your SAP message or
photocopy it and send it to us by fax. The fax number in Germany is:
(+49) 180/534 34 30

If you encounter a problem during installation, migration, or database copy, it is

not sufficient just to send a fax. You must also create an SAP message.

May 2000 75
6 Error Handling SAP AG

Fax Form
Type of installation (check relevant box)
Installation Type
New installation of a central instance from SAP CD
New installation of a dialog instance from SAP CD
New installation of SAP GUI from SAP CD
New installation of IDES
Database copy, homogeneous migration
Heterogeneous migration

Details of newly installed system or target system (database copy or

migration only)
OS/400 version: _________________ (for example, “V4.R1.M0”)
AS/400 model: _________ (for example, “530”)
Other SAP Systems, database or application instances on the host:
_____________________________________________________

Source system (database copy or migration only)

Operating system: ______ Version: ______ Database: ______ Version: ______

SAP System configuration

Development system: Test system: Production system:
________________ ________________ ________________

Programs used for installation:

Did you use the official SAP installation tool (R3SETUP) ? (yes/no)

Programs used for migration:

__ R3SETUP __ R3SZCHK __ R3INST __ DIINST __ R3CHOP __ R3COPY __ KINST __
R3load __ R3ldctl
__ sapdba

System copy method

__ R3load method __DB2/400-specific method

CD information
________________________________________
Enter here the line of information given in the file LABEL.EBC in directory /qopt/<volid>. The line
has the format: “SAP:<rel>:<CD_type>(1/2):<text>:<volid>”.
“<rel>” stands for the R/3 Release, “CD type” for “EXPORT” or “KERNEL”.

76 May 2000
SAP AG 6 Error Handling

Documentation
Which documentation are you using ?
Title: _________________________________________ R/3 Release: ____

SAP Notes
___ We do not have the current installation Notes.
___ The current installation Notes do not help me to solve my problem.
___ This installation Note contains information about the problem: __________

Problem Analysis
During which installation step/procedure did the problem arise?: __________________
List the error messages given in the log files/job log:
_______________________________________________________________________
Have you tried to solve the problem? List any steps you have taken:
_______________________________________________________________________
_______________________________________________________________________
What is the current status of the installation ?
______________________________________________________________________
For problem analysis we also require the installation log files located in these paths:
/usr/sap/kernel/<REL>/<SID>/log/kernel.log
/usr/sap/xload/<REL>/<SID>/log
/usr/sap/trans/log/<SID>

If the logs are very long, you can send us an excerpt. This should include all the error messages,
a few lines before and after each error message, and the last 10 to 30 lines.

May 2000 77
7 Additional Information SAP AG

7 Additional Information
This section contains general information on R/3 on IBM AS/400.
• AS/400 Library Structure [Page 78]
• OS/400 Integrated File System [Page 79]
• Code Page Tables [Page 81]
• Restoring a Backup [Page 86]
• Editing Stream Files [Page 87]

78 May 2000
SAP AG 7 Additional Information

7.1 AS/400 Library Structure

Definition
Libraries form the primary native organizational structure on the AS/400. A library is an object
that groups together related objects.
There are three different types of library:
• System libraries, for example, library QSYS for objects supplied as part of the operating
system
• User libraries, for example, the various SAP libraries:
Library Description
R3<REL>OPT Library for optimized executables
R3<SID>DATA Database library
R3<SID>JRN Journal receiver library
R3<SID>400 Library for work management objects
R3<REL>RFC Library for RFC SDK
R3<REL>CPIC Library for CPI-C SDK
R3WRKnn Internal SAP library
R3* Reserved for the SAP System
Q* System libraries

<SID> is the SAP system ID (for example “C11”); <REL> is the R/3 Release (for
example, “4.6B”), “nn” is the instance number.
• Product libraries, for example, library QPDA which contains objects associated with the
AS/400 Programming Development Manager (PDM).

Some of the SAP library names may vary if you assign your own library names.
However, we do not recommend that you change the default library names
without good reason.
Types of objects stored in libraries include, for example, files and programs.
Files do not contain the actual data. The data is stored in members within each file. In SQL
systems, such as SAP, each file contains exactly one member.

May 2000 79
7 Additional Information SAP AG

7.2 OS/400 Integrated File System

Definition
The AS/400 also provides a UNIX-style and PC-style integrated file system that provides
enhanced capabilities for managing new types of information processing, including client/server,
open systems, and multimedia.

Use
The integrated file system supports the use of stream files for storing and operating on data.
Stream files are files containing a continuous stream of data. This data might take the form of text
files or images, for example. Stream files are system objects with object type *STMF.
For information about displaying or editing stream files, see Editing Stream Files.

Structure
The OS/400 integrated file system has a hierarchy comparable to that used by UNIX. The
integrated file system treats the different types of support for accessing the various object types
as separate file systems. These file systems are:
• “/”: This file system corresponds to the UNIX “root” directory. This PC-style file system is not
case-sensitive.
• QOpenSys: The open systems file system. This UNIX-style file system is case-sensitive.
• QSYS.LIB: The library file system allowing the user to access objects residing in native
AS/400 libraries using IFS commands.
• QDLS: The document library services file system (not used by the SAP System)
• QLANSrv: The LAN Server/400 file system (not used by the SAP System)
• QOPT: The optical file system; this file system is mainly used during installation
• QFileSvr.400: This file system provides access to other file systems on remote AS/400
systems. It is used by several SAP functions, for example correction and transport, to access
remote stream files.

Take care with upper- and lowercase notation. The “/” file system is not case-
sensitive, but QOpenSys and the contents of SAP profiles are.
Integration
The integrated file system distinguishes between two different types of link: hard links and soft
links. A link is a named connection between a directory and an object.

80 May 2000
SAP AG

Hard and Soft Links

Type of Link Description

Hard link, also known as “link”, “absolute link” • Indicated by a separate directory entry
• Cannot exist unless linked to an object
• Cannot cross file systems
Soft link, also known as “symbolic link” • Takes the form of a path name contained
in a file
• Can exist without pointing to an existing
object. (Is an object of type *SYMLNK.)
• Can be removed without affecting the
object
• Can cross file systems
• Only allowed in the IFS

To see the contents of a symbolic link, use WRKLNK with Detail option
*EXTENDED. (This command corresponds to the UNIX command ls -l.) Select
option 12 Work with links.

May 2000 81
7 Additional Information SAP AG

7.3 Code Page Tables

The EBCDIC character set implemented in the SAP System and the SAP kernel differs from the
corresponding IBM character set. These tables show the SAP code pages supported. The text
underneath each table indicates the code page from which they were derived.
SAP Code Page 120

82 May 2000
SAP AG 7 Additional Information

SAP Code Page 500

May 2000 83
7 Additional Information SAP AG

SAP Code Page 410

84 May 2000
SAP AG 7 Additional Information

SAP Code Page 610

May 2000 85
SAP AG

SAP Code Page 800

7.4 Restoring a Backup

Use
You can restore a backup in the sequence given below.

Prerequisites
You have a full backup.

Procedure
1. Control the panel function.
2. Perform an IPL (initial program load) or Install System Menu.
3. To restore a user profile or profiles saved with AS/400 command SAVSYS (Save System) or
SAVSECDTA (Save Security Data), enter AS/400 command RSTUSRPRF (Restore User
Profile).

86 May 2000
SAP AG 7 Additional Information

4. To restore to the system a configuration object saved with the SAVSYS (Save System) or
SAVCFG (Save Configuration) command, enter AS/400 command RSTCFG (Restore
Configuration).
5. To restore libraries saved with the SAVLIB command with LIB(*NONSYS) specified, enter
AS/400 command RSTLIB (*NONSYS) (Restore Library).
6. To restore documents, folders, and distribution objects, enter AS/400 command RSTDLO
(Restore Document Library Object).
7. To restore a copy of an object or objects that can be used in the Integrated File System,
enter AS/400 command RST (Restore Object).
8. To restore saved changes in libraries, documents, and directories, enter AS/400 commands
RSTLIB, RSTOBJ, RSTDLO, RST.
9. To apply journaled changes (for a particular database file member) to recover the file, enter
the AS/400 command APYJRNCHG (Apply Journaled Changes).
10. To restore private authorities to user profiles, enter the AS/400 command RSTAUT (Restore
Authority).

Methods for Restoring a Backup

Parts of the System Command

Model- or Feature-Unique Licensed
Internal Code
Licensed Internal Code Function from Control Panel

OS/400 Objects in QSYS IPL or Install the System Menu

User Profiles RSTUSRPRF

Configuration Objects RSTCFG

OS/400 Optional Libraries

RSTLIB
*IBM
Licensed Program Libraries
RSTLIB
*NONSYS
IBM Libraries With User Data
RSTLIB
*ALLUSR
User Libraries

Filed Documents and Folders

Distribution Objects RSTDLO

Objects in Directories RST

Saved Changes in Libraries,
Documents, and Directories RSTLIB, RSTOBJ, RSTDLO, RST

Journaled Changes APYJRNCHG

Private Authorities RSTAUT

May 2000 87
7 Additional Information SAP AG

7.5 Editing Stream Files

Use
Stream files are files containing a continuous stream of data. Stream files are used, for example,
to store documents and images. On an AS/400 system, R/3 profiles are stored in stream files.

Procedure
You can access AS/400 stream files in a number of different ways.
• Using SAP tool EDTF
EDTF is an editor similar to SEU (Source Entry Utility). The prefix area of each record will
accept edit commands. To display the edit commands available, choose PF1.
• Using Client Access
If you have Client Access, you can also access stream files using this product. Using
CA/400’s Network Drive feature and the capability of CA/400 to perform a character-by-
character conversion from ASCII to EBCDIC and vice-versa, you can work on the AS/400
IFS in the same way as on the PC file system. That is, you can create, edit, and delete files
and directories with all the restrictions that apply to CA/400.

88 May 2000