Hello CA SMF DIRECTOR Boarders:
Looking for others' input here on how an SMF DIRECTOR EXTRACT treats a CAF3103W (NO DATA SELECTED - a "warning" type message) condition as a COND CODE 0004, where there are also other instances where a COND CODE 0004 occurs, mostly when CAF2417W (....AN OVERLAP IN INDEX...) can and does occur occasionally, even though we have specified the max-value of OVERLAP(300).
Currently, a circumvention is used (at this site) by having a 'dummy' DFSORT job-step that detects an empty file and generates an ABEND -- more accurately raising the "NO DATA" condition. Unfortunately, this alternative has to be explained.
From experience with running SMF DIRECTOR EXTRACT production-job requests, the CAF3103_ condition should more likely be treated as an ERROR, not a WARNING, while percolating a higher COND CODE at job-step end.
Any other sites / admins out there have this same challenge with interpreting a COND CODE 0004, when it is more about being an ERROR not a WARNING (CAF3103E and maybe a COND CODE 0008, instead)?
Looking for feedback and hopefully ammunition to help sway CA Support to change CAF3103_ to "E" or (less desired) provide a means to suppress the COND CODE 0004 for CAF2417W conditions which are mostly normal and can/do occur.
Regards,
Scott Barry
SBBWorks, Inc.