Modifying MVS image variables

To modify variables that are specific to an OS/390 or z/OS image, you can modify the member from which active parameters are loaded.

Before you begin

Before you can modify the variables, you must determine the location from which the parameters are loaded.

To determine the location from which the parameters are loaded

1. Using your normal method to review SYSOUT, review the active XIMACM started task.

   Alternatively, you can review the XIMACM procedure in your system PROCLIB library.

2. Locate the partitioned data set (PDS) that is allocated to the XIMPARM ddname.
3. On the //EXEC PGM=XIMMAIN statement, locate the PARM option.

   A keyword specifies SUFFIX=xxxx.

4. To determine the member name, append the SUFFIX to XIM.

   For example, if SUFFIX=PARM, the active parameters are loaded from the XIMPARM member, as shown in the following line of JCL:

   //XIMPARM DD DSN=RCDTJP.XIM.UDBPARM(XIMPARM)

To modify the variables

1. Edit the XIM xxxx member in the data set that is referenced by the //XIMPARM DD statement.

   In the example shown in XIMACMI member, the name of the member is XIMACMI.

2. Modify the INITIATORS variable.

   In the example shown in XIMACMI member, the member contains global variables and MVS image variables. The variables in the MVS image variables section override the same variables in the global variable section. For example, the default value for the global number of initiators is 8. However, for the DB2A subsystem ID, the number of initiators is 16.

   Important

   Typically, you should not modify other variables unless BMC Support directs you to do so. However, you must ensure that the values for the XIM_GROUP and XCF_GROUP parameters are unique for each version if both of the following conditions exist:

   • You have installed the worklist parallelism feature of the BMC Database Administration for Db2 solution in one environment (for example, production).

   • You later install a new version of the solution in a different environment (for example, test).

   In addition, the XIM group name that is specified on the Execution Worklist Parallelism Options panel must match the name of the group.

   For information about specifying the group name, see the ALTER and CHANGE MANAGER documentation .

   *   XIM STARTUP PARM FOR CHANGE MANAGER FOR DB2
   * 
   * 
   *   SYNTAX RULES: 
   *   USE COL 1 - 71
   *   USE ONE PARAMETER PER STATEMENT 
   *   DO NOT CONTINUE A PARM ONTO A SECOND LINE
   *   ANYTHING FOLLOWING A PARM AND ITS VALUE IS A COMMENT
   *   THE EQUAL SIGN IS THE REQUIRED DELIMITER
   *   SPACES TO THE LEFT AND RIGHT OF THE = ARE PERMITTED 
   *   BLANK LINES AND LINES BEGINNING WITH * ARE IGNORED 
   * *************************************************************** 
   *   GLOBAL VARIABLE SECTION         ****************** 
       XIM_GROUP=XIMACM
       XCF_GROUP=XIMACMCF 
       INITIATORS=8
       INIT_PROC=XIMACMI        *  PROC FOR TARGET INITIATORS
   * 
   * RESPONSE TIMEOUT INTERVAL (SECONDS) 
       RESPONSE_TIMEOUT=90      *  RESPONSE TIME OUT (SECONDS) 
       WORKLOAD_REFRESH=1       *  WORKLOAD REFRESH INTERVAL (MINUTES)
       ENVIRONMENT_TIMER=60     *  ENVIRONMENT TIMER INTERVAL (SECONDS) 
   * 
   * LOCAL MVS IMAGE VARIABLES (COMMENTED TO SHOW AS AN EXAMPLE)
   *  DO DB2A 
   *   INITIATORS=16            *  # OF INITIATORS AT STARTUP 
   *  END 
   *

3. Save the changes to the member.
4. Inactivate XIM by issuing the QUIESCE command: /F XIMACM,QUIESCE
5. Verify the status of XIM by issuing the STATUS command: /F XIMACM,STATUS
6. Shut down XIM by issuing the SHUTDOWN command: /F XIMACM,SHUTDOWN
7. Start XIM by issuing the start command: /S XIMACM

   The new instance of XIMACM uses the new parameters.

8. To verify the new parameters, issue the STATUS command: /F XIMACM,STATUS
9. Review the values that XIM displays in the system log.
10. If you use data sharing, repeat Step 4 through Step 9 for each OS/390 or z/OS image.