Made the change to the program to execute the COMMIT. It's running now,
the journal isn't being backed up with pending changes.

The leading post wasn't clear. Sorry for that, as I wasn't quite sure what
was going on. I was being told that the Journal was getting backed up
because the files were open. I argued over and over again that isn't the
issue. But I couldn't explain what it could be thus asking for help.
Right before Birgitta post back, the commitment issue hit me. Birgitta
confirmed it.

So far so good.

On Fri, Mar 2, 2012 at 2:00 PM, Michael Schutte <mschutte369@xxxxxxxxx>wrote:

Thanks. If I had it or known to look at it. I wouldn't have asked.

On Mar 2, 2012, at 1:37 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 02-Mar-2012 08:10 , Michael Schutte wrote:

Hope I was clear.

Perhaps clearer to have described the issue with some specifics, the
message(s) that actually diagnosed the issue [spooled joblog with
*seclvl text] that is preventing the action, along with the requested
action that failed, rather than describing what was presumably inferred
from those messages as possibly to be the origin. The description
suggesting that the "issue is that the Journal Commits are backing up
and not executing because the file is still active" is not explicit
about either what the effect of "not executing" was in messaging nor
what was the request that had been made but failed to effect the
"Journal Commits" action with those messages being logged to diagnose
the issue.

Regards, Chuck
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].