![[Library]](/bookmgr/libicon2.gif)
![[Contents]](/bookmgr/contents.gif)
![[Revisions]](/bookmgr/revs.gif)
![[Prev Topic]](/bookmgr/prev.gif)
![[Next Topic]](/bookmgr/next.gif)
![[Search]](/bookmgr/search.gif)
![[Search Results]](/bookmgr/dslist.gif)
![[Prev Topic Match]](/bookmgr/dsprev.gif)
![[Next Topic Match]](/bookmgr/dsnext.gif)
![[Notes]](/bookmgr/dnotes.gif)
![[List Notes]](/bookmgr/dlnotes.gif)
![[Print]](/bookmgr/print.gif)
![[Download]](/bookmgr/download.gif)
![[Help]](/bookmgr/help.gif)
3.4.2 Output Handling
Output produced by a background job differs from output in the foreground
in the following ways:
- Messages producing multiple levels are printed in their entirety. (It
is the same as entering a question mark (?) and recovering all levels
in the foreground.)
- The allocation of an output data set to the terminal causes that
output to be printed after all other output.
If it is necessary to see the output at your terminal rather than waiting
to have it printed on the system printer, one of two things can be done:
- Place the output in a data set
- Have the output held and use the OUTPUT command to look at it
For the appropriate JCL, see "Writing JCL for Command Execution" in
topic 3.4.4.1.
© Copyright IBM Corp. 1988, 2000
Return to library:
[
OS/390 |
TPF |
VM |
VSE |
IBM Hardware |
S/390 Redbooks |
RS/6000 SP
]
Glossary - IBM Dictionary of Computing
How to:
[
Order publications |
Contact OS/390
]