$S PUN(nn) and $S R(nnnnn).PU(m)

Function

To start punch activity. The $HASP190 message asks whether the requested setup has been completed for the specified device. Either verify that the setup is complete or issue the $T PUNnnnnn command to override specific setup specifications. Then reissue the $S command to physically start the punch.

Syntax


>>-$S--+-PUNnn------+--+-------------+-------------------------><
       '-Rnnnnn.PUm-'  +-,PUNnn------+   
                       '-,Rnnnnn.PUm-'

Parameters

nn: The identifier of the local punch (1-99) to start.
nnnnn: The identifier of the remote workstation R (1-32767) that is attached to punch m (1-7).
m: The identifier of the punch (1-7) that is attached to the remote workstation Rnnnnn (1-32767).

Authority Required

This command requires device authority. The description of the $T RDRnn command explains how to ensure that the authority of the appropriate MVS™ system command group is assigned.

This command requires update security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide, SA32-0991.

Scope

Single member. This command will be in effect for this member only. There is no need to have this command issued to all members of the MAS.

Messages

The $HASP000 message indicates the command was accepted.

If work is found, JES2 issues the $HASP150 message indicating that the specified device is starting to process output.

If no work is found, JES2 issues the $HASP160 message indicating that the specified device found no work in the queue(s).

The $HASP626 message indicates that the unit device has not been specified or is invalid.

The $HASP627 message indicates that the unit device has been specified, but is unavailable.

Example

 1   $s pun1,r3.pu2

  $HASP000 OK

JES2 starts local punch 1 and punch 2 at remote workstation 3.