Re: SMS command via Batch

[Neil Duffee]

Caveat:  I get the daily digest (as well as being behind on my reading) so this 
may have been hashed apart already.

Using the SCDS named '*ACTIVE*' (quotes are required) in ISMF will provide the 
same information as the DISPLAY SMS console command.  Issue your VARY then 
refresh the ISMF screen to see the new values.  (No, ISMF does *not* 
auto-update.  It's an ISPF application and the panel needs to go out and get 
the new status.)  If you're uncertain, REFRESH on the command-line.  (of 
course, any sort values you might have used are gone so you'll need to reissue 
the command ie.  REFRESH;SORT 39 IN D 4 IN D 2.)

ps.  If you want to see what you'd get if you did SETSMS SCDS(), use the actual 
SCDS name ie. 'SYS4.DFSMS.IGDSMS00.SCDS' (local name), in ISMF.  

pps.  I use SMS10 for a staging configuration that can be tested using 
NaviQuest, SETSMS SCDS(SMS10) so I can revert back if necessary, then transfer 
SMS10 to SMS00 & SETSMS SCDS(SMS00) when the config has been stable for several 
weeks.

ppps.  For the inevitable question, more info on NaviQuest can be found in the 
SMS Storage Admin Reference manual(s).

>  signature = 6 lines follows  <
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585  fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
"How *do* you plan for something like that?"  Guardian Bob, Reboot
"For every action, there is an equal and opposite criticism."
"Systems Programming: Guilty, until proven innocent"  John Norgauer 2004

-Original Message-
From: retired mainframer [mailto:retired-ma...@Q...] 
Sent: January 17, 2013 14:20
Subject: Re: SMS COMMAND VIA BATCH

I believe ISMF shows the status in the SCDS while the D command shows the 
status in the ACDS.  VARY commands update the ACDS but you need to manually 
update the SCDS if you want the change to be reflected in the next ACTIVATE.

:>: -Original Message-
:>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
:>: Behalf Of John Dawes
:>: Sent: Thursday, January 17, 2013 9:54 AM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: SMS COMMAND VIA BATCH
:>:
:>: I tried out your suggestion and it ran well.  When I run the command to
:>: query the status of the storage group D SMS,SG(CICSSG01),LISTVOL it
:>: shows that the VOLUME is D.
:>: However, when I check via ISMF it shows that it is in ENABLE status (col
:>: 25).  I cannot understand which status is right or why there is a
:>: discrepancy between the two.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[af dc]

Hi Boris, you're right. I did have line in cols 73-80.

Many thx,A.Cecilio


On Mon, Jan 21, 2013 at 12:52 PM, Boris Lenz wrote:

> On Mon, January 21, 2013 12:53, af dc wrote:
> > H Boris,
> > I'm not understanding why I'm getting the following error:
> >
> > # of MVS commands to issue: 1
> >  Issuing command #1...
> >  DISPLAY SMS
> > 11.50.35  IGD029I ERROR FOR DISPLAY SMS COMM 137
> > 11.50.35  ERROR IS EMBEDDED BLANKS BETWEEN OPERANDS OF COMMAND
> > READY
> > END
>
> Do you have ISPF line numbers in col 73-80?
>
> Can't think of anything else right now. The only transmission error in my
> REXX is in the line with "if (left(inplines.i,2)" (listserv translated the
> two ampersands). But that can't be the error in your case.
>
> Regards,
> Boris
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Boris Lenz]

On Mon, January 21, 2013 12:53, af dc wrote:
> H Boris,
> I'm not understanding why I'm getting the following error:
>
> # of MVS commands to issue: 1
>  Issuing command #1...
>  DISPLAY SMS
> 11.50.35  IGD029I ERROR FOR DISPLAY SMS COMM 137
> 11.50.35  ERROR IS EMBEDDED BLANKS BETWEEN OPERANDS OF COMMAND
> READY
> END

Do you have ISPF line numbers in col 73-80?

Can't think of anything else right now. The only transmission error in my
REXX is in the line with "if (left(inplines.i,2)" (listserv translated the
two ampersands). But that can't be the error in your case.

Regards,
Boris

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Richards, Robert B.]

It is telling you that you have embedded blanks between operands, some like 
this:  D   SMS (two blanks between D and SMS). Or what is COMM following SMS?

Bob

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of af dc
Sent: Monday, January 21, 2013 6:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMS COMMAND VIA BATCH

H Boris,
I'm not understanding why I'm getting the following error:

# of MVS commands to issue: 1
 Issuing command #1...
 DISPLAY SMS
