Explore topic-wise InterviewSolutions in .

There is no PICTURE clause to be GIVEN. EXAMPLE 01 WS-VAR USAGE COMP-1.

There is no picture clause to be given. Example 01 WS-VAR USAGE COMP-1.

COMP is a BINARY storage format while COMP-3 is PACKED decimal format.

COMP is a binary storage format while COMP-3 is packed decimal format.

It is STORED in the most SIGNIFICANT BIT. Bit is ON if -ve, OFF if +ve.

It is stored in the most significant bit. Bit is ON if -ve, OFF if +ve.

It will TAKE 4 bytes to occupy. Sign is stored as hex value in the LAST nibble. General formula is INT((n/2) + 1)), where n=7 in this EXAMPLE.

It will take 4 bytes to occupy. Sign is stored as hex value in the last nibble. General formula is INT((n/2) + 1)), where n=7 in this example.

There are at least five differences: COBOL II SUPPORTS STRUCTURED programming by using in line Performs and explicit scope terminators, It introduces NEW features (EVALUATE, SET. TO TRUE, CALL. BY CONTEXT, etc) It permits programs to be loaded and ADDRESSED above the 16-megabyte line It does not support MANY old features (READY TRACE, REPORT-WRITER, ISAM, Etc.), and It offers enhanced CICS support.

There are at least five differences: COBOL II supports structured programming by using in line Performs and explicit scope terminators, It introduces new features (EVALUATE, SET. TO TRUE, CALL. BY CONTEXT, etc) It permits programs to be loaded and addressed above the 16-megabyte line It does not support many old features (READY TRACE, REPORT-WRITER, ISAM, Etc.), and It offers enhanced CICS support.

A scope terminator BRACKETS its preceding verb, e.g. IF... END-IF, so that all statements between the verb and its scope terminator are grouped TOGETHER. Other COMMON COBOL II verbs are READ, PERFORM, and EVALUATE, SEARCH and STRING.

A scope terminator brackets its preceding verb, e.g. IF... END-IF, so that all statements between the verb and its scope terminator are grouped together. Other common COBOL II verbs are READ, PERFORM, and EVALUATE, SEARCH and STRING.

The PERFORM and END-PERFORM statements bracket all COBOL II statements between them. The COBOL equivalent is to PERFORM or PERFORM THRU a paragraph. In line PERFORMs work as long as there are no internal GO TOs, not even to an exit. The in line PERFORM for readability should not exceed a PAGE length - often it will REFERENCE other PERFORM paragraphs.

The PERFORM and END-PERFORM statements bracket all COBOL II statements between them. The COBOL equivalent is to PERFORM or PERFORM THRU a paragraph. In line PERFORMs work as long as there are no internal GO TOs, not even to an exit. The in line PERFORM for readability should not exceed a page length - often it will reference other PERFORM paragraphs.

NEXT SENTENCE GIVES control to the verb following the next period. CONTINUE gives control to the next verb after the explicit scope terminator. (This is not one of COBOL IIs finer IMPLEMENTATIONS). It is safest to USE CONTINUE rather than NEXT SENTENCE in COBOL II.

NEXT SENTENCE gives control to the verb following the next period. CONTINUE gives control to the next verb after the explicit scope terminator. (This is not one of COBOL IIs finer implementations). It is safest to use CONTINUE rather than NEXT SENTENCE in COBOL II.

PARTIAL list: REMARKS, NOMINAL KEY, PAGE-COUNTER, CURRENT-DAY, TIME-OF-DAY, STATE, FLOW, COUNT, EXAMINE, EXHIBIT, READY TRACE and RESET TRACE.

Partial list: REMARKS, NOMINAL KEY, PAGE-COUNTER, CURRENT-DAY, TIME-OF-DAY, STATE, FLOW, COUNT, EXAMINE, EXHIBIT, READY TRACE and RESET TRACE.

The PARAMETERS passed in a call by context are PROTECTED from modification by the called PROGRAM. In a normal call they are able to be modified.

