Fixes are available
16.0.0.2: WebSphere Application Server Liberty 16.0.0.2
16.0.0.3: WebSphere Application Server Liberty 16.0.0.3
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4
APAR status
Closed as program error.
Error description
WOLA CICS control transaction BBOC provides no way to be passed a long string of commands from the CICS operator console or using the INITPARMS option in CICS. For the operator console a limit of 126 characters exists and for INITPARMS a limit of 70 characters. The BBOC transaction supports over 140 characters worth of possible command data. Here are sample commands that are is valid, and larger than 140 characters: RO lpar,F cicsname,BBOC START_SRVR RGN=C23456789012 DGN=R2345999 NDN=D2345999 SVN=P2345999 SVC=* MNC=1 MXC=100 TXN=N SEC=N REU=Y REUC=100 REUT=30 STX=ZZO$ LTX=ZZO# RO lpar,F cicsname,BBOC START_SRVR RGN=C23456785555 DGN=R2345666 NDN=D2345666 SVN=P2345666 SVC=* MXC=100 REU=Y REUC=100 REUT=10 STX=ZZO$ LTX=ZZO#
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of WOLA with WAS on z/OS * **************************************************************** * PROBLEM DESCRIPTION: WAS z/OS WOLA in Liberty CICS BBOC * * control transaction does not provide a * * way to issue long command requests from * * the CICS operator console * **************************************************************** * RECOMMENDATION: * **************************************************************** WAS z/OS optimized local adapters (WOLA) does not provide a way to use the CICS BBOC control transaction to do the following basic things: 1) issue a command request that is longer than 140 characters on a CICS 3270 terminal, 126 characters from the CICS console, or 70 characters when using the INITPARMS CICS option. 2) send a registration or link server start request to the BBOC control transaction while the associated server is stopped and have it complete after the server is started 3) provide the name of a remote CICS transaction ID (TRANSID) or remote CICS system ID (SYSID) to be used on the EXEC CICS LINK PROGRAM() command done by the WOLA link invocation task (BBO#)
Problem conclusion
WAS z/OS WOLA CICS control transaction, BBOC, is updated to support several new capabilities. BBOC can now be passed command strings up to 500 characters using a new DOCTEMPLATE (DOC) option. This allows for command strings to be passed from a file in the file system, or from the member of a partitioned dataset (and any other sources supported with CICS Document Templates). The sub-parameter NAME=<doctemplatename> must be provided and a CICS document template configured and enabled with it's contents holding a single full BBOC command, up to 500 characters in length (a BBOC DOC command cannot be used inside this document template file). BBOC now has new options allowing a Link Server Start or Register request to be processed before the requested server to be attached to is yet started. This is done with a new RETRY=Y|N (default N) option and two new optional sub-parameters, RETINT=<n> (default 30, max 359000), to set a retry interval in seconds, and RETCNT=<n> (default 10, max 99999999), to set a retry count, or number of attempts to retry before stopping. BBOC now has options that allow the Link invocation task (BBO#), pass the TRANSID() or SYSID() options on the EXEC CICS LINK PROGRAM() for a target program. Option RTXP=Y|N (default N), adds the ability to have the Link invocation task (BBO#) pass the TRANSID(). When specified with no sub-parameters, it will default to using the EIBTRNID with the TRANSID() option on the EXEC CICS LINK PROGRAM() to the target application. New optional sub-parameters, RTXSYS=<sysid> and RTX=<transid>, offer the ability to provide the name of these two parameters (either TRANSID() or SYSID() but not both). The fix for this APAR is currently targeted for inclusion in fix pack 16.0.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI52665
Reported component name
LIBERTY PROF -
Reported component ID
5655W6514
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-11-17
Closed date
2016-05-11
Last modified date
2016-06-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PH06636
Fix information
Fixed component name
LIBERTY PROF -
Fixed component ID
5655W6514
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022