Building with identify=True

[lucianap1111]

Based on customer experience, the build is identified as successful with "Identify=false and they lost the traceability between source code and load module generated.

Could you please confirm what is the correct value for Identify? False? True?

[dennis-behm]

@lucianap1111

As outlined in the documentation, the setting <lang>_identifyLoad generates an IDRU record for the module during link phase:

dbb-zappbuild/samples/application-conf/Cobol.properties

Lines 66 to 74 in f3dfad6

	#
	# flag to generate IDENTIFY statement during link edit phase
	# to create an user data record (IDRU) to "sign" the load module with
	# an identify String: <application>/<abbreviatedGitHash>
	# to increase traceability
	#
	# can be overridden by file properties
	# default: true
	cobol_identifyLoad=true

This is a convenient way to put a fingerprint into the load module. You can read more about it here - https://github.com/IBM/dbb-zappbuild/blob/main/docs/HOWTOS.md#signing-load-modules-and-program-objects

However, not all scenarios can be captured. Which particular use case do you have? Why can't you use true?

In any case, this is a "supporting" function. It's the responsibility of the deployment tool to provide traceability from build outputs to source code - and this includes load modules, JCLs, parm cards and any other build output.

The DBB Build report captures repository url and hashes that need to be processed by the packaging actions to keep the relationship.