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.
The previous step deletes earlier file , while later it is not allocating the same dsn.
Code has below specs: -**************************************************************** -SET &ALLOCX2E = 'PP0TDSMI.LSEQ.TDS0207.EXPDEFRD.S'|&DATE_RUN; DYNAM FREE DDNAME HOLD2E DYNAM DELETE &ALLOCX2E DYNAM ALLOC FILE HOLD2E DA &ALLOCX2E - SPACE 30,10 CYLINDER NEW
while when running it is not picking the last character of date , which should be 160822. But it is picking the below and giving error. [I]ERROR AT OR NEAR LINE 394 IN PROCEDURE TDS0207 FOCEXEC FOC855) UNABLE TO LOCATE DATASET PP0TDSMI.LSEQ.TDS0207.EXPDEFRD.S16082 #026-08This message has been edited. Last edited by: <Emily McAllister>,
I tried to run this in test , there it is picking the correct date but the error is same.
DYNAM DELETE TDSMI.TEST.TDS0207.EXPDEFRD.S160822 ERROR AT OR NEAR LINE 394 IN PROCEDURE JULY0207FOCEXEC (FOC855) UNABLE TO LOCATE DATASET TDSMI.TEST.TDS0207.EXPDEFRD.S160822, #026-08
Why it is not finding this Dataset, I can see it when browsing... (through 3.4) ?
I suspect it's a (harmless) warning that the DELETE failed.
If the previous allocation of HOLD2E was a temp dataset, then after the FREE the dsn disappears and there is nothing left to delete.
As to the truncated dsn in the error msg, that may just be a space limitation in the message generator. What does the dsn look like in the echo of the dynam delete statement?
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005