PQ78562: HOLD DATA FOR PTF UQ79825 (SERVICE LEVEL W500104) MISSING STEP IN THE POSTINSTALL SCRIPT "POSTINSTALL.SH" | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description There several issues with the Installation of PTF UQ79825. 1) During the installation of PTF UQ79825 for WebSphere, there is ++HOLD for ACTION information which is unclear. The section which is unclear is: . Support for feature WS17417 in APAR PQ77964 requires the following Hold for action: . This section is missing instructions to update the SCHEDxx member running on the system, with the new information that was generated when the WebSphere Intallation Dialog was run. Member BBOSCHED in <high level qualifier>.CNTL dataset was changed. . The external symptom that the customer will see if this is not done is that message: IEF188I PROBLEM PROGRAM ATTRIBUTES ASSIGNED will be issued from the WebSphere Address spaces. . The actual text of the section for feature WS17417 will also be re-written, to clarify that the 'base app server' section needs to be run in a Deployment Manager config as well. . 2) Code is missing in the Daemon startup program (main) that will cause the Daemon address spaces to fail startup IF the above SCHEDxx changes are made on the system. This APAR will deliver the code necessary to have the Daemon address space start up when the SCHEDxx member is changed to remove the SYST variable. . 3) The job that needs to be run in the Deployment Manager config is BBODCPY1. BBOWCP1 is for the Base App server.Local fix In order to have WebSphere daemon address space start up, the changes to the SCHEDxx member will have to wait to be done until the code is delievered in this APAR. The user will see message: IEF188I PROBLEM PROGRAM ATTRIBUTES ASSIGNED in the WebSphere address spaces. This is an informational message which is being issued due to the fact that the WebSphere address spaces are 'multi-step' address spaces after W500104 level, and the SYST option is in the PPT entry of the SCHEDxx member. . The following update should be used as a REPLACEMENT to the HOLD DATA in PTF UQ79825 for the section of HOLD DATA titled: 'Support for feature WS17417 in APAR PQ77964 requires the following Hold for action:' . After applying this PTF, the shell script "postinstall.sh" must be run from the WebSphere SMP/E install root (i.e. /usr/lpp/zWebSphere/V5R0M0/bin/postinstall.sh). This script must be run before the server(s) are restarted after applying service. The script performs bootstrap operations to enable the post installer component to function. The bootstrap operations must be performed on each WebSphere node that was created with the customization dialog. The customization dialog created a "configured root" for each WebSphere node in the HFS. You will be prompted for a single configured root path name at a time. The shell script must be run from OMVS from the WebSphere adminstrator user id (e.g. "wsadmin")to ensure the proper group and file permissions are set. The user id that runs the "postinstall.sh" shell script must have the same default group as the files in the configured root. This script will first validate that the path specified is a configured root and then perform the bootstrap updates on that path. Specify the configured root by its absolute path, i.e '/WebSphere/V5R0M0/AppServer/'. . After running the postinstall script against all the nodes (both base Application Server and Deployment Manager) in the hfs, you must re-generate your server procs. Start up the WebSphere for z/OS customization dialog. . For each set of PROCs used by your Application Server(s) in your system, perform the following: . 1. Select option 1, "Configure base Application Server node" 2. Select option "L" to load all your WebSphere customization variables 3. Select option 3, "Generate customization jobs" 4. Run job BBOWCPY1 to repopulate your proclib. BBOWCPY1 is located in the "CNTLtarget data set", i.e. <high level qualifier>.CNTL(BBOWCPY1) . Perform similar steps for each Deployment Manager server in your system: . 1. Select option 3, "Configure Deployment Manager node" 2. Select option "L" to load all your WebSphere customization variables 3. Select option 3, "Generate customization jobs" 4. Run job BBODCPY1 to repopulate your proclib. BBODCPY1 is located in the "CNTLtarget data set", i.e. <high level qualifier>.CNTL(BBODCPY1) . ************************************************************ ************************************************************ Note: If you are doing a coldstart configuration of WebSphere V5.0 then the following additional action is required: 1. In the SCHEDxx member in the system PARMLIB concatenation. Find the entry for BBOCTL: PPT PGMNAME(BBOCTL) /* PROGRAM NAME BBOCTL */ KEY(2) /* PROTECTION KEY 2 */ NOSWAP /* NON-SWAPPABLE */ PRIV /* PRIVILAGED */ CANCEL /* CANCEL ALLOWED */ ensure the entry has the following line: SYST /* SYSTEM TASK, NOT TIMED */ The result should look like this: PPT PGMNAME(BBOCTL) /* PROGRAM NAME BBOCTL */ KEY(2) /* PROTECTION KEY 2 */ NOSWAP /* NON-SWAPPABLE */ PRIV /* PRIVILAGED */ SYST /* SYSTEM TASK, NOT TIMED */ CANCEL /* CANCEL ALLOWED */ With the SYST parameter coded, you will see informational message IEF188I PROBLEM PROGRAM ATTRIBUTES ASSIGNED for the WebSphere Address spaces. The information in member BBOSCHED which was generated during the WebSphere customization does not have the SYST parameter. After APAR PQ78562, the SCHEDxx member will need to have the SYST parameter removed. 2. Issue the command SET SCH=( xx■, xx...,L) to activate SCHEDxx and load a new program properties table. The HOLD DATA Associated with this APAR, when delieverd, will also include the missing step of updating the SCHEDxx member.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The ++Hold for ACTION text related to * * the post installer for Service Level * * W500104 (UQ79825) is missing a step to * * tell the user to update the SCHEDxx * * member. Not updating the SCHEDxx * * member causes an informational message * * to be displayed on the console / log * * (IEF188I PROBLEM PROGRAM ATTRIBUTES * * ASSIGNED ). * * * * Also, on new configurations, where * * the newly generated SCHEDxx member * * is used you will receive this failure * * when attempting to start the server: * * * * Z/OS PROGRAM BBODMNF PPT ENTRY BBOCTL * * IS NOT SPECIFIED. SYSTEM=<system name> * * SERVER=<none> PID=0X0201006F * * TID=0X24F5CF70 Z/OS DAEMON BBODMNF * * ENDED ABNORMALLY, REASON=C9C2241C * **************************************************************** * RECOMMENDATION: * **************************************************************** When applying this PTF to an existing WebSphere for z/OS configuration where the SCHEDxx member is not updated because of the missing ++Hold for Action text, the informational message (IEF188I) is displayed. This is because the SYST attribute in the SCHEDxx member is being ignored because the server proc is now multi-stepped. The ++Hold for Action for the post installer needs to be updated with the step to tell the user to update the SCHEDxx member to remove the SYST attribute. Here's what the entire ++HOLD for action should read: After applying this PTF, the shell script "postinstall.sh" must be run from the WebSphere SMP/E install root (i.e. /usr/lpp/zWebSphere/V5R0M0/bin/postinstall.sh). This script must be run before the server(s) are restarted after applying service. The script performs bootstrap operations to enable the post installer component to function. The bootstrap operations must be performed on each WebSphere node that was created with the customization dialog. The customization dialog created a "configured root" for each WebSphere node in the HFS. You will be prompted for a single configured root path name at a time. The shell script must be run from OMVS from the WebSphere adminstrator userid (e.g. "wsadmin")to ensure the proper group and file permissions are set. The user id that runs the "postinstall.sh" shell script must have the same default group as the files in the configured root. This script will first validate that the path specified is a configured root and then perform the bootstrap updates on that path. Specify the configured root by its absolute path, i.e '/WebSphere/V5R0M0/AppServer/'. After running the postinstall script against all the nodes (both base Application Server and Deployment Manager) in the hfs, you must re-generate your server procs. Start up the WebSphere for z/OS customization dialog. For each set of PROCs used by your Application Server(s) in your system, perform the following: 1. Select option 1, "Configure base Application Server node" 2. Select option "L" to load all your WebSphere customization variables 3. Select option 3, "Generate customization jobs" 4. Run job BBOWCPY1 to repopulate your proclib. BBOWCPY1 is located in the "CNTLtarget data set", i.e. <high level qualifier>.CNTL(BBOWCPY1) Perform similar steps for each Deployment Manager server in your system: 1. Select option 3, "Configure Deployment Manager node" 2. Select option "L" to load all your WebSphere customization variables 3. Select option 3, "Generate customization jobs" 4. Run job BBODCPY1 to repopulate your proclib. BBODCPY1 is located in the "CNTLtarget data set", i.e. <high level qualifier>.CNTL(BBODCPY1) For each system with this PTF applied, do the following: 1. In the SCHEDxx member in your system PARMLIB concatenation. Find the following: PPT PGMNAME(BBOCTL) /* PROGRAM NAME BBOCTL */ KEY(2) /* PROTECTION KEY 2 */ NOSWAP /* NON-SWAPPABLE */ PRIV /* PRIVILAGED */ SYST /* SYSTEM TASK, NOT TIMED */ CANCEL /* CANCEL ALLOWED */ and remove the following line: SYST /* SYSTEM TASK, NOT TIMED */ The result should look like this: PPT PGMNAME(BBOCTL) /* PROGRAM NAME BBOCTL */ KEY(2) /* PROTECTION KEY 2 */ NOSWAP /* NON-SWAPPABLE */ PRIV /* PRIVILAGED */ CANCEL /* CANCEL ALLOWED */ 2. Issue the command SET SCH=( xx , xx ...,L) to activate SCHEDxx and load a new program properties table.Problem conclusion Update the ++HOLD for action for the postinstaller with the step "update SCHEDxx". With this step, the user will not see the message "IEF188I PROBLEM PROGRAM ATTRIBUTES ASSIGNED" displayed on their console / log because of the unnecessary SYST attribute in the SCHEDxx member. Also, on new configurations, the support has been modified to properly update the SCHEDxx. When the customer does a cold start, the server will not start due a missing PPT entry in BBOCTL. An example of the message would be: Z/OS PROGRAM BBODMNF PPT ENTRY BBOCTL IS NOT SPECIFIED. YSTEM=S1E SERVER= <none> PID=0X0201006F TID=0X24F5CF70 Z/OS DAEMON BBODMNF ENDED ABNORMALLY, REASON=C9C2241C. The post installer introduced a multi-step server proc which required the removal of the SYST attribute from the BBOCTL SCHEDXX member. On startup, the daemon checks for the SYST attribute in BBOCTL and abends because the attribute has been removed. APAR PQ78562 is associated with SERVICE LEVEL W502000 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ78562.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ78562
IBM Group: Software Group
Modified date: Jan 3, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.