|
When you use the QWTSETP, or the QSYSSETPROFILEHANDLE API, you can change the currently running job from one user profile to another, which is actually pretty cool when you think about it. Real cloak and dagger stuff! ha! However, the qualified job name of the original job does NOT get updated to reflect the new user profile information (i.e., if the original job was S104WMRM/SHANNON/069403 and the new user profile the job was set to run under is BOB...the qualified job does not change to S104WMRM/BOB/069403). And I understand why that is, and...under most circumstances, this would be acceptable. However...I have the need to change the user profile a job runs under and then I need to telnet to a remote system using the new user profile and then log on transparently using the RMTUSER() paramater of Telnet. The problem is, that because the current Qualified job name is not updated to reflect the new user profile it was set to run under, the automatic logon using Telnet fails because, the Telnet session thinks that the user coming in is the original user (which it gets from the qualified job name) rather than the new user profile. 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? Thanks, Shannon O'Donnell
As an Amazon Associate we earn from qualifying purchases.
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.