Utilities and Other Interfaces › Address Space Creation Utility › Install the Utility

Install the Utility

The utility JCL PROC is invoked through the z/OS START command. As parameters, you supply a CA MIM JCL PROC name and any JCL PROC overrides that are typically used with the CA MIM JCL PROC. The general syntax for the utility is as follows:

START PROCASC,,,(parameters)

parameters

Specifies the CA MIM PROC name and any optional overrides that might be specified for the invocation of the CA MIM address space.

Examples:

1. Assume that you activate CA MII using a JCL PROC named MIMDASD. To have the CA MIM Address Space Creation Utility to create the MIMDASD address space as a system address space, do the following.
   1. Customize the PROCASC JCL PROC, rename it to MIMASC, and copy it to an appropriate proclib.
   2. Start the utility. Assume that you usually start MIMDASD as START MIMDASD. If you want to start MIMDASD as a system address space, then enter:

      START MIMASC,,,MIMDASD
      

   The MIMASC task starts and ends very quickly, but an address space named MIMDASD has also started. The MIMDASD address space continues through normal CA MIM initialization and remains active with a Dispatching Priority of x'FF'. This MIMDASD address space is considered a system address space and provides the best possible enqueue service rates.

2. Assume that you want to start MIMDASD as a system address space, but you need to format the checkpoint file, and you want to reuse the existing CA MIM CSA intercepts. To specify optional override parameters, do the following:

   START MIMASC,,,(MIMDASD,REUSE=YES,FORMAT=CHKPT)
   

   If you are running with heavy managed enqueue activity, you will benefit by having the CA MII address space run as a system service address space. The CA MIM Address Space Creation Utility does not provide much benefit for CA MIM address spaces running only the CA MIA or CA MIC components. Therefore, you may want to employ the CA MIM Address Creation Utility for your MIMDASD task, but choose not to use it for your CA MIM Tape or Console management tasks.

   You should code a WLM classification rule to explicitly assign CA MIM to the SYSTEM service class.

Note: For important information on specifying WLM classification rules, see the z/OS MVS Planning: Workload Management guide. An installation may need to explicitly specify CA MIM to one of these service classes in a classification rule, for example, if they want to assign CA MIM to a report class.

When CA MII executes as a system address space, the CA MII address space name does not appear in a z/OS “DISPLAY A,L” command response. This is true of all system address spaces. Any automated operations procedures for CA MII that are dependent upon the “D A,L” command response needs to be changed to use the z/OS “D A,taskname” form of the command. The z/OS “D A,taskname” command response output, where taskname is the CA MII address space name, is not effected by executing CA MII as a system address space. Also note that the MIMASC utility address space is active for only a few seconds while it launches the CA MIM task that you specified on the START command. MIMASC terminates immediately after it has created the desired CA MII address space.