1. For Version 2.2, RSCS converts the ASA carriage control to machine store-and-forwarded. The NDHGRCFM field in the data set header is changed accordingly. Records sent with machine carriage control character are store-and-forwarded without change.
2. Records (with or without carriage control of any type) sent as spanned records are store-and-forwarded without change.
3. For files sent to VM users--those not store-and-forwarded-- RSCS truncates any characters in print SYSOUT records that exceed the number allowed for the printer whose type is used to store the file on CP spool. (The method in which this printer type is determined is described in detail in section RSCS/CP Spool Interface Considerations.)

   At the destination node, records are truncated as described above.

1. If NDHGRCFM indicates that a punch file contains ASA or machine carriage control, RSCS replaces the carriage control in each record with a machine punch operation code (opcode). For store-and-forwarded files, carriage control is forwarded properly.
2. If NDHGRCFM indicates no carriage control, the file is forwarded without change (as 80-byte records with no carriage control).

RSCS truncates--only at the destination node--any records that conflict.

Table 1 is a table of virtual device types that are defined for different incoming NJE file types:

Once RSCS has determined the device type to use for a file at header processing time, the type will not be changed even if the data records themselves have different characteristics. Once the file is stored in CP spool, it will not be changed if it is forwarded to another non-VM NJE system. Hence, if RSCS receives a file with individual data records of 150 but the NDHGLREC field says 132, the file will be stored as a 1403 file and all characters after the 132nd character in each record will be truncated for printing on the RSCS node if an end node.

• Regular print files which are meant to be printed on a 3800 printer (indicated by the fact that their data set header contains a 3800 section)
• Virtual 3800 files that are currently only understood by a VM system and thus are only originated by RSCS.

Virtual 3800 files are also sent with a 3800 section in their data set headers. For purposes of this discussion, virtual 3800 files may be distinguished from regular 3800 files by two characteristics: First they contain actual 3800 CCW opcodes as well as machine carriage control characters and, secondly, they are the only type of file with a 3800 subsection that are originated by RSCS.

When virtual 3800 files are created by an RSCS node, they are sent with both an RSCS subsection and a 3800 subsection in the data set header. RSCS sets the virtual device type in the RSCS subsection to be virtual 3800 so another RSCS system can process the file correctly. Thus, RSCS can always recognize a virtual 3800 file it has created.

RSCS creates a virtual 3800 file out of any 3800 print file that has the OPTCD=J flag on in the 3800 section of the data set header. This occurs for store-and-forward files and for files for which RSCS is acting as an end node. RSCS then removes the TRC byte from each record at the destination node and inserts select CCWs that cause the proper character arrangement table to be selected. If such a file is printed on a real 3800 printer on the receiving node or another VM node, the printout should be as the originator intended. If the same file is sent back to another non-VM NJE system, the TRC bytes are re-inserted and the select CCWs removed.

RSCS changes 3800 files that have ASA carriage control to machine carriage control in the same way as other types of print files. For Version 3, this restriction is removed. (see Store-and-Forward Transparency).

Spanned 3800 records are not unspanned when they pass through an RSCS node. Records are unspanned only when the files are printed on the node RSCS is running on.