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



The method you performed (option 3 to restart IPL on manual) is also a
way to do it - I figured I'd mention the definite way rather than the
other method, as speed on the control panel is an important factor with
the way you did it.

When you came up on the A-side for your initial OS load, and then
load/apply your PTFs,  those PTFs will go on permanent.  Since you're
coming up B-side now, the PTF loads will go to temp apply.  No big deal
with known-good PTFs.

My pleasure to post - glad I can share my "useless trivia" (my wife's
quote) with the community.

Justin C. Haase - iSeries System Administrator
IBM Certified Systems Expert - eServer i5
Kingland Systems Corporation
email - justin.haase@xxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Wednesday, April 27, 2005 4:22 PM
To: Midrange Systems Technical Discussion
Subject: Re: Console QSECOFR Conundrum

Justin, thanks!

Exactly what was done while I was waiting for a response (nothing to
lose in the IPL....)

Question though:  I changed it to manual, changed the option to 3,
pressed enter and it IPL'd (changed the panel back to normal after
pressing enter).  How is that different from the "press the white button
twice" approach?

Is coming up on the A side important? (we IPL'd B, Normal )

In any case, the console was waiting for us to sign back on after a few
minutes of IPL'ing....

I never knew that the white button did anything but turn it ON.  Pushing
twice turns it OFF?  Learn something new every day.

Thanks for posting.

Pete
 

Haase, Justin C. wrote:

>I'd agree on IPL time for your freshly-scratched machine.  Plus, in the

>time it's taken to get a response, the powerdown and IPL would have 
>been done.
>
>What I would do:  switch 'er to manual, white button twice.  Once off, 
>switch back to A-side normal and bring it back up.  Take a look at 
>QSYSOPR once you're back in to ensure nothing horrible happened.
>Continue where you left off.  (After creating a PHELGREN profile).
>
>Justin C. Haase - iSeries System Administrator IBM Certified Systems 
>Expert - eServer i5 Kingland Systems Corporation email - 
>justin.haase@xxxxxxxxxxxx
>
>
>-----Original Message-----
>From: midrange-l-bounces@xxxxxxxxxxxx
>[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
>Sent: Wednesday, April 27, 2005 3:13 PM
>To: Midrange Mailing List
>Subject: Console QSECOFR Conundrum
>
>Been using this scratch install of the V5R2M0 Model 720 as a learning 
>option for a backup operator and we have run into an interesting issue.
>I was allowing the "trainee" the option to sign on to perform the Group

>PTF loads and CUME and in attempting to log on to the console, the guy 
>disabled both the QSECOFR userid AND the console. We haven't set up any

>other user profiles yet.
>
>The archives say that Qsecofr can sign on to the console even with a 
>disabled user profile, but, how do I bring the console back?
>
>I can force DST but I don't have an option in DST to re-enable the 
>console.
>
>Is it IPL time?
>
>Thanks,
>
>Pete Helgren
>
>
>--
>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.
>
>
>
>CONFIDENTIALITY NOTICE:  This e-mail communication, including
attachments, is covered by the Electronic Communications Privacy Act, 18
U.S.C. 2510-2521, is confidential, and may be legally privileged.  If
you are not the intended recipient or believe you received this
communication in error, please reply to the sender indicating that fact
and delete the copy you received.  In addition, retention,
dissemination, distribution, copying, or otherwise use of the
information contained in this communication is strictly prohibited.
Thank you.
>
>  
>
--
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.



CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, is 
covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is 
confidential, and may be legally privileged.  If you are not the intended 
recipient or believe you received this communication in error, please reply to 
the sender indicating that fact and delete the copy you received.  In addition, 
retention, dissemination, distribution, copying, or otherwise use of the 
information contained in this communication is strictly prohibited.  Thank you.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.