Author Topic: Need to bundle distributions that don't all always create, without time of day  (Read 2313 times)

J9CMOD

  • Jr. Member
  • **
  • Posts: 53
    • View Profile
We have some output that is distributed in a bundle, that contains our own banner pages from several jobs.  In order to get them to group together as one set of output, that the print operators use to determine forms they need to load, etc., we have a bundle (in SAR) with a 30 minute delay on it.  That allows all the output to be created before it is bundled and sent out. 
For CMOD, there does not appear to be a "delay" option, and I have not found anything that will work for us. 

I tried using the LOADED as the DISTRIBUTION METHOD on the Distribution and WAIT as the WAIT/IGNORE indicator on the Report Bundle   - This doesn't work for us because not all output is created every night, so the bundle will sit and wait for anything that did not produce.

DISTRIBUTION METHOD LOADED; IGNORE - Doesn't work because it sends each distribution out as it is ready.

DISTRIBUTION METHOD ALL READY - Says that the distribution won't be processed until all output is ready.  This won't work with WAIT, again because not all output is created every night.  When I use IGNORE, it still sends it out as each piece is ready.

TIME OF PRINT & TIME OF DAY don't work for us because we need this output to produce as soon as it is ready, and the time that it is ready can vary 2 hours.  Not to mention if the cycle is running late, the output would again produce separately as it is ready.

Does anybody have any idea what I can set these distributions up as so they will produce the way we needed.  For example, is there a way to have the distributions release when the JOB is done, regardless of when it runs, or how much output is ready?

I appreciate any help you can give.

Thanks!






J9CMOD

  • Jr. Member
  • **
  • Posts: 53
    • View Profile
To accomplish this need in SAR, we had them bundled, and used a time delay that was sufficient to make sure all reports that would be created had enough time run before the bundle was processed.
Here are the attributes as they are shown in SAR (where we set up bundle attributes).  If I could set the same attributes in CMOD, it would work for me.
Attributes:                                                         
  Banner   ===> ( MFB9790  , *        , *        )                 
  BDist    ===> CBO-EP1-J                                           
  Late     ===>                    Bundle Confirm?   ===>           
  Interval ===> 00:10              Wait (Int, Late)  ===> ( Y , N )

Claudio Boscaini

  • Newbie
  • *
  • Posts: 2
  • I/T Specialist at IBM Italy
    • View Profile
Hello, I would set the distribution method as EXTERNAL and run a JOB that activates the distribution at any time you like.  All bundles available at that particular time will be printed out.  You may add it as the final step to an existing job that you consider to be a trigger for your ODF distribution. 

J9CMOD

  • Jr. Member
  • **
  • Posts: 53
    • View Profile
Thanks Claudio.
I actually went that direction in November, and am in the process of getting it into Production.
I left this open in case somebody had a better idea, so I didn't have to add another set of jobs to our nightly cycle, but the External with the job to release is actually working out very well.