Re: [CMS-PIPELINES] LOOKUP AUTOADD wishlist: different key fields

2022-06-06 Thread Glenn Knickerbocker
On 6/6/2022 4:55 PM, Glenn Knickerbocker wrote: > I don't get where the confusion is. W2 is the key in the master record. > If W3 in this detail record doesn't match any masters, add this record > to the reference, the same as in my pipeline with the feedback loop. Ah, but thinking about it a li

Re: [CMS-PIPELINES] LOOKUP AUTOADD wishlist: different key fields

2022-06-06 Thread Glenn Knickerbocker
On 6/6/2022 3:42 PM, Rob van der Heij wrote: > On Mon, 6 Jun 2022 at 21:37, John P. Hartmann wrote: >> So which is the master and which is the detail? >> >> On 6/6/22 21:32, Glenn Knickerbocker wrote: >> >> PIPE ... | lookup autoadd w3 w2 ... >> >> FPLLUP761E Different key fields not allowed

Re: [CMS-PIPELINES] LOOKUP AUTOADD wishlist: different key fields

2022-06-06 Thread Rob van der Heij
On Mon, 6 Jun 2022 at 21:37, John P. Hartmann wrote: > So which is the master and which is the detail? > > On 6/6/22 21:32, Glenn Knickerbocker wrote: > >> PIPE ... | lookup autoadd w3 w2 ... > >> FPLLUP761E Different key fields not allowed with AUTOADD > Right. I can't see how a different

Re: [CMS-PIPELINES] LOOKUP AUTOADD wishlist: different key fields

2022-06-06 Thread John P. Hartmann
So which is the master and which is the detail? On 6/6/22 21:32, Glenn Knickerbocker wrote: PIPE ... | lookup autoadd w3 w2 ... FPLLUP761E Different key fields not allowed with AUTOADD Why not? It wasn't hard to write the pipeline to add the records to the reference myself, but in the ge

[CMS-PIPELINES] LOOKUP AUTOADD wishlist: different key fields

2022-06-06 Thread Glenn Knickerbocker
> PIPE ... | lookup autoadd w3 w2 ... > FPLLUP761E Different key fields not allowed with AUTOADD Why not? It wasn't hard to write the pipeline to add the records to the reference myself, but in the general case it gets pretty fiddly, grabbing the nonmatches from output 1 and delaying them wi

Re: [CMS-PIPELINES] PREFACE and REXXVARS error 233

2022-06-06 Thread John P. Hartmann
The callpipe implied in PREFACE does the commit on you (trace told me), so REXXVARS starts on commit level 0, does not commit to 0, and returns with code 233, as it should, but at that time it is too late for the dispatcher to pull the brake. Somewhere in the early 1980s, we got multistream pi

Re: [CMS-PIPELINES] PREFACE and REXXVARS error 233

2022-06-06 Thread Glenn Knickerbocker
On Tue, 31 May 2022 12:16:01 -0400, James Vincent wrote: >The giveaway: Do Until is evaluated at the end of the first iteration and I >am betting you have no "level 1" in play at the time, so the PIPE gets RC >233 and the VAR FILELIST is not set. The Do condition (or REXX) concludes >that "filelis