The parameters passed in a call by context are protected from modification by the called program. In a normal call they are able to be modified.

The linkage section is PART of a called PROGRAM that links or MAPS to data items in the calling program are working storage. It is the part of the called program where these SHARE items are defined.

The linkage section is part of a called program that links or maps to data items in the calling program are working storage. It is the part of the called program where these share items are defined.

A subscript is a working storage data definition item, TYPICALLY a PIC (999) where a value must be MOVED to the subscript and then incremented or decrements by ADD TO and SUBTRACT FROM statements. An INDEX is a register item that exists outside the programs working storage. You SET an index to a value and SET it UP BY value and DOWN BY value.

A subscript is a working storage data definition item, typically a PIC (999) where a value must be moved to the subscript and then incremented or decrements by ADD TO and SUBTRACT FROM statements. An index is a register item that exists outside the programs working storage. You SET an index to a value and SET it UP BY value and DOWN BY value.

Wake up - you haven't been paying attention! It is not possible to pass an INDEX via linkage. The index is not part of the calling programs WORKING storage. Those of us, who've MADE this mistake, APPRECIATE the lesson more than others.

Wake up - you haven't been paying attention! It is not possible to pass an index via linkage. The index is not part of the calling programs working storage. Those of us, who've made this mistake, appreciate the lesson more than others.

An external sort is not COBOL; it is performed through JCL and PGM=SORT. It is understandable without any code reference. An internal sort can use two different syntaxs: 1.) USING, GIVING sorts are COMPARABLE to external sorts with no EXTRA FILE processing; 2) INPUT PROCEDURE, OUTPUT PROCEDURE sorts ALLOW for data manipulation before and/or after the sort.

An external sort is not COBOL; it is performed through JCL and PGM=SORT. It is understandable without any code reference. An internal sort can use two different syntaxs: 1.) USING, GIVING sorts are comparable to external sorts with no extra file processing; 2) INPUT PROCEDURE, OUTPUT PROCEDURE sorts allow for data manipulation before and/or after the sort.

Scope terminators are MANDATORY for in-line PERFORMS and EVALUATE statements. For readability, it is RECOMMENDED coding practice to ALWAYS make scope terminators EXPLICIT.

Scope terminators are mandatory for in-line PERFORMS and EVALUATE statements. For readability, it is recommended coding practice to always make scope terminators explicit.

In COBOL II the optional clause WITH TEST BEFORE or WITH TEST AFTER can be added to all perform statements. By default the test is PERFORMED before the perform.

In COBOL II the optional clause WITH TEST BEFORE or WITH TEST AFTER can be added to all perform statements. By default the test is performed before the perform.

Absolutely. Evaluation of the WHEN CLAUSES PROCEEDS from top to bottom and their sequence can DETERMINE RESULTS.

Absolutely. Evaluation of the WHEN clauses proceeds from top to bottom and their sequence can determine results.

INITIALIZE MOVES spaces to alphabetic fields and zeros to alphanumeric fields. The REPLACING option can be USED to OVERRIDE these defaults.

INITIALIZE moves spaces to alphabetic fields and zeros to alphanumeric fields. The REPLACING option can be used to override these defaults.

In COBOL II the 88 levels can be SET rather than MOVING their associated values to the RELATED data item. (Web note: This change is not one of COBOL IIS better specifications.)

In COBOL II the 88 levels can be set rather than moving their associated values to the related data item. (Web note: This change is not one of COBOL IIs better specifications.)

LENGTH acts like a SPECIAL REGISTER to TELL the length of a group or elementary ITEM.

LENGTH acts like a special register to tell the length of a group or elementary item.

REPLACING allows for the same COPY to be used more than once in the same code by changing the REPLACE value.

REPLACING allows for the same copy to be used more than once in the same code by changing the replace value.

