[no subject]

2003-01-14 Thread templeton quinn
Hi All;

Has anyone ever configured structure MQPMO and MQGMO
into the segmentation status rather than the default
for sending and receving extra large message (> 100MB)
?

Regards;

Temple






_
STOP MORE SPAM with the new MSN 8 and get 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



2195 Error

2003-01-14 Thread Jeffrey Ross



Hello Fellow MQer's,
 
I have this weird problem with MQ V5.2, AIX 
4.3.3.  Our AIX Admins rebooted the machine.  After the reboot I 
started MQ and the Client Server and connected through MQ Explorer on 
WIn2K.  An application team that uses this particular server informed me 
they have been getting 2195 errors and an occasional 2059 error.  I 
verified that they were pointing to the correct queue manager and server IP and 
I am at loss at what could be causing this.  The application worked fine 
prior to this reboot.  There are no error messages in the log.
 
Has anybody seen anything like this?
 
My thought is MQ is fine.  I can do an amqsput 
and amqsget on the queue the application tries to access, I can navigate around 
the queue manager through MQ Explorer and through telnet.  I'm thinking 
something wasn't loaded right in the reboot of the server, but I'm not 
sure.  Of course this problem occurred late in the afternoon, so I was not 
able to find out, yet, how the machine was rebooted.
 
Thanks in advance,
Jeff


Re: MQSeries5.2 Performance on UNIX (persistent msgs) - facts and hints

2003-01-14 Thread Richard Tsujimoto



Volker,
 
There are two things you may want to take into 
account.  1.  Does your test include the overhead associated with a 
channel connection?  2. Does your test include the overhead for a process 
startup?  The former can be substantial and could skew your results, 
especially if your test load is small, e.g. 100 messages.
 

  - Original Message - 
  From: 
  Volker 
  Kaemmerer 
  To: [EMAIL PROTECTED] 
  Sent: Monday, January 13, 2003 5:59 
  AM
  Subject: MQSeries5.2 Performance on UNIX 
  (persistent msgs) - facts and hints
  Hi, came across some IBM documentation with 1200 
  msg/sec (persistent, 1KB, Fast-Binding) or e.g. "P6D: MQSeries for AIX V5.2 - Performance 
  highlights"  with up to 300 msgs/sec, (persistent, 1-2kB) processed by 
  MQSeries V5.2 on AIX UNIX 
  servers. We currently using a 
  single-process, single-threaded server application for MQPuts/Gets on one 
  queue manager with MQSeries V5.2 
  on one UNIX AIX 4.3.3 server. The 
  application can also be running in multiple processes and/or threads accessing 
  the same queue for MQGets and same queue for MQPuts. We 
  identified the performance optimum between 2-3 process or threads and 
  identified the Disk-IO being the performance limiting factor to approx. 45 msgs/sec (persistent, 
  <1KB) in our infrastructure. This Disk-IO is on the /var/mqm/qmgrs 
  filesystem, which is the only one 
  on this disk. This is far away from the IBM values for a single queue manager, 
  single server environment. What 
  can we do? We would be 
  interested to get some ideas of what kind of persistent throughputs are 
  achieved in your production live environment under UNIX (preferred AIX) and MQSeries V5.2 by 
  which type of hardware (disks) and MQSeries application 
  topology&architecture. What 
  kind of tuning on UNIX-Kernel, Disks, MQSeries and your application have 
  improved your performance considerably? What can you recommend or not recommend? Would be pleased to received some feedback 
  here. Thanks and best 
  regards,       
    Volker Kaemmerer --- Volker Kaemmerer           
                        
                        
            AMADEUS Data Processing GmbH  
                        
                        
                        
                        
               Communication Gateway   
                        
                 Phone:   
   +49-8122-43-4225                 
                        
             OSC - Open Systems Communication 
  Development                   
                        
                        
               FAX:       
    +49-8122-43-3260               
                        
               Berghamer Strasse 6 
    Email:      [EMAIL PROTECTED]   
                        
     D-85435 Erding, Germany


Re: COBOL Copybook with Redefines clause and WMQI

2003-01-14 Thread Tony Devitt
**

Note: This e-mail is subject to the disclaimer contained at the bottom
of this message.

**
:

A couple of points.
Make sure that the qualifier GROUP001 is included in your ESQL SET
statement if you have manually built the statement (as opposed to drag and
drop).e.g. OutputRoot.MRM.GROUP001.ElementName.   Tracing the flow
might be useful to determine what is being created.
I'm not sure what you mean by 'commenting out' the GROUP001 element.  This
Compound Type will contain two or more elements, or types, which are the
alternative 'choices'.   Any changes to the generated definition need to be
done with considerable care to ensure that you still have a valid
structure.  Again, tracing will let you check the output structure that is
being created in the flow.





  Saraswathy A
  cc:
  Sent by: MQSeriesSubject:  COBOL Copybook with Redefines 
clause and WMQI
  List
  


  01/14/03 07:28 PM
  Please respond to
  MQSeries List






Hi All,


I have messageset that has a copybook imported that contains a redefines
clause and WMQI created a element with the postfix Group001.
I have a message flow that uses a compute node which has the above
messageset as the output format. I get the following error at the output
node.
'  Mismatch between logical definition and message tree'

and if i comment out this Group001 element  i get a different error message


'illegal choice element'
What changes need to be done while tranformaing ? ,i have WMQI 2.1 for HP

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






:


The information transmitted in this message and attachments (if any)
is intended only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or taking
of any action in reliance upon this information, by persons or entities
other than the intended recipient is prohibited.

If you have received this in error, please contact the sender and delete this
e-mail and associated material from any computer.

The intended recipient of this e-mail may only use, reproduce, disclose or
distribute the information contained in this e-mail and any attached files,
with the permission of CGU Insurance.

This message has been scanned for viruses and cleared by MailMarshal.


:

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: CICS DPL BRIDGE BACK OUT QUESTION?

2003-01-14 Thread Miller, Dennis
I can't think of an easy way to divert the message to the DLQ. On the other hand, it's 
difficult to imagine the bridge monitor abending because of message content. My bet 
is, the cause of the abend is somewhere else and that's where you need to focus.

As for the backout fields you mention. They are provided for your application to use 
as it pleases. But it's a widely-used best practice to avoid poison message loops by 
comparing the backout count to the backout threshold and rerouting messages to the 
backout requeue if the threshold is exceeded.

regards,
Dennis

