SAP Basis Tech Supports

Symptom

If the objects for the secondary language do not match the current status of OS/400, various errors may occur that are very difficult to analyze. This note contains descriptions of the problems and symptoms that SAP Support are aware of, which can be traced back to this inconsistency.
You will recognize the inconsistency when you call the command DSPSWFRSC and switch to the ‘Display F11=Libraries/Releases’ view. This view lists the different releases for the objects in the different language libraries, for example:
Display Software Resources
Feature
Res.ID Option Feature Type Library Release
5722999 *BASE 5050 *CODE QSYS V5R3M0 L00
> 5722SS1 *BASE 2924 *LNG QSYS2924 V5R2M0 L00
> 5722SS1 *BASE 2978 *LNG QSYS2978 V5R2M0 L00
5722SS1 *BASE 5050 *CODE QSYS V5R3M0 L00
5722SS1 *BASE 2929 *LNG QSYS V5R3M0 L00
> 5722SS1 1 2924 *LNG QSYS2924 V5R2M0
> 5722SS1 1 2978 *LNG QSYS2978 V5R2M0

Descriptions of known problems and symptoms:
1. CPFB8ED with CRTLIB for SQL package library:
When you try to create a new library for SQL packages, the following error message appears in the job log of the work process
CPFB8ED: Device description *N not correct for operation.
with reason code 1, followed by
SAP4020: Error: CRTLIB LIB(R3Q11A2040) TEXT(’R/3 SQL packages for
system ‘) AUT(*EXCLUDE) CRTAUT(*EXCLUDE) failed.2. CPF9814 with prepare for an SQL statement:
You cannot start the system. The developer trace of the work process contains the following type of sequence:
C *** ERROR => CPF9814 occurred. Refer to job log.
[dbsldb4dbi.c 883]
C *** ERROR => Error 9998 in function db_prepare
[dbsldb4.cpp 7574]

3. CDP0162 in the job log

You cannot start the system. The job log of the sapstart process contains message CPD0162:
Parameters do not match those in program in QSYS.
4. ABAP upgrade phase OPTEXE_TRIG
The upgrade fails in the phase OPTEXE_TRIG. The following message is displayed:
‘create trigger’ failed for out of triggers which exceeds the treshhold of (parameter ‘/trigger/failed_treshhold’).
Typical entries in the following logs are:
* in OPTEXE_T.ECO:
This is /exe/tp version xxx.xx.xx (release xxx)
ERROR: Statement: CREATE TRIGGER “TR_00001I” AFTER INSERT ON “/OSP/T_BM_CTXT” BEGIN UPDATE TRIGTAB SET FLAGTRIG = ‘X’ WHERE TABNAME = ‘/OSP/T_BM_CTXT’ AND FLAGTRIG <> ‘X’; END
ERROR: SQL ERROR -901: SQL system error. MSGID=CPF0006 Job=821939/OFR/TP
* in PTTRDC00.LOG:
tp_exec_statement: CREATE TRIGGER “TR_00617U” AFTER UPDATE ON “UPP_DOC” BEGIN UPDATE TRIGTAB SET FLAGTRIG = ‘X’ WHERE TABNAME = ‘UPP_DOC’ AND FLAGTRIG <> ‘X’; END
TPERR- SQL system error. MSGID=CPF0006 Job=821939/OFR/TP
* Job log:
Receiver value too small to hold result.
Dump output directed to spooled file 952, job 821939/OFR/TP created on system on xx.xx.xx xx:xx:xx.
File QSQLSRC not created in library QTEMP.
Application error. MCH1210 unmonitored by QDDCPF at statement *N, instruction ‘00F6′. Function check.
CEE9901 unmonitored by QSQRXLTR at statement *N
In this case, the variable parts of the text may be displayed with unprintable characters or with a mix of characters.

Other terms

OS400, AS400, iSeries, secondary language, CPFB8ED, CPF9814, CPD0162

Reason and Prerequisites

The OS/400 operating system enables you to install a source language and optional secondary languages. The operating system and the additional license programs are divided into language-independent objects (for example, programs or service programs) and language-dependent objects (for example, commands, menus or message files). The language-independent objects are always stored in the QSYS library (for the operating system) or the product libraries of the license programs. The language-dependent objects are also in the QSYS library or the product libraries for the source language. For each additional language installed, a QSYS library is created where all language-dependent objects are contained for this language. stands for the four-digit IBM language code, that is, 2924 for English (single byte), for example.
To use screen displays and messages in a secondary language, the library of the secondary language (QSYS) must appear before the QSYS library in the library list of the job. You can do this using the command CHGSYSLIBL, the parameter SYSLIBLE in the subsystem descriptions, or the system value QSYSLIBL.
If, after the operating system is upgraded (with its source language), the secondary languages have not also been upgraded to the same release, the parameters in the command objects (*CMD) in the QSYS library no longer match the parameters in the program object (*PGM) of the QSYS library. This can lead to a high number of apparently inexplicable errors.

Solution

When you upgrade to a newer operating system release, make sure that all secondary languages are also updated to this new release. The secondary languages are usually provided on a separate CD.
If the problem has occurred in your system and you have the CD with the secondary languages, you can simply install the secondary languages using the command RSTLICPGM or option 21 from the menu LICPGM. If you have any problems with this installation, contact IBM Support.
If you do not have the CD with the secondary languages, you can avoid the problem temporarily either by deleting the obsolete secondary languages or by removing the QSYS library from all subsystem descriptions as well as deleting the system value QSYSLIBL. Changes in the subsystem descriptions only become affective after you terminate and start the subsystem.
For more information about secondary languages, refer to the IBM online documentation.