Chapter 18. Troubleshooting and tracing 387
/SM590000Problem: When you run the arsdb -I ARCHIVE -vu command from a BPXBATCH job, you 
see errors in STDOUT or in the output of arsdb -c, as shown in Figure 18-8.
Figure 18-8   ARSDB error
Reason or resolution: Enter an export command for DSNAOINI in the BPXBATCH job, or 
ensure that export DSNAOINI='/etc/ars/cli.ini' was defined. Verify that your cli.ini 
file is in this directory. Also, check that your cli.ini file references the correct DB2 
subsystem, for example:
[COMMON] 
MVSDEFAULTSSID=DB1M 
[DB1M] 
PLANNAME=DSNACLI
/SM590000Problem: During installation and migration, when you run arsdb -u -I or arsdb -I 
ARCHIVE -vx ARSSYS, you receive an error similar to Figure 18-9.
Figure 18-9   ARSDB error during installation and migration
Reason or resolution: Multiple resolutions can be attempted when you encounter this 
error:
– Check the ARSSOCKD region parameter. We recommend that you use region=0. Also, 
check your TSO logon region size. Increase TSO, log out of TSO, and log back in.
– When you run export (x), the contents of the ARSxxx table are exported to a flat file. 
The command attempts to write the file to the directory in which the arsdb command 
runs. Ensure that the user has write permissions for the file. Also, ensure that the user 
has permissions for the ARS_TMP intermediate file.
– Check the OMVS size to see whether it can be increased to the system limit 
(D OMVS,L). Check your OMVS limits: MAXMMAPAREA and MAXSHAREPAGES. The 
following example is output of the D OMVS,L command:
CURRENT    HIGHWATER     SYSTEM
USAGE USAGE LIMIT
MAXMMAPAREA    3107  3107 4096
The example shows current MAXMMAPAREA is 3107 and the maximum size that 
MAXMMAPAREA can go is 4096. In our experience, version 8.5 required at least 3646 
for the value of MAXMMAPAREA. In this example, the minimum memory size needed 
for CMOD will be 3107 + 3646 = 6753. Therefore, you must increase the 
MAXMMAPAREA from 4096 to a higher value, for example, 40960, to solve the 
problem.
DB Error: {DB2 for OS/390}{ODBC DRIVER} SQLSTATE=58004 ERRLOC=2:170:9 
CAF “CONNECT” failed using DB2 system:DB2K 
RC=08 and REASON=00f30002 -- SQLSTATE=58004, SQLCODE=-99999 
arsdb:.Unable to connect to DB2 ARSDBASE database 
or
arsdb: Unable to determine the database engine
arsdb -u -I 
CEE3204S The system detected a protection exception (System Completion 
Code=0C4). 
         From entry point u_file_write_44_arsxh at compile unit offset 
+00000054 at entry offset +00000054 at address