Compiling MQ applications in 64 bit mode.

2004-12-01 Thread Voges, P. (Pieter)
Title: Compiling MQ applications in 64 bit mode.





Please help urgently...


One of our developers is trying to compile MQ 5.3 client and server applications written in c on a AIX 5.2 server. When compiling them in 32 bit mode, it works fine. When compiling in 64 bit mode, it cant find the MQGET's, MQPUT's etc... He urgently needs to compile these as it will be interacting with other 64 bit applications already running on these servers. Are there different libraries for 64 bit applications, and if so, where can I find them.

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









Nedbank 
Limited Reg No 1951/09/06Directors: WAM Clewlow (Chairman)  Prof MM 
Katz (Vice-chairman)  ML Ndlovu (Vice-chairman)  TH Nyasulu 
(Vice-chairman)  TA Boardman (Chief Executive)  CJW Ball  MWT 
Brown  RG Cottrell  BE Davison  N Dennis+  Prof B 
Figaji  MJ Levett  JB Magwaza  ME Mkwanazi  PF Nhleko  
JVF Roberts+  CML Savage  JH Sutcliffe+  
(+British) Company Secretary: GS 
Nienaber 01.07.2004
This 
email and any accompanying attachments may contain confidential and proprietary 
information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution of or taking any 
action based on this information is prohibited. 
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability 
or responsibility for any interception, corruption, destruction, loss, late 
arrival or incompleteness of or tampering or interference with any of the 
information contained in this email or for its incorrect delivery or 
non-delivery for whatsoever reason or for its effect on any electronic device of 
the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.








FW: Error with CSD7 on AIX

2004-10-26 Thread Voges, P. (Pieter)
Title: FW: Error with CSD7 on AIX





Hi Everyone


We had a very strange problem when applying CSD07 on MQ 5.3 on AIX. After starting the QMGR with the applied maintenance the following errors came up as per the error log.  

Despite these errors, the queue manager was up and the channels started normally.  I could also define, display and delete a test queue.  We believe these errors were caused by the application still being connected to the queue manager when it came down. The channels not coming up were MVS channels and the MVS QMGR was down for an IPL. We are not using clustering and the problem seems to be initially that the repository manager first started up and then abended. All error codes point to 2009 (connection broken.)

The command server was not running and could not be started as the command queue was in use. The problem was that there were some "unix domain socket" which kept on increasing the whole day under the MQ execution controller (amqZxma0). We had to stop and restart the QMGR to resolve this. 

Has anyone seen something similar before?


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



 


The error log looks as follows:


10/24/04  04:09:15
AMQ9542: Queue manager is ending.


EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
- amqrmssa.c : 2094 ---
10/24/04  04:09:28
AMQ8004: WebSphere MQ queue manager 'ZANC000.SHREK' ended.


EXPLANATION:
WebSphere MQ queue manager 'ZANC000.SHREK' ended.
ACTION:
None.
---
10/24/04  04:09:40
AMQ9542: Queue manager is ending.


EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
- amqrmssa.c : 2094 ---
10/24/04  04:36:19
AMQ8003: WebSphere MQ queue manager 'ZANC000.SHREK' started.


EXPLANATION:
WebSphere MQ queue manager 'ZANC000.SHREK' started.
ACTION:
None.
---
10/24/04  04:36:19
AMQ9410: Repository manager started


EXPLANATION:
The repository manager started successfully.
ACTION:
None.
---
10/24/04  04:36:19
AMQ8024: WebSphere MQ channel initiator started.


EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
---
10/24/04  04:36:19
AMQ9002: Channel 'SHREK.TO.CSQ3' is starting.


EXPLANATION:
Channel 'SHREK.TO.CSQ3' is starting.
ACTION:
None.
---
10/24/04  04:36:39
AMQ9510: Messages cannot be retrieved from a queue.


EXPLANATION:
The attempt to get messages from queue 'SYSTEM.CLUSTER.COMMAND.QUEUE' on queue
manager 'ZANC000.SHREK' failed with reason code 2009.
ACTION:
If the reason code indicates a conversion problem, for example
MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise,
ensure that the required queue is available and operational.
- amqrrmfa.c : 4434 ---
10/24/04  04:36:39
AMQ9447: Unable to backout repository changes.


EXPLANATION:
Following an error, the repository manager tried to backout some updates to the
repository, but was unsuccessful. The repository manager terminates.
ACTION:
If the repository manager subsequently restarts successfully, this message can
be ignored.  If the repository manager does not restart, contact your IBM
support center for assistance.
- amqrrmfa.c : 32257 --
10/24/04  04:36:39
AMQ9510: Messages cannot be retrieved from a queue.


EXPLANATION:
The attempt to get messages from queue 'SYSTEM.CHANNEL.INITQ' on queue manager
'ZANC000.SHREK' failed with reason code 2009.
ACTION:
If the reason code indicates a conversion problem, for example
MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise,
ensure that the required queue is available and operational.
- amqrimna.c : 873 
10/24/04  04:36:39
AMQ9510: Messages cannot be retrieved from a queue.


EXPLANATION:
The attempt to get messages from queue 'SYSTEM.CLUSTER.REPOSITORY.QUEUE' on
queue manager 'ZANC000.SHREK' failed with reason code 2009.
ACTION:
If the reason code indicates a conversion problem, for example
MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise,
ensure that the required queue is available and operational.
- amqrfica.c : 404 
10/24/04  04:36:39
AMQ9411: Repository manager ended normally.


EXPLANATION:
The repository ma

Re: MQ Monitoring of CPU Utilization

2004-08-18 Thread Voges, P. (Pieter)
Title: MQ Monitoring of CPU Utilization



Please
respond to the list on this one - I would also like to
know...
 

