CA Bind Analyzer for DB2 for z/OSCA DetectorCA SQL-Ease for DB2 for z/OSCA Sysview Performance Management Option for DB2 for z/OSCA Database Detector for DB2 for z/OSCA Plan Analyzer for DB2 for z/OSCA Subsystem Analyzer for DB2 for z/OS
When I tried to unload our history data from the history files by using the IDB2UIFI utility, the unload job failed with the following error messages. The job failed with RC=8. DBG73110E DB2S 16:13:06 UNABLE TO COMMUNICATE WITH DATA COLLECTOR. DBSUB=DB2S, D DBG73117E DB2S 16:13:06 FAILING REQUEST CODE: POSTHIST AND TYPE: TCLOSE How should I do?
The execution jcl is was follows. //FUNLDHST JOB '073',MSGCLASS=9,CLASS=F,NOTIFY=&SYSUID //* //IDB2UNLD PROC DBSUB=DB2S, DB2 subsystem name. //* // DBLOC='DB2S', Used w/DBSUB and TESTVER to identify //* the data collector owning the //* history files. // REMEMBR=YES, Keep track of last data unloaded //* for subsequent UNLOAD=NEW option. //* REMEMBR=NO, Do not keep track of last data //* unloaded. // TESTVER=R180, Option used W/DBSUB and DBLOC to //* uniquely identify data collector. //* // UNLOAD=NEW, Unload only the records added since //* the last unload using REMEMBER=YES //* was executed. //* UNLOAD=ALL, Unload all records in the file(s). //* //* UNLDTYP=ALL, Unload both accounting and //* statistics files. // UNLDTYP=ACCTG, Unload accounting file only. //* UNLDTYP=STAT Unload statistics file only. //* // UNLDCHD=YES Unload DB2 parent and child records //* for parallelism threads. NO causes //* the utility to unload CA SYSVIEW for //* parallelism summary records only and //* not the individual parent and child //* records. //*------------------------------------------------------------------- //S01 EXEC PGM=IDB2UIFI,REGION=5M, // PARM=('/REQ=UNLDHIST,DBSUB=&DBSUB,DBLOC=&DBLOC,', // 'REMPOS=&REMEMBR,TESTV=&TESTVER,', // 'UNLD=&UNLOAD,UNLTYP=&UNLDTYP,UNLCHD=&UNLDCHD') //* //STEPLIB DD DISP=SHR, // DSN=CADB2.V18R0M0.DB2V.CDBALOAD //* //SMFOUT DD DISP=(,CATLG,DELETE), ONLINE HISTORY ARCHIVE // DSN=CADB2.V18R0M0.IDB2S.HSTACCTG.BK190129, // SPACE=(CYL,(200,200),RLSE), // UNIT=DASD, // VOL=SER=FB79DI, // DCB=(RECFM=VBS,LRECL=32760,BLKSIZE=4096) //* //SYSPARMS DD DUMMY //DBGPRINT DD SYSOUT=9 //SYSUDUMP DD SYSOUT=9 //PTIPARM DD DISP=SHR, // DSN=CADB2.V18R0M0.CDBAPARM.DB2V //PTILIB DD DISP=SHR, // DSN=CADB2.V18R0M0.DB2V.CDBALOAD // PEND //UNLOADS EXEC IDB2UNLD
MF. Mainframe, DB2, IDB2, z/OS
The TESTVER parameter in the IDB2UIFI job was specified as the following. TESTVER=R180 (Because the client uses R18.0, it should be specified as R180. If R19.0 is used, it should be specified as R190.) However, the TESTVER parameter in the IDDCPARMS member was commented out as follows. (The IDDCPARMS is usually specified in the SYSPARMS DD in the Data Collector.) * TESTVER=R180
Please see the explanation of the TESTVER parameter in the Reference Guide. TESTVER=xxxx Specifies a 1-4 character identifier for a separate unique data collector, which can be started on the same DB2 subsystem as another data collector. Default: Rxxy, where xx is the version number and y is the release number or space if the release number is zero. For example, r12.0 has a default TESTVER of R12 , r12.1 has a default TESTVER of R121.
Threfore, "R18" was set for the TESTVER vaule of your data collector as the default. (because the TESTVER parameter in their IDDCPRMS was commented out.)
You should do one of the following. 1. Specify the TESTVER=R18 in the IDB2UIFI job and rerun the job. 2. Remove the asterisk(*) for the TESTVER=R180 line in the IDDCPARMS and recycle the data collector and rerun the IDB2UIFI job.
Additional info; The following parameter values should be synchronized between a data collector and the IDB2UIFI job. DBSUB, DBLOC, TESTVER