Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

OS/VS Cobol to Enterprise Cobol conversion error

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics
View previous topic :: :: View next topic  
Author Message
srikanth_dyta

New User


Joined: 05 Jun 2003
Posts: 1
Location: NOIDA

PostPosted: Wed Sep 02, 2009 2:11 pm    Post subject: OS/VS Cobol to Enterprise Cobol conversion error
Reply with quote

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
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8117
Location: East Dubuque, Illinois, USA

PostPosted: Wed Sep 02, 2009 3:20 pm    Post subject:
Reply with quote

Make the program's input record length match the data set LRECL -- the best (and only viable) solution.
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Wed Sep 02, 2009 4:29 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA

PostPosted: Wed Sep 02, 2009 7:59 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Wed Sep 02, 2009 8:04 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA

PostPosted: Wed Sep 02, 2009 8:27 pm    Post subject:
Reply with quote

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. icon_smile.gif
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6968
Location: porcelain throne

PostPosted: Wed Sep 02, 2009 8:46 pm    Post subject:
Reply with quote

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
  1. posters don't know what the problem is
  2. 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
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Thu Sep 03, 2009 11:56 am    Post subject:
Reply with quote

Yeah, FILE STATUS 39 is quite generic to start with...
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> All Other Mainframe Topics All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts XML Parse for COBOL 5.2 Bhanu Praveen COBOL Programming 1 Sat Jul 08, 2017 8:58 pm
No new posts Dynamic output file creation in cobol... smileheal COBOL Programming 7 Thu Jun 15, 2017 10:53 pm
No new posts Search utility(3.14) using JCl and Cobol RKS3 COBOL Programming 12 Sat Jun 10, 2017 10:24 pm
No new posts COBOL DB2 program - zIIP eligible vasanthz COBOL Programming 7 Wed May 31, 2017 5:12 am
No new posts DB2 Program abending without giving a... rahulgarg14 DB2 7 Mon May 29, 2017 8:10 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us