Hi Anthony,

We see that you have opened a PMR for this, but will share the answer for future readers' benefit:

The IBM Record Generator for Java documentation shows that you can individually select a record definition in the SYSADATA file to generate via the symbol={definition-name} parameter, in the absence of which it uses the first 01 level item found in the file.

We believe that you can create a dummy COBOL program with all the required syntactic trappings in which you include the copybook(s) that you want to generate and then invoke the generator with the appropriate parameters against the SYSADATA file you get from the compile of that program. Hope this helps!

Regards, Nicole

-----------------------------------------------------
Answered by Nicole Trudeau on Apr 18, 2019
-----------------------------------------------------

Hi, Attached is the Adata file generated after compiling a copybook using  a dummy program. But it was not helpful. Java copy generation ended in error.

I think Adata file is not poperly generated with right options. Any specific compile options to be used and also the dummy cobol program is enough to be a simple one

or need a Cobol+CICS program.

Kindly help me and suggest .

As a member of the compiler team, I can't comment on how another tool is using the ADATA file. The error could very well be in the other tool. It would help to know what error message you got from the other tool, as well as any error messages you got from the compiler.

As far as the compiler goes:

- ADATA is the only option you need for the compiler to create an ADATA file.
- The ADATA accurately reports errors encountered during compilation, so if there were any compiler errors, I'd expect that another tool using the ADATA might not succeed either.
- ADATA generation should be successful for ANY valid program, no matter how big or small, no matter how many copybooks it uses, as long as compilation is successful.

As a member of the compiler team, I can't comment on how another tool is using the ADATA file. The error could very well be in the other tool. It would help to know what error message you got from the other tool, as well as any error messages you got from the compiler.

As far as the compiler goes:

- ADATA is the only option you need for the compiler to create an ADATA file.
- The ADATA accurately reports errors encountered during compilation, so if there were any compiler errors, I'd expect that another tool using the ADATA might not succeed either.
- ADATA generation should be successful for ANY valid program, no matter how big or small, no matter how many copybooks it uses, as long as compilation is successful.

As a member of the compiler team, I can't comment on how another tool is using the ADATA file. The error could very well be in the other tool. It would help to know what error message you got from the other tool, as well as any error messages you got from the compiler.

As far as the compiler goes:

- ADATA is the only option you need for the compiler to create an ADATA file.
- The ADATA accurately reports errors encountered during compilation, so if there were any compiler errors, I'd expect that another tool using the ADATA might not succeed either.
- ADATA generation should be successful for ANY valid program, no matter how big or small, no matter how many copybooks it uses, as long as compilation is successful.

Hi, Attached is the Adata file generated after compiling a copybook using  a dummy program. But it was not helpful. Java copy generation ended in error.

I think Adata file is not poperly generated with right options. Any specific compile options to be used and also the dummy cobol program is enough to be a simple one

or need a Cobol+CICS program.

Kindly help me and suggest .