1. Don't spool any more reports.<br />2. Print and/or flush some of the reports now on the Spool file.<br />3. Use the **SPLR CLEAR command to flush ALL spooled reports<br />** and release ALL SPL file records.<br />In order to do the last option the Spooler's status must be HALTED (on the **SPLR STATUS screen). To achieve this status enter:<br />**SPLR START<br />&nbsp;<br />Wait for status to change to RUNNING or SLEEPING, then Enter:<br />**SPLR HALT<br />&nbsp;<br />UNWANTED REPORTS ON FILE<br />In the event that there are reports on the SPL file, with proper RPH file headers, which are not wanted, enter:<br />RPHCHG rrr<br />&nbsp;<br />where:<br />rrr<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />= report number<br />Alter the Disposition to FLUSH. The Supervisor will discard this report on the next cycle and release all its SPL file records for use by other reports.<br />INVALID DATA ON FILES<br />In the event that there is invalid data noted on the RPH file or SPL file which cannot be properly processed by the Spooler then first enter:<br />**SPLR CLEAR<br />&nbsp;<br />Refer to SPOOL FILE FULL above for more instructions on using this command.<br />This should restore all the RPH file and SPL file records to "virgin" status; it also FLUSHes all reports which were on the files. If this does not correct the problem, then:<br />Restore the files from a recent "backup" or execute ALALDFIL with a control record to select only the SPL and RPH (cont.)<br />files. Executing ALALDFIL will initialize the files to a "virgin" status. Refer to ALALDFIL in the MAGEC "Offline (cont.)<br />Utilities" chapter for control card formats and JCL examples.<br />This situation should not occur, if it does that would be a strong indication that either:<br />1. The Spooler software is or has been flawed.<br />2. Someone else has "stepped on" the Spooler's files.<br />Call MAGEC Software's support line, if you are not able to correct the problem.<br />DEVICE HUNG IN BUSY STATUS<br />Occasionally you might find that a device (printer) is left in a status of BUSY (as per the DVCSEE screen), but that it (cont.)<br />is not actually printing a report. This might be because of a system crash, program abort while printing, or because (cont.)<br />the printer's status to CICS (or other TP monitor) was altered while it was printing. The MAGEC Spooler might not have (cont.)<br />sensed the error (especially if it occurred in between blocks of print data) and might have left the status of the (cont.)<br />printer as BUSY, though printing has actually ceased.<br />The first step in correcting this error situation is to issue the command:<br />**SPLR PAUSE/dddd<br />&nbsp;<br />where dddd is the device ID. If the printer is actually printing a report when the PAUSE command is issued, then the (cont.)<br />printing program (which is a part of the MAGEC Spooler system) will sense the PAUSE command and will cease printing and (cont.)<br />set the device status to PAUSED and set the report's status to HOLD. If the printer was not printing a report, then its (cont.)<br />status will still remain BUSY, but a "PAUSE PENDING" status will also be set for the device. The DVCSEE display would (cont.)<br />show both the BUSY status and the PAUSE PENDING message. In that case, you should next do:<br />DVCCHG dddd<br />&nbsp;<br />Then change the device status from BUSY to AVAILABLE (or another valid status). The report status, as shown on the RPHSEE screen, should be automatically altered to HOLD when you do this.<br /># <br />Printing on the System Line Printer<br />## <br />SPOOLPRT<br />A batch utility program is provided to allow spooled reports to be printed on the system line printer(s) which are (cont.)<br />usually located in the computer room. No special considerations need be made when spooling reports; in fact, the same (cont.)<br />report may be printed at an online hardcopy device and/or at the system line printer. A report may be spooled with a (cont.)<br />Disposition of KEEP and printed on one device then re-printed at another regardless of what type devices they (cont.)<br />are.<br />A special Location Code of SYS is reserved for the System Printers. The batch utility program scans the Spooler's files (cont.)<br />looking for reports routed to the Location of SYS which are READY to print. The name of the batch utility is (cont.)<br />SPOOLPRT.<br />Each execution of SPOOLPRT will find all the reports which are for Location SYS, are READY to print, and have (cont.)<br />Dispositions of KEEP or DELETE. All such reports are printed on the line printer and their Dispositions are altered (cont.)<br />according to the same rules as if they were printed to an online device.<br />If there are no reports to be printed then SPOOLPRT simply goes to end-of-job; therefore it is acceptable to execute SPOOLPRT whenever you suspect that there may be reports to be printed.<br />The DOS JCL to execute it is:<br />// JOB SPOOLPRT<br />// ASSGN SYS007,SYSLST<br />// EXEC SPOOLPRT<br />/*<br />/&<br />The OS JCL is:<br />//SPOOLPRT JOB acctg-data<br />//STEP1 EXEC PGM=SPOOLPRT<br />//SYS007 DD SYSOUT=*<br />//<br /># <br />Printing a Screen<br />## <br />The PRINTS Function<br />The Spooler includes a facility to allow you to "print" the contents of any MAGEC application's screen. The facility (cont.)<br />simply creates a "report" consisting of the screen image, including any data being displayed, and spools it by CALLing (cont.)<br />the Spool Subroutine just as your MMP's do. The screen image may be routed to any LOCATION, including SYS (which prints (cont.)<br />on the computer room line printer).<br />To print a screen you must first enter the appropriate function and key value to bring up the desired screen; then, on the top line of the screen (the Command Line) you enter:<br />PRINTS lll/c<br />&nbsp;<br />where:<br />lll<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />= LOCATION to route to<br />c<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />= a valid Print CLASS<br />The generated "report" will be routed to the LOCATION and CLASS you have specified. If you omit the "lll/c" then MAGEC (cont.)<br />will default to the LOCATION of the terminal you are at and the first (lowest) print CLASS specified on your terminal's (cont.)<br />DVC file definition. If your terminal is not defined on the DVC file then MAGEC will default to the LOCATION=SYS and (cont.)<br />CLASS=P for lack of anything better.<br />The values of SFUNCT and SKEY will be restored to what they were before you typed in the PRINTS command. If you (cont.)<br />overtype any screen data when you enter the PRINTS command then it will be printed as it appears on the screen, with (cont.)<br />your overtyped modifications.<br />After generating the spooled screen image report, MAGEC will place a message in the SCOMPL screen field on the top line of your screen to tell you the Report Number and routing generated.<br />Standard generated MMP's utilize exactly this function when you press the (PF13) hardcopy key from a "maintenance" (cont.)<br />screen (as opposed to the "browse" screens used by the LOC, SCN, and FND functions). The MMP's simply do a fetch to the (cont.)<br />PRINTS function (FTHFUNCT). You can accomplish the same results by typing in the PRINTS command at any (cont.)<br />time.<br /># <br />Auto-Start<br />## <br />Start-Up Options<br />The MAGEC Spooler includes an Automatic Startup feature which can be used to initiate the Supervisor's "polling" and to (cont.)<br />reset error conditions at the time that your TP Monitor is initiated. This eliminates the need to remember to manually (cont.)<br />START the Supervisor via the **SPLR screen whenever the Monitor is brought down and back up, whether by intent or as a (cont.)<br />result of a "crash".<br />The Auto Startup feature has four possible startup options:<br />WARM<br />**<br />Restart the supervisor and restart printing of reports which may have been interrupted by a "crash".<br />**<br />COLD<br />**<br />Restart the supervisor.<br />**<br />CLEAR<br />**<br />Flush any reports on file and restart the supervisor.<br />**<br />NONE<br />**<br />Do nothing.<br />The Auto Startup routine is invoked whenever the Monitor is initiated. The normal procedure should be to invoke the (cont.)<br />WARM option, the others are for exceptional cases. WARM-start has several variations controlled by other parameters you (cont.)<br />specify. It can "clean up" the SPL file and RPH file and dispose of erroneous reports to minimize the need for manual (cont.)<br />handling. It can also advise the console operator of situations which might indicate a problem, such as a report which (cont.)<br />was in process of spooling when the system "crashed", etc.<br />## <br />Setting Startup Options<br />The Startup options are stored on a special control record which is on the RPH file. A batch utility program is used to (cont.)<br />set the desired values into the control record. Some users insert an execution of this batch program into the Monitor (cont.)<br />startup deck so that they can alter the options at the time they initiate the Monitor, other users prefer to leave it (cont.)<br />as a separate stand-alone job. The program is named SPOOLOPT.<br />You can tell SPOOLOPT what options you wish set in either of two ways:<br />1. A control card in the jobstream.<br />&nbsp;<br />2. Via console prompts.<br />**<br />&nbsp;<br />If there is a control card present then SPOOLOPT will accept it and set the options accordingly and will not prompt the console operator. There are three parameters which are set:<br />1. Startup Option (Clear, Cold, Warm, None).<br />&nbsp;<br />2. Report Handling with errors (IGNORE, READY, FLUSH).<br />&nbsp;<br />3. Device Handling with errors (IGNORE, AVAILABLE, DISABLE).<br />&nbsp;<br />Items 2 and 3 apply only for the WARM startup option.<br />To execute SPOOLOPT in DOS:<br />// JOB SPOOLOPT<br />// ASSGN SYS006,SYSIPT<br />//&nbsp;DLBL&nbsp; RPHK1 ..... etc.<br />//&nbsp;DLBL&nbsp; SPLK1 ..... etc.<br />// ASSGN SYS007,SYSLST<br />// EXEC SPOOLOPT<br />- control card, if used<br />/*<br />/&<br />To execute SPOOLOPT in OS:<br />//SPOOLOPT JOB acctg-data<br />//STEP1 EXEC PGM=SPOOLOPT<br />//RPHK1&nbsp; DD&nbsp; DSN=MAGEC.RPH.CLUSTER.... etc.<br />//SPLK1&nbsp; DD&nbsp; DSN=MAGEC.SPL.CLUSTER.... etc<br />//SYS007 DD SYSOUT=*<br />//SYS006 DD *<br />- control card, if used<br />//<br />The control card format is:<br />Col. 01-09:<br />"SPOOLOPT"<br />Col. 10-19:<br />Startup option<br />CLEAR<br />Flushes all reports, then initiates the Supervisor.<br />COLD<br />Initiates the Supervisor polling without regard to errors.<br />WARM<br />Initiates the Supervisor, first scanning for errors and for reports which were being printed when the system was brought down.<br />NONE<br />Sets the Supervisor's Status to HALTED.<br />Col. 20-29:<br />Device-in-error handling option<br />IGNORE<br />It will ignore and bypass them.<br />READY<br />It will alter them to STATUS=READY, DISPOSITION=LEAVE.<br />FLUSH<br />It will flush them.<br />Col. 30-39:<br />Report-in-error handling option<br />IGNORE<br />It will ignore them.<br />AVAILABLE<br /><br />next: splr06.md.txt