That will work 'mostly' :-)

The secret is that there can be ONLY one active subsystem providing a signon screen to a workstation for you to be certain where it will pop up. That is the AT(*SIGNON) parm must be specified on the ADDWSE command for only one subsystem.

Generally this means you have to remove the *ANY entry from other subsystems such as QINTER and replace that with multiple entries to catch the workstations you want in QINTER (and any other subsystems as well.)

If a workstation matches AT(*SIGNON) workstation entries in multiple active subsystems then the subsystem in which it starts "cannot be predicted."

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 8/31/2015 12:09 PM, Voris, John wrote:

. . . What I remember is . . .
Putting MIS* as a WRKSTN entry in the subsystem QPGMR.
Starting STRSBS QPGMR before QINTER
Also, use the IBM command TFRJOB so the job can move to jobq QPGMR. Read the gotchas in the help text of the TFRJOB cmd, such as "The job must not be a group job".
( I know that is how we ensure that QSYSOPR always runs within QCTL subsystem, regardless which device they signon at. I just forget the particulars.)

- John V.


We have a need to switch some workstations to run under QPGMR so that we can shutdown QINTER for a few hours for system maintenance.
I do have workstation entry names in QPGMR with the value MIS*.

That does work occasionally, but I don't remember how and when. My client access session name is MIS_d1, but it continually goes directly to QINTER.
I want to test the process before this coming weekend.

Darryl

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.