Message : CPD5034
File position is undefined following a rollback operation.
Message Long Text :
Cause . . . . . : A rollback operation was performed for member &1 file &2 in library &3. Because this file was opened for SEQONLY(*YES) processing, the system has left this file at an undefined position. Recovery . . . : The application will need to reestablish the file's position before making a read request that requires the file to have a valid position. For example, a Read Same requires that the file has a valid position at some record before being able to return that same record. Alternatively, the user can issue an Override Database File (OVRDBF) command and specify SEQONLY(*NO). By doing this, the application may experience slower performance, but the file will be positioned to the record at which it was positioned on the most recent transaction boundary. In this case, the application will not need to explicitly reestablish the file's position.