ebcdic to ascii conversion

SAP R/3 Code Page Conversion EBCDIC ASCII

In-Place Procedure for Systems

on iSeries (AS/400)

Release 4 .6D Vers ion 1 .6

SAP® AG Neurottstr. 16 D-69190 Walldorf

SAP AG Copyright

Copyright ©Copyright 2002 SAP AG. All rights reserved.

No part of this documentation may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.

SAP AG further does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP AG shall not be liable for any special, indirect, incidental, or consequential damages, including without limitation, lost revenues or lost profits, which may result from the use of these materials. The information in this documentation is subject to change without notice and does not represent a commitment on the part of SAP AG in the future.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft®, Windows®, NT® ,EXCEL®, and SQL-Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, OS/390®, OS/400®, AS/400®, iSeries, pSeries, xSeries, zSeries, z/OS®, AFP, Intelligent Miner; WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server are trademarks of IBM Corp. in USA and/or other countries.

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

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 Marketplace, mySAP Workplace, mySAP Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP Business Workflow, SAP EarlyWatch Check, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SAP 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.

2 June 2004

SAP AG Contents

Contents Chapter 1: Introduction .................................................................................................1–1

General Information....................................................................................................1–2 Terminology ................................................................................................................1–4 SAP BW and SAP SEM System Considerations .......................................................1–4 ABAP Program Loads ................................................................................................1–4 General Requirements and Restrictions ....................................................................1–5 Organizational Preparations .......................................................................................1–7 Technical Preparations...............................................................................................1–9 Code Page Conversion Tool Considerations ...........................................................1–17

Chapter 2: R3load In-Place Procedure on iSeries......................................................2–1 Overview.....................................................................................................................2–2 Requirements and Restrictions ..................................................................................2–3 Preparing the In-Place Conversion ............................................................................2–5 Unloading the Database .............................................................................................2–6 Converting to the ASCII Code Page...........................................................................2–9 Troubleshooting........................................................................................................2–13

Chapter 3: General Subsequent Actions.....................................................................3–1 Subsequent Technical Actions ...................................................................................3–2

June 2004 3

SAP AG Typographic Conventions

Typographic Conventions

This convention. . . is used for. . .

Menu Text menu names and menu items; also field names and screen titles. Select File → Open

User Entry exact user input. These are words and characters you type on the keyboard exactly as they are in the documentation; also UNIX users like root, mail, ftp etc. Enter tail -f R3INST.log

File Name file names, UNIX scripts and paths/directories; also screen messages. Delete the line starting with dba in the file /etc/group

<Variables> variables in general, e.g. variable user entries or file names The home directory of the user ora<sid> is /oracle/<SID>

Book Title cross-references to other books

This icon. . . helps you identify. . .

Example an Example. Examples help clarify complicated concepts or activities.

Note a Note. Notes can contain important information like special considerations or exceptions.

Caution a Caution. Cautions should help you avoid errors, for example, those that could lead to data loss.

4 June 2004

SAP AG Change History

Change History

The following table lists the main changes between Version 1.5 and Version 1.6 of this document.

Changes Page

Chapter 1

Remove reference to possible problem with variants, as this has never occurred up to now

1-3

EXT kernel may also be used for conversion 1-5

The EXT kernel should be used if V5R3 is implemented 1-9

Addition of reference to the HR-Recruitment standard text conversion programs and notes 534966 and 595482. Removal of reference to program DB4_CVT_STANDARD_TEXTS

1-11

Program DB4_DDSHHVALUE is irrelevant for 4.6B systems 1-11

RFC Queues should be emptied prior to starting the code page conversion

1-13

Links for retrieving EXT kernel patches have been added 1-18

Chapter 2

Installation of the CPC patch and the latest DbSl patch is necessary if the EXT kernel is to be used

2-5

Query added to the R3SETUP dialog (R3SETUP library name) 2-7

2-10

Recommendation for the number of parallel R3LOAD jobs has been changed

2-7

2-11

Handling SQL0603 errors in the reload 2-14

Troubleshooting: SQL0303 errors and the use of RUTMSJOB and note 211492 to fix the affected tables

2-16

Chapter 3

Correct RFC passwords as described in note 411019 3-3

Program DB4_DDSHHVALUE is irrelevant for 4.6B systems 3-4

Removal of reference to program DB4_CVT_STANDARD_TEXTS 3-4

June 2004 5



Changes Page

References to points specific to V4R5 have been removed from the document, as this release is no longer supported by IBM

Chapter 1

New conversion CD51020297 with downward compatible ASCII kernel at patch level 1444 is now available

1-6

Transaction SLIN can be used to check the ASCII/EBCDIC portability of customer programs

1-6

PTF MF30606 is included in the latest V5R2 Infoapar and should be implemented tp prevent problems with the system backup

1-10

Extended NLS Support is part of the operating system in V5R2 1-10

Ensure PTFs SI08607 (V5R1) or SI08605 (V5R2) have been implemented, in order to avoid problems in the interpretation of the ‘update’ parameter used by SBMJOB

1-11

Note 620462 added to the table of important notes 1-12

4 new programs added to R46CCPC.CAR transport. See note 647583 for details

1-12

Chapter 2 Remove the following profile parameters from the system profile and allow them to default abap/locale_ctype install/codepage/db/transp install/codepage/db/non_transp install/codepage/appl_server

2-3

Number of parallel R3LOAD processes should not exceed 35, to avoid contention problems on larger systems.

2-7

2-10

Chapter 3

Run CRTSAPLCL for each additional code page that will be used in your system and also for the individual application servers in a 3-tier system.

3-2

Investigate note 554792 for information on accessing SAP-tables with 3-2

6 June 2004


operating system utilities after the codepage conversion.

Programs DB4_RPAP_IL_AFTER_CONVERSION and DB4_RPAP_NOTES_AFTER_CONV added to post processing for HR Recruitment customers

3-4

June 2004 7



Changes Page

Chapter 1

Code page conversion now possible from application release 4.6B 1-2

Code Page Conversion webform should only be submitted for the conversion of the production system.

1-2

Added reference to note 599700 1-3

Note 60252 added to table of notes in order to ensure that TCP/IP has been configured correctly

1-9

Implementation of the programs from the attachment R46CCPC.CAR in note 500950

1-9

Deletion of Invalid Temp. tables with SE14 1-11

Preventing potential problems in the unload caused by tables defined in the NAMTAB but not existing on the physical database

1-11

Add reference to note 535554 to the technical preparations 1-11

Chapter 2

CCSID of field information in QAQQINI will not be changed by the code page conversion.

2-3

Troubleshooting: Missing menu nodes and /or texts in area menus 2-14

Chapter 3

Procedure to ensure CCSID of 819 on system profiles 3-3

Removed implementation of Transport R346CCPC from post-processing

3-3

Remove reference to note 535554 from post-processing 3-3

Addition of the programs DB4_CVT_STANDARD_TEXTS, DB4_CVT_EBCDIC_LISTS and DB4_RESTORE_SOC3 to post-processing

3-3

Removed reference to report SAP_INFOCUBES_INDEX_REPAIR for in-place

3-5

8 June 2004



Changes Page

Chapter 1

Extended NLS Support must be implemented on the system to ensure that QSYSLOCALE is available

1-8

Run report RSBDCREO to reduce the amount of data in table APQD 1-10

Chapter 2

install/codepage/appl_server may never be specified in the system profile

2-3

Reference to SQL0603 (duplicate key) errors in the database load at step DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII has been removed. In the in-place procedure, these errors will be recorded on message queue R3CPCWARN and then a switch will be performed to the standard CCSID, 13488, so the problem should then be suppressed.

2-12

Problems with SM59 and RFC added to troubleshooting section 2-14

Chapter 3

Specify abap/import_char_conversion = 2 in the default profile

3-2

Always regenerate system profiles using RZ10 and check the CCSID. 3-3

Run report BMEN_CORRMEN1 to reset menu buffers and prevent problems with Easy Access menus.

3-3

Use of the attached transport from note 500950 in order to correct table contents after conversion

3-3

CO customers :Use transaction GR55 to regenerate all report groups 3-4

June 2004 9



Changes Page

Chapter 1

LODR3KRN specification amended. Always load the ASCII kernel from the conversion CD and then load any necessary patches.

1-8

Chapter 2

Correct the MSGQ specification in the CHGMSGQ command 2-5

Tables D021T and IACHTRCP added to the troubleshooting information for the message SQL0603 in the Load

