A fix is available
APAR status
Closed as program error.
Error description
ABEND04E RC00E80051 AND DSNY005I SUBSYSTEM STARTUP TERMINATED INVALID START COMMAND RECEIVED WHEN USER ENTER INCORRECT START DB2 COMMAND. For example, -db2a,START DB2 ( comma in front of START ) MASTER ADDRESS SPACE ATTEMPTS TO START AND THEN ABEND04E. THE ABEND04E MAY CAUSE THE ARM RESTART OF DB2 ON OTHER LAPR. USER CAN IDENTIFY THE ERROR VIA DSNY005I SO ABEND04E IS NOT NECESSARY.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 for z/OS users. * **************************************************************** * PROBLEM DESCRIPTION: * * If Db2 has not yet started, an * * invalid -START DB2 command causes * * ABEND04E RC00E80051, if the command * * is invalid because it includes a * * prepended comma (for example: * * -,START DB2, where a comma precedes * * the command keyword). * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** When Db2 is not started, Db2 subsystem support is designed to look for -START DB2 commands and to initiate Db2 subsystem startup to bring up the requested Db2 instance. However, a -START DB2 command with a prepended comma is not a valid Db2 command and is correctly rejected by Db2 subsystem startup. After the invalid command is rejected, Db2, by design, then issues the subject abend to terminate Db2 subsystem startup. Although this behavior is working as designed, a side effect of the Db2 abend is that Automatic Restart Management (ARM) may be triggered to cause Db2 to start up on another LPAR and this may be undesirable operationally.
Problem conclusion
Db2 has been modified so that when an invalid -START DB2 command with prepended comma is entered, Db2 subsystem support detects and rejects the command with an error message (DSN3106I) instead of initiating Db2 subsystem startup to detect and reject the command.
Temporary fix
Comments
APAR Information
APAR number
PH34047
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-02-01
Closed date
2021-02-26
Last modified date
2021-04-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
010PC2 UI74178 010PC2 010PC2 UI74179 010PC2 010PC2
Modules/Macros
DSN3EC0X
Fix information
Fixed component name
DB2 ZOS SUBSYS
Fixed component ID
5740XYR01
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B10"}]
Document Information
Modified date:
02 April 2021