SAP Basis Tech Supports

Symptom
Issues which may occur with operating system release IBM i 6.1 will be collected together in this note
1. The first operation on an SAP system after upgrading the operating sytem to V6R1M0 encounters a significant delay of several minutes.2. Message CPF32A6 “Cross-reference notification 2024 for request 514, problem type 1″ after the upgrade to V6R1M0.3. Problems with the memory-based database monitor (transactions ST04, DB4COCKPIT) after the upgrade to IBM i 6.1, for example message CPF9898 “DATABASE MONITOR HAS BEEN HALTED AND MUST BE CLEARED”.4. SQL0104 on export and import for SQL statements which contain the field name CLIENT.5. SQL0356 when installing usage type “Java Development Infrastructure”6. SAP Patches cannot be applied with command APYR3FIX between machines on 6.1. and those on older OP system levels.7. 4.6D-EXT: System fails to come up after upgrade to IBM i 6.1. DISP joblog displays the message:MCH0609, “Space address is not a teraspace storage address”.8. Installation or upgrade fails while adding entries into the Services table, or after installation the system will not start with error: NiPGetServByName2: service ’sapms<SID>’ not found: getservbyname_r9. The SAP system does not start. All work processes die and in the joblogs there is an MCH3601 from program QXDAEVT.10. If a first installation of an SAP system is attempted directly after a new operating system installation, then the R3GROUP user is set up with insufficient authorisation, which can lead to MCH1001 messages from CRTR3SYS at a later point in the installation.11. CHKR3PTF shows a missing PTF for product 5761JV1, which can only be applied after installation of option 13 of this product.12. Procedures and programs which use the CALLCMD-interface or RUNRMTCMD abort with an MCH0601 message in module QNMRCPP1.13. Very high CPU utilisation, often accompanied by many SQL0913 and CPF5027 messages indicating deadlock situations.14. SAP system fails to start after upgrading to 6.1, returning MCH3203 messages, if the system journals IFS files.15. After the OS upgrade, some OS APIs need execute access for user R3GROUP. Otherwise some SAP programs will fail.16. After implementation of the Hiper-Fixpack 29, SAP systems start begin to display problems in the PASE area. Work-process loops can occur and LICLogs indicating problems with the PASE loader (major code 0200) are created.17. SQL0331/SQL0000 in the OS-Joblog with SQL0904 and Reason code = 1 in the dev-trace only.
Other terms
AS/400, OS/400, i5/os, IBM i, OS upgrade, V6R1M0, V6R1, STROBJCVN
Reason and Prerequisites
1. When restoring programs onto IBM i 6.1 that were compiled for earlier releases, the programs need to be converted. This can be done manually by using the STROBJCVN, otherwise the conversion will take place automatically at first touch. The conversion is only needed for program objects in libraries, executables in the integrated file system (using the PASE runtime) are not affected. Internal tests have shown conversiontimes of 30 minutes for a 4.6D kernel library and 2 minutes for a 7.10 kernel.
Notethat also conversion of Java programs that correspond to classes, jars and names of an existing Java application in the integrated file system can lead to significant conversion time.2. In some rare cases the system cross-reference files can be corrupted during the upgrade to IBM i 6.1. This problem has been fixed by IBM with PTF SI29811, but the PTF is not included in some early shipments of IBM i 6.1. Installing the PTF after the upgrade to IBM i 6.1 does not solve problem.3. The memory-based database monitor is no longer supported in IBM i 6.1. Instead of it, the SQE Plan Cache dump must be used. The kernel patch levels that are required to support IBM i 6.1 ensure that the SQE Plan Cache dump is used as default.4. Please refer to note1134188for details.5. Please refer to note1138824for details.6. Please refer to note1167276for details. If possible, this note should be applied before upgrading to 6.1.7. Incompatibility with release 6.1 of the operating system in some new semaphore processing.8. The problem’s general symptom is that entries recently added to the services table are not found by APIs such as getservbyport, getservbyname and other similar APIs.9. Incompatibility caused by new processing introduced in the latest DB-Fixpack.10. Change to the *PUBLIC authorisation of some APIs.11. Option 13 of product 5761JV1 is now a prerequisite for running SAP NetWeaver Java stacks.12. Incorrect length specified for ip-Address during host name resolution.13. Loop in QSQCLOSE14. PASE signal SIGILL (for exception message MCH3203) occurs for an attempt to memory-map (mmap or shmat) an IFS file that is journalled.15. Change in the authorisation of some APIs.16. The PTF MF45977, included in the Hiper-Fixpack, causes the problem.17. SQL package corruption on double-byte character systems
Solution
General remark: In order to avoid problems with IBM i 6.1, the following patches must be applied:
| 4.6D | 6.40 | 7.00 | 7.10
—————-+——+——+——+——
APYR3FIX | 3 | 8 | 5 | -
APYR3KRN | – | 11 | – | -
AS4FIXFILE | 2 | 2 | 1 | -
AS4RMTCCMS | 5 | 12 | 7 | -
DBSLDB4RMT | 2 | – | – | -
disp+work (DW) | 2410 | 224 | 150 | 94
ILE | – | – | – | 11
JDBCEXIT | – | 3 | 2 | -
LIB_DBSL | 2380 | 231 | 149 | 94
LODR3KRN | 1 | 2 | – | -
LODSAPKRN | – | – | 8 | -
R3trans | 2367 | 216 | 144 | 84
tp | 2366 | 232 | 145 | 100
When using Java, the following levels of Software Deployment Tools are required:
6.40: SAP J2EE Engine 6.40: SP227.00: SAP SOFTWARE DELIVERY MANAGER 7.00: SP167.10: SP7
Note:SAP releases 4.5B and earlier are not supported to run with operating system release IBM i 6.1.
Solutions for the previously described issues:

1. SAP has provided changes to the kernel patch tools, so that the necessary conversion of program objects takes place when loading the kernel, but not at first touch. Details are explained in SAP Note 1117101. If you upgrade your kernels prior to the upgrade to IBM i 6.1, you should run the STROBJCVN command for all kernel libraries on your system right after the upgrade in order to avoid delays when starting SAP instances.
Note: You can avoid conversion of the mentioned Java objects by switching from Classic Java technology to IBM Technology for Java (IT4J) with your upgrade to IBM i 6.1. In order to do so ensure the following:IT4J is installed.The respective SAP Netweaver application servers have been reconfigured to use IT4J 1.4.2 (see note 1161275 for details).DoNOTrun STROBJCVN against the entire IFS.Do run STROBJCVN against the directory trees for any Java applications that will continue to use the Classic JVM.2. If you experience the problem, you need to run RCLSTG SELECT(*DBXREF) in order to fix the system cross reference files. The system needs to be in restricted state to run that command. To find out whether you have run into the problem, enter GO LICPGM and select option 5 “Prepare for install”. Select the option “Verify system objects”. If the final message is “Task to prepare for install successfully completed” (CPC3D8A), you do not need to perform the RCLSTG.3. Details about using the SQE Plan Cache dump can be found in SAP Note 1083218. If you cannot install the patch levels that are listed in that SAP Note, ensure that profile parameter as4/dbmon/enable = 0 is set. If you are running a Java instance, the profile parameter must be set in the Default profile.4. The problem has been solved by means of the patches to R3TRANS and TP which are mentioned in the table above.5. The problem has been solved by implementation of the support packages listed above for the Software Deployment Tools.6. The problem is solved with the APYR3FIX patch levels listed in the table above.7. The problem is solved with the 4.6D DW patch level listed in the table above.8. This problem is solved by applying PTF MF45089. An IPL is also necessary, therefore make sure the PTF is already applied in the system before starting any installation.9. Please ensure that the following PTFs have been installed, in order to avoid both the original error and others which were encountered in the course of the problem’s solution:latest CUM tapelatest DB-Fixpacklatest Hiper-Fixpacklatest PASE PTFsSI32551 and SI32608, if not included in the above packages yet.10. See note 175852 for the solution.11. Install the IBM IT4J JDK on your system. This is done by installing option 13 of licensed program 5761JV1. If this is not part of your IBM i OS installation media, you can order it by ordering PTF SI32444. After the product option is installed, you can install the missing PTFs for a successful CHKR3PTF. If a Java system is not installed, then you can simply ignore the message from CHKR3PTF for this PTF, if you wish, as the product is not required for non-Java systems.12. Install the latest Infoapar. This will include PTF SI33647, which solves this problem.13. Problem is solved by PTF SI33791 which has been superseded by SI33900. The PTFs will be included in the next Infoapar.14. Problem is solved by PTF MF46062, which also solves a problem with CORE file sizes.15. See note 175852 for the solution.16. Do not install Hiper-Fixpack 29. The latest Hiper-Fixpack (30) does not include the problem PTF. If Hiper-Fixpack 29 has already been installed then remove the PTF MF45977 or install the superseding PTF MF46393, when it becomes available.17. The problem is solved with PTF SI35069.