11.50.35  IGD029I ERROR FOR DISPLAY SMS COMM 137
11.50.35  ERROR IS EMBEDDED BLANKS BETWEEN OPERANDS OF COMMAND READY END

however it worked on:
# of MVS commands to issue: 1
 Issuing command #1...
 D U,,,03C1,4
11.44.55  IEE457I 11.44.55 UNIT STATUS 433
11.44.55  UNIT TYPE STATUSVOLSER VOLSTATE
11.44.55  03C1 359L O-NRD  -AS   /REMOV
11.44.55  03C2 359L O-NRD  -ASI00340 PRIV/REMOV
11.44.55  03C3 359L O-NRD  -ASI00082 PRIV/REMOV
11.44.55  03C4 359L O-NRD  -AS   /REMOV
READY
END

Can you pls geve me an hint ??
Many thx, A.Cecilio.




On Thu, Jan 17, 2013 at 4:23 PM, Boris Lenz  wrote:

> John,
>
> your command wasn't found because VARY is an MVS command, not a TSO 
> command, and IKJEFT01 is TSO.
>
> If, as others pointed out, the // COMMAND suggestion doesn't work due 
> to authorization issues or timing issues, you may want to try it in 
> TSO batch again, using the CONSOLE command (for which you're authorized 
> maybe).
>
> Something like this:
>
> //your-jobcard JOB ...
> //STEP01EXEC  PGM=IEBUPDTE,PARM=NEW
> //SYSPRINT  DD  DUMMY
> //SYSUT2DD  DISP=(,PASS),SPACE=(TRK,(1,1)),
> //  RECFM=FB,LRECL=80,DSORG=PO,DSNTYPE=LIBRARY
> //SYSIN DD  DATA,DLM='¬¬'
> ./ ADD NAME=MVSCMD
> /* rexx */
> /* issues MVS commands */
> arg dd
> call ReadInput
> if result ^= 0 then exit result
> call CountCmds
> say "# of MVS commands to issue: "result cartpfx = userid cartcnt = 0 
> address tso do k = 1 to inplines.0  "CONSOLE ACTIVATE NAME("userid"Z)"
>  'CONSPROF SOLDISP(NO) UNSOLDISP(NO) SOLNUM(1024) UNSOLNUM(1024)'
>  conscmd = inplines.k
>  'CONSOLE SYSCMD('conscmd') CART('conscart')'
>  gc = getmsg('R.','SOL',conscart,,5)
>  if gc = 4 then gc = getmsg('R.','EITHER',conscart,,5)  if gc = 0 then 
> do
> say " Issuing command #"k"..."
> say " "conscmd
> do i = 1 to r.0
>conscmdn = r.mdbgtimh ""r.i
>say conscmdn
> end
>  if gc > 0 then say 'Unable to retrieve message - GETMSG RC:' gc  end  
> 'CONSPROF SOLDISP(YES) UNSOLDISP(YES) SOLNUM(1000) UNSOLNUM(1000)'
>  'CONSOLE DEACTIVATE'
> end
> exit
> /**/
> CountCmds: procedure expose inplines.
>   j = 0
>   do i = 1 to inplines.0
> if (left(inplines.i,2) ^= "&&") then j=j+1
>   end
> return j
> /**/
> ReadInput: procedure expose dd inplines.
> maxcc = 0
>   address mvs "EXECIO * DISKR "dd" (STEM INPLINES. FINIS"
>   if rc ^= 0 then do
> say "RXLENZ01 ERROR READING INPUT FROM DD "dd
> maxcc = 16
>   end
>   if inplines.0 = 0 then do
> say "RXLENZ02 NO INPUT PROVIDED IN DD "dd
> maxcc = 16
>   end
> return maxcc
> /**/
> ¬¬
> //*
> //STEP02EXEC  PGM=IKJEFT01,PARM='%MVSCMD MVSCMDS'
> //SYSEXEC   DD  DSN=*.STEP01.SYSUT2,DISP=(OLD,DELETE)
> //SYSTSPRT  DD  SYSOUT=*
> //SYSTSIN   DD  DUMMY
> //MVSCMDS   DD *
> VARY SMS,VOLUME(SMC1G5),DISABLE,NEW
> //
>
>
> Regards,
> Boris
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[af dc]

H Boris,
I'm not understanding why I'm getting the following error:

# of MVS commands to issue: 1
 Issuing command #1...
 DISPLAY SMS
