Saving changes in batch format
Select option 5. Save changes in batch format to save the current changes in a file.
About this task
By selecting this option, you can save the current changes in a file as JCL records. You can then copy the JCL records to the SYSIN statement of an IMS Database Repair Facility batch job and apply the same changes that you made through the interactive operations to a copy of the database.
Current changes are defined as those changes made to a database that you did not undo. Every time that you make a change to the data in a database, the change is recorded in the UNDO table. When you undo a change, it is removed from the UNDO table. Therefore, the file that is created by option 5. Save changes in batch format has one change for each entry in the UNDO list for a given DBD. The UNDO list does persist across IMS Database Repair Facility sessions, but once you select option 2. View/Update database again, the UNDO list is cleared.
Procedure
Results
A message is displayed either indicating that the file was created successfully or that no changes were saved. If a new file is created, the message contains the file name. Press the End key to exit this panel and return to the Main menu.
Browse the created file. The file contains the data that you can copy into the SYSIN statement of a VSAM batch job or an OSAM batch job of IMS Database Repair Facility.
For example, if the DBD is DSFACHON, the high-level qualifier for the work data sets
(workhlq) that you specified when you started the IMS Database Repair Facility session is ZZZ, and the user ID is DBT, then the created file
name is ZZZ.DBT.FABZ.DSFACHON.BATCHINP
. The file contains the following data:
//* DBR ONLINE UPDATED DATA SET=DBT.HPPC.DB.DSFACHO0
//* COPY THESE RECORDS TO SYSIN IN THE OSAM BATCH JOB
ORBA 3380
VER 0020 F9E9E4E9E8C1D9C440404040D6D9C7C5404040404040404040404040
REP 0020 F9C8E4E9E8C1D9C440404040D6D9C7C5404040404040404040404040
- //* DBR...
- This comment line indicates which data set was changed.
- //* COPY...
- This comment line indicates that the data set changed was OSAM so you run the OSAM batch job.
- ORBA, VER, REP ...
- Copy these lines into the OSAM batch job's SYSIN statement.