>>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.
My bad, yes I was assuming you're using _BPX_JOBNAME for the ftpd. >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. My example was again assuming that _BPX_JOBNAME=FTPsomething is set for ftpd, then all sessions will run with TN=FTPsomething. And only then will the subrule catch the userids listed. In your case, your ftp session will run with service class OMVS (assuming the above shonw rules are all there are). Unfortunately, the OMVS subsystem section in the classification rules doesn't give you more than TN and UI (plus some less usefull). I always thought it to be difficult to setup some good rules for all that forked/spawned UNIX work. To distinguish between interactive users and system work, you need to be able clearly to distinguish TN and UI. If you don't force jobnames to adhere to some site specific rules, what inhibits a user to submit a batch job using the jobname of a server (say CTGMYJOB) and have all work happily run the same serviced class (SYSSTC in this example). -- Peter Hunkeler Credit Suisse ---------------------------------------------------------------------- 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
