cancel
Showing results for 
Search instead for 
Did you mean: 

Kernel Library Creating frequently

Former Member
0 Kudos
103

Hello,

We have what seems to be an endless stream of Kernel Library creates happening. I was led to believe that this was being done by saphostagent whenever there are changes and that performing a save of a library is treated  as a change. Hoever, we are seing multiple creates of the same libraries within the same 24 hour period.  Any ideas on what might be causing this?

This is just one of the libraries for example -

5/7/20140:01:12CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:08:26CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:15:28CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:22:25CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:28:37CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:35:41CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:42:32CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:28:37CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:35:41CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20140:42:32CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20141:03:54CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20141:11:31CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20141:19:15CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20141:26:25CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20141:34:02CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20141:42:12CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20141:49:40CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20141:57:10CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20142:05:18CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20142:13:17CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20142:20:42CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20142:28:19CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20142:34:42CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20142:42:21CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20142:48:02CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20142:53:12CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20143:00:32CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20143:09:19CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20143:19:23CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20143:29:04CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20143:36:48CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20143:44:59CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20143:51:08CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20143:57:09CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20144:03:24CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20144:14:48CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20144:19:51CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20144:24:43CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20144:29:53CO-ObjectQSYS/SAPBAPI06# type *LIB crea
5/7/20144:34:40CO-ObjectQSYS/SAPBAPI06# type *LIB crea

Thanks,

Craig

Accepted Solutions (0)

Answers (3)

Answers (3)

joachim_kern
Explorer
0 Kudos

Hi Craig,

Your joblog snipit shows two PRD events and only 1 BAP event.

In the List at the beginning of this thread the BAP recreation frequency was about every few minutes.

Now it seems that no recreation happened between 15:35 and 20:20

This means that the SAPILED works fine! The libraries PRD and BAP got new timestamps from outside.

As Volker mentioned this can be a replication tool like MIMIX. Therefore it is forbidden to include the kernel libraries in such a replication task.

Something must have changed the library timestamp of BAP and PRD at 20:20:34 respectively 20:20:46.

So could you please check, which job could be responsible for that at 20:20?

So far there is no reason to open an OSS ticket.

Best regards

Joachim

joachim_kern
Explorer
0 Kudos

Hi Craig,

Volker is right!

The code responsible for the refresh of the kernel libraries is part of the SAPHOSTAGENT package.

I f you have problems with new kernels (as 740 and 721 PL 200 implies) you probably have an outdated SAPHOSTAGENT.

So please provide the information Volker asked for and in addition please provide the joblog (or at least the last pages of it with the last iterations of the cycle) of the SAPILED Job running in SBS QUSRWRK.

Best regards,

Joachim

Former Member
0 Kudos

Hello all,

Our OS is at  version 7.1 TR7

SAPHOSTAGENT but

saphostexec -version

  • patch number                  176   

                                    

  • latest change number          1467487

I hadn't thought of looking at  PGM-SAPILED job logs but here's the last couple of pages.

Library SAPPRDIND recreated. A modification in the library was detected 

  which was not a patch result. (Last Patch time stamp is '1140511203743'

  (14E1174263); last library modification is '1140512153240'.) You can  

  temporarily disable the automatic recreation of the library on content

  change until the next official patch apply by creating *DTAARA SUPPORT

  in the library. For more information see note 1637588.                

Start update for System PRD.                                            

Job 076225/QSECOFR/SAPILEDX submitted to job queue QUSRNOMAX in library 

  QSYS.                                                                 

Library SAPPRDIND recreated. A modification in the library was detected 

  which was not a patch result. (Last Patch time stamp is '1140512153510'

  (14E1256110); last library modification is '1140512202046'.) You can  

  temporarily disable the automatic recreation of the library on content

   change until the next official patch apply by creating *DTAARA SUPPORT

   in the library. For more information see note 1637588.              

Start update for System PRD.                                           

Job 077415/QSECOFR/SAPILEDX submitted to job queue QUSRNOMAX in library

  QSYS.                                                                

Library SAPBAPIND recreated. A modification in the library was detected

  which was not a patch result. (Last Patch time stamp is '1140512141219

  (14E1251139); last library modification is '1140512202034'.) You can 

  temporarily disable the automatic recreation of the library on content

  change until the next official patch apply by creating *DTAARA SUPPORT

  in the library. For more information see note 1637588.               

Start update for System BAP.                                           

Job 077416/QSECOFR/SAPILEDX submitted to job queue QUSRNOMAX in library

  QSYS.                                                               

volker_gldenpfennig
Active Participant
0 Kudos

Hi Craig,

ok, 176 is from january ...

I would at least patch it up to 183 and see if it stays the same ...

If yes, I guess, you do have a special setting in your RSTLIB command or so. Because the "update timestamp" is always your restore ... Or do you use MIMIX or so and replicate this library ? (This would be forbitten)

If it stays the same, you need to open an OSS ticket with BC-OP-AS4.

Regards,

Volker Gueldenpfennig, consolut.gmbh

S_Sriram
Active Contributor
0 Kudos

Hi Craig

1. In which version of kernel you are getting this issue

2. Check this SAP Note   1177123 - IBM i: Reconstructing an ILE kernel library from SAR archive

BR

SS

Former Member
0 Kudos


Hello SS,

It has been happening since we upgraded to the 720 kernel. Our BI system is on the following version(from a WP trace) 

M relno      7210

M patchlevel 0

M patchno    200

M intno      20020600

M make       single threaded, Unicode, 64 bit, optimized

And our ECC is on this version (same issue here)

M relno      7400

M patchlevel 0

M patchno    46

M intno      20020600

M make       multithreaded, ASCII, 64 bit, optimized

Both systems are running in the same LPAR if there is any relation there.

BR,

Craig

former_member188883
Active Contributor
0 Kudos

Hi Craig,

Looks like the objects are created under System Library QSYS.

Could you share the steps used for performing Kernel upgrade.

Regards,

Deepak Kori

S_Sriram
Active Contributor
0 Kudos

Hi

Thanks for your info

Could you share the IBM OS/400  Version & PTF level?

Have you followed any document or note to upgrade the Kernel 721 & 740?

BR

SS

volker_gldenpfennig
Active Participant
0 Kudos

Hi Craig,

did you update the SAPHOSTAGENT as well ? This is always a requirement when patching the kernel. Otherwise, the kernels could be inconsistent to the saphostagent.

You can check the version of saphostagent in /usr/sap/hostctrl/work/dev_saphostexec

What is the patch and the date of that ?

How many objects do you have in library QRPLOBJ ?

Why are you sure, that is it not caused by saphostagent ?

Regards,

Volker Gueldenpfennig, consolut.gmbh