MVSFORUMS.com

venkat · Guest

Hi,
For one of the Programs namely batch program in production one of the variables namely description varies from 1 to 3500.But it is not working for (If we compile with E.Cobol),the program abends with FILE_STATUS '44'.it is working fine when we complie with os/vs cobol.we are doing telon to cobol conversion.for that we are compiling the telon program with OS/VS Cobol and the converted one with Enterprise cobol.iam enclosing the following code below.first statement description is for telon program.second one is for converted program.If i am not changing from 1 to 0 in the occurs clause in the second one i am getting U4094 Abend ie i am compiling with Enterprise cobol.First statement is compiled with OS/VS Cobol.If i am changing the second statement to from 1 to 0 i am getting return code 0.But i am getting empty output file.i have to compare the output file between the telon program and the converted one .I should not get any differences between the two output files when i compare.can you kindly tell me how to resolve this problem.

kolusu · Posted: Wed Aug 11, 2004 4:50 am Post subject:

Venkat,

please open posts with more meaningful topics. A title like 'abend' does not tell anything. Also choose the approriate forum. Abends & debugging go into the Problem determination forum. I am editing the title to reflect the post and also moving this post to the problem determination forum.

A file status code of 44 means that A boundary violation exists because an attempt was made to rewrite a record to a file and the record was not the same size as the record being replaced, or an attempt was made to write or rewrite a record that was larger than the largest or smaller than the smallest record allowed by the RECORD IS VARYING clause of the associated file-name.

Possible causes are:

Attempting to WRITE or REWRITE a record that is larger than the largest, or smaller than the smallest record allowed by the RECORD IS VARYING clause of the associated file
Attempting to REWRITE a record to a file and the record is not the same size as the record being replaced.

So I would check your file declaration and the write paragraph to see if the any of the above is true.

Hope this helps...

Cheers

kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

venkat · Guest

Hi,
I have checked for both the telon and the converted one.I am enclosing the jcl below.both are having varying record lengths.Logical record length is the same.

Telon Version
//DD1 DD DSN=A1.A2.A3(+1),DISP=(,CATLG,DELETE),
// UNIT=SYSDA,
// DCB=MODDSCB,RECFM=VB,BLKSIZE=0,LRECL=3511,DSORG=PS),
// SPACE=(3511,(10,1),RLSE),AVGREC=K

Converted version

/DD2 DD DSN=A4.A5.A6,DISP=(,CATLG,DELETE),
// UNIT=SYSDA,
// DCB=MODDSCB,RECFM=VB,BLKSIZE=0,LRECL=3511,DSORG=PS),
// SPACE=(3511,(10,1),RLSE),AVGREC=K

Regards

Venkat

kolusu · Posted: Wed Aug 11, 2004 5:59 am Post subject:

venkat,

Did you miss reading this statement in my program?

venkat · Guest

Hi Kolusu,
Any updates on my problem.

Regards

Venkat

kolusu · Posted: Thu Aug 12, 2004 7:34 am Post subject:

venkat · Guest

Hi Kolusu,
After the write statement it is giving file status code 44 if it is same as the production copybook like 1 to 3500 times.Before the write statement it was 0 and after the write statement it is giving 4094 abend for the converted code.But if we change the copybook like 0 to 3500 times it is not giving abend but an empty output file is created.I am not able to compare the output files between the telon version and the converted version.Could you tell me any information how to go about for the variable length record in enterprise cobol.

Venkat

kolusu · Posted: Thu Aug 12, 2004 10:36 am Post subject:

venkat,

Go thru the solution posted by me in this topic.

http://www.mvsforums.com/helpboards/viewtopic.php?t=2733

Also check this link which explains in detail about Requesting variable-length format

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IGY3PG10/1.9.1.1.3?DT=20020923143836#HDRWQ294

Hope this helps...

Cheers

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

Mike Chantrey · Posted: Thu Aug 12, 2004 10:55 am Post subject:

Note that this was posted on 'the other board' (bre's one I mean!) and I noted that it was not clear whether the poster had gone through the migration process from OS/VS COBOL to later releases or if they were just recompiling it without doing this. Following the migration guide might well solve any/all of the problems.