Hi Mark, Thanks for the feedback. Your second suggestion is the one I have adopted for the time being. I'll look forward to testing the update when it is released.
Thanks Richard Wilkinson Leicestershire County Council ------Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of mark2atsafe Sent: 10 January 2006 00:26 To: [email protected] Subject: [fme] Re: FME_MF_NAME - Another Predefined macro question Hi Richard, Does indeed seem like this is the problem. It's proposed that we have a workspace name macro available in this TCL - I think it's a small enough change to be done in FME2006GB (or a beta version) so expect to see it in the near future. In the meantime I hope one of our previous suggestions helps. Mark Mark Ireland, Product Support Engineer Safe Software Inc. Surrey, BC, CANADA [EMAIL PROTECTED] http://www.safe.com Solutions for Spatial Data Translation, Distribution and Access --- In [email protected], "mark2atsafe" <[EMAIL PROTECTED]> wrote: > > Hi Richard, > I haven't asked around but my theory would be that the TCL is being > run in a separate FME process - one which uses a temporary mapping > file called wb-xlate-a03680 (or whatever). > > Suggestions... > > 1) Use $FME_MappingFileId - I don't know what this is supposed to give > - but you can try it and see. > > 2) Create a macro within the workspace that contains the filename and > pass that through to the TCL. I think you can do this as... > > FME_END_TCL source xxxx.tcl; procname {$(macroname)} > > There have been a few recent messages here about how to pass info to > the TCL. You may also find fmepedia.com useful > > http://www.fmepedia.com/index.php/Pre_and_Post_Processing_with_TCL_FAQ > > Hope this helps > > Mark > > Mark Ireland, Product Support Engineer > Safe Software Inc. Surrey, BC, CANADA > [EMAIL PROTECTED] http://www.safe.com > Solutions for Spatial Data Translation, Distribution and Access > > > --- In [email protected], "RichardW" <[EMAIL PROTECTED]> wrote: > > > > A Happy new Year to all FME'ers > > > > FME_MF_NAME should expand to the name of the mapping file. > > > > To test this expansion I put the following line in the mapping file > > header, taken from the example in the documentation. > > > > TCL puts {FME_MF_NAME= $(FME_MF_NAME)} > > > > It produced the following output > > > > FME_MF_NAME= wb-xlate-a03680 > > > > > > My Mapping file is called AggregateTest.fmw which is what I expected > > FME_MF_NAME to expand to but it did not. > > > > Can anyone explain this and tell me how I can get the actual .fmw > > filename from within a fme_end_tcl script. I want to include this in > > my log entry. > > > > Thanks > > Richard Wilkinson > > Leicestershire County Council > > > Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links _______________________________________________________________________ Leicestershire County Council - rated a 'four-star' council by the Audit Commission _______________________________________________________________________ This e-mail and any files transmitted with it are confidential. If you are not the intended recipient, any reading, printing, storage, disclosure, copying or any other action taken in respect of this e-mail is prohibited and may be unlawful. If you are not the intended recipient, please notify the sender immediately by using the reply function and then permanently delete what you have received. Incoming and outgoing e-mail messages are routinely monitored for compliance with Leicestershire County Council's policy on the use of electronic communications. The contents of e-mails may have to be disclosed to a request under the Data Protection Act 1998 and the Freedom of Information Act 2000. The views expressed by the author may not necessarily reflect the views or policies of the Leicestershire County Council. Attachments to e-mail messages may contain viruses that may damage your system. Whilst Leicestershire County Council has taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
