During GVEXPORT processing we receive the following error messages: GV104 OPEN FOR OUTPUT GV108 RECORD COUNTS DISAGREE CATALOG =nn. How do we fix?

Document ID : KB000031663
Last Modified Date : 04/03/2018
Show Technical Document Details
Introduction:
GV108 messages with a return code other than 0 during export processing.
Question:

 

We have a lot of message GV108 when we use GVEXPORT (KSDS INDEX) after a /DBR of the index                                            

GV104  OPEN FOR OUTPUT                                               

GV108 RECORD COUNTS DISAGREE CATALOG =81        (sample value)                     

the GVEXPORT file can be recovered without problem ??                

 

Solution:

The GV108 message is an informational message that can cause a unwanted return code.                                                                 

The message is advising that the record count taken by Faver at the time of the EXPORT was different than the catalog information.                       

This is normal if you are using EXO, the KSDS has not been closed via a IDCAMS VERIFY, or the file was being updated while the EXPORT was in progress CA recommends that you do NOT USE EXO during EXPORT. Of course, this will mean Faver will want exclusive use of the KSDS. This might not be possible in an active environment.                                                    

If the return code is the issue, and you are positive the the file has no errors, CA can provide you a "special PTF" that allows you to change the return code from the GV108 message. This is very common for some environments.

You can only obtain the "special PTF" from CA support. Please open a case via support online or call the support center for assistance.         

Answer:

The GV108 message is an informational message that can cause a unwanted return code.                                                                 

The message is advising that the record count taken by Faver at the time of the EXPORT was different than the catalog information.                       

This is normal if you are using EXO, the KSDS has not been closed via a IDCAMS VERIFY, or the file was being updated while the EXPORT was in progress CA recommends that you do NOT USE EXO during EXPORT. Of course, this will mean Faver will want exclusive use of the KSDS. This might not be possible in an active environment.