CA Global SubSystem Configuration › Install the IMOD Editor

Install the IMOD Editor

The IMOD editor is an ISPF-based facility that lets you write, edit, compile, and test IMODs. Installation of the editor requires the following:

• Accessibility to the CA‑GSS Load Library, CAW0LOAD by the TSO user. This is accomplished through the system LINK LIST or by providing the appropriate STEPLIB statement.
• Accessibility from the CA‑GSS ISPF-related libraries (panel, message, and CLIST) to the TSO user. This is accomplished through dynamic allocation when the CA‑GSS editor program (SRVEDIT) is called.
• Construction of a parameter list, based on information provided to the CA‑GSS address space in the ISETS member of the CAW0OPTN data set.
• Addition of appropriate ISPF menu entries to permit invocation of the IMOD editor from an ISPF panel, if desired.

To install the IMOD editor

1. Review enqueue requirements.
   • CA‑GSS observes strict enqueue compliance to ensure that ISETs can be shared across multiple systems without risk of corruption. To ensure proper handling of enqueues, you must notify your enqueue management software about the CA‑GSS enqueues.
   • During update operations, an exclusive enqueue is obtained for qname IPGMGREX and rname F.dsn, where dsn is the 44‑byte cluster name, right padded with blanks.
   • During edit operations, an exclusive enqueue is obtained for qname IPGMGREX and rname P.imod.dsn, where imod is the 16‑byte IMOD name, right padded with blanks, and dsn is the 44‑byte cluster name, right padded with blanks.
   • All enqueues have a scope of SYSTEMS.
2. Construct the parameter list and update the CA-GSS RUNPARMS.

   The entry panel of the IMOD editor lists all ISETs (IMOD data sets) that are available for use. Each entry in this list includes the ISET name, a description, and the subsystem ID of the ISERVE address space, if any, which is linked with the ISET.

   Consider the following:

   • Only one data set may be referred to by a particular ISET name, although multiple ISET names may refer to a single data set.
   • If dynamic reloading or execution of IMODs is to be permitted, the ISET and DSNAME references must be identical to those appearing on the ISET statements defined to the CA‑GSS address space. You can ensure that the references will be identical by using the CAW0OPTN RUNPARM, ISETS, and EDITPARM members.
   • If UNIT=VIO is not valid for data set allocation in your data center, you must include a VIOUNIT parameter before the IMOD compiler can be executed.
   • The parameter list is referenced through the member name value that you specify on the EDITOR MEMBER statement. You should specify the EDITPARM member of the CAW0OPTN data set for this value.
   • A sample parameter list is provided in the ISETS member of the CAW0OPTN data set. You can customize this member, adding ISET definitions appropriate for your own environment. You must select values for the lowercase parameters. The EDITPARM member referenced by the EDITOR MEMBER statement contains an INCLUDE statement for the ISETS member. This ensures that the CA‑GSS task and the SRVEDIT program reference identical ISET lists.

     Note: For more information about the format of ISET initialization parameter statements, see the Reference Guide.

3. Modify the ISPF menu panel.

   You can invoke the IMOD editor by issuing the GSSEDIT command, or you can invoke the IMOD editor from an ISPF menu panel. The GSSEDIT command is a REXX EXEC that is contained in the distribution CLIST data set.

   To invoke the IMOD editor from ISPF, locate the appropriate ISPF menu panel and add the following menu items to the panel and in the PROC section:

   ISRV,'PGM(SRVEDIT) NEWAPPL(nnnn) NOCHECK'
   

   where nnnn is an arbitrary four-character ISPF application ID (such as ISRV).

Important! Use caution when modifying the ISPF primary menu panel. An error can prevent you from using ISPF. Always keep a backup member and a tested procedure that is independent of ISPF.