Examples of using CEEHDLR

[maxb@bfcsoftware.com]

I have a need to add error recovery capability to our programs used to do RF transactions in a warehouse. After searching the MC forum I have found some information on the CEEHDLR API which may be an answer to my problem. However, I have not used the system API's in the past and would like it if anyone could point me to some examples of using CEEHDLR API or if you have some exampes you would like to share that would be greatly appreciated. Thanks in advance, Max Blacknik

[David Abramowitz]

You bring up a very good point, in that there is no fully comprehensive guide to the "CEE" APIs. The IBM manuals are reference points, but there is no "how-to" book with examples, and 8x11 glossies to help guide the first few attempts. Maybe MC will publish one?!? Dave

[Guest.Visitor]

Max, There is some information available in the CEE API manual on-line. Here is the address I used to find it: http://publib.boulder.ibm.com/cgi-bi....1?ACTION=MATC HES&REQUEST=ceehdlr&TYPE=FUZZY&searchTopic=TOPIC&searchText=TEXT&searchIndex=IND EX&rank=RANK#FIRSTHIT 2.6.6.1 Examples of Using Bindable APIs For examples of using bindable APIs, see: "Sample Service Program" in topic 2.4.4, for an example of using CEEDOD "Managing Your Own Heap Using ILE Bindable APIs" in topic 2.5.7.3. for an example of using CEEGTST, CEEFRST, and CEECZST. "Using a Condition Handler" in topic 3.2.4.1, for an example of using CEEHDLR and CEEHDLU. "Using Cancel Handlers" in topic 3.2.5, for an example of using CEERTX and CEEUTX. Mark McCall

[Guest.Visitor]

Max, Hopefully this will get you started. As Mark pointed out, you should also check the manual. You can also use scoping messages to accomplish about the same thing. The biggest problem I see with these APIs is that you cannot pass a level like you can with the message APIs, which means that you cannot effectively wrap them in a custom interface.

 **************************************************  ****************************** ************** * CEEHdlr Register error handler. * * Output: * * FBCod Feedback code. * * Input: * * pPrc Procedure to call. * * pDta Pointer to parameter value. * **************************************************  ****************************** ************** DCeeHdlr PR D PR_ErrPrc * CONST PROCPTR D PR_ErrDta * CONST OPTIONS(*OMIT) D PR_FBCod 12A OPTIONS(*OMIT) **************************************************  ****************************** ************** * CEERtx Register call stack exit. * * Output: * * FBCod Feedback code. * * Input: * * pPrc Procedure to call. * * pDta Pointer to parameter value. * **************************************************  ****************************** ************** DCEERtx PR EXTPROC('CEERTX') Register callstk ext D PR_pPrc * PROCPTR CONST Procedure pointer D PR_pDta * CONST OPTIONS(*OMIT) Data pointer D PR_FBCod 12A OPTIONS(*OMIT) ... At top of program C* Register end of call stack procedure C CALLP CEERtx( C %PADDR('YOUREXITPROCEDURENAME'): C *OMIT: C *OMIT) C* Register unexpected error handler C CALLP CEEHdlr( C %PADDR('YOURABNORMALPROCEDURENAME'): C *OMIT: C *OMIT) **************************************************  ****************************** ************** * *YOURABNORMALPROCEDURENAME * **************************************************  ****************************** ************** PYOURABNORMALPR...B EXPORT DYOURABNORMALPR...PI D CurCnd 12A CONST D pUsrDta * CONST D RtnCod 10I 0 D NewCnd 12A *... Do abnormal cleanup stuff. *... Do normal cleanup stuff. C CALLP YOUREXITPROCEDURENAME C RETURN PYOURABNORMALPR...E **************************************************  ****************************** ************** * *YOUREXITPROCEDURENAME * **************************************************  ****************************** ************** PYOUREXITPROCED...B EXPORT DYOUREXITPROCED...PI *... Do normal cleanup stuff. PYOUREXITPROCED...E 

David Morris

[maxb@bfcsoftware.com]

Mark and David, Thank you for you responses. I will let you how things work out using these API's. Max