|
How about a process that would run periodically to remove members for deleted users or members that have not been accessed in x number of days? Joe Giusto II Patuxent Publishing Company 10750 Little Patuxent Parkway Columbia, MD 21044 mailto:JGiusto@patuxent.com <mailto:jgiusto@patuxent.com> http://www.lifegoeson.com <http://lifegoeson.com> -----Original Message----- From: Graap, Ken [SMTP:keg@exchange.gasco.com] Sent: Friday, June 09, 2000 4:30 PM To: 'Midrange' Subject: This way or that? Question - We have a process that adds a member (member name=device name) to a file which is then used as a work file for the current job. Once a member has been added it is never cleared or removed. At any time there may be as many as 500 members in this file and each member may contain several thousand records (1,000 - 50,000). There are also several logical views defined over this file. The first view has 6 formats and three other views have one each. So at any one time there can be up to 2000 indexes all defined with Access Path Maint *IMMED. When everything is added up, this 'work file' takes up 259MB of disk space for data and 814MB of disk space for indexes. A total of over 1GB. The developer who designed this process says that he doesn't remove these file members when a user signs off in order to avoid the overhead of adding a member each day when a user starts an application session. If you were designing this application to optimize the use of system resources (disk utilization, program performance, backup recovery etc) would you remove these work files daily and add new members when needed or would you leave the work files in place as we are doing? I'm looking forward to all your thoughts.... Kenneth **************************************** Kenneth E. Graap IBM Certified Specialist AS/400 Professional Network Administrator NW Natural (Gas Services) keg@nwnatural.com Phone: 503-226-4211 x5537 FAX: 603-849-0591 **************************************** +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.