Replacing data while allowing concurrent read access
This example illustrates how to run a LOAD REPLACE job while leaving the table space in read-only (RO) status.
This example uses the SHRLEVEL REFERENCE option to tell BMC AMI Load to leave the original table space in RO status during the load and create shadow data sets. BMC AMI Load loads the new data to these shadow data sets, and then stops the table space to perform rename or fastswitch processing.
The benefit of this job is data availability; the cost is the additional DASD required for the shadow copies during the load process.
//LODPARMS DD *
//SYSREC DD DISP=SHR,DSN=USER.DATA
//SYSIN DD *
LOAD DATA REPLACE SHRLEVEL REFERENCE INDDN SYSREC
INTO TABLE NGT.TABLE1
(ID POSITION(2),
MESSAGE POSITION(*) CHAR(34) NULLIF(1:1) = '?',
LANGUAGE POSITION(*) CHAR(10) DEFAULTIF(1:1) = '?')
//SYSREC DD DISP=SHR,DSN=USER.DATA
//SYSIN DD *
LOAD DATA REPLACE SHRLEVEL REFERENCE INDDN SYSREC
INTO TABLE NGT.TABLE1
(ID POSITION(2),
MESSAGE POSITION(*) CHAR(34) NULLIF(1:1) = '?',
LANGUAGE POSITION(*) CHAR(10) DEFAULTIF(1:1) = '?')
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*