| 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
| ||||
| ||||
Can anyone tell me why I am receiving java "command not found" errors from the vtmenu and mkvterm commands? They work fine on my P5 HMCs. Here is what I see: hscroot@nhcbl530:~> lshmc -V Version: 3 Release: 3.7 HMC Build level 20060207.1 U808917: CVE-2002-0843: Apache Buffer Overflow Vulnerability (07-28-2006) hscroot@nhcbl530:~> mkvterm /opt/hsc/bin/command/mkvterm: line 26: java: command not found This happens on several P4 HMCs. All are at the same level. Any ideas or suggestions welcomed.
__________________ Bob Blizard National Grid USA Service Co. "A prudent question is one half of wisdom." Francis Bacon |
|
#2
| ||||
| ||||
I had the same problem after upgrading the HMC software on a p4 HMC. I'm sorry that I can't verify what version it was. Anyway the cause of the problem was that java was not in the PATH. To fix it I had to open a call with IBM to get root access then edit the PATH to include the java directory. However, I would think that resolution would be included in a fix by now. Hint: if you get your 24 hours of root access disable the restricted shell on your personal account so you can easily diagnose these problems yourself! Good luck. |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |