When a program issues WRITE PRINTER (#PRINT) a RHDCREPTxxxxnnn Queue is created and goes away when the report gets written to the printer it was sent to.
DCMT D REPORTS should show any queued reports
If such queues are amassing and not going away, most likely you have applications writing to one or more printers that were offline for some reason. Resolve the printer problem and the queued reports will print and the queues will be deleted.
Example: If I set my printer class to 1, which in my CV is not a class associated with any actual printer, the reports sent there will simply queue up.
In my test I did 4 WRITE PRINTER requests while set to this Print class.
DCMT D REP CL/DEST REPORTS LINES 01 00004 0003120
this shows 4 reports queued in Class 1.
DCMT D CLASS 1 ON REPORT ORIGINAL PROGRAM RPT RPT NUM NUM PRINTER NAME LTERM-ID NAME PRI ID LINES COPIES USER HLQJ1 LTVTM001 IDMSDDDC 010 001 00780 001 BCB HLQJ2 LTVTM001 IDMSDDDC 010 001 00780 001 BCB HLQJ3 LTVTM001 IDMSDDDC 010 001 00780 001 BCB HLQJ4 LTVTM001 IDMSDDDC 010 001 00780 001 BCB The above display shows my 4 queued reports
QUED task shows those 4 queued reports With RHDCREPT followed by the report names you see in the above display
IDMS DC256002 V1900 T84 *** QUEUE STATUS IN DDLDCRUN *** IDMS DC256003 V1900 T84 QUEUE NAME INV TASK RECORDS CREATE RET EXP ACTION IDMS DC256004 V1900 T84 RHDCREPTHLQJ1 0000051 19.112 001 001 KEPT L IDMS DC256004 V1900 T84 RHDCREPTHLQJ2 0000051 19.112 001 001 KEPT L IDMS DC256004 V1900 T84 RHDCREPTHLQJ3 0000051 19.112 001 001 KEPT L IDMS DC256004 V1900 T84 RHDCREPTHLQJ4 0000051 19.112 001 001 KEPT L