I don't do the negotiating around here. That's the boss' job.
Original Message:
Sent: Thu January 16, 2025 08:13 AM
From: Rich Malloy
Subject: Simple Migration of BRMS from 5770-BR1 to 5770-BR2
@Robert Berendt - I'm curious as to your experience with the converting to Subscription. As you know (or may know) BR2 is a subscription pgm meaning different license keys and renewal terms etc. Did you have any involvement in that process - what kind of 'credit', if any, did you get from having left over SWMA from your BR1 product that carried over into the cost of BR2.
------------------------------
Rich Malloy
Original Message:
Sent: Wed January 15, 2025 04:02 PM
From: Robert Berendt
Subject: Simple Migration of BRMS from 5770-BR1 to 5770-BR2
Ah, you have to look under member locks. After you hit WRKOBJLCK hit F6 to work with member locks
Lock
Member Job User Type Lock Status
QA1AMB QRWTSRVR QUSER DATA *SHRUPD HELD
QRWTSRVR does not run in the subsystems you're told to end.
------------------------------
Robert Berendt IBMChampion
Business Systems Analyst, Lead
Dekko
Fort Wayne
Original Message:
Sent: Wed January 15, 2025 03:57 PM
From: Robert Berendt
Subject: Simple Migration of BRMS from 5770-BR1 to 5770-BR2
I ended those subsystems. Made sure they were ended.
From another system I ran: WRKOBJBRM OBJ(ROB/A) FROMSYS(GDI)
Checked the locks I checked before. Didn't see any
Tried to save QUSRBRM and two objects were locked:
Cannot allocate object for file QA1AMB in QUSRBRM.
Cannot allocate object for file QA1AOD in QUSRBRM.
Could not find a lock for them.
So on the remote system I got out of the WRKOBJBRM and signed off.
Now I can save QUSRBRM without issues. Just a lucky timing issue? Apparently WRKOBJBRM from a remote system fails to respect those subsystems.
I like to try things apparently IBM hasn't thought of.
------------------------------
Robert Berendt IBMChampion
Business Systems Analyst, Lead
Dekko
Fort Wayne
Original Message:
Sent: Wed January 15, 2025 02:01 PM
From: Robert Berendt
Subject: Simple Migration of BRMS from 5770-BR1 to 5770-BR2
Prior to running DLTLICPGM LICPGM(5770BR1) OPTION(*ALL) I thought I'd check to see if anything was locked.
WRKOBJLCK OBJ(QBRMS) OBJTYPE(*USRPRF)
shows these
Job User
QBRMNET QBRMS
QNMAPINGD QBRMS
Q1ACPDST QBRMS
WRKOBJLCK OBJ(QBRMSYNC) OBJTYPE(*USRPRF)
shows none.
WRKOBJLCK OBJ(QBRM) OBJTYPE(*LIB)
shows these jobs:
Job User
QBRMNET QBRMS
Q1ACPDST QBRMS
Should I be concerned about these prior to running the DLTLICPGM?
------------------------------
Robert Berendt IBMChampion
Business Systems Analyst, Lead
Dekko
Fort Wayne
Original Message:
Sent: Sun October 06, 2024 09:50 PM
From: Brian Nordland
Subject: Simple Migration of BRMS from 5770-BR1 to 5770-BR2
IBM has announced the withdrawal of the 5770-BR1 product ( https://www.ibm.com/docs/en/announcements/eos-eom-non-expiring-brms-cics-msp ) with a replacement product 5770-BR2.
The 5770-BR2 product follows along with IBM's product simplification journey and is a single product option containing all functionality. This means all of the product functionality in Base, Advanced, and Network features are all included in one purchase price. 5770-BR2 is simplified to contain all functionality from 5770-BR1 under a single option. In addition, 5770-BR2 has several new enhancements that are not in 5770-BR1, including the new BRMS web interface.
While it is not possible to have both 5770-BR1 and 5770-BR2 installed on a single partition at the same time, because the library naming is the same, the migration process is straightforward:
1. ✨Recommended PTFs: It is recommended to apply BRMS 5770-BR1 PTFs 7.5 SJ01879, 7.4 SJ01877 to improve the migration to 5770-BR2.
2. 🔃Migration Process: The following page gives additional information on the specific migration steps: BRMS (5770-BR2) Installation.
💡Useful Tip: While you cannot have both 5770-BR1 and 5770-BR2 installed on a single partition at the same time, you do not need to migrate all partitions at once. BRMS continues to support BRMS networks that contain a mixture of 5770-BR1 and 5770-BR2 at the same time. This enables you to take a staged approach with migrations.
------------------------------
Thanks,
Brian Nordland
Director of Development at Fortra
------------------------------