Lukas, thanks for the help. The ./ before the file name at the
oem_setup_env prompt worked. I am still having problems in that after
running the .sh file or using "ldfware -file xxxxx.img " to apply the
firmware, my firmware level, both temp and perm, does not change. I
do run "ldfware -commit", but I assume that just copies the temporary
image to permanent.

Working with IBM hardware so they should be able to get the problem fixed.


$ ldfware -file 01EA340_101_039.img
The image is valid and would update the temporary image to EA340_101.
The new firmware level for the permanent image would be EA330_031.

The current permanent system firmware image is EA330_031.
The current temporary system firmware image is EA330_031.


***** WARNING: Continuing will reboot the system! *****

Do you wish to continue?
Enter 1=Yes or 2=No
1


$ lsfware
system:EA330_031 (t) EA330_031 (p) EA330_031 (t)


On Fri, Oct 9, 2009 at 10:47 AM, Lukas Beeler
<lukas.beeler@xxxxxxxxxxxxxxxx> wrote:
On Fri, Oct 9, 2009 at 16:40, Steve Richter <stephenrichter@xxxxxxxxx> wrote:
get a "not found" error when I run the file:

$ oem_setup_env
# fw101.sh

This is AIX, not DOS. "." is never in $PATH. Use the full path or
./fw101.sh for the local directory.

--
Read my blog at http://projectdream.org
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].