Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+AW\:\s+TSM\s+Replication\s*$/: 3 ]

Total 3 documents matching your query.

1. [ADSM-L] AW: TSM Replication (score: 1)
Author: Michael Malitz <michael.malitz AT MM-IT DOT AT>
Date: Sat, 23 Jul 2016 18:51:57 +0200
Hallo Jeanne Bruno, Try the following: on the target server: enter q replnode <node_name> <name of the source server> it's kind of a "circumvention" -- you will see the data you would like to know, b
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2016-07/msg00069.html (18,533 bytes)

2. Re: [ADSM-L] AW: TSM Replication (score: 1)
Author: Jeanne Bruno <JBruno AT CENHUD DOT COM>
Date: Mon, 25 Jul 2016 12:20:26 +0000
Hello. Thanks Michael. Rick does this help you? (or do you think this is sufficient for your management team?) On the source server do 'q repln <nodename' On the target server do 'q replnode <nodenam
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2016-07/msg00070.html (19,684 bytes)

3. Re: [ADSM-L] AW: TSM Replication (score: 1)
Author: "Plair, Ricky" <rplair AT HEALTHPLAN DOT COM>
Date: Mon, 25 Jul 2016 13:18:04 +0000
This is very good information but it's not exactly what they want. These commands only show you a particular client. What I'm looking for is some kind of script or command that will show you a summar
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2016-07/msg00072.html (21,748 bytes)


This search system is powered by Namazu