> -Original Message-
> From: Ellis McCarthy [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, January 14, 2003 1:16 PM
> To:   [EMAIL PROTECTED]
> Subject:   CICS DPL BRIDGE BACK OUT QUESTION?
> 
> I am testing the use of the CICS DPL bridge.  I am triggering the bridge
> transaction.  When the bridge gets a bad message, the following appears to
> take place:  the bridge monitor abends,  the message is backed out and
> returned to the request queue, this bridge monitor is triggered, and the
> bad message is processed again, causing a processing loop.  How do i get
> the message to the dead letter queue.
> 
> The next question is how is the "Backout requeue name" and the "Backout
> threshold"  fields used, if the queue manager takes no action on these
> fields as the manual states.
> 
> Ellis
> 
> 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



CICS DPL BRIDGE BACK OUT QUESTION?

2003-01-14 Thread Ellis McCarthy
I am testing the use of the CICS DPL bridge.  I am triggering the bridge
transaction.  When the bridge gets a bad message, the following appears to
take place:  the bridge monitor abends,  the message is backed out and
returned to the request queue, this bridge monitor is triggered, and the
bad message is processed again, causing a processing loop.  How do i get
the message to the dead letter queue.

The next question is how is the "Backout requeue name" and the "Backout
threshold"  fields used, if the queue manager takes no action on these
fields as the manual states.

Ellis

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



Solved!!! 2059 in Applet (only from a browser though???)

2003-01-14 Thread Potkay, Peter M (PLC, IT)
I got the applet to connect to a remote queue manager through the browser or
thru the applet viewer.

The answer is in Appendix F of the Using Java manual for IBM.
http://publibfp.boulder.ibm.com/epubs/html/csqzaw09/csqzaw09tfrm.htm

THANK YOU JAMES KINGDON FROM HURSLEY for pointing me in this direction.


In your browser, go to Tools...Internet Options...Advanced and see what Java
Plug-In your browser is using (Under JAVA SUN).
On your PC, in the directory that has that plug in, find the java.policy
file and make the changes specified under Appendix F in the manual.




Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906


-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 9:14 AM
To: [EMAIL PROTECTED]
Subject: Re: 2059 in Applet (only from a browser though???)


I guess there is no way for this to work. By design, applets loaded in a
browser cannot make a network connection to another computer.
http://java.sun.com/sfaq/#socket


I think I will have to try this idea by using a JSP page that refreshes
itself every 5 seconds or so to give updated queue info.


Still curious why the applet run from the applet viewer in IDE works but not
from the applet viewer from the command prompt.
And why does IBM put that note about 2059 errors and security settings in
the sample applet code? Is there a way to override the applets inability to
connect to a remote computer?




Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906


-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2003 11:21 AM
To: [EMAIL PROTECTED]
Subject: 2059 in Applet (only from a browser though???)


I wrote a little applet that connects to a QM and gives you a depth on a
queue. There is a refresh button to get the most current depth of the queue.
When I execute this applet from my IDE (VisualCafe 4.5.1 Enterprise), it
works just great. But if I try to invoke the applet from a browser, the
applet fails to connect and gives a 2059 error. The below errors are also
thrown to the console. I get the same negative results when invoking this
applet from the AppletViewer from the command line.

I don't understand why the applet works in the IDE and not in the browser. I
did see this comment at the top of sample applet code in the Using Java MQ
manual:

***
// Note. If you receive MQ error 2 reason 2059 and you are sure your MQ and
TCPIP
// setup is correct,
// you should click on the "Applet" selection in the Applet viewer window
// select properties, and change "Network access" to unrestricted.

***


In my applet viewer window, I go to Applet...Properties and set the Class
Access to Unrestricted. It seems to make no diff either way. There is no
Network access setting.
When I run the applet from the IDE (and unselect the option for the IDE to
start up the applet in a browser), the applet works fine. When I click on
the applet viewer properties from here, the class access is again
unrestricted, but the Http proxy port # is blank. In the applet viewer, I
can't change the Http proxy port# from the prefilled 80. I space it out and
it reverts back to port 80. Is that a clue?


Here is the error thrown to the console:
*
Java(TM) Plug-in: Version 1.3.1_03
Using JRE version 1.3.1_03 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\PLAAHO Proxy Configuration:
Manual Configuration  Proxy: ftp=internet:80;http=internet:80  Proxy
Overrides: *thehartford.com,,localhost:49213,127.0.0.1,

c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
q:   hide console
s:   dump system properties
t:   dump thread list
x:   clear classloader cache
0-5: set trace level to 
 openConnection about to
start Version 1.1 MQJE001: An MQException occurred: Completion Code 2,
Reason 2059
MQJE012: Security error - cannot connect to host 157.209.105.95
MQJE001: Completion Code 2, Reason 2059
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2059 at
com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:172)
at
com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQCl
ientManagedConnectionFactoryJ11.java:270)   at
com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQCli
entManagedConnectionFactoryJ11.java:290)at
com.ibm.mq.StoredManagedConnection.(StoredManagedConnection.java:80)
at
com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionMa
nager.java:150) at
com.ibm.mq.MQQueueManager.obtainBa

RE : Re: MQSeries 5.2.1 and 2046 error between Win2000 client and IBM MVS server (mq 2.1)

2003-01-14 Thread COHEN David
Very Sorry for the mistake

David COHEN

-Message d'origine-
De : WR [mailto:[EMAIL PROTECTED]] 
Envoyé : mardi 14 janvier 2003 19:46
À : [EMAIL PROTECTED]
Objet : Re: MQSeries 5.2.1 and 2046 error between Win2000 client and IBM MVS server 
(mq 2.1)


Yes, you *should* call Morag "sir" -- she's a scary woman!  :-P

-Will


At 09:54 AM Tuesday 1/14/2003, COHEN David wrote:
>Thank you sir. I will test right now
>
>David COHEN
>
>
>-Message d'origine-
>De : Morag Hughson [mailto:[EMAIL PROTECTED]]
>Envoyi : mardi 14 janvier 2003 18:34
>@ : [EMAIL PROTECTED]
>Objet : RE : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint 
>and IBM MVS server (mq 2.1)
>
>
>MQSeries for OS/390 V2.1 doesn't support MQMD_VERSION_2. I think that 
>may your problem
>
>Cheers
>Morag
>
>Morag Hughson
>WebSphere MQ for z/OS Development
>Internet: [EMAIL PROTECTED]
>
>
>
>
>
>   COHEN
> David
>
>[EMAIL PROTECTED]
>   FR>  cc:
>
>   Sent by: MQSeriesSubject:  RE :  Re:
> MQSeries 5.2.1 and 2046 error between Win2000
>   List  cleint and
> IBM   MVS  server (mq 2.1)
>   
>   N.AC.AT>
>
>
>
>
>
>   14/01/2003
> 16:40
>
>   Please respond
> to
>
>   MQSeries
> List
>
>
>
>
>
>
>
>
>Dear Sir,
>
>Here is how all the structures look in MQGET. I am not sure which ones 
>to disable and replace with the memset. If you could send me your ideas 
>so I can build another version. Thank you
>
>
>MQODmqod= {MQOD_DEFAULT}; // Object
>description
>MQMDmqmd= {MQMD_DEFAULT}; // Message
>Descriptor
>MQGMO   mqgmo   = {MQGMO_DEFAULT};// Get
>message options
>MQCNO   mqcno   = {MQCNO_DEFAULT};//
>Connection Options
>MQCDmqcd= {MQCD_CLIENT_CONN_DEFAULT}; // Client
>Definition
>
>mqcno.Version   = MQCNO_VERSION_2;
>mqcno.ClientConnPtr = &mqcd;
>
>mqod.ObjectType = MQOT_Q;
>
>mqmd.Version= MQMD_VERSION_2; //
>Version-2 message descriptor structure
>mqmd.Encoding   = MQENC_NATIVE;   //
>Native machine encoding.
>mqmd.CodedCharSetId = MQCCSI_Q_MGR;   //
>Queue manager's coded character set identifier.
>
>mqgmo.Version   = MQGMO_VERSION_2;//
>Version-2 get-message options structure.
>mqgmo.Segmentation  = MQSEG_INHIBITED;//
>Segmentation not allowed.
>
>//No -O was specified.
>if (bDefaultOptions) {
> mqgmo.Options   = MQGMO_NO_WAIT | //
>Return immediately if no suitable message.
> MQGMO_FAIL_IF_QUIESCING |   // Fail if
>queue manager is quiescing.
> MQGMO_CONVERT | // Convert
>message data.
> MQGMO_COMPLETE_MSG |// Only
>complete logical messages are retrievable.
> MQGMO_ALL_MSGS_AVAILABLE |  // All messages in
>group must be available.
> MQGMO_ALL_SEGMENTS_AVAILABLE;   // All segments in
>a
>logical message must be available.
> }
> mqgmo.MatchOptions  = MQMO_NONE;
>// No matches.
>
> iOpenOptions= MQOO_INPUT_AS_Q_DEF |   // Open queue
>to get
>messages using queue-defined default.
> MQOO_FAIL_IF_QUIESCING; // Fail if queue manager is
>quiescing.
>
>
>David COHEN
>
>
>
>
>-Message d'origine-
>De : Peter Uranyi [mailto:[EMAIL PROTECTED]]
>Envoyi : mercredi 8 janvier 2003 13:20
>@ : [EMAIL PROTECTED]
>Objet : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and 
>IBM MVS server (mq 2.1)
>
>
>David,
>
>You are using a get option that is not valid on MVS.
>My first guess would be that in your program you have something like 
>this:
>
>gmo.Version = MQGMO_VERSION_2; /* Avoid need to reset Message  */ 
>gmo.MatchOptions = MQMO_NONE;  /* ID and Correlation ID before */
>/* every MQGET  */
>
>This does work if you connect to a queue manager on Windows or Unix but 
>not on MVS.
>
>Instead of using the above options, you have to reset the Message ID 
>and Correlation ID before every(!) MQGET.
>
>Like this:
>
>memcpy(md.MsgId, MQMI_NONE, sizeof(md.MsgId)); memcpy(md.CorrelId, 
>MQCI_NONE, sizeof(md.CorrelId));
>
>I hope this helps.
>Peter
>
>--- COHEN David <[EMAIL PROTECTED]> wrote:
> > Dear all
> >
> > I have a question regarding MQSeries 5.2.1 installed on an Windows 
> > 2000 as a client And MQSeries 2.1 installed on an IBM MVS as a 
> > server. When trying to do an MQGET on a queue I recei

