Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processing of Binder control statement members #500

Open
dennis-behm opened this issue Apr 2, 2024 · 0 comments · May be fixed by #501
Open

Processing of Binder control statement members #500

dennis-behm opened this issue Apr 2, 2024 · 0 comments · May be fixed by #501

Comments

@dennis-behm
Copy link
Member

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:

// 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.

@dennis-behm dennis-behm linked a pull request Apr 3, 2024 that will close this issue
@dennis-behm dennis-behm linked a pull request Apr 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant