HP 3000 Manuals HP 3000 Manuals
Chapter 5 Permanent Disk Files and Account Management Permanent Disk Files Types of spool files With the native mode spooler (NMS), the file system creates spool files as ordinary disk files. The NMS maintains three kinds of permanent disk files. These include: * input spool files (They are always linked.) * output spool files * checkpoint files
NOTE Checkpoint files are not spool files.
When the spooling subsystem creates these files, they are automatically put into the reserved account HPSPOOL. Input spool files and output spool files are linked to the spooling subsystem; however, if you are the creating user, you may access these files as if they were in your own group and account. Three new file codes designate the files as input spool files, output spool files, and checkpoint files. They are: 1515 input spool files 1516 output spool files 1517 checkpoint files Input spool files. Input spool files are created in the following ways: * By entering a job with the STREAM command or through a spooled input device (tape drive). The streamed or input spooled job is copied to an input spool file, and a job is scheduled. When the job logs on, the spool file becomes the job's input ($STDIN). See the JOB command in the MPE/iX Commands Reference Manual Volumes 1 and 2 (32650-90003 and 32650-90364) for more information. * By entering data from a spooled input device or by streaming a file with a DATA command in it. The results are placed into an input spool file and can be accessed by the user.account specified in the DATA command. See the DATA command in the MPE/iX Commands Reference Manual Volumes 1 and 2 (32650-90003 and 32650-90364) for more information. The system creates input spool files in the IN group of the reserved account HPSPOOL. These files remain in IN.HPSPOOL until a job or process uses them or you delete them by using the following: * ABORTJOB for a job's $STDIN spool file. * SPOOLF with the DELETE parameter for input spool files created with the DATA command. * A START NORECOVERY system startup deletes all JOB and DATA input spool files. Input spool file names have the format Innnn.IN.HPSPOOL where nnnn is a number. For example, I235.IN.HPSPOOL is an input spool file. Because input spool files are always linked to the spooling subsystem, IN.HPSPOOL is the only place in the system containing input spool files.
NOTE Job input spool files have a one-to-one correspondence with job master table (JMAT) entries. The JMAT is rebuilt for updates and START NORECOVERY. Whenever an update or START NORECOVERY occurs, the system purges all input spool files. Input spool files are only recovered during a START RECOVERY startup because the JMAT is only recovered at that time.
Output spool files. Output spool files normally reside in the OUT group of the HPSPOOL account and, unless you explicitly delete them, remain there until they print. You may use the ;SPSAVE parameter with the FILE, JOB, and SPOOLF...;ALTER commands to leave your spool file in OUT.HPSPOOL after all copies of the file print. Then you may copy the saved spool file into your own group and account so that you do not have to run the generating application again. If you use the SPSAVE parameter, the output spool file remains in OUT.HPSPOOL until you delete it. You may not use the ;SPSAVE parameter to save a private output spool file. Output spool file names have the format Onnnn.OUT.HPSPOOL where nnnn is a number. For example, O46.OUT.HPSPOOL is an output spool file. The OUT.HPSPOOL group contains only linked output spool files. If you copy an output spool file from OUT.HPSPOOL to your account, the copy is not linked into the spooling subsystem. If you issue the SPOOLF command with the parameters PRINT and DEV on the copy, another copy is made in OUT.HPSPOOL and this copy is linked. You can also create unlinked output spool files by using the BUILD or FILE commands with the ;SPOOL parameter or with the HPFOPEN intrinsic. Checkpoint files. Checkpoint files are companions to output spool files. A checkpoint file helps a spooler recover from device problems such as power failure and paper jams. It also helps a suspended spooler resume producing output. There is one checkpoint file per output spool file for each device that prints the spool file. The output spooler process creates the checkpoint file the first time that the process produces output for the companion output spool file. The checkpoint file is automatically deleted when you or the spooler delete the output spool file from the HPSPOOL account or after a spool file that is saved with the ;SPSAVE parameter has its last copy printed. Checkpoint files are placed in device name groups in the HPSPOOL account. For example, suppose LP1 is a device name, and the NMS creates the output spool file O1234.OUT.HPSPOOL that is printed by device LP1. Then the name of the companion checkpoint file is C1234.LP1.HPSPOOL. For another example, suppose that the device name consists of the eight digits 00000018 (indicating that the system manager did not explicitly configure a device name using SYSGEN). NMS creates the output spool file O26.OUT.HPSPOOL. When device 00000018 prints O26.OUT.HPSPOOL, the name of the companion checkpoint file is C26.D0000018.HPSPOOL (The D replaces the first 0 in the device name 00000018). Refer to "Account Management," in this chapter, for more information about naming checkpoint files.
NOTE The checkpoint file is created at the time an output spooler begins to print an output spool file, not before.
Private and nonprivate spool files You may choose to make an output file private (the default is nonprivate). All input spool files are automatically created private. Private output spool files are used for greater data security. Private spool files. Private output spool files differ from regular nonprivate spool files in the following ways: * Since they are level 2 privileged files, you may access them only by processes that call HPFOPEN while running at level 2 privileged mode. This means that the MPE/iX commands PURGE and PRINT fail. Level 3 programs such as FCOPY or your favorite editor and the FOPEN intrinsic can not open a private file. * You may not save a private file by using the ;SPSAVE option with the SPOOLF...;ALTER command. * Even if you have SM capability, you cannot store a private file. * If you have SM capability, you may use the PRINTSPF utility to print private spool files. * You may not copy, browse, or open the private output spool file as a disk file. This is also true of input spool files. * You may not alter the number of copies. * Unless you have SM capability, you may not alter the target device. * The only other control that you have over a private output spool file is to alter its priority, to defer or not defer it, or to delete it completely. You must have access to the spool file--according to the guidelines for nonprivate spool files--for this control. Nonprivate spool files. You may access nonprivate spool files according to the following guidelines: * If you have SM or OP capability--or you are logged on at the system console--you may access any nonprivate spool files. This means that you can read, delete, or alter a spool file using either the NMS commands and intrinsics or standard MPE/iX commands and intrinsics. * If you have AM capability, you may similarly access any spool file whose creating user is in your account. * If you are the creating user, you may access spool files that you create. If you have read access to nonprivate spool files, you may store and restore them with the STORE and RESTORE commands, respectively. If you have write access, you may purge nonprivate spool files using STORE with the ;PURGE option.