IDB2 IDOBLOAD BATCH JOB FAILED WITH DBG39047E PC OWNER DBGI HAS NOT YET BEEN STARTED

book

Article ID: 209507

calendar_today

Updated On:

Products

CA Sysview Performance Management Option for DB2 for z/OS

Issue/Introduction

 

Running the IDOBLOAD in batch the job failed with the following error message:

DBG39047E      13:45:38 PC OWNER DBGI HAS NOT YET BEEN STARTED

 

Environment

Release : 20.0

Component : CA SYSVIEW Performance Management Option for DB2 for z/OS

Resolution

Add the TESTVER and PCSSID parms to the SYSPARMS list for the Batch UI step of IDOBLOAD and rerun the job. The Batch UI is attempting to connect to an active DC in the same manner as the Online UI.  So if you are not using the default values for PCSSID and TESVER in your PC and DC started tasks, you will need to supply them in the parms for the  Batch UI job.