Note 1636252 - Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11


Header
SAP Link1636252
Version11
Release StatusReleased for Customer
Released on02.12.2011 11:51:18
PriorityRecommendations/additional info
CategoryUpgrade information
Primary ComponentBC-CST
Secondary Components

Summary
Symptom
You want to use the 7.20 or 7.20 EXT kernel as a downward-compatible kernel in one of the following NetWeaver releases
  • SAP NetWeaver 7.0 ("7.00")
  • SAP EhP1 for SAP NetWeaver 7.0 ("7.01")
  • SAP NetWeaver 7.10 ("7.10")
  • SAP EhP1 for SAP NetWeaver 7.10 ("7.11")
Other terms
7.20, 7.20 EXT, 720_EXT, AKK, DCK, Downward-Compatible Kernel
Reason and Prerequisites
Limitations
The installation of the 7.20 or 7.20 EXT kernel as a downward-compatible kernel is, until further notice, only released
  • for ABAP-only systems,
  • for 7.00 and 7.01.
Attention
  • This note is valid for all systems with Web AS Release 7.00, 7.01 (7.0 Enhancement Package 1), 7.10 and 7.11 (7.1 Enhancement Package 1) that still run with the 7.00-, 7.01-, 7.10- or 7.11 kernel that was originally delivered.
  • From Q1, 2012 on, the 7.20 kernel is normally delivered via a Support Package Stack and is then automatically active. Therefore, you should use this note only if you want to exchange the kernel manually in advance, perhaps to deal with a particular error in the old kernel.
  • You can also use the 7.20 EXT kernel as a downward-compatible kernel for the NetWeaver releases mentioned above. If you want to use the 7.20 EXT kernel, you have to download all archives from the link of the corresponding EXT branch on the SAP Service Marketplace (e.g., from link "SAP Kernel 7.20 EXT 64-BIT UC" if you look for 64-bit UC kernel ). Please notice that it is very important not to mix executables from kernel 7.20 and 7.20 EXT. It is explicitly mentioned in the text if the handling of the 7.20 EXT kernel differs from the handling of the 7.20 standard kernel.
  • You may have to perform an operating system upgrade before you upgrade the kernel, or you may have to ensure additional database-specific prerequisites before the kernel upgrade (for example, the 7.20 kernel may be supported for certain operating system releases or database releases only). In particular, this applies to SAP kernel 7.20 EXT.
    Release information is available at: http://service.sap.com/pam
Platform-Specific Information

Read the following platform-specific SAP notes:
  • MaxDB
    SAP Note 1487269.
  • MS SQL Server
    SAP Note 1341097 and SAP Note 1467086.

If you are using the 7.20 kernel as a DCK the following platform limitations are in place:
  • IBM AIX
    For AIX 5.2 the minimum Technology Level is TL10.
  • IBM DB2 UDB
    IBM DB2/UDB 8 is not supported with the 7.20 kernel.
  • IBM z/OS
    IBM z/OS 1.6, z/OS 1.7, and z/OS 1.8 are not supported with the 7.20 kernel.
  • Microsoft SQL Server
    The 7.20 kernel is intended for Microsoft SQL Server 2005 and higher. If you are still using Microsoft SQL Server 2000 refer to note 1341097. It describes how you can use a special version of the 720 DBMSSSLIB.DLL for the transition period until you upgrade to a higher SQL Server release.
  • Oracle Database
    Oracle 10.1 is not supported with the 7.20 kernel.

