LogGen1.CSV is the supplied combined export of diary-generation messages and SARA hits.
It brings reported actions and issues into a structured list with page, object, and instruction context. The filename can depend on how the log was saved; use the headings and record content to identify the format.
Use this file to answer “What was reported for this page or SARA?” Compare it with the prepared SARA instruction list and the detailed DTP trace. See Listing SARA Hits for viewing hits in Q++Studio.
NO;LEVEL;MESSAGE;PAGENUM;OBJID;PCODELN
The supplied file is UTF-8 with a byte-order mark and uses semicolons as separators. Read it with a CSV parser that respects quoted fields and doubled quotation marks. Do not split each row at commas or split MESSAGE text manually at semicolons. Preserve record order, accents, and special characters.
Column |
Interpretation |
NO |
Record number in this export. Use it to cite a particular entry; it is not a p-code number or a portable SARA ID. |
LEVEL |
100 identifies a SARA-hit entry. In this sample, the remaining generation messages have value 101. Do not interpret the numerical ordering as a severity scale. |
MESSAGE |
The recorded action or generation message. SARA hits include the command and a result such as deleted, replaced, or changed format only. Other messages may begin with a message ID. |
PAGENUM |
Page associated with the reported entry. Match it to the output-page context of the run. Zero in a global message does not identify a page to inspect. |
OBJID |
Object associated with the entry, where supplied. Interpret together with PAGENUM and the operation; zero may mean no specific object. |
PCODELN |
Instruction context. For LEVEL=100 in this sample, this corresponds to the 1-based SARA command number in the prepared list and plugin loading sequence. Confirm by matching command text; do not treat it as a physical log line or automatically as a pcl. number from qpplog.txt. |
NO;LEVEL;MESSAGE;PAGENUM;OBJID;PCODELN
3;100;"{| · END}={|}, deleted « · END»";16;4;1
This is a literal CSV excerpt from the complex run. Record NO=3 reports a hit for SARA command 1, on page 16/object 4. The command deletes the matched text “ · END”. PCODELN=1 identifies the SARA command in this run; NO=3 identifies this particular hit record. The double quotes delimit MESSAGE in the CSV file.
Read the Outcome as Well as the Command
Recorded outcome |
What it establishes |
deleted «…» |
The matched text was reported deleted. |
replaced «…» with «…» |
The reported match and replacement text, in the log’s display notation. |
changed format only of «…» |
A formatting action was reported while the matched text was retained. This is a hit, even though the visible string does not change. |
A hit records an action at that stage of processing. A later SARA can act on the same text or paragraph, and final checks can still report overflow or missing resources. Do not infer the final appearance solely from a hit message.
Repeated rows with the same page, object, command, and message can represent separate occurrences. Count recorded hits without deduplicating them. When a screenshot or font substitution makes a result ambiguous, retain both the hit record and the matching DTP trace.
Worked Example: 23 Commands and 521 Hits
The complex-run file contains 535 records: 521 SARA hits (LEVEL=100) and 14 other generation messages (LEVEL=101). The hit messages comprise 340 deletions, 170 formatting-only actions, and 11 text replacements. Nineteen of the 23 prepared commands have recorded hits.
Command number / PCODELN |
Recorded hits |
Diagnostic reading |
1–6 |
53, 121, 33, 22, 21, 3 respectively |
Deletions and formatting changes on pages in the 16–19 selection. |
7 |
0 |
The first deletion command for pages 20–23 has no recorded hit; this alone does not establish an error. |
8–11 |
123, 33, 5, 21 respectively |
Other commands in the 20–23 selection do have hits. |
12–17 |
36, 2, 2, 18, 2, 1 respectively |
Paragraph-rule changes and whitespace replacements on pages 24 and 25. |
18 |
0 |
Find-font criterion: Laenderkennzeichen2026 Regular; investigate the unavailable-font message. |
19–21 |
18, 4, 3 respectively |
Recorded actions on page 26, within the 26,27 selection. |
22–23 |
0, 0 |
Find-font criteria use Laenderkennzeichen2026 Regular and AstrologyP01; both are reported unavailable during command loading. |
The command number is established by counting logical instructions, not physical TXT lines: command 10 includes raw control characters. The absence of hits for commands 18, 22, and 23 is consistent with a font-related problem, but the logs do not prove that installing the fonts would be sufficient to produce every expected match.
Follow One Result Across the Three Files
The longer examples below show the parsed CSV fields, with MESSAGE wrapped for readability; they are not additional literal CSV rows.
NO=87; LEVEL=100; PAGENUM=16; OBJID=4; PCODELN=6
MESSAGE:
{rx|(?<=Kerstmis )(\(B\))}={COLOR(C=0 M=100 Y=0 K=0)|$0},
changed format only of «(B)»
For the lookbehind example, locate command 6 in the prepared list. It searches for “(B)” following “Kerstmis ” on pages 16–19 and preserves the match while changing its color. Filter the CSV by LEVEL=100 and PCODELN=6: the three entries report formatting-only hits. NO=87 identifies one on page 16/object 4. In qpplog.txt, locate the same SARA command and textbox to inspect the surrounding execution.
Example: A Capture-Group Replacement
NO=476; LEVEL=100; PAGENUM=24; OBJID=5; PCODELN=14
MESSAGE:
{rx|(.{1,}\d{4})(\s)(\s)}={|$1$3},
replaced «Oktober 2028&c&t» with «Oktober 2028&t»
For capture-group replacement, NO=476 has LEVEL=100, PAGENUM=24, OBJID=5, and PCODELN=14. Its message reports “Oktober 2028&c&t” becoming “Oktober 2028&t”, consistent with $1$3 omitting the second captured group. Here &c displays a return and &t a tab; retain that notation when citing the CSV.
These are meaningful special-character markers, not decorative text. For spaces, returns, tabs and other supported markers, consult Special Character Markers — InDesign. Compare their meanings as well as the visible strings when explaining a replacement.
Generation Messages Require Their Own Interpretation
The 14 non-hit entries include two messages about creating missing layers, one missing picture, eight missing fonts, and three text-overflow reports. These are different conditions, despite all using LEVEL=101 in this file. A missing layer followed by “creating it” describes a corrective action; it is not equivalent to an unresolved missing picture.
Example: A Missing-Font Message
NO=531; LEVEL=101; PAGENUM=0; OBJID=0; PCODELN=0
MESSAGE:
185920-Missing font with name «Laenderkennzeichen2026 Regular» and face «Regular»
This is a generation message, not a SARA hit. The message identifier is 185920, whereas 531 is the exported record number. Page, object and PCODELN are zero here because this entry does not identify a particular target or SARA command. Compare the same font name with the command-loading excerpt in the DTP Generation Log topic.
Example: A Text-Overflow Message
NO=533; LEVEL=101; PAGENUM=16; OBJID=1; PCODELN=0
MESSAGE:
108530-Text overflow in box 1 of page 16 (Belgische feestdagen en koningsdagen zijn optionee ...)
This entry identifies a specific target: object 1 on page 16. The parenthesized text is a preview included in the original message, including its ellipsis. It helps locate the affected box; it does not by itself establish whether the cause is missing fonts, extra text, box dimensions or another setting.
A leading number such as 185920 is a message identifier within MESSAGE, distinct from NO, LEVEL, and PCODELN. Retain the identifier and message text when investigating a report. In this sample, the overflow messages identify page 16/object 1, page 17/object 8, and page 18/object 14. The global missing-font messages use page and object zero.
Separate SARA-hit analysis from generation-message analysis. For hits, give counts by command and by page/object where relevant, including prepared commands with zero recorded hits. For other messages, group by message ID and retain affected targets. Explain what is directly recorded and which proposed causes still require checking the script, fonts, template, or final document.
Confirm that this export includes the relevant messages and hits for the same generation before using an absent row as evidence. A filtered or partial export cannot establish that no hit occurred elsewhere. Keep the original file available alongside any grouped summary; see the diagnostic-files overview.
Topic 189905, last updated on 22-Oct-2026
