Spool file

From MidrangeWiki
Revision as of 19:32, 27 June 2005 by Al Mac (talk | contribs)
Jump to: navigation, search

Output from programs on the 400 often go to a report stored in a spool file. When we make changes to where the report is "located" we are not moving it on disk, but changing its name headers wich are the basis of how lists of reports show up on vartious displays.

WRKSPLF

If you key this, and press enter, you get a list of all reports that you have created.

If you know some co-worker name, keying WRKSPLF then their name, will call up list of their reports.

WRKSPLF then F4 - top line some user name - second line some OUTQ = gives you list of just that person reports in that particular OUTQ.

WRKOUTQ

If you key this, and press enter, you get a list of all the OUTQ that have been setup, that you may see in your Library List.

You can then view all the reports in a particuar Q, or do other actions against the contents.

If you know the name of some outq, keying WRKOUTQ then that name, gives you the list of what reports are there.

WRKWTR

List Writers (Printers) and check on their status and what reports are waiting to print.

F21

F21 on any of the printer command screens toggles between Basic / Intermediate levels of how the data is provided.

Overrides

Within CLP programs we can apply overrides at run time. For convenient reference here are some that are available in addition to spool file.

When we develop some program, it is setup to use a particular physical or logical file with the output to a report at a particular location, and use some display screen.

At execution time, there can be overrides.

  • OVRDBF Override Data Base File
    • same file but different member
    • same file but different logical
    • same file layout but different library's version of it
  • OVRDKTF Override Diskette File
  • OVRDSPF Override Display File
  • OVRPRTF Override Printer File
    • Save it after printing
    • Give it a meaningful label on spool list
    • Send it to CPYSRCF dump format
      • won't look pretty
    • OUTFMT get at *HEX packed format contetns
  • OVRTAPF Override Tape File

At the end of the CLP program we typically DLTOVR delete the overrides that were used by that program.

We can also DSPOVR Display Override.

Create Printer File

Output from a program typically can go to a printer file. We can CRTPRTF create one with no structure, or we can compile one from DDS. After creating one, we can CHGPRTF change some characteristics over and above what a source file can do for us. We can copy some printer file that was created for some other program, then CHGPRTF the copy to meet the needs of why we made the copy.