In my firm, for a number of years, we have naturally been moving away from paper reports, and Excel is the preferred means.
We therefore tend to build extract files, rather than print spoolfiles.
We have a number of monthly reporting jobs, which build extract files.
Some of these extract files are based on other extract files.
Im wondering what the best way of distributing reports are. We are faced with three options.
1. As part of the monthly job, Let Iseries create an excel file, and FTP it to a location on the network.
2. use Catapult to read a spoolfile/work file.
3. Use microsoft reporting services (scheduled, or on demand)
Pros of the above ...
1. if monthly job fails, or there is a problem, no report gets distributed, so users know theres a problem
2. Not sure if it can read extract files, but can read spool files, create excel files and distribute/email.
3. More conventional means of data extraction, users have a URL and access reports as they see fit.
Cons against above ...
1. Always better to get Data Off database, rather than have database send it out (in my opinion).
.. plus, no URL to pick up report.
2. Very slow, resource heavy: need to design catapult reports. If job failed, there would be
no way of knowing. Plus, no URL to pick up report.
3. If job failed, there would be no way of knowing - extract file may hold last month's data.
Anyone got any thoughts on this, or other ideas? Is there a conventional method everyone uses?
Many thanks
We therefore tend to build extract files, rather than print spoolfiles.
We have a number of monthly reporting jobs, which build extract files.
Some of these extract files are based on other extract files.
Im wondering what the best way of distributing reports are. We are faced with three options.
1. As part of the monthly job, Let Iseries create an excel file, and FTP it to a location on the network.
2. use Catapult to read a spoolfile/work file.
3. Use microsoft reporting services (scheduled, or on demand)
Pros of the above ...
1. if monthly job fails, or there is a problem, no report gets distributed, so users know theres a problem
2. Not sure if it can read extract files, but can read spool files, create excel files and distribute/email.
3. More conventional means of data extraction, users have a URL and access reports as they see fit.
Cons against above ...
1. Always better to get Data Off database, rather than have database send it out (in my opinion).
.. plus, no URL to pick up report.
2. Very slow, resource heavy: need to design catapult reports. If job failed, there would be
no way of knowing. Plus, no URL to pick up report.
3. If job failed, there would be no way of knowing - extract file may hold last month's data.
Anyone got any thoughts on this, or other ideas? Is there a conventional method everyone uses?
Many thanks
Comment