Try: //send exec pgm=iebgener //sysprint dd sysout=* //sysin dd dummy //sysut2 dd sysout=(a,intrdr) //sysut1 dd data,dlm=qq $vs,""setprog blah,blah,blah""" qq
John Clifford IBM consultant in OKC On Wed, Jun 25, 2014 at 10:55 AM, zMan <[email protected]> wrote: > So revealing more of my vast ignorance: the OP seems to be suggesting that > operator commands can be issued from a batch job. I just spent 10 minutes > Googling and didn't find a description of how to do this. Can someone post > the JCL for a job to issue, say, a SETPROG? Will it always require operator > response? We have various test environments that need a series of operator > commands, and if I could put them into a job (or a Rexx program--is it also > possible to issue them from Rexx?), it would make life easier. > > > On Tue, Jun 24, 2014 at 4:31 PM, Walt Farrell <[email protected]> > wrote: > > > On Tue, 24 Jun 2014 11:28:26 +0530, Mainframe Mainframe < > > [email protected]> wrote: > > > > >3) Do I have to make any changes in RACF to avoid these issues. > > > > As another list member indicated, you should look up the ICH70007I > message > > and take the actions indicated in the book. > > > > -- > > Walt > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > -- > zMan -- "I've got a mainframe and I'm not afraid to use it" > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
