Author: Robert Sample
Posted: Fri Dec 23, 2016 7:15 pm (GMT 5.5)
You do understand, I hope, that Unix files (such as pipes) do NOT have a record structure whereas COBOL requires a record structure for its files? Furthermore, have you explored other ways to speed up your processing (such as using FREE=CLOSE and ensuring the output data set -- z/OS has files on tape and in Unix System Services; everything else is a data set; your use of "output files" in your post is incorrect terminology -- is closed as soon as the last record is written)? Also note that if the program output is generated throughout the long processing time, you may not be able to reduce the elapsed time for the programs without completely rewriting the entire application.
I found this article Two Kinds of Pipes by using Google for z/os batch pipes. I tested the write and read jobs given and they worked the way they are supposed to. I did not attempt to keep the pipe around to edit it, but then I don't see any reason to EVER edit a pipe. You'll want to use the jobs as specified without any changes to ensure they work at your site before you attempt to make any changes to them.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Fri Dec 23, 2016 7:15 pm (GMT 5.5)
You do understand, I hope, that Unix files (such as pipes) do NOT have a record structure whereas COBOL requires a record structure for its files? Furthermore, have you explored other ways to speed up your processing (such as using FREE=CLOSE and ensuring the output data set -- z/OS has files on tape and in Unix System Services; everything else is a data set; your use of "output files" in your post is incorrect terminology -- is closed as soon as the last record is written)? Also note that if the program output is generated throughout the long processing time, you may not be able to reduce the elapsed time for the programs without completely rewriting the entire application.
I found this article Two Kinds of Pipes by using Google for z/os batch pipes. I tested the write and read jobs given and they worked the way they are supposed to. I did not attempt to keep the pipe around to edit it, but then I don't see any reason to EVER edit a pipe. You'll want to use the jobs as specified without any changes to ensure they work at your site before you attempt to make any changes to them.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth