Trigger program w/ Commitment Control

[Guest.Visitor]

I mean, this thing is about to whip me ... and that is not good ... I am working in a totally OPM environment. I have a trigger program on a file. It starts commitment control via QCMDEXC. It calls multiple other programs which update/add to other files. The other programs send "smarts" back to tell the trigger program whether to COMIT or ROLBAK ... When either condition occurs, we get a CPF???? (cant remember), about the trigger program running in the same activation group, yatta, yatta, yatta ...does anyone have any idea what this all about ... by the way, does anyone know the value of byte 33 of the PARM1 of a trigger program if commitment control is not in play at the time the trigger program is invoked> ...bud

[Guest.Visitor]

Bud, That CPF???? is a CRITICAL piece of the puzzle. Get the msgid (at least) and we'll proceed.

[Guest.Visitor]

Bud, I did not completely follow your description of this problem, but when a comit or rolbck complains about activation groups, I would guess that you must somehow have something not running in the default activation group. Since OPM programs all run in the default activation group, I am a little puzzled. When you get your error, you might try displaying the job using the dspjob command or, if it is interactive, system request 3. Check out options 16 and 18 first. Determine what your comit definition is and the number of activation groups in the job. If you see any named activation groups without *DFTACTGRP, display the job's stack, option 11 and look for programs not running in the default activation group. To solve you problem, you may want to change the scoping of your commitment control. When you start commitment control, one option is whether it is scoped to activation groups or the job. In your case, scoping to the job should prevent activation group related errors. I would try to understand what is happening though. David Morris

[Guest.Visitor]

HTH: Trigger buffer content From To Type Field description 1 10 Char(10) Physical file name 11 20 Char(10) Physical file library name 21 30 Char(10) Physical file member name 31 31 Char(1) Trigger event ?1?=Insert, ?2?=Delete, ?3?=Update 32 32 Char(1) Trigger time ?1?=After, ?2?=Before 33 33 Char(1) Commit lock level ?0?=*None, ?1?=*Chg, ?2?=*CS, ?3?=*All 34 36 Char(3) Reserved 37 40 Integer(10) CCSID of data 41 48 Char(8) Reserved 49 52 Integer(10) Original record offset 53 56 Integer(10) Original record length 57 60 Integer(10) Original record null byte map offset 61 64 Integer(10) Original record null byte map length 65 68 Integer(10) New record offset 69 72 Integer(10) New record length 73 76 Integer(10) New record null byte map offset 77 80 Integer(10) New record null byte map length 81 96 Char(16) Reserved 97 * Char(*) Original record * * Char(*) Original record null byte map

[Guest.Visitor]

If I understand you, you have a commit or rollback in a trigger program. I have never seen this in a trigger program, it is usually done in the application. Can you do a commit or rollback in a trigger? Why would you?