Processing of Binder control statement members

[dennis-behm]

Users may have members/files that contain binder control statements like ALIAS definitions and additional binder control statements for a particular build file.

Instead of converting these information to linkEditStream build zAppBuild properties or split the processing by using the LinkEdit.groovy, users want to reuse the binder control "members" to configure the bind step in Cobol.groovy, PLI.groovy and other language scripts.

For instance in Cobol.groovy can be extended by adding the library with the binder control statement member to SYSLIN:

dbb-zappbuild/languages/Cobol.groovy

Lines 348 to 350 in 9f25617

	// add SYSLIN along the reference to SYSIN if configured through sysin_linkEditInstream
	linkedit.dd(new DDStatement().name("SYSLIN").dsn("${props.cobol_objPDS}($member)").options('shr'))
	if (sysin_linkEditInstream) linkedit.dd(new DDStatement().ddref("SYSIN"))

I envision a "lookup" feature in zAppBuild that assesses a user-defined config to locate the file with binder control statements; including uploading the found member to a library and conditionally adding it to SYSLIN.