2-12

10 June 2004



Changes Page

Chapter 1

Changed link to CPC Homepage http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000421617&

1-2

Note added to highlight the Code Page Conversion Check Service offered by SAP Standard Support Services

1-2

Note 554792 added to notes table 1-3

High Availability Software should support BLOBs and be turned-off during the productive code page conversion

1-5

Note regarding V5R2 certification for the ASCII kernel : available from patch level 1278

1-8

V5R2 includes the ASCII run-time environment in the operating system

V5R1 includes the ASCII run-time environment via PTFs in the latest Infoapar. The PRPQ 5799AAS should be removed if it has already been installed already on a V5R1 system (note 538239)

V4R5 still requires the implementation of the PRPQ 5799AAS for ASCII run-time support

1-8

1-9

Link for download of ASCII patches added : http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000018554&

1-13

Chapter 2

DDIC password modification resets the password to the original system default of “19920706”

2-8

Error in RFCRSBTCUPD_IND_IND caused by running under V5R2 without the certified kernel patch level on the ASCII kernel

2-14

Error in Trnsaction SICK caused by running V5R2 without the certified kernel patch level on the ASCII kernel

2.14

Chapter 3

Resume High Availability Software synchronization if it was turned-off during the code page conversion

3-2

Enable future use of Windows 2000 Application Server 3-2

June 2004 11


The following table lists the main changes between Version 0.95 Beta and Version 1.0 of this document.

Changes Page

Chapter 1

Removal of the reference to setting the parameters: abap/locale_ctype install/codepage/db/transp install/codepage/db/non_transp install/codepage/appl_server

1-6

Reference to SAP BW 2.0B added 1-6

QSYSLOCALE library is a prerequisite for correct functioning of the locale creation after the database load

1-8

Initialisation of the QADRT environment is necessary after installing it 1-8

Reference to Notes 16083, 93774 and 428855 added 1-9

Reference to Note 419990 for generation of consistent ABAP loads added

1-9

Reference to Note 538362 for correction of error in SAP_BW_MIGRATION when processing data classes added

1-10

Final check run of SAP_BW_MIGRATION should be made after all of the individual checks have been completed

1-11

Chapter 2

Use of <sid>OFR instead of QSECOFR for unload processing 2-5

Following Caution note added: R3SETUP is not complete until the following message is displayed: R3SETUP/R3SETUPDB4 finished

2-6 2-9

Modification of user DDIC to prevent password request 2-8

Additions to Troubleshooting section:

• DB4CPC_TR_DBEXPR3LOADEXEC_OS4_DB4 Message Permission denied from R3LOAD

• Message CPD0012 • DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII Check for possible inconsistencies in the R3LOAD processing after an uncontrolled system breakdown even when restart appears to have worked correctly. • DBR3LICSTANDALONE_IND_DB4ASCII SAPLICENSE exits with return code 254 • RFCRDDGENMC IND IND

2-11

2-11 2-12

2-13 2-13

12 June 2004


Connect to SAP gateway failed • Section added on problems during post-processing

2-14

Chapter 3

Reset modified user DDIC 3-2

Reference to Note 419990 to ensure consistent ABAP loads added 3-2

Reference to Note 535554 to ensure correct role authorization data for transaction PFCG added

3-2

June 2004 13

SAP AG Introduction Contents

Chapter 1: Introduction

Contents

General Information ..............................................................................................................1–2 Terminology ...........................................................................................................................1–4 SAP BW and SAP SEM System Considerations ................................................................1–4 ABAP Program Loads...........................................................................................................1–4 General Requirements and Restrictions.............................................................................1–5

General Requirements .......................................................................................................1–5 Restrictions.........................................................................................................................1–6

Organizational Preparations ................................................................................................1–7 Technical Preparations.........................................................................................................1–9

Preparing the System.........................................................................................................1–9 Code Page Conversion Tool Considerations ...................................................................1–17

June 2004 1–1

Introduction SAP AG General Information

General Information This documentation describes how to make a code page conversion from EBCDIC to ASCII when your operating system is OS/400. For technical reasons the code page conversion is only offered at SAP R/3 application releases 4.6B and 4.6C or for BW/SEM systems SAP BW 2.0B SP25 or SAP BW 2.1C SP17 (i.e. systems using the pre-requisite downward compatible kernel 4.6D). See note 599700 regarding the 4.6B conversion and the restrictions involved. A code page conversion should only be done by a person with experience in copying systems and with knowledge of the operating system, the database, and the ABAP Dictionary.

Note

Please note that releae V4R5M0 of the operating system is no longer supported by IBM and it is therefore assumed in this documentation that the code page conversion will be performed on releases V5R1M0 or later.

The person performing the code page conversion must either have attended the Code Page Conversion seminar provided by SAP (UABC92) or be certified by SAP to perform OS/DB conversions (TABC92).

A webform is provided by SAP, which you can use to provide information needed by the conversion support group. You should fill out the form and send it to SAP some weeks before the actual conversion of your production system takes place, to allow time to deal with any open issues. You should only submit the webform for the productive conversion. You can find the form at the following address:

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000421617&

Choose Code Page Conversion Notice Form.

Note

A Codepage Conversion Check Service is also offered by SAP Standard Support Services for your productive codepage conversion. This may be performed without additional cost if an upgrade check is included. See the question and answer document (point 62) at the URL given above for further information or contact SAP Standard Support Services.

Choose Questions and Answers about this new strategy

1–2 June 2004


SAP AG Introduction General Information

Caution

The PTF SI03716 (V5R1) from IBM is a prerequisite for the in-place conversion procedure. From operating system release V5R2M0 the PTF is included in the standard system.

Only the central instances will be converted by this procedure. Application servers should be deleted and re-installed. 3-tier sites will need to reconfigure to 2-tier for the duration of the code page conversion procedure.

SAP Notes

Read the following SAP Notes before beginning the code page conversion. These notes contain the most recent information regarding the code page conversion. They are available only in English. Make sure that you have the most recent version of these Notes.

Number Title

500950 R/3 EBCDIC → ASCII Codepage Conversion

599700 iSeries: Codepage Conversion with R/3 4.6B or BW

39510 AS/400: ASCII-EBCDIC Considerations

554792 AS/400: How to access the ASCII/UNICODE DB2/400 Database after conversion

Note

A full system backup should be performed before beginning the code page conversion.

Note

If you experience problems during an EBCDIC → ASCII code page conversion of a production system, create a message in component BC-INS-AS4 in the SAPNet − R/3 Frontend.

SAP will process SAPNet − R/3 Frontend messages concerning problems with the code page conversion only if there is a contact person available on site, who is either an SAP-certified migrator or else has attended the SAP Code Page Conversion Seminar.

June 2004 1–3

Introduction SAP AG Terminology

Terminology

Source System and Target System

For an in-place code page conversion, the source system and the target system remain the same, having the same <sid>.

Code page Conversion

In-place replication of an SAP System for the purpose of converting the databases from EBCDIC to ASCII. Certain SAP parameters may change during an in-place conversion.

Placeholders

Placeholders such as <sid> are used in commands. They are used in the same way as in the SAP System installation documentation, and must be replaced with the values valid for your site.

SAP BW and SAP SEM System Considerations The main difference between the code page conversion of an R/3 System on the iSeries and that of a SAP BW System or a SAP BW-based system such as SAP SEM, results from the DB-platform specific implementation of the Fact-Table indexing. This extremely platform-specific implementation of these indices cannot be depicted in the ABAP Dictionary, so this information is not available for the SAP Tools R3LDCTL and R3LOAD.

In this documentation, the additional steps required for the code page conversion of a SAP BW or SAP SEM System will be described in specific sections in this documentation.

ABAP Program Loads The ABAP loads are platform- and code page-dependent programs, which are generated during runtime and which are stored in database tables. They are not unloaded when you use the R3LOAD procedure to convert your SAP System. The ABAP loads are generated in the target system when they are first used.

1–4 June 2004

SAP AG Introduction General Requirements and Restrictions

General Requirements and Restrictions

General Requirements

Caution

The following in-place conversion method must not be used for systems with a non-Latin-1 code page.

The export/import procedure, described in the SAP documentation SAP R/3 Code Page Conversion EBCDIC -> ASCII Export/Import Procedure for Systems on iSeries (AS/400), must be used.

To make a code page conversion, the versions of the SAP System and the installation tools must be the same on the ASCII and EBCDIC systems (exceptions are only allowed if they are described in an SAP Note). Before starting the code page conversion :

