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

Subject: Re: Refresh Job after using the Set Profile Handle API and TELNET
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Wed, 28 May 2003 06:39:12 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Refresh Job after using the Set Profile Handle API and TELNET , Shannon O'Donnell

This mailing list archive is Copyright 1997-2025 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.