Re: BITSTREAM changes between MQSI version 2.0.2 and 2.1

[Kevin Tobin]

In WMQI CSD3 the BITSTREAM functionality was broken.  I believe this has been addressed and will be corrected in the next release.
The ASBITREAM function though not documented yet - does work.  If you need further assistance please contact me.

Cheers

Kevin

Kevin Tobin
Senior IT Specialist 
IBM WebSphere Services Asia Pacific
Level 9, 601 Pacific Hwy, St Leonards, 
Sydney NSW 2000
Phone:  +61 2 947-88249 
Fax:       +61 2 947-88467
Mobile    0421-052-812   -  International :  +61 421-052-812
e-Mail:    [EMAIL PROTECTED]

Re: Signalling

[Richard Tsujimoto]

Title: Signalling



I noticed that you set the MQGMO-WAIT option just 
prior to the second call MQGET, but didn't do so for the first call to 
MQBGET.  The following excerpt from the Programmer's Ref. manual may be 
helpful:
 
On OS/390, the following points apply:-If it is 
desirable for the application to proceed with other work while waiting for the 
message to arrive, consider using the signal option (MQGMO_SET_SIGNAL) instead. 
However the signal option is environment specific, and so should not be used by 
applications which are intended to be portable between different 
environments.-If there is more than one MQGET call waiting for the same 
message, with a mixture of wait and signal options, each waiting call is 
considered equally. It is an error to specify MQGMO_SET_SIGNAL with MQGMO_WAIT. 
It is also an error to specify this option with a queue handle for which a 
signal is outstanding.
 
