RE: Reserve DASD [2]

>David,   
>
>David Fung [david-fung@rocketmail.com] wrote:
>
>>We are going to install 60G of DASD for our project use. However,
>>there are many other projects and developers working on the same box.
>>Is there a way to reserve our 60G and prevent other people from using
>>it?
>
>If you want to keep your new DASD physically separate you could add it in
>it's own ASP (auxilliary storage pool). The engineer can do this for you when
>he installs the disks, otherwise you will have to use the dedicated service
>tools.
>
>Use the new ASP for all objects related to the project and they will be
>physically on the new DASD. There is no simple way to prevent other users who
>have authority to the CRTLIB or CRTJRNRCV command from cheekily pinching a
>bit of your ASP, but you can keep an eye on this fairly easily.
>
>An alternative and more flexible approach would be to assign a maximum DASD
>usage for each project and perform a regular analysis of space used. Each
>object on the system can be identified to its project by the library it's in.
>If any project goes over it's maximum then the project leader is responsible
>for reducing it's size. This approach normally requires some kind of sanction
>that can be applied if limits are exceeded and not reduced. This might mean
>buying more DASD and charging the cost to the guilty project, for example.
>
>HTH
>
>Dave Kahn, TCO, Kazakstan
>=========
>
>kahn@tengizchevroil.com   (to November 25)
>dkahn@cix.compulink.co.uk (from November 26)
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---