QSH / WebSphere - WARNING!!! -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Folks,

Learn from my mistakes.  Spent the last two days beating our heads against a
wall because we couldn't get a new WAS instance to create through QSH.
Then, once we did (found the TOUCH command was pointing to the wrong "real"
command via symbolic link), there were all sorts of other ones which were
messed up.

Lesson to be learned:  If you participated in a beta of QSH back in V4R2,
you will need to uninstall and re-install QSH or call IBM and have them give
you the script to change all symbolic links from pointing to the QSHELLUTIB
and moving it to QSHELL.  

Hope no one else learns this one the hard way.  Easy way to check - do a
WRKLNK, go to /usr/bin and check the symbolic links on the commands with a
12.  If they're pointing to /QSYS.LIB/QSHELL.LIB/(command) then you're okay.
Otherwise, get on the horn with IBM!  Have a great day.

Justin C. Haase
Midrange Systems Engineer - Kingland Systems Corporation
IBM Certified AS/400 Systems Administrator
Microsoft Certified Professional
e-mail - justin.haase@kingland.com
www.kingland.com

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.