I also noticed that you didn't wait on the ecb 
after the second call to MQBGET.

  - Original Message - 
  From: 
  Voges, P. 
  (Pieter) 
  To: [EMAIL PROTECTED] 
  Sent: Friday, November 29, 2002 6:10 
  AM
  Subject: Signalling
  
  Please help. 
  I have started getting intermittent 
  2069 errors for the first time after more than 5 years in production. We have 
  attempted to recompile and link with the 5.2 libraries but continue to get 
  this error.
  Currently I am in a LOOP (in a CICS 
  long running task (don't ask) ) processing a MQ,Q 
  
Copy the default values for the 
mqmd and mqgmo structures 
Move 
mqgmo-set-signal   to mqgmo-options 
add mqgmo-no-syncpoint to 
mqgmo-options 
move 
mqwi-unlimited   to mqgmo-waitinterval 

set the ECB to zero. 
setup mqgmo-signal1 with ECB 
address 
call 
MQGET  
    
    
    
    
     //First GET (with Signal) 
if  return-code = 0 
    Go 
Exit. 
//Ok lets process it. 
if  NOT WARNING OR not 
mqrc-signal-request-accepted   //Inform the Bridge and 
ABEND 
CICS WAIT EXTERNAL on the 
SINGLE ECB. 
evaluate 
ecb  

    when 
mqec-msg-arrived   
continue   
    when 
mqec-wait-interval-expired   go e-401m-no-msg   
    when 
other    
go e-401o-ecb-error 
end-evaluate 

Copy the default values for the 
mqmd and mqgmo structures 
move mqgmo-no-syncpoint to 
mqgmo-options 
add 
mqgmo-wait   
to mqgmo-options 
move 
mqwi-unlimited  to 
mqgmo-waitinterval 
call 
MQGET  
    
    
    
    
     //Second Get (after wait). 
if  return-code not = 
0    

    if  
reason = mqrc-no-msg-available 
    go 
e-401m-no-msg 

    
else 

    go 
e-401n-mq-failed  

    
end-if   

end-if   

go exit 
    
    
    
    
    
    // Ok Lets Process it. 

  MY QUESTION. How do I handle the 2069. DO I 
  
1) Only reset the ECB after the 
WAIT EXTERNAL 

  This will allow the WAIT 
  EXTERNAL to Return as soon as anything is posted to the ECB address even 
  if the First MQ get returned a 0(ok) reply?
2) Only set the mqgmo-set-signal 
when I get a  mqrc-signal-request-accepted again even if the previous get was 
successful.
3) Process the 2069 as I do the 
signal-request-accepted ie just drop into the wait external 4) Drop the wait option on the second 
get. 5) Combine 1 & 
3 6) Combine 1 & 3 
& 4 and expect the 2nd MQGET (after the wait external) to return NO 
MSG. 
  5 is my gut feel for this fix. 
  6 may be the solution 
  depending on how or why this MQRC-SIGNAL-OUTSTANDING  is being 
  returned. 
  If anyone as a solution of has a 
  flow chart of how these return codes get set, it would be most 
  appreciated 
  Thanks 
  André de 
  JagerIT OPS SA: S&M Retail and 
  Corporatecell 083 326 5243 
  ( 27(21) 488 8235 Speed 60888* 
  [EMAIL PROTECTED] 
  
 -Original 
Message- From:   
Voges, P. (Pieter)  Sent:   29 
November 2002 05:25 To: De 
Jager, A. (Andre); Ramjee, P. (Piyoosh); Strydom, G. (Gerard) 
Cc: CICS Subject:    RE: nxxpbtoz on prod. 
Please let me know how it is doing 
as soon as you have some info. 
Thank you Pieter 
VogesMQ SupportNedcor Bank LimitedTel: (011) 881 4410Sel: 083 6455 
300E-mail: [EMAIL PROTECTED]  


   

Searching for ESQL statements in the Configuration Manager

[Kulbir S. Thind]

Hi,

Its OK, I've found a way.  For those that are interested we've exported our message flows and have performed a search in the XML file that is created.

Regards,

Kulbir.
- Forwarded by Kulbir S Thind/SBH/Corp/SB_PLC on 29-Nov-2002 17:42 -




Kulbir S Thind

29-Nov-2002 17:35

        
                eAIM    D2 GSK House    (020) 8047 2820

        To:        MQSERIES

        cc:        
        Subject:        Searching for ESQL statements in the Configuration Manager

Hi there,

We wanted to see if we have used the BITSTREAM ESQL statement in any of the message flows in our Configuration Manager.  Rather than look at every node and examining the ESQL manually is there a database table (or any other method) that we can look at to see the ESQL statements in the message flows?  Just want to speed up the process for doing this search if possible!

Cheers,

Kulbir.

Searching for ESQL statements in the Configuration Manager

[Kulbir S. Thind]

Hi there,

We wanted to see if we have used the BITSTREAM ESQL statement in any of the message flows in our Configuration Manager.  Rather than look at every node and examining the ESQL manually is there a database table (or any other method) that we can look at to see the ESQL statements in the message flows?  Just want to speed up the process for doing this search if possible!

Cheers,

Kulbir.

BITSTREAM changes between MQSI version 2.0.2 and 2.1

[Kulbir S. Thind]

Hi there,

We are in the process of moving from MQSI version 2.0.2 (no CSD) to MQSI version 2.1 (CSD 3) and have hit a problem with the BITSTREAM function.

It looks like the function works correctly in MQSI 2.0.2 but doesn't in the latest release.  I'm attaching the relevant pieces of trace files of the same flow running on the two different versions of MQSI. 

MQSI 2.0.2 Trace - 



MQSI 2.1 Trace - 



Here is the code we are executing and having problems with:

*
-- Maintain DestinationList
SET OutputDestinationList = InputDestinationList;

-- Declare Variables
Declare CMH_LENGTH INTEGER;
 
SET CMH_LENGTH = 475;

-- Set Output message to be CMH in BLOB format plus the original message.
SET OutputRoot."BLOB"."BLOB" = BITSTREAM(InputRoot.MRM) || SUBSTRING(InputDestinationList.Destination.Scratchpad.Msg FROM CMH_LENGTH + 1);
*

From the trace files it can be seen that the InputRoot.MRM structure is populated and the problem lies in the ESQL SET OutputRoot."BLOB"."BLOB" statement.  The MQSI 2.0.2. release manages to successfully BITSTREAM the InputRoot.MRM and assign it to the OutputRoot."BLOB"."BLOB", however in version 2.1 the BITSTREAM function returns an empty string even though the trace shows a value is assigned to InputRoot.MRM.

Has anyone seen this before?  Is this a known bug in MQSI 2.1?

Thanks in advance,

Kulbir.

P.S.  We're working with MQSeries 5.3 on Windows 2000






[EMAIL PROTECTED]

Sent by: "MQSeries List" <[EMAIL PROTECTED]>
07-Oct-2002 17:55
Please respond to "MQSeries List" <[EMAIL PROTECTED]>

        
                        

        To:        MQSERIES

        cc:        
        Subject:        Re: Maximum connections to mqseries


There's also a MAXCONNETIONS parameter which must be set.





                      DAN.CAPODICCI@GE         To:      [EMAIL PROTECTED]
                      CAPITAL.COM              cc:
                      Sent by:                 Subject: Re: Maximum connections to mqseries
                      MQSERIES@akh-wie
                      n.ac.at


                      10/07/2002 12:50
                      PM
                      Please respond
                      to MQSERIES





Hi

There is a parameter that controls the limit of simultaneous connections to
a qmanager and as you have discovered, the default setting is 100.
Depending on your OS, you can up this number accordingly. If you are
running on UNIX, you can use a line such as this in your qm.ini to increase
that number:

Channels:
   MaxChannels=200

On NT/2000, there is a "channels" tab on your MQ Services panel, etc.

Thanks
Dan

-Original Message-
From: Mittal, Gaurav [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 07, 2002 12:30 PM
To: [EMAIL PROTECTED]
Subject: Maximum connections to mqseries


Hi All,
is there a maximum number of simultaneous connections that can be opened to
mqseries 5.2
For us after 100 connections it fails to create a queuemanager object and
gives following error

MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
MQJE001: Completion Code 2, Reason 2009
MQ exception occurred : Completeion code 2 Reason code 2009
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
        at
com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:166)
        at
com.ibm.mq.MQClientManagedConnectionFactoryJ11.
_createManagedConnection(MQCl
ientManagedConnectionFactoryJ11.j
ava:196)
        at
com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQCli

entManagedConnectionFactoryJ11.ja
va:213)
        at
