Urgent! XMI Export Log file - where is it?

[Eve]

In that case I'll bow out of the conversation. I'm here to help with specific issues, not engage in hypothetical discussions about how you think something should behave.

[qwerty]

To me a log is the same as what Paolo stated. Even if it doesn't give me a hint what went wrong it should help supporters to get me on track or even detect programming issues. Well, Sparxian thinking hasn't reached me for a long time.

q.

[Paolo F Cantoni]

In that case, I'll bow out of the conversation. I'm here to help with specific issues, not engage in hypothetical discussions about how you think something should behave.

OK, so here is a specific situation.

I have Integrity Checked the model to ensure no errors. I have selected a controlled package (at root level).  I have selected [ x ] Log Import / Export I have checked the entries in t_package to confirm "alles ist in ordnung".  The package is a LARGE package.  I have started the export and after half an hour (I expect the export to take many hours - since XML export is quite slow, relatively speaking) there is NO sign of the export file and, more importantly, NO sign of the log file.

I don't really expect to see the XML export since, from previous observations, it looks like a temporary file is used prior to final formatting and so it may be in some temporary location (which, nevertheless, would be good to know).  However, if the log file specification is as you described earlier: "The log file will be created in the same directory as the target XMI. package.xmi will produce a log file package_export.log." Then I would expect to see a file <package_name>_export.log there by now.  There isn't one.

In the above scenario is anything askew?  If not, why don't I see a log file?

Paolo

[Eve]

The XMI is created in memory. You won't see it anywhere until it's finished. Unfortunately, I suspect the same is true of the log file.

It's also worth noting here that turning off 'Format XMI Output' will be a noticeable difference on a large file. Also, have you tried the native xml export. That's much faster than generating XMI.

[Paolo F Cantoni]

The XMI is created in memory. You won't see it anywhere until it's finished. Unfortunately, I suspect the same is true of the log file.

It's also worth noting here that turning off 'Format XMI Output' will be a noticeable difference on a large file. Also, have you tried the native XML export. That's much faster than generating XMI.

(my emphasis)
Then, by definition, it's NOT a log file.

By Native XMI export you mean the Publish | Model Exchange | Export-XML | Export XML For current package and selecting (o) Native, yes?

I am giving it a go...

Though I note, with dismay, the absence of being able to specify a log file...

Paolo


[EDIT:  Notwithstanding the lack of a log file, the export completed within 15mins and I now have a <package_name>.xml file of ~0.5Gb.  I'll try importing it.
So, thanks to Eve, for suggesting this route]

[qwerty]

As I said: alternative facts. Aka. fake.

q.