Fixes are available
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
Customers using the Liberty WOLA CICS link server to route requests over to a remote CICS region are not able to specify both the RTXSYS (remote sysid) and RTX (remote transid) parameters together for the same link server. This means there is no way to pass both the TRANSID() and SYSID() parameters to the link invocation task (BBO# transaction) so that it may provide these on the EXEC CICS LINK PROGRAM() API call to invoke the target program. Another issue is the ability to pass the RTXSYS parameter, without also specifying either RTX or RTXP. A link server should be able to start with just the RTXSYS parameter.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty for z/OS * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Liberty z/OS WOLA CICS link * * server fixes for RTXSYS and RTX * * parameters * **************************************************************** * RECOMMENDATION: * **************************************************************** Customers using the Liberty z/OS WOLA CICS link server to route requests over to a remote CICS region are not able to specify both the RTXSYS (remote sysid) and RTX (remote transid) parameters together for the same link server. This means there is no way to pass both the TRANSID() and SYSID() parameters to the link invocation task (the default BBO# transaction) so that it may provide these on the EXEC CICS LINK PROGRAM() API call to invoke the target program. There is also no way to provide the RTXSYS parameter, without also providing either RTX and RTXP. This needs to be a supported option.
Problem conclusion
The WOLA CICS link server now allows both the RTX and RTXSYS parameters to be supplied for remote invocation of a target program. The parameter RTX=<remote transid> results in the WOLA link invocation task using 'EXEC CICS LINK PROGRAM() TRANSID(<remote transid>)' and RTXSYS=<remote sysid> results in 'EXEC CICS LINK PROGRAM() SYSID(<remote sysid>)'. With this fix, if both are supplied, both will be used for the same link server (for example: 'EXEC CICS LINK PROGRAM() TRANSID(<remote transid>) SYSID(<remote sysid>)'). The WOLA CICS link server also now allows the RTXSYS parameter to be provided alone, without the need to pass either RTXP or RTX. Behavior of the RTXP=Y|N parameter remains unchanged, and tells the link invocation task to use whatever the current EIBTRNID is for the transaction ID parameter on the EXEC CICS LINK PROGRAM() TRANSID(). The fix for this APAR is currently targeted for inclusion in fix pack 18.0.0.1. 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
PI92070
Reported component name
LIBERTY PROF -
Reported component ID
5655W6514
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-04
Closed date
2018-01-08
Last modified date
2018-01-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
LIBERTY PROF -
Fixed component ID
5655W6514
Applicable component levels
RCD0 PSY
UP
Document Information
Modified date:
04 May 2022