How to Implement CAISDI

This chapter briefly describes the requirements and recommendations for installing and running CAISDI.

Migration to CAISDI/elmds

Beginning with CA Common Services for z/OS Release 14.1, the CAISDI/elmds procedure (CDYFAPI) replaces CAISDI/med (CASDIMED) and CAISDI/els (CASDIELS). If problems arise during the transition, you can run any combination of elmds with med and els. See CAISDI/elmds Backout Procedure.

Consider the following migration issues before starting CAISDI:

• The elmds configuration file (CDYFCNFG) is processed before any other files. If you run either CAISDI/med (CASDIMED) or CAISDI/els (CASDIELS) (not both) as specified by the product suite above, you must specify NO_ELS or NO_MED appropriately in the CAISDI/elmds configuration file.

  The current med procedure CASDIMED allocates DDNAME MEDPARMS for its initialization statements. The current els procedure CASDIELS allocates SYSIN to process its primary initialization statements which can then specify additional data sets for input. The elmds procedure CDYFAPI has DDNAME MEDPARMS for initializing the med support and DDNAME ELSSTART for the primary initialization statements for els support.

  For the existing med parameters referred to as MEDPARMS, copy the existing MEDPARMS used by CASDIMED to a new library and allocate it to DDNAME MEDPARMS in the CDYFAPI procedure.

• On the MED INIT statement, the DEBUGMSG and REUSE parameters are deprecated. A message is issued but it does not cause termination.
• On the MED SERVER statement, the range for the TIMEOUT parameter has been changed from 10 to 3600 seconds to 20 to 180 seconds. The default remains at 30 seconds.
• For the existing els primary initialization statements, all products must copy their DEFAULT and DEFINE statements to a common file allocated to ELSSTART in CDYFAPI. All products are initialized once at the start of CDYFAPI. Unlike the existing els interface, it is not possible to remove or define a product after elmds has been started.
• The EVENTLIB data sets and members can remain as they are currently defined except that PRODNAME on the SETUP statement is limited to 100 characters.
• &PARM is no longer supported for els. Update any configuration files appropriately.
• On the ELS DEFAULTS and DEFINE statement, parameters USD_ID and USD_PW are deprecated. A message is issued but it does not cause termination. Use the URL_SYMBOL if necessary and see the CAISDI/soap Server documentation regarding URL_SYMBOL and associated user IDs and passwords. The configuration data set is no longer needed to hold Service Desk user IDs and passwords.
• The elmds interface provides an optional initialization statement (SYNTAX_CHECK_ONLY in CDYFCNFG) for elmds to verify syntax in the various configuration files and then terminate. With this parameter the elmds address space can be started to verify syntax changes, even if there is another instance active.
• The elmds log (CDYFLOG) contains messages and potentially trace information. CDYFLOG is spun automatically based on parameters in CDYFCNFG, or through operator commands.
• Messages for els and med are now written to CDYFLOG and not issued as a WTO in the application address space. New message IDs and text are used.
• If CASDIMED is run using the same MEDNAME as specified in the elmds MEDPARMS, then elmds must be started with either a different MEDNAME or with NO_MED in CDYFCNFG.
• If either the CASDIELS or CASDIMED procedure must be run, then elmds must first be started with NO_ELS or NO_MED (respectively) in CDYFCNFG.

  If both NO_MED and NO_ELS are specified in CDYFCNFG, CDYFAPI can be terminated after starting CASDIMED and CASDIELS.

• The string &SYSEDATE is a system variable that can appear in the els eventlib SUMMARY or DESCRIPTION sections. The variable is substituted with the current date in the form dd/mmm/yyyy. The support in this product is for English only. If another language is required, either use a user variable or open an enhancement request (DAR) requesting a change.