In case anyone is interested, I have also added a new enhancement to the âr option of the amsactz program to provide an Objects Options and Operations Options report. These reports will summarize what options (conn, open, get, put, close, callback, sub, subrq) your applications used by object and by operation. Here is an example for the amqsput sample that did 6 PUTs to a TCZ.TEST1 queue:
=================================================================================================================================
Application Objects Options Report
Options tracked are conn, open, get, put, close, callback, sub, subrq
=================================================================================================================================
pid: 15116 ApplicationName: amqsput UserId: mqm referenced the following options by object:
Object Name: TCZ.TEST1
Open Options: 8208 Count: 1
MQOO_OUTPUT
MQOO_FAIL_IF_QUIESCING
Put Options: 8260 Count: 6
MQPMO_NO_SYNCPOINT
MQPMO_NEW_MSG_ID
MQPMO_FAIL_IF_QUIESCING
Close Options: 0 Count: 1
MQCO_NONE
MQCO_IMMEDIATE
=================================================================================================================================
Application Operations Options Report
Options tracked are conn, open, get, put, close, callback, sub, subrq
=================================================================================================================================
pid: 15116 ApplicationName: amqsput UserId: mqm referenced the following options by operations:
Operation: MQXF_CLOSE
Close Options: 0 Count: 1
MQCO_NONE
MQCO_IMMEDIATE
Operation: MQXF_CONN
Connect Options: 256 Count: 1
MQCNO_SHARED_BINDING
Operation: MQXF_OPEN
Open Options: 8208 Count: 1
MQOO_OUTPUT
MQOO_FAIL_IF_QUIESCING
Operation: MQXF_PUT
Put Options: 8260 Count: 6
MQPMO_NO_SYNCPOINT
MQPMO_NEW_MSG_ID
MQPMO_FAIL_IF_QUIESCING
Thanks,
Tim
From: Tim Zielke
Sent: Monday, August 18, 2014 3:35 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: RE: MQ Application Activity Trace - How to restrict what it collects
Hello,
I sent a LISTSERV update a few weeks ago that my amqsact source code changes (called amqsactz.c) had been posted in the MH06 supportpac -> http://www-01.ibm.com/support/docview.wss?uid=swg24036430
I have also made another enhancement to the amqsactz.c, that I would like to mention. It has been posted on the Capitalware web site -> http://www.capitalware.com/mq_code_c.html
Also, for future enhancements to the amqsactz.c source, I plan on just using exclusively the Capitalware web site and pulling the amqsactz.c out of the next MH06 supportpac release. This will help avoid confusion of having it in two places.
This amqsactz.c enhancement includes a âr option to produce summary reports when run in the non-verbose mode. The summary reports will summarize what applications were found in the AAT records, and what objects, channels and operations that the applications referenced. Below is an example.
Thanks,
Tim
Example of amqsactz summary reports:
=================================================================================================================================
Application Summary Report
=================================================================================================================================
Pid ApplicationName UserId Tid Count MQI Count
18957 runmqtrm mqm 1 2
18979 WebSphere MQ Client for Java tzmqmon 1 196
18979 amqrmppa tzmqmmca 3 1
22910 amqsput mqm 1 3
22911 amqsput mqm 1 8
22912 amqsget mqm 1 9
=================================================================================================================================
Application Objects Referenced Report
=================================================================================================================================
pid: 18957 ApplicationName: runmqtrm UserId: mqm referenced the following objects:
pid: 18979 ApplicationName: WebSphere MQ Client for Java UserId: tzmqmon referenced the following objects:
pid: 18979 ApplicationName: amqrmppa UserId: tzmqmmca referenced the following objects:
pid: 22910 ApplicationName: amqsput UserId: mqm referenced the following objects:
ObjName: TCZ.TEST2 Count: 1
pid: 22911 ApplicationName: amqsput UserId: mqm referenced the following objects:
ObjName: TCZ.TEST1 Count: 1
pid: 22912 ApplicationName: amqsget UserId: mqm referenced the following objects:
ObjName: TCZ.TEST1 Count: 1
=================================================================================================================================
Application Channels Referenced Report
=================================================================================================================================
pid: 18957 ApplicationName: runmqtrm UserId: mqm referenced the following channels:
pid: 18979 ApplicationName: WebSphere MQ Client for Java UserId: tzmqmon referenced the following channels:
ChannelName: APP01.2S.SERVER Count: 196
pid: 18979 ApplicationName: amqrmppa UserId: tzmqmmca referenced the following channels:
ChannelName: CL.2S.MYSERVER123 Count: 1
pid: 22910 ApplicationName: amqsput UserId: mqm referenced the following channels:
pid: 22911 ApplicationName: amqsput UserId: mqm referenced the following channels:
pid: 22912 ApplicationName: amqsget UserId: mqm referenced the following channels:
=================================================================================================================================
Application Operations Executed Report
=================================================================================================================================
pid: 18957 ApplicationName: runmqtrm UserId: mqm executed the following operations:
Operation: MQXF_GET Count: 2
pid: 18979 ApplicationName: WebSphere MQ Client for Java UserId: tzmqmon executed the following operations:
Operation: MQXF_CALLBACK Count: 175
Operation: MQXF_CB Count: 7
Operation: MQXF_INQ Count: 7
Operation: MQXF_PUT Count: 7
pid: 18979 ApplicationName: amqrmppa UserId: tzmqmmca executed the following operations:
Operation: MQXF_CONNX Count: 1
pid: 22910 ApplicationName: amqsput UserId: mqm executed the following operations:
Operation: MQXF_CONNX Count: 1
Operation: MQXF_DISC Count: 1
Operation: MQXF_OPEN Count: 1
pid: 22911 ApplicationName: amqsput UserId: mqm executed the following operations:
Operation: MQXF_CLOSE Count: 1
Operation: MQXF_CONNX Count: 1
Operation: MQXF_DISC Count: 1
Operation: MQXF_OPEN Count: 1
Operation: MQXF_PUT Count: 4
pid: 22912 ApplicationName: amqsget UserId: mqm executed the following operations:
Operation: MQXF_CLOSE Count: 1
Operation: MQXF_CONNX Count: 1
Operation: MQXF_DISC Count: 1
Operation: MQXF_GET Count: 5
Operation: MQXF_OPEN Count: 1
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Potkay, Peter M (CTO Architecture + Engineering)
Sent: Tuesday, July 08, 2014 6:50 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ Application Activity Trace - How to restrict what it collects
Nice work Tim. Please update us when this gets into MH06.
http://www-01.ibm.com/support/docview.wss?uid=swg24036430
Peter Potkay
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Tim Zielke
Sent: Tuesday, July 08, 2014 6:08 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ Application Activity Trace - How to restrict what it collects
With a little tweaking of the amqsact program I got it to do the following:
First I changed the default amqsact terse output to create API 1 line summary lines like the following:
=================================================================================================================================
EYEC RecordNum Pid Tid Channel Name Date Time Operation CompCode MQRC HObj (ObjName)
1LS= 0 16622 1 2014-07-08 14:57:26 MQXF_CONN MQCC_OK 0000 -
1LS= 1 16622 1 2014-07-08 14:57:26 MQXF_OPEN MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 1 16622 1 2014-07-08 14:57:28 MQXF_PUT MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 2 16622 1 2014-07-08 14:57:29 MQXF_PUT MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 3 16622 1 2014-07-08 14:57:30 MQXF_PUT MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 4 16622 1 2014-07-08 14:57:31 MQXF_PUT MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 5 16622 1 2014-07-08 14:57:32 MQXF_CLOSE MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 6 16622 1 2014-07-08 14:57:32 MQXF_DISC MQCC_OK 0000 -
1LS= 7 28414 1 2014-07-08 14:57:50 MQXF_GET MQCC_FAILED 2033 2 (SYSTEM.DEFAULT.INITIATION.QUEUE)
1LS= 8 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:24 MQXF_CONNX MQCC_OK 0000 -
1LS= 9 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:24 MQXF_OPEN MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 9 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:25 MQXF_PUT MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 10 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:26 MQXF_PUT MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 11 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:29 MQXF_PUT MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 12 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:29 MQXF_CLOSE MQCC_OK 0000 2 (TCZ.TEST1)
1LS= 12 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:29 MQXF_DISC MQCC_OK 0000 -
1LS= 13 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:29 MQXF_BACK MQCC_OK 0000 -
1LS= 13 28435 17569 CLIENT.TO.SERVER 2014-07-08 16:19:29 MQXF_DISC MQCC_OK 0000 -
=================================================================================================================================
I added an EYEC (eye catcher) text so the API 1 line summary lines could be easily grepped out from the output, and also added the RecordNum, Pid, and Channel Name to the 1 line summary.
So now if I do the following:
amqsact âb | grep 1LS= > summary.txt
I get all the API calls in 1 line summaries, like listed above. If I want to reduce the API 1 line summaries to a subset by channel name, pid, tid, object name, etc., I can easily do that with greps.
Also, if I want to see more data for a given API call, I can do the following:
amqsact âv âb > verbose.txt
And then search for the specific RecordNum I want to research in the verbose.txt.
I plan on submitting this amqsact enhancement in one of the next MH06 supportpac iterations.
Thanks,
Tim
From: Tim Zielke
Sent: Monday, July 07, 2014 9:35 AM
To: 'Sailesh Krishnamurti'; ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: RE: MQ Application Activity Trace - How to restrict what it collects
I was thinking of altering the current amqsact with the following enhancements.
1. Require a back up queue for the SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE (i.e. SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE.BKUP).
2. Allow a back up processing option that just clears the S.A.T.A.Q.B and copies all messages from the S.A.T.A.Q to the S.A.T.A.Q.B.
3. Allow a reload option that just clears the S.A.T.A.Q and copies all messages from the S.A.T.A.Q.B to S.A.T.A.Q.
4. Allow a standard processing option that would do the following steps 5 â 7:
5. Allow for selections on channel name, queue name, pid, tid, etc. as mentioned below.
6. Destructively read any messages that do not meet the selection criteria from the S.A.T.A.Q.
7. Produce the reports it currently does, but only for records that matched on the selection criteria.
With the above enhancements, the administrator would have a way to quickly glean the S.A.T.A.Q for what information they want, if they wanted to use the MS0P supportpac to view the data. Also, they could easily do subsequent selections with the back up/reload option.
This would be more work, but I was also thinking of adding 1 line summary of each API into the output with a unique tag. This would allow the administrator to grep out a report that was just 1 line API summaries, and then search back into the verbose report to find more detailed information for that specific API call using the unique tag.
Just some suggestions for anyone else out there that was thinking of tweaking amsqct.
Thanks,
Tim
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Sailesh Krishnamurti (BLOOMBERG/ 120 PARK)
Sent: Monday, July 07, 2014 8:43 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ Application Activity Trace - How to restrict what it collects
I have voted for this too and am running into the same issue.
One way to do this would be to modify the amqsact code to have parameters to discard messages with certain parameters (such as queue name, channel name etc... Or a comma separated list) and run it frequently as a scheduled task. I am currently experimenting with this.
----- Original Message -----
From: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
At: Jul 7 2014 09:36:00
All,
I absolutely voted for this RFE. Turning on a trace by SVRCONN name or Queue name(s) would be very helpful. I would like to extend the options to include some kind of a list where a handful of SVRCONN names (5 or so) and maybe also a queue name list (5 or so of those with each one being wild carded (ACCOUNT_ACCESS*, CUSTOMER_ACCESS*, etc.). But even getting started with a more granular trace as specified in the RFE is worth a lot.
Thanks,
David Corbett
IBM Certified Solution Designer - WebSphere MQ V7.0
IBM Certified System Administrator - WebSphere MQ V7.0
From: "Potkay, Peter M (CTO Architecture + Engineering)" <***@THEHARTFORD.COM<mailto:***@THEHARTFORD.COM>>
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>,
Date: 07/07/2014 07:29 AM
Subject: Re: MQ Application Activity Trace - How to restrict what it collects
Sent by: MQSeries List <***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>>
________________________________
Thanks for the tips, Tim. Iâll have to experiment with that.
In the meantime I have opened a RFE on this topic. Here is the direct link to vote on this RFE if you think itâs a good idea.
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=55753
Headline: MQ Application Activity Trace - Allow MQ administrator to limit tracing by queue name, channel name, Connection ID
Description: The ApplicationTrace stanza in the mqat.ini file currently allows the MQ Admin to restrict Application Activity tracing by application name, by using the ApplName parameter.
This RFE is to add additional parameters to allow the MQ Admin to limit the application activity tracing even further - by queue name, or by MQ Client Channel name, or by Connection ID.
In a highly shared environment with multiple high volume applications sharing the same queue manager, the App Activity Trace is of limited value if those apps all have the same name due to the massive amount of trace data sent to SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE. By implementing this RFE we could definitely use the powerful App Activity Trace feature more often to solve problems on our own, hopefully reducing the # of PMRs we need to open.
Use case: Our queue managers all support multiple applications. Frequently there are dozens of instances of an application connected to the same queue manager, and restricting the App Activity Trace to an appl name still produces a massive amount of App Activity Trace output. For example, on a WMB Queue Manager, all the message flows are "DataFlowEngine". And on our queue managers where DataPower connects with their Front Side Handlers, there are dozens of "WebSphere Datapower MQClient".
By allowing us to restrict the App Activity Trace to a specific queue name or set of queue name with a wildcard, it would allow us to focus the App Activity Trace on the one App whose Activity we would like to Trace. Other options to focus the trace could be by MQ Client Channel Name and / or by Connection ID.
Peter Potkay
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Tim Zielke
Sent: Thursday, July 03, 2014 12:53 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ Application Activity Trace - How to restrict what it collects
Donât feel too bad. I had the same confusion when I first looked at it a while back. I was meaning to go back and figure it out (how to reduce the trace to just one program), and your question was the impetus to do that.
I donât think there is a way to restrict it to a channel name or queue name. How about this though? Use the qload program to destructively read out messages from the SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE that donât have a match on your queue name or channel name? That would leave you with the messages you are probably looking for. I havenât tested that though.
Thanks,
Tim
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Potkay, Peter M (CTO Architecture + Engineering)
Sent: Thursday, July 03, 2014 11:43 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ Application Activity Trace - How to restrict what it collects
Geez, that is simple and obvious now that I look at it. Duh.
It works fine. Only my amqsput* activity is going into the SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE. I can look at the messages with the amqsact sample program. Next up is getting MS0P going as it has a plug in for viewing these trace messages.
Any tricks on restricting the tracing activity to a specific queue name or MQ channel name? Use Case: I have an MQ Client Concentrator with dozens of DataPower client connections into it. Telling mqat.ini to only look for Datapower* still leaves with me with a lot to parse. Would be nice to further restrict it to a specific queue or client channel so that I can get trace activity only for one DataPower MQ Front Side Handler.
Peter Potkay
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Tim Zielke
Sent: Thursday, July 03, 2014 9:38 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ Application Activity Trace - How to restrict what it collects
Hi Peter,
The following works for me, if I only want to pick up application activity trace records for a specific module like amqsput*.
Also, add the following ApplicationTrace: stanza to what you currently have. This will turn any other module besides amqsput* off for activity tracing.
ApplicationTrace: # Application specific settings stanza
ApplClass=ALL # Application type
# Values: (USER | MCA | ALL)
# Default: USER
ApplName=* # Application name (may be wildcarded)
# (matched to app name without path)
# Default: *
Trace=OFF # Activity trace switch for application
# Values: ( ON | OFF )
# Default: OFF
ActivityInterval=0 # Time interval between trace messages
# Values: 0-99999999 (0=off)
# Default: 0
ActivityCount=0 # Number of operations between trace msgs
# Values: 0-99999999 (0=off)
# Default: 0
TraceLevel=MEDIUM # Amount of data traced for each operation
# Values: LOW | MEDIUM | HIGH
# Default: MEDIUM
TraceMessageData=0 # Amount of message data traced
# Values: 0-104857600
# Default: 0
Thanks,
Tim
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Potkay, Peter M (CTO Architecture + Engineering)
Sent: Wednesday, July 02, 2014 8:59 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: MQ Application Activity Trace - How to restrict what it collects
Iâm just starting to play with this App Activity Trace thing and the MS0P Support Pack to read the data produced. I wanted to start small and only capture activity by amqsput or amqsputc. I am getting that, but I continue to pick up activity from other things still talking to the Queue Manager â one of my BMC WMB monitoring agents, and what Iâm guessing is MQ Explorer itself based on the evidence, although Iâm kinda disappointed the Activity Trace Messages wouldnât be crystal clear in identifying MQ Explorer by name.
So what am I doing wrong given my mqat.ini file â why am I picking up activity from programs that donât match the amqsputc* string.
MQ 7.5.0.3 on RHEL 6.4
Below is my mqat.ini file.
#*******************************************************************#
#* Module Name: mqat.ini *#
#* Type : WebSphere MQ queue manager configuration file *#
# Function : Define the configuration of application activity *#
#* trace for a single queue manager. *#
#* *#
#*******************************************************************#
AllActivityTrace: # Global settings stanza
ActivityInterval=0 # Time interval between trace messages
# Values: 0-99999999 (0=off)
# Default: 0
ActivityCount=0 # Number of operations between trace msgs
# Values: 0-99999999 (0=off)
# Default: 0
TraceLevel=MEDIUM # Amount of data traced for each operation
# Values: LOW | MEDIUM | HIGH
# Default: MEDIUM
TraceMessageData=0 # Amount of message data traced
# Values: 0-104857600
# Default: 0
StopOnGetTraceMsg=ON # Stop trace on get of activity trace message
# Values: ON | OFF
# Default: ON
##################################################################
# Prevent the sample activity trace program from generating data #
##################################################################
ApplicationTrace: # Application specific settings stanza
ApplClass=ALL # Application type
# Values: (USER | MCA | ALL)
# Default: USER
ApplName=amqsact* # Application name (may be wildcarded)
# (matched to app name without path)
# Default: *
Trace=OFF # Activity trace switch for application
# Values: ( ON | OFF )
# Default: OFF
ActivityInterval=0 # Time interval between trace messages
# Values: 0-99999999 (0=off)
# Default: 0
ActivityCount=0 # Number of operations between trace msgs
# Values: 0-99999999 (0=off)
# Default: 0
TraceLevel=MEDIUM # Amount of data traced for each operation
# Values: LOW | MEDIUM | HIGH
# Default: MEDIUM
TraceMessageData=0 # Amount of message data traced
# Values: 0-104857600
# Default: 0
##################################################################
# Monitor amqsputc or amqsputc#
##################################################################
ApplicationTrace: # Application specific settings stanza
ApplClass=ALL # Application type
# Values: (USER | MCA | ALL)
# Default: USER
ApplName=amqsput* # Application name (may be wildcarded)
# (matched to app name without path)
# Default: *
Trace=ON # Activity trace switch for application
# Values: ( ON | OFF )
# Default: OFF
ActivityInterval=1 # Time interval between trace messages
# Values: 0-99999999 (0=off)
# Default: 0
ActivityCount=0 # Number of operations between trace msgs
# Values: 0-99999999 (0=off)
# Default: 0
TraceLevel=MEDIUM # Amount of data traced for each operation
# Values: LOW | MEDIUM | HIGH
# Default: MEDIUM
TraceMessageData=10 # Amount of message data traced
# Values: 0-104857600
Peter Potkay
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation.
---------------------------------------------------------------------
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html