Console Replacement - Step 2 -- MIDRANGE-L

Subject: Console Replacement - Step 2
From: Rich Loeber <rich@xxxxxxxxx>
Date: Mon, 30 Dec 2013 15:30:17 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

Suggestions?

Rich

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Console Replacement - Step 2 , Jim Oberholtzer

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.