• Ensure that the EBCDIC kernel on your system is up-to-date

• Order the latest version of the conversion CD (CD51020297) which contains the downward-compatible ASCII COM-kernel at patch level 1444 which is a pre-requisite for uploading subsequent patches from the SAP Service Marketplace.

It is also possible to use the EXT version of the EBCDIC and ASCII kernels to perform the conversion now. See note 500950 for details.

• Obtain the latest versions of the notes.

Caution

The PTF SI03716 (V5R1) from IBM is a prerequisite for the in-place conversion procedure. From operating system release V5R2M0, the PTF is included in the standard system.

Caution

SAP Note 39510 deals with points arising from the different sort sequences between ASCII and EBCDIC. Programs that have been developed by the customer should be checked for potential problems in connection with sorts, processing of ranges, SELECT-OPTIONS, CPIC and up/download considerations. Authorization and domain definitions should also be checked, as they may be specified by means of ranges. Transaction SLIN can be used to assist in this checking process. Just turn off all the checks except for the one relating to ASCII/EBCDIC Portability.

June 2004 1–5

Introduction SAP AG General Requirements and Restrictions

Restrictions

Caution

If High Availability software (e.g. MiMiX (Lakeview), LiveResiliency (Data Mirror), Vision-Suite (Vision Solution)) is in use at your site, then you must ensure that your current version supports BLOBs, as the ASCII system uses some tables with BLOBs.

It is also advisable to stop the data synchronization for the duration of the productive conversion.

Caution

The source system must be in a consistent state before it can be copied and the in-place conversion should only be performed when the SAP System is inactive.

Caution

SAP recommends in any case that the *INTERACT memory pool should not be configured, as there is normally very little truly interactive load on an R/3 System. For the code page conversion it is important that this restriction be observed, as otherwise all the R3SETUP procedures, which run in QINTER, will block the pool *INTERACT. As we also recommend that performance adjustment (QPFRADJ) is turned off, there is little hope of the system correcting itself automatically in the worst case.

Note

The language-set code page may not be changed during the SAP code page conversion (for example, Latin-1 (EBCDIC, 0120) to Latin-2 (ASCII, 1401)). If the system does not use the SAP code page 0120 (see table TCPDB), create a message in component BC-INS-AS4 in the SAPNet − R/3 Frontend to obtain the necessary code page conversion tables. Code page 0120 will be converted to 1100 during the standard code page conversion.

1–6 June 2004

SAP AG Introduction Organizational Preparations

Organizational Preparations

Note

Take into account the downtime of the source system (for preparations and conversion) when planning the code page conversion.

Note

For SAP BW and SAP SEM systems, you must make sure that a minimum level of SAP BW 2.0B SP23 or SAP BW 2.1C SP15 is installed on your system. If necessary, an upgrade should be performed prior to the code page conversion. To avoid the following spurious, but non-critical errors in the post-conversion processing, SAP BW 2.0B SP25 or SAP BW 2.1C SP17 or higher should be installed. The following messages may be ignored if they are displayed:

Error messages: Cannot add index to table RSMDCNVTAB CHA Error # 3

Cannot add index to table RSMDCNVTAB SID Error # 3

Archive Files

If at all possible, make an archiving run before running the code page conversion, as this will reduce the amount of data to be converted. Archived data does not require conversion, as the code page is stored along with the data, ensuring that conversion is automatically performed when you display from the archive.

Configuration Analysis / Hardware Analysis

The following factors have to be determined: • The expected size of the database • Additional disks or other hardware required • 10% additional memory required • No additional CPU requirement • Approximately 5% additional disk requirement for the exported pooled and cluster tables

during the in-place conversion • For R/3 Systems: 55-70% additional disk requirement • For SAP BW or SAP SEM systems: 40-50% additional disk requirement

Note

See Hardware and Software Requirements Check in the SAP System installation documentation to determine the system requirements.

June 2004 1–7

Introduction SAP AG Organizational Preparations

Test Run / Schedule • Perform a test run of the code page conversion. The time taken by the test run is used to

calculate the system downtime:− Perform a complete test run, meaning that the entire database is converted.

Approximate system downtime will be equal to the total test time (that is, time for the conversion and any post-installation processing).

− For SAP BW and SAP SEM systems, you must also take time to build the DB indices for the Fact Tables and may have to rename the logical system.

− Test all critical transactions on the system after conversion. Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used.

• Define a schedule for the test conversion and the final conversion.

1–8 June 2004

SAP AG Introduction Technical Preparations

Technical Preparations In order to ensure the consistency of the database, it is necessary to prepare the source system and to carry out some subsequent actions after the conversion is complete. This is not necessary when performing a test run.

The following list describes important preparatory actions (for further information on SAP System administration, see the SAP Online Documentation).

Preparing the System • Check that the latest IBM Info APAR for your system release has been implemented

before running the code page conversion. V5R2 users in particular, should ensure that MF30606 has been implemented, to prevent problems with uncommitted changes occurring, during the system backup, after the code page conversion. This is included in the latest Infoapar.

• The ASCII kernel should be loaded from the new conversion CD (CD51020297) to the system at some convenient point prior to the code page conversion using the following commands:

LODRUN DEV(*OPT) DIR(‘OS400/AS400/TOOLS’) ADDLIBLE LODR3KRN LODR3KRN SAVLIB(R346DAOPT) DEV(*STMF) STMFDIR('/QOPT/CD51020297/OS400/AS400/V4R5M0') KRNLIB(<ASCII-Krnlib>)

This kernel may not be applied at this point, however. The apply kernel follows in the course of the conversion procedure.

Note

If the V5R2 release of the operating system is installed, then the latest kernel patch must also be applied to the ASCII kernel in order to ensure that a V5R2 certified kernel is implemented. The patch may be found on the SAP Service Marketplace at :


V5R2 certification is available from patch level 1278.

If V5R3 is in use, then the latest 4.6D EXT kernel should be installed. This kernel can be found at:


V5R3 is certified from kernel patch level 1850

• The IBM source library QSYSLOCALE is required in order for the locales to be created after the database has been loaded. This requires the implementation of Extended NLS Support (License Program Option 21). This option is is part of the operating system at release V5R2.

June 2004 1–9



Introduction SAP AG Technical Preparations

• The ASCII runtime environment is also required for correct running of the R/3 System in an ASCII environment. At V5R2 the environment is included as part of the operating system. With release V5R1 the environment is included with PTFs SI04657 and SI06483 which may be implemented via the latest V5R1 Infoapar II12833.

Note

Customers at release V5R1 who have already installed the PRPQ 5799AAS should delete it and implement the latest Infoapar, as described in note 538239.

Note

The entry of QADRT in the system library list has no impact at all on the running of SAP systems in EBCDIC.

• Initialise the QADRT environment with the following batch job to prevent spurious errors

occurring later SBMJOB CMD(CALL PGM(QADRTCINF) PARM('update')) JOB(QADRTCINF)

Note

This initialization is necessary at all release versions of the operating system.

In order to avoid a potential problem with the way that QADRTCINF interprets the ‘update’ parameter, you should ensure that PTF SI08607 (V5R1) or SI08605 (V5R2) is implemented on your system. These PTFs have already been included in the latest Infoapar for each of these releases.

• Make sure you have implemented the following Notes on your system:

Number Title

16083 Standard jobs, reorganization jobs

60252 TCP/IP Host Name configured incorrectly

93774 TSV_INDEX_INDEX_NO_ROLL_MEMORY in RSORATDB

428855 OS/400 System Values

620462 Symbolic links MUST be correct before R3SETUP runs

1–10 June 2004


• Before you begin the EBCDIC > ASCII code page conversion, make sure that the following prerequisites have been satisfied, if the component HR-Recruitment (PA-RC) is in use on your system:

1. Note 534966 must have been implemented. 2. The conversion reports described in note 595482 : (RPAP_CONV_STDTEXTS_EBCDIC for standard texts,

RPAP_CONV_IND_LETTER_EBCDIC for individual applicant letters, RPAP_CONV_NOTES_EBCDIC for notes), must have been run. These reports will convert standard texts, applicant letters and notes, which were created in Winword prior to the implementation of note 534966.

• Attachment R46CCPC.CAR from note 500950

This transport contains the following reports for correction of text data in binary fields :

DB4_APQD - correct table APQD

DB4_DDSHPVALUE - correct table DDSHP

