VMFUTL2070W Build list NUCBL48 is not in the :BLD section of product parameter file
Article ID: 132584
Updated On:
Products
VM:Operator
Issue/Introduction
Appying service to VM:Operator and receiving the following warning:
VMFUTL2070W Build list NUCBL48 is not in the :BLD section of product parameter file
Environment
VM:Operator r3.1
z/VM 6.4
z/VM 6.4
Cause
Unable to apply VM:Operator PTF SO08021.
Received VMFUTL2070W Build list NUCBL48 is not in the :BLD section of product parameter file
When I ran the VMFBLD PPF BVMY031A VMOPERSFS (STATUS command,
I got:
VMFBLD2760I VMFBLD processing started
VMFSIP2453I Table ZVMY031A SRVAPPS G is a subset of table ZVMY031A SRVAPPS F
VMFBLD1851I Reading build lists
VMFUTL2070W Build list NUCBL48 is not in the :BLD section of product
parameter file BVMY031A PPF (compname VMOPERSFS)
VMFBLD2182I Identifying new build requirements
VMFBLD2182I New build requirements identified
VMFBLD2180I There are 12 build requirements remaining
VMFBLD2760I VMFBLD processing completed with warnings
The :BLD. section contains NUCBL51, not NUCBL48. We use a PPF override to change the filepool that the service files are stored in, so I checked ZVMY031A PPF, too. It also contains NUCBL51 instead of NUCBL48. VMOPER 192 contains both NUC51 TXTLIB and NUC48 TXTLIB, so I think there was a PTF at some point which changed the version of the common nucleus.
Received VMFUTL2070W Build list NUCBL48 is not in the :BLD section of product parameter file
When I ran the VMFBLD PPF BVMY031A VMOPERSFS (STATUS command,
I got:
VMFBLD2760I VMFBLD processing started
VMFSIP2453I Table ZVMY031A SRVAPPS G is a subset of table ZVMY031A SRVAPPS F
VMFBLD1851I Reading build lists
VMFUTL2070W Build list NUCBL48 is not in the :BLD section of product
parameter file BVMY031A PPF (compname VMOPERSFS)
VMFBLD2182I Identifying new build requirements
VMFBLD2182I New build requirements identified
VMFBLD2180I There are 12 build requirements remaining
VMFBLD2760I VMFBLD processing completed with warnings
The :BLD. section contains NUCBL51, not NUCBL48. We use a PPF override to change the filepool that the service files are stored in, so I checked ZVMY031A PPF, too. It also contains NUCBL51 instead of NUCBL48. VMOPER 192 contains both NUC51 TXTLIB and NUC48 TXTLIB, so I think there was a PTF at some point which changed the version of the common nucleus.
Resolution
You are correct, PTF RO99135 changed the Common Nucleus level (TXTLIB) from NUC48 TXTLIB to NUC51 TXTLIB.
Although it is annoying, you can ignore the message:
VMFUTL2070W Build list NUCBL48 is not in the :BLD section of product
Even though the VMSES control information has marked the NUC48 TXTLIB as being "DELETED", for some reason the fact that there is past VMSES control information indicating NUCBL48 BUILDLIST was used to build it in the past causes the VMFUTL2070W message to be issued each time VMFBLD is run.
The important things are that the NUC51 TXTLIB is now being serviced and built, and after running VMFBLD ( SERVICED you have ZERO build requirements remaining.
You should now be able to run VMDEPLOY to deploy the new service.
Additional Information
The warning will go away when we provide an RSU for VM:Operator.
Feedback
Yes
No
Powered by
