My guess is that killing the server jobs on the IBMi will cause the java VM to puke and then ACS will be unusable until a reboot.
I couldn't get a new connection testing just now.
I just tried to see if I could start acs with /PLUGIN=LOGON and use a different user. I was able to execute the command with no errors then start a 5250 session , but it still used my earlier credentials and not the new credentials.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Tuesday, March 23, 2021 4:50 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: How to change log-on user in ACS
I was asked how to use a different user in the IFS action of ACS - the person needed more authority than he had with the logon he first used.
This is the logon for the connection to the system, not the further logon you would have with a 5250 session.
One of those things I think I should know but have never needed to do - and I hope it's not in the docs that come with ACS!!
So how can we break the original connection without rebooting? And without finding the host server job, maybe, that is in use, if that is a way to do this? Or have someone do WRKOBJLCK over the user profile and kill the server jobs that are listed?
Regards
Vern
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