DB4_DDSHHVALUE - correct table DDSHH

This program need not be run if the conversion is being performed at 4.6B, as the table does not exist.

DB4_CVT_EBCDIC_LISTS - convert EBCDIC listings

DB4_BACKUP_SOC3 - export SOC3 prior to conversion

DB4_RESTORE_SOC3 - import SOC3 after conversion

The following 4 programs are also included in the transport and are described in note 647583. The programs are only required for customers who have implemented the HR Recruit,ment component (PA-RC). These customers must run the first 2 programs before the code page conversion is started.

DB4_RPAP_IL_BEFORE_CONVERSION - for applicant letters (Cluster AL)

DB4_RPAP_NOTES_BEFORE_CONV - for notes (Cluster AN)

DB4_RPAP_IL_AFTER_CONVERSION - for applicant letters (Cluster AL)

DB4_RPAP_NOTES_AFTER_CONV - for notes (Cluster AN)

In addition, one new table is also defined and generated in the dictionary :

DB4_SOC3 - backup table for SOC3

The CAR file contains a transport which should be uploaded to /usr/sap/trans with FTP in binary mode. The file can then be unpacked with the following instructions :

cd '/usr/sap/trans'

June 2004 1–11


sapcar '-xvf /usr/sap/trans/r46ccpc.car'

The following files will be unloaded :

1. /usr/sap/trans/data/r46ccpc.sap

2. /usr/sap/trans/cofiles/k46ccpc.sap

The transport should then be implemented with the following tp commands

tp 'addtobuffer sapk46ccpc <sid> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL'

tp 'import sapk46ccpc <sid> u12689 pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL'

Note

The program DB4_BACKUP_SOC3 should be executed prior to running the code page conversion. It takes a backup of the table to the newly generated database table DB4_SOC3. See note 603153 for more information.

The following 2 programs should also be run before the code page conversion if the component HR Recruitment is in use (PA-RC)

DB4_RPAP_IL_BEFORE_CONVERSION

DB4_RPAP_NOTES_BEFORE_CONV

The other programs are for use in the post-processing phase.

• No canceled or pending update requests should be in the system. Check this via: Tools →

Administration → Monitor → Update (SM13). If canceled or pending updates exist, these must be updated again or deleted from all clients. You can see whether canceled or pending updates exist by finding out if table VBDATA contains any entries. Proceed as follows in order to find the canceled or open updates: 1. Call transaction SM13. 2. Delete the default values for the client, user, and time. 3. Choose all update requests. If canceled or pending records exist, then these must be updated again or deleted. Check whether this action was successful using transaction SE16 for table VBDATA.

• To reduce the amount of data to be processed, you can clean-up your invalid/temporary

tables using SE14

1–12 June 2004


SE14 Extras Invalid Temp. table Select all of them and then ‘delete’

• RFC Queues should be empty before the code page conversion is started. Either complete the processing of RFC queues or delete them using report RSTRFCQD. The control tables for these queues contain fields which are defined as character but may contain binary data, which makes it impossible for the conversion procedure to be sure of converting them correctly.

• Prevent potential problems in the reload: caused by tables which exist in the NAMTAB but not on the physical database. − Use the SQL-Query given below to find out if any such tables exist

select t1.tabname from r3<sid>data/ddntt t1 exception join r3<sid>data/systables t2 on t1.tabname = t2.table_name

where t1.tabtype = 'T' and t1.tabform = 'T'

− Check any tables in the report to see if you need to convert them. For example, tables with names beginning QCM… are not usually converted, as they are left over after the activation of a table modification.

− Tables which are not required but are defined in the dictionary may be deleted using SE11. If the table is not defined in the dictionary, only in the NAMTAB, then it will have to be manually deleted using the following SQL statements :

DELETE FROM R3<sid>DATA/DDNTT WHERE TABNAME = ‘tabname’

DELETE FROM R3<sid>DATA/DDNTF WHERE TABNAME = ‘tabname’

− Tables which you wish to convert should be activated using SE11, entering the information in the dictionary first, if necessary

• Call DB02 and choose Refresh File Statistics to refresh the content of the statistics file

DBSTATTDB4, which is referenced to optimize the R3LOAD package sizes. • On non-SAP BW/SEM Systems you should run the consistency check of DB02 and save

the output for later comparison. • Suspend all released jobs. To do this, run report BTCTRNS1.

• To be able to generate ABAP loads that are consistent with their sources, call transaction SGEN, as described in Note 419990 (point 1) to specify the available loads.

• To avoid inconsistencies in role authorizations (transaction PFCG), ensure that note 535554 is implemented on the system before the code page conversion is started.

• To reduce the amount of data in table APQD run report RSBDCREO. This should be done to prevent problems running program DB4_APQD in the post-conversion processing.

• FI customers: An additional consistency check can be performed by running the job SAPF190 before the code page conversion, as well as after, and then comparing the results. No customer data may be changed in the meantime. (Accounting → Financial

June 2004 1–13


Accounting → General ledger → Periodic Processing → Closing → Check/count → Comparison)

• FI customers: Consistency can be checked further by running the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet), RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset retirements) before the code page conversion, as well as after, and then comparing the results. No customer data may be changed in the meantime.

• CO customers: An additional consistency check can be performed by running the report group 1SIP before the code page conversion, as well as after, and then comparing the results. No customer data may be changed in the meantime.

• SAP BW and SAP SEM customers: Correction report SAP_DROP_TMPTABLES to delete temporary objects Tables from a special namespace are used to store and re-use temporary information in SAP BW systems. Since these tables are sometimes created using native SQL, no ABAP Dictionary (DDIC) information exists for them. This can lead to problems if the tables are converted. Since the information contained in these tables is in any case redundant, they should be deleted before performing the code page conversion. The name of such tables should match one of the following patterns: − /BI0/01<number> − /BI0/02<number> − /BI0/02T<number> − /BI0/03<number> − /BI0/04<number>* − /BI0/06<number>

As logging is performed on other SAP BW tables, these tables should not be deleted using native SQL. Use the report SAP_DROP_TMPTABLES, specifying all the parameters, to delete them.

• SAP BW and SAP SEM customers: Correction report SAP_BW_MIGRATION − Check for changed Infocubes, ODS Objects and PSA structures

Infocubes will be activated during code page conversion to generate the correct structures (table layout, indexing). Therefore, check the system to ensure that there are no new versions of these objects, which have not yet been activated. All the latest versions should be activated before starting the code page conversion and also prior to any other pre-unload analyses, as the activation may also have an impact on them. Run report SAP_BW_MIGRATION, specifying the parameters as follows: Modified Versions: P_MODIF = only check for changes Check and Repair: P_REPAIR = perform the check and then automatically generate all changed objects

− Check the Data Class

1–14 June 2004


Caution

If the data class is incorrect, but the same in both SAP BW and DDIC, the program will not correct the error. Refer to Note 538362 to establish the necessary support package for your SAP BW system in order to correct this error.

SAP BW transactional data tables, which are in fact tables, are handled differently from other table types (for example, Basis tables, metadata) by the code page conversion. The data class is used to recognize these tables, which should belong to class DFACT. No other tables should be entered in this data class. Run report SAP_BW_MIGRATION with the parameters set as follows: Differing Data Classes: P_DATACL = check data classes Check and Repair: P_REPAIR = perform the check and then automatically generate all changed objects

− DB2/400-Specific Operations on the Source System Due to a long-standing program error, there is a possibility that some entries in the table DBDIFF may be incorrect. This can cause problems during the generation of the new ASCII system. In order to avoid these problems, the program SAP_BW_MIGRATION should be run with the parameter Repair DBDIFF Entries (P4_DBDIF) specified. Due to program cancellations, a situation may rarely arise, whereby temporary SAP BW-Tables are not registered in SAP BW. The report SAP_DROP_TMPTABLES will not, therefore, clear these tables. The program SAP_BW_MIGRATION should be run afterwards, with the parameter Delete Temporary Tables (P4_TMPTA) specified in order to remove these tables.

− Final Check Run of SAP_BW_MIGRATION To ensure that all the changes have been made successfully, the program should be run once more with all the relevant flags set. Once the reports SAP_DROP_TMPTABLES and SAP_BW_MIGRATION have been run, no more work may be done in the SAP BW system, since the effects of these corrections could be undone by the SAP BW functions. At this point the code page conversion should be started.

Caution

Prerequisites for a code page conversion:

