SYSVIEW for DB2 Data Collector started task finished with RC=0052 during start up
Article ID: 276023
Updated On:
Products
Issue/Introduction
After an upgrade to SYSVIEW for Db2 the Data Collector started task finished with RC=0052 and it was purged from the JES2 output.
DBG39049I ... INITIALIZING SYSVIEW FOR DB2 20.0
DBG39019I SSID ... HIGHEST MAINT LEVELSET IS 20.0.06
DBG99001E SSID ... ERROR IN COMMAND STREAM, PROCESSING ENDED
DBG39039I SSID ... TERMINATION COMPLETE FOR DATA COLLECTOR FOR DB2 SUBSYSTEM SSID
...
-JOBNAME STEPNAME PROCSTEP RC EXCP CONN TCB SRB
-IDB2DC IDB2DC 52 nnn nn .00 .00
IEF404I IDB2DC - ENDED - TIME=hh.mm.ss
-DB2IDB2 ENDED. NAME- TOTAL TCB CPU TIME= .00
TOTAL ELAPSED TIME= .0
$HASP395 IDB2DC ENDED - RC=0052
R nnnn,L
IEE600I REPLY TO nnnn IS;L
$HASP250 IDB2DC PURGED
Resolution
The cause of the RC=0052 is the following error message:
DBG99001E SSID ... ERROR IN COMMAND STREAM, PROCESSING ENDED
The message classes in the JES2 output have to be investigated. The IDB2DC Job was writing to SYSOUT=* (PRT='*' in the proc). Since the proc has no JOB statement the "*" will default to something. It is probably defined as a message class that is automatically purged because of the RC=0052.
Review the JES2 Spool output and check which MSGCLASS values that stay in the Spool. Then, code a JOB card with that MSGCLASS on the IDB2DC Data Collector proc.
The REQLIB parameter in the Data Collector has to be checked as well.
REQLIB=('HLQ.REQUESTS',
'HLQ.CDBATREQ')
The HLQ.CDBATREQ library should be at the same level as the maintenance applied over the HLQ.CDBALOAD load library.
Additionally double check HLQ.REQUESTS library to be sure there is not any old Request that has not the maintenance applied.
A Request without the maintenance applied might cause problems during the Data Collector start up as the library is concatenated first.
Feedback
