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.

Preparing z/OS

About this task

Follow these steps to prepare your z/OS operating system to run WebSphere Application Server for z/OS.

Procedure

  1. Make sure that all software prerequisites listed in Target system requirements are met.
  2. Make sure that the UNIX System Services environment is active and that the BPXPRMxx settings in effect meet or exceed the following minimum values:

    MAXTHREADS: 10000
    MAXTHREADTASKS: 5000
    MAXFILEPROC: 10000
    MAXSOCKETS (AF_INET domain): 12000

  3. Make sure that each WebSphere Application Server for z/OS server address space, as well as OMVS or batch job address spaces that run Java virtual machines, have access to enough virtual memory below the 2-gigabyte bar. (A Java virtual machine requires at least 250M of virtual memory, for example.) We recommend that all WebSphere Application Server address spaces be given at least 1024M of virtual memory.

    To do this: Specify REGION=0 (or a suitably large value, such as 1500M) for all batch job, started task and WLM job steps for WebSphere Application Server.

    Either specify MAXASSIZE(2147483647) or some similarly large value in BPXPRMxx to provide a large system-wide default address space size for Unix System Services address spaces, or set the ASSIZEMAX value in RACF (or similar security system) for each WebSphere Application Server for z/OS client or server user ID, including IDs used to run the batch Postinstaller or similar processes:
    ALTUSER WASUTIL1  OMVS(ASSIZEMAX(1073741824))  to allow WASUTIL1 a 1-gigabyte address space
    

  4. If you make use of 64-bit addressing mode, you must also make sure that each WebSphere Application Server for z/OS server address space, as well as OMVS or batch job address spaces that run Java virtual machines, have access to enough virtual memory above the 2-gigabyte bar. To do this:

    Specify a MEMLIMIT value that is greater than zero (0) , or a suitably large value such as 1500M, for all WebSphere Application Server for z/OS batch job, started task and WLM job steps that will use 64-bit addressing.

    Either specify MEMLIMIT(2147483647) or some similarly large value in BPXPRMxx to provide a large system-wide default above-the-bar address space size for Unix System Services address spaces, or set the MEMLIMIT value in RACF (or similar security system) for each WebSphere Application Server client or server user ID that will use 64-bit addressing:
    ALTUSER WASUTIL1  OMVS(ASSIZEMAX(1073741824)) to allow WASUTIL1 access to 1 gigabyte above the bar
  5. If you use localization and alternate code pages with UNIX System Services, make sure that all WebSphere Application Server for z/OS server, administrator and client user IDs (any user IDs that run WebSphere Application Server for z/OS scripts) are run with environment variables LANG and LC_ALL both set to the same locale based on code page IBM-1047. Settings based on any other code page can cause the scripts to fail. See "Changing the Locale in the Shell" in UNIX System Services User's Guide for more information.
  6. Make sure that the /tmp directory has at least 20 megabytes of free space.

    WebSphere Application Server for z/OS makes extensive use of the /tmp directory.

    You can use the df -kP /tmp shell command to show the number of available 1K blocks in the /tmp directory HFS. Divide the number of available 1K blocks by 1024 to determine the number of megabytes of free space.

    If your /tmp directory resides in a permanent read-write HFS, use the confighfs command in /usr/lpp/dfsms/bin to extend it as necessary. For example, the following command will add an additional 10 MB of space to the HFS in which /tmp resides:

    /usr/lpp/dfsms/bin/confighfs -x 10m /tmp

    If your /tmp directory resides in a temporary file system (TFS), modify the MOUNT statement in BPXPRMxx that defines it to add additional space. To define a 20 MB TFS and mount it at /tmp, for example, use the following MOUNT command:

    MOUNT FILESYSTEM('/TMP') TYPE(TFS) MOUNTPOINT('/tmp') PARM('-s 20')
    Note: If you do not specify a space ('-s') value, then the undesirably small default of 1 megabyte will be used.
  7. Determine the full data set names of the following system data sets used by WebSphere Application Server for z/OS:
    SCEERUN
    Language Environment runtime library
    SCEERUN2
    Language Environment runtime library
    System SSL
    System SSL runtime library (SGSKLOAD for z/OS Version 1 Release 5 and below, SIEALNKE for z/OS Version 1 Release 6 and above)

    Also, determine whether these data sets are in the system link pack area (LPA) or link list. Record this information on the worksheet.

    Note: If you are configuring WebSphere Application Server for z/OS on a collection of z/OS systems, with some systems at z/OS Release 5 or earlier and others at z/OS Release 6 or later, you might need to manually edit some of the cataloged procedures created by the customization process. See Link pack area, link list, and STEPLIB for more information.
  8. Make sure that all the following data sets are APF authorized:
    • cee_hlq.SCEERUN
    • cee_hlq.SCEERUN2
    • gsk_hlq.SGSKLOAD (on all systems at z/OS Version 1 Release 5 and below)
    • sys_hlq.SIEALNKE (on all systems at z/OS Version 1 Release 6 and above)
    • was_hlq.SBBOLPA
    • was_hlq.SBBOLOAD
    • was_hlq.SBBGLOAD
    • was_hlq.SBBOLD2
  9. Decide whether to run WebSphere Application Server for z/OS from the system link pack area and link list or from STEPLIB. See Link pack area, link list, and STEPLIB for more information.
  10. Make sure that any IEFUSI or JES2/JES3 exits on your system do not restrict WebSphere Application Server for z/OS address spaces to an address space size of less than 512 MB. Each WebSphere Application Server for z/OS address space should have a region size of at least 512 MB. All WebSphere Application Server for z/OS cataloged procedures are shipped with a default of REGION=0M.
  11. Make sure that the TSO segment default region size for WebSphere Application Server for z/OS installer and administrator TSO user IDs is at least 128 MB.

What to do next

Note: If you configured WebSphere Application Server for z/OS using the English ISPF Customization Dialog, and wish to allow the display of Japanese characters correctly in your environment, you need to modify some script files.
  1. Edit setupCmdLine.sh file

    from: CONSOLE_ENCODING="-Dws.input.encoding=cp1047 -Dws.output.encoding=cp1047"

    to: CONSOLE_ENCODING="-Dws.input.encoding=cp1399 -Dws.output.encoding=cp1399"

  2. Edit wsadmin.sh file

    from: EXTRA_D_ARGS="-Dfile.encoding=ISO8859-1

    to: EXTRA_D_ARGS="-Dfile.encoding=IBM-932

Making these two changes will enable you to see the Japanese messages correctly.



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/tins_prepzos.html