On Thu, 21 May 2009 08:35:04 -0500, John McKown <joa...@swbell.net> wrote:

>On Thu, 21 May 2009 08:25:01 -0500, McKown, John <jmck...@healthmarkets.com>
>wrote:
>
>>I could use some help. I am writing a REXX exec which interfaces with the
>ADDRESS SDSF stuff. Almost everything is working. But, from the H display, I
>cannot get the JOBID field populated. The REXX exec looks like:
>>
>
>I really, really hate it when I find the answer a minute after posting the
>question. I was picking up the wrong GROUP in the ISFPRMnn member when I ran
>in batch. I don't know why, but it did not pick up my TSOAUTH properly and
>so I fell into the DEFAULT group instead of the SYSTEMS group. Once I fixed
>that, all was OK.
>
>Sorry - I am SO glad that I'm on vacation next week.
>

If your security (ISFPARMS) depends on TSOAUTH, then in batch all you
get is JCL authority.  From the fine manual:


     When an SDSF batch session is started, it establishes the   
     following values for these criteria:                        
                                                                

     User ID   Set to the user ID from the ACEE (accessor        
               environment element), provided it contains a valid
               user ID OR Set to the job name minus the  last    
               character.                                        
                                                                 
     Logon proc name Set to BATCH for program name SDSF, and AFD 
     for program name ISFAFD.                                    
                                                                 
     Terminal name Set to BATCH for program name SDSF, and the LU
     name for program name ISFAFD.                               
                                                                 
     TSOAUTH for ISFGRP Set to JCL authority.              
      

In one of our small monoplex systems the ISFPARMS are still similar to 
those old defaults / samples that check for TSO ACCOUNT to classify
someone in the SYSPROG group and OPER to classify in the operator group
and then "all others".   So SDSF in batch on that system doesn't work for
sysprogs / operators.   I did set up some additional groups recently on
that system for production batch jobs (and the people on my team of
course) that work by userid  (IUID) with NTBL entries.  No one ever
seemed to use SDSF in batch in this particular environment prior to
z/OS 1.9 with SDSF / REXX.  

Regards,

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark.zel...@zurichna.com
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to