On Mon, 25 Jan 2010 14:27:16 -0600, Peter Hunkeler
<[email protected]> wrote:

>>>ftp's children run under the userid with which the
>>>remote user logged in; and the jobname is derived from that
>>>userid as well. You can't catch ftpd's child processes
>>>with ftpd's userid.
>>>
>>
>><snip>
>>
>>No, but you can do this to force the same jobname for all by doing
>>something like this in the ftp server proc:
>
>Right and I'm sorry again for the incomplete post from this morning.
>It is exactly this _BPX_JOBNAME option that I was vaguely remembering
>all over a sudden and that I wanted to look up first.
>
>Nevertheless, the rule you posted is assigning SYSSTC to each an every
>file transfer.

No, only the FTP daemon.   I think you are assuming I am using
_BPX_JOBNAME because I mentioned it.  We don't.    FTPs run
under a different classification in OMVS or the default of OMVS.
In my sandbox sysplex where I copied from, they run in
OMVS. 

>
>>Action    Type       Name     Start                Service     Report
>>                                         DEFAULTS: OMVS        OMVS
>> ____  1  TN         CTG*     ___                  SYSSTC      CICS
>> ____  1  TN         FTP*     ___                  SYSSTC      NETWORK
>> ____  1  TN         ETCRC*   ___                  SYSSTC      SYSTEM
>> ____  1  TN         ETCINIT* ___                  SYSSTC      SYSTEM
>
>Is this really what you want? I'd either assign a different jobname to
>the ftpd servers (_BPX_JOBNAME=FTPCLIEN) and then assign a separate
>service class to the "clients" (I know they are server processes as per
>client/server convention :-)

See my comments above.

>
>You may even want to prefer some userids in case you've got some automated
>transfers:
>
>Action    Type       Name     Start                Service     Report
>                                         DEFAULTS: OMVS        OMVS
> ____  1  TN         CTG*     ___                  SYSSTC      CICS
> ____  1  TN         FTP*     ___                  SYSSTC      NETWORK
> ____  1  TN         FTPCLIEN ___                  FTPSTD      NETWORK
> ____     2   UI         SYSXFER                     FTPHIGH     NETWORK
> ____  1  TN         ETCRC*   ___                  SYSSTC      SYSTEM
> ____  1  TN         ETCINIT* ___                  SYSSTC      SYSTEM
>
>
>--

Are you saying I can do this:

                                                             More ===>   
          --------Qualifier--------               -------Class--------   
Action    Type       Name     Start                Service     Report    
                                         DEFAULTS: OMVS        OMVS      
 ____  1  TN         CTG*     ___                  SYSSTC      CICS      
 ____  1  TN         FTP*     ___                  SYSSTC      NETWORK   
 ____  2    UI         MYUSERID ___                GOD         GOD_____  
 ____  1  TN         ETCRC*   ___                  SYSSTC      SYSTEM    
 ____  1  TN         ETCINIT* ___                  SYSSTC      SYSTEM    

And FTPs initiated by MYUSERID will go to service class GOD but the
rest of the OMVS work by MYUSERID will go to OMVS?   I don't think
so.  The TN is MYUSERID, not FTP*.   Or am I misunderstanding.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[email protected]
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 [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to