43
« on: March 22, 2018, 03:22:26 AM »
Currently, when we defined an indexer in the Application definition, we define a Trigger, Field and the index(s)...For the Index, we've always used the hex representation of the specific index defined...Ex
TRIGGER1=*,1,X'F1',(TYPE=GROUP) /* 1 */
FIELD1=3,20,8,(TRIGGER=1,BASE=0) /* PARTICIPANT */
FIELD2=1,38,8,(TRIGGER=1,BASE=0) /* POSTIN_DATE */
INDEX1=X'D7C1D9E3C9C3C9D7C1D5E3',FIELD1,(TYPE=GROUP,BREAK=YES) /* PARTICIPANT */
INDEX2=X'D7D6E2E3C9D5C76DC4C1E3C5',FIELD2,(TYPE=GROUP,BREAK=NO) /* POSTING_DATE */
We were told that we don't have to use the hex representation. We can just use the name itself. So for example, INDEX1 we would just use the word PARTICIPENT instead of the hex representation. When I tried that, first putting PARTICIPENT in quotes, INDEX1=X'PARTICIPENT',FIELD1,(TYPE=GROUP,BREAK=YES) it error indicating, The field name '& êèñäñ& +è' found in the index file does not match any expected fields. The field will be ignored....When I removed the quotes, then I received this error, PARTICIPANT WAS SPECIFIED WHEN QUOTED STRING EXPECTED. , WAS SPECIFIED WHEN = EXPECTED.
A side note, this data is coming from the MAINFRAME which I believe is in EBCIDIC and we're using F1 for our trigger. This maybe why the indexes are using HEX. I assumed that the parameter specified on the Indexer just had to match the name on the LOAD INFORMATION tab
Does anyone know what I'm missing or if you HAVE to use HEX?
Appreciate any input!
Take care
Dave