Re: MQSeries 5.2.1 and 2046 error between Win2000 client and IBM MVS server (mq 2.1)

2003-01-14 Thread WR
Yes, you *should* call Morag "sir" -- she's a scary woman!  :-P

-Will


At 09:54 AM Tuesday 1/14/2003, COHEN David wrote:

Thank you sir. I will test right now

David COHEN


-Message d'origine-
De : Morag Hughson [mailto:[EMAIL PROTECTED]]
Envoyi : mardi 14 janvier 2003 18:34
@ : [EMAIL PROTECTED]
Objet : RE : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and
IBM MVS server (mq 2.1)


MQSeries for OS/390 V2.1 doesn't support MQMD_VERSION_2. I think that may
your problem

Cheers
Morag

Morag Hughson
WebSphere MQ for z/OS Development
Internet: [EMAIL PROTECTED]





  COHEN
David

cc:

  Sent by: MQSeriesSubject:  RE :  Re:
MQSeries 5.2.1 and 2046 error between Win2000
  List  cleint and
IBM   MVS  server (mq 2.1)
  





  14/01/2003
16:40

  Please respond
to

  MQSeries
List








Dear Sir,

Here is how all the structures look in MQGET. I am not sure which ones to
disable and replace with the memset. If you could send me your ideas so I
can build another version. Thank you


MQODmqod= {MQOD_DEFAULT}; // Object
description
MQMDmqmd= {MQMD_DEFAULT}; // Message
Descriptor
MQGMO   mqgmo   = {MQGMO_DEFAULT};// Get
message options
MQCNO   mqcno   = {MQCNO_DEFAULT};//
Connection Options
MQCDmqcd= {MQCD_CLIENT_CONN_DEFAULT}; // Client
Definition

mqcno.Version   = MQCNO_VERSION_2;
mqcno.ClientConnPtr = &mqcd;

mqod.ObjectType = MQOT_Q;

mqmd.Version= MQMD_VERSION_2; //
Version-2 message descriptor structure
mqmd.Encoding   = MQENC_NATIVE;   //
Native machine encoding.
mqmd.CodedCharSetId = MQCCSI_Q_MGR;   //
Queue manager's coded character set identifier.

mqgmo.Version   = MQGMO_VERSION_2;//
Version-2 get-message options structure.
mqgmo.Segmentation  = MQSEG_INHIBITED;//
Segmentation not allowed.

//No -O was specified.
if (bDefaultOptions) {
mqgmo.Options   = MQGMO_NO_WAIT | //
Return immediately if no suitable message.
MQGMO_FAIL_IF_QUIESCING |   // Fail if
queue manager is quiescing.
MQGMO_CONVERT | // Convert
message data.
MQGMO_COMPLETE_MSG |// Only
complete logical messages are retrievable.
MQGMO_ALL_MSGS_AVAILABLE |  // All messages in
group must be available.
MQGMO_ALL_SEGMENTS_AVAILABLE;   // All segments in
a
logical message must be available.
}
mqgmo.MatchOptions  = MQMO_NONE;
// No matches.

iOpenOptions= MQOO_INPUT_AS_Q_DEF |   // Open queue
to get
messages using queue-defined default.
MQOO_FAIL_IF_QUIESCING; // Fail if queue manager is
quiescing.


David COHEN




-Message d'origine-
De : Peter Uranyi [mailto:[EMAIL PROTECTED]]
Envoyi : mercredi 8 janvier 2003 13:20
@ : [EMAIL PROTECTED]
Objet : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM
MVS server (mq 2.1)


David,

You are using a get option that is not valid on MVS.
My first guess would be that in your program you have something like this:

gmo.Version = MQGMO_VERSION_2; /* Avoid need to reset Message  */
gmo.MatchOptions = MQMO_NONE;  /* ID and Correlation ID before */
   /* every MQGET  */

This does work if you connect to a queue manager on Windows or Unix but
not on MVS.

Instead of using the above options, you have to reset the Message ID and
Correlation ID before every(!) MQGET.

Like this:

memcpy(md.MsgId, MQMI_NONE, sizeof(md.MsgId)); memcpy(md.CorrelId,
MQCI_NONE, sizeof(md.CorrelId));

I hope this helps.
Peter

--- COHEN David <[EMAIL PROTECTED]> wrote:
> Dear all
>
> I have a question regarding MQSeries 5.2.1 installed on an Windows
> 2000 as a client And MQSeries 2.1 installed on an IBM MVS as a server.
> When trying to do an MQGET on a queue I receive an error message 2,
> 2046.
>
> The MQGET connects fine to the Channel and to the Queue but when
> trying to retrive the message on the IBM MVS side the error 2, 2046
> appears. We can see on the IBM MVS side the error
>
> Csqx 208E error receiving data code 461
>
> I do not know if it is related
>
> ***
> Changing current directory to c:\rightfax\production\bin Connected to
> 'RightFAX' (0,0) Opened Queue 'RF_Queue'  (0,0) Creating primary
> buffer of size 64 Ko Unable to retrieve message error 2, 2046
> ***
>
> If I install

Re: GETTING 2035 ON MQOPEN IN NT

2003-01-14 Thread Beinert, William
I spent yesterday afternoon trying to get around this same issue, unsuccesfully, even 
though I setmqaut myself and my group with every conceivable authority.

I beat the problem by removing the + MQOO_ALTERNATE_USER_AUTHORITY from the MQOPEN and 
adding MQPMO_SET_IDENTITY_CONTEXT to the MQPUT options. The message was then put under 
the identity of md.UserIdentifier and it worked just fine.

HTH

Bill Beinert
Systems Programming
Con Edison
(212) 460-4853

When they took the fourth amendment,
   I was quiet because I didn't deal drugs!
When they took the sixth amendment,
   I was quiet because, I was innocent.
When they took the second amendment,
   I was quiet because I didn't own a gun!
Now they've taken the first amendment,
   and I can say (or do) nothing about it.
The Second Amendment is in place in case they ignore the others.
MODWN DAbE