11.50.35  IGD029I ERROR FOR DISPLAY SMS COMM 137
11.50.35  ERROR IS EMBEDDED BLANKS BETWEEN OPERANDS OF COMMAND
READY
END

however it worked on:
# of MVS commands to issue: 1
 Issuing command #1...
 D U,,,03C1,4
11.44.55  IEE457I 11.44.55 UNIT STATUS 433
11.44.55  UNIT TYPE STATUSVOLSER VOLSTATE
11.44.55  03C1 359L O-NRD  -AS   /REMOV
11.44.55  03C2 359L O-NRD  -ASI00340 PRIV/REMOV
11.44.55  03C3 359L O-NRD  -ASI00082 PRIV/REMOV
11.44.55  03C4 359L O-NRD  -AS   /REMOV
READY
END

Can you pls geve me an hint ??
Many thx, A.Cecilio.




On Thu, Jan 17, 2013 at 4:23 PM, Boris Lenz  wrote:

> John,
>
> your command wasn't found because VARY is an MVS command, not a TSO
> command, and IKJEFT01 is TSO.
>
> If, as others pointed out, the // COMMAND suggestion doesn't work due to
> authorization issues or timing issues, you may want to try it in TSO batch
> again, using the CONSOLE command (for which you're authorized maybe).
>
> Something like this:
>
> //your-jobcard JOB ...
> //STEP01EXEC  PGM=IEBUPDTE,PARM=NEW
> //SYSPRINT  DD  DUMMY
> //SYSUT2DD  DISP=(,PASS),SPACE=(TRK,(1,1)),
> //  RECFM=FB,LRECL=80,DSORG=PO,DSNTYPE=LIBRARY
> //SYSIN DD  DATA,DLM='¬¬'
> ./ ADD NAME=MVSCMD
> /* rexx */
> /* issues MVS commands */
> arg dd
> call ReadInput
> if result ^= 0 then exit result
> call CountCmds
> say "# of MVS commands to issue: "result
> cartpfx = userid
> cartcnt = 0
> address tso
> do k = 1 to inplines.0
>  "CONSOLE ACTIVATE NAME("userid"Z)"
>  'CONSPROF SOLDISP(NO) UNSOLDISP(NO) SOLNUM(1024) UNSOLNUM(1024)'
>  conscmd = inplines.k
>  'CONSOLE SYSCMD('conscmd') CART('conscart')'
>  gc = getmsg('R.','SOL',conscart,,5)
>  if gc = 4 then gc = getmsg('R.','EITHER',conscart,,5)
>  if gc = 0 then do
> say " Issuing command #"k"..."
> say " "conscmd
> do i = 1 to r.0
>conscmdn = r.mdbgtimh ""r.i
>say conscmdn
> end
>  if gc > 0 then say 'Unable to retrieve message - GETMSG RC:' gc
>  end
>  'CONSPROF SOLDISP(YES) UNSOLDISP(YES) SOLNUM(1000) UNSOLNUM(1000)'
>  'CONSOLE DEACTIVATE'
> end
> exit
> /**/
> CountCmds: procedure expose inplines.
>   j = 0
>   do i = 1 to inplines.0
> if (left(inplines.i,2) ^= "&&") then j=j+1
>   end
> return j
> /**/
> ReadInput: procedure expose dd inplines.
> maxcc = 0
>   address mvs "EXECIO * DISKR "dd" (STEM INPLINES. FINIS"
>   if rc ^= 0 then do
> say "RXLENZ01 ERROR READING INPUT FROM DD "dd
> maxcc = 16
>   end
>   if inplines.0 = 0 then do
> say "RXLENZ02 NO INPUT PROVIDED IN DD "dd
> maxcc = 16
>   end
> return maxcc
> /**/
> ¬¬
> //*
> //STEP02EXEC  PGM=IKJEFT01,PARM='%MVSCMD MVSCMDS'
> //SYSEXEC   DD  DSN=*.STEP01.SYSUT2,DISP=(OLD,DELETE)
> //SYSTSPRT  DD  SYSOUT=*
> //SYSTSIN   DD  DUMMY
> //MVSCMDS   DD *
> VARY SMS,VOLUME(SMC1G5),DISABLE,NEW
> //
>
>
> Regards,
> Boris
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Shmuel Metz (Seymour J.)]

In , on 01/18/2013
   at 10:02 AM, Fabio Luiz Pereira  said:

>I think it is not possible to vary a sms volume throught a IKJ.

VARY is not a TSO command, so IKJEFT01 can't perform it directly, but
I know of no reason that an authorized user couldn't use the CONSOLE
command to issue the VARY.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[retired mainframer]

