DBG37006E MIB 19:30:05 DB2 CALL FOR IFI CALL RESULTED IN FRB RETCODE 0100 AND FRB REASON CODE 00F30018
Article ID: 203945
Updated On:
Products
Issue/Introduction
CA Datacollector Started task IDB2DCSC job abends daily at a particular time(19:30 PST) in Production.
Below is the Information found from DBGPRINT
DBG43004I MIB 19:30:05 IFI FUNCTION READA COMPLETED WITH RETURN CODE 0100 AND REASON CODE 00F30018
DBG37006E MIB 19:30:05 DB2 CALL FOR TERMINATE THREAD RESULTED IN FRB RETCODE 0100 AND FRB REASON CODE 00F30018
DBG37005I MIB 19:30:05 DATA COLLECTOR DISCONNECTED FROM DB2 SUBSYSTEM MIB
DBG39038I MIB 19:30:05 TERMINATION STARTED FOR DATA COLLECTOR FOR DB2 SUBSYSTEM MIB
DBG84003I MIB 19:30:05 HEALTH CHECKER SUBTASK TERMINATING
DBG84004I MIB 19:30:05 HEALTH CHECKER SUBTASK TERMINATION COMPLETE
Environment
Release : 20.0
Component : CA SYSVIEW Performance Management Option for DB2 for z/OS
Resolution
The Data Collector userID needs to be granted EXECUTE on the CA-Insight explain plan, referenced in the PLANSxx member of the CDBAPARM. The IDGRANT in the .SOURCE library contains a sample GRANT EXECUTE statement.
See the following link for more about it. Security/db2-authorizations
Notes: Pay attention to whether initialization completed or not. The run time will be less than a minute if the IDGRANT was not done generally and the return and reason codes would have to match the one in the problem description.
Feedback