The ONLY WAY is to look at the output of the linkage editor (IEWL) or the load module itself. If the module is being CALLED DYNAMICALLY then it will not exist in the main module, if it is being called STATICALLY then it will be seen in the load module. Calling a working STORAGE variable, containing a program name, does not make a DYNAMIC call. This type of calling is known as IMPLICITE calling as the name of the module is implied by the contents of the working storage variable. Calling a program name literal.

The ONLY way is to look at the output of the linkage editor (IEWL) or the load module itself. If the module is being called DYNAMICALLY then it will not exist in the main module, if it is being called STATICALLY then it will be seen in the load module. Calling a working storage variable, containing a program name, does not make a DYNAMIC call. This type of calling is known as IMPLICITE calling as the name of the module is implied by the contents of the working storage variable. Calling a program name literal.

To correct an earlier ANSWER: All called modules cannot run standalone if they require PROGRAM variables passed to them via the LINKAGE section. Dynamically called modules are those that are not bound with the calling program at link edit time (IEWL for IBM) and so are LOADED from the program library (joblib or steplib) associated with the JOB. For DYNAMIC calling of a module the DYNAM compiler option must be chosen, ELSE the linkage editor will not generate an executable as it will expect u address resolution of all called modules. A Statically called module is one that is bound with the calling module at link edit, and therefore becomes part of the executable load module.

To correct an earlier answer: All called modules cannot run standalone if they require program variables passed to them via the LINKAGE section. Dynamically called modules are those that are not bound with the calling program at link edit time (IEWL for IBM) and so are loaded from the program library (joblib or steplib) associated with the job. For DYNAMIC calling of a module the DYNAM compiler option must be chosen, else the linkage editor will not generate an executable as it will expect u address resolution of all called modules. A Statically called module is one that is bound with the calling module at link edit, and therefore becomes part of the executable load module.

PIC 9.99 is a FOUR-POSITION FIELD that actually contains a decimal point where as PIC 9v99 is THREE- POSITION NUMERIC field with implied or assumed decimal position.

PIC 9.99 is a FOUR-POSITION field that actually contains a decimal point where as PIC 9v99 is THREE- POSITION numeric field with implied or assumed decimal position.

PICTURE 9v99 is a three position NUMERIC FIELD with an IMPLIED or assumed decimal point after the FIRST position; the v means an implied decimal point.

PICTURE 9v99 is a three position Numeric field with an implied or assumed decimal point after the first position; the v means an implied decimal point.

SEARCH is a SEQUENTIAL search from the beginning of the table. SEARCH ALL is a binary search, continually dividing the table in TWO halves until a match is found. SEARCH ALL is more efficient for tables larger than 70 items.

SEARCH is a sequential search from the beginning of the table. SEARCH ALL is a binary search, continually dividing the table in two halves until a match is found. SEARCH ALL is more efficient for tables larger than 70 items.

Make sure that LINK OPTION is AMODE=31 and RMODE=ANY. COMPILE option should NEVER have SIZE (MAX). BUFSIZE can be 2K, efficient enough.

Make sure that link option is AMODE=31 and RMODE=ANY. Compile option should never have SIZE (MAX). BUFSIZE can be 2K, efficient enough.

USE a file //dd1 DD sysout=(*, intrdr)WRITE your JCL to this file. PL some on TRY this out.

Use a file //dd1 DD sysout=(*, intrdr)write your JCL to this file. Pl some on try this out.

Using EXEC CICS SPOOL WRITE (var-name) END-EXEC COMMAND. Var-name is a COBOL host structure CONTAINING JCL STATEMENTS.

Using EXEC CICS SPOOL WRITE (var-name) END-EXEC command. Var-name is a COBOL host structure containing JCL statements.

1. You can REDEFINE a Variable from one PICTURE class to ANOTHER PICTURE class by USING the same memory location.
2. By REDEFINES we can INITIALISE the variable in WORKING-STORAGE Section itself.
3. We can REDEFINE a Single Variable into so many SUB variables. (This facility is very useful in solving Y2000 Problem.)

