> -----Original Message-----
<snip>
> 
> So are you saying your default (which production falls into) 
> is what your
> forked process is falling into?
> 
> What about classifying by accounting information?  Have you looked at
> help in the dialogs.  Strangely enough, the help is "Work 
> Qualifiers for
> USS Subsystem Type" instead of OMVS subsystem type (and PLEASE
> lets not start that thread again!):
> 
> ============================================
> 
>     ***********************************************                 
>     *                   USS                       *                 
>     ***********************************************                 
>                                                                     
> Listed below are the various work qualifiers which are valid for an 
> z/OS UNIX System Services subsystem type.                           
>                                                                     
> ACCOUNTING INFORMATION                                              
>     Account numbers for z/OS UNIX System Services forked or spawned 
>     address spaces are set as follows:                              
>                                                                     
>     o   Forked or spawned address spaces inherit accounting data    
>         from parent address space.                                  
>                                                                     
>     o   When daemon processes such as rlogind or cron create new    
>                                                                     
>     o   When daemon processes such as rlogind or cron create new    
>         work using setuid() and exec(), accounting data comes from  
>         the user's RACF profile (the WAACCNT value in the WORKATTR  
>         segment).  If this value is not defined in RACF, the address
>         space will not have accounting data.                        
>                                                                     
>     o   Accounting data can also be verified or changed using the   
>         IEFUSI installation exit.                                   
> 
> ===========================================
> 
> Regards,
> 
> Mark                       
> --

We don't use accounting information in our batch jobs. Well, there is something 
in there. But it is not meaningful or controlled. Basically, for batch, we use 
the job class to assign the service group. All TSO users get the same service 
group. STCs are classified, as needed, by STC job name. We have little UNIX 
work, so I generally lump 99% of it in one service class. The rest is grouped 
by RACF id for specific RACF ids. 

I'll look at that WAACCNT to see if I can use it, thanks!

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
[email protected] * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

----------------------------------------------------------------------
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