-Original Message-
From: Middleware Group Mailbox [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 1:33 PM
To: [EMAIL PROTECTED]
Subject: GETTING 2035 ON MQOPEN IN NT


Hi,

I have a C/MQ program secsput.c on NT that tries to open a remote queue
(REM.SECURITY.TEST.Q) with these options:

O_options = MQOO_OUTPUT /* open queue for
output*/
 + MQOO_FAIL_IF_QUIESCING   /* but not
if MQM stopping  */
 + MQOO_SET_ALL_CONTEXT /* set all
context */
 + MQOO_ALTERNATE_USER_AUTHORITY;   /* alternate user
*/

But when I run the program on a DOS windows:  >secsput REM.SECURITY.TEST.Q

 I got the follow error MQOPEN eneded with error 2035.

The mq log says this:

01/14/2003  13:12:34
AMQ8075: Authorization failed because the SID for entity '' cannot be
obtained.

EXPLANATION:
The Object Authority Manager was unable to obtain a SID for the specified
entity.
ACTION:
Ensure that the entity is valid, and that all necessary domain controllers
are
available.

I have no problem using >amqsput REM.SECURITY.TEST.Q

Any idea why?

Thanks,
Mohamed.

===
This email/fax message is for the sole use of the intended recipients(s) and
may contain confidential and privileged information.  Any unauthorized
review, use, disclosure or distribution of this email/fax is prohibited.  If
you are not the intended recipient, please contact the sender by email/fax
and destroy all paper and electronic copies of the original 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



GETTING 2035 ON MQOPEN IN NT

2003-01-14 Thread Middleware Group Mailbox
Hi,

I have a C/MQ program secsput.c on NT that tries to open a remote queue
(REM.SECURITY.TEST.Q) with these options:

O_options = MQOO_OUTPUT /* open queue for
output*/
 + MQOO_FAIL_IF_QUIESCING   /* but not
if MQM stopping  */
 + MQOO_SET_ALL_CONTEXT /* set all
context */
 + MQOO_ALTERNATE_USER_AUTHORITY;   /* alternate user
*/

But when I run the program on a DOS windows:  >secsput REM.SECURITY.TEST.Q

 I got the follow error MQOPEN eneded with error 2035.

The mq log says this:

01/14/2003  13:12:34
AMQ8075: Authorization failed because the SID for entity '' cannot be
obtained.

EXPLANATION:
The Object Authority Manager was unable to obtain a SID for the specified
entity.
ACTION:
Ensure that the entity is valid, and that all necessary domain controllers
are
available.

I have no problem using >amqsput REM.SECURITY.TEST.Q

Any idea why?

Thanks,
Mohamed.

===
This email/fax message is for the sole use of the intended recipients(s) and
may contain confidential and privileged information.  Any unauthorized
review, use, disclosure or distribution of this email/fax is prohibited.  If
you are not the intended recipient, please contact the sender by email/fax
and destroy all paper and electronic copies of the original 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



RE : RE : Re: MQSeries 5.2.1 and 2046 error between Win2000 client and IBM MVS server (mq 2.1)

2003-01-14 Thread COHEN David
Thank you sir. I will test right now

David COHEN


-Message d'origine-
De : Morag Hughson [mailto:[EMAIL PROTECTED]] 
Envoyé : mardi 14 janvier 2003 18:34
À : [EMAIL PROTECTED]
Objet : RE : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM MVS 
server (mq 2.1)


MQSeries for OS/390 V2.1 doesn't support MQMD_VERSION_2. I think that may your problem

Cheers
Morag

Morag Hughson
WebSphere MQ for z/OS Development
Internet: [EMAIL PROTECTED]



   

  COHEN David  

cc: 

  Sent by: MQSeriesSubject:  RE :  Re: MQSeries 5.2.1 
and 2046 error between Win2000   
  List  cleint and IBM   MVS   
   server (mq 2.1)  
   

   

   

  14/01/2003 16:40 

  Please respond to

  MQSeries List

   

   




Dear Sir,

Here is how all the structures look in MQGET. I am not sure which ones to disable and 
replace with the memset. If you could send me your ideas so I can build another 
version. Thank you


MQODmqod= {MQOD_DEFAULT}; // Object
description
MQMDmqmd= {MQMD_DEFAULT}; // Message
Descriptor
MQGMO   mqgmo   = {MQGMO_DEFAULT};// Get
message options
MQCNO   mqcno   = {MQCNO_DEFAULT};//
Connection Options
MQCDmqcd= {MQCD_CLIENT_CONN_DEFAULT}; // Client
Definition

mqcno.Version   = MQCNO_VERSION_2;
mqcno.ClientConnPtr = &mqcd;

mqod.ObjectType = MQOT_Q;

mqmd.Version= MQMD_VERSION_2; //
Version-2 message descriptor structure
mqmd.Encoding   = MQENC_NATIVE;   //
Native machine encoding.
mqmd.CodedCharSetId = MQCCSI_Q_MGR;   //
Queue manager's coded character set identifier.

mqgmo.Version   = MQGMO_VERSION_2;//
Version-2 get-message options structure.
mqgmo.Segmentation  = MQSEG_INHIBITED;//
Segmentation not allowed.

//No -O was specified.
if (bDefaultOptions) {
mqgmo.Options   = MQGMO_NO_WAIT | //
Return immediately if no suitable message.
MQGMO_FAIL_IF_QUIESCING |   // Fail if
queue manager is quiescing.
MQGMO_CONVERT | // Convert
message data.
MQGMO_COMPLETE_MSG |// Only
complete logical messages are retrievable.
MQGMO_ALL_MSGS_AVAILABLE |  // All messages in
group must be available.
MQGMO_ALL_SEGMENTS_AVAILABLE;   // All segments in
a
logical message must be available.
}
mqgmo.MatchOptions  = MQMO_NONE;
// No matches.

iOpenOptions= MQOO_INPUT_AS_Q_DEF |   // Open queue
to get
messages using queue-defined default.
MQOO_FAIL_IF_QUIESCING; // Fail if queue manager is
quiescing.


David COHEN




-Message d'origine-
De : Peter Uranyi [mailto:[EMAIL PROTECTED]]
Envoyé : mercredi 8 janvier 2003 13:20
À : [EMAIL PROTECTED]
Objet : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM MVS server 
(mq 2.1)


David,

You are using a get option that is not valid on MVS.
My first guess would be that in your program you have something like this:

gmo.Version = MQGMO_VERSION_2; /* Avoid need to reset Message  */ gmo.MatchOptions = 
MQMO_NONE;  /* ID and Correlation ID before */
 

RE : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM MVS server (mq 2.1)

2003-01-14 Thread Morag Hughson
MQSeries for OS/390 V2.1 doesn't support MQMD_VERSION_2. I think that may
your problem

Cheers
Morag

Morag Hughson
WebSphere MQ for z/OS Development
Internet: [EMAIL PROTECTED]



   

  COHEN David  

cc: 

  Sent by: MQSeriesSubject:  RE :  Re: MQSeries 5.2.1 
and 2046 error between Win2000   
  List  cleint and IBM   MVS   
   server (mq 2.1)  
   

   

   

  14/01/2003 16:40 

  Please respond to

  MQSeries List

   

   




Dear Sir,

Here is how all the structures look in MQGET. I am not sure which ones to
disable and replace with the memset. If you could send me your ideas so I
can build another version.
Thank you


MQODmqod= {MQOD_DEFAULT}; // Object
description
MQMDmqmd= {MQMD_DEFAULT}; // Message
Descriptor
MQGMO   mqgmo   = {MQGMO_DEFAULT};// Get
message options
MQCNO   mqcno   = {MQCNO_DEFAULT};//
Connection Options
MQCDmqcd= {MQCD_CLIENT_CONN_DEFAULT}; // Client
Definition

mqcno.Version   = MQCNO_VERSION_2;
mqcno.ClientConnPtr = &mqcd;

mqod.ObjectType = MQOT_Q;

mqmd.Version= MQMD_VERSION_2; //
Version-2 message descriptor structure
mqmd.Encoding   = MQENC_NATIVE;   //
Native machine encoding.
mqmd.CodedCharSetId = MQCCSI_Q_MGR;   //
Queue manager's coded character set identifier.

mqgmo.Version   = MQGMO_VERSION_2;//
Version-2 get-message options structure.
mqgmo.Segmentation  = MQSEG_INHIBITED;//
Segmentation not allowed.

//No -O was specified.
if (bDefaultOptions) {
mqgmo.Options   = MQGMO_NO_WAIT | //
Return immediately if no suitable message.
MQGMO_FAIL_IF_QUIESCING |   // Fail if
queue manager is quiescing.
MQGMO_CONVERT | // Convert
message data.
MQGMO_COMPLETE_MSG |// Only
complete logical messages are retrievable.
MQGMO_ALL_MSGS_AVAILABLE |  // All messages in
group must be available.
MQGMO_ALL_SEGMENTS_AVAILABLE;   // All segments in
a
logical message must be available.
}
mqgmo.MatchOptions  = MQMO_NONE;
// No matches.

iOpenOptions= MQOO_INPUT_AS_Q_DEF |   // Open queue
to get
messages using queue-defined default.
MQOO_FAIL_IF_QUIESCING; // Fail if queue manager is
quiescing.


David COHEN




-Message d'origine-
De : Peter Uranyi [mailto:[EMAIL PROTECTED]]
Envoyé : mercredi 8 janvier 2003 13:20
À : [EMAIL PROTECTED]
Objet : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM
MVS server (mq 2.1)


David,

You are using a get option that is not valid on MVS.
My first guess would be that in your program you have something like this:

gmo.Version = MQGMO_VERSION_2; /* Avoid need to reset Message  */
gmo.MatchOptions = MQMO_NONE;  /* ID and Correlation ID before */
   /* every MQGET  */

This does work if you connect to a queue manager on Windows or Unix but not
on MVS.

Instead of using the above options, you have to reset the Message ID and
Correlation ID before every(!) MQGET.

Like this:

memcpy(md.MsgId,

Re: Webshpere MQSeries

2003-01-14 Thread Gorse, Darry
Have a look at: http://www-3.ibm.com/software/ts/mqseries/mq_renaming.html

Of course if you look at the Q15 on FAQS, you should note that IBM uses A16,
another renaming effort!

Cheers,
Darry

-Original Message-
From: Prithwiraj Basu [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 9:32 AM
To: [EMAIL PROTECTED]
Subject: Webshpere MQSeries


Hi All,

What is the official name of the latest and greatest IBM MQSeries software?
Is it simply called Webshpere MQSeries or does it have a version number as
well?  Thank you.

Prithwiraj Basu

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



Segmentation on OpenVMS

2003-01-14 Thread Joshi, A (Anant)
Hi,

Can anyone please tell me MQSeries Client on
OpenVMS supports segmentation?
We are exploring if we can use MQSeries to
transfer larger files from OpenVMS nodes to others.

Thanks

==
This email (including any attachments to it) is confidential, legally privileged, 
subject to copyright and is sent for the personal attention of the intended recipient 
only. If you have received this email in error, please advise us immediately and 
delete it. You are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly prohibited.Although 
we have taken reasonable precautions to ensure no viruses are present in this email, 
we cannot accept responsibility for any loss or damage arising from the viruses in 
this email or attachments.We exclude any liability for the content of this email, or 
for the consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently confirmed in 
writing. If this email contains an offer, that should be considered as an invitation 
to treat.


==

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 : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM MVS server (mq 2.1)

2003-01-14 Thread COHEN David
Dear Sir,

Here is how all the structures look in MQGET. I am not sure which ones to disable and 
replace with the memset. If you could send me your ideas so I can build another 
version.
Thank you


MQODmqod= {MQOD_DEFAULT}; // Object
description
MQMDmqmd= {MQMD_DEFAULT}; // Message
Descriptor
MQGMO   mqgmo   = {MQGMO_DEFAULT};// Get
message options
MQCNO   mqcno   = {MQCNO_DEFAULT};//
Connection Options
MQCDmqcd= {MQCD_CLIENT_CONN_DEFAULT}; // Client
Definition

mqcno.Version   = MQCNO_VERSION_2;
mqcno.ClientConnPtr = &mqcd;

mqod.ObjectType = MQOT_Q;

mqmd.Version= MQMD_VERSION_2; //
Version-2 message descriptor structure
mqmd.Encoding   = MQENC_NATIVE;   //
Native machine encoding.
mqmd.CodedCharSetId = MQCCSI_Q_MGR;   //
Queue manager's coded character set identifier.

mqgmo.Version   = MQGMO_VERSION_2;//
Version-2 get-message options structure.
mqgmo.Segmentation  = MQSEG_INHIBITED;//
Segmentation not allowed.

//No -O was specified.
if (bDefaultOptions) {
mqgmo.Options   = MQGMO_NO_WAIT | //
Return immediately if no suitable message.  
MQGMO_FAIL_IF_QUIESCING |   // Fail if
queue manager is quiescing.
MQGMO_CONVERT | // Convert
message data.
MQGMO_COMPLETE_MSG |// Only
complete logical messages are retrievable.
MQGMO_ALL_MSGS_AVAILABLE |  // All messages in
group must be available. 
MQGMO_ALL_SEGMENTS_AVAILABLE;   // All segments in a
logical message must be available.
}
mqgmo.MatchOptions  = MQMO_NONE;
// No matches.

iOpenOptions= MQOO_INPUT_AS_Q_DEF |   // Open queue to get
messages using queue-defined default.
MQOO_FAIL_IF_QUIESCING; // Fail if queue manager is
quiescing.


David COHEN




-Message d'origine-
De : Peter Uranyi [mailto:[EMAIL PROTECTED]] 
Envoyé : mercredi 8 janvier 2003 13:20
À : [EMAIL PROTECTED]
Objet : Re: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM MVS server 
(mq 2.1)


David,

You are using a get option that is not valid on MVS.
My first guess would be that in your program you have something like this:

gmo.Version = MQGMO_VERSION_2; /* Avoid need to reset Message  */ gmo.MatchOptions = 
MQMO_NONE;  /* ID and Correlation ID before */
   /* every MQGET  */

This does work if you connect to a queue manager on Windows or Unix but not on MVS.

Instead of using the above options, you have to reset the Message ID and Correlation 
ID before every(!) MQGET.

Like this:

memcpy(md.MsgId, MQMI_NONE, sizeof(md.MsgId)); memcpy(md.CorrelId, MQCI_NONE, 
sizeof(md.CorrelId));

I hope this helps.
Peter

--- COHEN David <[EMAIL PROTECTED]> wrote:
> Dear all
>
> I have a question regarding MQSeries 5.2.1 installed on an Windows 
> 2000 as a client And MQSeries 2.1 installed on an IBM MVS as a server. 
> When trying to do an MQGET on a queue I receive an error message 2, 
> 2046.
>
> The MQGET connects fine to the Channel and to the Queue but when 
> trying to retrive the message on the IBM MVS side the error 2, 2046 
> appears. We can see on the IBM MVS side the error
>
> Csqx 208E error receiving data code 461
>
> I do not know if it is related
>
> ***
> Changing current directory to c:\rightfax\production\bin Connected to 
> 'RightFAX' (0,0) Opened Queue 'RF_Queue'  (0,0)
> Creating primary buffer of size 64 Ko Unable to retrieve message error 2,
> 2046
> ***
>
> If I install an MQSeries 5.2.1 on another Windows 2000 as a server and 
> define the queues the same way as on the IBM everything works fine
>
> Any idea ?
>
> David COHEN
>
> 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

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 : Re: MQSeries 5.2.1 and 2046 error between Win2000 client and IBM MVS server (mq 2.1)

2003-01-14 Thread COHEN David
Dear all 

Environment : MQSeries Server on IBM MVS and MQSeries 5.2.1 on a windows 2000 a a 
client
When generating an MQGET form the client we get a 2, 2046 error

Here is how all the structures look in MQGET. I am not sure which ones to disable and 
replace with the memset. If somebody knows then send me the ideas so  I can build 
another version

Thank you


MQODmqod= {MQOD_DEFAULT}; // Object
description
MQMDmqmd= {MQMD_DEFAULT}; // Message
Descriptor
MQGMO   mqgmo   = {MQGMO_DEFAULT};// Get
message options
MQCNO   mqcno   = {MQCNO_DEFAULT};//
Connection Options
MQCDmqcd= {MQCD_CLIENT_CONN_DEFAULT}; // Client
Definition

mqcno.Version   = MQCNO_VERSION_2;
mqcno.ClientConnPtr = &mqcd;

mqod.ObjectType = MQOT_Q;

mqmd.Version= MQMD_VERSION_2; //
Version-2 message descriptor structure
mqmd.Encoding   = MQENC_NATIVE;   //
Native machine encoding.
mqmd.CodedCharSetId = MQCCSI_Q_MGR;   //
Queue manager's coded character set identifier.

mqgmo.Version   = MQGMO_VERSION_2;//
Version-2 get-message options structure.
mqgmo.Segmentation  = MQSEG_INHIBITED;//
Segmentation not allowed.

//No -O was specified.
if (bDefaultOptions) {
mqgmo.Options   = MQGMO_NO_WAIT | //
Return immediately if no suitable message.  
MQGMO_FAIL_IF_QUIESCING |   // Fail if
queue manager is quiescing.
MQGMO_CONVERT | // Convert
message data.
MQGMO_COMPLETE_MSG |// Only
complete logical messages are retrievable.
MQGMO_ALL_MSGS_AVAILABLE |  // All messages in
group must be available. 
MQGMO_ALL_SEGMENTS_AVAILABLE;   // All segments in a
logical message must be available.
}
mqgmo.MatchOptions  = MQMO_NONE;
// No matches.

iOpenOptions= MQOO_INPUT_AS_Q_DEF |   // Open queue to get
messages using queue-defined default.
MQOO_FAIL_IF_QUIESCING; // Fail if queue manager is
quiescing.


David COHEN
Direction générale
Tél : 33 1 40 87 68 65
Mob:33 6 85 91 16 05
Fax :   33 1 40 87 11 27



-Message d'origine-
De : Wyatt, T. Rob [mailto:[EMAIL PROTECTED]] 
Envoyé : mercredi 8 janvier 2003 17:08
À : [EMAIL PROTECTED]
Objet : Re: MQSeries 5.2.1 and 2046 error between Win2000 client and IBM MVS server 
(mq 2.1)


David,

2046 is listed as OPTIONS_ERROR.  This means that your GET options are not correct.  
Please reply to the list with the code lines that set up your MQGMO fields.

-- T.Rob

-Original Message-
From: COHEN David [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 6:19 AM
To: [EMAIL PROTECTED]
Subject: MQSeries 5.2.1 and 2046 error between Win2000 cleint and IBM MVS server (mq 
2.1)


Dear all

I have a question regarding MQSeries 5.2.1 installed on an Windows 2000 as a client 
And MQSeries 2.1 installed on an IBM MVS as a server. When trying to do an MQGET on a 
queue I receive an error message 2, 2046.

The MQGET connects fine to the Channel and to the Queue but when trying to retrive the 
message on the IBM MVS side the error 2, 2046 appears. We can see on the IBM MVS side 
the error

Csqx 208E error receiving data code 461

I do not know if it is related

***
Changing current directory to c:\rightfax\production\bin Connected to 'RightFAX' (0,0) 
Opened Queue 'RF_Queue'  (0,0) Creating primary buffer of size 64 Ko Unable to 
retrieve message error 2, 2046
***

If I install an MQSeries 5.2.1 on another Windows 2000 as a server and define the 
queues the same way as on the IBM everything works fine

Any idea ?

David COHEN

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

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: analysis of MQ SMF records 115 and 116

2003-01-14 Thread john gilmore
I have some programs that analyze these records.  They in fact run on a mainframe, but that is adventitious.  I could run most of them on my Windoze workstation if I judged it sensible to download files of the (large) sizes involved.   What is important is that these and other SMF records are, in the jargon, self-defining ones.   Consider the PL/I structure declaration/template   declare 1 rec based(recp),    2 vhi binary fixed(15,0),    2 csl binary fixed(15,0),    2 vla(avhi refer(rec.vhi)) binary fixed(31,0),    2 csv character(acsl refer(rec.csl)) ;   declare (avhi, acsl) binary fixed(15,0) ;   In an existing instance of the structure/record rec, rec.vla is a fullword array of vhi elements and rec.csv is an SBCS (character) string csl bytes in length.  Moreover, the values of rec.vhi and rec.csl differ in general from one instance of rec to another.     Since PL/I and of course the HLASM, the mainframe High Level ASseMbler), support these records, their analysis in a PL/I or HLASM procedure is straightforward.  In C or Java it is notoriously difficult.  (Note also that while COBOL ODO groups appear to have some of the characteristics of PL/I self-defining refer-containing structures they are in fact very different.)   Extended use of assembly language on a workstation is usually ill-advised.  (Most workstation assemblers are so minimalist that they appear to a would-be user to have  had discouraging their use as one of their principal design objectives.)  IBM does make a version of PL/I, implemented originally for OS/2, available for use under Windoze too; and there are also some quondam DEC implementations available.  If (a) you know some PL/I and (b) you have access to a mainframe or other PL/I compiler and run-time library, I can make some of these programs available to you.     If not, I suggest the use of a package or mainframe SAS (which can also handle such self-defining records, albeit clumsily). John GilmoreSystemCraft LLCThe opinions expressed above are mine alone. In particular, they are not necessarily shared by my company or its clients.


Re: Analysis of MQ SMF Records Type 115 and 116

2003-01-14 Thread Kinlen, Dan
What if you do not have SAS ?

-Original Message-
From: Jan van Kemenade [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 9:24 AM
To: [EMAIL PROTECTED]
Subject: Re: Analysis of MQ SMF Records Type 115 and 116


> Does anyone have any programs or aware of packages (other than
Merrill's
> MXG ) that will assist in analyzing and reporting on MQ using the MVS
SMF
> Type 115 and 116 records?

There's SupportPac MP1B : http://www-
3.ibm.com/software/ts/mqseries/txppacs/mp1b.html


Cheers, Jan.
-/
/&Jan van Kemenade
\&www.cressida.info
-\

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: 2059 in Applet (only from a browser though???)

2003-01-14 Thread David C. Partridge
Can you run as a Java application (as distinct from applet)?   Java
applications can do (just about) what they want in this regard.

David

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: 2059 in Applet (only from a browser though???)

2003-01-14 Thread James Kingdon
Appendix F of the Using Java manual may be of some use.

Regards,
James.

Potkay, Peter M (PLC, IT) wrote:


I guess there is no way for this to work. By design, applets loaded in a
browser cannot make a network connection to another computer.
http://java.sun.com/sfaq/#socket


I think I will have to try this idea by using a JSP page that refreshes
itself every 5 seconds or so to give updated queue info.


Still curious why the applet run from the applet viewer in IDE works but not
from the applet viewer from the command prompt.
And why does IBM put that note about 2059 errors and security settings in
the sample applet code? Is there a way to override the applets inability to
connect to a remote computer?




Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906


-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2003 11:21 AM
To: [EMAIL PROTECTED]
Subject: 2059 in Applet (only from a browser though???)


I wrote a little applet that connects to a QM and gives you a depth on a
queue. There is a refresh button to get the most current depth of the queue.
When I execute this applet from my IDE (VisualCafe 4.5.1 Enterprise), it
works just great. But if I try to invoke the applet from a browser, the
applet fails to connect and gives a 2059 error. The below errors are also
thrown to the console. I get the same negative results when invoking this
applet from the AppletViewer from the command line.

I don't understand why the applet works in the IDE and not in the browser. I
did see this comment at the top of sample applet code in the Using Java MQ
manual:

***
// Note. If you receive MQ error 2 reason 2059 and you are sure your MQ and
TCPIP
// setup is correct,
// you should click on the "Applet" selection in the Applet viewer window
// select properties, and change "Network access" to unrestricted.

***


In my applet viewer window, I go to Applet...Properties and set the Class
Access to Unrestricted. It seems to make no diff either way. There is no
Network access setting.
When I run the applet from the IDE (and unselect the option for the IDE to
start up the applet in a browser), the applet works fine. When I click on
the applet viewer properties from here, the class access is again
unrestricted, but the Http proxy port # is blank. In the applet viewer, I
can't change the Http proxy port# from the prefilled 80. I space it out and
it reverts back to port 80. Is that a clue?


Here is the error thrown to the console:
*
Java(TM) Plug-in: Version 1.3.1_03
Using JRE version 1.3.1_03 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\PLAAHO Proxy Configuration:
Manual Configuration  Proxy: ftp=internet:80;http=internet:80  Proxy
Overrides: *thehartford.com,,localhost:49213,127.0.0.1,

c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
q:   hide console
s:   dump system properties
t:   dump thread list
x:   clear classloader cache
0-5: set trace level to 
 openConnection about to
start Version 1.1 MQJE001: An MQException occurred: Completion Code 2,
Reason 2059
MQJE012: Security error - cannot connect to host 157.209.105.95
MQJE001: Completion Code 2, Reason 2059
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2059 at
com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:172)
at
com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQCl
ientManagedConnectionFactoryJ11.java:270)   at
com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQCli
entManagedConnectionFactoryJ11.java:290)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:682)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:620) at
com.ibm.mq.MQQueueManager.(MQQueueManager.java:393)   at
Applet5.openConnection(Applet5.java:91) at
Applet5.start(Applet5.java:62)  at sun.applet.AppletPanel.run(Unknown
Source) at java.lang.Thread.run(Unknown Source) getcause=null
openConnection It didn't work 100 percent: CC=2 RC=2059 openConnection done
GENERAL EXCEPTION=null refreshDepths done GENERAL EXCEPTION=null
refreshDepths done







