Skip to main content

Upgrading to WebSphere MQ for z/OS Version 7.0

Upgrading to WebSphere MQ for z/OS Version 7.0
===============================================

This section describes the things that you must consider if you are migrating a single queue manager from a previous version of WebSphere® MQ.

First class migration support is provided to WebSphere MQ for z/OS® Version 7.0 from WebSphere MQ for z/OS Version 6.0. This means you can restart a queue manager at WebSphere MQ Version 7.0 by replacing the executable code (for example, the STEPLIB data sets) with equivalent Version 7.0 libraries and then restarting the queue manager. When a backward migration PTF has been applied to Version 6.0 code, it is possible to fall back from Version 7.0 operation to Version 6.0.
Start of changeThe points below can be carried out before or after the initial stage (1) of migrating a single queue manager from a previous version of WebSphere MQ.

* Apply the Version 7.0 coexistence and backward migration PTFs to the Version 6.0 code.
* Restart production WebSphere MQ systems with this PTF-updated Version 6.0 code. Verify correct function before proceeding and review any special actions detailed in the PTFs. If you require fall back at this stage, use normal maintenance procedures to revert to the Version 6.0 code before PTF application.

End of change
Follow these steps to migrate a production queue manager from WebSphere MQ Version for z/OS Version 6.0 to WebSphere MQ Version for z/OS Version 7.0:

1. Install Version 7.0 early code. Refresh the early code level of all queue managers in the LPAR.
2. Restart production WebSphere MQ systems with Version 7.0 code. Verify correct function of existing applications before using any new Version 7.0 functions. If problems become apparent at this stage, fall back to the Version 6.0 code with backward migration PTFs that have been previously validated for your environment.

For a queue-sharing group, apply the Version 6.0 coexistence and backward migration PTFs to all members before you migrate any member to Version 7.0.

For releases earlier than Version 6.0, no backward migration support from Version 7.0 is provided. You can migrate a queue manager from a release earlier than Version 6.0 directly to Version 7.0, but if problems arise there is no good fall back capability. This is not good practice for production systems, but it might be sufficient for a test queue manager. See section Migrating from an earlier unsupported release of WebSphere MQ or MQSeries for further information. Ensure that production systems are fully migrated to Version 6.0 and stability is achieved before migration to Version 7.0.

* Migrating to WebSphere MQ for z/OS Version 7.0
You might need to perform some additional tasks when migrating from a previous version, depending on which of the new features you want to use, and which level of WebSphere MQ you are migrating from. Generally, the earlier the version of WebSphere MQ you are migrating from, the more tasks you need to perform.
* Migrating from Version 6.0
* Start of changeControlling new functionality and backward migration using the OPMODE propertyEnd of change
The availability of new functions and backward migration for WebSphere MQ for z/OS can be controlled using the OPMODE property in the CSQ6SYSP macro.
* Changing to full function WebSphere MQ
* Reverting to previous versions
* Migrating from an earlier unsupported release of WebSphere MQ or MQSeries
Labels:

Comments

Post a Comment

adsrerrapop

Popular posts from this blog

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...
Post a Comment
Read more

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...
143 comments
Read more

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...
Post a Comment
Read more