Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Weird Behavior when calling a stored procedure

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] Weird Behavior when calling a stored procedure
 Login/Join
 
Virtuoso
posted
If I call a DB2 stored procedure directly, it returns a string that is exactly two characters longer than anything I specify for it. Example:

REMOTE DEST = MVS
-REMOTE BEGIN

TABLE FILE VSTP22A
OUTP
-* OUTP/A1550
-*PRINT COMPUTE OUTPUT_LINE/A1550 = SUBSTR(1550, OUTP, 1, 1550, 1550, 'A1550');
WHERE INP IN
(
'19XFA1581'
)
ON TABLE SET HOLDLIST PRINTONLY
ON TABLE SET EMPTYREPORT ON
ON TABLE HOLD AS PRE_LIST
END
-REMOTE END


I will get the following error from this request:

03/16/2018 11:26:26     LOOPBACK                         NUMBER OF RECORDS IN TABLE=        1  LINES=      1
03/16/2018 11:26:26     LOOPBACK                         (FOC034) THE PRINT LINE EXCEEDS THE MAXIMUM LINE WIDTH. WIDTH IS: 1552
03/16/2018 11:26:26     LOOPBACK                         (FOC1400) SQLCODE IS 34 (HEX: 00000022)
03/16/2018 11:26:26     LOOPBACK                         : THE PRINT LINE EXCEEDS THE MAXIMUM LINE WIDTH. WIDTH IS: 1552
03/16/2018 11:26:26     LOOPBACK                         (FOC1405) SQL PREPARE ERROR.


It doesn't matter what value I put for the length of the string, I get the errors above, and the width is shown to be two characters bigger than the length I specify. When I put in 1550, it tells me 1552 is too big. When I put in 1552, it tells me 1554 is too big.

I'm more or less stuck with the error because it grows to exceed whatever I specify. The proper length is 1550. You can see the two commented-out lines where I've tried to work around the issue, but to no avail. I get the same errors regardless.

I can use the stored procedure as the child of a join and pull the field, but that's problematic in my case. So the field can populate and work properly, just not when I call the routine directly.

This message has been edited. Last edited by: FP Mod Chuck,



 
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007Report This Post
Virtuoso
posted Hide Post
John

Just a guess but try SET PANEL=2000


Thank you for using Focal Point!

Chuck Wolff - Focal Point Moderator
WebFOCUS 7x and 8x, Windows, Linux All output Formats
 
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005Report This Post
Virtuoso
posted Hide Post
That moves me on to my next error! Thanks!



 
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007Report This Post
Guru
posted Hide Post
quote:
my next error!



John, what was the "next error"?


WebFOCUS Administrator @ Worldpay FIS
PROD/DEV/TEST: 8204, SANDBOX: 8206 soon - BIP, Reportcaster, Resource Manager, EUM, HyperStage soon, DB: HIVE,Oracle,MSSQL
 
Posts: 291 | Location: Greater Cincinnati  | Registered: May 11, 2005Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] Weird Behavior when calling a stored procedure

Copyright © 1996-2020 Information Builders