PQ88836: BBOWIAPP RECEIVES A RETURN CODE 256 WHEN THE INPUT PARAMETER EXCEEDS 500 CHARACTERS PER UNIX BPXBATCH MAXIMUM SIZE LIMITS | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer experienced BBOWIAPP failures when he made the cell, node, or server names larger. Different combinations of these name sizes caused a return code 256 when running the BBOWIAPP. Here is one of his failure examples: BPXBATCH SH /IPO1/WebSphere/V5R0M0A/AppServer/bin/wsadmin.sh =52 conntype none -c '$AdminApp install =37 /IPO1/WebSphere/V5R0M0A/AppServer/installableApps =49 /adminconsole.ear {-appname adminconsole =42 -MapRolesToUsers {{"administrator" No No WSADMIN WSCFG1} =57 {"monitor" No No WSADMIN WSCFG1} =33 {"operator" No No WSADMIN WSCFG1} =34 {"configurator" No No WSADMIN WSCFG1}}=39 -server WebSphere_Development_Server_0 =39 -node Development_Application_Server_Node_1 =44 -cell Development_Cell_1_Base =30 -copy.sessionmgr.servername WebSphere_Development_Server_0}' =60 For a total of 516 characters in the Input parameter of the BPXBATCH portion of the BBOWIAPP. In reviewing the "z/OS V1R4.0 UNIX System Services Command Reference", it states BPXBATCH "accepts one parameter string as input, the combination of SH|PGM and program_name. ... The total length of the parameter string must not exceed 500 characters." Customers attempting to use larger cell, node, and server names may experience this same return code 256 for BBOWIAPP due to the BPXBATCH input parameter maximum size.Local fix Use lengths for cell, node, and server names that, in combination with the rest of the input parameter for BPXBATCH, will not exceed the 500 character maximum. LOCAL FIX CHOICE #2, To keep your naming convention intact: Delete the following 4 lines from Step1 of the BBOWIAPP job: -MapRolesToUsers {{"administrator" No No WSADMIN WSCFG1} + { monitor No No WSADMIN WSCFG1} + {"operator" No No WSADMIN WSCFG1} + {"configurator" No No WSADMIN WSCFG1}} +Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The BBOWIAPP or BBODIAPP job issues * * a return code 256 when WAS home, cell * * node and server long names are * * specified such that the input * * parameters to BPXBATCH exceed 500 * * characters. * **************************************************************** * RECOMMENDATION: * **************************************************************** The BPXPATCH utility accepts at most 500 characters as input. If a long enough cell name, node name, server name, and WAS home directory are specified, this along with the additional parameters in the command result in an input to BPXBATCH which contains greater than 500 characters.Problem conclusion To lower the BPXBATCH input length, an unneeded section of the input defining -MapRolesToUsers will be removed. Additionally, environment variables will be defined during the execution of the job to further limit the BPXBATCH input length. APAR PQ88836 is associated with SERVICE LEVEL W502010 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ85162 APAR is sysrouted TO one or more of the following: PQ89824 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ88836.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 #: PQ88836
IBM Group: Software Group
Modified date: Jul 2, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.