Are you saying that if you do a WRKMSGD CPF32C6 you get no hits on your
development box?
CPC* messages are normally completion messages and cannot be monitored for
with MONMSG. Repeat "normally".
Prompt on RMVPFTRG. Move to top (on the title line for example). Press
F1. Scroll down to "Error messages for RMVPFTRG". What do you have on
your development box? On my 6.1 box I have CPF32C6.
You may be right...
http://forums.systeminetwork.com/isnetforums/showthread.php?t=26047
Change your product to only support releases currently supported by IBM
and your problem is solved.
Or, change your monmsg to include both.
See also the 5.1 Memo to Users
2m.ii) ADDPFTRG and RMVPFTRG commands
A new escape message (CPF32C6) is sent if errors are found on the Add
Physical File Trigger (ADDPFTRG) command or the Remove Physical File
Trigger (RMVPFTRG) command. This message is sent instead of CPC3204 and
CPC3206, which were previously sent for ADDPFTRG and RMVPFTRG,
respectively.
Prior to V5R1, the ADDPFTRG command required that you have *READ
authority to the referenced physical file (FILE parameter). In V5R1, you
must have *READ and *OBJOPR authorities to the physical file.
Prior to V5R1, the ADDPFTRG command required that you have *ADD, *DLT,
or *UPD authority to the physical file, depending on the value you
specified for the Trigger event (TRGEVENT) parameter. In V5R1, if
ALWREPCHG(*YES) is specified, you need *UPD and *OBJOPR authorities to
the file.
Rob Berendt
midrange.com
