Thanks for ur reply,
yes, we r using the latest version(Enterprise PL/I).
Srihari, dou have run jcl for running PL/I-IMS batch code???
it will be great, if u can help me in this regard.
I see a lot of misunderstandings around here...
let' s straighten things out a little bit
There is NO such a thing as a cobol-ims compiler nor a PL/i-ims compiler
for IMS related ( TRADITIONAL ) programming the only interface is
thru CBLTDLI for cobol an/or PLITDLI for pl/i osr ASMTDLI for assembler
the relevant IMS operations are carried by calling these interface subroutines
with the appropriate parameter list
NOR COBOL NOR PL/I NOR ASSEMBLER are aware of IMS in this environment
For the newer approach to IMS programming "EXEC" interface
still COBOL and PL/I and ASSEMBLER compilers are not involved
The appropriate PREPROCESSOR will be invoked to transform the "EXEC"
syntax in the appropriate control blocks layout ad calls to the relevant interface stubs
exactly like what happens for DB2 and CICS.... there is
NO DB2-cobol compiler, NO CICS-cobol compiler,
NO DB2-pli compiler, NO CICS-pli compiler,
NO DB2-assembler compiler, NO CICS-assembler compiler,
JUST PRECOMPILER or more correctly PREPROCESSORS
Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
Hello,
To learn what is the correct jcl for use on your system, you should talk with your dbas or system support people. They can show you what jcl/proc(s) should be used on your system.
Joined: 28 Nov 2006 Posts: 305 Location: Deerfield IL
Quote:
For the newer approach to IMS programming "EXEC" interface
still COBOL ... compilers are not involved
The appropriate PREPROCESSOR will be invoked to transform the "EXEC"
syntax in the appropriate control blocks layout ad calls to the relevant interface stubs