Preparing for Installation › Storage Requirements › Component Installation Requirements › Easytrieve Service Requirements

Easytrieve Service Requirements

Easytrieve Service has the following installation requirements:

• An IBM supported z/OS version.
• Easytrieve Service requires CA Sort for z/OS, IBM DF/Sort, or a compatible product with the module name SORT.
• The Easytrieve Service provided in CA Common Services is not the full-featured Easytrieve product.
• SMP/E prevents installation of CA Common Services Easytrieve into the same CSI where the full-featured Easytrieve product is already installed.
• New data set naming standards have been implemented starting with the CA Common Services r12 version of Easytrieve 6.4.

If you have the full-featured Easytrieve r6.4 product or any lower version of Easytrieve already installed at your site, install the Easytrieve Service provided with this release of CA Common Services into an SMP CSI where Easytrieve is not already installed. This release of Easytrieve must be installed into SMP Distribution and Target libraries that are different from your existing Easytrieve installation. This is necessary because the module names are the same for the two products.

If after installing the Easytrieve supplied with this release of CA Common Services, you have both a full-featured Easytrieve and a CA Common Services Easytrieve product installed, continue to use your full-featured Easytrieve for production jobs and CA Common Services Easytrieve for jobs provided by the other CA Technologies products that use the Easytrieve Service. This is necessary because the Easytrieve Service provided in CA Common Services is not the full-featured Easytrieve product, and this may affect your production Easytrieve jobs. Also, your production jobs may encounter some of the issues that can exist when moving from the 24-bit version of Easytrieve, (pre-r6.4), to the 31-bit version, (r6.4).

The following lists the minimum storage requirements for each Easytrieve distribution library and does not necessarily represent the actual distribution library allocation that is provided during the installation. Data set allocation JCL and (MSM) XML contains a block size of 0 for FB data sets with a LRECL of 80. This change was made in order to follow both IBM’s SMP/E packaging standards, and CA’s packaging standards. Specifying BLKSIZE=0 will allow your system to choose the most efficient block size for these data sets.