What are differences between Static Call and Dynamic Call?
Answer Posted / siri
STATIC CALL:-
------------
STATIC CALL IS IDENTIFIED BY A CALL IS
LITERAL..EX:-CALL'PGM1'....COMPILER OPTION IS NO DYNAM...ALL LITERAL CALLS ARE CONSIDER AS STATIC CALLS...OBJECT CALLS ARE LINKED BEFORE THE EXECUTION..STATIC CALL IS FAST..LOAD MODULE WILL BE LARGE....LESS FLEXIBLE...SUB PROGRAMS UNDERGOES TO CHANGE NEED TO RECOMPILE MAIN PRG ALSO..
DYNAMIC CALL:-
------------
IDENTIFIED BY A CALL IS VARIABLE...MOVE 'PGM1' TO WS-PGM
CALL 'WS-PGM'
COMPILER OPTION IS DYNAM...OBJECT CODS ARE LINKED DURING THE EXECUTION....SO PRG FIRST MOVE TO THE WORKING STORAGE VARIABLE AND NEST CALL THE WORKING STORAGE VARIABLE...PROCESS IS SLOW SO DYNAMIC CALL IS SLOW COMPARE TO STATIC CALL.....ITS NO NEED TO RECOMPILE THE MAIN PROGRAM
WHEN EVER THE SUB PROGRAM UNDER GOES TO CHANGE...THIS IS THE
MAIN ADVANTAGE IS IN DYNAMIC CALL....
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
What is the Purpose of Pointer in the string?
State the various causes of s0c1, s0c5 and s0c7.
how to convert the recors form vsam file to db2 table tru file aid
Write a program that uses move corresponding.
How do u write test cases?
What guidelines should be followed to write a structured cobol prgm?
Why do we code s9 (4) comp. Inspite of knowing comp-3 will occupy less space?
What is the problem of ordered sequential files access?
Which mode is used to operate the sequential file?
can you please let me know if there is any walkins for COBOL/PLI/DB2/IMS/JCL in pune other than IBM and ITC infotech
write a cobol logic. i have file that has 10 records .1 record go to first output file and second record goes to 2 output and etc
What is the difference between a binary search and a sequential search what are the pertinent cobol?
Our issue is there seems to be a disconnect, or no link, between our SELECT statement and our SD. We had SELECT SORT-FILE and SELECT SORT-FILE ASSIGN TO SORTWRK. ASSIGN TO SORTWRK1 SORTWRK2 SORTWRK3 SORTWRK4. with SD SORT_FILE RECORD CONTAINS 7833 CHARACTERS. In either case, at run time, the system ignored our SORTWRK# DD statements and allocated 16 sort works with the SORTWK## naming convention. Any ideas why the system does not recognize the connection? We do not even need the SORTWRK DD statements. Thanks
Which is not true about evaluate statement
how we sort two input files based on a common column and giving one o/p file please send me the coding logic?