Starting Commitment Control

[Guest.Visitor]

On Wednesday, August 05, 1998, 06:30 AM, Jim Adair wrote: We have recently starting using commitment control and everything works great. The problem begins when I try to start commitment control from a CL that is invoked from a commmand that is the initial program in everyones user profile. For some reason it simply won't start. If you run the same command after you have signed on the CL has no problem starting it. My question is why? Thanks! You mean it won't start per some error... or it appears not to have started per no information on WRKJOB OPTION(*CMTCTL)? Does the INLPGM use TFRJOB to finish the CL processing? It seems this has the latter effect; I do not know the expected outcome. Regards, Chuck Comments provided "as is" with no warranties of any kind whatsoever.

[Guest.Visitor]

I meant to suggest that if you follow STRCMTCTL with a TFRJOB in the initial program, you will not see commitment control active. Since you say you do not, then another thing that sometimes happens is that the INLPGM does a CALL QCMD <or similar interactive calls, like to a menuing program> *before* actions such as STRCMTCTL were performed in the program. If this is the case, then only after F3=Exit <or whatever the exit for the called-function is>, will the STRCMTCTL occur. Another thing is if the CL program has a program-scoped message handler that ignores errors <eg. monmsg cpf0000>, then a failed attempt to issue the start would only be a message in the joblog -- so after signing on with a user having this initial program, press F10 to see the previous messages. If there are no errors then use WRKJOB OPTION(*CMTCTL) to see if it was started, but maybe not in the way you had hoped. For example, there is scoping of commitment control; the default is to the activation group -- which by default, is the default activation group. Regardless you should compile the initial program with LOGCLPGM(*YES) for debug purposes for a better idea of what occurs <see DSPJOBLOG just after signing on; much like F10> Also there is no need that your other programs are not CLPs. They can call CL commands via CALL QCAPCMD API <or CALL QCMDEXC>. HTH. Regards, Chuck Comments provided "as is" with no warranties of any kind whatsoever.