ASCIIOUTPUT file locking/unlocking
Posted: Thu Dec 05, 2013 4:23 am
Hi all,
as you are probably aware, when calling an ASCIIOUTPUT function, TM1 will open the file for writing during the duration of the Prolog/Meta/Data/Epilog tab, then close it when proceeding to the next tab or exiting the process.
Question: Is there any way to force TM1 to close the file without needing to move to the next tab or exit the process?
...the context is I am creating a set of files that requires header+detail+footer sections. The header/details are written during the Data tab, and the footer files are written during the Epilog tab.
The next step is to merge all the detail+footer files together - however I have found I cannot do this during the Epilog tab of the original process (presumably because the footer files are still open) - hence I would need to create a whole new process just to merge the files.
Note: calling another process (to executecommand) from the Epilog also didnt seem to work - it appears that you have to exit the Epilog of the original process entirely.
Anyway, if anyone has any tips or workarounds for this it would be much appreciated.. otherwise I'll just have to go the long way around :p
Cheers,
Matt
as you are probably aware, when calling an ASCIIOUTPUT function, TM1 will open the file for writing during the duration of the Prolog/Meta/Data/Epilog tab, then close it when proceeding to the next tab or exiting the process.
Question: Is there any way to force TM1 to close the file without needing to move to the next tab or exit the process?
...the context is I am creating a set of files that requires header+detail+footer sections. The header/details are written during the Data tab, and the footer files are written during the Epilog tab.
The next step is to merge all the detail+footer files together - however I have found I cannot do this during the Epilog tab of the original process (presumably because the footer files are still open) - hence I would need to create a whole new process just to merge the files.
Note: calling another process (to executecommand) from the Epilog also didnt seem to work - it appears that you have to exit the Epilog of the original process entirely.
Anyway, if anyone has any tips or workarounds for this it would be much appreciated.. otherwise I'll just have to go the long way around :p
Cheers,
Matt