Re: Migrating from 5770-BR1 to 5770BR2

Bryan,
What you did will work in 99+% of the times. However, many are under the
false assumption that the BRMS communication subsystems has anything to do
with preventing a lock on a file in QUSRBRM from someone on a remote system
running a WRKMEDBRM against that system being upgraded.

On Thu, Jan 16, 2025 at 10:27 AM Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

i just ended the brms subsystem(s) then did the upgrade.

it was fairly painless, i did do a SAVLICPGM for 5770br1 before deleting
the installing Br2
i also saved qusrbrm.
as i recall there was some post work to get the (still needs lots of
work) web interface started

Bryan

Rob Berendt wrote on 1/16/2025 9:09 AM:

And how does one "just end brms networking" effectively enough that

remote

systems will stop doing remote SQL functions to BRMS files in QUSRBRM
against the QRWTSRVR job in subsystem QUSRWRK?

On Thu, Jan 16, 2025 at 9:12 AM Jim Oberholtzer <

midrangel@xxxxxxxxxxxxxxxxx>

wrote:

Just the instance you are working on


Jim Oberholtzer
Agile Technology Architects

On Jan 16, 2025, at 7:57 AM, Rob Berendt <robertowenberendt@xxxxxxxxx>

wrote:

"just end brms networking". Is that something I have to do on all

systems

which may communicate with this system?
When I opened a case about this with IBM and told them of this their
response was solely:
"Let me know if you still have any additional questions."

On Wed, Jan 15, 2025 at 2:46 PM Jim Oberholtzer <

midrangel@xxxxxxxxxxxxxxxxx>

wrote:

No just end BRmS networking


Jim Oberholtzer
Agile Technology Architects

On Jan 15, 2025, at 1:39 PM, Rob Berendt <

robertowenberendt@xxxxxxxxx>

wrote:

I'll grant you that the network is probably active. So, am I

supposed

to

put the system in restricted state prior to running the DLTLICPGM?

On Wed, Jan 15, 2025 at 2:32 PM Jim Oberholtzer <

midrangel@xxxxxxxxxxxxxxxxx>

wrote:

Looks like network is active.


Jim Oberholtzer
Agile Technology Architects

On Jan 15, 2025, at 1:29 PM, Rob Berendt <

robertowenberendt@xxxxxxxxx>

wrote:

I am trying to follow the instructions at

https://helpsystemswiki.atlassian.net/wiki/spaces/IWT/pages/2765848577/BRMS+5770-BR2+Installation

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?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--

-- .
Bryan

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.