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.
until today, we ran only FOCEXECs with read permission against IMS databases. now we are going to DELETE some segments in a IMS HDAM DB via SQL statements. at runtime we get a FOC42011 (WRITE=NO). we have RACF-rights for a update, the PSB has PROCOPT=A, a FOCPSB-member is provided. we have no experience with access files. any idea what is missing ?
Sounds like WRITE=NO is set in the access file. Can you try to change the access file to WRITE=YES and re=run the code? (I might be over simplifying but it's worth a shot).
Posts: 118 | Location: DC | Registered: May 13, 2005
best of all, we don't use a access file. (as I wrote) Today I created one, allcated it and the syntax-errors were gone. But I got a 0C4 at runtime. But this may be annother story.