USE command: To a sequential data set: Difference between revisions
Jump to navigation
Jump to search
m (pdf now converted to wiki) |
m (add "See also" section) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 11: | Line 11: | ||
</p> | </p> | ||
Where <var class | Where <var class="term">outputname</var> is in the form <code>OUT<i>xxxxx</i></code>, referring to the run's data definition statement in the z/OS or z/VSE JCL, or to the FILEDEF statement in the CMS EXEC. Output name can also be the name of a DEFINE DATASET definition. | ||
==Example== | ==Example== | ||
| Line 24: | Line 24: | ||
If you are using an external security interface, authorization to open sequential data sets is validated during execution of the command. For more information, refer to [[:Category:Security interfaces|Security interfaces]]. </p> | If you are using an external security interface, authorization to open sequential data sets is validated during execution of the command. For more information, refer to [[:Category:Security interfaces|Security interfaces]]. </p> | ||
[[Category: | ==See also== | ||
<ul> | |||
<li>[[USE command: Directing output]] </li> | |||
</ul> | |||
[[Category: User commands]] | |||
[[Category:Commands]] | [[Category:Commands]] | ||
Latest revision as of 21:14, 16 January 2018
Summary
- Privileges
- Any user
- Function
- Directs Model 204 output to a specified sequential data set rather than to the normal output device
Syntax
USE outputname
Where outputname is in the form OUTxxxxx, referring to the run's data definition statement in the z/OS or z/VSE JCL, or to the FILEDEF statement in the CMS EXEC. Output name can also be the name of a DEFINE DATASET definition.
Example
USE OUTPRINT USE OUT1
Usage notes
When output from Model 204, such as a SOUL request or a DISPLAY command, is being sent to a data set, the USE command must be specified before any commands that produce output to that data set are executed.
If you are using an external security interface, authorization to open sequential data sets is validated during execution of the command. For more information, refer to Security interfaces.