|
Hi Ron,
I'm working on an interface that loads a transaction file onto the system using ODBC into a flat transaction file. When the process finishes, we have proposed that a record be written to another file which is a transaction header of sorts, that will have a trigger on it. The trigger will simply submit a batch job which will then read the transaction file, validate it, and post it.So, I figured, since the trigger isn't actually doing anything with the data, it would be simple enough to use a CL.
So, the trigger doesn't actually need to know what data was written to the transaction header? No matter what data was written, it'll just submit a new job?
In that case, you can do it quite easily in CL. The following CL program should work:
PGM PARM(&TRGBUF &BUFLEN) DCL VAR(&TRGBUF) TYPE(*CHAR) LEN(9999) DCL VAR(&BUFLEN) TYPE(*CHAR) LEN(4) SBMJOB CMD(CALL MYPGM) ENDPGM
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.