Output from SFPURGER

As SFPURGER runs, it writes progress messages to the console. The most important of these are sent to the sysop user ID (see SFPURGER for the definition of this user ID). To keep a record of the processing, SFPURGER creates three output files. Each output file takes its file name from the CONTROL file that produced it. The file type is either LOGyynnn, RUNyynnn, or TSTyynnn.

SFPURGER LOGyynnn

The console log file for the run that occurred on Julian date yynnn. The LOG file contains a record of activities that occurred during the run.

SFPURGER RUNyynnn

The file that relates SFPURGER actions to the individual spool files processed during the run that occurred on Julian date yynnn. The RUN file identifies each spool file by file name, file type, and spool file number (spoolid). A RUN file can result only from invoking SFPURGER in RUN, FORCE, or SOS mode.

SFPURGER TSTyynnn

The file that results from invoking SFPURGER in TEST or TESTSOS mode contains the same kind of information as the RUN file. In other words, a TST file is simply a RUN file produced in a test mode, and then renamed.

Additionally, a no-run console log, SFPURGER NORyynnn, will appear instead of SFPURGER LOGyynnn if SFPURGER fails in RUN mode. To get this log, the failure must result from SFPURGER being invoked during prime shift, or twice in one day.

When you run SFPURGER, you will always get a LOG or NOR output file. Getting a RUN or TST file will depend on the success of your SFPURGER execution. If it completes successfully, you will get a RUN or TST file with your LOG file.