what happens if instead of STOP RUN we code GOBACK
Posted: Mon Mar 31, 2008 10:07 pm1.what happens if instead of STOP RUN we code GOBACK in the main program
2.how can data be passed to a dynamically called module without using linking storage section
3.for indexed fiole having an alternate key a new ddname has to be mentioned in jcl how is that mapped in cobol
4.what happens if you use an input file in jcl but donot mention the ddname in cobol
5.how to make sure a subroutine is called dynamically
6.why do we need input/output procedure to sort a file
7.what is the difference between inspect and examine
8.what is the order of specifying organization,accessmode and fiole status in the file definition area
9.if a new file is introduced to cobol which sections will not be affected
10. if we try to write a record to a ksds file which will result in creation of duplicate key what will be the file status
2.how can data be passed to a dynamically called module without using linking storage section
3.for indexed fiole having an alternate key a new ddname has to be mentioned in jcl how is that mapped in cobol
4.what happens if you use an input file in jcl but donot mention the ddname in cobol
5.how to make sure a subroutine is called dynamically
6.why do we need input/output procedure to sort a file
7.what is the difference between inspect and examine
8.what is the order of specifying organization,accessmode and fiole status in the file definition area
9.if a new file is introduced to cobol which sections will not be affected
10. if we try to write a record to a ksds file which will result in creation of duplicate key what will be the file status