×
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.
I've run into a problem with record locks due to commitment control.
If I update the same record in file A twice (via a service program call) in
the same module/program it works fine even though the record is locked.
If I update the record in file A via that same service program call and
then update file B and file B has a trigger that updates file A it fails in
the trigger program because of the record lock.
This is with STRCMTCTL and both *ACTGRP and *JOB. The trigger program is
*CALLER and shows with the same activation group as the service program
that does the file updates.
Is there anything I can do to let the trigger update the locked record? It
seems like there must be some way to do it if I can update the record twice
in the first place.
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.
midrange.com
