I've been following this MQSeries Clients tutorial in this web site and get stuck in this pb -On my server, I've run my queue manager. I've also created the channel, queue and client connection. It's my only default queue.manager. I've also run other things like channel initiator, command server, listener.On my client, I've set the client connection channel using:C:SET MQSERVER=CHAN2/TCP/130.34. )I've also verify it using:C:SET MQSERVERMQSERVER=CHAN2/TCP/130.34. ) I've checked my reason code - 2059 at this web site:I still can't find the something that I've missed. Can you pls offer me suggestions if you've tried this code b4, thanks.
Web Reason:On MVS/ESA, for CICS applications, this reason can occur on any call if the original connect specified a queue manager whose name was recognized, but which is not available.My response:What do they mean by CISC applications? I've checked that MVS is a stand-alone MVS subsystem. If MVS/ESA refers to a platform, then this will cause no pb to me. I'm working on Windows 2000 on Server and Win NT on Server.
=Web Reason:On OS/400, this reason can also be returned by the MQOPEN and MQPUT1 calls, when MQHCDEFHCONN is specified for the Hconn parameter.If the connection is from an MQ client application, this reason code can occur if there is an error with the client-connection or the corresponding server-connection channel definitions.My response:I've set the channel name the same as server's. I've also verify it. Define client connection channel# create a client-connection channel by setting the MQSERVER environment variable# define channel name, transport type and channel connection nameC:SET MQSERVER=CHAN2/TCP/130.34. )# Verify channel definition by displaying the current settingC:SET MQSERVERMQSERVER=CHAN2/TCP/130.34. And i guess 'amqsputc' takes only 2 parameters.Extract from help file:Running the amqsput and amqsputc samplesThese programs each take 2 parameters:The name of the target queue (required)The name of the queue manager (optional)If a queue manager is not specified, amqsput connects to the default queue manager and amqsputc connects to the queue manager identified by an environment variable or the client channel definition file. Hi viswa,Thanks for ur help. I really need to solve this asap.This is my process: Configure Server machine Creating a queue manager and starting MQSC on the server# create a queue managerC:crtmqm QM1There are 52 days left in the trial period for this copy of MQSeries.MQSeries queue manager created.Creating or replacing default objects for QM1.Default objects statistics: 29 created.
0 failed.Completing setup.Setup completed.# start queue managerC:strmqm QM1There are 52 days left in the trial period for this copy of MQSeries.MQSeries queue manager 'QM1' started. Start MQSeries commands (MQSC)# start MQSeries commandsC:runmqsc QM10784726, 5639-B43 (C) Copyright IBM Corp. Hi viswa,I've managed to solve this problem.I've finally executed the java MQIVP!C:Program FilesMQSeries Clientbinjava MQIVPMQSeries for Java Installation Verification Program5639-B43 (C) Copyright IBM Corp. Hi viswa,Thanks for your early response:) I really need this information very much to code a 'MQIVP similar' java application.For 1.I'll refer to link -I've chosen to useOn Server- MQSeries for the server- Lightweight Directory Access Protocol (LDAP)May I ask if this LDAP is available in the MQSeries v5.2 trial s/w?On Client- MQSeries Client for client- Java Developers Kit (JDK)- MA88: MQSeries classes for Java and MQSeries classes for Java Message ServiceCan you pls kindly tell me if this is enough? I'm confused by using 'VisualAge for Java' to code a Java Message Service application (consists MQSeries and Java codes).They've shown a complete setup process in / Or do you refer this as 2. 'Using the MQ-Jms api.'
Mqseries Using Java Pdf Free
?Will their coding be different too?Thanks for helpping me:)Dawn.