Not assigned to subsystem problem
david bulog
address 0---from my main consule port set at port 0/0 I type WRKCFGSTS
*DEV *LCLDSP
I go to option for Device W4--3196 terminal port 1 switch 0--"Powered
off or not yet available" status message which is false so I vary device
off and on and status message changes to "NOT ASSIGNED TO SUBSYSTEM"
Question 1:How do I assign to a subsystem(Like QCTL which my main
consule W1 is assigned to)
Question 2:Why didnt it do this for me as the the display details for W4
shows "Created by Auto-Configuration"
Im running Version 2R3 by the way
cheers dave
d2...@xtra.co.nz
nina jones
> address 0---from my main consule port set at port 0/0 I type WRKCFGSTS
> *DEV *LCLDSP
did you cable it thru the console or thru the as/400? if you cable it thru the console,
you will have to use port 0, address x (x being 1-6, zero being used by the console)
also, the terminal needs to be addressed, and that address needs to match the
configuration. did you get a manual with it?
> I go to option for Device W4--3196 terminal port 1 switch 0--"Powered
> off or not yet available" status message which is false so I vary device
> off and on and status message changes to "NOT ASSIGNED TO SUBSYSTEM"
> Question 1:How do I assign to a subsystem(Like QCTL which my main
> consule W1 is assigned to)
qctl is a special subsystem for the system console only (ctl = control). normally the
rest of the terminals are assigned to qinter (inter = interactive).
they normally fall into these based on the subsystem descriptions. unless someone has
fiddled with it, qinter is set for work station type *all, which everything should fall
into by default.
> Question 2:Why didnt it do this for me as the the display details for W4
> shows "Created by Auto-Configuration"
is w4 your new device? it sounds like the as/400 has found it and configured it.
a couple of things to try here:
key wrkactjob and see if qinter is up. (you should se qbatch, qcmn, qctl and qinter)
if not, power the system down and back up (pwrdwnsys *immed restart(*yes)
now wrkactjob again and see if qinter is up.
then, wrkdevd now look for your device. check the port, address, and controller.
one question - was this machine used? and did you recently get it?
hope that helps,
nj
Darryl Johns
The assignment of a device to a subsystem is in part determined by the
WorkStation entries (WSE) in the subsystem description. There are
descriptions for every subsystem (QCTL, QINTER, QSPL, QBASE, etc.).
The workstation to allocate is identified in these entries either by
TYPE or by NAME. The defaults are typically by TYPE. If that is the
case, make sure that the 3196 is represented in the type listing of
the susbsystem to which you want the device assigned. Or make sure
that the Workstation Type Entries have a *ALL.
If on the other hand the workstation is assigned by NAME (check the
Workstation Name Entrries ) then make sure you have a device
description created with the name that matches that which you put in
the subsystem description, and with the attributes in the device
description that match the switch and port settings on the device. The
workstation is allocated at the time the subsystem is started.
The Work Management Guide goes into further detail on this subject;
but these are the basics.
Regards,
Darryl Johns
IBM AS/400 e-business Specialist
On Sun, 06 Sep 1998 21:43:40 +1200, david bulog <d2...@xtra.co.nz>
wrote:
>I have just aquired a second terminal and have connected it to port 1,
>address 0---from my main consule port set at port 0/0 I type WRKCFGSTS
>*DEV *LCLDSP
>I go to option for Device W4--3196 terminal port 1 switch 0--"Powered
>off or not yet available" status message which is false so I vary device
>off and on and status message changes to "NOT ASSIGNED TO SUBSYSTEM"
>Question 1:How do I assign to a subsystem(Like QCTL which my main
>consule W1 is assigned to)
>Question 2:Why didnt it do this for me as the the display details for W4
>shows "Created by Auto-Configuration"
>
>Im running Version 2R3 by the way
>
>cheers dave
>d2...@xtra.co.nz
Darryl Johns
IBM AS/400 e-business Specialist
(opinions expressed are mine, not necessarily those of IBM)
Nicholas Bridge
Just a thought!
Nick B.