ODUG CMOD 10.1 Presentation question

[scottnys]

We had downloaded the ODUG presentation and I went thru it.  Is there anyone at 10.1 that uses ODF's Banner?  On one of the slides (forgot what page) under "SERVER:Miscellaneous", there was a BRIEF reference to ODF, "Banner in separate SYSOUT dataset".  I'm hoping that will be an OPTION like the option for the Manifest to be either/or.

One of the "fixes" that IBM tried to do for us, related to the Banner, was to not have the Banner/Report/Banner/Manifest in the SAME SYSOUT dataset. That didn't go well and they ultimately had to fix is so it was in the SAME SYSOUT.

Any thoughts would be appreciated.

[scottnys]

actual screen shot from presentation.

[Ed_Arnold]

Scott - as of right now ODF on 10.1 = ODF on 9.5 + all PTFs to date.

In other words, that slide is misleading in implying that there's something different about ODF 10.1 right out of the can.

But there is a difference between the two versions --- ODF 10.1 is completely 64-bit which should alleviate some large distribution problems and also provide the foundation for future enhancements.

Ed

[Ed_Arnold]

Verbiage behind the APAR that added that functionality:

Banner in separate SYSOUT dataset


Allow users the option of creating a  SYSOUT dataset for banner pages separate from the report.  A new ODF parm in the ars.cfg file, ARSODF_BANNER_ALLOC_PARMS, has been added to specify the allocation information to use when allocating the banner sysout datasets.    When ARSODF_BANNER_ALLOC_PARMS is specified, ODF will allocate a separate SYSOUT dataset for all banner pages for all distributions. The SYSOUT dataset will be allocated using the values specified in ARSODF_BANNER_ALLOC_PARMS and the class and destination specified in the report bundle definition. 

Example use:

ARSODF_BANNER_ALLOC_PARMS=FORMDEF(DUMMY)
   
In addition a new banner page type ‘E’ has been added to indicate the end of the distribution.  When ARSODF_BANNER_ALLOC_PARMS  is specified, the Banner exit will be called with type ‘E’.  Users will need to update their banner exit to either create an end of distribution page or add the following to arsodfxb.cob

                  when ODFBANER_Banner_End
      Move x'00'  to ODFBANER-PRINT-FLAG.

Note:  When using this parameter you should also specify report break yes on your distributions that contain multiple report bundle definitions.

[scottnys]

Thanks for the clarification Ed.
The same code you displayed was a proposed solution, from IBM, for our problem.  The problem with it is that spooling out 3 different DDs (first banner, report, trailing banner) there is no way to insure that the printer actually prints them TOGETHER and IN THAT ORDER.  They come out at the discretion of the printer (size for example).  When sending those 3 separate spooled outputs to another LPAR, forget keeping them together as well.  As long as it is an OPTION and we can still have the spooled output in ONE SYSOUT, that's OK.