com.ibm.mq.StoredManagedConnection.(StoredManagedConnection.java:80)
        at
com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionMa

nager.java:150)
        at
com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:560)
        at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:509)
        at com.ibm.mq.MQQueueManager.(MQQueueManager.java:286)
        at MqConnectTest.(MqConnectTest.java:42)
        at MqConnectTest.main(MqConnectTest.java:21)

Regds
Gaurav Sai Mittal
Wipro-EAI Consultant
952-324-0243(w)
952-941-5658(h)

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





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or state

Re: Sec Channel Exit code

[Michael Hecht]

I would like a copy of your article.

Thanks,

Michael Hecht
DTCC
[EMAIL PROTECTED]

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: Urgent Help needed on MQJMS

[mmh]

Have you resolved this issue? If not, could you please post the dump of
MQ RFH2 message that you have constructed. Just in case ... something wrong
in message construction.

FYI, I have been able to do this.

Manju

---Original Message---

From: MQSeries List
Date: Tuesday, November 26, 2002 02:56:54 PM
To: [EMAIL PROTECTED]
Subject: Urgent Help needed on MQJMS

Hi,

I have an MQ application which puts a message in a queue after setting the
RFH2 header using native Java APIs. Another application using MQJMS latest
ma88 pac,
picks the message from the queue. I have created q and qcf using JMSAdmin
and I am able to read the message but  folder which should get
populated from
RFH2 header usr folder values is coming as null. If someone can help me in
identifying the issue it will be great.

Looking for an early response.

Regards,
Vinay

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: MQSeries and MQSI process names

[Emile Kearns]

Title: Message



Will 
this do?
 


  
  
AMQPCSEA.EXE 
The command server 
  
AMQHASMN.EXE 
The logger 
  
AMQHARMN.EXE 
Log formatter (linear logs only) 
  
  
AMQZLLP0.EXE 
Checkpoint process 
  
AMQZLAA0.EXE 
LQM agents 
  
AMQZFUMA.EXE 
OAM process 
  
AMQZTRCN.EXE 
Trace 
  
AMQZXMA0.EXE 
Execution controller 
  
AMQXSSVN.EXE 
Shared memory servers 
  
AMQRRMFA.EXE 
The repository process (for 
  clusters) 
  
AMQZDMAA 

Deferred message 
  processor 
 
 
Emile Kearns
Office telephone no: 
+27(0)114586670
 
SOFTWARE 
FUTURESthe business advantageProud member of MGXwww.softwarefutures.com

  
  -Original Message-From: Matt Gurney 
  [mailto:[EMAIL PROTECTED]] Sent: 28 November 2002 
  12:27To: [EMAIL PROTECTED]Subject: MQSeries and 
  MQSI process namesIn the 
  past a document has been posted on the list describing all of the various 
  MQSeries process names, for all platforms,  and a description of what 
  they do.  Can someone please repost that document.  From memory, I 
  believe that document did not include MQSI processes, if anyone has something 
  similar for MQSI, that would be great too. I tried looking in the listserver archive, but couldn't 
  locate what I am after.Thanks in 
  advance,Matt Gurney 

Signalling

[Voges, P. (Pieter)]

Title: Signalling





Please help.





I have started getting intermittent 2069 errors for the first time after more than 5 years in production. We have attempted to recompile and link with the 5.2 libraries but continue to get this error.

