These statuses are important only when the spooled file is in a queue attached to an active writer. Then, the splfile in RDY would start printing when it's turn came. SAV would indicate it had already printed, and HLD would mean that the splfile wouldn't print automatically but had to be released to be printed. If you don't want all 5000 pages of a GL to print, the producing program should generate the splfile on hold, the the GL user can print only what they need or print it when they are satisfied that it is complete or correct. Splfiles have a generation option of whether to be saved or not after printing. If you want to be able to reprint a file without regenerating it, then it should generate with SAV *YES. Then it can be release and reprinted easily. ////////////////////////////////////// Good answer. Spool files are sometimes hld or set to Sav(*yes) so some post creation process can be run. So they can be e-mailed, copied to a remote system, captured by viewing software, or just saved. Phil

These statuses are important only when the spooled file is in a queue attached to an active writer. Then, the splfile in RDY would start printing when it's turn came. SAV would indicate it had already printed, and HLD would mean that the splfile wouldn't print automatically but had to be released to be printed. If you don't want all 5000 pages of a GL to print, the producing program should generate the splfile on hold, the the GL user can print only what they need or print it when they are satisfied that it is complete or correct. Splfiles have a generation option of whether to be saved or not after printing. If you want to be able to reprint a file without regenerating it, then it should generate with SAV *YES. Then it can be release and reprinted easily. ////////////////////////////////////// Good answer. Spool files are sometimes hld or set to Sav(*yes) so some post creation process can be run. So they can be e-mailed, copied to a remote system, captured by viewing software, or just saved. Phil