Preparing for Installation › Component Installation Requirements › CAISDI Requirements

CAISDI Requirements

CAISDI consists of the following individual components: soap, med, and els. In the past, these components were installed separately. Now, they are installed as one product.

Beginning with CA Common Services for z/OS Release 14.1, CAISDI/elmds has been added as a new component. CAISDI/elmds combines med and els functionality and runs in a permanent address space. CAISDI/elmds can be used instead of one or both of the individual med and els components.

CAISDI has the following installation requirements for the soap, els, and med individual components:

Note: CAISDI/elmds specific requirements are explicitly noted.

• An IBM supported z/OS version. (Also for elmds.)
• Use a region size of 4 MB or larger.
• CAISDI/med uses approximately 24 KB of the extended common service area (ECSA) for loading common storage resident services and intercepts.

  Some types of service calls use approximately 100 KB of ECSA while the service call is outstanding. However, CAISDI makes extensive use of cross-memory services to avoid the need for common storage areas.

• CAISDI/els uses varying amounts of CSA depending on which products use this component. (Also for elmds.)

  The CAISDI/els Interface Controller reports the ECSA usage for each product separately.

• CAI.CAW0OPTN contains the CAISDI initialization statements for all CAISDI components. If multiple z/OS systems share the parameter data set, the data set must reside on a shared DASD volume.
• CAI.CAIEVENT contains the event definitions for the CAISDI/els component. The CA Technologies products that use this interface provide the event members.
• CAISDI provides the interface to CA Service Desk over a network connection using TCP/IP. Be sure TCP/IP is up and running on at least one z/OS system. The CAISDI/soap client installation occurs there. (Also for elmds.)
• Define the UNIX System Services profile to UID 0 or a SUPERUSER (BPX.SUPERUSER) for the user ID for the CAISDI/soap Client address space. Also for elmds.
• Verify that CA Service Desk is installed and properly configured. (Also for elmds.)
• Some products generate Service Desk Request Description content in HTML format.

By default, CA Service Desk renders embedded HTML directives in the request description field. This capability can be deactivated. To render the request text properly, your CA Service Desk server must support HTML rendering. Ask your CA Service Desk administrator to perform this task.

This task involves customizing the detail_cr.htmpl form to add keeptags and keeplinks support.

Note: For more information about the installation and configuration of CA Service Desk, see the CA Service Desk Installation Guide.

The minimum storage requirements for each CAISDI distribution library. This list 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 an LRECL of 80. This change was made for both the IBM SMP/E packaging standards, and the CA Technologies packaging standards. Specifying BLKSIZE=0 allows your system to allocate the most efficient block size for these data sets.