Find 'em, Fix 'em / Investigation and Planning /Know where you're going/Analyze data changes

| Non-numeric in date record Invalid dates in records Change data with code

#### Non-numeric in date record

    01 CUST-MSTER.
       05 CUST-ID       PIC X(10).
       05 CUST-ACTIVE-DTE.
          10 CUST-YY    PIC 99.
          10 CUST-DDD   PIC 999.
       05 CUST-NAME     PIC X(32).
       05 CUST-ADDR     PIC X(80).
       05 FILLER        PIC X(66).
| Record 1 contains a non-numeric value in the date field. If you use it in a computation, a S0C7 will result. Record 4 contains a blank date field. Do your date routines treat this as a valid value or a null value?
    REC          1         2         3         4         5         6         7         8
    NUM 12345678901234567890123456789012345678901234567890123456789012345678901234567890
        ---------|---------|---------|---------|---------|---------|---------|---------|
    001 311548790289A44SMITH, JOHN                     702 MAIN ST, NEWCASTEL, MA, USA
    002 738498756263102SMITH, MARGARET                 36092 WALNUT ST, BLOOMIGHTON, MN
    003 984736102996002SMITH, NORMAN                   221 BAKER ST, ELMO, NE, USA
    004 7483929958     SMITH, OLIVER                   14 E 7TH AVE, GREENVILLE, NC, USA
    005 755437656675352SMITH, PATRICK

#### Invalid dates in records

    01 SUPP-MASTER.
       05 SUPP-ID       PIC X(10).
       05 SUPP-ACTIVE-DTE.
          10 SUPP-YY    PIC 99.
          10 SUPP-MM    PIC 99.
          10 SUPP-DD    PIC 99.
       05 SUPP-NAME     PIC X(32).
       05 SUPP-ADDR     PIC X(100).
       05 FILLER        PIC X(155).
| Record 2 contains an invalid date. Is is a reserved value? Record 4 contains another invalid date. It may be a typo, but is it another reserved value. Is this date field edited? You could lose some "magic" numbers with downstream consequences if you "correct" the values.
    REC          1         2         3         4         5         6         7         8
    NUM 12345678901234567890123456789012345678901234567890123456789012345678901234567890
        ---------|---------|---------|---------|---------|---------|---------|---------|
    001 9487263744771202ACME CORPORATION                 852 ELM ST, REDVALE, CA, USA
    002 8938576253999999BOUNDER, LTM                     14 ULM, EXETER, UK
    003 0001938477610705HANDLER & SONS                   598 2ND ST, MAYS LAKE, UT, USA
    004 8193856366871232DEWOLD PACKING CO.               872 RR 22, NEVILLE, OH, USA
    005 9039288477850515EDWARDS & PICKENS                529 SAWYER ST, ONTARIO,CANDADA

#### Change data with code

    01 POLICY-MASTER.
       05 POLICY-ID       PIC X(10).
       05 POLICY-DTE      PIC 9(8).
       05 POLICY-TYPE     PIC X(6).
       05 POLICY-RATE-CODE PIC X(6).
       05 POLICY-RD       PIC X(5).
       05 CUSTOMER-ID     PIC X(8).
| The code has been made year 2000 ready by expanding the declaration for POLICY-DTE to a 4-digit year. But the century bytes in the file itself need to be populated before this code can be used. Is POLICY-RD an undiscovered Julian date? Maybe RD stands for "review date?"
    REC          1         2         3         4         5         6         7         8
    NUM 12345678901234567890123456789012345678901234567890123456789012345678901234567890
        ---------|---------|---------|---------|---------|---------|---------|---------|
    001 7483726551  671202LIFE  CA22959523334528576255175648837
    002 4362746552  521005HOME  AZ14919211464537782999534524366
    003 8948735421  910530MARINEIL00868802723435142200074663520
    004 3764525563  770902HEALTHFL93969436484938726474617645277
    005 9587243543  850515AUTO  TX12939328973628894847374635589