If you are using the 7.20 EXT kernel as a DCK the following platform specific limitations are in place (check the PAM for general information about the supported DB and OS releases):
  • AIX
    As a prerequisite for using the 7.20 EXT kernel on an AIX system, the runtime environment must have at least the following release:
    • xlC.aix61.rte 11.1.0.2
    • xlC.rte 11.1.0.2
  • IBM i
    For the 7.20 EXT kernel, the OS release must be i7.1 or higher.
  • Linux
    Before the installation of the 7.20 EXT kernel, see SAP Note 1563102.
  • Microsoft Windows
    Using the 7.20 EXT kernel on Windows requires a specific C runtime that is included in the SAPEXE.SAR archive. SAP Note 1553465 describes how to apply the C runtime to your system.
  • Oracle Database
    On all OS platforms (except IBM Power Linux and Linux IA64 (Intel Itanium), before the installation of the 7.20 EXT kernel, make sure that the following prerequisites are met:
    • The database server runs with Oracle 11.2.0.2 or higher. The latest SAP Bundle Patch needs to be applied on top of the existing patchset release.
    • Install the Oracle 11g Instant Client on all application servers and the database server as described in SAP Note 1431794: Oracle 11.2.0 Instant Client.
      The Oracle client software can be downloaded from the SAP Service Marketplace at: https://service.sap.com/oracle-download
      Please note: After the installation of the Oracle 11g Instant Client, make sure that the library path for the <sid>adm user (LIBPATH, SHLIB_PATH, LD_LIBRARY_PATH) no longer contains any references to the old Oracle 10g Instant Client location.
  • On IBM Power Linux and on Linux IA64 (Intel Itanium), only Oracle 10g is supported. For these two platforms you do not have to make any changes to your database client.

Solution
The 7.20 kernel that is delivered by SAP for Release 7.02 (7.0 Enhancement Package 2) is downward-compatible to the kernels for releases 7.00, 7.01, 7.10, and 7.11. Therefore, you can eliminate errors by replacing the kernel with a 7.20 kernel so that you do not have to perform an SAP upgrade.
Important
  • You must exchange the kernels on all servers of the affected system.
  • The general SAP recommendation to keep up to date with the upgrades remains unaffected by this downward-compatible kernel because it does not correct application errors.
  • For compatibility reasons, the 7.20 kernel is still available for certain 32-bit platforms (Windows, Linux); however, we strongly recommend that you use the 64-bit variant. The 32-bit variant is not suitable for production operation and is not supported.
    The 7.20 EXT kernel is not available in a 32-bit variant.
  • You can upgrade to the 7.20 kernel without having to install the new GUI version on the front-end PCs.
Definition of terms

Here, 'kernel' means all executable programs located in /usr/sap/<SAPSID>/SYS/exe/run (UNIX, IBM i) or \\$(SAPGLOBALHOST)\sapmnt\<SAPSID>\sys\exe\<nuc|uc>\<platform> (Windows), not just the executable disp+work.

After you have installed a 7.20 kernel, you must
  • still import the Support Packages available for your installed SAP Release to correct repository objects using Support Packages;
  • in future, when correcting the kernel using kernel patches, use 7.20 patches only.

1. Obtaining the Archives

The elements that are required for importing the kernel are available as an SAR archive on SAP Service Marketplace under "SAP Kernel". There a differentiation is made between 32-bit and 64-bit kernels and also between the character width (Unicode or non-Unicode). As a further sub-option, a differentiation is made between the platform and under this, differentiation is made between database-independent archives and (for each database supported in the platform) database-dependent archives. The name of the archive is made from a template of type <name>_<plevel>-<uid>.SAR. Here, <name> is the actual name of the archive, followed by the patch level <plevel> and a unique ID <uid> in which the bit value, the character width, the platform and the database type of the relevant archive are included again. In general, only the short form <name>.SAR is used in this note (for example, SAPEXE.SAR). For more information about the download, see Note 19466.
You should download the following archives into the same directory <newkernel>:
  • Due to the digital signature of the archives (see Note 1598550), you require the latest SAPCAR. Therefore, download the archive SAPCAR_<plevel>-<uid>.EXE from SAP Service Marketplace under the name SAPCAR (UNIX, IBM i) or sapcar.exe (Windows) into your local <newkernel> directory.
  • Download the latest 7.20 stack kernel from SAP Service Marketplace. The stack kernel consists of the database-independent archive SAPEXE.SAR and the database-dependent archive SAPEXEDB.SAR. On Oracle on Windows, you also still require the current Oracle Instant Client (see Note 998004). If you use different platforms (for example, Windows Application Server with database DB2 on IBM i), you can immediately download the stack kernel for all of the required platforms.
  • If you use the Internet Graphics Server (IGS), you must also download the archives igsexe.sar and igshelper.sar. When upgrading to kernel 7.20 or kernel 7.20 EXT you also need to upgrade the IGS installation accordingly:
    • SAP IGS 7.20 needs kernel 7.20
    • SAP IGS 7.20 EXT needs kernel 7.20 EXT
           The archive igshelper. sar contains an optional component (see SAP note 1028690) that is only available as of SAP IGS 7.20. We recommend to apply the igshelper.sar to your installation as described in SAP note 1028690 when you are upgrading to kernel 7.20 or 7.20 EXT. The igshelper.sar is operating system independent and release independent regarding SAP IGS releases newer than or equal to 7.20. You can download igshelper.sar from http://service.sap.com/patches -> "Browse Our Download Catalog" -> "SAP Frontend Components" -> "SAP IGS HELPER APPLICATIONS" -> "SAP IGS HELPER" -> "SAP IGS HELPER".
  • If you use SAPCRYPTOLIB, you must also download the  corresponding archive in accordance with SAP Note 397175.
  • For IBM i only:
    • Download the package ILE_<plevel>-<uid>.SAR with at least patch level 109 as ILE.SAR.
    • If you have already changed your SAP system to SAPJVM, you must also download one of the archives SAPJVM4 or SAPJVM5, depending on which one you currently use.
    • If you know that there are already patches on SAP Service Marketplace for the SAPEXE.SAR that is used (for example, DW), download these into the directory. So they are automatically applied with the kernel.
    • For a 7.00/7.01 ASCII based dual stack system you used to download only ASCII Packages. The ASCII package contained the UNICODE part for the SCS Instance, too. The 7.20 Kernel does not contain UNICODE parts in the ASCII Packages. Therefore you have to download the UNICODE SAPEXE package in addition.
  • For UNIX/Windows only:
    Download any additional programs (such as RFCSDK or CPICSDK) if you still want to install such programs after the kernel installation.

2. Preparations

After you have centrally compiled the required kernel components, you must stop all of the relevant processes for the system to be processed and release or delete the kernel-specific resources. To do this, carry out the following actions as the user <sapsid>adm:
    1. Stop the SAP system. (You do not need to stop the database.)
  • On UNIX or Windows:
    Stop the SAP system as usual.
  • On IBM i:
    Stop the SAP system together with sapstartsrv:
    STOPSAP INSTANCE(*ALL) STARTUPSRV(*ALL) XDNLISTEN(*YES) WAIT(*YES) ENDSBS(*YES)
    2. Stop saposcol.
  • On UNIX (Web AS release 7.0 and 7.01):
    cd /usr/sap/<SAPSID>/SYS/exe/run
    ./saposcol -k
  • On UNIX (Web AS release 7.10 and 7.11):
    cd /usr/sap/hostctrl/exe
    ./saposcol -k
  • On Windows:
    If it exists, stop the Windows service SAPOsCol and delete it using the following commands:
    net stop saposcol
    sc delete saposcol
  • On IBM i:
    CALL PGM(SAPOSCOL) PARM('-k')
    3. Stop the SAProuter.
    4. Stop sapstartsrv (this is required on UNIX and Windows only):
  • On UNIX:
    kill -2 <pid of sapstartsrv>
  • On Windows:
    Stop and deactivate (Startup Type = Disabled) the services SAP<SID>_<INSTANCE no.>.
    5. Remove any IPC objects that still exist (this is required on UNIX only):
  • cleanipc <instance no> remove

3. Installing SAPHOSTAGENT

For Releases 7.00 and 7.01 (7.0 Enhancement Package 1), you must also install the package SAPHOSTAGENT.SAR in the latest 7.20 version available (in accordance with Note 1031096). On IBM i,you must also update this to the latest version for Releases 7.10 and 7.11 (7.10 Enhancement Package 1).
Afterwards, you must delete the call of the program SAPOSCOL from all of the start profiles. (not Windows)
The SAPHOSTAGENT is available on the SAP Service Marketplace (http://service.sap.com/swdc) under following menu path: "Support Packages and Patches" -> "Browse our Download Catalog" -> "SAP Technology Components" -> "SAP HOST AGENT".
4. Importing the new kernel

Import the 7.20 kernel from the directory <newkernel> on the host of the central instance and then on all of the application servers with local executables.
4.1 On UNIX
    1. Log on as user <sapsid>adm and switch to the directory /usr/sap/<SAPSID>/SYS/exe/run.
    2. We recommend saving the old kernel before deploying the new kernel.
    Save the old kernel by creating a tar archive of the complete kernel directory using the following command:
           tar -cvf ../sapexe.tar
    3. Switch to the user root and change the owner of all files to <SAPSID>adm using the following commands:
           su - root
chown <sapsid>adm /usr/sap/<SAPSID> /SYS/exe/run/*
exit
              Important: On the operating system OS/390, you must use the command "su <user>" instead of "su - root", where <user> must have the UID 0.
    4. Delete all of the files from the kernel directory, including the subdirectories. This ensures that there are no remaining files from the earlier release, which have a different name in Release 7.20 or are in a different place in a subdirectory.
           rm -rf *
    5. Unpack the new kernel with the following commands:
           <newkernel>/SAPCAR -xvf <newkernel>/SAPEXE.SAR
<newkernel>/SAPCAR -xvf <newkernel>/SAPEXEDB.SAR
    6. Oracle only:
    Unpack the DBATools with the following command:
           <newkernel>/SAPCAR -xvf <newkernel>/DBATOOLS.SAR

Also unpack the Oracle instant client to the directory.
    7. If you use IGS, you must unpack the IGS archive using the following
    command:
           <newkernel>/SAPCAR -xvf <newkernel>/igsexe. sar
    8. To deploy the IGSHELPER archive switch to the relevant local directory /usr/sap/<SAPSID>/<INSTANCE> on every instance and execute the command:
           <newkernel>/SAPCAR -xvf <newkernel>/IGSHELPER. SAR
    9. Switch to the user root and run the shell script saproot.sh, which is available in the kernel directory.
           su - root (or su <user with UID 0> on OS/390)
cd /usr/sap/<SAPSID>/SYS/exe/run
./saproot.sh <SAPSID>
exit
    10. Delete all of the local executables on the individual instances. To do this, switch to the relevant local executable directory /usr/sap/<SAPSID>/<INSTANCE>/exe and execute
           rm -rf *
    11. Since executables from the local executable directories may already be executed for the start before sapcpe runs, start an initial copy of the executables.
           cd /usr/sap/<SAPSID>/<INSTANCE>/work
sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile>

4.2 On Windows
    1. Log on as user <sapsid>adm and switch to the global host in your kernel directory, for example: <drive>:\usr\sap\<SAPSID>\sys\exe\<uc|nuc>
    2. Rename the <platform> directory, for example <platform>.save.
    3. Create a new directory <platform> and switch to this directory.
    Unpack the new kernel from the directory <newkernel> of the downloaded archive in the specified sequence.

    Important: Do not call SAPCAR.EXE directly without specifying a path; instead, use the specified directory structure.

    <newkernel>\SAPCAR.EXE -xvf <newkernel>\SAPEXE.SAR
    <newkernel>\SAPCAR.EXE -xvf <newkernel>\SAPEXEDB.SAR
    4. Oracle only:
    Unpack the DBATools to the <platform> directory:

    <newkernel>\SAPCAR.EXE -xvf <newkernel>\DBATOOLS.SAR

    Also unpack the Oracle instant client to the <platform> directory.
    5. If you use IGS, unpack the new IGS using the following command:

    <newkernel>\SAPCAR.EXE -xvf <newkernel>\igsexe.sar
    6. Deploy the IGSHELPER.SAR archive in the instance directory of the primary application server instance and for every additional application server instance.

    For the primary application server instance and every application server instance proceed as follows:
      a) Log on to your host as user <SID>adm.
      b) Copy the IGS archive IGSHELPER.SAR to a temporary directory <TEMPDIR> of your choice (for example, c:\temp).
      c) Switch to one of the following instance directories on the:
    • primary application server instance:
      <drive>:\usr\<SAPSID>\DVEBMGS<No>
    • additional application server instance:
      <drive>:\usr\sap\<SAPSID>\D<No>
      d) Unpack the IGSHERLPER.SAR archive using the following command:
      sapcar.exe -xvf <TEMPDIR>\IGSHELPER.SAR
    7. On all instances in the directories <drive>:\usr\sap\<SAPSID>\<INSTANCE>\exe, delete all of the files (including the subdirectories).
    8. Since executables from the local executable directories may already be executed for the start before sapcpe runs, start an initial copy of the executables.
    <drive>:
    cd \usr\sap\<SAPSID>\<INSTANCE>\work
    sapcpe <drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile>
    9. Install the current C runtime library by executing vcredist_<platform>.msi in the command box (or by double-clicking this file in the Windows Explorer). Before you start the system for the first time, and if you have a distributed system environment, perform this step manually on each node where a component of the system is configured to run.
    10. Activate (Startup Type = Automatic) and start the Windows Services SAP<SID>_<INSTANCE no.> of primary application server instance and of every additional application server instance to active the new version of sapstartsrv.exe.


MSCS only:
    1. Start and Stop the clustered (A)SCS instances and the appropriate SAP services using the cluster admin tool.
    2. Update the files on all cluster nodes in the Windows\SAPCLUSTER directory with the corresponding files in the central kernel staging directory.
    3. You have to follow step 6-10 also for the ERS instances on your cluster nodes.
    Search for REPSRV.lst in all Start Profile of the ERS instances (line Start_Program_00 =)and if exists replace it with SCS.lst.
    Be sure to check if your Enqueue Replication Service is replicating again after starting the ERS instances.

4.3 On IBM i:

Log on as a QSECOFR-type user and execute the following commands or actions:
    1. Point the current directory explicitly to the downloaded archives:
    CHGCURDIR '<newkernel>'
    2. Extract the required tools from *SAVF file ILE_TOOLS in ILE.SAR by program iletools into SAP_TOOLS (*LIB) - use 'Copy & Paste' to transfer the following command to your session and execute it:
    CALL QP2SHELL PARM('/QOpenSys/usr/bin/csh' '-c' 'SAPCAR -xvf ILE.SAR iletools ILE_TOOLS;iletools')
    3. Set the authorities of the objects in SAP_TOOLS by these commands:
    ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('Y')
    ADDLIBLE  SAP_TOOLS
    FIXSAPOWN *NONE SAP_TOOLS
    4. For SAP systems with a release lower than 7.10, check the contents of the file /usr/sap/sapservices. If sapstartsrv is started under the name sapstartsrvu (/usr/sap/<sapsid>/SYS/exe/run/sapstartsrvu ...), you must change the entry so that sapstartsrv is started from the subdirectory .../uc of the previous directory in future (/usr/sap/<sapsid>/SYS/exe/run/uc/sapstartsrv ...)

Log on as <SAPSID>ADM and execute the following commands for importing the new kernel:
    1. ADDLIBLE SAP_TOOLS
    2. Check whether the environment variable CLASSICUSERCONCEPT is set by the login process (use WRKENVVAR); if it is not set, run command
    ADDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE('Y')
    3. Check that all instance- and start-profiles of the system contain the parameter DIR_CT_RUN. If missing in a 7.00/7.01 environment set it to: DIR_CT_RUN = $(DIR_EXE_ROOT)/run (for Windows instances: DIR_CT_RUN = $(DIR_EXE_ROOT)\run ); For 7.10/7.11 set it to: DIR_CT_RUN = $(DIR_EXE_ROOT)/$(OS_UNICODE)/as400_pase_64 (for Windows: DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\ntamd64 )
    4. Please remove any DLTOLDPKG call from all start profiles, because with the 7.20 Kernel DLTOLDPKG will be started by STARTSAP automatically. For further information please refer to note 1657890.
    5. Apply all archives in <newkernel> simultaneously to the system:
    APYSIDKRN SID(<SAPSID>) ARCHIVES('<newkernel>/*') SAVSAR(*NONE) MODE(*FULLY) CHGENV(*NO) UPDAPAR(*NO)
    6. Remove the SQL packages left over from using the old kernel:
    DLTR3PKG SID(<SAPSID>)

Log off and then log on again with <SAPSID>ADM. You are now in the new 7.20 environment with the kernel library SAP<sapsid>IND.
(Caution: The name of the kernel library is predefined after you import the 7.20 kernel and can no longer be freely selected.)

If you change a system with a 7.10 or 7.11(7.1 Enhancement Package 1) kernel to the 7.20 kernel and have not yet changed the user concept, use the opportunity and change it now in accordance with Note 1149318 because future upgrade or update paths require the new user concept and they can only use the faster storage management with SHM_SEGS after the changeover (see Note 808607).
5. Additional steps
5.1 CAUTION: Retroactive kernel patches

In some executables (in particular, disp+work), errors were corrected at a later date. You must apply these kernel patches in any case. These are available in SAP Support Portal (http://service.sap.com/swdc).

Read Note 19466 (Downloading SAP kernel patches) or Note 1097751 for IBM i.
5.2 Additional manual changes in Dual-Stack systems
  • You must set the following parameter in the default system profile DEFAULT.PFL:
    system/type = DS
  • In all Dnn and DVEBMGSnn instance profiles, you must set the following parameter:
    FN_JSTART = jcontrol$(FT_EXE)
  • For installing further Support Packages you have to install the latest JSPM version, at least the following JSPM version:
    Release 7.00: JSPM version SP 24.
    Release 7.01: JSPM version SP 9.
5.3 Reinstalling SAPCRYPTOLIB

If you use SAPCRYPTOLIB, reinstall it according to SAP Note 510007, step 1.
The installation procedure is also described in the SAP Help Portal, http://help.sap.com, Search Documentation for
  • "Installing the SAP Cryptographic Library on the AS ABAP"
  • "Installing the SAP Cryptographic Library on the AS Java"

(enter the search string with quotation marks), Product Type "SAP NetWeaver", Release "7.0 EHP2".

5.4 Reinstalling additional programs

If you had installed additional programs such as RFC Library, CPIC Library, and so on, you must install them again. To do this, proceed as follows:

On UNIX:
Execute the following commands as user <sapsid>adm:
    1. cd /usr/sap/<SAPSID>/SYS/exe/run
    2. <newkernel>/SAPCAR -xvf <newkernel>/<additional package>.SAR

On Windows:
Execute the following commands as user <SAPSID>ADM:
    1. CD \USR\SAP\<SAPSID>\SYS\EXE\RUN
    2. <newkernel>\SAPCAR.EXE -xvf <newkernel>\<additional package>.SAR

On IBM i:
On IBM i, you do not have to install any further programs.
5.5 Special features for the syslog (AS ABAP and Dual-Stack systems)

We recommend that you set the profile parameter
           rslg/new_layout = 9.

If no old system log file exists, this parameter must be set. See Note 1517379 for further information.
5.6 Dynamic work processes (AS ABAP and Dual-Stack systems)

The 7.20 kernel supports the dynamic increase of the number of
work processes at runtime. However, this function is not fully compatible with lower ABAP versions. To prevent errors from occurring, deactivate it by setting the following parameters:
           rdisp/wp_no_restricted = 0
rdisp/configurable_wp_no = 0
rdisp/dynamic_wp_check = FALSE
5.7 DDIC_TYPELENG_INCONSISTENT short dumps

The 7.20 kernel checks complex DDIC structures in more detail than the previous kernels. Short dumps of the type DDIC_TYPELENG_INCONSISTENT may occur, for example, when calling transaction SM66. For more detailed information about correcting these inconsistencies, see Note 1610716. You can also implement this note before changing the kernel.
5.8 Start the SAP system with the new kernel
    1. Start the SAP system.
    2. Start the SAProuter.

AS Java or Dual-Stack systems:
If the Java instance doesn't start, check if SAP note 1163719 applies.
5.9 Load format of ABAP programs

After you start the SAP system with the new kernel, the following message is displayed in the system log: 'Load format of PROGRAM not valid.'

You can ignore this message because the load format is automatically regenerated.

It is also possible to regenerate these ABAP load formats directly. For more information about this, see Notes 170039, 162991 and 155580.

Affected Releases
Software ComponentReleaseFrom ReleaseTo ReleaseAnd subsequent
KRNL32NUC7.107.207.20
KRNL32UC7.107.207.20
KRNL64NUC7.107.207.20
KRNL64UC7.107.207.20
SAP_BASIS70700701
SAP_BASIS71710711
KERNEL727.207.20
Related Notes
1632755IBM i: Description of command APYSIDKRN
1632754IBM i: Umstellung auf ein Instanz-spezifisches Verzeichnis
1629598SAP Kernel 720 will replace older kernel versions
1610716Correcting runtime objects with incorrect alignment
1598550SAPCAR: Signed archive
1597627HANA connection
1563102Linux Requirements for 7.20 EXT kernel
1553465Prerequisites for running the 720_EXT kernel on Windows
15533017.20 EXT Kernel - Usage
15533007.20 EXT Kernel - Extended Kernel Maintenance
1517379Which system log format does the 720 kernel write?
1341097MSSQL: 720 DCK, 7.0* on SQL 2000, dbmssslib_oledb.dll
1163719CCMS: Incorrect version of the JMON library
1149318User concept conversion using tool CONVUSRCPT
1078134IBM i: Distribution of ILE and PASE system components
1031096Installing Package SAPHOSTAGENT
1028690True Type Fonts delivered with IGS
808607iSeries: Memory management in a system based on PASE
684106Microsoft runtime DLLs
510007Setting up SSL on Web Application Server ABAP
397175SAP Cryptographic Software - Export control
170039Kernel upgrade 4.5A/4.5B: -> Mass generation
162991Generation tools for ABAP programs
155580Creating report loads after transport
19466Downloading SAP kernel patches


Source: http://www.saptechno.com/sap-notes.html?view=sapnote&id=1636252
Related Posts Plugin for WordPress, Blogger...