Currently I am in a LOOP (in a CICS long running task (don't ask) ) processing a MQ,Q

Copy the default values for the mqmd and mqgmo structures
Move mqgmo-set-signal   to mqgmo-options
add mqgmo-no-syncpoint to mqgmo-options
move mqwi-unlimited   to mqgmo-waitinterval 
set the ECB to zero.
setup mqgmo-signal1 with ECB address
call MQGET                       //First GET (with Signal)

if  return-code = 0     Go Exit. //Ok lets process it.
if  NOT WARNING OR not mqrc-signal-request-accepted   //Inform the Bridge and ABEND
CICS WAIT EXTERNAL on the SINGLE ECB.

evaluate ecb  
    when mqec-msg-arrived   continue   
    when mqec-wait-interval-expired   go e-401m-no-msg   
    when other    go e-401o-ecb-error
end-evaluate 

Copy the default values for the mqmd and mqgmo structures
move mqgmo-no-syncpoint to mqgmo-options
add mqgmo-wait   to mqgmo-options
move mqwi-unlimited  to mqgmo-waitinterval
call MQGET                       //Second Get (after wait).
if  return-code not = 0    
    if  reason = mqrc-no-msg-available
    go e-401m-no-msg 
    else 
    go e-401n-mq-failed  
    end-if   
end-if   
go exit                         // Ok Lets Process it.


MY QUESTION.
How do I handle the 2069.
DO I

1) Only reset the ECB after the WAIT EXTERNAL 

This will allow the WAIT EXTERNAL to Return as soon as anything is posted to the ECB address even if the First MQ get returned a 0(ok) reply?

2) Only set the mqgmo-set-signal when I get a  mqrc-signal-request-accepted again even if the previous get was successful.

3) Process the 2069 as I do the signal-request-accepted ie just drop into the wait external
4) Drop the wait option on the second get.
5) Combine 1 & 3
6) Combine 1 & 3 & 4 and expect the 2nd MQGET (after the wait external) to return NO MSG.


5 is my gut feel for this fix. 
6 may be the solution depending on how or why this MQRC-SIGNAL-OUTSTANDING  is being returned.


If anyone as a solution of has a flow chart of how these return codes get set, it would be most appreciated


Thanks


André de Jager
IT OPS SA: S&M Retail and Corporate
cell 083 326 5243 ( 27(21) 488 8235 Speed 60888
* [EMAIL PROTECTED] 


 -Original Message-
From:   Voges, P. (Pieter)  
Sent:   29 November 2002 05:25
To: De Jager, A. (Andre); Ramjee, P. (Piyoosh); Strydom, G. (Gerard)
Cc: CICS
Subject:    RE: nxxpbtoz on prod.


Please let me know how it is doing as soon as you have some info.



Thank you 
Pieter Voges
MQ Support
Nedcor Bank Limited
Tel: (011) 881 4410
Sel: 083 6455 300
E-mail: [EMAIL PROTECTED] 




 -Original Message-
From:   De Jager, A. (Andre)  
Sent:   28 November 2002 03:45
To: Voges, P. (Pieter); Ramjee, P. (Piyoosh); Strydom, G. (Gerard)
Cc: CICS
Subject:    nxxpbtoz on prod.


The new version of NZPPINTZ is now in emerbin0.load on prod and has been phased into
ftrpprn0.


From Yesterdays stats we can expect bto to fall over anytime after 10pm.


New version is the same (4.0) version as targbin0.load but compiled with the 5.2 copy books and libs.


André de Jager
IT OPS SA: S&M Retail and Corporate
cell 083 326 5243 ( 27(21) 488 8235 Speed 60888
* [EMAIL PROTECTED] 

Re: How to know the channel stopped

[Christian Wolfhagen]

Hirosi,

This sounds like a case of using MQ for synchronous transactions, which is not in line 
with MQ's asynchronous nature. The whole idea is that you may put data onto the system 
and then forget about it. MQ will make sure that the data reaches its target.
You may put the display channel into your programs using pcf commands or if you rely 
on a reply coming back from the recipient there are ways of designing this using 
expiry on the messages etc. All depends on what you are doing.

Christian Wolfhagen
Senior Consultant
 
Cressida Technology Ltd.

Phone: +45  4848 2593
Mobile: +45  2176 7113
e-mail: [EMAIL PROTECTED]
WWW: http://www.cressida.info

Attachments within this mail have been automatically compressed using ZipMail for 
Notes and Exchange to save you Time, Storage and Bandwith!
See www.cressida.info/products_mk.shtml for details!


-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED]] On Behalf Of 
‚”‚‚‡‚•‚”‚‰
Sent: 29. november 2002 06:09
To: [EMAIL PROTECTED]
Subject: Re: How to know the channel stopped

In message <[EMAIL PROTECTED]>
   "Re: How to know the channel stopped"
   "Michael F Murphy/AZ/US/MQSolutions <[EMAIL PROTECTED]>" wrote:

Thanks a lot for infos.
I don't like to discuss about system setting or how to error recovery.
Many applications sends messages to remote system as a request, and
they issue timeout/no return message 2033.
In some case a remote transaction shoud have crashed
only for this message, and another request may go good.

If applications can know the channel-stopping, it can display message
box to say "system is down, all msg not available".
If cann't, he cann't say this error(2033) is limitted or prevalent to
current all system.

--
Hirosi Taguti
[EMAIL PROTECTED]

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