DBG21023E HISTORY: FILE HISTACCT INVALID HISTORY FILE.

Document ID : KB000030732
Last Modified Date : 14/02/2018
Show Technical Document Details

QUESTION/PROBLEM:

Using the following JCL in Unloading the HISTACCT and HISTSTAT,

 

//HISTUNLD EXEC PGM=IDB2UIFI,REGION=5M, 

// PARM=('/REQ=UNLDHIST,DBSUB=DB2D,DBLOC=DB2D,', 

// 'REMPOS=NO,UNLD=ALL,UNLTYP=ALL,UNLCHD=YES') 

//STEPLIB DD DISP=SHR, 

// DSN=DB2.PLATINUM.USER.CDBALOAD 

//HISTSTAT DD DISP=SHR,DSN=DB2.PLATINUM.R17.IDB2VSAM.USR.HSTACCTG 

//HISTACCT DD DISP=SHR,DSN=DB2.PLATINUM.R17.IDB2VSAM.USR.HSTSTATS 

//* 

the job failed with the following messages: 

DBG39049I 07:26:00 INITIALIZING CA-INSIGHT 17.0 SP0 

DBG73100I 07:26:00 INITIALIZING LDS FILE UTILITY PROGRAM 

DBG73102I 07:26:00 INPUT PARAMETERS: REQ=UNLDHIST,DBSUB=DB2D,DBLOC=DB2D,,RE 

DBG21023E DB2D 07:26:01 HISTORY: FILE HISTACCT INVALID HISTORY FILE. 

DBG36017E DB2D 07:26:01 OPEN FAILED FOR DDNAME HISTACCT 

DBG73107I DB2D 07:26:01 LDS FILE UTILITY PROGRAM COMPLETED RC= 8 

DBG98003I DB2D 07:26:01 ROUTINES USED 49152 BYTES OF GETMAIN STORAGE 

 

ANSWER:

The problem is caused by the swapping of the datasets for HISTACCT DD to HISTSTAT and HISTSTAT DD to HISTACCT.

//HISTSTAT DD DISP=SHR,DSN=DB2.PLATINUM.R17.IDB2VSAM.USR.HSTACCTG <=========WRONG

//HISTACCT DD DISP=SHR,DSN=DB2.PLATINUM.R17.IDB2VSAM.USR.HSTSTATS <=========WRONG

 

Changing it to the correct DD as below:

//HISTSTAT DD DISP=SHR,DSN=DB2.PLATINUM.R17.IDB2VSAM.USR.HSTSTATS  ====>CORRECT

//HISTACCT DD DISP=SHR,DSN=DB2.PLATINUM.R17.IDB2VSAM.USR.HSTACCTG ====>CORRECT 

 

Fixing that resolved the problem.