Re: Refresh Job after using the Set Profile Handle API and TELNET

I have not reported it to IBM.   I'm not sure yet that it's a bug, or if I'm
just not understanding, completely, how Telnet and the QWTSETP API work in
relation to each other.


Shannon O'Donnell


----- Original Message -----
From: "David Gibbs" <david@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, May 28, 2003 6:39 AM
Subject: Re: Refresh Job after using the Set Profile Handle API and TELNET


> At 10:31 PM 5/27/2003, you wrote:
> >So..after all that explanation...does anyone have a suggestion on how to
> >update the qualified job (or other alternative) so that I can perform an
> >automatic signon under the new profile?
>
> When you use QWTSETP to change the user handle, only the CURRENT USER gets
> changed ... the job id remains the same.  I really don't think there is a
> way for you to change the job id (I'm pretty sure you wouldn't want it to
> either).
>
> It does, however, sound like you have found a bug in telnet ... all
> programs should use the CURRENT USER for user id dependant functions.  If
> telnet isn't doing that, it probably should.
>
> Have you reported it to IBM?
>
> david
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>