CEE* FC handling (was RE: date math in CL)

Tom, 

Thanks for the ... eh ... "feedback"  <g>

Obviously, as I showed in the example I posted, I didn't want to clutter
the post with error handling, but just to demonstrate a solution to the
original question.  So you and I are on the same page; I just wanted to
know, well, maybe better stated, confirm that you did it that way for just
the reasons you stated.

ANYWAY, so here is the new thread on the FC.  This was my first foray into
the CEE world that will end up in a production environment.  As I looked
at the documentation for the CEEDAYS & CEEDATE APIs, I didn't find any
*good* information on the FC.

In my demo CL, I did a dump and the FC variable has a value of
X'0000000041C3C5C500000000' after a successful CEEDATE call.  The
X'C3C5C5' is 'CEE'

Don't have a lot of time to get into it now, but for those interested, it
appears that the IBM docs on the FC are in the ILE Concepts manual,
chapter "Exception and Condition Management", section "Condition
Handling".  The short of it seems to be is that, if the first 4 bytes of
the FC are hex zeros, then the CEE proc call was successful.  Other than
that, I haven't had time to dig in further, so if others are so inclined,
please report back here.  If someone has already invented this wheel,
please let us know.

GA

--- Tom Liotta <qsrvbas@xxxxxxxxxxxx> wrote:
> GA:
> 
> I can copy/paste and send easily enough when I have my own sample stuff
> just sitting around. It's effectively impossible to send "production"
> quality code which includes proper error handling, messaging, etc., etc.
> In this case, I messed around with a number of CEE* APIs and had a ready
> made sample. I left out fc simply because I didn't need it to
> demonstrate these APIs to myself.
> 
> I gotta figure others will use samples as a guideline. They can see the
> structure and enough detail to find everything else in the proper
> manuals. Besides, sample code should _never_ be included without first
> understanding the details... well, unless it's your own system or
> similarly unrestricted.
> 
> Now, the feedback code -- fc -- is common across many of the CEE* APIs.
> Learning to handle it is the subject of a different thread. It certainly
> ought to be handled properly in _production_ code, but can clutter
> simple examples. In this case, the question was essentially direct: How
> can date math be done in CL? The sample, which you also worked out, can
> be just as direct. Uncluttered, minimum details to show the process.
> 
> Send another question explicitly about fc and let's see how many kinds
> of responses exist. That could be a big learning experience for all of
> us -- me included.
> 
> Tom Liotta



        
                
__________________________________
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash