Fixes are available
Rational Business Developer 9.1
Rational Business Developer Fix Pack 2 (8.5.1.2) for 8.5.1
Rational Business Developer 9.1.1
Rational Business Developer Fix Pack 1 (9.0.1.1) for 9.0.1
Rational Business Developer Fix Pack 1 (9.1.1.1) for 9.1.1
Rational Business Developer Fix Pack 2 (9.0.1.2) for 9.0.1
APAR status
Closed as program error.
Error description
Environment: z\OS Product name: IBM Rational Business Developer Program Version : 9.0.1 Description. Its observed that during the IMSVS build of an IMS transaction program, the FDABIND gets triggered with the applicable setup. Package binds configured (customized bind part in build descriptor): TSOLIB ACTIVATE DA('%DSNLOAD%') ALLOC FI(DBRMLIB) SHR DA('%EZEPID%.%SYSTEM%.DBRMLIB') DSN SYSTEM(%DSYS%) BIND PACKAGE(%COLLECTIONNAME%) - MEMBER(%EZEALIAS%) - ACT(REP) - VALIDATE(BIND) - ISOLATION(CS) - OWNER(%OWNERNAME%) - QUALIFIER(%QUALIFIERNAME%) - CURRENTDATA(NO) - EXPLAIN(NO) Following this process the bind will refer to the DBRM from the IMS Transaction program, which does not have any SQL statements, and therefore gets the build via the FDACL procedure. FDACL does not invoke the the DB2 processing so no associated DBRM member is created and therefore the FDABIND fails with a member not found error eg: READY TSOLIB ACTIVATE DA('SYS1.F1D200.DB2.SDSNLOAD') READY ALLOC FI(DBRMLIB) SHR DA('V538.ELA.IMSVS.DBRMLIB') READY DSN SYSTEM(D20Q) DSN BIND PACKAGE(CT74661) MEMBER(T74600) ACT(REP) VALIDATE (BIND) ISOLATION(CS) OWNER(T0T7466) QUALIFIER(T0T7466) CURRENTDATA(NO) EXPLAIN(NO) DSNT230I =D21Q BIND DBRM-MEMBER-NAME ERROR USING V0C1403 AUTHORITY PACKAGE=SEVOL0D2D20Q00.CT74661.T74600 MEMBER T74600 NOT FOUND IN PDS SEARCH ORDER DSNT233I =D21Q UNSUCCESSFUL BIND FOR PACKAGE = SEVOL0D2D20Q00.CT74661.T74600.() DSN DSN END In this scenario a Symbolic Parameter should be provided to prevent the FDABIND being executed.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** If there was any SQL being used in a program, the FDABIND step was always generated. Some users do not wish to have a bind done, as they might be using a package. We have introduced a new symbolic parameter named SQLBYPASSBIND and if specified with a value of YES, then the FDABIND step will be skipped.
Problem conclusion
The software has been updated and a fixtest is available.
Temporary fix
Comments
APAR Information
APAR number
PI16049
Reported component name
RATL BUS DEV
Reported component ID
5724S5000
Reported release
901
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-15
Closed date
2015-03-23
Last modified date
2015-03-23
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
RATL BUS DEV
Fixed component ID
5724S5000
Applicable component levels
R901 PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
14 October 2021