Recently there was a lot of hooha about the wonders of REXX and we all ( well, I ) got a little bit carried away.
I proudly was the first to install a REXX procedure on our system. All it did was replace an OPNQRYF by an SQL INSERT into a file in QTEMP : UPDATE etc, WITH NC.
Tested, installed, no problem. The program ran last night and woke up the boss in the small hours of the morning. Got hauled into the office first thing.
A program that ran after mine that did a STRCMTCTL LCKLVL(*CHG) crashed because of CPF8351 commitment control already active.
It would seem that STRREXPRC, or the SQL that it ran also started the commitment control.
The shame ! Obviously I didn't test the whole batch sequence of programs, only my own.
Any last words before I set my own commitment control to hara-kiri ?
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.
midrange.com
