Basis Errors and Solutions

IBM i: Changing a table with an Encoded Vector Index (EVI)

July 30, 2009 at 11:45 am

[AS/400] [changing table] [encoded] [i5/OS] [iSeries] [OS400] [vbscript encoded] [vector]

IBM i: Standalone installation of CCMS agentSymptom You use the CCMS agent SAPCCMSR to transfer data about the system status from a server to a central monitoring system. This note describes how you can install the CCMS agent...
IBM i: Error when starting a remote instanceSymptom If you want to stop a remote instance from the central instance host, the command STOPSAP has no effect. Other terms AS/400, OS400, system i, i5/OS, iSeries Reason and Prerequisites This...
IBM i: Checking already completed child processesSymptom Terminating an SAP system takes longer than usual. Sometimes only the job SAPSTART is active in the subsystem without being terminated. Other terms AS/400, OS400, system i, i5/OS, iSeries Reason and...
IBM i: Overwriting when determining communication dataSymptom SAPOSCOL ends due to a termination, and MCH3601 is displayed in the function AiUpCall in the job log. Other terms AS/400, OS400, system i, i5/OS, iSeries Reason and Prerequisites When determining...
IBM i: Missing replacement of R3INLPGM in R3400Symptom When you apply a patch, the program R3INLPGM in the library R3400 should be replaced automatically. However, this does not occur. Other terms AS/400, OS400, system i, i5/OS, iSeries Reason and...
IBM i:Expression operator not allowed for parameter INSTHOSTSymptom Installation fails in step createInstanceOS4 due to problem with command CRTR3INST when using a hostname containing special characters. Other terms OS/400, AS/400, install, SAPinst, AS/400, iSeries, SCS, i5, CRTR3INST Reason and...
IBM i: Java error in host names with hyphensSymptom You execute an upgrade or an installation for a Java stack. Various SAP commands (for example, STARTSAP, STOPSAP) require the host name of your IBM i as a parameter. Other terms...
IBM i: IT4J: Xlp64k is not supported by some processorsSymptom After the conversion of your SAP NetWeaver system to IT4J using CONFIGJVM, the system no longer starts. The Java processes terminate, and the system issues the following message: JVMJ9GC032E System configuration...

Symptom

Changing a table for which there is an Encoded Vector Index (EVI) fails, for example, when you include a dimension in an InfoCube. Apart from the following information in the developer trace, there is practically no error message:
M *** ERROR => AS400_API (APICODE 42) failed with SY-SUBRC = 4 [abas4api.c 1548]
M *** ERROR => Parameter ‘FILE’ is too short, length ‘30′ required [abas4api.c 498]

Other terms

AS/400, OS/400, iSeries, i5/OS

Reason and Prerequisites

This problem occurs with the following call in the function GET_DISTINCT_EVI_VALUES in SDB1FDB4:
CALL ‘AS400_API’
ID ‘APICODE’ FIELD API_GETFILEINFO
ID ‘FILE’ FIELD INDEXNAME
ID ‘LIBRARY’ FIELD DB_LIBNAME
ID ‘ACC_PATH’ FIELD ACCESSMETHOD
ID ‘DIST_VALUES’ FIELD DIST_VALS
ID ‘API_ERR_TEXT’ FIELD ERRORTEXT.
This error occurs because the index names in the ABAP Dictionary can only be 18 characters long, and therefore the field INDEXNAME is defined with a length of 18 characters only. However, the kernel function that is called expects a length of 30 characters.

Solution

Apply the patches specified for your release. As as result, the kernel for the parameter FILE also tolerates fields that are less than 30 characters long.

ReleasePatch level6.40disp+work Level 2927.00disp+work Level 2167.01disp+work Level 527.10disp+work Level 1617.11disp+work Level 48