3. Installation › 3.3 Define Database Complex › 3.3.6 Set Up the CA MICS ISPF Environment

3.3.6 Set Up the CA MICS ISPF Environment

 
 This section discusses alternatives for setting up the ISPF
 environment at your installation to accommodate the CA MICS
 online facilities.
 
   *********************************************************
   *  Consult the System Requirements chapter of the       *
   *  CA MICS System Administrator Guide for information   *
   *  regarding supported levels of ISPF and recommended   *
   *  maintenance levels.                                  *
   *********************************************************
 
 DYNAMIC ALLOCATION REQUIREMENTS
 
 One of the critical options in a TSO LOGON procedure is the
 maximum number of concurrent dynamic allocations (DYNAMNBR)
 allowed to a TSO user.  We recommend you allow at least 100
 dynamic allocations.  We selected 100 because there is no way
 to predict accurately  the number of concurrent dynamic
 allocations that might exist.
 
 For example, while the TSO user might be performing limited
 CA MICS functions on one side of the ISPF split screen, the
 other side of the split screen could be involved in an
 application that requires many allocations.
 Also, dynamic allocation requirements for CA MICS
 applications fluctuate from one site to another and from one
 user to another.  For example, a MICF inquiry requires a
 different number of allocations that are based on its complexity.  If
 the inquiry references multiple CA MICS databases, then the
 number of allocations increases as compared to an inquiry
 that references a single CA MICS database.
 
 Experience dictates the DYNAMNBR best suited for your
 site.  There is a memory overhead that is associated with the
 DYNAMNBR, so your objective is to select a value that
 satisfies the needs of your users while not being excessively
 large.

 CA MICS AND THE SASCP COMMAND PROCESSOR
 
 CA MICS uses ISPF dialog manager services under the control
 of the SASCP command processor.  The ISPF system programmer
 uses the ISPTCM table during the installation and
 customization of ISPF to define the characteristics of
 commands that operate under ISPF, such as whether a
 command processor can issue ISPF dialog manager services.
 Coordinate with your ISPF system programmer about the
 following points to ensure that CA MICS can operate at your
 site.
 
 The ISPTCM table is used to define characteristics about
 commands that run under ISPF.  The characteristics for
 the SASCP command processor can be explicitly coded
 (ISPMTCM ENTRY ...) or assigned by default.  To verify that
 your site's ISPTCM table allows the SASCP command processor
 to issue ISPF dialog manager services, review and, if
 necessary, execute the steps that follow.
 
 To determine if the characteristics for the SASCP command
 processor have been explicitly coded, look in the ISPTCM
 table for the following line:
 
 ISPMTCM ENTRY ENTNAME=SASCP,FLAG=xx...
 
 o If the line is present and the optional FLAG=xx keyword is
   specified, verify that the required "4" bit is in the
   first digit.  Values that have the "4" bit on are "4x",
   "5x", "6x", "7x", "Cx", "Dx", "Ex", and "Fx".  If it is
   not, correct the ISPTCM table and reassemble it.
 
 o If the line is present and the optional FLAG=xx keyword is
   NOT specified, the keyword takes on the default value
   (FLAG=02) which does not enable the SASCP command processor
   to use ISPF dialog manager services.  Correct the ISPTCM
   table as described in the preceding paragraph and reassemble
   it.
 
 o If the SASCP command processor is not explicitly defined
   (there is not an ISPMTCM ENTRY ENTNAME=SASCP,FLAG=xx...
   line in the ISPTCM table), inspect the header entry in the
   ISPTCM table.  The syntax of the header entry is:
 
   ISPMTCM HEADER DFFLAG=xx,...
 
   o If the optional DFFLAG=xx keyword is not specified, the
     keyword takes on the default value (DFFLAG=61) which
     enables the SASCP command processor to use ISPF dialog
     manager services.  No further work is required.

   o If the optional DFFLAG=xx keyword is specified, verify that
     it has the required "4" bit on in the first digit.
     Values that have the "4" bit on are "4x", "5x", "6x",
     "7x", "Cx", "Dx", "Ex", and "Fx".  If it is not, you must
     either:
 
     - change the header entry (ISPMTCM HEADER DFFLAG=xx,...)
       to specify the optional DFFLAG=xx keyword, where xx is
       either "4x", "5x", "6x", "7x", "Cx", "Dx", "Ex", or
       "Fx", and reassemble the table
 
       or
 
     - code an explicit entry for the SASCP command processor
       (ISPMTCM ENTRY ENTNAME=SASCP,FLAG=xx...), set the
       optional FLAG=xx keyword to one of the values discussed,
       and reassemble the table.

 INSTALLING THE CA MICS WORKSTATION FACILITY (MWF)
 
 Adding the CA MICS online facilities to your ISPF environment
 is a two-step process.  First, you add a CA MICS
 option to one of your installation's ISPF menus to invoke a
 CLIST.  Second you create this CLIST which allocates CA MICS
 libraries, connects the libraries to the ISPF environment
 with the ISPF library definition (LIBDEF) service, and
 invokes the CA MICS Workstation Facility.  This
 approach minimizes modifications to your installation's
 ISPF environment and we avoid conflicts between CA MICS
 online facilities and your other ISPF applications.  CA MICS
 libraries are allocated ONLY when needed and ISPF searches
 CA MICS libraries ONLY when processing CA MICS.
 
 Each installation's ISPF environment and requirements are
 unique.  To meet your unique requirements, CA MICS provides
 two sample MWF CLISTs you can use as a starting point for
 creating your own unique MWF CLIST.  The JCLGEN0 job
 generates the sample CLISTs, MWFSMPL1 and MWFSMPL2, into
 sharedprefix.MICS.CLIST.
 
 The following sections illustrate how to add CA MICS online
 facilities to your ISPF environment.  The first section is an
 overview of the ISPF LIBDEF service and related issues.  The
 second section is a sample LIBDEF implementation.  The third
 section describes an alternative implementation that may be
 useful for initial CA MICS testing.
 
 The samples that follow assume familiarity with ISPF Dialog
 Manager Services.  The samples that are shown in this guide use CA MICS
 sharedprefix libraries and ISPF default library names.  Do
 not use these samples without verifying these library names;
 your installation might not use the same library names.
 Note: The generated samples in sharedprefix.MICS.CLIST
 reflect the library name definitions that you specified in
 sharedprefix.MICS.PARMS(JCLDEFC).
 
 The following sections illustrate:
 
     1 - ISPF LIBDEF Service Overview
     2 - Sample CA MICS Online Facilities Implementation
     3 - Alternative Online Facilities Implementation