Using IWMARIN0 (example of steps for defining an application environment)

Before you begin

Workload management must be running in goal mode, and you must have access to a WLM definition, either saved in a WLM definition data set, or active in the WLM couple data set. The user of IWMARIN0 must have update access to the RACF FACILITY class profile MVSADMIN.WLM.POLICY. Perform the following steps to create the BBOC001 application environment.

Steps for this task

  1. Open the main panel by issuing IWMARIN0.
    Either load a WLM goal mode definition from a WLM definition data set, or extract a working goal mode definition from the WLM couple data set. Then choose option 9:
     File Utilities Notes Options Help ---------------------------
     Functionality LEVEL003     Definition Menu            WLM Appl LEVEL004 
    Command ===> ______________________________________________________________ 
    Definition data set . . : CB.MYCB.WLM
    Definition name . . . . .CB390 (Required) 
    Description . . . . . . . WLMSetup for WebSphere Application Server for z/OS 
    Select one of the following options. . . . . 9__ 1. Policies 
                                                     2. Workloads 
                                                     3. Resource Groups 
                                                     4. Service Classes 
                                                     5. Classification Groups 
                                                     6. Classification Rules 
                                                     7. Report Classes 
                                                     8. Service Coefficients/Options 
                                                     9. Application Environments 
                                                     10. Scheduling Environments 
    
  2. Fill in the field on the next panel as shown:
    Application-Environment Notes Options Help ---------------------------------------------------
    					 Create an Application Environment 
    Command ===> ______________________________________________________________ 
    Application Environment . . . BBOC001_________________________ 
    Required Description . . . . . . . . .WebSphere Application Server for z/OS IVT server___ 
    Subsystem Type . . . . . . . .CB__ 
    Required Procedure Name . . . . . . . .BBO5ASR 
    Start Parameters . . . . . . .JOBNAME=&IWMSSNM.S,ENV=CELL1.&SYSNAME..  
                                          &IWMSSNM_________________________________
                                           _________________________________ 
    Limit on starting server address spaces for a subsystem instance: 
    2        1. No limit 
             2. Single address space per system 
             3. Single address space per sysplex 
                .---------------------------------------------------------------------.
                | Selection List empty. Define an application environment. (IWMAM600) | 
                .---------------------------------------------------------------------.
    

    When filling out the previous panel, follow these guidelines:

    • The Application Environment name is either the ClusterTransitionName (if the server is not clustered) or the cluster short name (if the server is clustered).
    • The recommended JOBNAME value is &IWMSSNM.S. For example, if the server short name is BBOS001, then set JOBNAME=BBOS001S.
    • ENV=... must be of form cell_short_name.node_short_name.server_short_name
      • In a base server, the location service daemon default is that both cell_short_name and node_short_name are the same as system_name.
      • In a Network Deployment server, the location service daemon default is that both cell_short_name and node_short_name are the same as sysplex_name. As you add base server nodes to the deployment manager server's cell, you have to update the ENV= parameter of each in the WLM application environment definition. The reason for this change is because a base server node assumes the cell name of the deployment manager server once the base server node is added to the deployment manager server's cell.
    • Change CELL1 to your cell_short_name and &SYSNAME to your node_short_name as needed. Otherwise, the defaults will be assumed.
    • The value of the &IWMSSNM variable (defined by WLM) is the server short name.

  3. Save the application environment.
    The following panel appears:
    Application-Environment Notes Options Help 
    -------------------------------------------------------------------------- 
             Application Environment Selection List Row 1 to 12 of 12 
    Command ===> ______________________________________________________________ 
    Action Codes: 1=Create, 2=Copy, 3=Modify, 4=Browse, 5=Print, 6=Delete,
         /=Menu Bar 
    Action  Application Environment  Name           Description 
        __ BBOC001                                  WebSphere Application Server for z/OS IVT server 
    ******************************* Bottom of data ******************************** 
    
  4. From the Utilities menu, select Install definition.
  5. From the Utilities menu, select Activate service policy.
  6. From the File menu, select Exit.

Results

You are done when BBOC001 has an application environment.



Searchable topic ID:   tinswlmex
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tins_wlmex.html

Library | Support | Terms of Use | Feedback