Difference between STATIC AND DYNAMIC CALL

-

 Sl #
STATIC Call
DYNAMIC Call

1
Identified by Call literal.
Ex: CALL ‘PGM1’.
Identified by Call variable and the variable should be populated at run time.
01 WS-PGM PIC X(08).
Move ‘PGM1’ to WS-PGM
CALL WS-PGM
2
Default Compiler option is NODYNAM and so all the literal calls are considered as static calls.
If you want convert the literal calls into DYNAMIC, the program should be compiled with DYNAM option.
By default, call variables and any un-resolved calls are considered as dynamic.

3.
If the subprogram undergoes change, sub program and main program need to be recompiled.
If the subprogram undergoes change, recompilation of subprogram is enough.
4
Sub modules are link edited with main module.
Sub modules are picked up during run time from the load library.
5
Size of load module will be large
Size of load module will be less.
6
Fast
Slow compared to Static call.
7
Less flexible.
More flexible.


Comments

Post a Comment

Popular posts from this blog

COBOL + DB2 complication process.

-
Image
There are various step involved before we run/execute a COBOL + DB2 program.   Below step are the various steps.   Precompile.   Compile.   Link edit.   Bind.   Package & plan. Step 1: Precompile               COBOL compiler did not understand about SQL statement so, it undergoes to precompile. In precompile.     Expands all include copybooks which are written in program.     Extracts all SQL statements into DBRM and SQL statement are convert into call statements.    Generates time-stamp for modified source codes and DBRM .there are checked at run time.   Check syndicated error of SQL statements and validates the fields based on the table declaration from dclgen copybook.    Notes: precompilation process can be executed even if DB2 is down. DSNHPC    ----------- It is the program used for precompilation. Step 2:  Compile            It is same as normal COBOL compilation.it takes modified source as input and compilers.  IGYRCTL --
Read more

ABEND list for JCL

-
what is ABEND?   An ABEND (abnormal end) is an exception condition which results in the abnormal termination of a program or software. It is a common terminology used in the mainframe world where a JCL terminates with an error code.  S0CB -    Attempting to divide by 0 and not using ON SIZE ERROR S002 -    Very large record length/ wrong record length Sx22 -   Job has been cancelled. The value of x will vary depending on the way the job was  cancelled. . S222 -    Means job was cancelled by a user or operator without a dump.                If a TSO session times out you will probably get an S522 ABEND code. S222 -    The job was cancelled (by subsystem or operator) because it violated               Some restriction. S522 -    JOB or TSO session exceeded maximum job wait time OR               Operator did not mount the require tape within allowed time limit    S806 -    Load module not found SB37
Read more

difference between jes2 and jes3

-
JES2 JES3       1.        Decentralization.       2.        Every processor the incoming job individually.       3.        It is prestep allocation.       4.        Dataset allowed before step is executed.       5.        It is a local process.       6.        Control statement (//*). 1. Centralization. 2. It control process and assign job to sub processor. 3. It is prejob allocation. 4. Dataset allowed before job is schedule. 5. It is global process. 6. Control statement (/*).
Read more