How to Use Built-in Variables (NR, NF, FNR) in awk on Linux

When you are writing advanced data manipulation scripts using the awk compiler in a Linux terminal, relying purely on manual counters (e.g., i++) to track file progress is computationally inefficient. The GNU awk engine is pre-loaded with a matrix of highly optimized, dynamic internal state variables. By mathematically monitoring these variables, you can force the script to execute specific logical operations based on its exact geographic position within a file.

Executing the State Variable Matrix

The three most critical architectural variables for positional awareness are NF, NR, and FNR.

• NF (Number of Fields): An integer representing exactly how many distinct columns (fields) exist in the current record being parsed.
• NR (Number of Records): A global integer counter representing the total number of lines processed so far across all input files.
• FNR (File Number of Records): A local integer counter representing the number of lines processed in the current file only. It mathematically resets to 1 whenever awk opens a new file.

Deploying the Positional Vector

Imagine you have two files: data1.txt and data2.txt. You need to combine them, but you must mathematically tag each line with its original file line number, its global line number, and ignore any lines that are structurally broken (e.g., they don’t have exactly 4 columns).

To execute the precision monitoring vector, analyze this structural command sequence:

awk '{ if (NF == 4) { print "Global:", NR, "| FileLine:", FNR, "| Payload:", $0 } else { print "Anomalous Record Detected at Global:", NR } }' data1.txt data2.txt

Analyzing the State Calculus

The exact millisecond you execute this script, the awk engine intercepts the payload.

• The engine opens data1.txt. It reads the first line.
• It instantly updates its internal state: NR = 1, FNR = 1. It sweeps the line and calculates it has 4 columns (NF = 4).
• The logic gate if (NF == 4) evaluates to True. It prints: Global: 1 | FileLine: 1 | Payload: ...
• It reaches line 100 of data1.txt. The state is NR = 100, FNR = 100.
• The engine finishes data1.txt and violently transitions to data2.txt.
• It reads the first line of data2.txt.
• It instantly mutates its internal state: NR = 101 (the global counter continues to increment), but critically, FNR = 1 (the local counter mathematically resets).
• If it detects a broken line with only 3 columns, the NF == 4 gate fails. The engine drops to the else block and prints the anomaly warning, using the NR variable to pinpoint exactly where the catastrophic data failure occurred in the master stream.