A fix is available
APAR status
Closed as new function.
Error description
New Function . This APAR also resolves a storage problem with SP245 Key0. APAR OW55360 increased the IRAEASQE block size by '48' bytes, but IRARMRM3 was not updated with the correct freemain size. Issuing repeated JES $PXEQ commands with WLM managed initiators can result in storage fragmentation. .
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of z/OS 1.2 (HBB7705) and above. * **************************************************************** * PROBLEM DESCRIPTION: For exploiting WLM's Queue and Server * * management capabilities the customer * * has to define one or multiple * * application environments through WLM's * * administrative application. The * * application environment definition * * tells WLM how it can start server * * address spaces in order to manage the * * number of servers for the environment. * * The customer defines a name, the * * subsystem type of the application, the * * name of the start procedure for the * * server address spaces and optionally * * parameters which are passed to the * * application server. * * This function is exploited by various * * applications like DB2, scalable * * webserver, MQSeries Workflow and * * Websphere Enterprise Edition. * * Restrictions and requirements for the * * application environment definitions are * * usually described in the documentation * * of the application. * * * * In some cases, for example for the * * OS/390 Websphere environment, the * * customer must define the application * * environments twice, once to Websphere * * and in an additional customization step * * to WLM. The second step could be * * avoided if WLM would allow applications * * to dynamically define application * * environments when they need it and to * * change and remove the definitions if * * required. * * * * A second issue arises for embedded * * Websphere environments. In this case * * the websphere runtime can be included * * in other applications such as Lotus * * Domino or IMS Connect bridge. In * * addition to ease the installation for * * the customer, embedded instances may be * * started multiple times without knowing * * from each other. Today's implementation * * of application environments does not * * support multiple application * * environments with the same name on the * * same system. * **************************************************************** * RECOMMENDATION: * **************************************************************** In order to ease installation and customization of Websphere a new service to define and delete application environments via API is needed. In addition support is needed to have multiple application environments with the same name on the same system.
Problem conclusion
Temporary fix
Comments
The line item Dynamic Application Environments API addresses the customization and replication problems of application environments. It provides a new service IWMAEDEF which allows an application to define and remove application environments as well as enhancements to allow multiple application environments with the same name on the same system. In order to support multiple copies of the same Websphere runtime within different applications a new identifier is supported to distinguish the instance from other instances of the same type. This new identifier is named nodename and is added to the existing subsystem type and subsystem name identifiers. WLM provides a new service IWMAEDEF which allows applications to define application environments dynamically on the systems with dynamic application environments support. Application environments defined with this new service (dynamic application environments) have a single system scope in contrast to application environments defined via the WLM administrative application. This definition comprises of the name of the application environment, the subsystem type of the application, the nodename of the application environment, the subsystem name of the application environment, the name of the start procedure for server address spaces and optionally the parameters passed to the start procedure for the server address spaces, optionally the replication policy whether WLM can start one or multiple server address spaces for the application environment. The default will be to start multiple server address spaces. The IWMCONN and IWMQINS services are enhanced to support the new optional NODENM parameter in order to allow work managers of different entities to run on the same system. The operator is able to display and modify dynamic application environments similar to existing static application environment: The corresponding operator interfaces are enhanced to provide a set of new externals for dynamic application environments. The new DISPLAY WLM,DYNAPPL= and VARY WLM,DYNAPPL= commands are introduced to display and modify dynamic application environments just like static application environments. The new commands support the new optional STYPE, SNAME and SNODE parameters to further qualify the dynamic application environment of interest. DISPLAY WLM,DYNAPPL=applenvname ,Options with Options stype=subsystem_type sname=subsystem_name snode=nodename The applenvname in the display command does allow the * wildcard to display multiple dynamic application environments. The * wildcard is only allowed as the last character in applenvname. VARY WLM,DYNAPPL=applenvname,REFRESH| QUIESCE|Q| RESUME ,OPTIONS with Options: stype=subsystem_type sname=subsystem_name snode=nodename The operation of dynamic and static application environments is disjoint from each other similar to definition and exploitation by the application. Dynamic application environments have a single system scope. Security Aspects: Because the server address spaces started on behalf of an application environment can run in problem program state, workload management allows to check the validity of a server through an SAF product such as RACF. When the server is being created, workload management makes an SAF call using a new SERVER class to check whether the server is valid for the application environment. If no SERVER class has been defined to the SAF product, workload management allows the server address space to be started. The SERVER and STARTED classes with a SAF product can be used to restrict access to application environment servers. For example, DB2, CB or IWEB servers with application environments have to associate a userid with the MVS procedure name being used to start the server. This is done using the STARTED resource class or by changing ICHRIN03 (started procedures table). Then the SERVER resource class is used to authorize this userid, and possibly others, to become a server for DB2 stored procedures, CB method requests, or Internet Connection Server web requests. Currently the server profile consists of the subsystem_type, subsystem_name and application_environment_name in the following form: subsystem_type.subsystem_name.application_environment_name A new node_name qualifier is an additional information which can be added to the server profile. The node_name is optional therefore if the parameter is not used the server profile will not change and WLM will use it in the same format as today. If the node_name is specified by the queue manager WLM expects the server profile to have the following format: subsystem_type.subsystem_name.application_environment_name. node_name The node_name is appended to the three existing qualifiers in order to avoid ambiguities with existing profile names. Today the maximum length for the server profile supported by RACF is 44 characters.
APAR Information
APAR number
OW54622
Reported component name
WORK LOAD MANAG
Reported component ID
5752SCWLM
Reported release
705
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2002-05-07
Closed date
2003-04-16
Last modified date
2003-08-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA02430 UA02431 UA02432 UA02433 UA02434 UA02435
Modules/Macros
IRAAENV IRAD2SEX IRAEASQE IRAENJON IRAENRES IRAEVREQ IRAMSCTH IRAPAASC IRAPABQD IRAPACAL IRAPACAP IRAPACA2 IRAPACA3 IRAPADFB IRAPADGM IRAPAGBS IRAPAHK2 IRAPAHK3 IRAPAHK4 IRAPAHK5 IRAPAHK6 IRAPAHK7 IRAPAHK8 IRAPAHK9 IRAPAQPP IRAPAQUE IRAPAQU2 IRAPASPD IRAPATCD IRAPATOP IRAPATRA IRAPATSE IRAPAWHR IRAQUEUE IRARAMP3 IRARMRM3 IRARMWL3 IRASRMST IRAWLMPL IWMAEDEF IWMAEDEP IWMCONN IWMCONNP IWMCTMOD IWMC4CHD IWMD3BQC IWMD3BQV IWMEMCT IWME2AID IWME2AIN IWME2ASC IWME2ASR IWME2AST IWME2BCN IWME2BLC IWME2BND IWME2BQY IWME2BRQ IWME2BSL IWME2CCO IWME2CCP IWME2CNF IWME2CNM IWME2CNR IWME2CON IWME2CRE IWME2CSC IWME2CSP IWME2CVP IWME2CVQ IWME2DIS IWME2DRG IWME2FAT IWME2FQI IWME2INF IWME2IN1 IWME2LCC IWME2LCP IWME2LIM IWME2QXT IWME2RAE IWME2REG IWME2REQ IWME2RIP IWME2RSR IWME2SCL IWME2SEL IWME2SEM IWME2SEX IWME2SRF IWME2SRM IWME2SRS IWME2SSM IWME2SV1 IWME2SV2 IWME2TAF IWME2TSK IWME2TTM IWME2WAR IWME2XIT IWMI2NUC IWMI2TSK IWMMT IWMO2DIS IWMO2MST IWMO2VRY IWMP2ACT IWMP2SET IWMP2TRN IWMQINS IWMQINSP IWMQ2CON IWMQ2DAE IWMQ2DEL IWMQ2DIS IWMQ2FIX IWMQ2FX2 IWMQ2INS IWMQ2IN1 IWMQ2SAM IWMQ2SEL IWMQ2STO IWMQ2VCN IWMQ2VEE IWMQ2VEQ IWMQ2VSI IWMWCDA IWMWLMEN IWMWLMJP IWMW2AR IWMW2BCL IWMW2BGR IWMW2CLS IWMW2CON IWMW2CRE IWMW2DIS IWMW2EVR IWMW2MCO IWMW2QWK IWMW2RCL IWMW2REF IWMW2RPT IWMW2SWB IWMW2TR IWMW4FSV IWMW4SEL IWMX2CRE IWMX2DEL IWMX2NTF IWMYCON IWMYMDEF IWMZ2DAE IWMZ2DAT IWMZ2DSE IWMZ2DSW IWMZ2QUE IWMZ2SER IWMZ2VAE IWMZ2VAT IWMZ2VWD IWMZ2WOR SGIIWM
Fix information
Fixed component name
WORK LOAD MANAG
Fixed component ID
5752SCWLM
Applicable component levels
R7J5 PSY UA02433
UP03/05/08 P F305
R7J6 PSY UA02434
UP03/05/08 P F305
R7J7 PSY UA02435
UP03/05/08 P F305
R705 PSY UA02430
UP03/05/08 P F305
R706 PSY UA02431
UP03/05/08 P F305
R707 PSY UA02432
UP03/05/08 P F305
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.