Eventually you can replace the first character in the remote devicename from Q to Z or similar to avoid name collisions. At worst you might end up with a specific character for every source system. Good luck!
Best regards,
Stefan Tageson
TietoEVRY
mobile +46 732 369934
Sensitivity: Internal
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of ~TA~
Sent: den 29 april 2020 21:17
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Telnet came from where
Ah, now I understand. Force the WSID on the Target system to the be the same as the WSID on the Source system. Hmm, that is a definite possibility. The only snag I can see is if the Source WSID is already in use on the Target system.
Thanks for the idea.
~TA~
On 4/29/2020 2:06 PM, Stefan Tageson wrote:
Correct, but if the device name is the same on the target system you know what it is on source system .....
Best regards,
Stefan Tageson
TietoEVRY
mobile +46 732 369934
Sensitivity: Internal
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
~TA~
Sent: den 29 april 2020 21:01
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Telnet came from where
This would set the device name on the TARGET system.
What I need to know is the workstation ID of the session that initiated the telnet on the SOURCE system.
Thanks.
~TA~
--
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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=02%7C01%7CStefan.Tageson%40evry.com%7Cc2e2838cb0824a55c84e08d7ec71eb00%7C40cc2915e2834a2794716bdd7ca4c6e1%7C1%7C0%7C637237846347096321&sdata=BrYG%2BqMbJMIKsFR30RV1ccIl6t%2FLXldbCUkgvytp2tc%3D&reserved=0
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fmidrange-l&data=02%7C01%7CStefan.Tageson%40evry.com%7Cc2e2838cb0824a55c84e08d7ec71eb00%7C40cc2915e2834a2794716bdd7ca4c6e1%7C1%7C0%7C637237846347096321&sdata=MEPyGtTis6erHhjwLWruCVkX9PBTbhSNDBHtGLPVnMo%3D&reserved=0.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Famazon.midrange.com%2F&data=02%7C01%7CStefan.Tageson%40evry.com%7Cc2e2838cb0824a55c84e08d7ec71eb00%7C40cc2915e2834a2794716bdd7ca4c6e1%7C1%7C0%7C637237846347096321&sdata=bvGl1iUat9mhktn7luMVGZiNm69CjuVCcHLQR8TghtE%3D&reserved=0
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.