× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Just going from memory but I think they added something for BLOB support.
Don't know if it was added in V5R1 or if just the room for it was reserved.
I think I found something about it in the V5R1 What's new this release
document.

Scott Mildenberger

> -----Original Message-----
> From: Smith, Nelson [mailto:NSmith@lincare.com]
> Sent: Friday, November 16, 2001 7:11 AM
> To: 'midrange-l@midrange.com'
> Subject: RE: V5R1 Trigger data buffer shifted
>
>
> I understand dereferencing to the variable portions of the buffer.
>
> The previous poster stated that new fields had been added to
> the buffer.  Is
> that statement true or not?  I can't find anything on any new
> fields in the
> fixed portion and it appears to still be 96 bytes long.  Of
> course, there is
> still a reserved section there that could possibly be used
> for new fields.
>
> If we are talking about new fields in the variable portion, I
> don't see
> anything new there either, just the four offsets to the two
> data buffers and
> the two null maps.
>
> If something new has been added, I would just like to know if
> it is anything
> useful.
>
> > -----Original Message-----
> > From:       thomas@inorbit.com [SMTP:thomas@inorbit.com]
> > Sent:       Friday, November 16, 2001 12:06 AM
> > To: midrange-l@midrange.com
> > Subject:    RE: V5R1 Trigger data buffer shifted
> >
> > Nelson:
> >
> > On Thu, 15 November 2001, "Smith, Nelson" wrote:
> >
> > > So, exactly what has been added?  Surely not the infamous
> "Who fired
> > me?"
> > > field?   That would be just too helpful.  Is the info
> section still 96
> > bytes
> > > or has that changed?
> >
> > The definition shows sections that have no fixed offset.
> They are allowed
> > to change positions at any time, maybe because of a new
> version/release,
> > maybe a PTF, maybe just because a different program caused
> the DB to fire
> > the trigger. Their positions cannot be relied on. The only way to
> > implement those sections is to use the offsets as supplied.
> >
> > I would suggest you simply declare the unfixed sections as
> based data
> > structures and set the address of the data structures at
> run-time by using
> > the offsets added to the address of the fixed portion. It
> should be a
> > fairly minor change.
> >
> > Tom Liotta
> >
> > --
> > Tom Liotta
> > The PowerTech Group, Inc.
> > 19426 68th Avenue South
> > Kent, WA 98032
> > Phone  253-872-7788
> > Fax  253-872-7904
> > http://www.400Security.com
> >
> >
> > ___________________________________________________
> > The ALL NEW CS2000 from CompuServe
> >  Better!  Faster! More Powerful!
> >  250 FREE hours! Sign-on Now!
> >  http://www.compuserve.com/trycsrv/cs2000/webmail/
> >
> >
> >
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing
> > list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
>
> **************************************************************
> **************************************************************
> **************************************************************
> ******************
> This message originates from Lincare Holdings Inc. It
> contains information which maybe confidential or privileged
> and is intended only for the individual or entity named above.
> It is prohibited for anyone else to disclose, copy,
> distribute or use the contents of this message.
> All personal messages express views solely of the sender,
> which are not to be attributed to Lincare Holdings Inc., and
> may not be copied or distributed without this disclaimer.
> If you received this message in error, please notify us
> immediately at MailAdmin@lincare.com or (800) 284-2006.
> **************************************************************
> **************************************************************
> **************************************************************
> ******************
> _______________________________________________
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.