Prior to Version 5 Release 1, the database manager accepted isolation level uncommitted read as a preprocessor parameter, but internally the isolation level was escalated. As of Version 5 Release 1, isolation level uncommitted read is fully supported. However, this isolation level to take effect, packages that were prepped with uncommitted read in a previous release must be explicitly repreprocessed after migration.
As of Version 5 Release 1, installation and service of the database manager code is done using VMSES/E, which is a component of the VM operating system. Several administrative and maintenance processes have changed as a result, including:
Any user exits (date, time, or accounting), field procedures, or applications that run in single user mode that are dependent on running in a 370 mode virtual machine must be converted to execute in an ESA mode virtual machine. AMODE 24 is still supported, however it cannot be used if the database is started with SYNCPNT=Y. If the database is started with SYNCPNT=Y (which is possible only in multiple user mode), exits and field procedures must run with AMODE 31. If the database is started with SYNCPNT=N, exits, field procedures, and single user mode applications that require AMODE 24 can be used.
The text of several messages was modified as the result of the renaming of the product. Applications with dependencies on the text of messages may be affected.
The User Facility Subset is no longer supported; machines on which the subset was previously installed must now contain the full product.