Richard,
 
Do I rebuild the INDEX VOLUME for volume M2BRS1 ?  

________________________________
From: Richard Marchant <[email protected]>
To: [email protected] 
Sent: Monday, May 7, 2012 8:14:12 AM
Subject: Re: IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD

Willie,

Try rebuilding the INDEX VTOC by using the following and then rerun the 
DCOLLECT:

//STEP1    EXEC PGM=ICKDSF                                
//SYSPRINT DD SYSOUT=*                                    
//VOLDD    DD UNIT=(3390,,DEFER),VOL=(PRIVATE,SER=volser),
//        DSN=SYS1.VTOCIX.volser,DISP=SHR                
//SYSIN    DD *                                          
  BUILDIX DDNAME(VOLDD) OSVTOC                            
//                                                        

//STEP1    EXEC PGM=ICKDSF                                    
//SYSPRINT DD SYSOUT=*                                        
//VOLDD    DD UNIT=(3390,,DEFER),VOL=(PRIVATE,SER=volser),    
//        DSN=SYS1.VTOCIX.volser,DISP=SHR                    
//*        SPACE=(TRK,10,,CONTIG)                              
//SYSIN    DD *                                                
  BUILDIX DDNAME(VOLDD) IXVTOC
//                                


Richard Marchant

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
willie bunter
Sent: 07 May 2012 02:03 PM
To: [email protected]
Subject: IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD

Good Day To All,

For the past 2 days a DCOLLECT batch job has been failing because of the 
following :
IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD.  I am able to access the 
volume.  The volume is not SMS managed and the INDEX STATUS of the volumes is 
enabled.  I GOOGLED the error messages but I didn't find anything that would 
recommend a fix to the problem.  I am not sure if the dsn it writes out the 
output to is corrupt or something else.  The VVDS error message appear for 
several volumes and dsns.  Below is an example:

.IDCAMS  SYSTEM SERVICES                                         
.                                                                
. DCOLLECT OUTFILE(OUTPUT) VOLUMES(*)                            
.IDC3302I  ACTION ERROR ON SMVS1.DCOLLECT.DATASETS.JOUR          
.IDC3309I ** RECORD X'01900000C4' NOT WRITTEN.  LENGTH INVALID   
.IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD FOR         
.IDC21809I SYS1.VVDS.VPFX007 ON VOLUME PFX007       
IDC3302I  ACTION ERROR ON SMVS1.DCOLLECT.DATASETS.JOUR         
IDC3309I ** RECORD X'01900000C4' NOT WRITTEN.  LENGTH INVALID  
IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD FOR        
IDC21809I SYS1.VVDS.VPROD36 ON VOLUME PROD36                   

I noticed the following in the JESMSGLG
IAT1600 JOB IF00DCOL (J0162246) LINES EXCEEDED BY 300,000        
IEC331I 050-096(00000000,M2BRS1),IF00DCOL,DATASET,VMMC,IGG0CLE2  
  
Could the problem be caused by the above error message?  I am not sure where 
the problem could be.  Could anybody suggest a solution if possible?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to