Peter Potkay



This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary,

Webshpere MQSeries

2003-01-14 Thread Prithwiraj Basu
Hi All,

What is the official name of the latest and greatest IBM MQSeries software?
Is it simply called Webshpere MQSeries or does it have a version number as
well?  Thank you.

Prithwiraj Basu

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: Analysis of MQ SMF Records Type 115 and 116

2003-01-14 Thread Bullock, Rebecca (CSC)
Milt, there's a SupportPac that reads in the SMF data. Sorry, I'm not sure
the number, but it MIGHT be MP1B.  -- Rebecca

Rebecca Bullock
Computer Sciences Corporation
MFCoE/Newark CS Team

Educational Testing Service Account
Princeton, NJ 08541

email: [EMAIL PROTECTED] or [EMAIL PROTECTED]


-Original Message-
From: Milton Weinberger [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 9:00 AM
To: [EMAIL PROTECTED]
Subject: Analysis of MQ SMF Records Type 115 and 116


Does anyone have any programs or aware of packages (other than Merrill's
MXG ) that will assist in analyzing and reporting on MQ using the MVS SMF
Type 115 and 116 records?

Has anyone moved these records to a distributed platform to work with them
versus analysis using tools on MVS?

Thanks.
Milt





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.

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 e-mail and any files transmitted with it may contain privileged or
confidential information. It is solely for use by the individual for whom
it is intended, even if addressed incorrectly. If you received this e-mail
in error, please notify the sender; do not disclose, copy, distribute, or
take any action in reliance on the contents of this information; and delete
it from your system. Any other use of this e-mail is prohibited. Thank you
for your compliance.

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: Analysis of MQ SMF Records Type 115 and 116

2003-01-14 Thread Jan van Kemenade
> Does anyone have any programs or aware of packages (other than
Merrill's
> MXG ) that will assist in analyzing and reporting on MQ using the MVS
SMF
> Type 115 and 116 records?

There's SupportPac MP1B : http://www-
3.ibm.com/software/ts/mqseries/txppacs/mp1b.html


Cheers, Jan.
-/
/&Jan van Kemenade
\&www.cressida.info
-\

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: 2059 in Applet (only from a browser though???)

2003-01-14 Thread Potkay, Peter M (PLC, IT)
I guess there is no way for this to work. By design, applets loaded in a
browser cannot make a network connection to another computer.
http://java.sun.com/sfaq/#socket


I think I will have to try this idea by using a JSP page that refreshes
itself every 5 seconds or so to give updated queue info.


Still curious why the applet run from the applet viewer in IDE works but not
from the applet viewer from the command prompt.
And why does IBM put that note about 2059 errors and security settings in
the sample applet code? Is there a way to override the applets inability to
connect to a remote computer?




Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906


-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2003 11:21 AM
To: [EMAIL PROTECTED]
Subject: 2059 in Applet (only from a browser though???)


I wrote a little applet that connects to a QM and gives you a depth on a
queue. There is a refresh button to get the most current depth of the queue.
When I execute this applet from my IDE (VisualCafe 4.5.1 Enterprise), it
works just great. But if I try to invoke the applet from a browser, the
applet fails to connect and gives a 2059 error. The below errors are also
thrown to the console. I get the same negative results when invoking this
applet from the AppletViewer from the command line.

I don't understand why the applet works in the IDE and not in the browser. I
did see this comment at the top of sample applet code in the Using Java MQ
manual:

***
// Note. If you receive MQ error 2 reason 2059 and you are sure your MQ and
TCPIP
// setup is correct,
// you should click on the "Applet" selection in the Applet viewer window
// select properties, and change "Network access" to unrestricted.

***


In my applet viewer window, I go to Applet...Properties and set the Class
Access to Unrestricted. It seems to make no diff either way. There is no
Network access setting.
When I run the applet from the IDE (and unselect the option for the IDE to
start up the applet in a browser), the applet works fine. When I click on
the applet viewer properties from here, the class access is again
unrestricted, but the Http proxy port # is blank. In the applet viewer, I
can't change the Http proxy port# from the prefilled 80. I space it out and
it reverts back to port 80. Is that a clue?


Here is the error thrown to the console:
*
Java(TM) Plug-in: Version 1.3.1_03
Using JRE version 1.3.1_03 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\PLAAHO Proxy Configuration:
Manual Configuration  Proxy: ftp=internet:80;http=internet:80  Proxy
Overrides: *thehartford.com,,localhost:49213,127.0.0.1,

c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
q:   hide console
s:   dump system properties
t:   dump thread list
x:   clear classloader cache
0-5: set trace level to 
 openConnection about to
start Version 1.1 MQJE001: An MQException occurred: Completion Code 2,
Reason 2059
MQJE012: Security error - cannot connect to host 157.209.105.95
MQJE001: Completion Code 2, Reason 2059
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2059 at
com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:172)
at
com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQCl
ientManagedConnectionFactoryJ11.java:270)   at
com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQCli
entManagedConnectionFactoryJ11.java:290)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:682)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:620) at
com.ibm.mq.MQQueueManager.(MQQueueManager.java:393)   at
Applet5.openConnection(Applet5.java:91) at
Applet5.start(Applet5.java:62)  at sun.applet.AppletPanel.run(Unknown
Source) at java.lang.Thread.run(Unknown Source) getcause=null
openConnection It didn't work 100 percent: CC=2 RC=2059 openConnection done
GENERAL EXCEPTION=null refreshDepths done GENERAL EXCEPTION=null
refreshDepths done







