Well, if you must do JCL, then you need to use the JCL statement for COMMAND
not IKJEFT01.  Vary does not work under it.

It might work under OPER in TSO.

But, I find, //  COMMAND,VARY....

COMMAND Statement

z/OS V1R12.0 MVS JCL Reference
SA22-7597-14

Purpose

Use the COMMAND statement to specify an MVS™ or JES command that the system
issues when the submitted JCL is converted.

The COMMAND statement is the preferred way within the job control language
to specify commands, rather than using the JCL command statement, which is
described in JCL Command Statement. That is because the COMMAND statement is
in standard JCL statement format, is parsed and processed using code common
to the other JCL statements, and if necessary may be continued across
multiple card images, that is, is not limited to 80 characters. Note that
some MVS subsystems, including TSO, JES2, and JES3, offer additional ways to
enter system commands outside JCL, which may be preferable under certain
circumstances.


Acceptable

Lizette

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf
> Of John Dawes
> Sent: Thursday, January 17, 2013 8:31 AM
> To: [email protected]
> Subject: SMS COMMAND VIA BATCH
> 
> G'Day,
> 
> I am trying to execute the following command via batch however I was
unsuccessful :
> COMMAND VARY NOT FOUND
> 
> Could anybody suggest how I can correct my problem:
> 
> /*
> //STEP001 EXEC PGM=IKJEFT01
> //SYSPRINT DD SYSOUT=*
> //SYSTSPRT DD SYSOUT=*
> //SYSTSIN  DD *
> VARY SMS,VOLUME(SMC1G5),DISABLE,NEW
> /*
> //
> 
> Thanks in advance.
> 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to