what happens if instead of STOP RUN we code GOBACK



what happens if instead of STOP RUN we code GOBACK

Postby veturisarma » Mon Mar 31, 2008 10:07 pm

1.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
veturisarma
 
Posts: 1
Joined: Mon Mar 31, 2008 10:00 pm
Has thanked: 0 time
Been thanked: 0 time

Re: what happens if instead of STOP RUN we code GOBACK

 

Re: cobol queries respnd immediately please!!!!!

Postby CICS Guy » Tue Apr 01, 2008 12:56 am

I would expect that you will get better results if you attempted to answer your questions and provide an explaination of why you think your answers are correct.
Do you need pointers to the various manuals?
CICS Guy
 
Posts: 255
Joined: Wed Jun 20, 2007 4:08 am
Has thanked: 0 time
Been thanked: 0 time


Return to Interview Questions

 


  • Related topics
    Replies
    Views
    Last post