Re: TFRJOB

AFIAK, TFRJOB shouldn't change which subsystem your display comes up in.
It transfers your JOB.   When you sign off, your job is ended.

Instead, what I would do to test this is:

1) Create a new subsystem that uses your new sign-on screen.
2) Set up routing & job queue entries as appropriate (use DSPSBSD to
     see what QINTER, et al, have)
3) Use ADDWSE to add your workstation to the new subsystem.
4) Sign off of your workstation, and from another display start
     the new subsystem.   
5) When the new subsystem starts, it should grab your display away
     from QINTER, since you're currently signed off.

As far as I know, the workstation entries (added with ADDWSE) and the
order in which the subsystems are started is what controls which sign-ons
come up in which subsystems.



On Mon, 19 Mar 2001 fdenoncourt@harcourt.com wrote:

> I am changing QDSIGNON and have been referring to an article written
> several years ago and to IBMs current web site. To test the change I should
> TFRJOB to another subsystem that has the new QDSSIGNXX assigned to it.  The
> transfer works fine but once I sign-off to view my new QDSIGNON,  I am back
> at QINTER so I cannot see my changes.  I had tried QCTL and QPGMR with the
> same results.
> A new subsystem was created for me.  Signing off after TFRJOB leaves the
> sign-on display at the new subsystem. Is there something special about
> about QCTL and QPGMR? The person who created the new subsystem wasn't sure
> why it worked out this way but since I was rolling again it wasn't an issue
> - with him.
> Now, I am just plain curious. No big hurry. If anyone has the time and
> inclination, it would be useful information.
> Thanks,
> Fran Denoncourt
> 

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---