|
Don't tell me. This person hardcoded the offsets? Pointers to the rescue! Rob Berendt ================== "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Scott Mildenberger <Smildenber@Washcor To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> p.com> cc: Sent by: Fax to: midrange-l-admin@mi Subject: RE: V5R1 Trigger data buffer shifted drange.com 11/09/2001 11:54 AM Please respond to midrange-l Yes, the trigger buffer shifted. There were some fields added to the buffer info section prior to the record images. You need to use the image offsets provided in the trigger information to map your external DS to the proper location. Scott Mildenberger > -----Original Message----- > From: jmoreno@militarycars.com [mailto:jmoreno@militarycars.com] > Sent: Friday, November 09, 2001 9:33 AM > To: Midrange-L@Midrange.com > Subject: V5R1 Trigger data buffer shifted > > > Hello > > One of our machines was upgraded to V5R1 and we discovered > that the trigger > data buffer has shifted in V5R1 > > The V5R1 Database information center tells me that the trigger buffer > section in V5R1 is the same that the one in V4R4 > > We use an external definition of a database file with the > trigger buffer > information, the image of the record before, the null byte > map, the record > after and finally the new record null byte map. > > We have been using this technique (described by some as the > softcoding of a > trigger) for several years and never had any problems. > > I am about to load the latest and greatest database group ptf > and hopefully > this will resolve the problem. > > Has anyone else experienced this problem ? > > Regards > > Jorge Moreno > Systems Analyst > Woodbury, New York > > _______________________________________________ > 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 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 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.