IBM i: Checking already completed child processes
[aq tm processes] [AS/400] [business processes] [i] [i5/OS] [iSeries] [no more processes] [OS400] [processes] [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: 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 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
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 Prerequisites
When the instance is stopped, SAPSTART sends a stop command to all jobs you started and it then checks if they are still active. SAPSTART does not notice if a job is terminated before this check, and it waits five minutes for a job (which has been completed for a long time) to end. This error was eliminated with these corrections.
Solution
Apply the following patches with at least the specified patch levels (the specification nn will soon be defined):
SAP Release 640: Patch SAPSTART with patch level 31
SAP Release 700: Patch SAPSTART with patch level 24
SAP Release 701: Patch SAPSTART with patch level 3
SAP Release 710: Patch SAPSTART with patch level 5
SAP Release 711: Patch SAPSTART with patch level 5