It can become a problem if someone needs to make a change to the SCDS (such
as update an ACS routine) and activate it while forgetting that some ACDS
updates are not present in the SCDS.  Once the SCDS is activated (which
means it is copied to the ACDS), the previous ACDS updates disappear.  So if
the reason you disabled the volume is still valid, you would not be happy if
it were suddenly re-enabled.

If the operator command you issued (such as V SMS,...) is intended to be a
permanent fix to the problem at hand, once it has been satisfactorily tested
I would immediately update the SCDS with the same change.  That way, a
future SCDS update will not introduce a regression problem.

:>: -Original Message-
:>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
:>: Behalf Of John Dawes
:>: Sent: Friday, January 18, 2013 6:16 AM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: SMS COMMAND VIA BATCH
:>:
:>: Retired Mainframer,
:>:
:>: I think you hit the nail on the head.  Would it be a problem if ACDS and
:>: SCDS do not show the same status?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[John Dawes]

Retired Mainframer,
 
I think you hit the nail on the head.  Would it be a problem if ACDS and SCDS 
do not show the same status?



From: retired mainframer 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Thursday, 17 January 2013 2:19 PM
Subject: Re: SMS COMMAND VIA BATCH

I believe ISMF shows the status in the SCDS while the D command shows the
status in the ACDS.  VARY commands update the ACDS but you need to manually
update the SCDS if you want the change to be reflected in the next ACTIVATE.

:>: -Original Message-
:>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
:>: Behalf Of John Dawes
:>: Sent: Thursday, January 17, 2013 9:54 AM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: SMS COMMAND VIA BATCH
:>:
:>: Boris,
:>:
:>: I tried out your suggestion and it ran well.  When I run the command to
:>: query the status of the storage group D SMS,SG(CICSSG01),LISTVOL it
:>: shows that the VOLUME is D.
:>: However, when I check via ISMF it shows that it is in ENABLE status (col
:>: 25).  I cannot understand which status is right or why there is a
:>: discrepancy between the two.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Rouse, Willie]

Try activating a console session before you issue the VARY command.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Fabio Luiz Pereira
Sent: Friday, January 18, 2013 5:03 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMS COMMAND VIA BATCH

Hi all,
I think it is not possible to vary a sms volume throught a IKJ. You need to use 
Naviquest. There is a chapter in the DFSMS Storage Admin. Manual about this 
facility.
F�bio

> Date: Thu, 17 Jan 2013 07:30:50 -0800
> From: jhn_da...@yahoo.com.au
> Subject: SMS COMMAND VIA BATCH
> To: IBM-MAIN@LISTSERV.UA.EDU
> 
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


This E-mail and any of its attachments may contain Prince George’s
County Government or Prince George's County 7th Judicial Circuit
Court proprietary information or Protected Health Information,
which is privileged and confidential.  This E-mail is intended
solely for the use of the individual or entity to which it is
addressed.  If you are not the intended recipient of this E-mail,
you are hereby notified that any dissemination, distribution,
copying, or action taken in relation to the contents of and
attachments to this E-mail is strictly prohibited by federal law
and may expose you to civil and/or criminal penalties. If you have
received this E-mail in error, please notify the sender immediately
and permanently delete the original and any copy of this E-mail and
any printout.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Fabio Luiz Pereira]

Hi all,
I think it is not possible to vary a sms volume throught a IKJ. You need to use 
Naviquest. There is a chapter in the DFSMS Storage Admin. Manual about this 
facility.
Fábio

> Date: Thu, 17 Jan 2013 07:30:50 -0800
> From: jhn_da...@yahoo.com.au
> Subject: SMS COMMAND VIA BATCH
> To: IBM-MAIN@LISTSERV.UA.EDU
> 
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
  
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[R.S.]

W dniu 2013-01-17 22:45, Steve Conway pisze:

Within your JES2PARM, you can specify by JOBCLASS whether to allow command
processing or not.  I think JES2 gets first whack at saying "No", followed
by RACF (if JES2 thinks it's OK).


Well... so?

JOBCLASS can allow (ask operator) or deny all the commands, regardless 
of command type and user who issued it. Not funny. Tha't why OPERCMDS is 
created - to make distinction between MVS.DISPLAY and MVS.QUIESCE as 
well as JOHN and FRANK.


JOBCLASS is free of choice in vanilla system, so any user can use any 
class. It can be limited using exits, such exit could check ...in RACF.



--
Radoslaw Skorupka
Lodz, Poland






--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. 


BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax 
+48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Shmuel Metz (Seymour J.)]

