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

Simplify the deployTypes in BMS language processing #572

Open
dennis-behm opened this issue Nov 22, 2024 · 0 comments
Open

Simplify the deployTypes in BMS language processing #572

dennis-behm opened this issue Nov 22, 2024 · 0 comments

Comments

@dennis-behm
Copy link
Member

Today, the script is using a utility method to retrieve the deployType. This works, but is not the correct way for the BMS processing.

These are the two occurrences:

String deployType = buildUtils.getDeployType("bms_copy", buildFile, null)

String deployType = buildUtils.getDeployType("bms", buildFile, null)
linkedit.dd(new DDStatement().name("SYSLIN").dsn("&&TEMPOBJ").options("shr"))
linkedit.dd(new DDStatement().name("SYSLMOD").dsn("${props.bms_loadPDS}($member)").options('shr').output(true).deployType(deployType))

Instead, the script should just evaluate the two file properties and pass it to the DD statement:

#
# default deployType
bms_deployType=MAPLOAD
#
# default deployType for generated copybooks
bms_copy_deployType=MAPCOPY

Todo:

  • Please switch to standard file property syntax, like in here:
    String parameters = props.getFileProperty('bms_compileParms', buildFile)
  • pass the deployType for the BMS copygen command to the DD statement.
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

No branches or pull requests

1 participant