Hal,

Here's what you can find in z/OS V1R7.0 JES2 Commands, SA22-7526-05:

<quote>

5.243 $VS - Enter MVS system commands through JES2

Function

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

Syntax


>>__$VS__,'command('command')...________________________________________><

Parameters

'command'

The MVS system command(s) that are submitted through JES2. You must use
double quotes in any MVS command that uses single quotes. 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 the proper MVS system command group authority
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.

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), SA22-7631

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.

</quote>

Incidentally, it's quite a while since I saw a "card reader".

Chris Mason

----- Original Message ----- 
From: "Hal Merritt" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Thursday, 02 March, 2006 8:07 PM
Subject: Re: Commands in Batch


> Also might also be aware that the commands are executed immediately upon
> submission on that LPAR. There is no delay or routing. There is no
> relevance where the commands appear; they can appear anywhere in the
> job.
>
> I think I read in some IBM doc that the //  COMMAND ' ' was the
> 'preferred' method.
>
> I am not familiar with the /*$VS,' ' syntax.
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
> Behalf Of Ed Finnell
> Sent: Thursday, March 02, 2006 12:36 PM
> To: [email protected]
> Subject: Re: Commands in Batch
>
>
> In a message dated 3/2/2006 12:30:49 P.M. Central Standard Time,
> [EMAIL PROTECTED] writes:
>
> am going  to use the  /*$vs,'       ' command in the batch. B4  the
> JOBCARD
>
>
>
> >>
> The initiator that it runs in need AUTH=ALL and if opercmds. is active
> the
> submitting user needs authority to the subclass.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to