Re: V5R1 Trigger data buffer shifted

[barsa@xxxxxxxxxxxxxxxxxxx]

If you had coded the trigger bugger using the information already contained
in the trigger buffer, it would have worked properly.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                    jmoreno@militarycar
                    s.com                     To:     Midrange-L@Midrange.com
                    Sent by:                  cc:
                    midrange-l-admin@mi       Subject:     V5R1 Trigger data 
buffer shifted
                    drange.com


                    11/09/01 11:32 AM
                    Please respond to
                    midrange-l






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.