Re: amqcrsta processes
On Tru64, the last version of MQ is v5.1. But I prefer runmqlsr independently of MQ version because works fine, moreover without sysadmin ;-). Tibor > To get threading, you need to use the MQ listener (runmqlsr) instead of > inetd. The MQ listener is the preferred method starting with MQ 5.3. > -Original Message- > From: W Samuel [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 17, 2004 9:24 AM > To: [EMAIL PROTECTED] > Subject: Re: amqcrsta processes > Hi everyone, > Thanks for your replies. > The platform is Tru 64 unix. Do these TuningParameters > apply for this platform? > How do we configure a threaded inetd listener ? > Regards > W Samuel > --- Someswara R Adiraju wrote: > > Hi WS, >> >> You can tune your qm.ini parameters. Consider adding >> these parameters and >> try restarting the queue manager.. >> >> TuningParameters: >> AgentClassMap=(1,1,1) >> AgentClassLimit=(10,15,100) >> >> Hope this helps. >> >> Cheers, >> Somesh Adiraju >> >> >> >> >> Emile Kearns >> Sent by: MQSeries List >> 06/17/2004 02:22 PM >> Please respond to >> MQSeries List >> >> >> To >> [EMAIL PROTECTED] >> cc >> >> Subject >> Re: amqcrsta processes >> >> >> >> >> >> >> Consider using a threaded listener. >> >> -Original Message- >> From: MQSeries List [mailto:[EMAIL PROTECTED] >> On Behalf Of W Samuel >> Sent: 16 June 2004 12:13 PM >> To: [EMAIL PROTECTED] >> Subject: amqcrsta processes >> >> Hi everyone, >> >> On our Unix system, we have 5 active queue managers >> We've reached a state where none of these queue are responding anymore >> >> I've noticed that there are around 200 amqcrsta >> processes. I know that amqcrsta is related to >> channels >> but cant understand why so many processes are >> running >> >> >> Any idea how come so many amqcrsta processes are >> running and how can this be controlled/tuned ? >> >> Thanks, >> WS >> >> >> >> >> >> > ___ALL-NEW >> Yahoo! >> Messenger - so many all-new ways to express >> yourself >> http://uk.messenger.yahoo.com >> >> Instructions for managing your mailing list >> subscription are provided in >> the Listserv General Users Guide available at http://www.lsoft.com >> Archive: http://vm.akh-wien.ac.at/MQSeries.archive >> >> Any views expressed in this message are those of the individual >> sender, and T-Systems South Africa (Pty) Ltd accepts no >> liability therefore, >> except where the sender specifically states them to >> be those of T-Systems >> South Africa (Pty) Ltd. Although this message has >> been scanned for the >> possible presence of computer viruses prior to >> despatch, T-Systems South >> Africa (Pty) Ltd cannot be held responsible for any >> viruses or other >> material transmitted with, or as part of, this >> message. >> >> Instructions for managing your mailing list >> subscription are provided in >> the Listserv General Users Guide available at http://www.lsoft.com >> Archive: http://vm.akh-wien.ac.at/MQSeries.archive >> >> > ___ALL-NEW Yahoo! > Messenger - so many all-new ways to express yourself > http://uk.messenger.yahoo.com > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive
MQ logging
Title: Message Sorry for the simple question... I'm very new to MQ... By default does MQ log all messages that it transmits? If so, where is that log. If not, is it possible to configure MQ to track all the messages that it transmits? Thank you! Brian
Fw: MQ Proj Mgr opportunity...
would help if I attached the job Jody - Original Message - From: peabody associates To: Peabody Assoc Sent: Friday, June 18, 2004 3:44 PM Subject: MQ Proj Mgr opportunity... Hello, I was hoping someone might know of someone for the below opportunity. Thank you for any help you can offer! Regards, Jody KovalDirector of IT Placement ServicesPeabody Associates, Inc.(203) 595-9605[EMAIL PROTECTED] MQ Project Manager (Brokerage) - Peabody Associates, Inc. Location: US-NY-New York CIty Company: Peabody Associates, Inc. Internal Job #: 2477 Posted: 6/16/2004 Job Skills: Access, Project Manager, Web Job Type: W2 Start Date: now Pay Rate: $70,000 - $100,000 / year Travel: none requiredJob Description:MQ Project Manager in from Brokerage environment needed for full time opportunity with Major International Investment Firm in New York City. This is an AVP to a level opportunity with a base salary of 70 to 100k plus bonus. Must have steady employment history and experience in Investment Banking Industry. MAIN DUTIES/RESPONSIBILITIES OF THE ROLE: Project Manager/Coordinator for Messaging Integration Services Person part of global team responsible for coordinating Messaging Integration projects. Liaison between End Users (Development community), internal development team, and Support teams. This position is not extremely technical, however, sound technical skills are still needed. This opportunity is geared to someone who is interested in technical analysis and design, client presentations, client relationship management and project coordination and implementation and has good overall business sense. Required: Excel, Visio,Access, Excellent communication skills. Not required but good to have: Web Development (ASP), Knowledge of Messaging (MQ, Tibco, E4JMS), Business Objects.REQUIRED TECHNICAL SKILLS: Excel,Visio,Web, MQ serices DESIRED TECHNICAL SKILLS: Tibco, E4JMS, Business Objects, SCM REQUIRED WORK EXPERIENCE/BACKGROUND: Financial industry experience DESIRED WORK EXPERIENCE/BACKGROUND: 4+ years in the Financial industry EDUCATION/CERTIFICATION: BS DegreeMS Degree is desirable FULLY QUALIFIED CANDIDATES ONLY please respond to:Jody KovalDirector of IT Placement ServicesPeabody Associates, Inc.(203) 595-9605[EMAIL PROTECTED]
MQ Proj Mgr opportunity...
Hello, I was hoping someone might know of someone for the below opportunity. Thank you for any help you can offer! Regards, Jody KovalDirector of IT Placement ServicesPeabody Associates, Inc.(203) 595-9605[EMAIL PROTECTED]
WBIMB Message mapping
I still have that outstandng question on Message mapping for the Broker. Suppose I have a input data object I have built from a database call. I have multiple destinations that I need to send the data too. BUT.the destinations all have different formats (some get less of the data than others). Without building a mapping routine for each can I build the output messages by interrogating the output formats and fill in what is needed from the input fields. (Assuming the tags match from input format to output format) What I am trying to do is build a GENERIC mapping routine. I have 2000 plus interfaces and am trying to cut some of the work down. bobbee _ Getting married? Find great tips, tools and the latest trends at MSN Life Events. http://lifeevents.msn.com/category.aspx?cid=married Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Triggered sh/ksh Script
Thanks everyone. All beter solutions than the quickie I came up with. The TM2 position is an interesting point. I can now sleep better tonight!!! bobbee From: "Chad P. Little" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Triggered sh/ksh Script Date: Fri, 18 Jun 2004 09:10:59 -0400 Bobbee- Maybe this is what you are looking for. #!/bin/ksh TriggerMessage=$1 StrucId=`echo "$TriggerMessage" | cut -c 1-4` Version=`echo "$TriggerMessage" | cut -c 5-8` QName=`echo "$TriggerMessage" | cut -c 9-56` ProcessName=`echo "$TriggerMessage" | cut -c 57-104` TriggerData=`echo "$TriggerMessage" | cut -c 105-168` ApplType=`echo "$TriggerMessage" | cut -c 169-172` ApplId=`echo "$TriggerMessage" | cut -c 173-428` EnvData=`echo "$TriggerMessage" | cut -c 429-556` UserData=`echo "$TriggerMessage" | cut -c 557-684` QMgrName=`echo "$TriggerMessage" | cut -c 685-732` Thanks. Chad Robert Broderick <[EMAIL PROTECTED]To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Triggered sh/ksh Script List <[EMAIL PROTECTED] .AC.AT> 06/17/2004 16:19 Please respond to MQSeries List Anybody have a copy of a sh/ksh script that is triggered and handles the TM2 passed data area I want to extract the Triggered Queue name. bobbee _ Check out the coupons and bargains on MSN Offers! http://youroffers.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This transmission is intended only for use by the intended recipient(s). If you are not an intended recipient you should not read, disclose, copy, circulate or in any other way use the information contained in this transmission. The information contained in this transmission may be confidential and/or privileged. If you have received this transmission in error, please notify the sender immediately and delete this transmission including any attachments. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive _ Getting married? Find great tips, tools and the latest trends at MSN Life Events. http://lifeevents.msn.com/category.aspx?cid=married Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Triggered sh/ksh Script
Thanks Neil,
I wrote one that extracts the Triggering Queue Name but I like yours as it
makes all the fields available.
bobbee
From: Neil Casey <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Triggered sh/ksh Script
Date: Fri, 18 Jun 2004 08:00:19 +1000
Hi bobbee,
I use the following to extract info from the TMC2 header in ksh. The script
uses BMCs qmm program, but you don't care about that bit, only the
extraction of the parameters and testing the format.
#
#!/bin/ksh
# eventmsg - Date: Jan2003
# This script will process event messages. It will discard all messages
# except performance events.
# It receives an MQTMC2 format parameter block from runmqtrm.
# It is expected that this MQTMC2 format will remain even with upgrade of
MQ
# if this format changes; then this program will not work.
#
# To use this program, you need to:
# 1. Run a trigger monitor -
#nohup runmqtrm -m QUEUEMGR -q SYSTEM.DEFAULT.INITIATION.QUEUE &
# 2. Subscribe to the BMC Listener Queue -
#qmm put BMC.LISTENER.COM "subscribe A QUEUEMGR CADS.EVENT.QUEUE"
# 3. Define a process to start this script -
#mqsc define process(EVENT.MSG.FORMAT)
applicid('/var/mqm/scripts/eventmsg/e
ventmsg.sh')
# userdata('/var/mqm/scripts/event_report.csv')
# envrdata('/var/mqm/scripts/eventmsg/eventmsg.awk')
# 4. Activate triggering on the event queue -
#mqsc alter ql(CADS.EVENT.QUEUE) process(EVENT.MSG.FORMAT) trigger
trigtype(
first)
# initq(SYSTEM.DEFAULT.INITIATION.QUEUE)
# echo "Trigger message is:" > /var/mqm/scripts/eventmsg.log
# echo $1 >> /var/mqm/scripts/eventmsg.log
# echo "Trigger message ends." >> /var/mqm/scripts/eventmsg.log
export STRUCTNAME=`echo $1 | cut -d' ' -f1 -`
export VERSION=`echo $1 | cut -c5-5 -`
export PARMDATA=`echo $1 | cut -c6- - `
# QNAME is put into MQTMC by runmqtrm
export QNAME=`echo $PARMDATA | cut -d' ' -f1 -`
# AWKSCRIPT is found in the envrdata of the process
export AWKSCRIPT=`echo $PARMDATA | cut -d' ' -f4 -`
# OUTFILE comes from the userdata field of the process
export OUTFILE=`echo $PARMDATA | cut -d' ' -f5 -`
# QMGR is placed in the structure by runmqtrm
export QMGR=`echo $PARMDATA | cut -d' ' -f6 -`
# echo "Structure Name = $STRUCTNAME" >> /var/mqm/scripts/eventmsg.log
# echo "Structure Version = $VERSION" >> /var/mqm/scripts/eventmsg.log
# echo "Parameter Data = $PARMDATA" >> /var/mqm/scripts/eventmsg.log
# echo "Queue Name = $QNAME" >> /var/mqm/scripts/eventmsg.log
# echo "awk Script Name = $AWKSCRIPT" >> /var/mqm/scripts/eventmsg.log
# echo "Output File Name = $OUTFILE" >> /var/mqm/scripts/eventmsg.log
# echo "Queue Manager = $QMGR" >> /var/mqm/scripts/eventmsg.log
if test "x$STRUCTNAME"="xTMC" && test "x$VERSION"="x2" ; then
qmm "set qmgr=$QMGR;delete $QNAME detail" | \
tee -a /var/mqm/scripts/eventmsg.dump | \
nawk -f $AWKSCRIPT >> $OUTFILE ;
else
echo "Invalid Trigger Message $STRUCTNAME $VERSION. Giving Up" >>
\
/var/mqm/scripts/eventmsg.log ;
fi
#===
Neil Casey
National Australia Bank
Southern Star Technology
WebSphere MQ Support
1/122 Lewis Rd Wantirna South
office. +61 3 9886 2375 (x82375)
mobile. +61 414 615 334
|-+->
| | Robert Broderick |
| | <[EMAIL PROTECTED]|
| | OTMAIL.COM> |
| | Sent by: MQSeries |
| | List |
| | <[EMAIL PROTECTED]|
| | .AC.AT> |
| | |
| | |
| | 18/06/2004 07:04 |
| | Please respond to |
| | MQSeries List |
|-+->
>--|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Triggered sh/ksh Script
|
>--|
I take it the 2nd arg it the TM2 data area?
>From: "Wyatt, T. Rob" <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Triggered sh/ksh Script
>Date: Thu, 17 Jun 2004 13:48:27 -0700
>
>Bobbee,
>
>Would you settle for Perl if no MQSeries module was required?
>
>#!/usr/bin/perl -w
>#--#
># trigger.pl
>#
># Script parses a WMQ TMC2 tigger message and runs the application as
># specified in the process definition. Uses unpa
Re: Persistent messages and logging question. [Deutsche Boerse Systems:Virus checked]
Ronald, your understanding of logging, archiving and pageset buffering is wrong, and its hard to explain in a few sentences how it all works. You should first read the concepts and planing guide, and maybe then return with questions. To give you some short answers: if a persistent message arrives, it is written to the log buffer and to the pageset buffer. if the unit of work, that put this message into mq, is committed, then the log buffer is written to the log dataset. now mq can not lose the message. the message itself will be written to the pageset if it is not read within a certain time range (2 checkpoints i think). when a log is full, all of it is archived. the archive log filenames and the related rba ranges are written to the bsds (the bsds is an inventory of your active and archive logs, it also holds checkpoint and restart information). there is nothing that is copied to be kept in the active logs. the removal of the message will also result in log records. the older log records are not touched (why should they be touched)? if mq has to reprocess all the logs e.g. to recover a pageset, it will first find the message being put, and later find the message being get, so everything is fine. if a queuemanager is recycled it will check the pagesets and logs and the proper stored rba values to determine if there is recovery work to do. mq will then read from the rba required to recover (there is forward and backward recovery, depending what work has to be done). if a message has been stored in the pageset, and the rba values are fine (no recovery required), then there is no need for mq to read the log records that have been created when the message arrived. the message is there, ready to be processed (in the pageset). why read it from the log again? recovery of messages in a pageset is only done if the pageset was destroyed and has to be rebuild. in this case, you need to put a backup in place. mq will detect that the rba of this pageset is not correct (quite low) and will reapply all changes that are recorded in the log. Is is all related to media recovery, but the logs are also used for backout handling , hold restart information, backing up cf strucures, I hope this answers some of your questions. Regards, Stefan Ronald Weinger <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 18.06.2004 14:01 Please respond to MQSeries List To: [EMAIL PROTECTED] cc: (bcc: Stefan Raabe/DBS/GDB) Subject: Persistent messages and logging question. [Deutsche Boerse Systems:Virus checked] . Questions on the role of the BSDS and logs on z/OS with persistent messages: Initial state: WMQ for Z/OS V5.3. Qmanager remains running 24x7 for 2 week periods, then is down for MVS maintenance for 8 hours, then back up 24x7 for 2 weeks. Case: A persistent message arrives on a queue immediately after WMQ is brought back up. An active log entry is made(?). The message is not removed from the queue, so after 2 weeks, WMQ is recycled, the message is dumped onto a pageset, and is back 'on the queue' when the Qmanager is brought back. In the initial 2 week period, all sorts of things were going on, so logs were written, new WMQ objects defined, logs were archived, backups taken, etc. When the persistent message first arrived on the queue I assume a log entry was made. Over the 2 week time period many other log entries were made, so there are many archived logs, The active logs are reused after the automatic archiving. Questions: 1) What happens to the initial log entry for the persistent message? Does it get archived or copied to a location in an active log during the archive process? If it is archived, when the Qmgr was recycled does it have to dig through all the archived logs to find the entry for that one message? 2) What role does the BSDS play? 3) When the message is eventually removed, does the original log entry have to be 'cancelled'? The concern is, obviously, is the process cost of recovery of messages that, contrary to the Ten Commandments, are 'stored' on queues. The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. --Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen.Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bittesofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet.The information contained in this message is confidential or protected bylaw. If you are not the intended recipient, please contact the sender
Re: Question on MQ logging
Guys, I have asked this question before (please see my email below), but i think i was more interested in getting numbers for my logging issue that i did not bother asking. Now i am at a point where i need to understand if the design makes any sense. ** * all messages in the queue being marked persistent * Using static queues * size of each message will be around 3MB * Also this is a design where each QM may have around 1000 or so users (each user has a queue for herself/himself) but at a given time only 150 users (queues) would be trying to use the Queue manager. (hhmmm that makes me think, is it ok to have that many users connect to the same QM at the same time or introducing a diff QM would be better option?) ** Does or Can a Queue Manager really support 1000 queues ? Assuming not more than 200 people connect at the same time. Because this design involves static queues it could be storage intensive right ? If so, does anyone have an idea of what numbers we are looking at ? Like storage wise or machine spec ? Also i hope there are not any legalities involved in this, especially because the clients are freely available. Thanks in advance, Usha At 11:10 AM 9/19/2003 -0400, you wrote: Why not make them as big as possible? Even the dinkiest server nowadays has gigs and gigs of space. I use crtmqm -lc -lf 16384 -lp 40 -ls 23 QMNAME. And set your LogBufferSize to 512 if you have descent memory on the server. The above values are for a 5.3 queue manager. -Original Message- From: Usha Suryadevara [mailto:[EMAIL PROTECTED]] Sent: Friday, September 19, 2003 11:01 AM To: [EMAIL PROTECTED] Subject: Question on MQ logging Hello all, I am using MQ for the first time and am trying to come up with some standard values for configuring the QM. Part of this design involves: * all messages in the queue being marked persistent * size of each message will be around 3MB * Also this is a design where each QM may have around 1000 or so users (each user has a queue for herself/himself) but at a given time only 150 users (queues) would be trying to use the Queue manager. (hhmmm that makes me think, is it ok to have that many users connect to the same QM at the same time or introducing a diff QM would be better option?) At this point i was wondering if anyone knows what the optimum values (a range or approximate values are good enough) of *log file size *primary files * secondary files would be, if i am using Circular logging. Any information addressing the above questions would help me and my company a lot. Thanks in advance, Usha This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential 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 email and delete this communication and destroy all copies.
Error / Memory Leak MQ Series 5.2
Hi All We have a memory leak in MQ Series implementation caused by some threads hanging in SessionAsyncHelper implementation which is causing abnormal creation of com.ibm.mq.Pint objects. I am aware of a resolution / fix for MQ series 5.3 for this issue http://www-1.ibm.com/support/docview.wss?uid=swg1IY48122 Wondering if there is a similar fix for 5.2 - our system is currently running into memory issues and we cannot move off of 5.2 currently. Thanks in advance Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Triggered sh/ksh Script
Bobbee- Maybe this is what you are looking for. #!/bin/ksh TriggerMessage=$1 StrucId=`echo "$TriggerMessage" | cut -c 1-4` Version=`echo "$TriggerMessage" | cut -c 5-8` QName=`echo "$TriggerMessage" | cut -c 9-56` ProcessName=`echo "$TriggerMessage" | cut -c 57-104` TriggerData=`echo "$TriggerMessage" | cut -c 105-168` ApplType=`echo "$TriggerMessage" | cut -c 169-172` ApplId=`echo "$TriggerMessage" | cut -c 173-428` EnvData=`echo "$TriggerMessage" | cut -c 429-556` UserData=`echo "$TriggerMessage" | cut -c 557-684` QMgrName=`echo "$TriggerMessage" | cut -c 685-732` Thanks. Chad Robert Broderick <[EMAIL PROTECTED]To: [EMAIL PROTECTED] OTMAIL.COM> cc: Sent by: MQSeries Subject: Triggered sh/ksh Script List <[EMAIL PROTECTED] .AC.AT> 06/17/2004 16:19 Please respond to MQSeries List Anybody have a copy of a sh/ksh script that is triggered and handles the TM2 passed data area I want to extract the Triggered Queue name. bobbee _ Check out the coupons and bargains on MSN Offers! http://youroffers.msn.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This transmission is intended only for use by the intended recipient(s). If you are not an intended recipient you should not read, disclose, copy, circulate or in any other way use the information contained in this transmission. The information contained in this transmission may be confidential and/or privileged. If you have received this transmission in error, please notify the sender immediately and delete this transmission including any attachments. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Gale L. Dillehay/IT/SEARS is out of the office.
I will be out of the office starting 06/18/2004 and will not return until 06/21/2004. I will respond to your message when I return. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Persistent messages and logging question.
Questions on the role of the BSDS and logs on z/OS with persistent messages: Initial state: WMQ for Z/OS V5.3. Qmanager remains running 24x7 for 2 week periods, then is down for MVS maintenance for 8 hours, then back up 24x7 for 2 weeks. Case: A persistent message arrives on a queue immediately after WMQ is brought back up. An active log entry is made(?). The message is not removed from the queue, so after 2 weeks, WMQ is recycled, the message is dumped onto a pageset, and is back 'on the queue' when the Qmanager is brought back. In the initial 2 week period, all sorts of things were going on, so logs were written, new WMQ objects defined, logs were archived, backups taken, etc. When the persistent message first arrived on the queue I assume a log entry was made. Over the 2 week time period many other log entries were made, so there are many archived logs, The active logs are reused after the automatic archiving. Questions: 1) What happens to the initial log entry for the persistent message? Does it get archived or copied to a location in an active log during the archive process? If it is archived, when the Qmgr was recycled does it have to dig through all the archived logs to find the entry for that one message? 2) What role does the BSDS play? 3) When the message is eventually removed, does the original log entry have to be 'cancelled'? The concern is, obviously, is the process cost of recovery of messages that, contrary to the Ten Commandments, are 'stored' on queues. The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message.
Re: WMQ Workflow and Content Manager integration
Thanks Emile, nice to hear from a fellow South African! Francois van der Merwe Senior IT Specialist: IBM MQSeries Certified Specialist, Solutions Expert & Developer IBM, Cape Town, South Africa +27 (0)82 556 9467 / +27 (0)21 402 5597 [EMAIL PROTECTED], yahoo messenger fmerwe2001 Emile Kearns <[EMAIL PROTECTED]To: [EMAIL PROTECTED] TEMS.CO.ZA>cc: Sent by: MQSeries Subject: Re: WMQ Workflow and Content Manager integration List <[EMAIL PROTECTED] AC.AT> 18/06/2004 08:34 Please respond to MQSeries List Currently involved with such a project CM has its own WF but it looks immature. >From my research, it looks fairly easy to initiate CM from MQ WF, but I have not tried it yet. As things progresses here, I will let you know. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Francois Van der Merwe1 Sent: 18 June 2004 08:08 AM To: [EMAIL PROTECTED] Subject: WMQ Workflow and Content Manager integration Anybody did any WMQ WF integration with Content Manager? Is it easy to allow WMQ WF to call / initiate CM WF? I've got many more questions, so any directions for where I can get more information will REALLY be appreciated. Francois van der Merwe Senior IT Specialist: IBM MQSeries Certified Specialist, Solutions Expert & Developer IBM, Cape Town, South Africa +27 (0)82 556 9467 / +27 (0)21 402 5597 [EMAIL PROTECTED], yahoo messenger fmerwe2001 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Any views expressed in this message are those of the individual sender, and T-Systems South Africa (Pty) Ltd accepts no liability therefore, except where the sender specifically states them to be those of T-Systems South Africa (Pty) Ltd. Although this message has been scanned for the possible presence of computer viruses prior to despatch, T-Systems South Africa (Pty) Ltd cannot be held responsible for any viruses or other material transmitted with, or as part of, this message. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: z/os Channel Exits
Thanks to all that responded. I believe we have the examples needed. Pat Ferzola -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Pat Ferzola Sent: Thursday, June 17, 2004 11:41 AM To: [EMAIL PROTECTED] Subject: z/os Channel Exits Does anyone have a z/os channel exit that we can use as a sample. It needs to be able to track input and output to be able to support response time SLA's. Thanks. Pat Ferzola The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you
