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.
Depending on how you install your database, the rows may or may not be locked by Maintain when you do a database command. If you never want the rows locked, issue a COMMIT statement after database commands like NEXT, UPDATE, INCLUDE and DELETE. This will break the lock. If this is an SQL database, you can install with the Repeated Read option.
As for the disconnect error, there are MANY reasons for this. The first is if you exit the Maintain application by clicking on the Browser X instead of a proper exit button. You can get rid of that by adding: MNTCON EXIT_WARNING OFF in your ESASPROF.PRF.
If the error occurs at runtime, like when clicking on a calendar, make sure you have the most current versions of the calendar files available. I need more details.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003