How can DUAL LOGGING be avoided with Batch Backout executions when being invoked by PRM.

Products

• CA Distributed Database Management
• CA Database Analyzer for DB2 for Oracle
• Database Analyzer (IMS Tools)
• Mainframe Configuration Manager for IMS for z/OS
• IMS TOOLS - MISC
• Compress Data Compression (IMS Tools)
• Database Analyzer for IMS for z/OS
• Database Copier for IMS for z/OS
• Database Organizer for IMS for z/OS
• Mainframe Extended Terminal Manager (IMS Tools)
• High Performance Recovery for IMS for z/OS
• Database Organizer (IMS Tools)
• Mainframe Program Restart Manager for IMS for z/OS
• Secondary Index Builder for IMS for z/OS
• Secondary Index for IMS for z/OS

Issue/Introduction

Issue:

If an application program abends and Batch Backout needs to be invoked by PRM to remove updates which occurred after the last checkpoint, DUAL LOGGING will be done by default for the log records written by Batch Backout. This is even true when the application program execution itself is only using SINGLE LOGGING.

Resolution:

To avoid DUAL LOGGING being used with Batch Backout invoked by PRM, add the PRM run option "IEFRDER2=DUMMY" to the application program execution.
This forces SINGLE LOGGING being used with Batch Backout (instead of using DUAL LOGGING by default).

Environment

Release:
Component: PRM