VERIFIED SOLUTION i

Information about MailStream Plus's and EngageOne Delivery Audit's Job Description, Job Name, and Mail360 Owner Code field lengths.

MailStream Plus all versions
EngageOne Delivery Audit all versions
 
MailStream Plus (MSP)can produce the Mail Piece Job file using the IMBCTL parameter. This file is used as input to the separate product "EngageOne Delivery Audit" (EODA). EODA (formerly called 'Mail360 Data Manager') is used to track Mail Pieces thru the USPS delivery system.

MSP has xx INF parameters M3JOBD, M3JOBN, and M3OWNI to populate the Job Description, Job Name, and Mail360 Owner.  Each of these fields is allowed to be up to 30 bytes.

Per the Mail Piece job file layout in the EODA User's guide, the lengths allowed for the same fields in that application are:
Job Description   512 bytes
Job Name           50 bytes
Owner Code         64 bytes

Although the Mail Piece Job file is allowed to have the fields larger in EODA, MSP only supports populating the first 30 bytes for each.  If a larger size text field is put on one of those MSP xx INF parameters, a message like the below will occur-
RP INF                     M3JOBN M3JOBN7891123456789212345678931234567894123456
                                                                ########         0009: Data Length for RP INF is Invalid
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8


The MSP job will continue normally, but will ignore the extra bytes over the MSP 30 byte limit. 
UPDATED:  January 3, 2018