If the new SBS is started after the Client Access session was "connected" then the original SBS will have control over the WS. Make sure the new subsystem is started before activating your 5250 sessions with Client Access.

being QCTL, it should be running 24/7, except when a PwrDwnSys or other command that physically ends that subsystem.

wierdest thing is, when i changed the 5250 emulator and saved it, last friday, it worked for myself and the two others that would be using the QCTL subsystem. today, we come up in QINTER.

Here's an explanation of how devices are allocated to subsystems (6.1): http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_61/rzaks/rzakswrkstationallocationa.htm

Not sure I like the idea of running IT staff in QCTL anyway. QCTL users would have a higher run priority, and IT folks tend to do things that are generally not good for performance. You'd be better off creating a clone of QINTER, and putting them there. If you need to get to QCTL, there's always TFRJOB.

good advice, dale.

already put that in motion as far as QCTL. have two .ws profiles for the three of us who keep laptops at home, to check system status, batch status, etc.

these are the ones with named devices that show up in QCTL as a work station entry. just used "IT" as an example, not a generalization of how someones normal job gets into the subsystem.