I am attempting to run a PXX report against one of our production MUFs, where the start-up option for this MUF is set to PXXSTATS=DETAIL. The report runs and the output is simply:
PXX END, PXX NOT CLOSED (MUF STILL ENABLED OR PXX WAS FULL AT EOJ)
Does this mean that there is no information in the PXX report, or that there is no PXX data to report?
However, I run the same report against the test equivalent of this production MUF and obtain a full report. The test version of this MUF also has the PXXSTATS=DETAIL start-up option.
This production MUF is part of a Primary/Shadow MUF configuration in which the PXX is shared. Why I am not getting any output?
If you are sharing a physical PXX dataset, then results would be unpredictable due to having two MUF instances (Primary and Shadow MUFs) opening the same file. There is no way to determine what is being written to the PXX as two MUF instances are using the same Physical PXX dataset.
We strongly suggest move to the MUF Startup Option SYSOUT for all the PXX output, and to eliminate the PXX file by using this in the MUF proc: EXEC PGM=DBMUFPR,PARM='PGMDT=20161031,NO_PXX'
If you want to use a physical PXX file, you will need a separate file for the primary MUF and for the Shadow MUF.
User Connectivity section inside Shadow MUF Environment.