Sign on in QCTL instead of QINTER

[Guest.Visitor]

You need to change your initial program to do a TFRJOB to jobq QCTL. that will move you there.

[Guest.Visitor]

Hmmmmm. I could do that...BUT...all the folks here in IS use the same initial pgm...which would put everyone in QCTL. Guess I could separate everyone. Would the 400 being in a restricted state still enable me to sign on?

[Guest.Visitor]

It sounds like you need to state your Goal by doing this? If you log on via a regular workstation session, have your initial program move you to QCTL you would be there until the sub-systems are all ended. The only device that is active in restricted state is the console. You may want to consider what we have done. We support our AS/400's remotely all the time because our IT Staff is not typically at the location of where the AS/400s are sitting. In my case I live in Atlanta Georgia, but all the computers are in South Dakota, and Denver Colorado. It just goes to show you, you don't have to live and work in the same place these days. We replaced all of our old twinax type consoles with Gateway PCs and connected them to the AS/400 via the com ports using "IBM Remote Console". Then we are running Windows 2000, and a software product called VNC and we can log on to any of our AS/400 Consoles/PC's from anywhere. The PC Consoles are on a different subnet, so if the AS/400 network were to fail for any reason, we can still get the the PC systems by the nature that the PC's are on other network hardware. We bring our systems up and down, coordinate IBM, and no one is at the data center. I can watch SRC's change, etc. We are basically lights out. Hope this helps, or has triggered some other ideas for you. Keith

[Guest.Visitor]

Simple... Just make sure that your workstation name (or partial name) is not described in any other subsystem. We make the workstation names unique. chuck Opinions expressed are not necessarily those of my employer. "brettmc" <brettmc@mcpressonline.com> wrote in message news:6ae73100.-1@WebX.WawyahGHajS... | How do I set up my profile/workstation/sbs description to sign on into QCTL instead of QINTER? I've added my display device name to QCTL workstation name entries but something is missing. Can someone clue me in? | | Brett

[Guest.Visitor]

brettmc wrote: > How do I set up my profile/workstation/sbs description to sign on > into QCTL instead of QINTER? I've added my display device name to > QCTL workstation name entries but something is missing. Can someone > clue me in? Brett, The key is to make 1 or 2 changes. 1) Place your workstation session id in QCTL and make sure that the subsystem controls your job at *Signon. If Qinter still grabs it: 2) Add an entry, if not already there, for you workstation and set the subsystem control to *Enter. Bill

[Guest.Visitor]

In response to brett's message, it sounds like you want a second console at your desk. Adding a workstation entry into the QCTL (which is more times than oft a the controlling subsystem) needs to be done for what ever you call your session. Although, notice that you will log into Qinter first (if it is up), even if you do a TFRJOB (all the TFRJOB command does is transfer you to a specified JOBQ, which will end when a PWRDWNSYS, ENDSYS or ENDSBS *ALL is run). When the sbs Qinter ends - you will be booted out to the signon screen again, if not done originally from the tfrjob. You will only be able to be logged on during a restricted state if your workstation is designated as a console (WRKSTNTYPE *CONS). There are many products that allow a non-twinax device (i.e. TCP/IP connected) simulate a console. I've used TwinData's and IBM's products and both are fine.

[Guest.Visitor]

How do I set up my profile/workstation/sbs description to sign on into QCTL instead of QINTER? I've added my display device name to QCTL workstation name entries but something is missing. Can someone clue me in? Brett