Summary
JRPL files are temporary files used by Syniti Replicate when running on IBM i systems. Each time Syniti Replicate runs a mirroring replication, these JRPL files are deleted and recreated.
If a file is locked, Syniti Replicate cannot delete it, and the file must be deleted manually.
Situations such as the following may cause JRPL files to remain locked:
The IBM i system is busy and a timeout error occurs.
The IBM i system experiences an abrupt shutdown.
When this happens, you may see the following error message in the Syniti Replicate log indicating that a JRPL file is locked.
System.Data.Sql400.Sql400Exception: ODBS Execute Error: Error occurred while opening file JRPL0353. [SQLCODE: -443 SQLSTATE: 38501]
at System.Data.Sql400.Sql400Command.ExecuteNonQuery()
at nn.b()
at iu.a(p5 A_0, Boolean A_1)
at iu.a(Boolean& A_0)
at iu.a(p5 A_0, Boolean& A_1)
at si.e()
or “JRPLXXXX in library DBMOTOLIB in use.”Solution
The JRPL files should be deleted from the IBM i system using the IBM i console. Before doing so, stop the Syniti Replication Agent service and ensure that only one instance of Syniti Replicate is running. You will not lose any transaction information by deleting the JRPL files, because the Replication Agent (Data Replicator) always starts from the last processed transaction, and the files are deleted and recreated for each mirroring event.
If the files are locked due to a timeout error, you should also use the Management Center to edit the connection properties of the IBM i connection. Increase the Init timeout value for the connection and ensure that the Command timeout is set to -1.