Yes, there is a matching IM 2019 R3 as well. If you are producing PSR's that are used between PB & IM then A) You need to make sure that your have PB & IM 2019 R3 installed: A) on the developer's PC; B) IM2019R3 is required to be used when App EXE's are compiled from PB2019R3 and C) PB / IM 7.x PSR's should no longer be used with PB 2019 R3 App's or IM 2019 R3 users.
This seems like a simple task ... say read the PSR into a DW Control and then use the SaveAs() to write it back to disk. Unfortunately, the PSR contains the DWO source as well as data. So just reading the PSR will not change the DWO source - which is still in PB 7.x format.
The proper way forward would be to check each migrated DWO in PB2019R3 (edit source) PBL(s) that interact as a PSR and make sure that the "Release=" attribute is set to "19". That will complete the last piece of the DWO syntax source code migration ( TIP: You can write a small PB App utility to do that in an automated fashion). Then you need to rebuild the PSR's from the new properly migrated DWO source that now includes the migrated DWO source and data in PB2019R3 format.
If it a historical issue, I would just write a small PB App utility that reads the PB v7.x PSR into a DW Control and then have the utility save the result as a PDF using the SaveAs (PDF!) command.