The answer is that there is no negative fallout from Log Parser for not testing the length of the Message string. Just trying the following seems to work.
SUBSTR(Message, 0, 1999) AS Message1,
SUBSTR(Message, 2000, 1999) AS Message2,
SUBSTR(Message, 4000, 1999) AS Message3,
SUBSTR(Message, 6000, 1999) AS Message4,
Chunking the data is ugly, but following up the import with a stored procedure, from a vbs script allows me to import the rest of the way into a CLOB (Oracle).