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.
I have scheduled jobs that do DB2 hold files, and they seem to run smooth more often or not. However, every once in awhile, I'll get an error like the following:
FIXFORM SUBCOMMAND ELEMENT OR FIELDNAME NOT RECOGNIZED: TGT_BATCH_DT
The fieldname referenced is indeed not part of the query, but I have no idea how the heck it gets brought in. What is common is that the field is recognizable as one that I use in other queries, but those queries aren't necessarily running when this error occurs. The output table always ends up being empty as a result of the error.
Could there be some sort of memory leak, or is there some sort of code I can put in to protect myself? I've only received this error with DB2 hold files. We're on 7.1.4.
Posts: 59 | Location: Minneapolis | Registered: September 01, 2004
When you are creating HOLD files in a database format...like FOCUS... it is actually a two-step process. The data is extracted to a HOLD file called FOC$HOLD and then a MODIFY is used to load the data into the file. The FOC$HOLD master is used to read the data for the MODIFY.
I'd expect the same thing is occurring here.
The problem comes when the FOC$HOLD master already exists in your path (perhaps created by a similar job) and gets read instead of the one created as part of this job.
Are you using an APP HOLD command in some procedures to write HOLD files to a specific application folder? Ensure that FOC$HOLD master is not be kept in some of your jobs.
ttfn, kp
Access to most releases from R52x, on multiple platforms.
Posts: 346 | Location: Melbourne Australia | Registered: April 15, 2003