Thank you Pieter VogesMQ SupportNedcor LimitedTel:
(011) 881 4410Sel: 083 6455 300E-mail:
[EMAIL PROTECTED]



  -Original Message-From: Herd, Stewart
  [mailto:[EMAIL PROTECTED]Sent: Wednesday, August 18, 2004
  1:04 PMTo: [EMAIL PROTECTED]Subject: MQ Monitoring
  of CPU Utilization
  Dear Listers,  
  Can anyone share what methods or tools they currently utilize to monitor and
  tune MQ 5.3 on Mainframe, specifically CPU utilization in a high volume
  environment.
  Much appreciated 
  Stewart 




Nedbank
Limited Reg No 1951/09/06Directors: WAM Clewlow (Chairman)  Prof MM
Katz (Vice-chairman)  ML Ndlovu (Vice-chairman)  TH Nyasulu
(Vice-chairman)  TA Boardman (Chief Executive)  CJW Ball  MWT
Brown  RG Cottrell  BE Davison  N Dennis+  Prof B
Figaji  MJ Levett  JB Magwaza  ME Mkwanazi  PF Nhleko 
JVF Roberts+  CML Savage  JH Sutcliffe+ 
(+British) Company Secretary: GS
Nienaber 01.07.2004
This
email and any accompanying attachments may contain confidential and proprietary
information.  This information is
private and protected by law and, accordingly, if you are not the intended
recipient, you are requested to delete this entire communication immediately and
are notified that any disclosure, copying or distribution of or taking any
action based on this information is prohibited. 
Emails
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability
or responsibility for any interception, corruption, destruction, loss, late
arrival or incompleteness of or tampering or interference with any of the
information contained in this email or for its incorrect delivery or
non-delivery for whatsoever reason or for its effect on any electronic device of
the recipient.
If
verification of this email or any attachment is required, please request a
hard-copy version.






URGENT MQ QUEUE SHARING

2004-07-27 Thread Voges, P. (Pieter)
Title: URGENT MQ QUEUE SHARING 





I urgently need any help I can get as a matter of urgency. Please reply to my personal mail adress as I struggle to subscribe to the list again. I need to do a presentation to management on MQ queue sharing in a sysplex environment. I got the Redbook. Is there anybody out there with a slideshow or anything that can help me to present the topic to management.

Any help will be appreciated.


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



  






 This 
email and any accompanying attachments may contain confidential and proprietary 
information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution of or taking any 
action based on this information is prohibited.
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability 
or responsibility for any interception, corruption, destruction, loss, late 
arrival or incompleteness of or tampering or interference with any of the 
information contained in this email or for its incorrect delivery or 
non-delivery for whatsoever reason or for its effect on any electronic device of 
the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.






Re: amqcrsta process

2004-01-13 Thread Voges, P. (Pieter)
Title: RE: amqcrsta process





Hi Bill


The main creator of amqcrsta processes are channel connections when using the Inetd Unix listener. A new process will be created for every channel connection. If the amount of processes seems to be a problem you can rather use the MQ listener which will only create 1 runmqlsr process. We had the same thing happening. Please note that IBM's recommendation is that the Inetd listener is better prior to 5.3, but from version 5.3 the MQ listener is better since it incorporates a threaded approach.(Start a number of threads under one process and then start additional processes.) We rolled out 5.3 a while ago and are very happy with the results using the MQ listener. 

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





-Original Message-
From: Bill Anderson [mailto:[EMAIL PROTECTED]]
Sent: 13 January 2004 08:07
To: [EMAIL PROTECTED]
Subject: amqcrsta process



I am tracking down a problem on our legacy MQ server which is MQ 5.2
running on AIX 4.3.3. That machine has been bounced 3 times in one week
because of problems with system recourses (or so it appears). We get errors
complaining that a semaphore cannot be obtained, and the process requesting
it timed out. The queue manager becomes unresponsive. that is to say you
can't talk to it using runmqsc.


Because we are migrating customers off that platform on to WMQ 5.3, there
are only about 10 active connections remaining on it (and only one qmgr is
there). I noticed that if you look for the number of processes owned by mqm
there are around 95, of which about 49 are amqscrsta process. I have never
really counted the number of amqscrsta processes on a given machine but
that seems very high to me.


Any thoughts?



Bill Anderson
Senior Systems Analyst
SITA Atlanta, GA
770-303-3503 (office)
404-915-3190 (cell)
[EMAIL PROTECTED]
http://www.mconnect.aero/


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 
email and any accompanying attachments may contain confidential and proprietary 
information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution of or taking any 
action based on this information is prohibited. 
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability 
or responsibility for any interception, corruption, destruction, loss, late 
arrival or incompleteness of or tampering or interference with any of the 
information contained in this email or for its incorrect delivery or 
non-delivery for whatsoever reason or for its effect on any electronic device of 
the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.






Support for MQ5.2

2003-11-25 Thread Voges, P. (Pieter)
Title: Support for MQ5.2





The question of support for different MQ releases and the dates on which it is dropped have been asked so many times that I will be surprised if anybody responds to this. The problem is that the dates I get from IBM locally, the dates I see on IBM's international website and the dates people mention on this list differs. As I am working for a major bank in South Africa and are tasked to insure that we are always running on a supported version I really need some clear answers on this. According to my latest info support for 5.2 on the distributed platforms end on December 31, 2003 and on OS/390 the date is April 30, 2004. Can anybody confirm this PLEASE...  

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









This 
email and any accompanying attachments may contain confidential and proprietary 
information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution of or taking any 
action based on this information is prohibited. 
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability 
or responsibility for any interception, corruption, destruction, loss, late 
arrival or incompleteness of or tampering or interference with any of the 
information contained in this email or for its incorrect delivery or 
non-delivery for whatsoever reason or for its effect on any electronic device of 
the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.






Re: inet2 vs MQ listener (UNIX)

2003-07-30 Thread Voges, P. (Pieter)
Title: RE: inet2 vs MQ listener (UNIX)





http://www.developer.ibm.com/tech/faq/individual/0,,2:28060,00.html


Thank you 
Pieter Voges 
MQ Support 
Nedcor Limited 
Tel: (011) 881 4410 
Sel: 083 6455 300 
E-mail: [EMAIL PROTECTED] 
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter>




-Original Message-
From: Francois Van der Merwe1 [mailto:[EMAIL PROTECTED]]
Sent: 30 July 2003 01:48
To: [EMAIL PROTECTED]
Subject: Re: inet2 vs MQ listener (UNIX)



Whould you mind pointing me to where I can get this link.  Thanks


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]





      "Voges, P.
      (Pieter)"    To:   [EMAIL PROTECTED]
  <[EMAIL PROTECTED]    cc:
  COM> Subject:  Re: inet2 vs MQ listener (UNIX)
  Sent by: MQSeries
  List
  <[EMAIL PROTECTED]
  N.AC.AT>



  30/07/2003 12:30
  Please respond to
  MQSeries List





According to a link from IBM I found on their web page - Inetd is better
prior to 5.3 and MQ listener is better from 5.3



