This content has been marked as final. Show 8 replies
I'm not a mainframe expert but I think you would need a DD name where the PDF file was stored.
The DD name could be located in the extract file (and mapped to a GVM variable) or perhaps returned from a DAL script such as the following:
PDFName = "DD:PDF(medfax)"
Again, not my area of expertise but perhaps it will help (or least spark others to join in).
Does anybody have any additional information on using AddMultipageBitmap? Navin, did you ever get this to work on z/OS?
I'm trying to do the same thing. I added a section level rule for AddMultipageBitmap with the following as my options:
I put the following in my JCL in both GenData & GenPrint:
//TIFFILE DD DSN=MY.TIFF.PDS,
I see this in my NAFILE after running Gendata following the section to which it was attached:
But then I get a bad return code from GenPrint, with the following information in the ERRFILE:
DM12041: Error : FAP library error: Transaction:<CHARIDIC>, area:<LBYLoadGBM>
message:<The LOG file named <DD:TIFFILE(TEST1)> cannot be found in the Library <LBYI> or the Workspace tree>.
DM12041:, Error : FAP library error: Transaction:<CHARIDIC>, area:<FSI.V115.SOURCE(FAPGLBTM),Mar 23 2012 14:42:10,11,5,4,696>
message:<Cannot load bitmap on this or later page(s) DD:TIFFILE(TEST1)>.
DM12041, which is explained a "general purpose error", is supposed to be followed by additional DM### error messages...but in this case, it isn't, so that doesn't help at all.
Anybody got any ideas? I'm not sure what it means by "workspace tree" in this context...I can't put the Tiff in the library as a Logo, since it's a dynamic TIFF only available at run time, etc.
Apparently I spoke too soon. While I no longer get error messages, and it's successfully pulling in 1-page TIFF's, it does not appear to be working correctly for multiple-page TIFF's. I have a 3-page TIFF that I'm now trying to pull in, and it seems to know it's 3 pages long, but my output shows page 1 three times, rather than showing me all three pages of my TIFF, etc.
I believe you may have found another bug. There currently is a bug open against your original issue and the workaround is what was described by user9976633 .
I am currently following up with PD to see if this new issue is part of the original bug, or if it is a new bug all together.
Edited by: user9976581 on Jan 10, 2013 10:18 AM