Hello Frank,
I'd be happy to have a look at one of your MQ programs, to see how much needs to done - and how to approach. Provided that your programs are already using the copy members specified in the AMQ3GET4 and AMQ3PUT4 sample programs (you find them in the QRPGLESRC source file in library QMQMSAMP) it should be very straight forward. The two source members also provide an excellent template to use for the most common MQ configurations/applications. Anyway, feel free to reach out, if you still need help.
On a separate but related note, once you get the upgrade sorted out, you might also be interested in the use of workload capping groups to reduce the license footprint of your IBM MQ licensed program - more details can be found here:
https://apimymymy.wordpress.com/2017/09/26/apis-by-example-workload-capping-groups-save-license-fees-and-manage-workload-capacity/
Cheers,
Carsten
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of frank boke
Sent: 10. april 2020 16:48
To: midrange-l-request@xxxxxxxxxxxxxxxxxx; midrange-l@xxxxxxxxxxxxxxxxxx
Subject: MQ Version 9.0 upgrade changing pgm's?
Hi Folks, what needs to be done to get MQ ready for Version 9.0?
We’re at V8 and I saw in the linkdoc that we’re forced to change pgm’s and the person who was our “MQ” programmer is long gone.
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.pro.doc/q127140_.html#q127140___rpgcompat
Are these difficult changes to make?
Anyone out there have the expertise to make the changes quickly or provide details on how to make the changes quickly?
This email message (including all attachments) is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information, or may otherwise be protected by work product or other legal rules. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Unless otherwise indicated in the body of this email, nothing in this communication is intended to operate as an electronic signature and this transmission cannot be used to form, document, or authenticate a contract. Awaze and/or its affiliates may monitor all incoming and outgoing email communications, including the content of emails and attachments, for security, legal compliance, training, quality assurance and other purposes.
The sender believes that this email and any attachments were free of any virus, worm, Trojan horse, malicious code and/or other contaminants when sent. Email transmissions cannot be guaranteed to be secure or error-free, so this message and its attachments could have been infected, corrupted or made incomplete during transmission. By reading the message and opening any attachments, the recipient accepts full responsibility for any viruses or other defects that may arise, and for taking remedial action relating to such viruses and other defects. Neither Awaze nor any of its affiliated entities is liable for any loss or damage arising in any way from, or for errors or omissions in the contents of, this message or its attachments.
midrange.com
