Re: How to get a mgtools syssnap when system is in restricted state and console is locked?

BR2. Same issue with commitment control carried over from BR1.

On Thu, Mar 6, 2025 at 2:43 PM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

Is it IBM that won’t work it or Fortra? BR1 or BR2. I’ve been told
your on your own with the perpetual license versions of any Fortra
supported LPPs that are not subscription based.
Jim Oberholtzer
Agile Technology Architects

On Mar 6, 2025, at 1:06 PM, Rob Berendt <robertowenberendt@xxxxxxxxx>

wrote:

That exit point idea might run the syssnap before the job is technically
hung. Therefore they will discount the value of it. See your last
statement.

On Thu, Mar 6, 2025 at 1:08 PM Marc Rauzier <marc.rauzier@xxxxxxxxx>

wrote:

Le 06/03/2025 à 18:44, Rob Berendt a écrit :
How can I get a mgtools syssnap when system is in restricted state and
console is locked?

BRMS has this issue where they leave a commitment control hanging. I

can

easily duplicate it by simply running
SETUSRBRM USER(QSECOFR) USAGE(*ADMIN)
WRKMEDBRM TYPE(*ERR) LOC(USSI7VTL) SYSNAME(*ALL)
A DSPJOB OPTION(*CMTCTL) shows they leave the commitment control

hanging

I reported this to IBM years ago and the guy with BRMS says they are
incapable of writing code with such an error as this and I must have

been

doing something else. They closed the case.
I've gotten into the habit of signing off/on again before doing

critical

operations. Problem is that I should do my signoff/on immediately

after

those BRMS operations. Instead I wait until after the ENDTCP and

ENDSBS.

So now I'm in restricted state and try the sign off. Normally works.

This

time the job was hung.

If you can reproduce the problem, you can try to set an exit program for
QSYS/SIGNOFF command. This program would test a special value, through a
data-area or anything else for example, that you set before reproducing
the problem and invoke a QMGTOOLS/SYSSNAP command if it finds the
expected special value. This exit program would do nothing in the other
cases to avoid disturbing normal SIGNOFF behavior.

However, I don't know if SYSSNAP invokes any QShell or Java
script/program, which I am quite sure is not allowed in restricted

state.

Opened up a new case.
IBM won't work on this until I get a syssnap while the system is in
restricted state and the console job is hung. I guess it will be years
longer until this gets resolved...

Looks like they don't really want to work on the topic...
--
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.