Re: Future Of DB2 Modernization

Well I understood the problem to be the use of FieldProc.
it did not seem to be specific to Townsend's framework - just that they had
solved the problem of using it with legacy programs.

On Sat, Jul 30, 2016 at 8:47 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Thanks again, Vern.

The "problem" referenced in the article appears to be specific to
Townsend's framework. So maybe I'll just have to get over the ambiguity. I
suspect that the OAR interface and handler were the key to solving the
problem rather than SQL I/O per se.

If anyone wants to chime in on OAR as a wrapper around SQL, that's an
interesting topic too.



On Fri, Jul 29, 2016 at 2:27 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

You'll have to read the article again - there is a brief mention of the
problem.there, as I recall.

There is also an earlier article at IT Jungle that doesn't include any
mention of yours truly - sort of my preference here! There is a link to
this article in 2 places in the one you refer to here.

There was also a press release - here is the link from the Townsend
Security site -

http://townsendsecurity.com/news/townsend-security-announces-major-step-forward-with-FIELDPROC

Beyond that, I'm not at liberty to say - you could contact Patrick if you
want to ask more.

Cheers
Vern

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.