In <05dc01cdf4c8$fea86de0$fbf949a0$@mindspring.com>, on 01/17/2013
   at 08:40 AM, Lizette Koehler  said:

>It might work under OPER in TSO.

OPER is by design very limited; I'd suggest CONSOLE if you're
authorized for it.

-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 Atid/2
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Jonathan Goossen]

Or you can have something like OPSMVS intercept the WTOR and reply No.

Thank you and have a Terrific day!

Jonathan Goossen, DTM
ACT Mainframe Storage Group
Personal: 651-361-4541
Department Support Line: 651-361-
For help with communication and leadership skills checkout Woodwinds 
Toastmasters.



IBM Mainframe Discussion List  wrote on 
01/17/2013 03:45:24 PM:

> From: Steve Conway 
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 01/17/2013 03:45 PM
> Subject: Re: SMS COMMAND VIA BATCH
> Sent by: IBM Mainframe Discussion List 
> 
> Within your JES2PARM, you can specify by JOBCLASS whether to allow 
command 
> processing or not.  I think JES2 gets first whack at saying "No", 
followed 
> by RACF (if JES2 thinks it's OK).
> 
> 
> Cheers,,,Steve
> 
> Steven F. Conway, CISSP
> LA Systems
> z/OS Systems Support
> Phone: 703.295.1926
> steve_con...@ao.uscourts.gov
> 
> 
> 
> From:   "R.S." 
> To:     IBM-MAIN@LISTSERV.UA.EDU
> Date:   01/17/2013 04:34 PM
> Subject:Re: SMS COMMAND VIA BATCH
> Sent by:IBM Mainframe Discussion List 
> 
> 
> 
> W dniu 2013-01-17 17:06, Ed Gould pisze:
> > Lizette:
> >
> > AND that is only if the JES2 init parms are set up that way. Which of
> > course is a big NONO (security wise).
> >
> 
> Big what-what? AFAIK all commands from job are under OPERCMDS class.
> 
> 
> 
> -- 
> Radoslaw Skorupka
> Lodz, Poland
> 
> 
> 
> 
> 
> 
> --
> Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
> przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by 
> jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie 
jeste 
> adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej 
> przekazania adresatowi, informujemy, e jej rozpowszechnianie, 
kopiowanie, 
> rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie 
> zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, 
> prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale 
> usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub 
> zapisane na dysku.
> 
> This e-mail may contain legally privileged information of the Bank and 
is 
> intended solely for business use of the addressee. This e-mail may only 
be 
> received by the addressee and may not be disclosed to any third parties. 

> If you are not the intended addressee of this e-mail or the employee 
> authorised to forward it to the addressee, be advised that any 
> dissemination, copying, distribution or any other similar activity is 
> legally prohibited and may be punishable. If you received this e-mail by 

> mistake please advise the sender immediately by using the reply facility 

> in your e-mail software and delete permanently this e-mail including any 

> copies of it either printed or saved to hard drive. 
> 
> BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 
00, 
> fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl
> Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego 
> Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 
> 526-021-50-88. 
> Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w 
> caoci wpacony) wynosi 168.555.904 zotych.
> 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


This e-mail message and all attachments transmitted with it may
contain legally privileged and/or confidential information intended
solely for the use of the addressee(s). If the reader of this
message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, forwarding or
other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all
copies and backups thereof. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Steve Conway]

Within your JES2PARM, you can specify by JOBCLASS whether to allow command 
processing or not.  I think JES2 gets first whack at saying "No", followed 
by RACF (if JES2 thinks it's OK).


Cheers,,,Steve

Steven F. Conway, CISSP
LA Systems
z/OS Systems Support
Phone: 703.295.1926
steve_con...@ao.uscourts.gov



From:   "R.S." 
To: IBM-MAIN@LISTSERV.UA.EDU
Date:   01/17/2013 04:34 PM
Subject:    Re: SMS COMMAND VIA BATCH
Sent by:IBM Mainframe Discussion List 



W dniu 2013-01-17 17:06, Ed Gould pisze:
> Lizette:
>
> AND that is only if the JES2 init parms are set up that way. Which of
> course is a big NONO (security wise).
>

Big what-what? AFAIK all commands from job are under OPERCMDS class.



-- 
Radoslaw Skorupka
Lodz, Poland






--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by 
jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste 
adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej 
przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, 
rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie 
zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, 
prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale 
usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub 
zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. 
If you are not the intended addressee of this e-mail or the employee 
authorised to forward it to the addressee, be advised that any 
dissemination, copying, distribution or any other similar activity is 
legally prohibited and may be punishable. If you received this e-mail by 
mistake please advise the sender immediately by using the reply facility 
in your e-mail software and delete permanently this e-mail including any 
copies of it either printed or saved to hard drive. 

BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, 
fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego 
Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 
526-021-50-88. 
Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w 
caoci wpacony) wynosi 168.555.904 zotych.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[R.S.]

