WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: z/OS

             Personalize the table of contents and search results
This topic applies only on the z/OS operating system.

Customizing base z/OS functions on the other systems in a sysplex

Some z/OS system functions, like the Language Environment (LE) and DB2, must be customized to properly interface with the server runtime. During the server runtime installation process, you use the customization dialogs to customize these functions on the system where the server runtime is initially installed. If you want to use the server runtime in a sysplex environment, you must make sure that the same customization changes are made to all of the other systems in the sysplex, on which the server runtime is installed.

Before you begin

Create copies of the sample files.

About this task

The following steps help you customize the z/OS system functions on the other systems in the sysplex. The resulting customization should mirror the customization on the initial system.

The following steps assume that your default server runtime data set high-level qualifier (hlq) is BBO. If it is not, modify these steps to use your specified hlq.

Procedure

  1. Update the SCHEDxx file to include the statements from the BBOSCHED sample file that you initially ran in the customization dialog.
  2. APF-authorize the BBO.SBBOLOAD, BBO.SBBOLD2, and BBO.SBBOLPA data sets.
    Important: Do not APF-authorize the BBO.SBBOULIB or BBO.SBBOMIG data sets. These data sets must run under the authority of the client user.
    Example: Your PROGxx PARMLIB member might include the following entries:
    
    
    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 (LE) data sets SCEERUN and SCEERUN2, and the DB2 data set SDSNLOAD are APF-authorized.
  4. Place the server runtime modules in the appropriate link pack area (LPA) or link list.

    The following table indicates where to place each module.

    Table 1. Placing modules in LPA or link list
    Modules Notes
    BBO.SBBOLPA Load all members into the LPA.
    BBO.SBBOLOAD 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 the SBBOLD2 data set 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 that the server runtime modules are loaded into dynamic LPA and are available after an IPL, create a new PROGxx member with the SETPROG LPA commands and invoke the PROGxx member from the PARMLIB COMMNDxx.

    Example:
    
    
    SETPROG LPA,ADD,MASK=*,DSNAME=
    BBO.
    SBBOLOAD
    SETPROG LPA,ADD,MASK=*,DSNAME=
    BBO.
    SBBOLPA
    
    
    • Change BBO to the appropriate qualifier if BBO is not the high-level qualifier for your server runtime data sets.
    • If you are using SETPROG on a running system, before you add the module BBO.SBBOLPA, BBO.SBBOLOAD, or BBO.SBBOMIG, you must purge any already existing module with the same name from the LPA.
  5. Optional: If you used a PROGxx file for APF authorizations or the LPA, must issue the following command:
    SET PROG=xx
    
  6. Optional: Make sure that all of the BBO.* data sets are cataloged.
  7. Update your SYS1.PARMLIB(BLSCUSER) member with the IPCS models supplied by member BBOIPCSP. For more information about the SYS1.PARMLIB(BLSCUSER) member, see z/OS MVS IPCS User's Guide.
  8. Optional: Start System Management Facility (SMF) recording. If you want to start SMF recording to collect system and job-related information on the WebSphere Application Server for z/OS 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 that 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. Issue the following command to start writing records to a Direct Access Storage Device (DASD):
      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).

Results

The same z/OS system function customization exists on all of the systems in the sysplex on which the server runtime is installed.



In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/trun_othbase.html