Before running the in-place code page conversion, make sure that: - No upgrade-prepare is performed. - No incremental conversion is in progress.

June 2004 1–15


To test if an incremental conversion is in progress, start the transaction ICNV. If there are any table entries in the TICNV, an incremental conversion is in progress. In this case, you have the following options:

1. Defer the code page conversion until the incremental conversion has finished.

2. Try to finish the incremental conversion by performing the following steps:

a) If the tables are in state ‘For conversion’ or in state ‘Done’, delete the entries by choosing CONTROL -> DELETE ENTRY.

b) If the tables are in any other state, you have to finish the incremental conversion. Choose the button Assistant and proceed according to the Online Documentation.

1–16 June 2004

SAP AG Introduction Code Page Conversion Tool Considerations

Code Page Conversion Tool Considerations

Note

It is recommended that you use the latest version of the code page conversion tools R3SETUP, R3LDCTL and R3LOAD for your SAP System release (EBCDIC and/or ASCII) if not stated otherwise. If patches for the programs are available, you can download them from the SAP Service Marketplace. Otherwise, the latest version will be available on the conversion CD.

You can find the EBCDIC patches at: http://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000019588&

The ASCII patches may be found at :


The patches for the EXT versions of the kernel may be found at:

EBCDIC EXT-Kernel


ASCII EXT-Kernel


For the latest documentation, refer to SAP Note 500950.

June 2004 1–17



http://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000057239&%20


SAP AG R3load In-Place Procedure on iSeries Contents

Chapter 2: R3load In-Place Procedure on iSeries

Contents

Overview .........................................................................................................................2–2 Requirements and Restrictions ...................................................................................2–3

Requirements .............................................................................................................2–3 Technical Restrictions ................................................................................................2–3

Preparing the In-Place Conversion..............................................................................2–5 Loading the Objects Required for the Conversion (Library R3SETUP) .....................2–5 Copying the Command Files from CD........................................................................2–5

Unloading the Database................................................................................................2–6 User Entries for R3SETUP.........................................................................................2–6

Converting to the ASCII Code Page.............................................................................2–9 Converting to the ASCII Code Page on iSeries..........................................................2–9 Modifying User DDIC..................................................................................................2–9 Reloading the Database ...........................................................................................2–10

Troubleshooting...........................................................................................................2–13 In the Database Unload............................................................................................2–13 In the Database Load ...............................................................................................2–14 Problems During Post-Processing ...........................................................................2–16

June 2004 2–1

R3load In-Place Procedure on iSeries SAP AG Overview

Overview This chapter describes the in-place code page conversion procedure for the DB2/400 platform.

With the SAP installation tool R3SETUP, you can export and import your database in a database-independent format. This procedure generates a database export of all SAP cluster and pooled tables and converts all others that are defined in the ABAP Dictionary in-place, without performing an export/import.

The R3load procedure consists of three main steps: 1. Unloading the pooled and cluster databases that are not to be converted in-place 2. Performing the in-place conversion for the transparent tables 3. Reloading the pooled and cluster databases

Caution

Only central instances will be converted by this procedure. Application servers should be deleted and re-installed. 3-tier sites will need to reconfigure to 2-tier for the duration of the code page conversion procedure.

2–2 June 2004

SAP AG R3load In-Place Procedure on iSeries Requirements and Restrictions

Requirements and Restrictions

Requirements • The PTF SI03716 (V5R1) from IBM is a prerequisite for the in-place conversion

procedure. From operating system release V5R2M0 the PTF is included in the standard system.

• A full system backup should be performed before beginning with the code page conversion.

• Sufficient free disk space for the in-place conversion. About 5% additional space will be required temporarily, for the pooled and cluster tables that must be exported. For an R/3 system, an increase of 55-70% disk space utilization may be expected after the in-place conversion. For SAP BW, an increase of about 50% in the database size may be expected.

Technical Restrictions • R3SETUP will convert all SAP objects that are defined in the ABAP Dictionary.

Other objects are not converted by R3SETUP (e.g. amended query option files – QAQQINI copied and amended for a specific system or customer-defined tables outside the SAP Standard).

QAQQINI (if a special version exists) should not under any circumstances be changed in the course of the code page conversion. The following CCSID information will be shown by DSPFFD both before and after the code page conversion :

CCSID = 37 for QQPARM and QQVAL and CCSID = 13488 for QQTEXT

Note

It is the customer’s responsibility to convert any of his own customer-defined tables

• Changes to database objects that cannot be maintained in the ABAP Dictionary (Transaction SE14) will not be converted.

• Some objects (for example, EVIs) will not be converted even though they are accessible with SE14. EVIs from the SAP BW standard system will be rebuilt when report SAP_INFOCUBE_INDEXES_REPAIR is run. Any customer-generated EVIs will have to be manually rebuilt.

• No index names longer than 18 characters are allowed on the database to be converted.

• The following profile parameters should be removed from the system profile and allowed to default :

June 2004 2–3

R3load In-Place Procedure on iSeries SAP AG Requirements and Restrictions

abap/locale_ctype install/codepage/db/transp install/codepage/db/non_transp install/codepage/appl_server

• The language-set code page may not be changed during the conversion (for example,

Latin-1(EBCDIC, 0120) may not be converted to Latin-2 (ASCII, 1401) or vice-versa). If source tables do not have an SAP code page of 0120, you should create a message on component BC-INS-AS4 in the SAPNet – R/3 Frontend to obtain the necessary code page conversion tables. The standard code page conversion will convert EBCDIC 0120 to ASCII 1100.

See also the section ”General Requirements and Restrictions” in chapter “Introduction”.

2–4 June 2004

SAP AG R3load In-Place Procedure on iSeries Preparing the In-Place Conversion

Preparing the In-Place Conversion See also the chapter “Introduction”, section “General Preparations”, and the chapter ”Preparations”.

Loading the Objects Required for the Conversion (Library R3SETUP) 1. Sign on to your iSeries machine with a user that has the same authority as QSECOFR. 2. Enter the command:

CALL R3<sid>400/R3INLPGM. 3. Check that the library R3SETUP does not exist. It should be renamed if it exists. 4. Place the code page conversion CD into the CD drive of your iSeries machine. 5. To load the objects required for installation and configuration from the CD, execute

the LODRUN (Load and Run) command by entering: LODRUN <CD_device_description_name> DIR(‘/OS400/AS400/INSTALL’)

6. If you are planning to convert using the EXT version of the kernel, then the CPC patch from the EBCDIC area in the SAP Service Marketplace should be installed at this point. It is also necessary to install the latest DbSl patch in the R3SETUP library, as well as the kernel. Once both patches have been installed, then run FIXR3OWNS from a user with QSECOFR authorization.

Copying the Command Files from CD 1. Add the R3SETUP library to your library list. To do so, enter the following command: ADDLIBLE R3SETUP

Note

If, for any reason, the library R3SETUP is to be renamed on your system, this must be done before the CPYR3CPC command in step 3 below is executed. The command sets up a new link based on the name of the R3SETUP library. A subsequent rename will invalidate this link.

2. Check that the directories /tmp/unload/<sid>, /tmp/reload/<sid> and /tmp/data/<sid>/data do not exist.

3. Enter the command: CPYR3CPC SID(<sid>) METHOD(*INPLACE) <SID> is the SAP system ID of the system you want to convert.

4. Log off from the system.

The following template files are copied to the directories listed below: /tmp/unload/<sid> DBEXIP.R3S /tmp/reload/<sid> DBCPIP.R3S, DBCPIPBW.R3S

June 2004 2–5

R3load In-Place Procedure on iSeries SAP AG Unloading the Database

In addition the directory /tmp/data/<sid>/data is also created to contain the export files.

Note

Running R3SETUP (General Procedure)

For information on using R3SETUP, see Chapter 5 of the documentation SAP Basis Installation: IBM eServer iSeries

Unloading the Database

User Entries for R3SETUP

Caution

Authorization problems occur with V5R2 if user <sid>OFR is not used for the unload processing.

You should always log off and then log on again as <sid>OFR before restarting R3SETUP after an error in the unload processing

1. Sign on again to your iSeries machine as user <sid>OFR. 2. Enter the following commands:

STOPSAP (and wait until the system has really stopped) cd ’/tmp/unload/<sid>’ addlible R3SETUP

Note

Use DSPLIBL to ensure that R3SETUP is ahead of the kernel in your library list.

