HMMMM...The trigger we are using for doing the actual indexes is TRIGGER2....We look for the word ACCOUNT. In the indexer we used for the mainframe file, we had this trigger set with a RECORDRANGE only looking in the first 6 lines. If we left it as is, looking in ANY row in column 2 it would find it down the page certain times...
TRIGGER2=*,2,X'4143434F554E543A',(TYPE=FLOAT) /* ACCOUNT: */
The other Trigger is just for channel 1
TRIGGER1=*,1,X'31',(TYPE=GROUP)
And the last one is for the POSTING DATE because its only on the first page...The one works as we are getting that date for POSTING DATE and not the ingestion date...
so from this, do you think its the TRIGGER 2 causing the problem even though the index fields are being captured???