CLAYTON@xrt.upenn.EDU ("Paul D. Clayton") (07/08/87)
Question From TSO Financial... I have an on-going problem with the VMS JBSYSQUE.DAT file that the job controller uses to hold records for batch and print files that need processing or have completed. The documentation suggests that a new version of the file be created on a regular monthly basis to improve the responsiveness and performance of the overall system. The side effect of this is that any jobs in the existing file are lost the job controller unless they are re-submitted and thereby placed in the new version of the file. This is the catch. I do NOT have ANY time during the tiime when the systems are up to create a new version of the file, which would there are no jobs waiting in either the batch or print queues. Typically I have around 40 jobs waiting for execution in the batch queues and around a dozen print jobs hung because some of the 40+ LN03's have run out of paper. I DO NOT want to have these jobs lost when a new file is created, and I am not looking forward to typing in the PRINT or SUBMIT commands manually to get them back into the system. The result is I have not created a new file in over a year and half and the file has grown to over 4.5K blocks. The performance is LOUSY!! The QUESTION is, does anyone have a program that will perform $GETQUI requests of both batch and print, create an intermediate file/record of outstanding jobs then perform $SNDJBC requests to put these jobs back into the system based on the information that is in the intermediate file/record?? If anyone has a partial solution, I am also interested. Paul D. Clayton - Manager Of Systems TSO Financial - Horsham, Pa. USA Ma Bell - 215/ 657-4000 Net Address - CLAYTON%XRT@CIS.UPENN.EDU