>I submitted an RCF on the subject of examples for actually using zEDC funct=
>ions from HLL's other than C not long after this message chain and received=
> no response at all from the RCF team. A follow-up email requesting status=
> or at least an acknowledgement that the documentation addition
Agreed on all points:
Errors: disp5ay --> display and repeated "If RC Not = 0 Then" near the end of
the program code. I'll send an RCF on that one.
I added a pseudo-random initialization of the zinput area based on the RANDOM
function with a seed of the current CCYYMMDD date and it does work
The example has two bugs in it (a typo and a repeated line), but fixing those
it does appear to work. A better test would have been to compress something
other than just binary zeroes, and also to re-init the "input" (now output)
area so you can actually "see" it work (in the debugger).
I've done it (called the Binder Fast Data API from COBOL). My program returns
interesting data about PDSE program object modules, such as the sections,
compiler versions and compile dates, binder information, user data IDRs, and so
on.
The hardest part was dealing with modules with enormously
I agree, but failing that they can (and should) at least put in a reference to
the COBOL documentation.
Yeah, calling the Binder Fast Data API (or even worse the "regular" Binder API)
from COBOL would be a stretch to document. Not sure I would even attempt that
one, and I have written code to
Thanks.
That seems like an odd place to put it. What's next, a chapter on how to call
the Binder Fast Data API from COBOL?
I'd think this chapter should be in the Callable Services for High Level
Languages manual.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
An off-list communication from another interested party pointed me to this link
to the online Enterprise COBOL Programmers Guide V6.4, which has exactly the
documentation I have been requesting, at least for COBOL programmers:
Chapter 36. Using zlib compression from a COBOL program
To be more clear: I am asking for examples of non-C-language un-authorized HLL
calls to the "zlib" un-authorized functions and a list of any COPY/INCLUDE
members necessary to accomplish those calls, not the zEDC authorized functions
nor the hardware-level DFLTCC instruction.
Peter
I submitted an RCF on the subject of examples for actually using zEDC functions
from HLL's other than C not long after this message chain and received no
response at all from the RCF team. A follow-up email requesting status or at
least an acknowledgement that the documentation addition