W dniu 2013-01-17 17:06, Ed Gould pisze:

Lizette:

AND that is only if the JES2 init parms are set up that way. Which of
course is a big NONO (security wise).



Big what-what? AFAIK all commands from job are under OPERCMDS class.



--
Radoslaw Skorupka
Lodz, Poland






--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. 


BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax 
+48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[retired mainframer]

I believe ISMF shows the status in the SCDS while the D command shows the
status in the ACDS.  VARY commands update the ACDS but you need to manually
update the SCDS if you want the change to be reflected in the next ACTIVATE.

:>: -Original Message-
:>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
:>: Behalf Of John Dawes
:>: Sent: Thursday, January 17, 2013 9:54 AM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: SMS COMMAND VIA BATCH
:>:
:>: Boris,
:>:
:>: I tried out your suggestion and it ran well.  When I run the command to
:>: query the status of the storage group D SMS,SG(CICSSG01),LISTVOL it
:>: shows that the VOLUME is D.
:>: However, when I check via ISMF it shows that it is in ENABLE status (col
:>: 25).  I cannot understand which status is right or why there is a
:>: discrepancy between the two.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[John Dawes]

Boris,
 
I tried out your suggestion and it ran well.  When I run the command to query 
the status of the storage group D SMS,SG(CICSSG01),LISTVOL it shows that the 
VOLUME is D.
However, when I check via ISMF it shows that it is in ENABLE status (col 25).  
I cannot understand which status is right or why there is a discrepancy between 
the two.



From: Boris Lenz 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Thursday, 17 January 2013 11:23 AM
Subject: Re: SMS COMMAND VIA BATCH

John,

your command wasn't found because VARY is an MVS command, not a TSO command, 
and IKJEFT01 is TSO.

