Re: How to get connection name from DebuggeeProcess? -- WDSCI-L

Hello Thomas,

The debug team has looked at your requirements.
For the job name, this is something they have accepted as a future
requirement but for the connection name, it is currently officially
supported via
import com.ibm.etools.iseries.debug.internal.core.AS400ConfigurationConstants;

IDebugTarget pdtdebugTarget = ...
String connectionName = pdtdebugTarget.getLaunch().getLaunchConfiguration().getAttribute(AS400ConfigurationConstants.RESID_CONNECTION_NAME, "");

There are no plans to provide an alternative API to get this information.

I hope this helps,
______________________________________________________________________________________

Edmund Reinhardt
905-413-3125
IBM Canada Ltd Rational Developer for i Access Client Solutions
Architect
[1]https://www.linkedin.com/in/edmundreinhardt/ [2]http://ibm.biz/rdi_hub [3]http://ibm.biz/IBMi_ACS

----- Original message -----
From: Thomas Raddatz <thomas.raddatz@xxxxxx>
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] Re: [WDSCI-L] How to get connection name from
DebuggeeProcess?
Date: Mon, Oct 12, 2020 1:38 AM

Hi Edmund,

Thank you for forwarding my enhancement request to the debugger
developer. It should not be that hard to do the necessary changes.

I assume that the next iSphere version will be another major step
forward. Not only because of the debugger menu extensions but also
because of the "Job Trace Explorer" that currently is under development.

I assume that I can release a next beta version, soon.

Regards,

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von Edmund
Reinhardt
Gesendet: Donnerstag, 8. Oktober 2020 00:57
An: wdsci-l@xxxxxxxxxxxxxxxxxx
Cc: Morris Kwan <mkwan@xxxxxxxxxx>
Betreff: Re: [WDSCI-L] How to get connection name from DebuggeeProcess?

   Your request to extend the DebuggerProcess.getAttribute() API sounds
   reasonable. I will forward it to the debugger developer. In the
meantime
   I suggest using your work arounds, as this will not be delivered in
the
   near future.

   Your enhancements sound great Thomas. Thanks for all the value you
are
   providing to the community.



______________________________________________________________________________________


Edmund Reinhardt
905-413-3125

IBM Canada Ltd Rational Developer for i
Access Client Solutions
   Architect
[1][4]https://www.linkedin.com/in/edmundreinhardt/  [2][5]http://ibm.biz/rdi_hub  [3][6]http://ibm.biz/IBMi_ACS ;





   ----- Original message -----
   From: Thomas Raddatz <thomas.raddatz@xxxxxx>
   Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
   To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
   Cc:
   Subject: [EXTERNAL] Re: [WDSCI-L] How to get connection name from
   DebuggeeProcess?
   Date: Wed, Oct 7, 2020 4:46 AM

   Hi Edmund,

   As I mentioned before extending the debugger popup menu works, now.
So
   far I added:

   * Copy Qualified Name

   Copies the qualified job name to the clipboard.

   * Job Log Explorer

   Starts the job log explorer for the job that stopped at the
breapoint

   * Work With Spooled Files

   Opens the "Work With Spooled Files" view for the job that stopped
at the
   breapoint

   These options are really helpful. But there are a few concerns that
I
   hassle with:

   a) Package '' com.ibm.debug.pdt.internal.*" is not exported and
   accessing the classes is discouraged.

   b) There is no reliable method for retrieving the job name. The
only
   options are calling either "DebuggeeProcess.getAttribute(null)" or
   "DebuggeeProcess.getLabel()". Both methods are private due to the
   restricted package access and I have to use a regular expression
for
   retrieving the job name from the string returned.

   c) The connection name is completely missing. All I have is the DNS
name
   (or IP address) and the debugger port. Hence the only option I have
to
   find the connection is spinning through all available connections
   looking for an active connection with a matching IP address.

   It was over the top if you clould add the missing pieces to the
   attribute list of DebuggeProcess (actually IProcess) to ensure
reliable
   information. That would also solve the "discouraged access"
