| Blogs | Classifieds | Downloads | FlashChat | Gallery | Googlemap | Invite Friends | Links | Projects | Reviews | Wiki |
| |||||||||
Welcome to the pSeries Tech Forums,
our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software. You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments. Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community. Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
| Our Sponsors | |
| | |
| Want to advertise? | |
![]() |
| | LinkBack | Thread Tools |
|
#1
| ||||
| ||||
Hi, I have recently installed aix 4.3.3.0 (base level) on RS/6K machine and later did the update to aix 4.3.3.0 with ML11. However when I execute the command "oslevel" the machine shows "4.3.2.0", in contrast "oslevel -r" respond with "4330-11". To clarify, verified the boot media and it's clearly AIX 4.3.3. Despite of updating almost all the base level filesets to 4.3.3.0 (ML11), I couldn't get the desired output (4.3.3.0)on "oslevel" command which is required by the compilers to work on. Greatly appreciate any help. Thank you. |
|
#2
| ||||
| ||||
try running the oslevel command with the -l flag. This will list filesets at levels earlier than maintenance level specified by the <level> parameter oslevel -r -l 4330-11 Usage: oslevel [ -l <level> | -g <level> | -q ] [ -r ] -l : List filesets at levels earlier than maintenance level specified by the <level> parameter -g : List filesets at levels later than maintenance level specified by the <level> parameter -q : List names of known maintenance levels -r : Appies all flags to Recommended Maintenance Levels -f : Forces cache rebuilt |
|
#3
| ||||
| ||||
Hi, I did tried "oslevel -rl 4330-11" but it returned back to prompt without any fileset info. It looks there is no broken filesets from the previous/present ML level. Anything to do with "bos.rte"?? Thanks. |
|
#4
| ||||
| ||||
If your are truly at 4330-11 when you run "lslpp -l bos.rte" you should see the following. lslpp -l bos.rte Fileset Level State Description ---------------------------------------------------------------------------- Path: /usr/lib/objrepos bos.rte 4.3.3.76 COMMITTED Base Operating System Runtime Path: /etc/objrepos bos.rte 4.3.2.0 COMMITTED Base Operating System Runtime |
|
#5
| ||||
| ||||
Hi, Thanks. The problem resolved after updating the IMNSearch fs's. Not sure whether really it causes the actual issue. However the "lslpp -l bos.rte" and "oslevel -rl 4330-11" outputs does not show any clue to the actual issue. Pls find the posts below. a). "lslpp -l bos.rte" returns with following output. # lslpp -l bos.rte Fileset Level State Description ---------------------------------------------------------------------------- Path: /usr/lib/objrepos bos.rte 4.3.3.77 COMMITTED Base Operating System Runtime Path: /etc/objrepos bos.rte 4.3.3.75 COMMITTED Base Operating System Runtime b). "olsevel -rl 4330-11" output does not show any broken filesets during the upgrade. I assume it means the upgragde were alright. Thanks. |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |