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'm modifying existing code and adding an argument to a call that should just not be an issue. But it is. As best I can tell I've hit some internal limit on arguments. Here's the call:
Call appl_private_ins
From Incoming_Action
passDrgSpecialistID
passDrgSpecialistNm
passInsSpecialistID
passInsSpecialistNm
passInsEligStartDt
passInsEligEndDt
passDrgEligStartDt
passDrgEligEndDt
StkInsInfoEdit.COMMENTS_TXT
StkApplicantEdit
stkPassKey
Current_Userid
StkIndFlg
New_Rec_Flg
i
into
StkIndFlg;
That i at the end of the argument list is the 16th. When the routine being called opens, even if I do absolutely nothing with that argument, nothing seems to work properly.
The question -- is there a limit on the number of arguments you can call a Maintain Form with?This message has been edited. Last edited by: <Emily McAllister>,
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
John We do not document a limit to the number of variables. However, there could be a limit to the number of characters (ie 32K) that we can pass. What is the format of the last variable? What release are you in? Are any of the variables very long?
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003
I added an A3. So either that's not the issue or I'm the unluckiest SOB to ever program.
I can't imagine we're at 32K with this thing. The new form opens, it just doesn't fill. The code that is supposed to execute on startup apparently isn't running.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
I've figured out that Case Top is running, and I can see one stack fill. The rest of the data appears to balk loading when the extra argument is in place.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
I cannot find anything regarding the number of from and to arguments in a CALL. However, I know there is a limit of 15 files in a MAINTAIN command, so it would seem that 15 is the limit for CALLS as well. Can you create a stack which has all the arguments you need to pass?
CALL appl_private_ins FROM StkCall INTO StkIndFlg
I have not run into any limitations with the number of fields in a stack being passed via CALL.
Deana
WebFOCUS 7.6.8 and 7.7.03; Windows Server 2003 R2 and Windows Server 2008 R2, respectively; Development environments - Windows Server 2003 R2 and Windows 7 Professional, respectively; excel, html, pdf