problem,
   because getAttribute(key) is part of the interface IProcess:

   1) CONNECTION_NAME

   2) QUALIFIED_JOB_NAME

   Or instead of 2) three dedicated attributes:

   2a) JOB_NAME
   2b) JOB_USER
   2c) JOB_NUMBER

   This is nothing more than a question and of course I know that IBM
   cannot make money with that. I also know that it cannot be changed
right
   now. But if it is not too hard for you, I may have a chance to
refactor
   my classes to make them reliable and stable.

   Regards,

   Thomas

   -----Ursprüngliche Nachricht-----
   Von: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von
   Tools/400
   Gesendet: Montag, 5. Oktober 2020 22:02
   An: wdsci-l@xxxxxxxxxxxxxxxxxx
   Betreff: Re: [WDSCI-L] How to get connection name from
DebuggeeProcess?

   Hi Edmund,

   Thank you very much for your help and thank you very much to the
debug
   developer. The information you provided did indeed help a lot to
create
   the menu item action.

   Now I can successfully open the iSphere "Job Log Explorer" view
from the
   "Job" node of the call stack, when the debugger stops at a SEP.

   I am just a little converned about that package
   "com.ibm.debug.pdt.internal.*" is not exported. So hopefully its
classes
   will not be changed for the next years.

   I also hope that I can rely on the following statements for
retrieving
   the qualified job name:

      private static final String PATTERN =
   "\\S*\\s+((\\d{6})/(.{1,10})/(.{1,10}))\\s+.*";

      protected String getQualifiedJobName(IProcess process) {

      Pattern pattern = Pattern.compile(PATTERN);
      Matcher matcher =
pattern.matcher(process.getAttribute(null));
      if (matcher.find()) {
      return matcher.group(1);
      }

      return null;
      }

   Now I am going to add an action for opening the iSphere "Work With
   Spooled Files" view to show the spooled files of the job.

   Both items are on my wish list for a long time.

   Best Regards,

   Thomas.

   Am 05.10.2020 um 17:20 schrieb Edmund Reinhardt:
   > Hello Thomas,
   > It looks like you are innovation and creating lots of new
goodies
   which is
   > always welcome!
   > Here feedback from the debug developer on your questions
   > 1) The package com.ibm.debug.pdt.internal.core.model is
actually
   exported
   > from the com.ibm.debug.pdt.core plugin. The user said it is
not
   exported
   > probably because he did not add the plugin
   "com.ibm.debug.pdt.core" to
   > the Require-Bundle list in the MANIFEST.MF file of his own
plugin.
   Please
   > add him to add com.ibm.debug.pdt.core as a Require-Bundle and
try
   again.
   > 2) The user can use the base class PDTDebugTarget to access
most
   of the
   > methods for PDT debug target. The connection label is a field
of
   this
   > class. PDTDebugTarget is under the
   > package com.ibm.debug.pdt.internal.core, which is also
exported
   from
   > plugin com.ibm.debug.pdt.core
   >
   > I hope this helps you get the connections name and create
your
   menu item
   > action.
   >
   >
   >
______________________________________________________________________
   > ________________
   >
   >
   > Edmund Reinhardt
   > 905-413-3125
   > IBM Canada Ltd Rational
Developer for
   i Access Client Solutions
   > Architect
   > [1][4][7]https://www.linkedin.com/in/edmundreinhardt/   ;
   >
[2][5][8]http://ibm.biz/rdi_hub   [3][6][9]http://ibm.biz/IBMi_ACS  ;
   >
   >
   >
   >
   >
   > ----- Original message -----
   > From: Tools/400 <thomas.raddatz@xxxxxxxxxxx>
   > Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
   > To: wdsci-l@xxxxxxxxxxxxxxxxxx
   > Cc:
   > Subject: [EXTERNAL] [WDSCI-L] How to get connection name
from
   > DebuggeeProcess?
   > Date: Sun, Oct 4, 2020 10:06 AM
   >
   > Hi (IBM),
   >
   > I already managed adding a menu entry to the popup menu of
