|
View previous topic :: View next topic
|
| Author |
Message |
akodakka
New User
.jpg)
Joined: 20 May 2010
Posts: 75
Location: India
|
|
|
|
Hi All
I have CICS PROG A which should link/call a another PROG B which is DB2 prog( will retrieve data from tables and pass that to prog A)
My doubt here is ..is the PROG A can use LINK to call PROGB OR can i use use CALL to PROG B. ( My system is an online processing )..
Which one is the best option here...
2) Is my prog B is a batch program if i use CALL instead of link or this should be called as CICS-DB2 program
Please advise |
|
| Back to top |
|
 |
Manigandan Aravindhan
New User
Joined: 09 Oct 2007
Posts: 81
Location: India
|
|
|
|
You cannot invoke a batch program from CICS, If your ProgB is a batch program then double link edit(Compile it as online as well) the same. Then use Link to call a ProgB.
Thanks,
Manigandan |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Manigandan wrote: |
| You cannot invoke a batch program from CICS, If your ProgB is a batch program then double link edit(Compile it as online as well) the same. Then use Link to call a ProgB. |
that is old and no longer true. That was the methodology used in the 1970's/80's, but since the 1990's you nolonger need to use the double module silliness anymore.
there are topics in the forum that discuss where the load libraries of the batch programs in the CICS JCL need to be located.
You can issue a COBOL CALL in a CICS program to a batch module. The same batch load module can be CALLed from another batch module.
This/can be accomplished with dynamic CALL's.
I have worked on systems that have 10, 15 levels of dynamic batch CALL's that work both in CICS and batch.
I have also (am currently) worked on systems that have this double module crap. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hi Dick,
In inventory we see LIFO and FIFO.
In code we see WORF - (Write Once, Run Forever) 
And many of these that are still running were intended to be a stop-gap measure until the "real" code could be completed. . .
d |
|
| Back to top |
|
|
|
|
