________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Mark Zelden [[email protected]] Sent: Wednesday, October 12, 2011 9:03 AM To: [email protected] Subject: Re: REXX fails accessing SDSF console
On Wed, 12 Oct 2011 05:50:34 +0000, Uriel Carrasquilla <[email protected]> wrote: > "The biggest problem I have found with batch is that many shops have SDSF security set up (from the default/sample parms) based on TSO authorities (JCL, OPER, ACCT) and TSOAUTH is automatically set to JCL for a batch SDSF job (regardless of what authorities the USERID actually has). This is the documented behavior. " Mark, let me thank you for your help. My TSOBATCH REXX is now working as expected. The problem was the CONSOLE being used with ISPF SDSF interactively while running the REXX at the same time. I forced the REXX to use a different console (instead of the USERID default that gets assigned). The PARMLIB(ISFPRMxx) member was set up by my predecesor and it did have AUTH(ALL) for my user group. When reading your remarks, I don't understand how authorization for SDSF can be set up any other way. Could you please elaborate? ---------------------------------------------------------------------- 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