1. You can REDEFINE a Variable from one PICTURE class to another PICTURE class by using the same memory location.
2. By REDEFINES we can INITIALISE the variable in WORKING-STORAGE Section itself.
3. We can REDEFINE a Single Variable into so many sub variables. (This facility is very useful in solving Y2000 Problem.)

A program that follows a top down approach. It is also one that other PROGRAMMERS or USERS can FOLLOW logically and is easy to read and UNDERSTAND.

A program that follows a top down approach. It is also one that other programmers or users can follow logically and is easy to read and understand.

Here s9(4)comp is small INTEGER ,so two words EQUAL to 1 byte so TOTALLY it will occupy 2 BYTES(4 words).here in s9(4) comp-3 as one word is equal to 1/2 byte.4 words equal to 2 bytes and sign will occupy 1/2 byte so totally it will occupy 3 bytes.

Here s9(4)comp is small integer ,so two words equal to 1 byte so totally it will occupy 2 bytes(4 words).here in s9(4) comp-3 as one word is equal to 1/2 byte.4 words equal to 2 bytes and sign will occupy 1/2 byte so totally it will occupy 3 bytes.

The following features are available with VS COBOL II: 1. MVS/XA and MVS/ESA support. The compiler and the object PROGRAMS it produces can be RUN in either 24- or 31-bit addressing MODE. 2. VM/XA and VM/ESA support the compiler and the object programs it produces can be run in either 24- or 31-bit addressing mode. 3. VSE/ESA supports the compiler and the object programs it produces can be run under VSE/ESA.

The following features are available with VS COBOL II: 1. MVS/XA and MVS/ESA support. The compiler and the object programs it produces can be run in either 24- or 31-bit addressing mode. 2. VM/XA and VM/ESA support the compiler and the object programs it produces can be run in either 24- or 31-bit addressing mode. 3. VSE/ESA supports the compiler and the object programs it produces can be run under VSE/ESA.

Indexing USES binary displacement. SUBSCRIPTS use the value of the OCCURRENCE.

Indexing uses binary displacement. Subscripts use the value of the occurrence.

The LINKAGE section is used to pass data from ONE program to ANOTHER program or to pass data from a PROC to a program.

The linkage section is used to pass data from one program to another program or to pass data from a PROC to a program.

The Purpose of POINTER PHRASE is to specify the leftmost position within receiving field where the first TRANSFERRED character will be STORED.

The Purpose of POINTER phrase is to specify the leftmost position within receiving field where the first transferred character will be stored.

When any DATA name, file-name, Record-name, CONDITION name or Index defined in an Including Program can be referenced by a directly or indirectly in an included program, PROVIDED the SAID name has been declared to be a global name by GLOBAL Format of Global Clause is01 data-1 pic 9(5) IS GLOBAL.

When any data name, file-name, Record-name, condition name or Index defined in an Including Program can be referenced by a directly or indirectly in an included program, Provided the said name has been declared to be a global name by GLOBAL Format of Global Clause is01 data-1 pic 9(5) IS GLOBAL.

The difference between the next and CONTINUE VERB is that in the continue verb it is used for a SITUATION where there in no EOF condition that is the records are to be ACCESSED again and again in an file, whereas in the next verb the indexed file is accessed sequentially, read next record COMMAND is used.

The difference between the next and continue verb is that in the continue verb it is used for a situation where there in no EOF condition that is the records are to be accessed again and again in an file, whereas in the next verb the indexed file is accessed sequentially, read next record command is used.

In using COBOL on PC we have only FLAT files and the programs can access only limited storage, whereas in VS COBOL II on M/F the programs can access up to 16MB or 2GB DEPENDING on the addressing and can USE VSAM files to make I/O OPERATIONS FASTER.

In using COBOL on PC we have only flat files and the programs can access only limited storage, whereas in VS COBOL II on M/F the programs can access up to 16MB or 2GB depending on the addressing and can use VSAM files to make I/O operations faster.

GLOBAL variables are ACCESSIBLE only to the batch program WHEREAS external variables can be referenced from any batch program RESIDING in the same system library.

