Skip to Content
0

OS release OS400 2 7 00100004604T is not supported with this kernel (741)

Nov 16, 2017 at 04:31 PM

141

avatar image
Former Member

We were in AS/400 V7R1 and have recently upgraded to V7R2. According to PAM, our Kernel 7.41 should still work for V7R2. Why then are we receiving this error when logged into the system: "OS release OS400 2 7 00100004604T is not supported with this kernel (741)".

We are currently in 7.41 Non-Unicode 64 bit.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Christian Bartels Nov 21, 2017 at 08:55 AM
1

Hi Cristina,

trace file dev_rd indicates a signal 6 in sapgenuuid(). With that, I've found SAP Note 2288677, which suggests to install the latest patch for SAP Host Agent (current patch level for release 7.21 is 31) as it provides API sapgenuuid for kernel releases 7.42 and higher.

Kind regards,

Christian Bartels.

Share
10 |10000 characters needed characters left characters exceeded
Matt Fraser
Nov 16, 2017 at 05:32 PM
0

Hi Cristina,

I added a couple tags to your question to help increase visibility. As this is an operating system question at its core, adding a tag for your OS (or DB platform) would be best. I added "IBM z/OS," but I'm not an expert with IBM systems, so it may be that a different tag is more appropriate.

You are correct in that the PAM says that for OS/400 V7R2 the Kernel 7.41 Non-Unicode should still work. However, kernel 7.41 has been out of maintenance for a couple years now. You should seriously consider updating to kernel 7.49, or at least 7.45. The PAM indicates that 7.49 remains downward-compatible with V7R2, so that shouldn't be an issue.

I would also draw your attention to Note 1969546 (Release Roadmap for Kernel 74x and 75x), which draws out minimum kernel releases based upon your NetWeaver Support Pack level. For instance, if you are running NetWeaver 7.4 and have Basis SP 8 or higher, you must be on at least kernel 7.42.

It would also help if you could let everyone know what your NetWeaver release is (I assumed for the moment that you're on 7.4), and your Support Package Stack level (or at least, SAP_BASIS sp level, assuming this is an ABAP system).

Cheers,
Matt

Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Thanks, Matt. We've found SAP Note 68440 - IBM i: How do I upgrade to a later OS release? wherein we've found out that Patch Level should be at least 31 for Kernel 7.41 and we are in Patch 26 only. Right now, we've performed Kernel Upgrade to 7.49 Patch 301. Unfortunately, our SAP System is not starting up after the activity. Gateway stopped eventually after execution of start commands. Kindly see the attached dev_disp and dev_rd logs for reference. May we know what could be the possible cause of this? Dispatcher and Gateway Components are in the same version upon checking.

dev-disp.txt dev-rd.txt

dev-disp.txt (186.7 kB)
dev-rd.txt (7.1 kB)
0

Hi Cristina,

First, an FYI about notifications in the SAP Community. It's sort of a quirk, but notifications are only sent for replies directly to the recipient's message. In other words, you received a notification when I "answered" your question, because that answer was a reply to the question. Likewise, you should receive a notification for this "comment" on your answer above, because it's a reply to your answer. However, I did not receive a notification when you "answered" your own question (above), because your "answer" is not a reply to my "answer." For me to receive such a notification, it would have to have been a "comment" made directly to my answer. I know, it's weird, and a lot of people don't like how this works. It confuses many people and causes many missed notifications. There are suggestions in the works to improve upon this in the future.

I looked through your dispatcher and gateway logs, and didn't immediately see any obvious issues. One thing that happens sometimes when upgrading a kernel on Windows systems is that it takes a double restart for it to work the first time. I.e., with the first system start after replacing the kernel, it doesn't work fully -- it gets about halfway there. So, do a normal shutdown and normal restart after this, and the second time (and all future times) it should work fine. This doesn't always happen, but it's fairly common. Even if the system seems to start properly after a kernel update, it's a good practice to do a clean shutdown and restart again, after all the patches have been distributed to all the application servers. I don't know if this is ever a problem on IBM systems, but it wouldn't hurt to give it another restart just to be sure.

Otherwise, I'm aware that replacing a kernel on OS/400 is not as simple as it is in Windows, and that you have to run various commands and processes at the OS level. I assume you're familiar with all this, and with Note 1632755 (IBM i: Description of command APYSIDKRN).

The other Notes I would highlight, though I'm sure you've already found them, are 2514637 (SAP Support Package Stack Kernel 7.49 Patch Level 301) and 2514778 (Known regressions in kernel 7.49 patch level 301). I also note that patch 400 has just been released today, and the various patch notes are available in the download section, but the main note for this patch level is still being worked on. I don't think you need to update to this, however -- we run patch 301 ourselves without any problems (though admittedly not on IBM i).

It may still be helpful for those trying to help you if you indicate what your NetWeaver release is and what your SAP_BASIS support pack level is.

Cheers,
Matt

0
Former Member

Thanks for this FYI, Matt. SAP Host Agent Upgrade resolved our startup issue. However, we encountered CONVT_OVERFLOW upon execution of ST06 after the OS Upgrade to V7R2. May we know if you have any idea how to resolve this? We are on SAP Netweaver 7.4 SAP_BASIS SP Level 6.

0
avatar image
Former Member Nov 22, 2017 at 03:21 AM
0

Thanks, All. We found SAP Note 2537239 also and proceeded in upgrading SAP Host Agent which resolves the issue in startup. Right now, we are experiencing CONVT_OVERFLOW dump upon execution of ST06 after the said Kernel Upgrade as seen on the attached file. May we know how can this be resolved?

convt-overflow.txt


convt-overflow.txt (12.7 kB)
Show 3 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Upon checking, it seems that CONVT_OVERFLOW dump was not caused by the Kernel Upgrade 749 Patch 301 as we have one system which was not upgraded yet and encountered the same dump upon execution of ST06. It probably caused by the OS Upgrade from V7R1 to V7R2. May we know how can this be resolved?

0
Former Member

We are on SAP Netweaver 7.4 SAP_BASIS SP Level 6 by the way.

0

This sounds like the problem that is described in SAP Note 2338102 - ST06: Runtime error CONVT_OVERFLOW when calling transaction. The solution was provided in SAP NetWeaver 7.40 SP16, but there are also correction instructions available that are attached to the SAP Note.

Kind regards,

Christian Bartels.

1
avatar image
Former Member Nov 21, 2017 at 09:30 AM
0

Hi Cristina,

Based on the error in dev_rd regarding signal 6 , please see note #2537239 - IBM i : Signal 6 encountered: sapgenuuid()

to resolve the issue.

The entries in the dev_rd can be seen as:

Signal 6 encountered.
=> 64 bit R/3 Kernel
=> 64 bit OS400 Kernel

sapgenuuid() at 0x1000de54c
	pfget_uuid() at 0x10064f698
	pfcreate_sap_uuid_force() at 0x10064f13c
	GwInitReader__FiPPc() at 0x1000022c0
	main() at 0x100000908


Regards,

Manjunath Hanmantgad
Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member
0