Looking in from *way* outside, I wonder that the problem might *not* be security. The message states simply there was a non-zero RC. (Ok, security could cause that too.)
Does the MGCRE interface indicate which sub-system the command is to be directed to? Perhaps it should only be D SPOOL without the sub-system identifier ($). Alternately, could there be something in between ie. for SDSF, you use /$D SPOOL. Again, n00b response to be ignored as such. --------> signature = 8 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 "Schrodinger's backup: The condition of any backup is unknown until a restore is attempted." John McKown 2015 -----Original Message----- From: Terry Sambrooks [mailto:terr...sam...@btc...com] Sent: October 12, 2015 11:17 Subject: Re: Using MGCRE with JES2 Commands In respect of "Please post the full IEE707I message and the command attempted." The reality is that ANY z/OS command is accepted but ANY JES2 command is rejected so if I use $DSPOOL as an example the message received is: IEE707I $DSPOOL NOT EXECUTED If the program were not linked AC(1) it would SD22 which it does not. I am the security guy and as such own JES%.** which ought to give me access to commands which do not have an explicit profile, or so I thought. [snip] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
