We had a FAVER job fail this weekend with a RC4
GV105 EMPTY CLUSTER EXPORTING DEFINITION
GV111 CONDITION CODE SET TO 004
Is there something we need to do to fix this so the job doesn't fail? Or is there a check we can place in the job so the job doesn't get marked failed if this is an acceptable error?
Release : 4.5
The message:
GV105 EMPTY CLUSTER EXPORTING DEFINITION
Is explaining that the particular cluster happens to be empty and the definition would be exported anyway. The RC is automatically set to 4 so you are aware. The job did not fail in any way.
At the end of the export job you saw this message:
28 OBJECTS SUCCESSFULLY PROCESSED --->> tells us that 28 clusters were exported
0 UNSUCCESSFUL --->> nothing failed
CONDITION CODE PAGE NUMBER
-------------- -----------
004 127 -->> condition code is 4
004 379
There is nothing wrong with the export process.
Recommend that you review the RC4 as a potential pass and allow subsequent jobs to continue in your scheduling package. In this case Faver is working exactly as designed.