As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
New TIBCO Community Coming Soon
In early summer, TIBCO plans to launch a new community—with a new user experience, enhanced search, and expanded capabilities for member engagement with answers and discussions! In advance of that, the current myibi community will be retired on April 30. We will continue to provide updates here on both the retirement of myibi and the new community launch.
What You Need to Know about Our New Community
We value the wealth of knowledge and engagement shared by community members and hope the new community will continue cultivating networking, knowledge sharing, and discussion.
During the transition period, from April 20th until the new community is launched this summer, myibi users should access the TIBCO WebFOCUS page to engage.
I seem to be having some trouble testing date fields within Maintain. When I went looking for info, the DS 5.3 documentation didn't say much, then found a bit here from Mark D. that said Maintain can't test literals, only variables (which sounds a bit lacking).
So one question is: can I test for an empty value ? Would I use a ' ' or 0 for the test literal, or do I have to assign that to a variable ?
ie. If stk.Date_Fld EQ ' ' (or EQ 0) ???
also: For all DbNam.Seg.KeyFld Into stk Where date_Fld NE ' ' (or EQ 0) ???
And why would maintain lack the capability to test for literal values in date fields and not other format types ?
Thanks,This message has been edited. Last edited by: Dave Ayers,
Morning Dave, I have a technique that always works for me. Some of the other ways, testing for either blank or 0 can be inconsistent. Here is what I do:
Compute EmptyDate/YMD; For all next field into stk where date_field NE EmptyDate;
If date_field EQ EmptyDate then...
Just make sure that the format of EmptyDate is the same as your date fields. Now, as for having to use a variable instead of a literal, what is the value of an unset date? Should it be blank? Dec 31, 1900? Zero? I'm not really sure. I find that using a variable removes the question.
Posts: 663 | Location: New York | Registered: May 08, 2003
Thanks for the tip. It seems to have worked, through I had so many issues (business rules as well as technical) with that particular program it's hard to tell at this point.
Also that is something that should be clearly stated in the Maintain documentation ! I can only say that there was no mention of it in the 5.3 online docs.
Heres another little nugget I discovered recently:
In the current set of Maintain programs I'm working on, I am using mostly focexecs to source data for record selection from HTML tables. Some of them have no Calls at all in them. Fine as far as it goes, but I was getting a FOC03839 'Invalid In State' errors on my remote deployment compile.
After a Tech Support Case to find out what in the world that error meant, , and trying 'EXEC xxx Drop' without consistent success, I inserted a Call to a dummy, no op, .mnt before the first EXEC, and no more errors. It's a damn, dumb workaround, but it works !