Author: Abhi Nature
Subject: Reply to: Easytrieve - Report writing - Only 1 REPORT para executing.
Posted: Wed Sep 14, 2016 12:33 pm (GMT 5.5)
Okay. This was interesting!
From the manual - ...if another report is already using the associated
print file, the PRINT statement outputs data to a work file that is spooled
until the associated JOB activity processing is complete
Therefore, the data from second REPORT paragraphs and further was spooled to a work file since multiple REPORT paragraphs were writing to same output file. Only first REPORT paragraph was directly writing to output file. This paragraph was holding the output file. Once JOB activity was completed, spooled data from work files should supposedly write to output file. This was not happening.
Spooled data from work files in my case was not writing to output file! The reason - I was using STOP EXECUTE! STOP EXECUTE immediately terminates all easytrieve function. This implies that writing spooled data from work files is yet another JOB activity, an internal one. Only writing STOP worked - it terminates only the current activity.
Subject: Reply to: Easytrieve - Report writing - Only 1 REPORT para executing.
Posted: Wed Sep 14, 2016 12:33 pm (GMT 5.5)
Okay. This was interesting!
From the manual - ...if another report is already using the associated
print file, the PRINT statement outputs data to a work file that is spooled
until the associated JOB activity processing is complete
Therefore, the data from second REPORT paragraphs and further was spooled to a work file since multiple REPORT paragraphs were writing to same output file. Only first REPORT paragraph was directly writing to output file. This paragraph was holding the output file. Once JOB activity was completed, spooled data from work files should supposedly write to output file. This was not happening.
Spooled data from work files in my case was not writing to output file! The reason - I was using STOP EXECUTE! STOP EXECUTE immediately terminates all easytrieve function. This implies that writing spooled data from work files is yet another JOB activity, an internal one. Only writing STOP worked - it terminates only the current activity.