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     Returning data to calling procedure

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Returning data to calling procedure
 Login/Join
 
Platinum Member
posted
I have a proc I use in several places that creates a file called MYOWG (via HOLD). If I want to use this in other, calling procedures, what's the best way to do this? HOLD? SAVE? I have a multiuser environment, so if I use a FILEDEF, won't that file be overwritten when the 2nd user calls the proc? Should I use -INCLUDE or EXEC proc?

Thanks.


Thanks.

Mark
WF 7.6 Windows
 
Posts: 150 | Registered: July 26, 2007Report This Post
Virtuoso
posted Hide Post
So are you wanting everyone who runs this procedure to have their own copy of MYOWG?

As for -INCLUDE vs. EXEC, they both do basically the same thing, but -INCLUDE is a little easier if you're passing parameters, easier for troubleshooting because you can see the -INCLUDED code. Also, I think that EXEC opens an additional agent, but I may be mistaken on that.


Regards,

Darin



In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
Platinum Member
posted Hide Post
Yes, essentially, I want the called proc (procB) to return a bunch of data that can be used by multiple calling procedures (probA). Problem seems to be that if procB HOLDs or SAVEs the data, it's not accessible by procA. Or is there a way to do this?

My thought at this point is to define a HOLD (MYOWG) in calling procedure procA with the structure I need, then have called proc procB do a TABLE FILE MYOWG MORE FILE ...

Should that work? Is that the best way to do that, or is there another way?

>>>>>
I have since figured this out...mainly due to my ignorance. I think I misunderstood what a FILEDEF does. What I have done now is created a Focus SYNONYM that I can use for holding the data. Now both procs can access that structure.

This message has been edited. Last edited by: MacLonghorn,


Thanks.

Mark
WF 7.6 Windows
 
Posts: 150 | Registered: July 26, 2007Report This Post
Gold member
posted Hide Post
Why not use a FILEDEF to SAVE to a location with a unique identifier for the filename? Something like a combination of userid and timestamp will normally make it a unique filename. Of course, you then have to worry about cleanup also, otherwise the number of files will get out of hand.


Diptesh
WF 7.1.7 - AIX, MVS
 
Posts: 79 | Location: Warren, NJ, USA | Registered: October 25, 2006Report 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     Returning data to calling procedure

Copyright © 1996-2020 Information Builders