Answer Posted / ravi

Here is the difference between static and dynamic calls, it
is mentioned very clearly in IBM COBOL Manual, read it
carefully, it should clear all your doubts regarding calls



WORKING-STORAGE SECTION.

01 PGM-NAME PIC X(08).

PROCEDURE DIVISION.

BEGIN-PARA.

MOVE “SUBPROG” TO PGM-NAME.

* Dynamic call

CALL PGM-NAME USING RECORD-1. ****** Here PGM-
NAME is called as identifier*******

*Static Call

CALL “SUBPROG” USING RECORD-2. ****** Here it is
CALL literal where literal is SUBPROG*******





If you do not know the program-name to be called until run
time, use the format CALL identifier, where identifier is a
data item that will contain the name of the called program
at run time. For example, you could use CALL identifier
when the program to be called varies depending on
conditional processing in your program. CALL identifier is
always dynamic, even if you use the NODYNAM compiler option.





Making static calls

When you use the CALL literal statement in a program that
is compiled using the NODYNAM and NODLL compiler options, a
static call occurs. With these options, all calls of the
CALL literal format are handled as static calls. In the
static CALL statement, the COBOL program and all called
programs are part of the same load module.



Making dynamic calls

When you use a CALL literal statement in a program that is
compiled using the DYNAM and the NODLL compiler options, or
when you use the CALL identifier statement in a program
that is compiled using the NODLL compiler option, a dynamic
call occurs.





Making both static and dynamic calls

You can use both static and dynamic CALL statements in the
same program if you compile the program with the NODYNAM
compiler option. In this case, with the CALL literal
statement the called subprogram will be link-edited with
the main program into one load module. The CALL identifier
statement results in the dynamic invocation of a separate
load module. When a dynamic CALL statement and a static
CALL statement to the same subprogram are issued within one
program, a second copy of the subprogram is loaded into
storage. Because this arrangement does not guarantee that
the subprogram will be left in its last-used state, results
can be unpredictable.



Performance considerations of static and dynamic calls

Because a statically called program is link-edited into the
same load module as the calling program, a static call is
faster than a dynamic call. A static call is the preferred
method if your application does not require the services of
the dynamic call.

Statically called programs cannot be deleted using CANCEL,
so static calls might take more main storage. If storage is
a concern, think about using dynamic calls. Storage usage
of calls depends on whether:

The subprogram is called only a few times. Regardless of
whether it is called, a statically called program is loaded
into storage; a dynamically called program is loaded only
when it is called.
You subsequently delete the dynamically called subprogram
with a CANCEL statement.
You cannot delete a statically called program, but you can
delete a dynamically called program. Using a dynamic call
and then a CANCEL statement to delete the dynamically
called program after it is no longer needed in the
application (and not after each call to it) might require
less storage than using a static call.

Step 1 RC 4 Step 2 Step 3 I want to know the COND parameter which can be coded in step 2 or 3. Step 2 should be executed based on Step 1 RC and Step 3 should not be executed based on step 1's RC

4903

---

which parameter is used to check the syntax of a jcl without executing it?

1363

---

What are steplib and joblib? What for they are used?

1229

---

I want my job (careerride) to be executed in 1 minute and 2 seconds. How do I do that?

1236

---

Name the parameters which can be used to limit the number of records written to a sysout dataset?

1155

---

how can a gdg base be created in a jcl. What is the difference between empty and scratch parameter while defining/altering gdg base?

1280

---

Explain how can the submitting users racf authority be overridden in a job stream?

1128

---

How does the jcl specify the job to os?

1157

---

Is it possible to code instream data in a PROC?

1332

---

Is automatic restart possible in jcl? If yes, how?

1116

---

What does a disposition of (new,catlg,keep) for a dsn mean?

1150

---

Must tape dataset definitions include vol=ser specifications?

1724

---

why should SYSIN DD * statement should not be included inside a PROCedure snippet??? please answer this.. i need to know.

2456

---

I have a cobol db2 program(PGM A) where other program (PGM B) will call this program and passes some 50 fields data to PGM A. PGM A has some layout in which it receives the data from PGM B. And this layout has been copied in the linkage section pf PGM A. After getting the data, PGM A writes the data in a flat file in the same layout which it receives from PGM B. PGM B is a simple COBOL pgm. Please provide a JCL to run these programs.

2358

---

Give the syntax of job specifying jcl statement.

1147

---