the
   "Debug"
   > view in order to start the "iSphere Job Log Explorer", when
the
   debugger
   > stops at a service entry point:
   >
   >    targetID="org.eclipse.debug.ui.DebugView"
   >    id="org.eclipse.debug.ui.debugview.popupMenu">
   >
   > I also could retrieve the qualified job number from the
IProcess
   > selected object (Last entry in den Debug view, e.g.
"Process:
   > 403007/QUSER/QZRCSRVS Program SPLF").
   >
   > Hence I now have 1 out of 2 parameters that I need to open
the
   Job Log
   > Explorer. The missing parameter is the connection name.
   >
   > I can see, that IProcess is a DebuggeeProcess and that
   DebuggeeProcess
   > has an "fTarget" attribute. fTarget is a PICLDebugTarget
class
   and has
   > an "fConnectionLabel" attribute. So that is close to the
   connection name
   > that I need.
   >
   > Sadly I am stuck here. The problems I could not yet solve
are:
   >
   > a) com.ibm.debug.pdt.internal.core.model.DebuggeeProcess is
not
   exported
   > and hence cannot be imported to the iSphere project.
   >
   > b) The same thing applies to
   > com.ibm.debug.internal.pdt.PICLDebugTarget
   >
   > c) Retrieving the connection name.
   >
   > So the question is, how can I get the connection name at
