I am using a partial key (1st field) to read a keyed file (2 fields - both keys - ascending order):
ABCKEY KLIST KFLD WRKABC (this has a value that I know has at least 1 record in my external file) (indicators)
C ABCKEY SETLL FILE 506070
C ABCKEY READE FILE 8090
C *IN90 DOWEQ *OFF C
I added the indicators on both the SETLL and READE (initially only had 90 in EQ indicator) to see where the problem was. I know for a fact that my WRKABC field has a value that has several records in my FILE. When I debug my program, after the SETLL, 50, 60 and 70 are off. (Shouldn't 70 be on?) After the READE - 90 is on, but I think should be off. When I look to see what record it is reading, it is pointing at the first record AFTER this match: Example: WRKABC = 'A1234' FILE has: A1234 12847258 A1234 38356738 A1234 49384678 A1234 78793867 A1235 94849687 <---- job shows it is on this record Any idea what is happening? I am concerned because we have several existing programs that use these 2 operations.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!