How can I create an FM-style error log by scripting ?

With the pointers from Rick and Klaus, I managed to adapt the BookErrorLog to do what I wanted it to do. It is, as Klaus indicated, simply a FrameMaker document which is opened from the fminit directory. And even though it is read-only, I can still make changes to it via scripting. So now my conversion log has exactly that title, and all issues that were found are hyperlinked to the location where they were found. 

See also the FDK Programmers Guide and Reference PDFs, where the Book Error Log syntax is detailed.

Hi Jang,

Here is a simple function that I use:

CP.writeBookErrorLog = function (objId, docId, bookId, msg) { 
    
    /// msg = CP.writeBookErrorLog (objId, docId, bookId, msg);
    
    msg = 'log -b=' + bookId + ' -d=' + docId + ' -o=' + objId + ' --' + msg;
    CallClient ('BookErrorLog', msg);
    
    return msg; // Return for troubleshooting.
};

You need to pass in the ids of each of your objects; for example, book.id, doc.id, pgf.id, etc. If you aren't running it on a book, pass in 0 for the bookId. msg is the text that you want to appear.

The book error log is actually a FrameMaker document. You can see that by pressing Esc F l k to unlock it. Here is some code I use to get its object handle so I can save it, etc.

CP.getBookErrorLogDoc = function () {
	
	var regex, doc;
	
	// Regex for findingthe book error log.
	regex = /Book Error Log/;
	
	doc = app.FirstOpenDoc;
	while (doc.ObjectValid () === 1) {
		if (regex.test (doc.Label) === true) {
			return doc;
		}
		doc = doc.NextOpenDocInSession;
	}    
};