onspaces -a: Add a chunk to a dbspace or blobspace

>>-onspaces -a--+-dbspace---+--+- -p--pathname--------------+--->
                '-blobspace-'  |                        (1) |   
                               '- -p--\--\--.--\--drive-----'   

>-- -o--offset-- -s--size--------------------------------------->

>--+- -m--pathname offset--------------+-----------------------><
   |                               (1) |   
   '- -m--\--\--.--\--drive offset-----'

Use onspaces -a to add a chunk to a dbspace or blobspace.


Element	Purpose	Key considerations
-a	Indicates that a chunk is to be added	You can have up to 32766 chunks in an instance. You can put all those chunks in one storage space, or spread them among multiple storage spaces.
*drive*	Specifies the Windows™ drive to allocate as unbuffered disk space The format can be either *\\.\<drive>, where drive* is the drive letter assigned to a disk partition, or *\\.\PhysicalDrive<number>, where PhysicalDrive* is a constant value and *number* is the physical drive number.	For more information, see Allocating raw disk space on Windows. Example: \\.\F: For path name syntax, see your operating-system documentation.
-m *pathname offset*	Specifies an optional path name and offset to the chunk that mirrors the new chunk Also see the entries for pathname and offset in this table.	For more information, see Adding a chunk to a dbspace or blobspace.
-o *offset*	After the -a option, offset indicates, in kilobytes, the offset into the disk partition or into the device to reach the initial chunk of the new blobspace or dbspace	Unsigned integer. The starting offset must be equal to or greater than 0. The starting offset plus the chunk size cannot exceed the maximum chunk size. The maximum offset is 4 terabytes. For more information, see Allocating raw disk space on UNIX.
-p *pathname*	Indicates the disk partition or unbuffered device of the initial chunk of the blobspace or dbspace that you are adding The chunk must be an existing unbuffered device or buffered file.	The chunk path name can be up to 256 bytes. When you specify a path name, you can use either a full path name or a relative path name. However, if you use a relative path name, it must be relative to the directory that was the current directory when you initialized the database server. UNIX™ example (unbuffered device): /dev/rdsk/c0t3d0s4 UNIX example (buffered device): /ix/ids9.2/db1chunk Windows example: c:\Ifmxdata\ol_icecream\mychunk1.dat For path name syntax, see your operating-system documentation.
-s *size*	Indicates, in kilobytes, the size of the new blobspace or dbspace chunk	Unsigned integer. The size must be equal to or greater than 1000 kilobytes and a multiple of the page size. The starting offset plus the chunk size cannot exceed the maximum chunk size. The maximum offset is 4 terabytes.
*blobspace*	Names the blobspace to which you are adding a chunk	See Adding a chunk to a dbspace or blobspace. Syntax must conform to the Identifier.
*dbspace*	Names the dbspace to which you are adding a chunk	See Adding a chunk to a dbspace or blobspace. Syntax must conform to the Identifier.

This command has an equivalent SQL administration API function.