Re: Strange iSeries Access Operations Console Behavior

[kirkg@xxxxxxxxxxxxx]

OPS Console  uses at least "1" of the SST/DST user ID's to establish the 
initial connection. Most of the time this ID is '11111111' ( 8 #1s).  The 
default password for that ID is also '11111111' but it can be changed. 
Other default IDs available are '22222222' 'QSRV' and 'QSECOFR'. All of 
these ID's are stored separately from their OS versions. what may have 
happened is that 1 or more of these SST/DST IDs are disabled
_____________________
Kirk Goins CCNA
Systems Engineer, Manage Inc.
IBM Certified i5 Solution Sales
IBM Certified iSeries Solutions Expert
IBM Certified Designing IBM e-business Solutions 
Office 503-353-1721 x106 Cell 503-577-9519
kirkg@xxxxxxxxxxxxx      www.manageinc.com

There are 10 types of people in the world:
Those that understand binary, and those that don't.



Paul Tykodi <ptykodi@xxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/17/2005 03:00 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
Strange iSeries Access Operations Console Behavior







Dear List,
 
  I am doing some work for a customer who has an iSeries 9406-800 running 
V5R2. They use a PC (Win XP sp2) as their iSeries console. It is connected 
to the iSeries server using a special cable provided by IBM and the cable 
connects to a board in the iSeries back plane. The setup appears to allow 
the iSeries Access Operations Console software to establish a high speed 
serial communication link with the iSeries server.
 
  Recently the PC software has claimed that all of the iSeries server 
administrative user ID's are disabled and this has caused the console 
function to stop working due to logon failure. When I plugged a twinax 
terminal into the iSeries, I found that at the server end of the 
communication all of the user ID's are fine and the system is running 
fine.
 
  It seems like the iSeries Access Operations Console software may have 
written some erroneous password information to the registry and that has 
caused it to fail. The un-install and re-install of the software does not 
resolve the problem.
 
  The PC is at the latest iSeries Access service pack for V5R2.
 
  Does anyone know what registry keys might have become corrupted to cause 
this unexpected behavior?
 
  Thanks.
 
  Best Regards,
 
  /Paul
  --
  Paul Tykodi
  Principal Consultant
  TCS - Tykodi Consulting Services LLC
 
  E-mail: ptykodi@xxxxxxxxxx

 
---------------------------------
 Yahoo! FareChase - Search multiple travel sites in one click.