ANR2788E and ANR1905E when trying to start the server

Resolving The Problem

The directory path values in dsmserv.opt (eg: ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY) are case sensitive on both Windows and Unix systems.

First, verify the path to the log directory exists on the file system.
The log path values in DB2 must match the values in dsmserv.opt. If DB2 reports the “Path to log files” as E:\tsmdata\log, then ACTIVELOGDIRECTORY should be E:\tsmdata\log instead of e:\tsmdata\log.

In order to get the log path values, open a DB2 command prompt and issue:
db2 connect to tsmdb1
db2 get db cfg for tsmdb1

Look for the following values in the DB2 output:
Path to log files = E:\tsmdata\log\
Overflow log path (OVERFLOWLOGPATH) = e:\tsmdata\archlog\RstDbLog\
First log archive method (LOGARCHMETH1) = DISK:e:\tsmdata\archlog\archmeth1\
Failover log archive path (FAILARCHPATH) = e:\tsmdata\archlog\failarch\

Note: It is not recommended to change the DB2 values. Edit the dsmserv.opt to reflect the DB2 values.

Based on the values above, the dsmserv.opt values should be:
ACTIVELOGDIRECTORY E:\tsmdata\log
ARCHIVELOGDIRECTORY e:\tsmdata\archlog

This error has also been seen when the path to the directory contains a space. For instance:
C:\Program Files\Log. Use the 8.3 naming convention. (eg: progra~1). From a DOS Command prompt, issuing "dir /x" will reveal the 8.3 naming convention for directories.