Also when running batch DQBATCH jobs, the steps reading these tables got the following message "URT - ERROR "72" ON FT OPEN"
We did complete the Datacom Encryption process on another table within the same dbid earlier that day, but the database reopened fine afterwards. It was the batch jobs later that night that failed. We had to init and reload the tables to be able to reopen them, just concerned that encryption means we need to init before every reload or what is going on here.
z/OS CA Datacom 15.1
The Datacom Data area getting the RC 72(082) error was last INITed with an old Datacom version, version 10.0. The specific defect here is that encryption is in the base but not the area and that is wrong and the area has been seen as encrypted in error. You will only see this with areas that were last INITed with an older Datacom version, like version 10.0. So not with more recent versions like version 12.0 and 14.0.
Problem solved after running DBUTLTY INIT/LOAD (BACKUP was available).
If you want to implement encryption then run BACKUP/INIT/LOAD on ALL areas in the database if you are unsure of the last INIT Datacom code that has been used. You can run DBUTLTY REPORT TYPE=H,DBID=nnnnn and check the date on function INIT to see when the last initialization was run.