HP3000-L Archives

March 2001, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Burgess Peter <[log in to unmask]>
Reply To:
Burgess Peter <[log in to unmask]>
Date:
Thu, 22 Mar 2001 12:41:34 -0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (47 lines)
Hi all

If any one wants to see an example of a user exit. We wrote one to ensure
that we kept in a bug from a certain release of software when we upgraded to
the latest version. It was easier to intercept the dbopen calls than to
remove the fix in many programs we had to do. Let me know if you want an
example of one in production using cobol/image.

Regards

Peter Burgess
Microwarehouse
www.microwarehouse.co.uk



-----Original Message-----
From: Lars Appel [mailto:[log in to unmask]]
Sent: 22 March 2001 11:44
To: [log in to unmask]
Subject: Re: Image Data Types


Jim wrote...

> ... my list of suggested data type fields was USA centric.  Guilty.

Ok. Sentenced to read five off-topic postings *before* deleting them.

:-) ;-) :-)

> ... I do think
>that HP should look at providing intrinsics to make editing data like
dates as
>consistent and easy as possible.  And in the case of dates HP as responded.

A concept like "user exits" might provide flexible data validation or
pre-/post-processing for DBGET/DBPUT/DBUPDATE intrinsics. But this could
also open a can of worms in terms of complexity and robustness...

On the other hand, nobody would have to wait for HP to implement such a
feature. As far as I recall, there are already a couple of people/products
using an "intercept" approach with Image Intrinsic "look alikes" in some
user level NMXL or NMRL that call XL.PUB.SYS internally.

Lars.

ATOM RSS1 RSS2