z/OS JES2 Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


$VS - Enter MVS system commands through JES2

z/OS JES2 Commands
SA32-0990-00

Function

To enter an MVS™ system command in a job stream, through an automatic JES2 command, or within the JES2 initialization data set.

Syntax

Read syntax diagramSkip visual syntax diagram
>>-$VS--,'command--(--'command'--)----------------------------><

Parameters

‘command'
The MVS system command(s) that are submitted through JES2. You must use double quotation marks in any MVS command that uses single quotation marks. For example, to issue an MVS SEND command, you would enter:

$VS,'SEND "message text",USER=(userid)'.

Authority Required

This command requires system 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 control security access authority. For a description of assigning command input authority, see z/OS JES2 Initialization and Tuning Guide, SA32-0991.

Processing Considerations

The $VS command is valid only as an automatic command or in a job stream. If you wish to issue an MVS command from the console for immediate execution, enter the MVS command directly; $VS will not be accepted for this purpose.

The $VS command is normally entered from a local JES2 card reader that has system authority. The responses to the MVS command(s) entered with the $VS command appear at the console with master level authority on the issuing system.

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

Entering an MVS command using $VS does not generate any JES2 messages. For information about any MVS messages, see z/OS MVS System Messages, Vol 1 (ABA-AOM), SA38-0668

Example

 1   $vs, 'v (234,235,236),offline','d a'

JES2 submits the MVS VARY and DISPLAY commands to the MVS system for processing if the commands were issued in a job stream or as automatic commands.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014