Author Topic: ODF justification  (Read 1879 times)

htees

  • Jr. Member
  • **
  • Posts: 17
    • View Profile
ODF justification
« on: February 22, 2019, 09:38:00 AM »
Hey folks; I'm trying to put together a few justification bullets for management on ODF.

Other than report splitting/ distribution, reporting, emailing distributions, re-printing, and monitoring, what are some other cool uses folks are doing  that maybe we can apply to our setup? Does auto distribution likely take a load off of the system by lessening retrievals?

CMOD 9.5.12, using ICN ,  a MULTITUDE of differing documents, reports and formats stored.

Thanks! HT 
Harold Thomas
Developer Advisor, Anthem BC/BS

Nolan

  • Full Member
  • ***
  • Posts: 152
    • View Profile
Re: ODF justification
« Reply #1 on: February 22, 2019, 10:18:57 AM »
We use ODF on Z/OS not sure how it works on distributed.   Here are two cool things we do that are a little different, there could be better ways but this was set up years ago.

- We create ODF bundle distributions and send the results back to OnDemand for ingestion.  This allows us to have repacked reports for viewing, exporting.
- We also combine the banner exit, Automation (AOC), to flag when a report is successfully archived.  A dummy distribution kicks off and the banner exit puts out a WTO for the automation to capture a message and then post a flag in our scheduler.  This is required for reports that are loaded via the spool and you don't know when it successfully archived.

 
J.

#zOS #AIX #Windows #Multiplatforms
#DB2 #TSM #ODF #zODF #ODWEK
#CapacityPlanning #AFP #ReportDistribution
#Finance #ICN

Greg Ira

  • Full Member
  • ***
  • Posts: 240
    • View Profile
Re: ODF justification
« Reply #2 on: February 25, 2019, 07:20:44 AM »
Reloading a report for various reason is our most "uncommon" use of ODF.  One example is a report that comes in in EBCDIC that some users want "as is".  We use ODF to reload a second copy that runs through an input exit that converts the doc to an ASCII based CSV file that other users can then import the file directly into an Excel spreadsheet.
 We also use the reload method keep both a raw version of the report and an AFP version of the same report per a request from the users.  I think it was a data verification thing which was easier done against the raw version.
 I don't think auto distribution lessens the workload on the server much as the distribution is a retrieval itself however it did make it easier on some units that, for whatever reason, didn't want/couldn't get access for some users to any version of the CMOD client.