SAP Note 15023 - Initializing table TCPDB (RSCP0004) (EBCDIC)

Symptom:

During the installation procedure you are requested by means of this note to specify your character set.

Syslog CP2: Table TCPDB contains ... entries
-or-
In the TemSe administration, character set check, a message is issued stating that table TCPDB has not been maintained. However, the table cannot be maintained using SM31.
-or-
Syslog CP4: Table TCPDB contains ... entries, but...
-or-
The contents of table TCPDB is incorrect.
-or-
Syslog: miss: TSL1T(D,CP2):TCPDB...

Cause and prerequisites

Read Note 42305.

Solution

Read Note 42305, import report RSCPINST if you have not already done so. Then call reoport RSCPINST.

If report RSCPINST is not available and you cannot import it, read the following attachment to maintain table TCPDB. However, this procedure is not recommended.

================================ Attachment =========================
Run report RSCP0004. Its screen list contains the explanations, and you can trigger the necessary actions by double-clicking on the appropriate lines.
Comment: Remember that EBCDIC as well as ASCII compatible character sets are supplied. On AS/400 you may only use EBCDIC character sets. On Unix and NT however, you may only use ASCII compatible character sets. (For DB2/390 only the application server of the operating system is relevant).

Comment: If TCPDB is empty, enter first the character set you have been using up to now. This way you ensure that you can continue working later on. (If TCPDB is empty the system takes the character set from profile value 'install/codepage/db/transp'.)

Note: up to and including Release 3.1G, the corresponding profile values (install/codepage/db/transp and install/codepage/db/non_transp) are more powerful, meaning that an empty or incorrectly filled table TCPBD in a productive system does not cause an error. A set of check programs are confused by this, and then report the errors.
As of Release 3.1H and 4.0A, this table directly controls the kernel. It therefore makes sense to have a correct entry as soon as possible.

What if there is something wrong in TCPDB?

The program RSCP0004 reports: "There is no offical tool for repairing this situation."
Reason: The entry was not designed to be changed. It defines how the texts in the database should be understood. If more than one incorrect TCPDB entry should be corrected, that is, the code page must be changed, the entire database must be converted.
This is the unofficial way to solve this:
+ In the OK code line, enter: "DELE"
+ Position the cursor on the incorrect entry
+ [ENTER]
+ Confirm the deletion popup
+ The next popup reports: "This is not allowed."
+ In the popup, use [F2] or a double-click to go to the specially
marked line, then
+ Repeat RSCP0004 and make the correct entries
If the table contains several entries, they must first be deleted with this program completely, and then recreated.

Instead of deleting, you may also stop the R/3 system, and delete the contents of table TCPDB with SQL means.

Several Codepages ?

In normal R/3 systems, a single selected code page is used in the database, which explains why there is only one entry in table TCPDB.
If you want to use a MDMP system (several code pages within one single system) refer to Note 73606.

Additional key words

RSCP0004, MDMP, TCPDB, RSCP0001, TSL1T, TCP0D, iSeries