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.
ibit####.pdf is the file name given to the components of a compound report. Where #### is an incrementing number from ibit0001 to the total number of components in the compound report. Each component seems to create a ibit####.pdf in the associated app folder. Here's the PARs:
The Problem: These files can be overwritten when the users execute the same compound report with different parameters concurrently. So, their final compound report may consist of some of their ibit####.pdf components and some of another execution of the same report.
The Action which needs to be taken: To Be Determined.
The desired Result: Different / unique names for those components.
Thanks in advance for your pointers...This message has been edited. Last edited by: Kerry,
In FOCUS Since 1983 ~ from FOCUS to WebFOCUS. Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
Unfortunately: Yes I do have APP HOLD in my fexes. They're needed because I have to have a source file for the Dynamic Distribution List (DDL) in RC. That is build in my main extract procedure. That’s only needed because I need a predefined source file for the DDL list creation. Otherwise, I’d need one fex for each of the 40+ Report Caster Jobs / Tasks in this application.
-Doug
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005
How about manually allocating your DDL files via APP MAP / FILEDEF while still leaving APP HOLD untouched (pointing to EDATEMP) for the rest? Very simplistic?
Can't you rearrange APP PATH and APP HOLD after the "main extract", so that what was the hold folder is simply part of the path, and app hold points to the agent's work folder?
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
Thanks Guys... I can do those things suggested. I can even delete those files via DELETEF. But, back to my original question: can they be renamed? Kinda like the eay you can "rename" a HOLD file. That is, if the "AS MYNAME" is not used, then the name is "HOLD" (kinda)...
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005