Symptoms:
- XCMONHST50 job temporary storage consumption can creep up to high numbers over time.
- User may see no data in the QM query reports targeted at XCMONHST archival data in insure/MONITOR.
- User may also see "Data mapping error" message repeated endlessly in the joblog of XCMONHST job.
- XCMONHST job may take a long time to terminate, with function *JOBLOG listed in the WRKACTJOB display
- Duplicate jobs may show up in the insure/MONITOR gui or in the XCMONHST file
- User may see LASTSQL field in XCMONHST file corrupted with other job's SQL statement text