In COBOL "BEFORE" advancing is there or not ?
Answers were Sorted based on User's Feedback
Answer / nag(igate)
Yes, Before advancing clause is there. but it is default in
perform statement.
ex:
Perform para1 varying I from 1 by 1 until I > 10 { test
before or after}
1. if we code before: the condition will check first then
loop will execute. it is default.
2. if we code after: the loop will execute first then
condition will check.
pls correct me, if i am wrong..............
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / raja
After clause is default, but before clause also there.
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / ravi
Before advancing is not there.
only after advanving is allowed
Is This Answer Correct ? | 0 Yes | 2 No |
EXPLAIN MAIN FRAME TESTING PROCESS...HOW TO FIX THE MAINFRAME BUGS?
in cobol i have one file it contains records like 10,4,23,98,7,90..... total records 100. iwant 10 to 20 in reverse order in cobol environ ment any one please give the answer......
If i got a job on mainframe technology, will i have a bright future?. Some people are discouraging me. Let me know, is it true? Please bring back me from the confusion.
What is the utilization of copybook in cobol?
What does EXIT do ?
what is the difference between implicit and explicit scope terminator with example?
I have two sequential files, FILE-1 and FILE-2. FILE-1 contains 2 columns(A,B) and FILE-2 contains 3 columns (C,D,E).I want an output file, FILE-3 which has all five columns with duplicates eliminated from column A.
Suppose, file A has 100 records and file B has 500 records. We want to write records common to both A and B into file C and records which are present only in either A or B into another file D. What should be the logic of Cobol program to achieve this?
7 Answers Bank Of America, Mind Tree,
How can you add a particular field/coloumn in copybook?
Why we need to use redefine clause when we can define the variable seperately... what is actual need....
Should I use STOP RUN in the sub program??why?
where do u use low-value and high value in cobol