This article presents a sample of what the Customization Dialog's generated instructions might look like. This is a sample only--you must use the instructions generated from your own variables when configuring your system.
----------------------------------------------- The customization dialog has created jobs based on the information you provided. These instructions tell you how to modify the operating system and run the jobs to customize WebSphere for z/OS. RULES: 1. If you created the target data sets (*.CNTL and *.DATA) on another (driving) system, you must copy them to the target system and give them the same data set names. 2. You must perform these instructions on your target system.
Doing manual configuration updates ---------------------------------- The customization dialog for WebSphere for z/OS does not attempt to update configuration data for your base operating system or existing subsystems. You must do the following manual steps prior to running the WebSphere for z/OS configuration jobs. Perform these steps to do manual configuration updates: 1. Update BLSCUSER. Refer to member BBOIPCSP in 'DATASET.CNTL' In order to use the IPCS support provided by the product, append the contents of this member to the BLSCUSER member in your IPCSPARM or system PARMLIB datasets. ------------------------------------------------------------------- 2. Update SCHEDxx. Refer to member BBOSCHED in 'DATASET.CNTL' In order to set the correct program properties for the WebSphere for z/OS run-time executables, append the contents of this member to the SCHEDxx member in your system PARMLIB concatenation. Note: When you are finished, issue the command SET™ SCH=(xx,xx) to activate SCHEDxx and load a new program properties table. ------------------------------------------------------------------- 3. Make sure the following data sets are APF-authorized: BOSS.VICOM.W000170.SBBOLPA BOSS.VICOM.W000170.SBBOLOAD BOSS.VICOM.W000170.SBBOLD2 CEE.SCEERUN CEE.SCEERUN2 GSK.SGSKLOAD Add these datasets to your PROGxx or IEAAPFxx parmlib members, as appropriate, ensuring you specify the correct volsers. ------------------------------------------------------------------- 4. If you want to collect the SMF120 records created by the run-time servers, update SMFPRMxx via the following: a. Update the SYS or SUBSYS(STC,...) statement for started tasks to include the 120 record. b. (Optional) You can specify designated subtypes 1-6. EXAMPLE: SUBSYS(STC,EXITS(IEFU29,IEFACTRT),INTERVAL(SMF,SYNC), TYPE(0,30,70:79,88,89,120,245)) --- For details on the SMF records, see related topics in the WebSphere for z/OS Information Center at http://www.ibm.com/software/webservers/appserv/zos_os390/library/ ------------------------------------------------------------------- 5. Update your active BPXPRMxx member to have the following WebSphere for z/OS configuration HFS: OMVS.WAS.CONFIG.HFS mounted at: /WebSphere/V6R0 in read/write mode. EXAMPLE: MOUNT FILESYSTEM('OMVS.WAS.CONFIG.HFS') MOUNTPOINT('/WebSphere/V6R0') TYPE(HFS) MODE(RDWR) ------------------------------------------------------------------- 6. The WebSphere product libraries will be placed in STEPLIB as needed, rather than in the system link pack area and system link list. SBBOLPA: ========= The following data set will be placed in the STEPLIB concatentation for the location service daemon. The data set's load modules will be loaded in the MVS™ common storage area when the location service daemon is started. Make sure the target MVS system has at least 8MB free storage in extended CSA before starting the daemon. BOSS.VICOM.W000170.SBBOLPA SBBOLOAD and SBBOLD2: ==================== The following data sets will be placed in the STEPLIB concatenation for the location service daemon, controller and servant regions, and in the setupCmdLine.sh script in the WebSphere Configuration HFS. You must not remove these STEPLIB statements. BOSS.VICOM.W000170.SBBOLOAD BOSS.VICOM.W000170.SBBOLD2 BBORTSS5: ========= The BBORTSS5 module is used by WebSphere Application Server V5 and V6 for component trace support. A copy of this module must be in the system link pack area in order for CTRACE to work correctly. If a copy of BBORTSS5 (any release) is currently loaded into LPA, you need take no further action. Otherwise, issue the following MVS console command to load BBORTSS5 into dynamic LPA: SETPROG LPA,ADD,MODNAME=BBORTSS5, DSNAME=BOSS.VICOM.W000170.SBBOLPA Alternatively, you can place the following statement in a parmlib PROGxx member which is activated with the SET PROG= command after system IPL is complete: LPA ADD MODNAME(BBORTSS5) DSNAME(BOSS.VICOM.W000170.SBBOLPA) Make sure that the BBORTSS5 module is loaded into LPA after each system IPL. ------------------------------------------------------------------- 7. Make sure the following Language Environment® data set is in the system link list: CEE.SCEERUN ------------------------------------------------------------------- 8. Make sure the following Language Environment data set is in the system link list: CEE.SCEERUN2 ------------------------------------------------------------------- 9. Make sure the following System SSL data set is in the system link pack area or the system link list on all MVS systems at or below z/OS Version 1.5: GSK.SGSKLOAD ------------------------------------------------------------------- 10. WebSphere for z/OS regions open a large number of files (more than 1024). Make sure your BPXPRMxx parmlib member(s) specify a value of MAXFILEPROC that is greater than or equal to 2000. Use the following MVS console command to see your current MAXFILEPROC setting: D OMVS,OPTIONS
Running the customized jobs --------------------------- The customization dialog built a number of batch jobs with the variables you supplied. You must run the jobs in the order listed below using user IDs with the appropriate authority. BEFORE YOU BEGIN: Complete the section above entitled "Doing manual configuration updates." Follow the table below, which lists in order the jobs you must submit and the commands you must enter. Special handling notes are included in the table. All jobs are members of DATASET.CNTL Attention: After submitting each job, carefully check the output. Errors may exist even when all return codes are zero. +-----------+----------------------------------------------------------+ | BBOMSGC | User ID requirement: Update authority for data set | +-----------+ SYS1.MSGENU and/or SYS1.MSGJPN. | | Done: | | | | ATTENTION: This is optional unless you require message | | | translation. | | By: | | | | This job sets up MMS to translate messages for WebSphere | | | for z/OS. | | | | | | There are two steps to update SYS1.MSGENU and | | | SYS1.MSGJPN. Remove the unneeded step and change the | | | target libraries, if necessary. | +-----------+----------------------------------------------------------+ | BBOWMNMT | User ID requirement: UID=0 and authority to allocate | +-----------+ | | Done: | OMVS.WAS.CONFIG.HFS | | | | | | This job: | | | | | By: | o Creates a mount point directory | | | | | | /WebSphere/V6R0 | | | | | | o Allocates the configuration HFS | | | | | | OMVS.WAS.CONFIG.HFS | | | | | | and mounts it at the above mount point. | | | | | | BEFORE YOU BEGIN: The BBOWMNMT job assumes your root HFS | | | is mounted in read/write mode. If the root HFS is not in | | | read/write mode, manually create the directory | | | | | | /WebSphere/V6R0 | | | | | | and any needed higher directories, set file permissions | | | to 775, and set the owning user ID and group to WSADMIN | | | and WSCFG1 before running BBOWMNMT. | | | | | | EXAMPLE: If you plan to use /WebSphere/V6R0M0 as your | | | directory, issue the following commands from within the | | | OMVS shell: | | | | | | mkdir -p -m 775 /WebSphere/V6R0M0 | | | chown -R WSADMIN:WSCFG1 /WebSphere | | | | +-----------+----------------------------------------------------------+ | BBOMHFSA | User ID requirement: UID=0. | +-----------+ | | Done: | This job populates the previously-created HFS. | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | BBOWCPYM | User ID requirement: update authority for: | +-----------+ | | Done: | SYS1.PROCLIB | | | | | By: | | | | | | | | | | | | | This job copies the tailored start procedures, | | | parameters, and EXECs to the run-time libraries. | | | | | | ATTENTION: Be aware that you may overlay existing | | | members in the above data sets. | | | | +-----------+----------------------------------------------------------+ | BBOWWPFM | User ID requirement: UID=0. | +-----------+ | | Done: | This job sets up the runtime HFS. | | | | | | | | By: | Upon completion, examine the job output. Success is | | | indicated by rc=0. | | | | +-----------+----------------------------------------------------------+ | BBOMHFSB | User ID requirement: UID=0. | +-----------+ | | Done: | This job will complete the HFS initialization. | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | BBOWMNAN | User ID requirement: UID=0. | +-----------+ | | Done: | This job will federate your node into the specified | | | Deployment Manager cell. Ensure that your Deployment | | | Manager is running before submitting this job | | | | | | Upon completion, examine the job output. Success is | | By: | indicated with a RC=0 in the job output. | | | | +-----------+----------------------------------------------------------+ | -------- | Start the node agent server | +-----------+ | | | Note: The node agent is automatically started by the node| | | federation process. This step is information, for | | | starting the node agent at other times. | | | | | | Issue the following MVS command to start your node agent | | | server: | | Done: | | | | START BBO6ACR,JOBNAME=BBON001, | | By: | ENV=AQTS.AQTS.BBON001 | | | | | | | | | RESULT: The following message appears on the console and | | | in the job log of BBON001. | | | | | | BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR | | | z/OS CONTROL PROCESS BBON001 | | | | +-----------+----------------------------------------------------------+ | The product is now configured. You may create and manage | | application servers in the node using the administrative console or | | scripting. | | | +----------------------------------------------------------------------+