|
View previous topic :: View next topic
|
| Author |
Message |
srikanth_dyta
New User
Joined: 05 Jun 2003
Posts: 1
Location: NOIDA
|
|
|
|
While converting a OS/VS Cobol program to Enterprise Cobol program, I am getting a FILE STATUS 39 error.
Error in the spool indicates that there is a mismatch between program's input record length and that of the dataset's LRECL.
Please provide a good solution for this. |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
| Make the program's input record length match the data set LRECL -- the best (and only viable) solution. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
I'm from the generation of Enterprise Cobol -- but does that really make a diffenrece whether you use OS/VS Cobol or Enterprise Cobol if the problem statement is about "LRECL mismatch"?
Usually in such situation it gives U4038 at my shop. |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| FILE STATUS 39 could be any file attribute, not just LRECL. Are you certain it's a LRECL problem? Is the file an ISAM file by any chance instead of a VSAM file? |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Oh Terry...
| Terry Heinze wrote: |
| FILE STATUS 39 could be any file attribute, not just LRECL. Are you certain it's a LRECL problem? |
| Quote: |
| Error in the spool indicates that there is a mismatch between program's input record length and that of the dataset's LRECL. |
|
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| Anuj Dhawan wrote: |
Oh Terry...
| Terry Heinze wrote: |
| FILE STATUS 39 could be any file attribute, not just LRECL. Are you certain it's a LRECL problem? |
| Quote: |
| Error in the spool indicates that there is a mismatch between program's input record length and that of the dataset's LRECL. |
|
I need to be convinced it was a logical record length problem. A copy/paste of the actual error message would be preferable to taking someone's word for what the error was.  |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
Terry, I agree with you.
If 'error in spool indicates there is a mismatch between...' is true,
why the post?
seems a rather obvious solution. But experience in the forum has shown that - posters don't know what the problem is
- and they do not describe the problem sufficiently or accurately
taking things for granted and making assumptions are the reasons that
posters have 'unsolvable' problems.
I have decided not to make suggestions (other that sarcasitc ones) until
the problem is explained and all the relevent info is available. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Yeah, FILE STATUS 39 is quite generic to start with... |
|
| Back to top |
|
|
|
|
