If you find time please go through this mail and let me know if you have more information on this. As I know some tools like SMART/RESTART are available for RESTART logic but we can implement it on our own as follows. But I think it is important to know something about it as a Mainframe programmer. I don't know how many of us are using this logic in our programs.
Restart Logic in DB2 is more important in huge Databases like DB2. Plz go thru the below material from which u can get idea abt coding restar logic. Incase of program abend, u can retreive last read record from this table and read thru till u reach last committed record. Insert/update any table/file where u can store key of last read record i want to know how it wilk work.ĭepending on your requirement and available resources, you can have something like this:: Thanks for your reply but i need more clarification with example.Ĭan anybody give program for this. The last sucessful record is the record after the commit. We need to have a logic where in we store the last sucessful record and ensure that when restarted records only after the last sucessful record is inserted. Now when restarted all records are inserted again. The objective is for eg: you are inserting 1 million records to database from a file.Īfter inserting 1,800,000 records if there is an abort, then due to roll back all inserts are lost. Restart logic is mostly project specific. Restart logic to commit after reading every 1000 recordsĬan any body please explain more about Restart logic (commit after reading every 1000 records)
Restart logic to commit after reading every 1000 records -IBM Mainframes
0 kommentar(er)
