× 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.



Jeff,

Yeah, my experience was ugly, but I was also pushing the bleeding edge with the JS12 blade and knew that I was in for some fun. Since that last round of firmware/OS updates in June, the blade has been about as reliable as the old 520 I had. I had a VIOS issue a few weeks back and the length of time it took to recover was self inflicted. But I do think that an install "wizard" would be a step forward as long as it included a boatload of diagnostic tools so the stuff that Aaron experienced could be quickly diagnosed and corrected. I don't care if the end user ignores every caution that you give them prior to starting an install, your install procedure should *assume* that the end user ignored your instructions and should guide them (gently) through doing it the correct way. I sit my wife in front of my installer wizard (she about as close to a Luddite as there is) and watch to see what she does wrong at every step and then I rewrite the routine to anticipate those missteps.

But I don't think the i is *supposed* to be a user installed system, like the HP you get at Costco.

Pete


Jeff Crosby wrote:
Aaron,

I cannot help you, but I have to say something.

I am NOT looking forward to the day when my company needs to replace the 520
with Power i equipment. The amount of trouble people like you and Lukas and
Pete had and are having getting new machines set up and running gives me the
willies. I want simplicity, not this new complexity being introduced.

Just my $.02.


On Fri, Oct 30, 2009 at 8:45 AM, Aaron Bartell <aaronbartell@xxxxxxxxx>wrote:

I am now in section "Initial IBM i OS configuration" (
http://wiki.midrange.com/index.php/GettingStarted).

Upon first logging in with QSECOFR/QSECOFR it requires you to change the
QSECOFR password. No issue, I did that and proceeded to the next step of
putting the system into manual mode, was prompted by the DST logon prompt,
and I entered QSECOFR and the *new* password. Well, it didn't take the new
password, so I tried QSECOFR as the password - no go. And now it is
telling
me "Id disabled" when I try to log in. When I do an F1 on that message to
get more info it just takes me to the help for the screen, so I don't even
have a message id to do a search on to see how to resolve the issue. This
is the only page I could find, but it requires that I am able to log in to
DST to enable a DST profile - thanks IBM:

http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/index.jsp?topic=/rzamh/rzamhenabledevidsdst.htm

Help.

Aaron Bartell
http://mowyourlawn.com
--
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.





As an Amazon Associate we earn from qualifying purchases.

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-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.