We recently upgraded to a new machine at OS Level V5R4 CUM 8305. Our old machine was also at V5R4 but the CUM level was only 8057. Ever since the upgrade, I have been having SQL Problems. My latest problem involves trying to update a QTEMP File that was built using CRTPF and specifying a record length. When my CLLE tries to update the temporary file, the system issues a message indicating the file is journaled and therefore the update action is invalid. I have commitment control set to *NONE on the RUNSQLSTM. To correct the issue I added a SET Statement to the SQL Source Member. (SET TRANSACTION ISOLATION LEVEL NO COMMIT) This also caused the CLLE to abort with a message indicating the Commit level was not at a break point.
I have been surfing the net in search of an answer, but have had no luck. Any suggestions or ideas would be greatly appreciated.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!