|
A WRKDSKSTS, followed by F11=Display storage use Would show you if there is more than one ASP. WRKDOMSVR 12=Work object links Then do a WRKLNK 8=Display attributes For each directory /GDISYS01 /GDISYS01/NOTES /GDISYS01/NOTES/DATA And see if they are assigned to one of these other ASPs. Object . . . . . . : /GDISYS01 Type . . . . . . . . . . . . . . . . . : DIR Owner . . . . . . . . . . . . . . . . : QNOTES System object is on . . . . . . . . . : Local Auxiliary storage pool . . . . . . . . : 1 Object overflowed . . . . . . . . . : No But if it isn't the ASP then I, too, would like to know how he figures it's all on these 6 disks. There are a few reasons for multiple ASP's, none of which we use. 1 - Segregate applications by disk type. For instance, keep Notes on one asp to a - Use older drives, or on large arms with few arms, and let the "real" stuff have the speed. b - Limit the size of all the data that Notes can use. Probably better served by doing CHGUSRPRF USRPRF(QNOTES) MAXSTG(...) 2 - Keep journal receivers on a different ASP. To a - speed performance - keeping the writes for data not beating the arms writing to the receiver b - if the disk drive for data fails you can restore that and reapply your journal receivers that should not be affected. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.