Willie: I would suggest if you havent all ready looking at this IEC message IEC331I 050-096(00000000,M2BRS1),IF00DCOL,DATASET,VMMC,IGG0CLE2
----------------------------------------------------------- IEC331I rc-crs[sfierror],jjj, sss,proc[func],mmm VOL,ser,NAME,dsname Explanation: An error condition was detected while processing a catalog management request directed to either a VSAM or an ICF catalog. See message IDC3009I for an explanation of the return and reason codes. Note: If rc-crs is 004-33 or 04-34, a VSAM catalog was OPENed. IBM support for VSAM catalogs will end January 1, 2000. This message is intended to help identify VSAM catalogs that are still in use. If you need to use a VSAM catalog after December 31, 1999, you must convert it to an ICF catalog. To do this, use facilities such as the IDCAMS CNVTCAT command. For more details on 004-33 and 004-34, see message IDC3009I. In the message text: rc The return code. crs The catalog reason code. sfierror Hexadecimal fullword of information that further describes the error; this information appears only if an invoked subfunction (SFI) detected the error. The meaning depends on the possible combinations of the return code and the reason code. jjj The job name. sss The step name. proc The name of the VSAM catalog management procedure that caused the message to be issued. (The name omits the IGGP prefix.) func Indicates that an error occurred during the VSAM catalog/ACB open process. mmm The name of the VSAM catalog management control section (CSECT) that detected the error condition. ser The volume serial number. dsname The data set name or component name. System action: The command is ended. Application Programmer Response: See programmer response for the specific return code and reason code in message IDC3009I. System programmer response: If the error recurs and the program is not in error, look at the messages in the job log for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the SYSOUT output for the job. Source: DFSMSdfp Routing Code: 2,11 Descriptor Code: 6 Regards, Scott J Ford Software Engineer http://www.identityforge.com ________________________________ From: willie bunter <[email protected]> To: [email protected] Sent: Monday, May 7, 2012 10:06 AM Subject: Re: IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD Richard, Here it is: Organization . . . : PS Record format . . . : VB Record length . . . : 340 Block size . . . . : 27998 1st extent cylinders: 5 Secondary cylinders : 5 Data set name type : SMS Compressible. . : NO Current Allocation Allocated cylinders : 45 Allocated extents . : 9 Current Utilization Used cylinders . . : 5 Used extents . . . : 1 The VVDS is okay for the 2 volumes mentiond. Could it be that the dsn has been corrupted? ________________________________ From: Richard Marchant <[email protected]> To: [email protected] Sent: Monday, May 7, 2012 9:52:02 AM Subject: Re: IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD Willie, What DCB info do you have for SMVS1.DCOLLECT.DATASETS.JOUR ?? I would suggest it be RECFM=VB LRECL=644 List the VTOCS on volumes PFX007 and PROD36 just check they are good, if not may be a rebuild of the INDEX VTOCs might help. Richard Marchant -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of willie bunter Sent: 07 May 2012 02:39 PM To: [email protected] Subject: Re: IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD Richard, Here is the JCL: //* //DATASET EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //OUTPUT DD DSN=SMVS1.DCOLLECT.DATASETS.JOUR,DISP=OLD //SYSIN DD * DCOLLECT OUTFILE(OUTPUT) VOLUMES(*) /* //* //VOLUME EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //OUTPUT DD DSN=&&TEMP,DISP=(NEW,PASS,DELETE), // UNIT=SYSDA,SPACE=(TRK,(1,1)), // DSORG=PS,RECFM=VB,LRECL=264 //SYSIN DD * DCOLLECT OUTFILE(OUTPUT) VOLUMES(*) NODATAINFO /* //* //INF0DCOL EXEC PGM=INF0DCOL,COND=(0,LT,VOLUME) //RECIN DD DSN=&&TEMP,DISP=(OLD,DELETE) //RECOUT DD DSN=SMVS1.DCOLLECT.VOLUMES.JOUR,DISP=OLD //* //MERGE EXEC PGM=IEBGENER,COND=((0,LT,VOLUME),(0,LT,INF0DCOL)) //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=SMVS1.DCOLLECT.VOLUMES.JOUR,DISP=OLD //SYSUT2 DD DSN=SMVS1.DCOLLECT.VOLUMES.ACCUM,DISP=MOD //SYSIN DD DUMMY At step DATASET it puts out the COND=0008. However the job continues to its entirety. ________________________________ From: Richard Marchant <[email protected]> To: [email protected] Sent: Monday, May 7, 2012 8:27:14 AM Subject: Re: IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD Willie, Please post the JCL use used. Richard Marchant -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of willie bunter Sent: 07 May 2012 02:20 PM To: [email protected] Subject: Re: IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
