IBM i: Overwriting when determining communication data
[AS/400] [Communication] [determining] [i] [i5/OS] [iSeries] [just communication] [OS400] [overwriting] [System]
- 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: Missing replacement of R3INLPGM in R3
400 Symptom 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: 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: Changing a table with an Encoded Vector Index (EVI)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...
- 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...
- 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...
Symptom
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 the communication data, an internal memory is created that is too small. If this internal memory is filled gradually during the runtime of SAPOSCOL, the system writes data beyond the end of the buffer. The following buffer is destroyed as a result, and the program SAPOSCOL terminates with a dump.
Solution
CAUTION: The corrections consist of two parts, both of which must be implemented. If you imported only one package, terminations may still occur due to different views of the buffer from both program parts.
Apply the following patches with at least the patch levels specified below:
SAP Release 640: SAPOSCOL patch level 100 and DW patch level 293
SAP Release 700: SAPOSCOL patch level 75 and DW patch level 151
SAP Release 701: SAPOSCOL patch level 18 and ILE patch level 53
SAP Release 710: SAPOSCOL patch level 36 and ILE patch level 161
SAP Release 711: SAPOSCOL patch level 12 and ILE patch level 48