Global variables are accessible only to the batch program whereas external variables can be referenced from any batch program residing in the same system library.

IDENTIFICATION DIVISION and PROGRAM-ID PARAGRAPH are mandatory for a compilation ERROR FREE COBOL program.

IDENTIFICATION DIVISION and PROGRAM-ID paragraph are mandatory for a compilation error free COBOL program.

Structured programming is a Logical way of programming, you divide the functionalities into modules and code logically. OOP is a Natural way of programming; you identify the objects first, and then write functions, procedures AROUND the objects. Sorry, this may not be an ADEQUATE answer, but they are two different programming paradigms, which is difficult to PUT in a SENTENCE or two.

Structured programming is a Logical way of programming, you divide the functionalities into modules and code logically. OOP is a Natural way of programming; you identify the objects first, and then write functions, procedures around the objects. Sorry, this may not be an adequate answer, but they are two different programming paradigms, which is difficult to put in a sentence or two.

Subscript REFERS to the array of occurrence, where as INDEX REPRESENTS an occurrence of a table element. An index can only modified using perform, search & SET. Need to have an index for a table in order to USE SEARCH and SEARCH All.

Subscript refers to the array of occurrence, where as Index represents an occurrence of a table element. An index can only modified using perform, search & set. Need to have an index for a table in order to use SEARCH and SEARCH All.

Redefines clause is used to ALLOW the same STORAGE allocation to be REFERENCED by DIFFERENT DATA names.

Redefines clause is used to allow the same storage allocation to be referenced by different data names.

SIX SECTIONS

1. FILE SECTION
2. WORKING-STORAGE SECTION
3. LOCAL-STORAGE SECTION
4. SCREEN SECTION
5. REPORT SECTION
6. LINKAGE SECTION

SIX SECTIONS

1. FILE SECTION
2. WORKING-STORAGE SECTION
3. LOCAL-STORAGE SECTION
4. SCREEN SECTION
5. REPORT SECTION
6. LINKAGE SECTION

DB2 PRECOMPILER (if embedded sql used), CICS TRANSLATOR (if CICS pgm), Cobol compiler, Link EDITOR.
If DB2 program, create plan by BINDING the DBRMs.

DB2 precompiler (if embedded sql used), CICS translator (if CICS pgm), Cobol compiler, Link editor.
If DB2 program, create plan by binding the DBRMs.

MOVE a VALUE to RETURN-CODE REGISTER. RETURN-CODE should not be DECLARED in your PROGRAM.

Move a value to RETURN-CODE register. RETURN-CODE should not be declared in your program.

These are compiler options w.r.t SUBSCRIPT out of range checking. NOSSRANGE is the DEFAULT and if chosen, no run time ERROR will be FLAGGED if your INDEX or subscript goes out of the permissible range.

These are compiler options w.r.t subscript out of range checking. NOSSRANGE is the default and if chosen, no run time error will be flagged if your index or subscript goes out of the permissible range.

DYNAM.

DYNAM.

In static linking, the called subroutine is link-edited into the CALLING program , while in dynamic linking, the subroutine & the main program will exist as SEPARATE LOAD modules. You choose static/dynamic linking by choosing either the DYNAM or NODYNAM link edit option. (Even if you choose NODYNAM, a CALL identifier (as opposed to a CALL literal), will translate to a DYNAMIC call).

A statically called subroutine will not be in its initial state the next time it is called unless you explicitly use INITIAL or you do a CANCEL. A dynamically called routine will always be in its initial state.

In static linking, the called subroutine is link-edited into the calling program , while in dynamic linking, the subroutine & the main program will exist as separate load modules. You choose static/dynamic linking by choosing either the DYNAM or NODYNAM link edit option. (Even if you choose NODYNAM, a CALL identifier (as opposed to a CALL literal), will translate to a DYNAMIC call).

A statically called subroutine will not be in its initial state the next time it is called unless you explicitly use INITIAL or you do a CANCEL. A dynamically called routine will always be in its initial state.