+1
it pains me to use the phrase "fire up a green screen"!
Me too!
-Ken Killian-
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve Ferrell via WDSCI-L
Sent: Wednesday, August 21, 2019 9:52 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.6.0.6 SEP not working...
Hi Craig,
What you are (Likely) seeing is your HA software doing a SAVCHGOBJ to capture a snapshot. (I worked on an HA product before RDi.)
Asking for a test library where you can copy your objects to (that isn't being mirrored or backed up) will allow the SEP flow to work more smoothly. Or ask IT to set your snapshot to your lunch hour (or better yet after hours).
You WANT your library and your source mirrored, but the *PGM objects don't need to be. But most HA software work on the library level, so they do a SAVCHGOBJ on your library and that lock alone may mess with the SEP.
This thread did give me some great ideas for "in product diagnosis" to make it easier to find object locks and query QHST so users can see what outside processes may be messing with their sessions.
Trust me, it pains me to use the phrase "fire up a green screen"!
Steve Ferrell
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Craig Richards
Sent: Wednesday, August 21, 2019 8:22 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.6.0.6 SEP not working...
@Steve
Thanks Steve that's interesting to hear about those commands that can upset the SEP.
I sometimes shy away from using the debugger because in my experience it often has issues.
But, on the subject of what you were saying re commands - I know from general editing that fairly often my ctrl-s to save a member will fail because a mimix job has the member locked for a short duration.
Usually if I check QSYSOPR once this has happened I will see:
Save-while-active checkpoint processing for library nnnnnnnnnn complete
Where I am working at the moment they seem to run some kind of save-while-active (I've never looked into the details) at least once during the middle of the day so this might explain why it appears to me that the debugger seems a bit unreliable.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
midrange.com
