oslevel -> TYPERML ?

[kimmers]

Hi,

I know that the AIX system has been installed as 4.3.3.0 but giving a 'oslevel' it returns as a value TYPERML.
I was trying to find out from that script/subprogram (/usr/bin/oslevel) that where the oslevel has been defined but could't find it, or is it hard coded somewhere?

I believe java131 uses the same info as a parameter since some links are created wrongly on a install based on that command.

Got any hint on this?

#Kimmers

 

[kimmers]

Sorry,

I found one thread handling this case, I have to try it out.
thread52-231894 on a keyword at the first time didn't return any matches.

Regards,

#Kimmers

 

[DSMARWAY]

Also have a look at the following thread ,
thread52-304077 a look at the part about links .

HTH

 

[kimmers]

Hi,

Thank You for the follow up.
I checked my links based on that thread and yes, those were created wrongly.
I made the corrections as requested there.

Do you think the maintenance level is causing still the TYPERML to appear as an return for a oslevel -command?

I wonder why since even if you make the simplest OS installation from the CD it doesn't have any maintenance patches included and the oslevel -command returns the installed version number. Unless ofcourse there has been a known bug or if the installation failed somehow.
Those I could think of which might be causing it.

Regards,

#Kimmers

 

[aixqueen]

There may be two issues...one was the bos.rte.install needed patches after the install of 4.3.3.0 or it had oslevel problems...the other was that

Any time you have filesets that are lower than the installed level (even one), you can get the oslevel command to return errors.... My guess is that you have several filesets
of the OS that are not at 4.3.3. You need to find them and either upgrade them or
delete them if they are no longer used.

Type RML
I believe is merely telling you that the release maintenance level has a problem...

http://techsupport.services.ibm.com/server/aix.techTips?refNo=90605188914736

http://techsupport.services.ibm.com/server/aix.techTips?refNo=91623329313242

You can run the instfix command to see what level of aix you are at:
instfix -i |grep ML
or
instfix -ik 4330-01_AIX_ML

If the output indicates that not all filesets are found, you can also determine
which filesets are not updated using the command:
instfix -ciqk 4330-09_AIX_ML | grep ":-:"
or
To see what needs to be installed to bring you up to a particular
maintenance level:

# instfix -ivk 4330-06_AIX_ML|grep not | grep ':'
See if you can find what is below your level of operating system and then as I said either delete it or upgrade it.
The bos.rte.install and bos.rte filesets had bugs and needed upgrade as well...
but look for old filesets first...then look to put an update cd on your system to bring you up to the correct maintenance level

Also try erasing any .oslevel* files
in the /tmp directory and then try again

Good Luck and let us know what shows up?

 

[kimmers]

Hi and Thank You,
I will most likely do the update next week to the correct level.

Here are outputs to your commands:
instfix -i |grep ML
All filesets for AIX43ML were found.
All filesets for 4.3.1.0_AIX_ML were found.
All filesets for AIX43ML were found.
Not all filesets for 4.3.2.0_AIX_ML were found.
Not all filesets for 4320-01_AIX_ML were found.
Not all filesets for 4320-02_AIX_ML were found.
Not all filesets for 4.3.3.0_AIX_ML were found.

----
instfix -ik 4330-01_AIX_ML
There was no data for 4330-01_AIX_ML in the fix database.

----
instfix -ciqk 4330-09_AIX_ML | grep ":-:"

----
instfix -ivk 4330-06_AIX_ML|grep not | grep ':'
There was no data for 4330-06_AIX_ML in the fix database.

----
ls -l /tmp/.oslevel*
-rw-r--r-- 1 root system 79751 Mar 11 15:09 /tmp/.oslevel.mlinfo.cache

I will remove this when I do the update.

Regards,

#Kimmers

 

[aixqueen]

On the items where not all filesets are found...
you would do the following command substititing the info for maintenance level

instfix -ciqk 4320-01_AIX_ML | grep ":-:"

find out what is not installed and update or install that fileset and then go to the next

instfix -ciqk 4320-02_AIX_ML | grep ":-:"

same for
instfix -ciqk 4330_AIX_ML | grep ":-:"

an update cd with patches and the issue of smitty update_all may fix some of the problems, but some of the filesets may be obsolete....or never got upgraded during the migrations from 4.3.1 to 4.3.2 to 4.3.3.........

Find what is missing and try to update....or as I said if it is obsolete, delete the fileset...
I am sue you know...but
PLEASE do a mksysb before you mess with the update or the removal of filesets as you may need to restore . Same with user data in other volume groups...just in case.
Good luck