PQ85162: BBOWIAPP RECEIVES A RETURN CODE 256 WHEN THE INPUT PARAMETER EXCEEDS 500 CHARACTERS PER UNIX BPXBATCH MAXIMUM SIZE LIMITS | |||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||
APAR status Closed as fixed if next. 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: BBOWIAPP receives a return code 256 * * when the input parameter exceeds 500 * * characters. * **************************************************************** * RECOMMENDATION: * **************************************************************** BBOWIAPP uses BPXBATCH to invoke the shell script wsadmin.sh to install applications. The "z/OS V1R4.0 UNIX System Services Command Reference" states that 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 a return code 256 for BBOWIAPP due to the BPXBATCH input parameter maximum size being exceeded.Problem conclusion Temporary fix Comments BBOWIAPP will be updated to allow more than 500 characters as the parameter string so that it will not give a return code of 256 due to the BPXBATCH max input parameter size. This APAR is being closed FIN with concurrence from the submitting customer. A solution to this problem will be delivered in a WebSphere Application Server for z/OS release within the next 18 months.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ88836 Modules/Macros Publications Referenced
|
Document Information |
Current web document: swg1PQ85162.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 #: PQ85162
IBM Group: Software Group
Modified date: Feb 28, 2006
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.