At 15:40 -0600 on 01/09/2012, Jonathan Goossen wrote about Re:
IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH IN:
Shouldn't the block size be 26176. The current block size is 4*LRECL
instead of 4*(LRECL+4) as VB requires.
That is not important. So long as the block size is LRECL+4 or
g
At 17:10 -0600 on 01/09/2012, Mark Zelden wrote about Re: IDC3309I **
RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH IN:
On Mon, 9 Jan 2012 16:32:49 -0500, Robert A. Rosenberg
wrote:
Just because MAXLRECL = AVGLRECL does not mean ALL the records are
6544 long. In fact since there were only 2 erro
On Mon, 9 Jan 2012 16:32:49 -0500, Robert A. Rosenberg
wrote:
>Just because MAXLRECL = AVGLRECL does not mean ALL the records are
>6544 long. In fact since there were only 2 errors, all the other
>records were 6540 or shorter. You have the correct fix by making the
>LRECL=6548 since you need to
gt; > From: af dc
> > To: IBM-MAIN@bama.ua.edu
> > Date: 01/09/2012 09:53 AM
> > Subject: IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH
> > INVALID during DFHSM BCDS REPRO
> > Sent by: IBM Mainframe Discussion List
> >
> > Hello,
> &g
dc
> Sent: Monday, January 09, 2012 7:45 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH INVALID
> during DFHSM BCDS REPRO
>
> Hello,
> during a repro from BCDS to seq file I got the following errors:
>
> IDC3309I ** REC
At 13:19 -0600 on 01/09/2012, Mark Zelden wrote about Re: IDC3309I **
RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH IN:
On Mon, 9 Jan 2012 15:44:57 +, af dc wrote:
Hello,
during a repro from BCDS to seq file I got the following errors:
IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH IN
with communication and leadership skills checkout Woodwinds
Toastmasters
IBM Mainframe Discussion List wrote on 01/09/2012
09:44:57 AM:
> From: af dc
> To: IBM-MAIN@bama.ua.edu
> Date: 01/09/2012 09:53 AM
> Subject: IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH
> I
, January 09, 2012 2:20 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH INVALID
during DFHSM BCDS REPRO
On Mon, 9 Jan 2012 15:44:57 +, af dc wrote:
>Hello,
>during a repro from BCDS to seq file I got the following errors:
>
&g
On Mon, 9 Jan 2012 15:44:57 +, af dc wrote:
>Hello,
>during a repro from BCDS to seq file I got the following errors:
>
>IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH INVALID
>IDC3309I ** RECORD X'C5E7D7F2F1' NOT WRITTEN. LENGTH INVALID
>
>jcl repro:
>//BCDS#RI EXEC PGM=IDCAMS,COND=
Hi Elardus,
DFHSM were out on all lpars.
A.Cecilio
On Mon, Jan 9, 2012 at 4:49 PM, Elardus Engelbrecht
wrote:
> af dc wrote:
>
>>during a repro from BCDS to seq file I got the following errors:
>>IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH INVALID
>>IDC3309I ** RECORD X'C5E7D7F2F1' NOT
af dc wrote:
>during a repro from BCDS to seq file I got the following errors:
>IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH INVALID
>IDC3309I ** RECORD X'C5E7D7F2F1' NOT WRITTEN. LENGTH INVALID
>How can I correct these 2 records ??
Was HSM active during your IDCAMS job? Shutdown all HS
Hello,
during a repro from BCDS to seq file I got the following errors:
IDC3309I ** RECORD X'2BC5E7D7F2' NOT WRITTEN. LENGTH INVALID
IDC3309I ** RECORD X'C5E7D7F2F1' NOT WRITTEN. LENGTH INVALID
jcl repro:
//BCDS#RI EXEC PGM=IDCAMS,COND=(0,NE)
//SYSPRINT DD SYSOUT=*
//BCDSIN DD DSN=HSM.BCDS,D
12 matches
Mail list logo
