I've a KSDS file where Phone Number is the key and there are various other fields including Customer Name. In Customer Name field we have special characters which business wants to correct. Now there will be an ESDS file (as input file) wherein we will have only two fields - phone number and their corresponding 'valid' Customer Names.
We have to do this using an online program/transaction which we'll trigger only once. I am new to online programs. Would appreciate if anyone could advice what approach to follow. Thanks!
Can you clarify what it has to be an online program?
It is much easier to write a one-off batch program than a one-off CICS program (I've never heard of a one-off online program!). There's all the stuff you'd need to define for CICS then, presumably, take it all out again after successful completion - or will it be a periodic thing?
I expect CICS is using the KSDS, but that the ESDS is new? Even if you are 24/7, presumably a "maintenance window" is a possibility?
To me the requirement screams "batch". Simple processing, produce audit report with name before/after, number of changes, number of keys not found (you never know), number of change records read, business date, run date, time.
Out of interest, is there really no possibility of requiring the same telephone number for more than one client? Different members of same household, different members of same company without a fancy switchboard, telephone in student halls-of-residence? Lucky you, maybe they are all cell-phones.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Hello and welcome to the forum,
We have to do this using an online program/transaction which we'll trigger only once.
This is surely not a business requirement. . .
It is much easier to write a one-off batch program than a one-off CICS program (I've never heard of a one-off online program!)
Yup, batch would be a better choice. What some of my clients have done is to assign a few transaction-ids for one-off situations. These are enabled and disabled after the one run. The source has separate names, but when used, they are set up as one of the one-time-shot transactoins.
Have you considered how this is to be initiated? One way could be to initialte the online transaction from a batch job.
There must be some time when the online is down (i.e. to run backups or run the normal batch processes. This one-off could be scheduled for one of the batch windows. . .