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.
There are many ways to do this and doing a Forum search will identify some. Here is one way.
DEFINE FILE CAR
SMDATE/MDYY=&MDYY;
DATEI/I8MDYY=SMDATE;
DTYY/A2=EDIT(EDIT(DATEI),'$$$$$$99');
DTMO/A2=EDIT(EDIT(DATEI),'$$99');
END
TABLE FILE CAR
PRINT COUNTRY SMDATE DATEI DTYY DTMO
IF RECORDLIMIT EQ 1
END
Are you running this in a mainframe FOCUS environment as well as a WebFOCUS environment?
Are the Masters the same? There's nothing that's new in the DEFINE statements and they should work in both environments, so the only thing I can think of is that the Masters are different.
Or there is invalid data in the Date column.
(FOC1426) DATA ELEMENT VALUE TOO BIG FOR SEGMENT/FIELD %1%2%3%4
An error occurred when converting a data item for the field in the segment with the names given in the message. Data could not be converted without truncation from the USAGE to the ACTUAL format. FOCERROR is posted to 1426.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
This process is being run only on the Mainframe. In WebFocus, there is an app that is running successfully against this table, using the RPT_D field. The MFDs are identical,as verified by a compare function.
The RPT_D field appears to be fine, based on the success in WebFocus, and the table data - in part:
RPT_D PROD_N ENT_TY_C TX_CT DATE CHAR(7) CHAR(3) SMALLINT ---PRIMARY PRIMARY PRIMARY- -------- ****** **************************** TOP OF DATA ******* 000001 01/01/2007 0000208 010 4 000002 01/01/2007 0000208 019 5 000003 01/01/2007 0000208 030 9 000004 01/01/2007 0000216 010 5
It's resolved - Our FOCUS environment is configured different than the WebFocus environment - hardly optimal. The FOCUS environment doesn't handle DB2 dates. The MFD in FOCUS needed to have (as opposed to DATE for WebFOCUS): FIELD=RPT_D ,RPT_D ,A10 ,A10 MISSING=OFF,$