View previous topic :: View next topic
|
Author |
Message |
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
Daniel Prosser wrote: |
Don, the problem has been resolved now - thanks anyway.
Daniel |
Wait wait wait wait... so what was the fix?
I didn't see this thread originally in April, but it bumped today. I don't see what the actual resolution was.
Whenever I get a wrong length record, it's usually a blank file or a temp file that has taken an extent.
The blank file happens when a file is allocated in a previous step, but never actually opened. I usually make that happen by having the wrong DD name on an output file. I'm sure there is a proper name for that besides "blank."
If you are using a temp file, and it takes an extent, other steps can't see the data on the extent(s). That is an IBM restriction. It can cause this to happen, but I would expect to see a short file instead since this is a fixed length record. |
|
Back to top |
|
|
Daniel Prosser
New User
Joined: 05 Nov 2010 Posts: 57 Location: Amsterdam
|
|
|
|
Ed,
the problem was with a DB2 utility that was still running. we terminated the utility and it ran fine.
Dan. |
|
Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
I don't think that's what actually caused the wrong record length.
Did the extract step fail, leaving an empty file, then the next step tried to read that bad file?
It's important to know the difference. If there's something else that is causing this problem, I want to know in case I run into it again. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
probably the suggestion id coming a little late ...
You replied to a topic that was started about three years ago and has been dormant for about a year and a half.
and the utility was reported on ...
Quote: |
Thu Oct 11, 2012 8:37 am |
as having been already terminated
Quote: |
the problem was with a DB2 utility that was still running. we terminated the utility and it ran fine.
|
|
|
Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008 Posts: 1249 Location: Richfield, MN, USA
|
|
|
|
I would hope that after a year and a half, the Thread Starter has found a solution. |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
I've PM'd and will tidy the rest of this new stuff away shortly... |
|
Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009 Posts: 582 Location: London
|
|
|
|
We had a similar issue which turned out to be due to the SYSREC file being in compressed format. If you change it to a standard non-compressed file it might work.
Oops sorry, just realised this was an old post sorry! |
|
Back to top |
|
|
|