dependency build + submit of JCL in translator?
One answer
Hi Bernd,
You can configure your translator to call a REXX script that invokes the JCL, waits for it to complete, pulls the return code from the job log, and returns it. There are many examples out there of scripts that make use of the outtrap function to get the job name and check the job status.
You will need to configure the translator with a proper SYSLIB and indicate the build outputs business as usual in order to make the dependency build work. You will also likely need to take advantage of the @{source.member.name} and @{source.dataset} variables to tell your REXX script what source needs to be built.
As always you will need to test this thoroughly to be sure there are no undesirable side effects that might result from this implementation (e.g. problems due to spinning in the REXX script waiting for the JCL to finish).
Robin
You can configure your translator to call a REXX script that invokes the JCL, waits for it to complete, pulls the return code from the job log, and returns it. There are many examples out there of scripts that make use of the outtrap function to get the job name and check the job status.
You will need to configure the translator with a proper SYSLIB and indicate the build outputs business as usual in order to make the dependency build work. You will also likely need to take advantage of the @{source.member.name} and @{source.dataset} variables to tell your REXX script what source needs to be built.
As always you will need to test this thoroughly to be sure there are no undesirable side effects that might result from this implementation (e.g. problems due to spinning in the REXX script waiting for the JCL to finish).
Robin