Need help with command line compile.

In article <CJHo8r.yAn@alert.com> dbn@alert.com writes: ... >We are developing a system to archive historical data from our ... >* An initial capacity of 34GB with growth rates of 10GB per year. ... >We are considering building one or more databases with a dbspace per >platter [in cooked filesystems] in a multi-drive optical jukebox. The way I understand Online/Optical, the optical disks are only used for BLOB storage as BLOBspaces. If your database is like most, your data is not in BLOBs. Therefore, your optical devices will have to be rewritable, since, even if your data is only INSERTed once, the index and reserved pages are rewritten many times. With the current, relatively low cost, you might want to reconsider regular magnetic disks. Informix will have no problem with that size database, as long as the data is not in one large table. We run a decision support database on magnetic disk that is 40GB in size and have 10-30 users (including batch posting) running against it at any given time. You are right about having one DBspace or chunk per platter. DBspaces can span several chunks/platters, but there is no reason for chunks to span platters UNLESS your platters are small (<1.5GB). Current levels of Informix Online (anything less than 6.0) are limited to about 40-50 chunks, so you want chunks at least 1GB to get to the size you want to get to. Also, there is a limit to chunk size at 2 GB. ----------------------------------------------------------------- Jim Burks jburks@promus.com The Promus Companies Memphis, Tennessee, USA