RE: Can't get a signon

QINTER was not started. IBM did walk me through a getting CONSOLE session which shouldn't be confused with a TERMINAL session.
Thanks for the good advice none the less.
As an aside, I never had to wait so long for support. I think with the hurricane and it being the day after a holiday and because month end was on Sunday, IBM support is extremely busy today. I sure am and this partition is just one we run for a subsidiary in another state. Wasn't my fault QINTER was not active...

Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, September 02, 2008 9:31 AM
To: Midrange Systems Technical Discussion
Subject: Re: Can't get a signon

Well, if CWBPING works then your system is not in a restricted state.
Other than that, it's a non issue as the HMC couldn't give a rip if
iSeries access is working, let alone installed.

Since your system is not in a restricted state, try a regular session and
ensure that the subsystem in system value QCTLSBSD is up and running. Use
WRKACTJOB SBS(...). If the status of the subsystem is END you may want to
consider starting that. Of course, a plethora of autostart jobs may start
kicking out.

Do you see a job normally associated with the system console active in
that subsystem? The name of the system console may be altered by the
value QDEVNAMING. *NORMAL may result in DSP01, *DEVADR may result in
DSP010000. You may wish to try WRKDEVD DSP* and check the status of the
device, and it's associated controller.

There's a quick start, keep us posted.

Rob Berendt