I have some challenges when stopping the DB2 DDF function. It is expected for the DDF to stop immediately. However, lately I have had persistent threads that prevented this process to complete for upto 30 mins.
Are there any suggestions on how best to handle this process?
=DB2P- STOP DDF MODE(FORCE)
No checking done here
Then we start the DDF with the following command
No Checking done here
I sometimes see
DSNL024I =DB2P - DDF IS ALREADY IN THE PROCESS OF STOPPING
Not currently monitored for. This will be added to OPSMVS Msg rules
Then when the DDF Display is done with DETAILS it shows
DSNL080I =DB2P- DSNLTDDF DISPLAY DDF REPORT FOLLOWS:
DSNL082I LOCATION LUNAME GENERICLU
Other than putting in a lot of code and checks and double checks, any easier way to handle this type of issue?
I am planning to implement R13.5 with SSM3 in the near future. Anything in there I can use?