Peter Potkay



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,

Re: removal of expired messages in 5.3

2003-01-14 Thread Bruce Giordano
No.  5.2 did add the feature though that expired messages will be deleted
when they are browsed.  Previously, they only went away on destructive
gets.
  - Bruce



  David Thomas <[EMAIL PROTECTED]>
  To:  
   [EMAIL PROTECTED]
  Sent by: MQSeries List  cc:
  <[EMAIL PROTECTED]>   Subject:   Re: removal of 
expired messages in 5.3



  Monday January 13, 2003 05:11 PM
  Please respond to MQSeries List






Bruce is this feature available on 5.2 ?





Bruce Giordano <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on
01/13/2003 04:29:32 PM

Please respond to MQSeries List <[EMAIL PROTECTED]>

Sent by:MQSeries List <[EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:

Subject:Re: removal of expired messages in 5.3


I'm not aware of a specific utility.  However, on OS/390 you can use the
EXPRYINT queue manager attribute to control how often the queue manager
automatically scans for expired messages.
 - Bruce Giordano



  Firoz Kotta <[EMAIL PROTECTED]>
  To:
  [EMAIL PROTECTED]
  Sent by: MQSeries List  cc:
  <[EMAIL PROTECTED]>   Subject:
  removal of expired messages in 5.3



  Monday January 13, 2003 03:58 PM
  Please respond to MQSeries List






Does version 5.3 come with a utility to remove expired messages. I would
like to know if there are any available for both OS/390 and Aix.

Thanks!

Firoz Kotta

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

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



Analysis of MQ SMF Records Type 115 and 116

2003-01-14 Thread Milton Weinberger
Does anyone have any programs or aware of packages (other than Merrill's
MXG ) that will assist in analyzing and reporting on MQ using the MVS SMF
Type 115 and 116 records?

Has anyone moved these records to a distributed platform to work with them
versus analysis using tools on MVS?

Thanks.
Milt





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.

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: MQSI Buffer Size is initially set to 3732 for all MQGETS?

2003-01-14 Thread Potkay, Peter M (PLC, IT)



In the
PMR we opened, we were told that upon further investigation, IBM found that this
algorithm was not functioning correctly.
 
Quote**

1)  
If the buffer size is increased for a message flow, when
does it get dropped back to its default start value? .
A) When the MQInput node resizes its buffer it should then re-evaluate the
buffer size after 10 more messages or more have passed through the flow. During
these ten messages, it will keep a record of the largest message size to pass
through the flow. If the largest message size since resizing is less than 75% of
the current buffer size then it will reduce it to that smaller value. . However,
whilst examining this functionality we have noticed that the conditions will
never be met which would lead to re-evaluating the buffer size for reduction.
This means we will never reduce the size of the MQGET buffer for the MQInput
node once it has been increased. Can an APAR be raised to address the problem of
'MQInput node msg buffer never reduced after increase'. . 
 
