*RMC12001 - 08/10/2006 - The Batch Queue Reorganization has been sig- * nificantly restructured to replace the browse * of the PCR file for each report with the use * of the ROPERPI index file. This will reduce * the I/O of the job by at least 90%. We also * added a new command, $WTOMSG, to allow the * program to issue WTO messages for all signif- * icant events and errors. * *Problem Summary: * The old design of the batch reorganization program caused it to * browse the entire ROPEPCR file to determine which printers had * the report being processed assigned to it. This results in very * heavy file activity (#reports x #printers), and in systems with * many reports, printers or both, the batch reorganization execution * time can be substantial. The ROPERPI (Report to Printer Index) * file was created to alleviate this problem and did so for those * online processes (mainly R#WU and R#OR) that could benefit from * it but this was not done for the batch reorganization program. * *Symptoms: * The Batch Reorganization runs for a long time and does very many * I/O operations to the ROPEPCR file. * *Temporary Fix: * The following replacement object modules must be obtained from * technical support: * ROPEBQOR * The following replacement source modules must be obtained from * technical support: * RUNBQOR * *Documentation Changes: * The ROPES RPI data set must now be defined to the job stream. * DD statement //ROPERPI DD DISP=SHR,DSN=ROPES.RPIFILE.BASE is now * required. * * A new control card has been added. The operation is specified * in column 1 and is coded $WTOMSG. If present, then certain * critical messages will be written to the operator as well as * to the job's SYSOUT. * * Additional forms of the diagnostic messages will be presented * naming the ROPERPI data set if it cannot be opened, or if I/O * errors occur when processing the file. * *Permanent Fix: * This problem will be corrected by PTF in the next release of * ROPES. * *End Of Document