this
   point
   > (???):
   >
   > public class OpenJobLogDebugPopupAction implements
   > IViewActionDelegate {
   >
   >    private static final String PATTERN =
   > "\\S*\\s+((\\d{6})/(.{1,10})/(.{1,10}))\\s+.*";
   >
   >    private Object shell;
   >    private IStructuredSelection structuredSelection;
   >
   >    public void run(IAction arg0) {
   >    Object selectedObject =
   structuredSelection.getFirstElement();
   >    if (selectedObject instanceof IDebugElement) {
   >    IDebugElement debugElement =
   (IDebugElement)selectedObject;
   >    if (selectedObject instanceof IProcess) {
   >    IProcess process = (IProcess)debugElement;
   >    String connectionName = ???;
   >    String qualifiedJobName =
   getQualifiedJobName(process);
   >    if
   (!StringHelper.isNullOrEmpty(qualifiedJobName)) {
   >    LoadRemoteJobLogJob job = new
   > LoadRemoteJobLogJob("iSphere", qualifiedJobName);
   >    job.run();
   >    }
   >    }
   >    }
   >    }
   >
   > (The example above uses hard coded connection "iSphere".)
   >
   > Regards,
   >
   > Thomas.
   >
   > --
   > This is the Rational Developer for IBM i (WDSCI-L)
mailing
   list
   > To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
   > To subscribe, unsubscribe, or change list options,
   > visit:

[4][7][10]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6  ;
   > or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
   > Before posting, please take a moment to review the archives
   > at
[5][8][11]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0   ;.
   >
   > Help support midrange.com by shopping at amazon.com with
our
   affiliate
   > link: [6][9][12]https://amazon.midrange.com  ;
   >
   >
   >
   >
   > References
   >
   > Visible links
   > 1. [10][13]https://www.linkedin.com/in/edmundreinhardt/  ;
   > 2. [11][14]http://ibm.biz/rdi_hub  ;
   > 3. [12][15]http://ibm.biz/IBMi_ACS  ;
   > 4.
[13][16]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6  ;
   > 5.
[14][17]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0  ;
   > 6. [15][18]https://amazon.midrange.com/  ;
   >

   --
   This is the Rational Developer for IBM i (WDSCI-L) mailing list
   To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe,
   unsubscribe, or change list options,
   visit:
[16][19]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6  ;
   or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
   Before posting, please take a moment to review the archives at

[17][20]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0  ;.

   Help support midrange.com by shopping at amazon.com with our
affiliate
   link: [18][21]https://amazon.midrange.com  ;
   --
   This is the Rational Developer for IBM i (WDSCI-L) mailing list
   To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
   To subscribe, unsubscribe, or change list options,
   visit:
[19][22]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6  ;
   or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
   Before posting, please take a moment to review the archives
   at
[20][23]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0  ;.

   Help support midrange.com by shopping at amazon.com with our
affiliate
   link: [21][24]https://amazon.midrange.com  ;




References

   Visible links
   1. [25]https://www.linkedin.com/in/edmundreinhardt/ ;
   2. [26]http://ibm.biz/rdi_hub ;
   3. [27]http://ibm.biz/IBMi_ACS ;
   4. [28]https://www.linkedin.com/in/edmundreinhardt/ ;
   5. [29]http://ibm.biz/rdi_hub ;
   6. [30]http://ibm.biz/IBMi_ACS ;
   7.
[31]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6 ;
   8.
[32]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0 ;
   9. [33]https://amazon.midrange.com/ ;
  10. [34]https://www.linkedin.com/in/edmundreinhardt/ ;
  11. [35]http://ibm.biz/rdi_hub ;
  12. [36]http://ibm.biz/IBMi_ACS ;
  13.
[37]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6 ;
  14.
[38]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0 ;
  15. [39]https://amazon.midrange.com/ ;
  16.
[40]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6 ;
  17.
[41]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0 ;
  18. [42]https://amazon.midrange.com/ ;
  19.
[43]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6 ;
  20.
[44]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0 ;
  21. [45]https://amazon.midrange.com/ ;
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
[46]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6 ;
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[47]https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0 ;.

Help support midrange.com by shopping at amazon.com with our affiliate
link: [48]https://amazon.midrange.com ;
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [49]https://lists.midrange.com/mailman/listinfo/wdsci-l ;
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [50]https://archive.midrange.com/wdsci-l ;.

Help support midrange.com by shopping at amazon.com with our affiliate
link: [51]https://amazon.midrange.com ;

References

Visible links
1. https://www.linkedin.com/in/edmundreinhardt/
2. http://ibm.biz/rdi_hub
3. http://ibm.biz/IBMi_ACS
4. https://www.linkedin.com/in/edmundreinhardt/
5. http://ibm.biz/rdi_hub
6. http://ibm.biz/IBMi_ACS
7. https://www.linkedin.com/in/edmundreinhardt/
8. http://ibm.biz/rdi_hub
9. http://ibm.biz/IBMi_ACS
10. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
11. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
12. https://amazon.midrange.com/
13. https://www.linkedin.com/in/edmundreinhardt/
14. http://ibm.biz/rdi_hub
15. http://ibm.biz/IBMi_ACS
16. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
17. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
18. https://amazon.midrange.com/
19. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
20. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
21. https://amazon.midrange.com/
22. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
23. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
24. https://amazon.midrange.com/
25. https://www.linkedin.com/in/edmundreinhardt/
26. http://ibm.biz/rdi_hub
27. http://ibm.biz/IBMi_ACS
28. https://www.linkedin.com/in/edmundreinhardt/
29. http://ibm.biz/rdi_hub
30. http://ibm.biz/IBMi_ACS
31. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
32. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
33. https://amazon.midrange.com/
34. https://www.linkedin.com/in/edmundreinhardt/
35. http://ibm.biz/rdi_hub
36. http://ibm.biz/IBMi_ACS
37. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
38. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
39. https://amazon.midrange.com/
40. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
41. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
42. https://amazon.midrange.com/
43. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
44. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
45. https://amazon.midrange.com/
46. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-32918e2147f457c4af8b2b7f2b86ccaa462e7cb6
47. https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fwdsci%2dl&umid=8295ea84-3b3c-4b57-a0cb-41d6fed67ae5&auth=9aef805e690002f0e1ecb337a51f380fbb6abf82-4f530aa867dbd71b1e183388efb7d474c035e9a0
48. https://amazon.midrange.com/
49. https://lists.midrange.com/mailman/listinfo/wdsci-l
50. https://archive.midrange.com/wdsci-l
51. https://amazon.midrange.com/