UPDATEMAXA

The UPDATEMAXA option tells BMC AMI Load whether to update the MAXASSIGNEDVAL column of the SYSIBM.SYSSEQUENCES table when loading identity column values from an input file. BMC AMI Load validates the input file values against the range that is defined on the identity column and updates the value of MAXASSIGNEDVAL based on this range and the current value of MAXASSIGNEDVAL.

UPDATEMAXA.png

Related topics

UPDMAXA


NO

Tells BMC AMI Load not to update the MAXASSIGNEDVAL column of the SYSIBM.SYSSEQUENCES table when loading identity column values from an input file

YES

Tells BMC AMI Load to update the MAXASSIGNEDVAL column of the SYSIBM.SYSSEQUENCES table


To load identity column values from an input file, you must specify an identity override clause on the LOAD command. BMC AMI Load allows any of the following clauses:

  • OVERRIDE(IDENTITY)
  • IDENTITYOVERRIDE YES
  • IDENTITYOVERRIDE

Important

  • IDENTITY values extracted from the input file are subject to entire record validation and selection before the highest or lowest value for the IDENTITY is computed. If a row is not selected due to WHEN specification, conversion error, part selection or check constraint validation, then the value for the IDENTITY in the record does not participate in the set of values; for computing the highest or the lowest values.
  • If you do not specify the identity column in the field specification clause, the UPDATEMAXA specification is ignored. 

Computed values do not adhere to discarded rows due to unique index violations.

For an ascending sequence, if the computed number is higher than MAXVALUE, then MAXVALUE is used instead of the computed value. For a descending sequence, if the computed number is lower than MINVALUE, then MINVALUE is used instead of the computed value.

The computed value is then compared with the MAXASSIGNEDVAL value. If the computed value is higher (ascending) or lower (descending), the update takes place. If not MAXASSIGNEDVAL remain as is.

The update occurs during the BMC AMI Load switch phase after posting SYSCOPY with a LOAD entry. Any failure during the update causes the job to fail with RC=16 (STEP-MUST-COMPLETE). If the job fails, you must restart the job.

Restriction

The scope of the update is limited to a single table under a single LOAD command. If you specify more than one INTO table clause under one LOAD command that has more than one identity column, the UPDATEMAXA results in an error and issues message NGTL959.

Specifying the default

You can specify the default for the UPDATEMAXA value in the //LODPARMS configuration options by using the UPDMAXA installation option.

 

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