What does Imbed option do while defining a KSDS

Madhu Kashyap · New User Joined: 19 Jan 2006 Posts: 19

Hi ,

Can anyone please tell me what does Imbed option do while defining a KSDS?

senthils · Posted: Thu Jan 19, 2006 2:48 pm

Without replicate and Imbed, data CAs and CIs can be stored in different places on the disk from the index. This means that several I/Os are required for each access.

With Imbed and noreplicate, each data CA has its sequence set record at the front of the CA. If the CASZ is 1 cylinder then the sequence set is maintained on the 1st track of the cylinder. If the CASZ is less than 1 cylinder then one track is added to the CASZ. Thus, it costs 1 track per CA as the sequence set is written around the track as often as possible. Rotational delay is reduced as the r/w arm is placed above the sequence set and data. However, index updates cause an overhead as each copy of the sequence set has to be updated. Sequential processing benefits immensely from Imbed.

With replicate and noimbed, all data CAs and indexes are separate. Each higher level index is written as often as possible on a track. This option uses a lot of extra space and also requires extra I/O for index updates. If using this option the index should be allocated in cylinders and imbed should also be used. Since sequential processing only uses the sequence set, then replicate is of no value for sequential processing.

Rupesh.Kothari · Member of the Month Joined: 27 Apr 2005 Posts: 463

HI,

Madhu Kashyap · New User Joined: 19 Jan 2006 Posts: 19

Thanks for answering my query.

nagendrat · New User Joined: 18 Jan 2006 Posts: 5

The IMBED option places the index component's sequence set records in the space with the data component and causes the sequence set record to be duplicated as many times as possible on its track. This means that the first track of each control area will not be available for user data