CHGMSGQ MSGQ(<sid>OFR) DLVRY(*HOLD) CHGJOB BRKMSG(*HOLD) The change to the message queue and the job should prevent long-running terminal

sessions being held up by BREAK messages.

Note

If SAPOSCOL is active on this <sid>, it should also be stopped

2–6 June 2004

SAP AG R3load In-Place Procedure on iSeries Unloading the Database

3. Start R3SETUP with the specified command file option, specifying the command file

to unload the pooled and cluster tables that are not to be converted in-place: R3SETUP dbexip.r3s

4. In the Requesting installation details step (CENTRDBINSTANCE_IND_DB4ASCII), you are prompted to enter your choice or confirm the default value: • The SAP system ID of the EBCDIC system, this must be the original <sid>. • The SAP instance number of the EBCDIC system, this must be the original

number. • The name of the SAP central instance host of the EBCDIC system, this must be

the original host-name. • The name of the R3SETUP library. • The maximum number of parallel processes you wish to run, for example 8.

Note

SAP recommends one R3LOAD job per available CPU, except in the case of 1-way systems where 2 R3LOAD jobs should be specified. For larger systems the value should not exceed 35 parallel processes in order to avoid contention.

R3SETUP now runs through the remaining export steps without requiring further user entries. A complete list of the steps is given here. The output files will be split up into export files with suffix .001, .002, .003, and so on. The size of the export files will be calculated based on an internal algorithm in R3LOAD.

Caution

R3SETUP is not complete until the following message is displayed:

R3SETUP/R3SETUPDB4 finished

Step Description Technical Name

Requesting export details DB4CPC_DBEXPORTINSTANCE_OS4_DB4 Check validity of TCPDB entry DB4CPC_TR_TCPDBCHECK_OS4_IND Requesting export-specific parameters DB4CPC_DBEXPASSISTENT_OS4_DB4 Requesting information on CD-ROMs DBEXPSERVER_IND_IND Creating the export directories DBEXPDIRECTORIES_IND_DB4 Creating the R3load control files DB4CPC_R3LDCTL_OS4_DB4 Clear Monitor Data DB4CPC_DB4CLEANUPEXPORT_OS4_IND Creating a link for R3load R3LOADLINK_IND_DB4

June 2004 2–7

R3load In-Place Procedure on iSeries SAP AG Unloading the Database

Copying the control files for R3load DBEXPCOPYR3LDCTLFILES_IND_IND Creating the command files for the export DB4CPC_DBEXPR3LOADCMD_OS4_DB4 Preparing to start R3load DBR3LOADEXECDUMMY_IND_IND Exporting the database DB4CPC_DBEXPR3LOADEXEC_OS4_DB4

When the export has finished, R3SETUP ends with the message R3SETUP finished.

List of Files Unloaded from iSeries

Files from Directory /tmp/data/<sid>

Files with extension 001, 002, ...

Files with extension STR, TOC, TPL

Watching the Unload Progress

All error messages, warnings and other information from R3SETUP are written to the log file DBEXIP.log.

You can obtain online help on a message by clicking on it in the log view and choosing Help.

Important error, warning and info messages are also written to your terminal and to the message queue R3<sid>DATA/R3CPCWARN.

When R3SETUP Stops

If R3SETUP exits with an error message, see the log file for error details and possible solutions. Eliminate the cause of the error and restart R3SETUP. The unload will be continued with the step that had not finished successfully.

When the unload is completed, R3SETUP ends with the message R3SETUP finished.

Caution

DO NOT, UNDER ANY CIRCUMSTANCES, attempt to start the R/3 System in the period between running R3SETUP to unload and then running it again to reload the converted databases.

2–8 June 2004

SAP AG R3load In-Place Procedure on iSeries Converting to the ASCII Code Page

Converting to the ASCII Code Page

Converting to the ASCII Code Page on iSeries

Performing the Switch to the ASCII Kernel

Note

This switch must be performed after the R3SETUP unload using the EBCDIC kernel has been successfully completed and before the R3SETUP conversion of the central instance is started.

Use the following procedure to activate the ASCII kernel, which has been previously loaded from the migration CD. For more information, see “Technical Preparations”. RMVR3KRN <sid>

ADDLIBLE <ASCII-krnlib> APYR3KRN SID(<sid>) KRNLIB(<ASCII-krnlib>) DLTSQLPKG(*YES)

Note

If the deletion of the SQL-Packages does not work for any reason, you can either repeat the APR3KRN command as given above or use DLTR3PKG to delete them DLTR3PKG SID(<sid>) PKGTYPE(*ALL)

If the deletions still fail, delete the packages manually. The libraries from which they need to be deleted have names of the format R3<sid>annnn. SQL Packages are also contained in libraries with the generic name R3<sid>X000*

DO NOT delete SQL Packages from the library QSYS.

Caution

Log off from the session to clean up any residual session pointers to EBCDIC objects.

Modifying User DDIC If the password for user DDIC has been modified after the initial installation, it will be requested by R3SETUP at a point in the procedure after the databases have been loaded. As this may not be convenient if, for example, the procedure is running overnight, the following SQL statement may be used to prevent the request being made by R3SETUP:

June 2004 2–9

R3load In-Place Procedure on iSeries SAP AG Converting to the ASCII Code Page

UPDATE R3<sid>DATA/USR02 SET BCODE = x'61D26428640DBAB5' WHERE mandt = '000' and bname = 'DDIC'

This will change the password back to the original system default “19920706”.

Reloading the Database

Caution

Authorization problems might occur due to a switch from your logon user to <sid>OFR. Therefore, you should always log off and then log on again as a user with QSECOFR authorization before restarting R3SETUP.

1. Sign on again to your iSeries machine with a user that has the same authority as QSECOFR.

2. Run the initial program to set up the <sid>OFR environment: CALL R3<sid>400/R3INLPGM CHGMSGQ MSGQ(<user>) DLVRY(*HOLD)

<user> is the user with which you you signed-on CHGJOB BRKMSG(*HOLD)

The change to the message queue and the job should prevent long-running terminal sessions being held up by BREAK messages.

3. Add the library R3SETUP to your library list and change your current directory to the one containing the reload templates: ADDLIBLE R3SETUP CD ‘/tmp/reload/<sid>’

4. Start R3SETUP specifying the command file for converting the code page of an R/3 dialog instance: R3SETUP dbcpip.r3s For SAP BW and SAP SEM systems: Use the template dbcpipbw.r3s

5. In the Requesting installation details step (CENTRDBINSTANCE_IND_DB4ASCII), you are prompted to enter your choice or confirm the default values:

• Your SAP system ID of the ASCII system. The original <sid> must be entered

here. • The SAP instance number of the ASCII system. The original instance number

must be entered here. • The name of the SAP central instance host of the system. The original host name

must be entered here. • The name of the R3SETUP library.

• Enter the name of the ASCII Kernel Library • Enter the number of parallel R3load processes you require, for example 8

2–10 June 2004

SAP AG R3load In-Place Procedure on iSeries Converting to the ASCII Code Page

Note

SAP recommends one R3LOAD job per available CPU, except in the case of 1-way systems where 2 R3LOAD jobs should be specified. For larger systems the value should not exceed 35 parallel processes in order to avoid contention.

R3SETUP now runs through the remaining installation steps without requiring further user entries unless the password for the DDIC user has been changed from the default value. If this change has been made, a password entry will be required for the steps that run after DBR3START_IND_DB4ASCII.

Caution

R3SETUP is not complete until the following message is displayed: R3SETUP/R3SETUPDB4 finished

A complete list of the performed steps is given below.

Step Description Technical Name

Requesting installation details DB4CPC_CENTRDBINSTANCE_OS4_DB4ASCII

SAP codepage needed to install an ASCII system

DB4CPC_DB4ASCIIINFO_IND_DB4ASCII

Check that the ASCII kernel is available DB4CPC_CHKASCIIKRN_OS4_IND

Checking Available Space for the SAP Instance DB4CPC_CENTRDBSPACECHECK_OS4_DB4ASCII

Requesting information on CDs DB4CPC_CDSERVERMIG_OS4_DB4ASCII

Delete SQL Packages DELETE_EPACKAGE_OS4_DB4ASCII

Create ASCII locales DB4CREATELOCALE_IND_DB4ASCII

Copying the PTF Check File CPYPTFFILE_IND_DB4ASCII

Checking if the DB Export CD is available CHECKEXPORTCDINCDROM_IND_IND

