Data360 Analyze

Hi,

Recently we have had several dataflows in which the Scratch file sizes have been extreme - crashing the server on a couple of occasions !

To help analysts manage the space as they develop – is there any "easy" way to check the Scratch files and folder without needing to copy the Scratch file path from the Node Log ?

                Are the (Scratch file) Output Data paths available though a D360 property ?

                Is there some sneaky trick which would help analysts "map" from the rather cryptic Scratch file names back to an identified node ?

Any suggestions would be appreciated

------------------------------
Tim Ross
Revenue Assurance
TELSTRA LIMITED
Melbourne VIC
------------------------------

By Scratch files you mean the temporary execution data files.

If that is the meaning, then yes you can obtain the base directory in which these files will be stored using the ls.brain.tempDir property.

------------------------------
Adrian Williams
*Precisely Software Inc.
------------------------------

Thanks for the reply Adrian. 

Unfortunately it is the "<Tempfilename>.brd"  part which I'm looking for

------------------------------
Tim Ross
Revenue Assurance
TELSTRA LIMITED
Melbourne VIC
------------------------------

Original Message:
Sent: 06-26-2025 07:16
From: Adrian Williams
Subject: Finding and mapping SCRATCH files

By Scratch files you mean the temporary execution data files.

If that is the meaning, then yes you can obtain the base directory in which these files will be stored using the ls.brain.tempDir property.

The format of the path to the temp file (.brd) is <tempExecutionDir>/<UID_1><Username>/<Data_Flow_Name>/<UID_2>/<Tempfilename>.brd

However, I don't know of a way to identify the node that generated the output file.

------------------------------
Adrian Williams
*Precisely Software Inc.
------------------------------