Thank you
Pieter Voges
MQ Support
Nedcor Limited
Tel: (011) 881 4410
Sel: 083 6455 300
E-mail: [EMAIL PROTECTED]
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter>







-Original Message-
From: Francois Van der Merwe1 [mailto:[EMAIL PROTECTED]]
Sent: 30 July 2003 11:15
To: [EMAIL PROTECTED]
Subject: inet2 vs MQ listener (UNIX)






Is the one better than the other?



Francois van der Merwe



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 email and any accompanying attachments may contain confidential and
proprietary information.  This information is private and protected by law
and, accordingly, if you are not the intended recipient, you are requested
to delete this entire communication immediately and are notified that any
disclosure, copying or distribution of or taking any action based on this
information is prohibited.



Emails cannot be guaranteed to be secure or free of errors or viruses.  The
sender does not accept any liability or responsibility for any
interception, corruption, destruction, loss, late arrival or incompleteness
of or tampering or interference with any of the information contained in
this email or for its incorrect delivery or non-delivery for whatsoever
reason or for its effect on any electronic device of the recipient.



If verification of this email or any attachment is required, please request
a hard-copy version.


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 
email and any accompanying attachments may contain confidential and proprietary 
information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution of or taking any 
action based on this information is prohibited. 
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability 
or responsibility for any interception, corruption, destruction, loss, late 
arrival or incompleteness of or tampering or interference with any of the 
information contained in this email or for its incorrect delivery or 
non-delivery for whatsoever reason or for its effect on any electronic device of 
the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.







Re: inet2 vs MQ listener (UNIX)

2003-07-30 Thread Voges, P. (Pieter)
Title: RE: inet2 vs MQ listener (UNIX)





According to a link from IBM I found on their web page - Inetd is better prior to 5.3 and MQ listener is better from 5.3 

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





-Original Message-
From: Francois Van der Merwe1 [mailto:[EMAIL PROTECTED]]
Sent: 30 July 2003 11:15
To: [EMAIL PROTECTED]
Subject: inet2 vs MQ listener (UNIX)



Is the one better than the other?


Francois van der Merwe


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 
email and any accompanying attachments may contain confidential and proprietary 
information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution of or taking any 
action based on this information is prohibited. 
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability 
or responsibility for any interception, corruption, destruction, loss, late 
arrival or incompleteness of or tampering or interference with any of the 
information contained in this email or for its incorrect delivery or 
non-delivery for whatsoever reason or for its effect on any electronic device of 
the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.






UPGRADING MQ5.1 TO 5.3 ON AIX

2003-07-14 Thread Voges, P. (Pieter)



Hi
everybody
 
