JSPM reports invalid kernel File

[Former Member]

Java Support Packs Stacks on SOLMAN 4.0 - Invalid Kernal File.

We are trying patch our SOLMAN 4.0 Java Stack from Current SP11 to SP13

using JSPM. We are getting this SAPEXDB Kernal error problem?

Details Messages: Kernel with Packages level SAP kernel and Version 7.00.114.0 that is located in /usr/sap/trans/EPS/in is invalid. Kernel with patch level SAP Kernel Unicode OS400_PPC64 and version 7.00.114.0 with archive names /usr/sap/trans/EPS/in/SAPEXE_114-20001357.SAR is invalid. Required archives SAPEXEDB.SAR are missing from kernel archive name set /usr/sap/trans/EPS/in/SAPEXE_114-20001357.SAR

Eventhough we have the SAPKERNEL files in the EPS/in directory it is

still sayings that file is Invalid.

These are two files we have in the EPS/in folder.

"SAPEXE_114-20001357.SAR"

"SAPEXEDB_114-20001357.SAR"

I even try renaming the SAP Kernel Director to SAPEXE.SAR and SAPEXEDB.SAR

Enviroment: OS/400-DB400 - SOLMAN 4.0 Current SP11 trying to Patch 13.

Using JSPM options Support Pack Stacks.

Please advice!

Thanks

Kumar

[Former Member]

Hi,

First why do you have .SAR files in EPS\in directory and check whether your downloaded files is datatbase dependent.

I think your are not updating the kernel so use JSPM and give the path of the downloaded file in JSPM it will automatically identify if it matches with your system.

Regards;

Sudhakar Manoharan

[Former Member]

Sudhakar,

Where else do you place the ".SAR" files? if you want your upgrade your Kernel patches via JSPM, I think that is where everyone puts it? correct?

Kumar

[Former Member]

look into this note 901270. Hope it will help you

[Former Member]

Hi,

Please check the OS-DB combination of the kernel which you have downloaded.

Also check whether your system is<b> unicode or non-unicode</b>.

If your system is unicode and if you are trying to patch it with a non-unicode kernel, JSPM will not identify those files. Cross check this.

It will work.

Any queries revert back

Reward points if useful.

Regards,

Nayana

[Former Member]

I hope you have all the Java Support pack files in the EPS/in directory. Why do you have the kernel *.SAR files in EPS/in directory? Are you trying to patch your kernel? If not, move those files to another directory and try the JSPM.

regards

tamilboy

[Former Member]

trying to patch them as a stack.

[Former Member]

Can you please post the contents of the sapmanifest.mf and sapmanifestdb.mf

I hope you have downloaded the correct files with repect to your OS and DB.Please verify once.

Message was edited by:

Bidwan Baruah

[Former Member]

Hi Bidwan,

here you gooo

<----sapmanifest.mf---->



Manifest-Version: 1.0

keyname: SAP_KERNEL
keyvendor: sap.com
keylocation: SAP AG

kernel os: as400_pase_64

kernel release: 700
kernel patch number: 75
compilation mode: UNICODE
compiled for: 64 BIT

patch number disp+work: 75
patch number msg_server: 73
patch number R3trans: 71
patch number tp: 75
patch number dbsl: 74
patch number gwrd: 74
patch number saplicense: 0
patch number enqt: 66
patch number icman: 74
patch number jcontrol: 0
patch number jlaunch: 0
patch number jcmon: 0
patch number vscan_rfc: 49
patch number ldap_rfc: 36



<----sapmanifestdb.mf---->

Manifest-Version: 1.0

keyname: SAP_KERNEL
keyvendor: sap.com
keylocation: SAP AG

kernel os: as400_pase_64
kernel db: db4

kernel release: 700
kernel patch number: 75
compilation mode: UNICODE
compiled for: 64 BIT

patch number disp+work: 75
patch number msg_server: 73
patch number R3trans: 71
patch number tp: 75
patch number dbsl: 74
patch number gwrd: 74
patch number saplicense: 0
patch number enqt: 66
patch number icman: 74
patch number jcontrol: 0
patch number jlaunch: 0
patch number jcmon: 0
patch number vscan_rfc: 49
patch number ldap_rfc: 36

Thanks

Kumar