Originally posted by: SystemAdmin

Here is the output of few commands:

bootinfo -y
64

bootinfo -K
64

ls -al /unix
lrwxrwxrwx 1 root system 21 Mar 16 2007 /unix -> /usr/lib/boot/unix_mp
But according to http://www.ibm.com/developerworks/aix/library/au-dutta_cmds.html /unix should point to booted kernel. So if booted kernel is 32 bit multiprocessor one why is bootinfo -K showing it to be 64-bit?
#AIX-Forum

Originally posted by: SystemAdmin

Perhaps when the bootimage was created (bosboot), the 64-bit kernel was specified instead of the one pointed to by /unix.

Convention is to always link the kernel that is being used to /unix; AFAIK this is a manual process. Thus, it possible for bootinfo -K to return 64 eventhough /unix points to /usr/lib/boot/unix_mp.

You might also notice some messages on boot indicating that /unix does match the kernel that is loaded upon boot.
#AIX-Forum

Originally posted by: alethad

The bootinfo -y is only showing you which hardware architechture(32-bit vs 64-bit) you have. The bootinfo -K is showing you what the OS is currently running.

Which one are you supposed to be running? If your application is 32-bit it shouldn't have any problem running in the 64-bit mode unless your software vendor has a problem with it.

Just 2 cents of info for you.
Good luck.
#AIX-Forum

Originally posted by: bassemir

It would be interesting to see what the "prtconf" command shows... the 64 bit kernel?

Is it possible it was booted with the 64 bit kernel and someone changed it?

Rich
#AIX-Forum

Originally posted by: SystemAdmin

ptrconf produces the following output:

CPU Type: 64-bit
Kernel Type: 64-bit
I am not sure if somebody changed the symlink or not (because this is quite "public" machine).
Sorry but I am not too much aware of how AIX systems work. If /unix pointing to booted kernel is just a convention, than it might well be the case that somebody changed the symlink.
#AIX-Forum

Originally posted by: tony.evans

What do you get from the following commands,

ls -l /usr/lib/boot/unix*
uptime
date
ls -l /unix
bootlist -o -m normal
lsvg -l rootvg | grep boot

Message was edited by: tony.evans

Message was edited by: tony.evans
#AIX-Forum

Originally posted by: SystemAdmin

I suppose I should clarify my statement that it is a convention. There are in fact some mechanisms in the OS that rely on /unix being linked to the currently running version of the kernel. For example, if you have set any tunables then they will not be applied at boot time, see the error messages below that I get when /unix does match the kernel that I used when creating the bootimage (bosboot).

Thus, it is preferable for /unix to point to the kernel that are booting with.

System initialization completed.
Setting tunable parameters...Cannot access tunable parameters because /unix does not match the running kernel.
Cannot access tunable parameters because /unix does not match the running kernel.
Cannot access tunable parameters because /unix does not match the running kernel.
Cannot access tunable parameters because /unix does not match the running kernel.
Preserving 368127 bytes of symbol table http://nfs.ext64
Cannot access tunable parameters because /unix does not match the running kernel.
Cannot access tunable parameters because /unix does not match the running kernel.
Cannot access tunable parameters because /unix does not match the running kernel.
Cannot access tunable parameters because /unix does not match the running kernel.
complete
#AIX-Forum

Originally posted by: derekb

The solution is to reboot a second time.
I recently upgraded my OS to TL7 SP3 using NIM. Changed the bootlist after the upgrade pointing to the upgraded disks, rebooted and vmo -a does not work. I verified all the typical commands, prtconf, bootinfo -K, getconf. IBM OS support guys told me to reboot again and this will fix it.
#AIX-Forum