We are
experiencing problems to upgrade mq5.1 to 5.3 on AIX 4.3. When we initialy tried
to do the upgrade we had problems trying to start the new QMGR. It just
wouldn't start. After entering the strmqm QMGRNAME  command, it came
back sying an internal MQ error has occured. In the error log it complains
oubout:  Major Errorcode  : -
xecF_E_UNEXPECTED_SYSTEM_RC with the following system
info:  Probe Description :- AMQ6119: An internal WebSphere MQ error
has occurred  ('22 - A system call received a
parameter that is not val' from semget.FDCSequenceNumber :-
0 
 
 B[A{ xcsFreeMem} xcsFreeMem
rc=OK---} xusDelStanzaLineList rc=OK---{ xusReadSingleStanza{
xcsSetlocale} xcsSetlocale rc=OK{ xusGetLineType} xusGetLineType rc=Unknown(2){
xusAddStanzaLineList-{ xcsGetMem-} xcsGetMem rc=OK}
xusAddStanzaLineList rc=OK{ xusGetLineType} xusGetLineType
rc=OK{ xusAddStanzaLineList-{ xcsGetMem-} xcsGetMem
rc=OK} xusAddStanzaLineList rc=OK{ xusGetLineType} xusGetLineType rc=Unknown(1){
xusAddStanzaLineList 
 
I read
in the manual that any JAVA components need to be de-installed and re-intalled
after the upgrade. We de-intalled it. We even tried to delete the 5.1 libraries
and install the 5.3 from fresh - keeping only the /var/mqm directory but were
getting the same error.
 
Any
comments or advice on this one would be really appreciated.
Thank you Pieter VogesMQ SupportNedcor LimitedTel:
(011) 881 4410Sel: 083 6455 300E-mail:
[EMAIL PROTECTED]


 



This
email and any accompanying attachments may contain confidential and proprietary
information.  This information is
private and protected by law and, accordingly, if you are not the intended
recipient, you are requested to delete this entire communication immediately and
are notified that any disclosure, copying or distribution of or taking any
action based on this information is prohibited.
Emails
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability
or responsibility for any interception, corruption, destruction, loss, late
arrival or incompleteness of or tampering or interference with any of the
information contained in this email or for its incorrect delivery or
non-delivery for whatsoever reason or for its effect on any electronic device of
the recipient.
If
verification of this email or any attachment is required, please request a
hard-copy version.






Re: MQCONN FAILED

2003-07-09 Thread Voges, P. (Pieter)
Title: RE: MQCONN FAILED





Thanks everybody for the feedback. This one really get to me. I have checked all 3 logs, and 2 of them is empty since the last time the QMGR was sterted. The one under SYSTEM shows a channel going inactive at 18:00 the previous day because of disconnect interval, and active again on the day in question at 09:00. There is nothing inbetween at 06:10 when the error occured.

On the sollution to retry the connect because the QMGR might still be coming up, doesn't help. The QMGR has been running since May 18 and this happened on June 25. 

Thank you 
Pieter Voges 
MQ Support 
Nedcor Limited 
Tel: (011) 881 4410 
Sel: 083 6455 300 
E-mail: [EMAIL PROTECTED] 
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter>




-Original Message-
From: Robert Broderick [mailto:[EMAIL PROTECTED]]
Sent: 08 July 2003 04:24
To: [EMAIL PROTECTED]
Subject: Re: MQCONN FAILED



With an extension on Peter's comments there are three error logs you need to
look at. One in /errors and two in /qmgrs one under @SYSTEM/error and one
under YOUR_QMGR/error.


   bobbee



>From: "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: MQCONN FAILED
>Date: Tue, 8 Jul 2003 08:23:52 -0400
>
>Did you check both the server level MQ error logs as well as the queue
>manager specific error logs?
>
>
>-Original Message-
>From: Voges, P. (Pieter) [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, July 08, 2003 2:36 AM
>To: [EMAIL PROTECTED]
>Subject: MQCONN FAILED
>
>
>
>We ran into an interesting problem and if anybody can explain it or supply
>me with any info in this regard I will really appreciate it.
>
>We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX
>box(4.3). On the box there is an application running as a process that
>starts up in the morning and then firstly does a connect to the QMGR. Last
>week the app started and tried to connect. It got a 2059 (QMGR not
>available) return code. Later in the day the app was restarted and
>connected
>fine. My problem is that the QMGR had been running for a month when this
>happened. It was up and running on the first connect attempt. There was no
>intervention between the 2 attempts. There are no errors in the logs. It is
>a very low volume box so no default maximums was reached.
>
>Can anybody provide me with any possible causes or direct me to whatever
>else I can check.
>
>Thank you
>Pieter Voges
>MQ Support
>Nedcor Limited
>Tel: (011) 881 4410
>Sel: 083 6455 300
>E-mail: [EMAIL PROTECTED]
>< http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter
><http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter> >
>
>
>
>
>
>   _
>
>
>
>
>
>
>This email and any accompanying attachments may contain confidential and
>proprietary information.  This information is private and protected by law
>and, accordingly, if you are not the intended recipient, you are requested
>to delete this entire communication immediately and are notified that any
>disclosure, copying or distribution of or taking any action based on this
>information is prohibited.
>
>Emails cannot be guaranteed to be secure or free of errors or viruses.  The
>sender does not accept any liability or responsibility for any
>interception,
>corruption, destruction, loss, late arrival or incompleteness of or
>tampering or interference with any of the information contained in this
>email or for its incorrect delivery or non-delivery for whatsoever reason
>or
>for its effect on any electronic device of the recipient.
>
>If verification of this email or any attachment is required, please request
>a hard-copy version.
>
>
>
>   _
>
>
>
>
>
>
>
>
>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.
>


_
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail


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 
email and any accompanying attachments may contain confidential and proprietary 
information.  This informatio

Re: MQCONN FAILED

2003-07-08 Thread Voges, P. (Pieter)
Title: MQCONN FAILED



That 
was my initial thought as well, but the app and the qmgr runs on the same AIX 
server
 
Thank you Pieter VogesMQ SupportNedcor LimitedTel: 
(011) 881 4410Sel: 083 6455 300E-mail: 
[EMAIL PROTECTED] 
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter> 


  -Original Message-From: Kearns, Emile E 
  [mailto:[EMAIL PROTECTED]Sent: 08 July 2003 09:05To: 
  [EMAIL PROTECTED]Subject: Re: MQCONN 
  FAILEDImportance: High
  Were 
  there any netweork / TCP problems at that stage
  
-Original Message-From: Voges, P. (Pieter) 
[mailto:[EMAIL PROTECTED]Sent: 08 July 2003 
08:36To: [EMAIL PROTECTED]Subject: MQCONN 
FAILED
We ran into an interesting problem and if anybody can 
explain it or supply me with any info in this regard I will really 
appreciate it.
We got a QMGR (5.1 - I know I must upgrade to 5.3) running 
on a AIX box(4.3). On the box there is an application running as a process 
that starts up in the morning and then firstly does a connect to the QMGR. 
Last week the app started and tried to connect. It got a 2059 (QMGR not 
available) return code. Later in the day the app was restarted and connected 
fine. My problem is that the QMGR had been running for a month when this 
happened. It was up and running on the first connect attempt. There was no 
intervention between the 2 attempts. There are no errors in the logs. It is 
a very low volume box so no default maximums was reached.
Can anybody provide me with any possible causes or direct me 
to whatever else I can check.   
Thank you Pieter Voges 
MQ Support Nedcor Limited 
Tel: (011) 881 4410 Sel: 083 
6455 300 E-mail: [EMAIL PROTECTED] 
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter> 





This 
email and any accompanying attachments may contain confidential and 
proprietary information.  This 
information is private and protected by law and, accordingly, if you are not 
the intended recipient, you are requested to delete this entire 
communication immediately and are notified that any disclosure, copying or 
distribution of or taking any action based on this information is 
prohibited. 
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any 
liability or responsibility for any interception, corruption, destruction, 
loss, late arrival or incompleteness of or tampering or interference with 
any of the information contained in this email or for its incorrect delivery 
or non-delivery for whatsoever reason or for its effect on any electronic 
device of the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.





  


  For information about the Standard Bank group visit our web site
www.standardbank.co.za

Disclaimer and confidentiality note

Everything in this e-mail and any attachments relating to the official business of the Standard Bank Group Limited  is proprietary to the group.
It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are
those of the sender unless clearly stated as being that of the group.The person addressed in the e-mail is the sole authorised recipient. Please
notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way.
Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference.
I




This 
email and any accompanying attachments may contain confidential and proprietary 
information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution of or taking any 
action based on this information is prohibited. 
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability 
or responsibility for any interception, corruption, destruction, loss, late 
arrival or incompleteness of or tampering or interference with any of the 
information contained in this email or for its incorrect delivery or 
non-delivery for whatsoever reason or for its effect on any electronic device of 
the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.






MQCONN FAILED

2003-07-07 Thread Voges, P. (Pieter)
Title: MQCONN FAILED





We ran into an interesting problem and if anybody can explain it or supply me with any info in this regard I will really appreciate it.

We got a QMGR (5.1 - I know I must upgrade to 5.3) running on a AIX box(4.3). On the box there is an application running as a process that starts up in the morning and then firstly does a connect to the QMGR. Last week the app started and tried to connect. It got a 2059 (QMGR not available) return code. Later in the day the app was restarted and connected fine. My problem is that the QMGR had been running for a month when this happened. It was up and running on the first connect attempt. There was no intervention between the 2 attempts. There are no errors in the logs. It is a very low volume box so no default maximums was reached.

Can anybody provide me with any possible causes or direct me to whatever else I can check.   


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









This 
email and any accompanying attachments may contain confidential and proprietary 
information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution of or taking any 
action based on this information is prohibited. 
Emails 
cannot be guaranteed to be secure or free of errors or viruses.  The sender does not accept any liability 
or responsibility for any interception, corruption, destruction, loss, late 
arrival or incompleteness of or tampering or interference with any of the 
information contained in this email or for its incorrect delivery or 
non-delivery for whatsoever reason or for its effect on any electronic device of 
the recipient.
If 
verification of this email or any attachment is required, please request a 
hard-copy version.







Re: MQ 5.2 Versus & MQ 5.3

2003-03-26 Thread Voges, P. (Pieter)
Title: RE: MQ 5.2 Versus & MQ 5.3





What about MQ5.1 and MQ5.3 do you need a re-compile for client apps.


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





-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 26 March 2003 05:23
To: [EMAIL PROTECTED]
Subject: MQ 5.2 Versus & MQ 5.3



Hi All


We are having some MQ 5.2 client applications which are talking to the
MQ 5.2 Server. Now we are thinking to move to MQ 5.3 version. In this
scenario ,do we need to change any client code for MQ 5.3 Server.


And one more thing is, can we have communication between MQ 5.2 Queue
Manager to MQ 5.3 Queue Manager?.


Could you please give any suggestion on these issues. It is urgent to
me..


Thanks & Regards
Narasimha


Disclaimer:
This e-mail is confidential and may also be privileged.  If you are not
the intended recipient, please notify us immediately; you should not
copy or use it for any purpose, nor disclose its contents to any other
person.







This email and any accompanying attachments may 
contain confidential and proprietary information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution, or taking any action 
based on this information is prohibited.
Emails cannot be guaranteed to be secure or free of 
errors or viruses.  The sender does not accept any liability or 
responsibility for any interception, corruption, destruction, loss, late arrival 
or incompleteness of or tampering or interference with any of the information 
contained in this email or for its incorrect delivery or non-delivery for 
whatsoever reason or its effect on any electronic device of the 
recipient.
If verification of this email or any attachment is 
required, please request a hard-copy version.







Re: OS/390 client attachement feature

2003-02-12 Thread Voges, P. (Pieter)
Title: RE: OS/390 client attachement feature





Hallo everybody


Thanks for all the feedback on CAF being a seperate chargeable product. I know that. We are licenced for it and got it running.

Let me refrain my question. I need to make a copy of the load module for CAF alone. It seems that it is stored in the SCSQAUTH library. (Thank you Rebecca for the info, I have verified it locally). It further seems that it get stored in two members (csqxjcly and csqxjcl) which at installation time gets linked into one loadmodule CSQXJCL. What I need to know is if this load module is all you need to include in the SCSQAUTH library to enable the CAF.   

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





-Original Message-
From: Andrew Miller [mailto:[EMAIL PROTECTED]]
Sent: 12 February 2003 01:17
To: [EMAIL PROTECTED]
Subject: Re: OS/390 client attachement feature



Pieter,
  OS/390 CAF is a seperate chargeable product which, unless you
have asked Big Blue to include as part of your PAC, you may not actually
have. It comes under a seperate FMID which is instantly forgettable.


Regards,


Windy



On 11/02/2003 13:45:42 MQSeries List wrote:


>Can anybody tell me in which MQ dataset on ver 5.2 the abovementioned
software
>gets stored if I need to copy it.
>
>Thank you
>Pieter Voges
>MQ Support
>Nedcor Limited
>Tel: (011) 881 4410
>Sel: 083 6455 300
>E-mail: [EMAIL PROTECTED]
>
>
>
>





For more information on Standard Life, visit our website
http://www.standardlife.com/


The Standard Life Assurance Company, Standard Life House, 30 Lothian Road,
Edinburgh EH1 2DH, is registered in Scotland (No. SZ4) and regulated by the
Financial Services Authority. Tel: 0131 225 2552 - calls may be recorded or
monitored. This confidential e-mail is for the addressee only. If received
in error, do not retain/copy/disclose it without our consent and please
return it to us. We virus scan and monitor all e-mails but are not
responsible for any damage caused by a virus or alteration by a third party
after it is sent.
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 email and any accompanying attachments may 
contain confidential and proprietary information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution, or taking any action 
based on this information is prohibited.
Emails cannot be guaranteed to be secure or free of 
errors or viruses.  The sender does not accept any liability or 
responsibility for any interception, corruption, destruction, loss, late arrival 
or incompleteness of or tampering or interference with any of the information 
contained in this email or for its incorrect delivery or non-delivery for 
whatsoever reason or its effect on any electronic device of the 
recipient.
If verification of this email or any attachment is 
required, please request a hard-copy version."



Re: MQ listener on 5.1 on AIX

2003-02-12 Thread Voges, P. (Pieter)
Title: Message



As a 
process (Runmqlsr) start with 'start listener' under runmqsc
 
Thank you Pieter VogesMQ SupportNedcor LimitedTel: 
(011) 881 4410Sel: 083 6455 300E-mail: 
[EMAIL PROTECTED] 
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter> 


  -Original Message-From: Emile Kearns 
  [mailto:[EMAIL PROTECTED]]Sent: 12 February 2003 
  02:00To: [EMAIL PROTECTED]Subject: Re: MQ listener 
  on 5.1 on AIX
  How 
  do you start the listener?
  As a 
  Daemon or as a Process?
   
   
  Emile Kearns
  Office telephone no: 
  +27(0)114586756
   
  SOFTWARE 
  FUTURESthe business advantageProud member of MGXwww.softwarefutures.com
  
  -Original Message-----From: Voges, P. 
  (Pieter) [mailto:[EMAIL PROTECTED]] Sent: 12 February 2003 
  01:09To: [EMAIL PROTECTED]Subject: Re: MQ listener 
  on 5.1 on AIX
  We got various clients connecting to 
  a AIX QMGR. Sometimes when connecting applications do funny things we reach 
  the maximum amount of processes started on the Unix box. If this conditions 
  keeps on for a while to an extend that existing processes gets cancelled, can 
  this be the cause for the MQ listener to stop running.
  Thank you Pieter 
  VogesMQ 
  SupportNedcor LimitedTel: 
  (011) 881 4410Sel: 083 6455 
  300E-mail: [EMAIL PROTECTED] <http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter> 
  
  
 -Original 
Message----- From:   
Voges, P. (Pieter)  Sent:   11 
February 2003 03:46 To: [EMAIL PROTECTED] Subject:    OS/390 client attachement fuature 
Can anybody tell me in which MQ dataset on ver 
5.2 the abovementioned software gets stored if I need to copy it. 

Thank you Pieter 
VogesMQ SupportNedcor LimitedTel: (011) 881 4410Sel: 083 6455 
300E-mail: [EMAIL PROTECTED] <http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter> 

  "This email and any accompanying attachments may 
  contain confidential and proprietary information.  This information is 
  private and protected by law and, accordingly, if you are not the intended 
  recipient, you are requested to delete this entire communication immediately 
  and are notified that any disclosure, copying or distribution, or taking any 
  action based on this information is prohibited.
  Emails cannot be guaranteed to be secure or free of 
  errors or viruses.  The sender does not accept any liability or 
  responsibility for any interception, corruption, destruction, loss, late 
  arrival or incompleteness of or tampering or interference with any of the 
  information contained in this email or for its incorrect delivery or 
  non-delivery for whatsoever reason or its effect on any electronic device of 
  the recipient.
  If verification of this email or any attachment is 
  required, please request a hard-copy 
version."
"This email and any accompanying attachments may 
contain confidential and proprietary information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution, or taking any action 
based on this information is prohibited.
Emails cannot be guaranteed to be secure or free of 
errors or viruses.  The sender does not accept any liability or 
responsibility for any interception, corruption, destruction, loss, late arrival 
or incompleteness of or tampering or interference with any of the information 
contained in this email or for its incorrect delivery or non-delivery for 
whatsoever reason or its effect on any electronic device of the 
recipient.
If verification of this email or any attachment is 
required, please request a hard-copy version."



Re: MQ listener on 5.1 on AIX

2003-02-12 Thread Voges, P. (Pieter)
Title: RE: MQ listener on 5.1 on AIX





We got various clients connecting to a AIX QMGR. Sometimes when connecting applications do funny things we reach the maximum amount of processes started on the Unix box. If this conditions keeps on for a while to an extend that existing processes gets cancelled, can this be the cause for the MQ listener to stop running.

Thank you 
Pieter Voges
MQ Support
Nedcor Limited
Tel: (011) 881 4410
Sel: 083 6455 300
E-mail: [EMAIL PROTECTED] 
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter>



 -Original Message-
From:   Voges, P. (Pieter)  
Sent:   11 February 2003 03:46
To: [EMAIL PROTECTED]
Subject:    OS/390 client attachement fuature


Can anybody tell me in which MQ dataset on ver 5.2 the abovementioned software gets stored if I need to copy it.


Thank you 
Pieter Voges
MQ Support
Nedcor Limited
Tel: (011) 881 4410
Sel: 083 6455 300
E-mail: [EMAIL PROTECTED] 
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter>




"This email and any accompanying attachments may 
contain confidential and proprietary information.  This information is 
private and protected by law and, accordingly, if you are not the intended 
recipient, you are requested to delete this entire communication immediately and 
are notified that any disclosure, copying or distribution, or taking any action 
based on this information is prohibited.
Emails cannot be guaranteed to be secure or free of 
errors or viruses.  The sender does not accept any liability or 
responsibility for any interception, corruption, destruction, loss, late arrival 
or incompleteness of or tampering or interference with any of the information 
contained in this email or for its incorrect delivery or non-delivery for 
whatsoever reason or its effect on any electronic device of the 
recipient.
If verification of this email or any attachment is 
required, please request a hard-copy version."



OS/390 client attachement fuature

2003-02-11 Thread Voges, P. (Pieter)
Title: OS/390 client attachement fuature





Can anybody tell me in which MQ dataset on ver 5.2 the abovementioned software gets stored if I need to copy it.


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





 



Strange Behaviour QMGR

2003-01-31 Thread Voges, P. (Pieter)
Title: Strange Behaviour QMGR





Please help, any input will be appreciated.


Strange new problem on unix(AIX) qmgr  connected to os390 and NT qmgr's. Happened on 30 December and 31 January. Unix ver 5.1, mvs and NT ver 5.2

QMGR to QMGR connected through sender and receiver channels - disconnect interval 0.


The following are noticed between NT and Unix even though the channels on both sides shows as "running" and messages are not received. Soon after this, no RUNMQSC commands can be entered on Unix and eventually the QMGR needs to be bounced. There are no error logs on Unix. 

What causes a connection on a port to get a CLOSE_WAIT status?


What can be done to rectify it. When it hits this state soon RUNMQSC does not accept any input and shortly thereafter the QMGR cannot being brought down, not even with the '-i' command. After  restarting the unix qmgr, everything is sorted out.   


Command failed: chmod a+rw /dev/null
chmod: /dev/null: Not owner

Press return to continue:
08:07:00 all_adm@flash_boot1:/main/nedcor/home/all_adm
>netstat -a| grep 1414
tcp4   0  0  swift1.1414    safeprod.it.nedn.3798  ESTABLISHED
tcp4   0  0  swift1.1414    mvsprod.it.nedne.2573  ESTABLISHED
tcp4   0  0  *.1414 *.*    LISTEN
tcp4   0  0  swift1.32905   safeprod.it.nedn.1414  CLOSE_WAIT


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

-

"The contents of this electronic message and any attachments relating to the official business of Nedcor Limited and subsidiaries ("Nedcor") are proprietary to Nedcor. They are confidential, legally privileged and protected by law. Views and opinions are those of the sender and do not represent Nedcor's views and opinions nor constitute any commitment by or obligation on Nedcor unless otherwise stated or agreed to in writing by Nedcor.

The person addressed in this electronic message is the sole authorised recipient. If you have received this message in error, you are to delete it immediately and notify the sender that it has unintentionally reached you. You may not use or disclose the contents of this message to any other person.

Nedcor cannot assure that the integrity of this communication has been maintained, nor that it is free of errors, viruses, interception, tampering or interference. Nedcor therefore does not accept liability or legal responsibility for the contents of this electronic message, its non-delivery or incorrect delivery for whatever reason, its effect on electronic devices or its transmission in an unencrypted medium."

---





Signalling

2002-11-29 Thread 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] 
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter>



 -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] 





Channels out of sync - MQ5.2 OS/390

2002-11-18 Thread Voges, P. (Pieter)
Title: Channels out of sync - MQ5.2 OS/390





I am experiencing problems with channels going out of sync on MVS. We upgraded to version 5.2 a while ago from 1.2


After coming up on the new version I had to bring the QMGR down again and started up on the old version to recover some messages and then we started up again on the new version. It looks as if the SYSTEM.CHANNEL.SYNCQ was populated with entries during this process as if gives the error message "csqx517e channel name repeated" at startup time. 

Now from time to time I get a message "csqx526e message sequence error"


I think the only way to resolve this is to clear the SYSTEM.CHANNEL.SYNCQ on mvs and reset the sequence numbers on the distributed QMGR's. 

I need to know if I can do this and if anybody agrees that this could be the problem since there are definitely duplicates in the SYSTEM.CHANNEL.SYNCQ 

Is it save to do this.


Any help will be appreciated.


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







Re: copy-restores question

2002-11-07 Thread Voges, P. (Pieter)
Title: RE: copy-restores question





We have done this on numerous occasions in the past without any problems. We copied our /var/mqm directory to the new machine which contains all MQ stuff. The channels was setup to connect through DNS in stead of IP adress, so we pointed the DNS entry to the new IP adress - no problem. 

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





-Original Message-
From: Rick Tsujimoto [mailto:[EMAIL PROTECTED]]
Sent: 07 November 2002 10:19
To: [EMAIL PROTECTED]
Subject: copy-restores question



We're planning to swap and rename servers, so that the machine that hosted
MQSeries, e.g. server-a, will be copied to another server, e.g. server-b.
Once the copy is done, we plan to swap ther server names, such that,
server-b becomes server-a and vice-versa.  Other than the "new" server-a
has a different IP address, are there any reasons why this wouldn't work
for MQSeries?  I remember hearing some users having problems copying
filesystems, so I made it a practice to uninstall and reinstall MQSeries
when a machine is being replaced.  I'd like to avoid this, if possible.


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





IMB TRANSACTION AND MESSAGING CONFERENCE

2002-11-03 Thread Voges, P. (Pieter)
Title: URGENT - REVERT BACK TO 5.1 FROM 5.2



Hi 
everyone
 
I 
would like to attend the IBM transaction and messaging conference in Las 
Vegas from February 10 - 14 next year. I need to apply now and need some 
indication of costs for budgeting purposes. I am working in South-Africa and can 
obtain the cost for the return flights quite easy. But I urgently need an 
estimation of the other cost. (Cost of the conference, accommendation, transport 
etc.)
 
If 
anybody can give me an indication on that it will really be appreciated. 

 

  
  Thank you 
  
  Pieter 
  Voges 
  MQ 
  Support Nedcor Bank 
  Limited Tel: 
  (011) 881 4410 
  Sel:  
  083 6455 
  300 E-mail: 
  [EMAIL PROTECTED] 
  http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter
   


Re: Problems in displaying Queue Definitions

2002-09-06 Thread Voges, P. (Pieter)
Title: RE: Problems in displaying Queue Definitions





Someone else had the same question last week. We experienced the same problem a while ago. You need to change your logon proc. Add the 5.2 library to your user profile list for your TSO user.(For the PROC you use to sign on with.

-Original Message-
From: P Karthikeyan [mailto:[EMAIL PROTECTED]]
Sent: 06 September 2002 09:58
To: [EMAIL PROTECTED]
Subject: Problems in displaying Queue Definitions



Hi all,


I have installed the MQ V 5.2 in OS/390 and tried to display the queue definitions of a
queue manager of  MQ V 2.1 OS/390 using the CSQOREXX panels of MQ V 5.2 OS/390. Iam
getting the results


 CSQ9001E -Q KEYWORD 'CFSTRUCT' IS INVALID
 CSQ9001E -Q KEYWORD 'QSGDISP' IS INVALID


I know that the queue definitions have been changed in MQ V 5.2 OS/390 from MQ V 2.1 OS390
with  the addition of some more parameters like 'CFSTRUCT'.


Is it possible to view the definitions of queues of MQ 2.1 in CSQOREXX panels of MQ V 5.2
without any changes in existing queue definitions??


Thanks in advance for your help.



Regards,
Karthik







***The information contained in this message is legally privileged and confidential
information intended only for the use of the addressed individual or entity indicated in
this message (or responsible for delivery of the message to such person). It must not be
read, copied, disclosed, distributed or used by any person other than the addressee.
Unauthorised use, disclosure or copying is strictly prohibited and may be unlawful.
 Opinions, conclusions and other information on this message that do not relate to the
official business of any of the constituent companies of the TATA CONSULTANCY SERVICES
shall be understood as neither given nor endorsed by the Group. If you have received this
message in error, you should destroy this message and kindly notify the sender by e-mail.
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





Re: Problems in MQ Admin Utility in MQ V 5.2/OS390

2002-08-28 Thread Voges, P. (Pieter)
Title: RE: Problems in MQ Admin Utility in MQ V 5.2/OS390





If u are using this under a TSO panel - add the 5.2 library to your logon user profile list.


Pieter Voges
Nedcor Bank Limited 


-Original Message-
From: P Karthikeyan [mailto:[EMAIL PROTECTED]]
Sent: 28 August 2002 10:19
To: [EMAIL PROTECTED]
Subject: Problems in MQ Admin Utility in MQ V 5.2/OS390



Hi all,


We have installed the MQSeries V 5.2 in OS390 and we faced the following while trying to
display all the queues associated with the queue manager using the IBM Supplied MQ admin
Utility (CSQOREXX) where MQ52 is the queue manager name.


 CSQO096E Internal error in CSQOXDSP. MQ52 not in keyword table. The explanation of the
message is not useful much











 Explanation: An internal error has occurred.



 Module: CSQORATR



 Severity: 12



 System Programmer Response: Collect the following items, and contact your IBM support
center:
   1. The number of the message, and the values of program and att-name
   2. The name of the panel involved
   3. A description of the actions that lead to the problem


   Could any one in the list throw some light on the problem. The installation went
   through fine without any problems.


   Thanks & Regards,
   Karthik






* * * The information contained in this message is legally privileged and confidential
information intended only for the use of the addressed individual or entity indicated in
this message (or responsible for delivery of the message to such person). It must not be
read, copied, disclosed, distributed or used by any person other than the addressee.
Unauthorised use, disclosure or copying is strictly prohibited and may be unlawful.
Opinions, conclusions and other information on this message that do not relate to the
official business of any of the constituent companies of the TATA CONSULTANCY SERVICES
shall be understood as neither given nor endorsed by the Group. If you have received this
message in error, you should destroy this message and kindly notify the sender by e-mail.
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





Re: MQSeries Clustering and Queue Sharing Groups

2002-08-25 Thread Voges, P. (Pieter)
Title: RE: MQSeries Clustering and Queue Sharing Groups





Please respond with any feedback to the LIST and not individually as I am also interested in this. For the use of Sysplex in a MVS environment would the use of clustering or queue sharing groups be the way to go?

Thank you


Pieter Voges
Nedcor Bank Limited 


-Original Message-
From: Crowder, Randall [mailto:[EMAIL PROTECTED]]
Sent: 23 August 2002 10:31
To: [EMAIL PROTECTED]
Subject: MQSeries Clustering



All,


We are having an internal discussion about the use of MQSeries clustering at
my company.  Basically, our support organization is trying to eliminate
clustering with the contention that it is very difficult to support in a
production environment.  On the other hand, we (application group) are
interested in using the load balancing capabilities within our overall
application architecture.  The final configuration would have about 8 NT
boxes clustered with 2 mainframe queue managers.  We might gradually add
boxes and queues over time but would rarely remove boxes or queues.  I'm
guessing that we'd have 20 to 40 clustered queues on each box.


I'd appreciate any feedback - positive or negative on clustering.  Also,
interested in knowing if anyone has 5.3 up in a similar configuration and
how it compares to older versions.


Thanks,
Randy C.


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





C++ Foundation Classes

2002-08-13 Thread Voges, P. (Pieter)
Title: C++ Foundation Classes





Hi Everyone


I got an interesting question from the development team. It comes down to an application running on a Nt Box written in C++ using the mq-client libraries connecting to a QMGR on a Unix AIX Box. The question is whether or not there are build-in error handling in the C++ Foundation classes to cater for loss of connectivity (either network or the QMGR going down). Example - if you do a put to a queue on a qmgr which the client lost connectivity to, will this be handled automatically or will he keep on trying to put infinitaly regardless of the lost connectivity. (Will the classes try to restore the connectivity and how?)

Any info will be appreciated


Pieter Voges
MQ Support
Nedcor Bank Limited
  


-Original Message-
From: Paul Clarke [mailto:[EMAIL PROTECTED]]
Sent: 13 August 2002 02:11
To: [EMAIL PROTECTED]
Subject: Re: Channel that always stays running



Can I add my two cents worth about Heartbeats. There have been one or two
slightly misleading comments about them which I think I ought to address.


Heartbeats serve at least three purposes.


1/ They maintain contact with the receiver channel even when there are no
messages to send. This allows the receiver channel to ask the sender
channel to end (for example a STOP CHANNEL MODE(QUIESCE). So, if you issued
a normal quiesce stop channel on a receiver and the channel wasn't moving
any messages it may take up to the heartbeat interval before the channel
actually ended.


2/ Since a heartbeat is only sent in relative inactivity the receiver
channel will free its resources when it gets one. For example it will free
off any excessive message storage and close its queue cache.


3/ It allows the receiver to predict when data should arrive down the
socket. This is most pertinent to the current discussion of network outage.
Without heartbeats a receiver channel can not predict when the next message
will arrive from the sender since the sender has no clue either. However,
with heartbeats enabled the receiver knows that either it will receive a
heartbeat or a message within a known interval. Consequently the recveiver
can issue a receiver with a timeout. If this receive does time out it means
that something has gone seriously wrong. In an ideal world a network outage
would cause the TCP/IP recv() call to return a nice return code however, as
we all know, TCP/IP is notoriously bad at telling us about outages so this
timeout is probably our best defence. I would still recommend that people
use KEEPALIVE though since there are some cases, such as SVRCONN channels,
where we can't use a timeout. One last point about the timeout. The timeout
value used will be


    if (Heartbeat Value < 1 minute) Timeout = Heartbeat * 2
   else Timeout = Heartbeat + 1 minute


In other words we add a little contingency on the timeout for network
latency.


Heop this helps,


P.


Paul G Clarke
WebSphere MQ Development
IBM Hursley


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: 'Phantom' messages on queue

2002-07-02 Thread Voges, P. (Pieter)
Title: RE: 'Phantom' messages on queue





It has to do with commit and syncpoint. If commit was specified in the application and now syncpoint was taken the physical message is on the queue but you can't see it.

> Thank you 
> 
> Pieter Voges
> MQ Support
> Nedcor Bank Limited    
> Tel: (011) 881 4410
> Sel:  082 5790 790
> E-mail: [EMAIL PROTECTED] 


> 




-Original Message-
From: Heinz Klein [mailto:[EMAIL PROTECTED]]
Sent: 30 June 2002 09:41
To: [EMAIL PROTECTED]
Subject: 'Phantom' messages on queue



Hello.


Two clients reported (I have not seen it by myself but have quite high
confidence in their technical skills) a VERY strange behavior: running
the OS/390 batch sample (MQSeries V2.1 in both cases) against a trans-
mission queue which shows CURDEPTH > 0, they can see the messages when
they browse the queue, but if they run the sample asking for destructive
GETs they get 2033 (MQRC_NO_MSG_AVAILABLE) before ANY message is read.
Re-running the sample with the browse option shows all the message in
the queue.


IPPROCS and OPPROCS of the queue are 0 (actually one of the customers
shut down the Channel Initiation to make sure there was nothing pending
from this side).


I cannot imagine if and how this could happen. Has anyonse seen this and,
if yes, has an explanation for it?


Thanks in advance for any contribution.


Heinz Klein


OLTP Tecnologia & Solucoes Ltda.
Sao Paulo/SP - Brasil


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





CUSTOMIZE SUPPORTPAC MA17 OS/390

2002-05-29 Thread Voges, P. (Pieter)
Title: CUSTOMIZE SUPPORTPAC MA17  OS/390 





Hi everyone.


I got some messages on a dead letter queue which I need to get back to the original queue quite urgently on MVS MQ 1.2


The problem is that I first need to strip the DLQ header before taking it back. I searched through IBM's website and fount Supportpac MA17 which does all this. My Problem is that I am stuck now as the readme doc is not very clear. I would appreciate any help I can get from someone that installed and used this before.

I downloaded the supportpac and created the 4 datasets on MVS


MA17.CBS
MA17.CLIST
MA17.CSR
MA17.ISPPENU


with all their members in. Step 5 in the readme doc says INSTALLATION. According to this the samples should be installed in the same way as those already supplied with the product. This is where I am stuck. What do I need to do from here. What should be copied where and what should be compiled where?

Any help will be appreciated 


   Thank you 


Pieter Voges
MQ Support
    
Tel: (011) 881 4410
Sel:  082 5790 790
E-mail: [EMAIL PROTECTED] 

http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter