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][Case opened] NOCLOSE: different behavior in WF 8.2

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[Solved][Case opened] NOCLOSE: different behavior in WF 8.2
 Login/Join
 
Danny-SRL
Virtuoso
posted
The NOCLOSE option on a -WRITE dialog manager command used keep the file open until either a -CLOSE command was encountered or the session terminated.
However, in 8.2, it is at the end of the procedure in which the -WRITE is used that the file is closed.
See the following example:

wt.fex
  
-*WT
FILEDEF WT DISK WT.FEX
-RUN
EX WT1
-RUN
EX WT2
-RUN
-CLOSE WT
-RUN
!TYPE WT.FEX

wt1.fex
  
-* WT1
-WRITE WT NOCLOSE WT1

wt2.fex
  
-* WT2
-WRITE WT NOCLOSE WT2


The output in 8.2 is
WT2

In 8.1 it was
WT1
WT2

This message has been edited. Last edited by: Danny-SRL,


Daniel
In Focus since 1982
wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF

 
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006Report This Post
BabakNYC
Virtuoso
posted Hide Post
According to a 7.x to 8.x compatibility case I saw in the support site:

The FILEDEF must have the parameter (APPEND, to allow all the info to be
appended to the file.

FILEDEF DIAT_FILE DISK C:\test.txt (APPEND

Not sure if this might be applicable to you since this is an 8.1 to 8.2 issue.


WebFOCUS 8206, Unix, Windows
 
Posts: 1853 | Location: New York City | Registered: December 30, 2015Report This Post
jgelona
Master
posted Hide Post
Try using -INCLUDE instead of EX. They are not processed the same way.


In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
 
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006Report This Post
Danny-SRL
Virtuoso
posted Hide Post
Babak,
Not necessary with NOCLOSE.
The whole idea with NOCLOSE is just that: the file stays open!

John,
Changing to -INCLUDE is not an option: customers have been using EX.

A case has been opened.


Daniel
In Focus since 1982
wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF

 
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006Report This Post
jgelona
Master
posted Hide Post
Danny, I think the problem is you are a victim of code tightening. When using the EX procname, procname must be a fully executable procedure and in your example it isn't, now if you add a FILEDEF for WT to WT1 and WT2, it will probably work. On the otherhand, -INCLUDE will work just fine. I believe the EX command will get it own agent and therefore knows nothing about the WT ddname.

From the manual

One procedure calls another procedure using:
◾The command -INCLUDE, which incorporates a whole or partial procedure and executes immediately when encountered. (A partial procedure might contain header text, or code to include at run time based on a test in the calling procedure.)


◾The command EXEC. The command is stacked and executed when the appropriate Dialogue Manager command is encountered. The called procedure must be fully executable.


In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
 
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006Report This Post
Danny-SRL
Virtuoso
posted Hide Post
John,
Using your logic, WF should refuse to write to WT in both wt1 and wt2 focexecs.
It should say that a FILEDEF is missing, which it doesn't.
So, IMHO, this is not a case of "code tightening", rather one of a PITN.
And customers fuming...


Daniel
In Focus since 1982
wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF

 
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006Report This Post
Danny-SRL
Virtuoso
posted Hide Post
FYI
In 82M Gen Number 1095, this has been taken care of:
170529018
DMH: NEW - NOCLOSE with - WRITE not kept between ex fexs
A procedure calls several procedures using EX fex where each
procedure issues a -WRITE NOCLOSE to the same ddname. Only the
last -WRITE is showing in the file rather than all the values
from the previous -WRITEs.


Daniel
In Focus since 1982
wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF

 
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 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     [Solved][Case opened] NOCLOSE: different behavior in WF 8.2

Copyright © 1996-2020 Information Builders