DSNG013I csect-name ATTEMPTING TO START DB2 WITH AN UNSUPPORTED CODE LEVEL. REASON reason-code CODE LEVEL: code-level CATALOG LEVEL catalog-level HIGHEST ACTIVATED LEVEL highest-activated-level MINIMUM LEVEL minimum-level

Explanation

The code level of the starting Db2 subsystem is not supported by the highest activated Db2 13 function level.

csect-name
The name of the control section that issued the message.
reason-code
The reason that the message was issued is indicated by one of the following values:
1
The code-level code level of the starting Db2 subsystem is lower than the highest-activated-level function level.
2
The minimum-level function level of the of the starting Db2 subsystem is higher than the highest-activated-level function level.
3
The code-level code level of the starting Db2 subsystem is not compatible with the catalog-level catalog level.
Start of change4End of change
Start of changeThe code-level code level of the starting Db2 subsystem is not compatible with the indicated highest-activated-level function level. Db2 13 subsystems cannot fall back to the earlier Db2 version after function level V13R1M500 or higher is activated in the later Db2 version.End of change
code-level
The code level of the starting Db2 subsystem. The format is VvvRrMmmm, where vv is the version, r is the release, and mmm is the modification level.
catalog-level
The catalog level of the Db2 catalog and system objects. The format is VvvRrMmmm, where vv is the version, r is the release, and mmm is the modification level.
highest-activated-level
The highest function level that was ever activated. The format is VvvRrMmmm, where vv is the version, r is the release, and mmm is the modification level.
minimum-level
The lowest function level that is supported by the code level of the starting Db2 subsystem.

System action

Db2 terminates with reason code 00E7009D.

System programmer response

Ensure that the Db2 startup procedure points to the correct set of load libraries and that the activated function level is supported by the code level and catalog level.

Problem determination

Collect the following diagnostic items.
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 (04E and 04F abends).
  • Contents of the BSDS (both copies if dual BSDS in use) obtained by using the Db2 print log map (DSNJU004) utility.