View source for DEFINE PUNCH command

==Summary==
<dl>
<dt>Privileges
<dd>User 0 or system manager
<dt>Function
<dd>Specifies an output definition that, together with the USE command, directs <var class="product">Model&nbsp;204</var> punched output to a particular system or device. The definition remains in effect throughout the run unless it is overridden by another DEFINE PUNCH command specifying the same name. 
</dl>
==Syntax==
<p class="syntax">DEFINE PUNCH name [LIKE previousname] WITH
  SCOPE=SYSTEM [CLASS] [COPIES] [DIST]
  [HDR1 | HDR2 | HDR3] [HOLD | NOHOLD] [ID] 
  [INTERPRET | NOINTERPRET] [INTRDR] [NAME] [OUTLIM]
  [ROUTE] [ROUTER={MVS | VM}] [TAG] [WRITER]
</p>
 
<b>Where:</b>
<p>The options ROUTER, SEP/NOSEP, HDR1, HDR2, and HDR3 are common to all routers. The options common to all routers are described in the table below.</p>
<table>
<caption>DEFINE PUNCH options (all routers)   </caption>
    
<tr> <th>Option</th> <th>Specifies...</th> </tr>
   
<tr> <th><var>
<p>HDR1</p>
<p>HDR2</p>
<p>HDR3</p>
</var></th> <td>
<p>First, second, or third word of text on the <var class="product">Model&nbsp;204</var> separator line. This option can have up to eight characters and is used with the SEP option.</p>
<p>The default for HDR1 is M204LIST. </p>
<p>For HDR2, the default under z/VM is the first eight characters of the <var class="product">Model&nbsp;204</var> user ID if you do not indicate a NAME option. </p>
HDR3 has no default.       </td> </tr>
 
<tr> <th><var>ROUTER </var></th> <td>
<p>Method used in routing output. MVS and VM are the acceptable values for this option. The ROUTER option is required unless already specified in a template referred to by the LIKE phrase of the current DEFINE PUNCH command. This option has no default value.</p>
</td> </tr>
 
<tr> <th><var>
<p>SEP</p>
<p>NOSEP</p>
</var></th> <td>
<p>Whether a separator is inserted in <var class="product">Model&nbsp;204</var> output. </p>
<p>SEP indicates that there is a separator. Options HDR1, HDR2, and HDR3 form a single line with a blank space between each one. </p>
<p>NOSEP, the default, indicates that there is no separator.   </p>
</td> </tr>
   
</table>
<p>The options in the table below are router-specific. The possible routers are listed in parentheses before the option definition.</p>
==Syntax notes==
You can specify any number of DEFINE PUNCH output options. Options must be separated by commas or by one or more blanks.
==Examples==
The following examples show DEFINE PUNCH commands for a system running under native z/OS. The first example uses the WITH phrase to define the attributes of an output destination:
<p class="code">DEFINE PUNCH THIRDP - 
WITH SCOPE=SYSTEM,ROUTER=MVS, -
ROUTE=THIRD,NOSEP 
</p>
<p>The following example creates an output definition by using the LIKE phrase to refer to most of the attributes of the definition created in the first example. The WITH phrase is used to redefine the ROUTE option. </p>
<p class="code">DEFINE PUNCH FOURTHP LIKE THIRDP - 
WITH SCOPE=SYSTEM,ROUTE=FOURTH   
</p>
<p>The following examples show DEFINE PUNCH commands for a system running under native z/VM or a guest operating system under z/VM:</p>
<p class="code">DEFINE PUNCH THIRDP            - 
  WITH SCOPE=SYSTEM,ROUTER=VM, -
  ID=RSCS,TAG=THIRD,NOSEP,HOLD  
DEFINE PUNCH FOURTHP LIKE THIRDP - 
  WITH TAG=FOURTH,NOHOLD 
</p>
==Usage notes==
<p>The DEFINE PUNCH command specifies a destination for <var class="product">Model&nbsp;204</var> punched output and describes the characteristics of output that is to be sent to that destination. The options for this command give you more control over output and tailor the <var class="product">Model&nbsp;204</var> separator page. The destination might be another system or an alternate device. Any number of different definitions can be specified. These definitions exist for the duration of the <var class="product">Model&nbsp;204</var> run and are available to all users. Once a particular definition has been specified, it can be changed only with another DEFINE PUNCH command or USE command for that destination.</p>
<p>The DEFINE PUNCH command is optional. The information supplied in this command can be specified instead in the USE command that actually directs the output to the alternate device.</p>
<p>The DEFINE PUNCH command can be issued when <var class="product">Model&nbsp;204</var> is running under native z/OS, native z/VM, or a guest operating system under z/VM, or z/VSE/POWER. The guest operating system can be any z/OS or z/VSE operating system supported by <var class="product">Model&nbsp;204</var>. This command is not available under z/OS if the Preferred Machine Assist feature is used.</p>
<p>Whenever you issue a USE command to direct output to a destination other than your terminal, <var class="product">Model&nbsp;204</var> determines whether an output definition has been specified for that alternate destination in a DEFINE PUNCH command. The characteristics-for example, output identifiers, number of copies, separator format-specified in the DEFINE PUNCH definition are used to produce the output. These characteristics can be overridden by any options specified in the USE command itself. (See [[USE command: Directing output|USE: Directing output]].) In addition, certain characteristics are determined by the device selection made by the system manager in the Job Control Language or EXEC procedure for the run.</p>
[[Category: System manager commands]]
[[Category:Commands]]