Steps for customizing base z/OS functions on the other systems in the sysplex

Before you begin

You must have the WebSphere Application Server for z/OS product code installed through SMP/E and have created copies of the product sample files.

Why and when to perform this task

Repeat the same customizations to base z/OS functions that you did for your initial installation and customization of the Application Server. The steps are repeated here for convenience.

Note: The following steps assume that your default Application Server data set high-level qualifier (hlq) is "BBO". If it is not, modify the examples to use your specified hlq.

Perform the following steps to change the base system:

Steps for this task

  1. Change SCHEDxx to include the statements from the BBOSCHED sample file you ran in the customization dialog.
  2. APF-authorize the BBO.SBBOLOAD, BBO.SBBOLD2, and BBO.SBBOLPA data sets.

    Example: Your PROGxx PARMLIB member could include:

    
    
    APF FORMAT(DYNAMIC)                                                     
    /*********************************************************************/ 
    /* BOSS LOCAL DATASETS                                               */ 
    /*********************************************************************/ 
    APF ADD                                                                 
        DSNAME(BBO.SBBOLOAD)                                     
        VOLUME(vvvvvv)                                                      
    APF ADD                                                                 
        DSNAME(BBO.SBBOLD2)                                      
    
    
        VOLUME(vvvvvv)                                                      
    APF ADD                                                                 
        DSNAME(BBO.SBBOLPA)                                      
        VOLUME(vvvvvv)                                                      
    
    
    where vvvvvv is your volume identifier.

  3. Ensure that the Language Environment data set, SCEERUN, and the DB2 data set, SDSNLOAD, are authorized.
  4. Do not APF-authorize BBO.SBBOULIB or BBO. SBBOMIG, because they should run under the authority of the client user.
  5. Place Application Server modules.
    Use the following table to place Application Server modules:
    Placing modules in LPA or link list
    Modules Notes
    BBO.SBBOLPA Load all members into the LPA.
    BBO.SBBOLOAD We recommend you dynamically load all members into the LPA. If your virtual storage is constrained, place the members in the link list.
    BBO.SBBOMIG You can put members into the link list or LPA.
    BBO.SBBOLD2 Do not put members from SBBOLD2 in the LPA. Place these members in the link list.
    BBO.SBBOULIB Do not place these members in either the LPA or link list.

    Rule: These data sets are PDSEs and cannot be added to members in LPALSTxx or IEALPAxx.

    Recommendation: For automation, if you want to ensure the Application Server modules are loaded into dynamic LPA and available after an IPL, create a new PROGxx member with the SETPROG LPA commands and invoke the PROGxx member from PARMLIB COMMNDxx.

    Example:

    
    
    SETPROG LPA,ADD,MASK=*,DSNAME=
    BBO.
    SBBOLOAD
    SETPROG LPA,ADD,MASK=*,DSNAME=
    BBO.
    SBBOLPA
    
    
    • Change "BBO" if it is not the high-level qualifier for your Application Server data sets.
    • If using SETPROG on a running system, be sure to purge modules with the same name as those from BBO.SBBOLPA, BBO.SBBOLOAD, or BBO.SBBOMIG that are already in the LPA.



  6. (Optional)   If you used a PROGxx file for APF authorizations or the LPA, be sure to issue:
    
    
    SET PROG=xx
    
    
  7. (Optional)   Make sure all the BBO.* data sets are cataloged.
    While not required, this is highly recommended.
  8. Update your SYS1.PARMLIB(BLSCUSER) member with the IPCS models supplied by member BBOIPCSP.
    For details in BLSCUSER, see z/OS MVS IPCS User's Guide.
  9. (Optional)   Start SMF recording.
    If you want to start SMF recording to collect system and job-related information on the WebSphere Application Server system:
    1. Edit the SMFPRMxx parmlib member.
      1. Insert an 'ACTIVE' statement to indicate SMF recording.
      2. Insert a SYS statement to indicate the types of SMF records you want the system to create.

        Example: Use SYS(TYPE(120:120)) to select type 120 records only. Keep the number of selected record types small, to minimize the performance impact.

    2. To start writing records to DASD, issue the following command:
      
      
      t smf=xx
      
      
      
      Where xx is the suffix of the SMF parmlib member (SMFPRMxx). For more information about the SMF parmlib member, see z/OS MVS System Management Facilities (SMF).

      When you activate writing to DASD, the data is recorded in a data set (specified in SMFPRMxx).




Searchable topic ID:   trunothbase
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/trun_othbase.html

Library | Support | Terms of Use | Feedback