BMC AMI Load SHRLEVEL

SHRLEVEL specifies the extent to which applications can concurrently access a table space or partition during a BMC AMI Load job.

Discard processing differs slightly when working with RESUME YES SHRLEVEL NONE rather than RESUME YES SHRLEVEL CHANGE. If loading a file containing duplicate keys, RESUME YES SHRLEVEL NONE does not load any of the key values (including the original value), while RESUME YES SHRLEVEL CHANGE loads only the first key value of the set of duplicates.

 The following table displays RESUME YES SHRLEVEL NONE processing:

Row number

Key value

Status at the end of the job

1

'ABC123'

DISCARDED

2

'ABC123'

DISCARDED

3

'ABC123'

DISCARDED

4

'ABC123'

DISCARDED

5

'ABC123'

DISCARDED

Related topics

Basic-options

BMC-AMI-Load-Syntax-diagrams

Sort-considerations

Rows loaded: 0


 The following table displays RESUME YES SHRLEVEL CHANGE processing:

Row number

Key value

Status at the end of the job

1

'ABC123'

LOADED

2

'ABC123'

DISCARDED

3

'ABC123'

DISCARDED

4

'ABC123'

DISCARDED

5

'ABC123'

DISCARDED

Rows loaded: 1


SHRLEVEL.png

You can specify one of the following keywords:

NONE

SHRLEVEL NONE (the default) specifies that applications have no concurrent access to the table space or partition.

WRITETO(B) overrides SHRLEVEL NONE.

For more information about RESUME YES SHRLEVEL NONE processing, see the RESUME YES SHRLEVEL NONE processing table.

CHANGE

SHRLEVEL CHANGE specifies that applications can concurrently read from and write to the table space or partition into which BMC AMI Load is loading data. You can specify SHRLEVEL CHANGE with either LOAD RESUME YES or LOAD REPLACE.

LOAD RESUME YES SHRLEVEL CHANGE

This specification tells BMC AMI Load to use SQL to insert rows into the specified tables. Therefore, switching or change of status does not occur.

If you specify RESUME YES SHRLEVEL CHANGE, you cannot specify any of the following options:

  • RESUME NO
  • REPLACE
  • KEEPDICTIONARY
  • LOG NO
  • ENFORCE NO
  • COPY YES
  • COPYDDN
  • RECOVERYDDN
  • PREFORMAT

If you specify LOAD RESUME SHRLEVEL CHANGE, you cannot specify COPY YES.

For more information about LOAD RESUME YES SHRLEVEL CHANGE processing, see the LOAD RESUME YES SHRLEVEL CHANGE processing table.

LOAD REPLACE SHRLEVEL CHANGE

This specification tells BMC AMI Load to write the loaded data to shadow data sets, keeping the original data sets intact during the load process. After the data is loaded, BMC AMI Load performs rename or fastswitch processing and deletes the original data sets.

Warning

This option fully replaces the data in the table space or partition, including any inserts, updates, or deletes to the original object that occur during the load process.

The following considerations apply to LOAD REPLACE SHRLEVEL CHANGE:

  • If you specify PART, the following processes take place:

    • BMC AMI Load replaces the specified partitions. BMC AMI Load does not apply changes to any of the partitions that occur during the load process.
    • During the load, NPIs are in RW status. NPI changes that occur during the load for the partitions that are being loaded are discarded. NPI changes that occur during the load for the remaining partitions are applied after the load.
  • BMC AMI Load drains the objects before the switch phase. You can control the time-out values for this drain by using the +QRETRY parameter or the BMC-AMI-Load-DRAIN_WAIT syntax option.

REFERENCE

SHRLEVEL REFERENCE specifies that applications can concurrently read from the table space or partition into which BMC AMI Load is loading data. You can specify SHRLEVEL REFERENCE only with LOAD REPLACE.

BMC AMI Load writes the loaded data to shadow data sets, keeping the original data sets intact during the load process. After the data is loaded, BMC AMI Load stops the objects briefly to perform rename or FASTSWITCH processing, then deletes the original data sets.

The following considerations apply to SHRLEVEL REFERENCE:

  • If you specify PART, NPIs are in RW status during the load. NPI changes that occur during the load for the partitions that are being loaded are discarded. NPI changes that occur during the load for the remaining partitions are applied after the load.
  • If you do not specify COPY YES or COPYDDN, BMC AMI Load places the table space in copy pending status after the load.If you do specify COPY YES or COPYDDN, the copy is a SHRLEVEL REFERENCE copy.

Considerations

The following considerations apply to all SHRLEVEL keywords.

  • Tables defined with the DATA CAPTURE CHANGES attribute are commonly known as Change Data Capture (CDC) tables. Running BMC AMI Load on CDC tables can cause data being replicated to become inconsistent until a refresh is done. The Db2 12 subsystem parameter UTILS_BLOCK_FOR_CDC specifies that certain Db2 Utilities will be blocked for CDC tables or tables spaces containing CDC tables.
  • When processing LOAD INTO TABLE with SHRLEVEL NONE or SHRLEVEL REFERENCE, BMC AMI Load checks whether any CDC tables are being processed. If BMC AMI Load is processing a CDC table and the UTILS_BLOCK_FOR_CDC subsystem parameter is set to YES, BMC AMI Load issues an error message and proceed with +CLEANUP processing.
  • When processing LOAD INTO TABLE with SHRLEVEL CHANGE REPLACE, BMC AMI Load checks whether any CDC tables are being processed or if there are any CDC tables in the same table space as the Load target table. If BMC AMI Load finds a CDC table and the UTILS_BLOCK_FOR_CDC subsystem parameter is set to YES, BMC AMI Load issues an error message and proceeds with +CLEANUP processing. 
  • BMC AMI Load processing is not blocked for SHRLEVEL CHANGE RESUME YES.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*