I have a source program compiled with Cobol-2. The output
file has a record length of 100 defined in the program but
a record of 60 bytes getting written into it. i.e. The rest
of 40 bytes I am not Writing anything. But it by default
puts some values into the last 40 bytes. However it does
not impact anything. But when Compiled the module with
Enterprise Cobol the last 40 bytes were spaces as fillers.
Can anyone explain?

Answers were Sorted based on User's Feedback



I have a source program compiled with Cobol-2. The output file has a record length of 100 defined ..

Answer / ram.g

hi

Before writing into the output file, just explicitly give
move spaces to rest of fields..
eg: ww-filler pic x(40) value spaces.
move ww-filler to ww-out-rec(61:40)
write ww-out-rec.

i hope the above code will resovle your problem.

Happy coding,
Ram.G

Is This Answer Correct ?    3 Yes 0 No

I have a source program compiled with Cobol-2. The output file has a record length of 100 defined ..

Answer / ramanujam

it may be filled with null values. Junk charecters.
Due to before writing data it has to initialize.

That is the reason it is showing junk charecters.

Is This Answer Correct ?    2 Yes 0 No

I have a source program compiled with Cobol-2. The output file has a record length of 100 defined ..

Answer / prashanth

IN THE CASE OF FB , IT WILL FILL SPACE I.E, FILLER, BUT IN
VARAIBLE MODE YOU CAN'T SEE SPACE OR FILLER.

Is This Answer Correct ?    2 Yes 0 No

I have a source program compiled with Cobol-2. The output file has a record length of 100 defined ..

Answer / vish

I think you ppl are hitting on wrong direction for
answering this question. The question doesn't seem to be
asking how to resolve a junk character, instead it's asking
about the different behaviour of the same program in two
different versions of Cobol - COBOLII and Enterprise COBOL.
One is placing junk characters in the last 40 bytes and the
other one intialized it to spaces. Any possible answer from
anyone now...?

Is This Answer Correct ?    1 Yes 0 No

I have a source program compiled with Cobol-2. The output file has a record length of 100 defined ..

Answer / sivakumar sekharannair

I will try to answer as per my understanding on the
behaviour.
With cobol-2 junk values- This is because the the 40 bytes
are not properly initialized and so the system puts some
junk values.
With enterprise cobol - spaces- I beleive that the
enterprise cobol before using an work arean intialize it by
itself and then use it. that is the reason why the unused
40 bytes had spaces.
My answer is just an assumption

Is This Answer Correct ?    1 Yes 0 No

Post New Answer

More COBOL Interview Questions

What is the local-storage section?

1 Answers  


What is difference between comp & comp-4?

6 Answers  


Syntax for JCLLIB & JOBLIB???

1 Answers  


how to convert vsam table into DB2 table?

1 Answers   IBM, Wipro,


Which is the best IBM mainframe Training Institute in Ameerpet, Hyderabad

35 Answers  


What is the difference between copy and include in cobol?

1 Answers  


How to Write the RESTART Logic Using COBOL?

4 Answers   GalaxE, L&T, Syntel, TCS,


Under which scenario you would go for a static call as opposed to dynamic call?

5 Answers   TCS,


which certifications r 4 cobol,jcl,db2,cics what is format of xam n what is importance of these certifications... plz post answer only if u r sure... thanks

1 Answers  


How to recover a deleted source physical file from library?

1 Answers   HCL,


What is the maximum data length for Numeric DataType ?

3 Answers   Cap Gemini,


What are ISOLATION LEVELS? Where do we need to specify them in compiling JCL (Exactly which statement and what is syntax for it)?

2 Answers   T systems,


Categories