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.
Our company is upgrading to Focus 7.2 for S/390, and in testing our 7.0 focexecs we have run across a problem with defined fields. It seems that whenever there is a defined field that does not reference an actual "real" field in the master, we get a FOC062. The only way we've been able to get around this is by adding a WITH clause to the defined field. Has anyone else experienced this? We were hoping to not have to make any code changes in our focexecs. Any insight would be helpful (Susannah??) Thanks! Jen
FOC062) A CONSTANT REQUIRES A REAL FIELD ON THE LEFT SIDE. USE 'WITH': A constant is calculated but no real fields are specified. Use the form: 'fieldname WITH realfield = expression;'. The real field indicates the point at which the expression is evaluated during the retrieval.
Posts: 68 | Location: Springfield MA | Registered: May 07, 2003