Creating a link for R3load R3LOADLINK_IND_DB4ASCII

Clean up selected data (DDIC, DBMON, IFS) DB4CLEANUPASCII_OS4_IND

Copy sort sequence tables DB4CREATESORTTABLE_IND_DB4ASCII

Creating the command files for the DB load DBR3LOADCMD_IND_IND

Preparing to load the ABAP Dictionary tables DBR3LOADDDICDUMMY_IND_DB4ASCII

Loading the ABAP Dictionary tables DB4CPC_DBR3LOADDDIC_OS4_DB4ASCII

Preparing to start R3load DBR3LOADEXECDUMMY_IND_IND

R/3 Systems only: Loading the database DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII

SAP BW/SEM Systems only: Loading the database

DB4CPC_DBR3LOADEXEC_BW_OS4_DB4ASCII

June 2004 2–11

R3load In-Place Procedure on iSeries SAP AG

SAP BW/SEM Systems only: Loading the SAP BW Fact Tables

DB4CPC_DBR3LOADFACT_OS4_IND

Preparing to load the database views DBR3LOADVIEWDUMMY_IND_IND

Loading the database views DB4CPC_DBR3LOADVIEW_OS4_DB4ASCII

Deleting ASCII loads DELETELOADS_IND_DB4ASCII

Starting journaling STARTJOURNAL_IND_DB4ASCII

Ensuring ABAP Dictionary consistency DIPGNTAB_IND_DB4ASCII

Deleting the SQL packages DELETE_PACKAGE_IND_DB4ASCII

Changing code page specific records DB4CPC_TCPDBENTRY_OS4_IND

Clear the tables TATGPC and TATGPCA DB4CLEANUPTATGPC_OS4_IND

Creating a temporary R/3 license DBR3START_IND_DB4ASCII

Starting the R/3 System DB4CPC_DBR3START_IND_DB4ASCII

Post-activation of runtime objects for synchronous matchcodes

RFCRDDGENMC_IND_IND

Adjust background entries RFCRSBTCUPD_IND_IND

2–12 June 2004

SAP AG R3load In-Place Procedure on iSeries Troubleshooting

Troubleshooting

In the Database Unload

Technical Name/Problem/Error Message Solution

Unexplained error in job log R3SETUP ended abnormally. No other error messages.

Log off and log on again before restarting R3SETUP.

DbSl returns error SQL0104 (RC=-104) Invalid token

DLTR3PKG and then restart R3SETUP

Message CPD0012: characters in qualifier beginning W-nnnnnnnn not valid

Messages may be ignored if no other errors are reported in the unload.

DB4CPC_DBEXPORTINSTANCE_OS4_DB4 Message: Name Db4CodePageConv not known to registry

Incorrect version of R3SETUP is being used. Possibly an old version is being used due to an incorrect library list or else the latest patches for the EBCDIC versions of R3SETUP, R3LDCTL and R3LOAD have not been downloaded from the SAP Service Marketplace.

DB4CPC_TCPDBCHECK_OS4_IND More than one code page defined in table TCPDB

Fields CPTRANSFLD and CPPOOLCLUS must contain the same valid code page value. There should be only one entry.

DB4CPC_TCPDBCHECK_OS4_IND Conversion of code page xxxxx not supported by SAP

Only code pages 0120, 0410, 0500, 0610, 0700, 0800 and 0860 are supported.

DB4CPC_R3LDCTL_OS4_DB4 Message: Invalid or incomplete option “-o” for /sapmnt/<sid>/exe/R3ldctldb4 –o

Incorrect version of R3LDCTL is being used. Probable cause: the latest patches for the EBCDIC versions of R3LDCTL and R3LOAD have not been downloaded from the SAP Service Marketplace.

DB4CPC_TR_DBEXPR3LOADEXEC_OS4_DB4

R3LOAD jobs fail with the following message: Permission denied when copying the .STR files.

Problem only occurs with V5R2. User <sid>OFR was not used for the export processing. To work around the problem: give user <sid>OFR temporary *ALLOBJ authorization. Once the export processing is complete, the *ALLOBJ authorization should be revoked.

DB4CPC_DBEXPR3LOADEXEC_OS4_DB4 QCM tables exist in the nametab but not on the database. For possible reasons, see Note 9385.

Check the situation using the following SELECTs to compare, then delete the relevant entries from SAPAPPL1_n.STR. SELECT * FROM R3<sid>DATA/DDNTT WHERE TABNAME LIKE ‘QCM%’ SELECT * FROM R3<sid>DATA/DDNTF WHERE TABNAME LIKE ‘QCM%’

June 2004 2–13

R3load In-Place Procedure on iSeries SAP AG Troubleshooting

In the Database Load


Unexplained error in job log R3SETUP ended abnormally. No other error messages.

Log off and log on again before restarting R3SETUP.

DbSl returns error SQL0104 (RC=-104) Invalid token

DLTR3PKG and then restart R3SETUP

DB4CPC_CENTRDBINSTANCE_OS4_DB4ASCII Message: Name Db4CodePageConv not known to registry

Incorrect version of R3SETUP is being used. Possibly an old version is being used due to an incorrect library list.

DB4CREATELOCALE_IND_DB4ASCII Message: Locale xx_xx_Isnn using ccsid 500 failed to create into R3<sid>400

Install Extended NLS Support (Licpgm. 5769SS1 Product Option 21)

DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII CHGPF for the CCSID fails due to existence of a CCSID mod. flag on some individual column(s) of the database._DB4ASCII

Create a message in SAPNet – R/3 Frontend in component BC-INS-AS4.

DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII Power cut or similar during the R3LOAD processing may leave tables inconsistent, even though the restart appears to have worked correctly.

Check if any tables with names of the format ‘xxxx&’ still exist after completion of the R3LOAD processing: SELECT * FROM R3<sid>DATA/SYSTABLES WHERE TABLE_NAME LIKE ‘%&’

Use CPYF to complete the processing for any affected tables: CPYF FROMFILE(“xxxx&”) TOFILE(“xxxx”) MBROPT(*ADD) FMTOPT(*MAP)

DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII SAP* log files contain SQL –906 errors from DbSl. The R3LOAD joblog has MCH3203 with error code 1720,error class 0

Reorganize the affected file and increase the maximum access path size to 1 TB, as follows: RGZPFM FILE(R3<sid>DATA/xxxxx) CHGPF FILE(R3<sid>DATA/xxxxx) ACCPTHSIZ(*MAX1TB)

DB4CPC_DBR3LOADEXEC_OS4_DB4ASCII Message: SQL0603 ‘Unique index cannot be created because of duplicate keys’ during creation of primary key

For any table names beginning with QCM*, the error can be circumvented by clearing the table using CLRPFM. Any other table name should first be reported to SAP via a problem report in the SAPNet –R/3 Frontend, component BC-INS-AS4

DB4CPC_TCPDBENTRY_OS4_IND

Error 250: unable to change code page table TCPDB

Investigate the job log for additional messages. If you cannot solve the problem, create a message in SAPNet – R/3 Frontend in component BC-INS-AS4.

2–14 June 2004

SAP AG R3load In-Place Procedure on iSeries Troubleshooting


Error 251: In-place conversion only allowed for code page 0120

Use the Export/Import procedure.


Error 252: invalid parameter Correct the parameter in error.


Error 253: conversion of code page xxxxx not supported by SAP

Only code pages 0120, 0410, 0500, 0610, 0700, 0800 and 0860 are supported


Error 254: invalid entry in table TCPDB

Fields CPTRANSFLD and CPPOOLCLUS must contain the same valid code page value.


Error 255: unable to retrieve current code page from TCPDB

To ensure the correct system environment, you must log off and then log on again between the unload and the reload steps.

DBR3LICSTANDALONE_IND_DB4ASCII

SAPLICENSE exited with unsuccessful code of 254

In R3<sid>DATA, delete first the LF MLIC0001 and then the PF MLICHECK and restart R3SETUP.

RFCRDDGENMC_IND_IND

Error RFC_IOS Connect to SAP Gateway failed

Check the value of GWSERV in the error message. It should be sapgwnn where nn = the instance you are installing. If nn is not correct, then you entered it incorrectly in the template and you need to check the values of the variables SAPCISYSNR and SAPSYSNR in the template and to change them manually, as necessary, before restarting R3SETUP.

RFCRDDGENMC_IND_IND RFCRSBTCUPD_IND_IND

