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

SCLM to Groovy Migration - zImport does not support same language being used for different types #51

Open
drbruce-git opened this issue Sep 16, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@drbruce-git
Copy link
Contributor

I have 2 different types, HPP and JCL that both use a language of TEXT. If I use an import type of LANG the wrong language is appended to these files with all the files getting .jcl.

I think the problem exists in both GenerateBuildProperties.groovy and GenerateZImport.groovy

The scriptMappings look OK however:

scriptMapping = TEXT :: hpp/text/.h
scriptMapping = CPP :: cpp/cpp/.c
scriptMapping = COPYBOOK :: dclgenc/copybook/.cpy
scriptMapping = TEXT :: jcl/text/.jcl

Causes build to fail with:
Caught: com.ibm.dbb.build.BuildException: java.io.FileNotFoundException: /u/dohertl/sclmMigration/jazz00/repo/jazz00/hpp/text/incl1.txt
com.ibm.dbb.build.BuildException: java.io.FileNotFoundException: /u/dohertl/sclmMigration/jazz00/repo/jazz00/hpp/text/incl1.txt

There seems to be a lot of mismatch here. In langexts.txt I told it to use .h as the extension, however it imports the file in as INCL1.jcl and then tries to reference it with incl1.txt?

Workaround is to leave the HPP files as .txt or create separate language definitions.

@drbruce-git drbruce-git added the bug Something isn't working label Sep 16, 2020
@drbruce-git
Copy link
Contributor Author

In GenerateZImport.groovy I have determined that the design used states this:

If an import type of LANG is used then all files of the same language get the same extension
If an import type of TYPE is used then all files of the same type get the same extension.

I will need to see what GenerateBuildProperties.groovy is doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant