If RTC is just used for versioning cobol applicatons what is the best way to transfer to host for building?
We are using RTC just to version cobol applications, but not build them. We are ging to use our existing build JCL to build.
What is the best way to transfer members to the host to build with our existing JCL build scripts?
Just a build? Is there some way to use File Agent? Is there a way to be able to select just the members you have modified?
|
Accepted answer
Bill,
Take a look at https://ryehle.wordpress.com/2012/05/01/sample-custom-ant-task/ for a sample Ant task that will load your modified files to MVS. Bill Sigler selected this answer as the correct answer
|
One other answer
We are using the Translator Definition to execute a Rexx on the mainframe that takes the source that the Build Definition dropped into a PDS and pushes it to our existing SCM Tool's Build routine. We pass the information as Name=Value pairs and the Rexx parses it to know the name of the PDS the member is in and what the member name is and an identifier that the Build is being performed from RTCz. The PDS/Member come into the EXEC script as RTCz variables. EXEC '<pds where rexx lives>(<name of rexx>)' 'CALLINGPGM=RTCZ LIBRARY=@{source.dataset} MEMBER=@{source.member.name}' This allows us to submit builds for all of our Host code (Rexx, COBOL, PL1, Easytrieve, Assembler, etc) since our existing SCM Tool Build function handles the language identification and creates the appropriate JCL for the Build. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.