Lock wait (LCKW) problems during the running of these reports. ABAPs are being generated during the start of the SAP System and this conflicts with the run requests in these steps.

Use WRKACTJOB to investigate the situation. “Kill” all but one of the affected work processes, allowing them to restart normally. After this, the problem is normally solved, as the SAP System will have performed its COMMITs by then. You can then restart the procedure if necessary.

RFCRSBTCUPD_IND_IND

The DDIC password is repeatedly requested, even though it was changed to the original system default when the system was prepared for conversion and also entered correctly as a response to the request.

Customer has V5R2 but has not applied the latest kernel patch for the ASCII kernel and is therefore running with the version of the kernel from the conversion CD, which is not certified for V5R2. Apply the latest ASCII kernel patch from the SAP Service Marketplace : http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000018554&

June 2004 2–15

R3load In-Place Procedure on iSeries SAP AG Troubleshooting

Problems During Post-Processing


Error CPF327B: File xxxxx information cannot be retrieved with reason code 4 when performing a backup or DSPFD

Delete the affected file on the database and then recreate it using transaction SE11.

Table change logs (if in use) are corrupt after the code page conversion

Implement Note 513839.

Transaction PFCG Role authorizations show inconsistent or incorrect information after the code page conversion.

Implement Note 535554.

Transaction SICK

Error message “OS release OS/400 V5R2 M0 730 is not supported with this kernel (46D)”

Apply the latest ASCII kernel patch from the SAP Service Marketplace : http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000018554&

Transaction SM59

RFC tasks get logon errors after the conversion See note 411019. Check RFC destinations and recreate RFC passwords.

Missing texts and/or nodes in Area Menus. Run report BMEN_CORRMEN1, as described in note 316313

SQL0303 errors caused by inconsistencies between DDIC and database field definitions

Run the ABAP report RUTMSJOB in order to find out how many tables are affected and then use the procedure described in note 211492 to fix them.

2–16 June 2004

SAP AG General Subsequent Actions Contents

Chapter 3: General Subsequent Actions

Contents

Subsequent Technical Actions ............................................................................................3–2 Subsequent Actions Required on the ASCII System.........................................................3–2

June 2004 3–1

General Subsequent Actions SAP AG Subsequent Technical Actions

Subsequent Technical Actions

Subsequent Actions Required on the ASCII System

Actions on Operating System Level

• Adapt the configuration files on operating system level to meet network and SAP requirements.

• Adapt additional software components, for example, RFC, CPIC, SAP ArchiveLink, if required.

• If High Availability Software synchronization was turned off during the code page conversion, then the synchronization should be restarted.

• Ensure that the default profile contains the following specification : abap/import_char_conversion = 2

This will prevent the occurrence of problems in connection with SAPScript on 3-tier systems where the application servers are not on iSeries. Even if you have no immediate plans to use 3-tier it is advisable to set this value to prevent problems later.

• The following steps enable use of the Windows 2000 Application Server after the code page conversion. Even if you have no immediate plans you should perform them :

1. Logon as a user with QSECOFR authorizations

2. CALL R3<sid>400/R3INLPGM - add the kernel to your library list

3. CALL CRTSAPSHR - create the sapmnt and saptext NetBIOS shares

4. CRTSAPUSR USER(*ADM) SID(<sid>) - create the <sid>ADM user for the system

5. MKDIR ‘/sapmnt/<sid>/exe/run_nt’ – add the global patch update directory

• Run CRTSAPLCL for each additional code page that will be used in your system after the conversion. This is necessary to avoid the TEXTENV_INVALID condition when logging on after implementing a new language in an MDMP environment.

• CRTSAPLCL is also necessary in a 3-tier environment. It should be run for each individual application server, as the locales will not be contained in the application server kernel.

Actions on Database Level

If you access SAP tables via operating system utilities or your own programs, then you should investigate the use of the commands CRTSAPLF and CRTSAPVIEW for accessing ASCII/UNICODE databases via the operating system. These commands are described in note 554792.Actions on SAP System Level

• If you modified user DDIC prior to the database export to avoid R3SETUP’s password request, then log on to DDIC in client 000 to reset the password. The modified password setting is 19920706.

• Run installation check: Tools → Administration → Administration → Installation Check (transaction SICK).

3–2 June 2004

SAP AG General Subsequent Actions Subsequent Technical Actions

• Delete the SAPscript loads as described in note 6873

• Delete canceled and finished jobs. Execute program RSBTCDEL for all users and jobs (User and Job Name = ‘*’), marking the field delete with forced mode: Tools → ABAP Workbench → ABAP Editor (SE38).

• Reschedule your cancelled jobs using report BTCTRNS2.

• Adapt all jobs needed in the target system: 1. Copy the old jobs 2. Modify the new jobs 3. Delete the old jobs.

• Regenerate the ABAP loads, as described in Note 419990 (point 6), to ensure consistency between the generated loads and their corresponding sources.

• Check the consistency of the Temporary Sequential Objects (TemSe) (“Are there files of TemSe objects for which no TemSe objects exist?”): Tools → CCMS → Spool → TemSe administration (SP12). For more information, see SAP Note 16875.

• Adapt the definition of the printers (device types and character set definitions) to meet the new system requirements.

• Adapt the RFC destination: Tools → Administration → Administration → Network → RFC destinations (SM59). Clean the transactional RFC: Tools → Administration → Monitor → Transactional RFC (SM58). See the relevant description in the SAP Online Documentation.

• Make sure that RFC passwords are correct, as described in note 411019.

• Always regenerate system profiles using transaction RZ10 and check subsequently that they have CCSID 819 and not 500. Do this as follows :

− Import the profile using RZ10

− Delete or rename the old profile in IFS

− Save and activate the profile in RZ10. The new version should have CCSID 819 when you check it with WRKLNK option 8

• Run Report BMEN_CORRMEN1 to reset all menu buffers. This will prevent problems with the Easy Access menus.

• Adapt other CCMS settings, for example, alert thresholds, if required.

The following programs should be run to ensure that known problems with binary data in character fields are avoided :

DB4_APQD - correct table APQD

DB4_DDSHPVALUE - correct table DDSHP

DB4_DDSHHVALUE - correct table DDSHH

June 2004 3–3

General Subsequent Actions SAP AG Subsequent Technical Actions

This program need not be run if the conversion is being performed at 4.6B, as the table does not exist.

Caution

These three reports may only ever be run once !! A second run will destroy data which has already been converted.

If the tables are too big, however, the reports will abort before an update has been performed. In this case the report may be rerun after steps have been taken to reduce the table size. In case of doubt, open a report in the SAPNet – R/3 Frontend under component BC-INS-AS4.

DB4_CVT_EBCDIC_LISTS - convert EBCDIC listings (note 600755)

DB4_RESTORE_SOC3 - import SOC3 after conversion (note 603153)

The following programs should only be run if the customer has the HR Recruitment component implemented (PA-RC). See note 647583

DB4_RPAP_IL_AFTER_CONVERSION - applicant letters (Cluster AL)

DB4_RPAP_NOTES_AFTER_CONV - for notes (Cluster AN)

• Make data archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) accessible in the ASCII system. Adapt the file residence information in the ASCII system. Refer to the SAP Online Documentation (Basis Components → System Administration → Application Data Archiving and Reorganization) for help.

Checking the ASCII System

The following actions are suitable for checking the consistency of the ASCII system:

• Call transaction STMS to set up the Transport Management System.

• Check the system log (SM21).

• Non-SAP BW/SEM Systems: Check the consistency of the database (DB02) and compare with the consistency check that you ran prior to the in-place conversion.

• Perform server check (SM51).

• Test transactions frequently used by the customer.

3–4 June 2004

SAP AG General Subsequent Actions Subsequent Technical Actions

• FI customers: Run the job SAPF190 (accounting reconciliation) and compare the results to those gained on the source system before the code page conversion (Accounting → Financial Accounting → General ledger → Periodic Processing → Closing → Check/count → Comparison).

• FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet), RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset retirements) and compare the results to those gained on the source system before the code page conversion.

• CO customers: Run the report group 1SIP and compare the results to those gained on the source system before the code page conversion.

• CO customers: Use transaction GR55 (Execute Report Group) to regenerate all report groups

SAP BW customers: Run the report SAP_BW_MIGRATION, specifying parameter Index Model Tables (P4_DMTAB), to activate missing indices for a number of model tables. This only takes a few seconds.

June 2004 3–5

ebcdic to ascii conversion

Documents