KB Article #179857
new DIAGC value set in error procedure is not sent to SENTINEL
Problem
EXECSE script issue the command: "cftutil halt part=&PART,idtu=&IDTU,diagc=My New DiagC"
EXECSE is correctly executed on error and the new DIAGC value is printed in cft logs
The new value is not present in the Sentinel's XFBTransfer table
Resolution
The sentinel notification for the failed transfer is sent at error detection, then, and only then, the error procedure is changing the CFT DIAGC to a new string.
The procedure may need to issue a WLOG with the new DIAGC and if log messages are tracked, it can then be treated on Sentinel side.
It will make use of the xfblog instead of the xfbtransfer.