If, as others pointed out, the // COMMAND suggestion doesn't work due to 
authorization issues or timing issues, you may want to try it in TSO batch 
again, using the CONSOLE command (for which you're authorized maybe).

Something like this:

//your-jobcard JOB ...                                              
//STEP01    EXEC  PGM=IEBUPDTE,PARM=NEW                              
//SYSPRINT  DD  DUMMY                                                
//SYSUT2    DD  DISP=(,PASS),SPACE=(TRK,(1,1)),                      
//          RECFM=FB,LRECL=80,DSORG=PO,DSNTYPE=LIBRARY              
//SYSIN    DD  DATA,DLM='¬¬'                                        
./ ADD NAME=MVSCMD                                                  
/* rexx */                                                          
/* issues MVS commands */                                            
arg dd                                                              
call ReadInput                                                      
if result ^= 0 then exit result                                      
call CountCmds                                                      
say "# of MVS commands to issue: "result                            
cartpfx = userid                                                    
cartcnt = 0                                                          
address tso                                                          
do k = 1 to inplines.0                                              
"CONSOLE ACTIVATE NAME("userid"Z)"                                  
'CONSPROF SOLDISP(NO) UNSOLDISP(NO) SOLNUM(1024) UNSOLNUM(1024)'    
conscmd = inplines.k                                                
'CONSOLE SYSCMD('conscmd') CART('conscart')'                        
gc = getmsg('R.','SOL',conscart,,5)                                
if gc = 4 then gc = getmsg('R.','EITHER',conscart,,5)              
if gc = 0 then do                                                  
    say "        Issuing command #"k"..."                          
    say "        "conscmd                                          
    do i = 1 to r.0                                                  
      conscmdn = r.mdbgtimh ""r.i                                  
      say conscmdn                                                  
    end                                                              
if gc > 0 then say 'Unable to retrieve message - GETMSG RC:' gc    
end                                                                
'CONSPROF SOLDISP(YES) UNSOLDISP(YES) SOLNUM(1000) UNSOLNUM(1000)'  
'CONSOLE DEACTIVATE'                                                
end                                                                  
exit                                                                
/**/                                                                
CountCmds: procedure expose inplines.                                
  j = 0                                                              
  do i = 1 to inplines.0                                            
    if (left(inplines.i,2) ^= "&&") then j=j+1                      
  end                                                                
return j                                                            
/**/                                                                
ReadInput: procedure expose dd inplines.                            
maxcc = 0                                                            
  address mvs "EXECIO * DISKR "dd" (STEM INPLINES. FINIS"            
  if rc ^= 0 then do                                                
    say "RXLENZ01 ERROR READING INPUT FROM DD "dd                    
    maxcc = 16                                                      
  end                                                                
  if inplines.0 = 0 then do                                          
    say "RXLENZ02 NO INPUT PROVIDED IN DD "dd                        
    maxcc = 16                                                      
  end                                                            

Re: SMS COMMAND VIA BATCH

[Darth Keller]

Have you ever looked at using Naviquest to issue your SMS commands?   You 
can generate the JCL through the ISMF panels.

ISMF; 
ENHANCED ACS MANAGEMENT; 
BATCH TESTING/CONFIGURATION MANAGEMENT SELECTION MENU;
CONFIGURATION CHANGES BATCH SAMPLES SELECTION MENU;
Change Storage Group Volume Status 
Comment from the generated JCL:  SAMPLE JCL TO ADD NEW VOLUMES AND 
THEIR STATUS


An example from my JCL library: 
Note:  MY_ID would be where I specify my TSO userID; 
SGPAL in this example is the storage group name. 
SCDS name is pretty much self-documented.


//ADDVOL1 EXEC ACBJBAOB, 
//PLIB1='SYS1.DGTPLIB', 
//TABL2=MY_ID.TEST.ISPTABL 
//SYSUDUMP DD  SYSOUT=* 
//TEMPFILE  DD  DSN=&&VOLADDS,DISP=(NEW,KEEP), 
//  SPACE=(CYL,(15,15)),LRECL=300,RECFM=F,BLKSIZE=300 
//SYSTSIN  DD * 
PROFILE PREFIX(MY_ID) 
ISPSTART CMD(ACBQBAI9) + 
BATSCRW(132) BATSCRD(27) BREDIMAX(3) BDISPMAX() 
/* 
//VOLADD  DD  * 
UPDHLVLSCDS() 
SCDSNAME('SMS.SCDS01.SCDS') VOL(PALF00) SG(SGPAL) STATUSALL(DISNEW) 
SCDSNAME('SMS.SCDS01.SCDS') VOL(PALF01) SG(SGPAL) STATUSALL(DISNEW) 
/* 
//VOLALT  DD  * 
/* 
//VOLDEL  DD * 
 /* 
 //ADDVOL2 EXEC ACBJBAOB, 
 //PLIB1='SYS1.DGTPLIB', 
 //TABL2=MY_ID.TEST.ISPTABL 
 //SYSUDUMP DD  SYSOUT=* 
 //SYSTSIN  DD DSN=&&VOLADDS,DISP=(OLD,DELETE) 
 //***   



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
/* 
//  

This e-mail message and all attachments transmitted with it may
contain legally privileged and/or confidential information intended
solely for the use of the addressee(s). If the reader of this
message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, forwarding or
other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all
copies and backups thereof. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Boris Lenz]

John,

your command wasn't found because VARY is an MVS command, not a TSO command, 
and IKJEFT01 is TSO.

If, as others pointed out, the // COMMAND suggestion doesn't work due to 
authorization issues or timing issues, you may want to try it in TSO batch 
again, using the CONSOLE command (for which you're authorized maybe).

Something like this:

//your-jobcard JOB ...   
//STEP01EXEC  PGM=IEBUPDTE,PARM=NEW  
//SYSPRINT  DD  DUMMY
//SYSUT2DD  DISP=(,PASS),SPACE=(TRK,(1,1)),  
//  RECFM=FB,LRECL=80,DSORG=PO,DSNTYPE=LIBRARY   
//SYSIN DD  DATA,DLM='¬¬'
./ ADD NAME=MVSCMD   
/* rexx */   
/* issues MVS commands */
arg dd   
call ReadInput   
if result ^= 0 then exit result  
call CountCmds   
say "# of MVS commands to issue: "result 
cartpfx = userid 
cartcnt = 0  
address tso  
do k = 1 to inplines.0   
 "CONSOLE ACTIVATE NAME("userid"Z)"  
 'CONSPROF SOLDISP(NO) UNSOLDISP(NO) SOLNUM(1024) UNSOLNUM(1024)'
 conscmd = inplines.k
 'CONSOLE SYSCMD('conscmd') CART('conscart')'
 gc = getmsg('R.','SOL',conscart,,5) 
 if gc = 4 then gc = getmsg('R.','EITHER',conscart,,5)   
 if gc = 0 then do   
say " Issuing command #"k"..."   
say " "conscmd   
do i = 1 to r.0  
   conscmdn = r.mdbgtimh ""r.i   
   say conscmdn  
end  
 if gc > 0 then say 'Unable to retrieve message - GETMSG RC:' gc 
 end 
 'CONSPROF SOLDISP(YES) UNSOLDISP(YES) SOLNUM(1000) UNSOLNUM(1000)'  
 'CONSOLE DEACTIVATE'
end  
exit 
/**/ 
CountCmds: procedure expose inplines.
  j = 0  
  do i = 1 to inplines.0 
if (left(inplines.i,2) ^= "&&") then j=j+1   
  end
return j 
/**/ 
ReadInput: procedure expose dd inplines. 
maxcc = 0
  address mvs "EXECIO * DISKR "dd" (STEM INPLINES. FINIS"
  if rc ^= 0 then do 
say "RXLENZ01 ERROR READING INPUT FROM DD "dd
maxcc = 16   
  end
  if inplines.0 = 0 then do  
say "RXLENZ02 NO INPUT PROVIDED IN DD "dd
maxcc = 16   
  end
return maxcc 
/**/ 
¬¬   
//*  
//STEP02EXEC  PGM=IKJEFT01,PARM='%MVSCMD MVSCMDS'
//SYSEXEC   DD  DSN=*.STEP01.SYSUT2,DISP=(OLD,DELETE)
//SYSTSPRT  DD  SYSOUT=* 
//SYSTSIN   DD  DUMMY
//MVSCMDS   DD * 
VARY SMS,VOLUME(SMC1G5),DISABLE,NEW 
//


Regards,
Boris

--
For IBM-MAIN s

Re: SMS COMMAND VIA BATCH

[David Devine]

An alternative way to skin this particular cat would be to use batch sdsf.

//JS0015   EXEC PGM=SDSF   
//ISFOUT   DD   SYSOUT=*   
//ISFINDD   *  
/RO *ALL,D SMS,SG(STANDARD),LISTVOL
/* 

The command string is limited to 42 chars so not great, but has the benefit in 
that if you can issue commands via sdsf you can use this.

Dave

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[John Dawes]

One question,  When I run the job don't I need the EXEC  PGM=x in order to 
issue the command ?  I checked the manual for an example but it just displays 
the actual COMMAND.
 Examples of the COMMAND StatementExample 1The following shows an example 
COMMAND statement with the START command.// COMMAND ’S VTAM’ start VTAMExample 
2The following is an example of a command that is continued with the command
operand in apostrophes.// COMMAND ’SEND ’’This message will be sent to user 
SCOTTC
// when this job is converted’’,USER=(SCOTTC)’



From: Steve Thompson 
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Thursday, 17 January 2013 10:50 AM
Subject: Re: SMS COMMAND VIA BATCH

From:  Lizette Koehler
Date:  01/17/2013 09:42 AM


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


Lizette's directive is a good one. You can also do the following:

//  VARY .

But in all of these, you will need to ensure that you have Security 
authority to issue commands via JCL.

This authority can be effected in a few ways.

Regards,
Steve Thompson

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Ed Gould]

Lizette:

AND that is only if the JES2 init parms are set up that way. Which of  
course is a big NONO (security wise).


Ed


On Jan 17, 2013, at 9:40 AM, Lizette Koehler wrote:

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:IBM- 
m...@listserv.ua.edu] On

Behalf

Of John Dawes
Sent: Thursday, January 17, 2013 8:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Pew, Curtis G]

On Jan 17, 2013, at 9:40 AM, Lizette Koehler  wrote:

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

It's important to note that the command is issued when the JCL is converted, 
usually shortly after the job is submitted, and not when the job is executing. 
This may not be what you want; for example, you may wish the command to be 
issued after step A but before step B.

-- 
Curtis Pew (c@its.utexas.edu)
ITS Systems Core
The University of Texas at Austin

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Steve Thompson]

From:   Lizette Koehler
Date:   01/17/2013 09:42 AM


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


Lizette's directive is a good one. You can also do the following:

//  VARY .

But in all of these, you will need to ensure that you have Security 
authority to issue commands via JCL.

This authority can be effected in a few ways.

Regards,
Steve Thompson

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMS COMMAND VIA BATCH

[Lizette Koehler]

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:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of John Dawes
> Sent: Thursday, January 17, 2013 8:31 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

SMS COMMAND VIA BATCH

[John Dawes]

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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN