RE: V5R1 Trigger data buffer shifted

["Westdorp, Tom" <Tom.Westdorp@xxxxxxxxxxxxxxxxxx>]

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
No new fields, they lengthened the null map which moved the after image
farther out the buffer.  We beta'd r510.  I argued with IBM for quite awhile
on getting some notice of this in the r510 installation info.  They
eventually included it in the info apar referenced in the memo to users.

My problem wasn't the movement of the data, I was using pointers (although
some others here were not) but I put the entry onto a data queue which
became too short by a few bytes when the new length of the r510 buffer came
into use.  <boom>  DDE's.

IBM's response was that I should test the length of the data vs the length
of the queue on every transaction and rebuild the queue automatically if and
when it became necessary.  Easy for them to say, I do a couple million
transactions every day.  But hey, they sell hardware don't they?  I thought
a mention in the memo to users would suffice but best I could get was the
info apar referenced in the memo to users.  I'm *SURE everyone reads that.
<sigh>

-----Original Message-----
From: Smith, Nelson [mailto:NSmith@lincare.com]
Sent: Friday, November 16, 2001 6: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.