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

That is what I am doing Rob. Minus the password, of course.  Because I have
the system value (QRMTSIGN) set to *SAMEPRF on both systems, and because my
intent is to telnet from one system to another using the same user profile
on both systems, a password is not required when doing Telnet using the
RMTUSER paramater.

The problem is, I think...is that because the current qualified job name is
still pointing to the original user,  when I Telnet, and it's using the NEW
User profile I changed the current job to....the remote system sees the
telnet request as originating from the ORIGINAL User profile, but using a
NEW User profile on the RMTUSER parameter.  And therefore forcing a signon
panel to appear.

Just a little more background here in case someone can think of a better
alternative for handling this particular problem....

I have multiple AS/400's scattered throughout the state. We have a need to
allow users from SYSTEMA  to get on to SYSTEMQ to look up some very specific
information. There are business and logistical reasons why we cannot just
bring the data from SYSTEMQ to SYSTEMA, so instead, we actually take them to
the remote system.

Now, if we were to duplicate the user profiles from every AS/400 on every
other AS/400, we could simply Telnet using the RMTUSER paramater and things
would be jake. However, duplicating and maintaining all those user profiles
would present its own set of nightmares (i.e., duplicate users on multiple
systems, etc..), so the approach I want to take is to create just a couple
of "Public" profiles that can exist on every system.  I then had hoped to be
able to change the current job of a user who needs to go to a remote system
to a PUBLIC profile, telnet them to the remote system (transparently), and
then bring them back when they are done and reset their profile back to the
origianl user.

But that's not working because TELNET on the remote system is seeing the
request coming from the original user profile rather than the changed/new
user profile.


Shannon O'Donnell


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


> Any reason why you can't do this:
> TELNET RMTSYS(RMTLOC) RMTUSER(USER) RMTPWD(pwd)
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
> _______________________________________________
> 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.
>
>