Re: Calling Program information

Mark S. Waterbury wrote:

I think this will only work if you do not set *INLR *ON.

Mark:

That's possible, though it's been way too long since I've tried anything like what this part of the thread is about. Seems odd, though, that the ENDCMTCTL wouldn't be where the boundary was. Kind of seems to make it irrelevant, particularly since the STRCMTCTL was at the same level.

It was merely a minor comment, more to the thought that it's _possible_ to start along the path of commitment control with very changes to source code. Not the best approach, but sometimes you don't have appropriate access to the source code that's needed. Sometimes you can get the effect through changes to 'control logic' without changing 'application logic'. (And I don't want that to mean that they're separate logics!)

Tom Liotta

> Tom Liotta wrote:

Vern Hamberg wrote:

ENDCMTCTL requested with changes pending. (RB C CM) --- message CPA8350
? CM
Commit operation performed before ending commitment control; reason code
01. --- message CPI8350

So in this case, an explicit commit is needed - either as a COMMIT opcode or %commit BIF, or as a response to inquiry message CPA8350.

But also note the possibility of the COMMIT /command/ being executed just before the ENDCMTCTL command.