Determining storage needs for the object store

Object store records are not permanent. They are deleted when they are no longer needed. Unlike the ICL, the object store does not grow beyond a certain point, unless there is a sharp increase in certificate request activity. Typically, a certificate request record is less than twice the size of the ICL record. Assume that one object store record and its companion posting record occupy a total of 2560 bytes of storage. With a space allocation of CYL(3,1), the data set can have a maximum of 125 cylinders on a single 3390 volume for a total size of 105 MB, which would hold at least 41,000 concurrent certificate requests. If multiple volume support is used, you can double this amount.

If your anticipated needs differ greatly from the preceding value, you need to adjust the space allocation parameters CYL(3,1) on the DEFINE CLUSTER statement for the object store. (This is the first DEFINE CLUSTER statement in IKYCVSAM. See IKYCVSAM for a code sample of this file.) You might also want to proportionally adjust the space allocation parameters TRK(5,1) on the DEFINE ALTERNATEINDEX statements for the object store. These are defined in the DEFALTDX job step. (Their names contain the ost qualifier.)

If you set the RemoveInactiveReqs and RemoveCompletedReqs parameters in the configuration file to 0d, certificate request records are not deleted and you should adjust the space allocation accordingly.