No joy here .... no F13 option presented. Not sure how I can IPL into DST
without a working console.
On 12/30/2013 3:49 PM, Jim Oberholtzer wrote:
I'm guessing you're going to IPL in manual mode but before you do that:
Go into SST, and take option 8 "Work with Service Tools and user IDs and
You should see an "F13=Select STS LAN adapter" option, press F13
You'll see that the LAN console device has an "*" under "Selected. Put a
"1" in press enter.
You'll now see the configuration for the LAN console. Try "F17=Deactivate
followed by activate"
That will take several seconds.
Now try connecting with LAN console again. If it works then you can go in
and change the security options to allow you to fix stuff from SST.
If it does not work, I'm afraid your stuck with an IPL into DST to correct
the devices and user profiles.
Chief Technical Architect
Agile Technology Architects
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Monday, December 30, 2013 2:30 PM
To: Midrange Systems Technical Discussion
Subject: Console Replacement - Step 2
I now have iSeries Access reinstalled on my replacement PC, but can't get
the OpsConsole to work. At the moment, I have no console, so I need to
get this working just using SST from a regular terminal session. The
problem is that working with service tools device IDs is disabled and
I follow the instructions to fix that, it fails.
I'm all set to just create a second console device, but it looks like I
need to be able to do so from SST and the menu option is disabled.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l