Author Topic: Trigger and Indexing Issue  (Read 1449 times)

Aysha Sheslyn

  • Newbie
  • *
  • Posts: 1
    • View Profile
Trigger and Indexing Issue
« on: September 30, 2020, 01:43:50 PM »
Hi,

I am from Application side and we are on the process of migration from EOS to CMOD. The source is Mainframe file. We have been stuck with a problem involving Trigger and indexes. Since the CMOD support team also found it tough to fix the issue, I am posting it here. Please excuse my lack of knowledge in CMOD.

We have a file which has the Carriage Control (Page Break with X'8B'). Next line starts with a 5 char label which decides the indexing part.  But the way we have kept our indexing seems wrong and hence getting a wrong result in CMOD.

Here is the indexing info:

CONVERT=NO
INDEXOBJ=ALL
CPGID=500
FILEFORMAT=RECORD
TRC=NO
CCTYPE=M
CC=YES
INDEXSTARTBY=0
UNIQUEBNGS=YES
INSERTIMM=NO
MCF2REF=CF
DCFPAGENAMES=NO
IMAGEOUT=ASIS
RESTYPE=NONE
INPEXIT=ACIFAILC
INDXEXIT=ACIFCXLC
TRIGGER1=*,1,X'8B',(TYPE=GROUP)
FIELD1='000000000000001'
INDEX1='LINE_COUNT',FIELD1,(TYPE=GROUP,BREAK=NO)
FIELD2='        '
INDEX2='JOB_NAME',FIELD2,(TYPE=GROUP,BREAK=NO)
FIELD3=1,2,5,(TRIGGER=1,BASE=0)
INDEX3='FORM_NAME',FIELD3,(TYPE=GROUP,BREAK=YES)


Kindly help me with the issue and please ask me for more details for you to understand the issue.

Thanks,
Aysha

Nolan

  • Full Member
  • ***
  • Posts: 152
    • View Profile
Re: Trigger and Indexing Issue
« Reply #1 on: September 30, 2020, 02:28:06 PM »
Why are field1 and field2 hardcoded?  Field3 looks correct but 1 and 2 should be using the same  style

FIELD1=Line,Column,Length,(TRIGGER=1,BASE=0)  <---put real location values for line/column/length
FIELD2=Line,Column,Length,(TRIGGER=1,BASE=0)  <---put real location values for line/column/length
J.

#zOS #AIX #Windows #Multiplatforms
#DB2 #TSM #ODF #zODF #ODWEK
#CapacityPlanning #AFP #ReportDistribution
#Finance #ICN