Hello,
I've used this as part of build and test automation. I develop software that runs on multiple platforms, including several Unix/Linux platforms as well as Windows and z/OS. Our source control is on the windows platform. Every night we check to see if there were source code checkins. If so, we pull the latest source out of the source control and ftp the source to all platforms and then fire off a build to ensure it builds properly.
In the ftp process we grab the job number and save it for the following morning when another FTP job pulls the build results down from the mainframe. The output is parsed in order to check return codes. The build results are posted on an intranet web page so that each morning we simply check the intranet page to see if the nightly build results were successful across all platforms.
FTP to JES used much?
Re: FTP to JES used much?
by gc1958 » Sat May 22, 2010 5:56 pm
- gc1958
- Posts: 4
- Joined: Sat May 22, 2010 1:27 am
- Has thanked: 0 time
- Been thanked: 0 time
Re: FTP to JES used much?
by richiewu » Mon Jul 12, 2010 7:34 pm
I structured an IDE based on Unix environment,
such as highlight, auto complete, auto indent, submit jcl, fetch jes result, compile with RDZ, locate error line and integrate with compiler result
http://blog.csdn.net/richardsa
most of them are written in Chinese.
such as highlight, auto complete, auto indent, submit jcl, fetch jes result, compile with RDZ, locate error line and integrate with compiler result
http://blog.csdn.net/richardsa
most of them are written in Chinese.
Re: FTP to JES used much?
by richiewu » Mon Jul 12, 2010 7:46 pm
gc1958 wrote:Hello,
I've used this as part of build and test automation. I develop software that runs on multiple platforms, including several Unix/Linux platforms as well as Windows and z/OS. Our source control is on the windows platform. Every night we check to see if there were source code checkins. If so, we pull the latest source out of the source control and ftp the source to all platforms and then fire off a build to ensure it builds properly.
In the ftp process we grab the job number and save it for the following morning when another FTP job pulls the build results down from the mainframe. The output is parsed in order to check return codes. The build results are posted on an intranet web page so that each morning we simply check the intranet page to see if the nightly build results were successful across all platforms.
Can you tell us how to grab job number in ftp process?
Every time I submit JCL via shell in Cygwin, it won't display the job number but it will be displayed when type ftp command step by step.