> Looking at what you had at that point should be a strong clue. (and
then manually delete the dataset).
After I found out he did his research, I gave a few hints.
Here's the biggest one though:
Look at the input size!
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
---
Rex
You are spot on. Sorry Rohit.
--- On Wed, 8/3/11, Pommier, Rex R. wrote:
From: Pommier, Rex R.
Subject: Re: IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS
(04034379)
To: IBM-MAIN@bama.ua.edu
Received: Wednesday, August 3, 2011, 9:32 AM
Willie,
Not quite. I thought the
Can you try to increase unit from unit=sysda to unit=(sysda,20)
it's only a sample but this space error except for vam message may seems too
easy to solve...
and if I can, I'd suggest you to read sort manual to setup properly your
statement i.e. using dynalloc and usize command.
regards
-
bunter
Sent: Wednesday, August 03, 2011 11:19 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS
(04034379)
Rohit,
Your input dsn and output dsn is the same. Your output dsn is the same name as
the GDG base P1OPSBP.FC610.NVFF411A. Verify your
, DIAGNOSTIC INFORMATION IS
(04034379)
Rohit,
Your input dsn and output dsn is the same. Your output dsn is the same name as
the GDG base P1OPSBP.FC610.NVFF411A. Verify your output dsn.
--- On Wed, 8/3/11, Rohit Bhandari wrote:
From: Rohit Bhandari
Subject: Re: IEC614I EXTEND FAILED - RC 000
Rohit,
Your input dsn and output dsn is the same. Your output dsn is the same name as
the GDG base P1OPSBP.FC610.NVFF411A. Verify your output dsn.
--- On Wed, 8/3/11, Rohit Bhandari wrote:
From: Rohit Bhandari
Subject: Re: IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS
ender: IBM Mainframe Discussion List
Date: Wed, 3 Aug 2011 17:42:37
To:
Reply-To: IBM Mainframe Discussion List
Subject: Re: IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS
(04034379)
Hi ,
This is the JCL code
//NVF411A EXEC PGM=SORT
//SYSPRINT DD SYSOUT=*
//SYSOUTDD SYSOUT=*
//S
itter: @TedMacNEIL
-Original Message-
From: Rohit Bhandari
Sender: IBM Mainframe Discussion List
Date: Wed, 3 Aug 2011 17:42:37
To:
Reply-To: IBM Mainframe Discussion List
Subject: Re: IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS
(04034379)
Hi ,
This is the JCL
Hi ,
This is the JCL code
//NVF411A EXEC PGM=SORT
//SYSPRINT DD SYSOUT=*
//SYSOUTDD SYSOUT=*
//STEPLIB DD DSN=SYS1.SORTLIB,DISP=SHR
//SORTWK01 DD SPACE=(CYL,(100,100),RLSE),UNIT=DISK
//SORTWK02 DD SPACE=(CYL,(100,100),RLSE),UNIT=DISK
//SORTWK03 DD SPACE=(CYL,(100,100),RLSE),UNIT=DISK
//
>IEC032I
E37-08,IFG0554P,NVF411,NVF411A,SORTOUT,620F,BTCP51,04034379,P1OPSBP.FC610.NVFF411
Did you even attempt to look up this message?
-
Ted MacNEIL
eamacn...@yahoo.ca
Twitter: @TedMacNEIL
--
For IBM-MAIN subscribe / signoff
Which kind of file are you allocating?
And what are allocation space options?
Have you tried specifing
//*VAMBYPAS* DD DUMMY
Regards.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.
I ended up adding space to the
> respective Storage Groups , still it persists .
>
> VAMEX37 NVF411 P1OPSBP.FC610.NVFF411A SECONDARY EXTENT DOUBLED 400
> IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS (04034379) , 490
> NVF411A, ,P1OPSBP.FC610.NVFF411A
Hello members,
We are facing this issue for last few days , I ended up adding space to the
respective Storage Groups , still it persists .
VAMEX37 NVF411 P1OPSBP.FC610.NVFF411A SECONDARY EXTENT DOUBLED 400
IEC614I EXTEND FAILED - RC 000, DIAGNOSTIC INFORMATION IS (04034379) , 490
NVF411A
13 matches
Mail list logo
