HDRCTL parameter: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
RPuszewski (talk | contribs) No edit summary |
||
Line 30: | Line 30: | ||
<tr><th align="right"><var>4</var></th> | <tr><th align="right"><var>4</var></th> | ||
<td>Pause at the end of an output page.</td></tr> | <td>Pause at the end of an output page.</td></tr> | ||
<tr><th align="right"><var>8</var></th> | |||
<td>Daemon threads must honor headers.</td></tr> | |||
</table> | </table> | ||
<p> | <p> |
Revision as of 16:59, 16 January 2024
Header control
Summary
- Default value
- 0
- Parameter type
- User
- Where set
- By any user
- Related products
- All
- Introduced
- Model 204 V2.2 or earlier
Description
The formatting of page headers
Valid settings of HDRCTL are (options can be summed):
Setting | Meaning |
---|---|
1 | Suppress header 0 (system header with date, time, page number). |
2 | Suppress the blank line that normally follows header 0 for non-request output. |
4 | Pause at the end of an output page. |
8 | Daemon threads must honor headers. |
Setting 4 of HDRCTL is valid only for the following device types:
IODEV | Access method/device type |
---|---|
29 | Remote User Language thread (line-at-a-time). |
37 | SNA Communications Server (formerly VTAM) 3767 and NTO - An additional line is added to each page, in addition to OUTLPP plus PGSEP, to receive a reply.
Note: The |
39 | IUCV User Language thread (line-at-a-time). |
45 | CMS console (line-at-a-time). |
Note: Use of HDRCTL 4 on Batch2 threads results in a pause being sent to BATCH2 which then responds by sending an attention back to Model 204 because a BATCH2 has no way of pausing (it is not an interactive device). An attention will usually cause an evaluating request to be terminated.