Rules for coding text strings

• Put the text string in the first request unit (RU) in the first chain at the start of a print request. For example, in a CICS® application, include the text string in the data that is sent in the first SEND command of a chain. NetSpool determines the start of a print request using the bracket and chaining of the data, and using the end-of-file rules specified for the LU in the printer definition.
• In 3270 data streams, put the text string after the Command Code and the Write Control Character, but before any End Message Control Character (X'19').
• Consider using a delimiter, such as a carriage return, between the text string and any print data to be sure that the data prints correctly on the page. In 3270 data streams, you can use a Set Buffer Address Control as the delimiter.
• In data streams that contain double-byte character set (DBCS) data, code the text string as single-byte data.
• IBM® suggests that you do not use embedded job attributes if you specify the Timer end-of-file rule. Results can be unpredictable.