View previous topic :: View next topic
|
Author |
Message |
ashokakash
New User
Joined: 15 Nov 2006 Posts: 21 Location: Chennai
|
|
|
|
I have seen a statement in PL1 program that is given below
#IMS (ETAPD51,1,3,(TPPCBP,WDBDPJ01P,IMSDGVB0P,IMSDGFB1P));
#GMPDSTD(ETAPD51,(..<some X Y Z parameters here>..));
Here ETAPD51 is an IMS program and the program where this statement is written is also an IMS program. Can anybody explain what does this statement do?
I never have come across such code in my experience...
Thanks |
|
Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006 Posts: 1193 Location: Dublin, Ireland
|
|
|
|
Quote: |
I never have come across such code in my experience... |
Nor have I. I would think that the #IMS and #GMPDSTD are user-written MACROs to invoke the functions required. What does a compile listing show?
Regards,
Garry. |
|
Back to top |
|
|
cheryala
New User
Joined: 20 Mar 2006 Posts: 46
|
|
|
|
it is quite possible that, there might be a precompile step which will convert these statements into equivalent PLI statements. check the compile listing. You might find the PLI equivalent lines which are undstandable to PLI compiler. |
|
Back to top |
|
|
Srihari Gonugunta
Active User
Joined: 14 Sep 2007 Posts: 295 Location: Singapore
|
|
|
|
I suppose pre-processor statements in PL1 start with %. But anyway, as Cheryala suggested, you can see the compile listing for exact conversion. |
|
Back to top |
|
|
cheryala
New User
Joined: 20 Mar 2006 Posts: 46
|
|
|
|
Quote: |
I suppose pre-processor statements in PL1 start with % |
Yes..pre-processor statements will start with %. But what I exactly want to say is , he must be (assumption only) using a version control tool (just like CHANGEMAN) to compile the source. And his firm might have customised it to their needs and included another precompiler step which will read the PLI source lines and interpretes the lines starting with # and replaces them with equivalent PLI statements and then the source generated after this pre-modification step, his actual PLI compile step follows. |
|
Back to top |
|
|
|