A fix is available
APAR status
Closed as program error.
Error description
FM/Db2 bind job FMN2BN3K ends with RC8, and the following messages are received: BIND PACKAGE(FMN2PLPK) MEMBER(FMN2D2I8) VALIDATE(BIND) ISOLATION(CS) RELEASE(COMMIT) ENCODING(EBCDIC) EXPLAIN(NO) DSNT230I +<SSID> BIND DBRM-MEMBER-NAME ERROR USING DB2ADMN AUTHORITY PACKAGE=<SSID>.FMN2PLPK.FMN2D2I8 MEMBER FMN2D2I8 NOT FOUND IN PDS SEARCH ORDER DSNT233I +<SSID> UNSUCCESSFUL BIND FOR PACKAGE = <SSID>.FMN2PLPK.FMN2D2I8.() Also, DBRM member ADBASW is copied but is not bound.
Local fix
Remove the following statements from step FMN2BND2: BIND PACKAGE(FMN2PLPK) - MEMBER(FMN2D2I8) - VALIDATE(BIND) - ISOLATION(CS) - RELEASE(COMMIT) - ENCODING(EBCDIC) - EXPLAIN(NO) Remove the following statement from step COPYDBRM: SELECT MEMBER=((FMN2ASW,ADBASW,R)) Rerun job FMN2BN3K
Problem summary
**************************************************************** * USERS AFFECTED: Users binding against Db2 V13 subsystems. * **************************************************************** * PROBLEM DESCRIPTION: FM/Db2 sample member FMN2BN3K included * * references which were not required and * * resulted in an RC=8 when binding * * against a Db2 V13 subsystem. * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** The sample member FMN2BN3K was: 1) Copying DBRM FMN2ASW to ADBASW but ADBASW was not bound. 2) Binding DBRM FMN2D2I8 but the DBRM was not shipped. This resulted in an RC=8
Problem conclusion
FM/DB2 sample FMN2BN3K was modified to remove references to FMN2ASW and FMN2D2I8 and ensure the bind job completed with RC=0.
Temporary fix
Comments
APAR Information
APAR number
PH56296
Reported component name
FILE MANAGER Z/
Reported component ID
5755A0300
Reported release
F10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-08-10
Closed date
2023-10-11
Last modified date
2023-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FMN2ACOO FMN2ACSO FMN2AGDO FMN2APMO FMN2APRO FMN2AREO FMN2ARMO FMN2ARPO FMN2ARRO FMN2ARSO FMN2ARTO FMN2ARYO FMN2ASLO FMN2ASQO FMN2ASWO FMN2AZPO FMN2BN1K FMN2BN2K FMN2BN3K FMN2BN3P FMN2CHK FMN2DATA FMN2FCQT FMN2FDBI FMN2FDBX FMN2FDFM FMN2FSC4 FMN2FSC5 FMN2FTU2 FMN2FX2C FMN2FX2D FMN2GEN FMN2INEX FMN2LVL FMN2MENU FMN2MJPN FMN2P0KB FMN2P0KR FMN2PEXO FMN2PIOP FMN2POKB FMN2POKR FMN2PXO2 FMN2PXOB FMN2RBO4 FMN2RDPZ FMN2REO5 FMN2RET1 FMN2RET2 FMN2REXO FMN2RGEN FMN2RIM5 FMN2RIMA FMN2RIMB FMN2RIML FMN2RRT6 FMN2RRT8 FMN2RTSS FMN2RX62 FMN2RXO9 FMN2RXOE FMN2RXTO FMN2ST00 FMNDA00 FMNDC17 FMNMOD2 FMNMOD2G FMNMOD2I
Fix information
Fixed component name
FILE MANAGER Z/
Fixed component ID
5755A0300
Applicable component levels
RF12 PSY UI93971
UP23/10/19 P F310
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"F10"}]
Document Information
Modified date:
02 November 2023