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.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I have a fex that is returning the following error:
(FOC36346) INCORRECT USE OF DATE-TIME FIELD OR CONSTANT
Here's my fex... -SET &Y6MO = DATECVT((DATEADD((DATECVT(&YYMD,'I8YYMD','YYMD')), 'D', -183)), 'YYMD','HYYMDI'); TABLE FILE JOBDATA SUM CNT.DST.BIDID AS 'COUNT,DISTINCT,BIDID' BY CLIENTID WHERE BIDOUT GE &Y6MO;
Here's an excerpt from the jobdata master file. FIELDNAME=BIDOUT, ALIAS=bidout, USAGE=HYYMDI, ACTUAL=HYYMDI, MISSING=ON, $
I figured a DATECVT to HYYMDI would make it compatible with the BIDOUT field of the same type.
Any ideas?
Prod: Single Windows 2008 Server running Webfocus 7.7.03 Reporting server Web server IIS6/Tomcat, AS400 DB2 database.
If you -TYPE your &Y6MO variable, you will see that it is not a datetime stamp. If you just need the time to be zeroes, you can set up the amper variable so that it is just a date and then concatenate the time to it and use the second variable in your WHERE clause.
You may probably want to use a combination of the techniques provided by both jimster06 and GinnyJakes. I just did and it help me to solve a query problem I was having when trying to retrieve information from Oracle table:
-* Any date to be processed
-DEFAULT &MYSTARTDT=20080701;
-* Go 6 months back (or something like that) and set value as date/time
-SET &MYSTARTDTTM=EDIT(DATECVT(DATEADD(DATECVT(&MYSTARTDT,'I8YYMD','YYMD'), 'D', -183), 'YYMD','A8YYM'), '9999/99/99') | ' 00:00:00';
-TYPE &MYSTARTDTTM
-* Retrieve from DB
TABLE FILE ...
PRINT ...
WHERE DTTM_IN_TABLE GE DT(&VACTSTARTDT);
END