***
 
We
responded that although we agree the algorithim is not working as designed,
something at some point IS dropping the buffer, otherwise we would have never
noticed a problem in the first place.
 
Peter Potkay IBM
MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X
77906 

  -Original Message-From: Kevin Tobin
  [mailto:[EMAIL PROTECTED]]Sent: Monday, January 13, 2003 11:11
  PMTo: [EMAIL PROTECTED]Subject: Re: MQSI Buffer
  Size is initially set to 3732 for all MQGETS?FYI The
  precise formula is If the buffer
  has become "too big"  (less than 3/4 )   for the largest message
  from the last 10 messages received by
  an individual thread - the buffer is shrunk to the size of the largest message
  received since  WMQI last resized
  the buffer + the sizeof the MQMD. Cheers! Kevin
  Kevin TobinSenior IT
  Specialist IBM WebSphere Services Asia PacificLevel 9, 601 Pacific
  Hwy, St Leonards, Sydney NSW 2000Phone:  +61 2 947-88249 Fax:
        +61 2 947-88467Mobile    0421-052-812
    -  International :  +61 421-052-812e-Mail:  
   [EMAIL PROTECTED]
  


  
  Tim
Armstrong/Australia/IBM@IBMAU Sent by: MQSeries List <[EMAIL PROTECTED]>
14/01/03 12:49 PM Please respond to MQSeries List 
                  To:    
   [EMAIL PROTECTED]         cc:      
       
  Subject:        Re: MQSI Buffer Size is
initially set to 3732 for all MQGETS?        If you desperately need it write your own simple
  input node, cant rememberfrom which version of WMQI this becomes
  available.RegardsTim A       
               "Potkay, Peter M 
                     (PLC,
  IT)"                 To:    
    [EMAIL PROTECTED]           
                            
     RTFORD.COM>              
   Subject:  Re: MQSI Buffer Size is initially set to 3732 for all
  MQGETS?                 
     Sent by: MQSeries           
           List         
              
                   
   AC.AT>             
         14/01/2003 11:04       
               Please respond to 
                     MQSeries
  ListThe problem with priming the flow with the 22K
  message is that at somepoint(not as quickly as the documented
  algorithm would suggest, but sometimewithin usually about 8 hrs), MQSI
  drops the buffer size back down based onthe average size of the previous
  messages. So we would constantly have tokeep pumping these fat messages
  through to be sure the buffer stays big.We are also going to be multi
  threaded and clustered as well.We were able to shave enough time in
  other parts of the roundtrip so thatthis is not that critical anymore.
  However it will be nice if we get thisability in the
  future.Peter PotkayIBM MQSeries Certified Specialist,
  Developer[EMAIL PROTECTED]X 77906-Original
  Message-From: Tim Armstrong [mailto:[EMAIL PROTECTED]]Sent:
  Monday, January 13, 2003 5:51 PMTo: [EMAIL PROTECTED]Subject:
  Re: MQSI Buffer Size is initially set to 3732 for all
  MQGETS?Temporary workaround. Push a 22k message with special
  attributes that willwe just discarded by the message flow as soon as
  possible after a restart.This should work for single threaded flows but if
  you are allowingmultithreaded messages flows then you may still encounter
  the problem.RegardsTim A     
                 "Potkay, Peter
  M                   
   (PLC, IT)"                
  To:[EMAIL PROTECTED]           
                            
     RTFORD.COM>              
   Subject:  Re: MQSI BufferSize is initially set to 3732 for all
  MQGETS?                 
     Sent by: MQSeries           
           List         
              
                   
   AC.AT>             
         14/01/2003 08:10       
               Please respond to 
                     MQSeries
  Listfyi, We have put in a formal reques

AW: Re: COBOL Copybook with Redefines clause and WMQI

2003-01-14 Thread Saraswathy A
all the fields have been assigned and in the same order. I even tried setting all  
default values (0 or space) ,instead of my input values.
Still get the same error!

-Ursprüngliche Nachricht-
Von:Alan Stewart [mailto:[EMAIL PROTECTED]]
Gesendet:   Di 14.01.2003 14:30
An: [EMAIL PROTECTED]
Cc: 
Betreff: Re: COBOL Copybook with Redefines clause and WMQI

I get this error when a field is not getting set by some value in the
copybook in order. Check that all fields have been assigned a value or
'touched' with a space for PIC X() fields, 0 for integer fields etc.

Check also that your redefine section is exactly the same length as the
part of the copybook that it is redefining.
Alan




Saraswathy A <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
14/01/2003 07:28 PM
Please respond to
MQSeries List <[EMAIL PROTECTED]>


To
[EMAIL PROTECTED]
cc

Subject
COBOL Copybook with Redefines clause and WMQI






Hi All,


I have messageset that has a copybook imported that contains a redefines
clause and WMQI created a element with the postfix Group001.
I have a message flow that uses a compute node which has the above
messageset as the output format. I get the following error at the output
node.
'  Mismatch between logical definition and message tree'

and if i comment out this Group001 element  i get a different error
message

'illegal choice element'
What changes need to be done while tranformaing ? ,i have WMQI 2.1 for HP

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

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: Conversion problems between IBM MVS Mq 2.1 and Windows 2000 MQ 5.2.1

2003-01-14 Thread David C. Partridge
The data at the MVS end is not necessarily in the CCSID that you think it
is.   I assume that the data is being sent as CCSID 500?  Is that correct?
If so make darn sure that the accented characters and braces are actually at
the code points that match CCSID 500.   It may be that you are using one of
3270 CCSIDs without knowing, but are still sending the data as CCSID = QMGR
CCSID.

On the Windows 2000 system what CCSID is the qmgr set to, and what are you
using to display the message (remember that a console app will probably use
CCSID 850, but notepad will use one of the Windows Western European CCSIDs -
1252 I think, and the codepoints ARE different).

Dave

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: COBOL Copybook with Redefines clause and WMQI

2003-01-14 Thread Alan Stewart

I get this error when a field is not
getting set by some value in the copybook in order. Check that all fields
have been assigned a value or 'touched' with a space for PIC X() fields,
0 for integer fields etc.

Check also that your redefine section
is exactly the same length as the part of the copybook that it is redefining.
Alan






Saraswathy A <[EMAIL PROTECTED]>

Sent by: MQSeries List <[EMAIL PROTECTED]>
14/01/2003 07:28 PM



Please respond to
MQSeries List <[EMAIL PROTECTED]>





To
[EMAIL PROTECTED]


cc



Subject
COBOL Copybook with Redefines
clause and WMQI








Hi All,


I have messageset that has a copybook imported that contains a redefines
clause and WMQI created a element with the postfix Group001.
I have a message flow that uses a compute node which has the above messageset
as the output format. I get the following error at the output node.
'  Mismatch between logical definition and message tree'

and if i comment out this Group001 element  i get a different error
message 

'illegal choice element'
What changes need to be done while tranformaing ? ,i have WMQI 2.1 for
HP

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


This email is 
intended for the named recipient only. The informationcontained in this message may be 
confidential, or commerciallysensitive. If you are not the intended recipient you must 
not reproduceor distribute any part of the email, disclose its contents to any 
otherparty, or take any action in reliance on it. If you have received thisemail in 
error, please contact the sender immediately.  Please deletethis message from your 
computer.



COBOL Copybook with Redefines clause and WMQI

2003-01-14 Thread Saraswathy A
Hi All,


I have messageset that has a copybook imported that contains a redefines clause and 
WMQI created a element with the postfix Group001.
I have a message flow that uses a compute node which has the above messageset as the 
output format. I get the following error at the output node.
'  Mismatch between logical definition and message tree'

and if i comment out this Group001 element  i get a different error message 

'illegal choice element'
What changes need to be done while tranformaing ? ,i have WMQI 2.1 for HP

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: Running multiple brokers from 1 configuration manager V2.1

2003-01-14 Thread Vivekananda Doraswamy
Dennis,

  In message sets, we can duplicate the msgsets with the same name.
But, the new msgset will have a higher "level" number than the original
one. But before doing this, the original msg set should be finalized. For
further details, please check the "Working With Messages" manual.


Thanks & regards ...  Vivek

Vivekananda. D




  Dennis Bryngelson
cc:
  Sent by: MQSeries List   Subject:  Re: Running multiple 
brokers from 1 configuration
  <[EMAIL PROTECTED]> manager V2.1


  01/13/2003 06:27 PM
  Please respond to
  MQSeries List





I can see where the renaming works on flows.  How about message sets (there
is no copy feature that I can see).  What if I want more than 1 version of
a message set open and changing in a development box with 1 config manager?
There is that pesky IDENTIFIER that changes (now I have to change it in the
compute node) for each unique message set

Thanks,
Dennis Bryngelson
Phone: (763) 765-4224
Fax: (763)  765-3820
mailto:[EMAIL PROTECTED]



Vivekananda
Doraswamy To: [EMAIL PROTECTED]
 Subject: Re: Running multiple
brokers from 1 configuration manager
Sent by:   V2.1
MQSeries List



01/13/2003
04:39 AM
Please respond
to MQSeries
List






Dennis,

  There is no inbuilt support for the version control in WMQI. You
might need to do one of the following depending on the number of msg flows
in your config manager.

1) If you have large number of msgflows, you need to use an external
Version control tool .Here you need to import the msgflows from the Version
control tool, do the modification in the Control center and then export
back to the Tool.

2) If the number of msgflows are less, then simply copy the msgflow, paste
it and rename one of the msgflows and use the other one for changes.



Thanks & regards ...  Vivek





  Dennis Bryngelson
cc:
  Sent by: MQSeries List   Subject:  Running
multiple brokers from 1 configuration
  <[EMAIL PROTECTED]> manager V2.1


  01/13/2003 02:41 PM
  Please respond to
  MQSeries List





I am new with working with Websphere Integrator V2.1 and have a question.
We are running a configuration manager and have 13 brokers deployed from
this 1 configuration manager.   If you have a flow and lets say you are
modifying it,  how do you keep it separate from the current version and
still maintain the same name?  (or is this not possible)?  I would
appreciate any thoughts or other peoples solution to this..

Thanks,
Dennis Bryngelson
Phone: (763) 765-4224
Fax: (763)  765-3820
mailto:[EMAIL PROTECTED]
*

PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.

*

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

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