18.08.2013 Views

LINC Programming Reference Manual - Public Support Login - Unisys

LINC Programming Reference Manual - Public Support Login - Unisys

LINC Programming Reference Manual - Public Support Login - Unisys

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PRINT.FRAME (PF)<br />

PRINT.FRAME (PF)<br />

The PRINT.FRAME; command executes the logic of the specified Report Frame (including<br />

any PRINT.FRAME; commands), and then the Frame is output for printing.<br />

The AS; command option indicates that you are printing this Report as a Shadow Report<br />

with a different title.<br />

The AT; command option directs that printing is to start at the line specified (counting from<br />

the top of the page). If headings have printed beyond this line, printing will commence<br />

from the next available line. If the specified line is less than the current line, the Frame is<br />

printed on the next page. If the line specified by the AT; command option is greater than<br />

GLB.FORMDEPTH, the Frame will be printed on a new page on a line calculated by<br />

subtracting the value of GLB.FORMDEPTH until an acceptable value is found.<br />

For example, suppose a Report requesting printing to start at line 53 is directed to Video.<br />

Since GLB.FORMDEPTH is 48, one page is skipped (48 lines) and output starts at line 5.<br />

At the time of the first PRINT.FRAME; to the print file (or a shadow print file) in ROC and<br />

non-ROC Reports, the current value of GLB.STN is captured. On subsequent<br />

PRINT.FRAME; commands to the same print file, the associated captured GLB.STN value<br />

is compared with the then current GLB.STN. If they are different, a RELEASE; command is<br />

invoked before performing the requested print. Similar logic applies for GLB.DEVICE and<br />

GLB.PRINTHOST in ROC Reports.<br />

Multiple blank pages are not printed if the <strong>LINC</strong> System is using the Report Output Control<br />

System (ROC) for video output (device type of VD).<br />

Notes:<br />

$ In an MCP based <strong>LINC</strong> System that does not use ROC, a Frame that contains only<br />

logic may print a blank line when accessed by the PRINT.FRAME; command.<br />

Use an END.NO.PRINT; command to prevent a blank line from being printed.<br />

In ROC Reports, a blank line is not printed in this case.<br />

$ ROC files are created with the usercode of the parent <strong>LINC</strong> System when the value of<br />

GLB.USER is spaces. ROC text files for UNIX <strong>LINC</strong> Systems are created with the<br />

usercode of the initiator of the Report when GLB.USER is spaces, with read/write<br />

access for all.<br />

$ System Data items associated with Report or Shadow Report output should not be<br />

used if there is no associated PRINT.FRAME; command, as COBOL syntax errors<br />

would result.<br />

$ The values of GLB.STN, GLB.DEVICE, and GLB.PRINTHOST are only relevant at the<br />

time of the actual printing of the Frame. Their values may change any number of<br />

times between PRINT.FRAME; commands, without affecting the printing of the<br />

Report.<br />

1-196 v

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!