Use this tab to specify the incoming file type for Print Utility and TCP/IP.
For Print Utility, you can access this tab when you add files to the spool. For TCP/IP, you can access this tab when you modify LPD and Socket properties.
Click an option you want to learn more about.
Indicates the current format of the file.
If BHCS cannot interpret a specific type, then choose to receive
the file as Binary (raw).
|
Option |
Description |
|
Standard ASCII |
ASCII files with ASCII carriage control (carriage return, line feed, and form feed). Standard ASCII includes support for enhanced channel skip processing. This is the default. For LPD users, this is usually set to LPR command l, p, or f on the File Properties dialog box. The end of the input file may be determined by 0x1A characters. If 0x1A is the last byte of data in the file, 0x1A is removed. If 0x1A is in the middle of the file, and it is immediately followed by at least five null bytes, then 0x1A and everything after it is removed. If 0x1A is in the middle of the file, and at least one of the next five bytes is NOT null, then all of the data is passed through. There can be multiple 0x1A characters in a file. |
|
ASCII with ASA carriage control |
ASCII files with ASA carriage control. For LPD users, this is usually set to LPR command r - FORTRAN. |
|
ASCII with 1F processing |
Files generated by some applications that use special formats for sending commands or resources to printers. |
|
SYSIN data (JCL) |
Files that contain SYSIN data. These files are intended for an RJE or NJE host. When SYSIN jobs are added to the Spool Window, they appear shaded in a light blue background. |
|
Barr DOS (ASCII or S/370) |
Files from the Barr DOS product's spool directory. LPD users can select this option if they are receiving data on an LPR or IP socket connection from Xerox's XPAF mainframe application. Refer to the File and record formats topic for more information. |
|
VBM and Xerox formats |
Files in mainframe VBM Acronym for Variable Block with Machine carriage control. This is a standard mainframe file format. format, also known as RDW Record Descriptor Words or BDW Block Descriptor Words format, or files that contain data in Xerox file formats. Refer to the Xerox file formats topic for more information. |
|
Binary (raw) |
Files that you want to send into BHCS without the Barr software interpreting or modifying the data. This option is typically used to send fully formatted print streams such as PCL Acronym for Printer Control Language. Hewlett-Packard uses this language in its LaserJet, DeskJet, and RuggedWriter printer lines. Because of the Laser Jet's dominance in the laser printer market, Printer Control Language has become a de facto standard. or PostScript. When printing the file, you can select Pass data to printer without conversion on the Advanced Printer Options dialog box to print the file without any conversions. See the Passing data to the printer without conversion topic for more information. |
|
Binary with Barr routing header |
Files in binary format that contain a header. Usually these are files that have been processed by Elixir. In Print Utility, if you specify values for header fields on the Spooling Properties dialog box, these values will override the settings imported from the Barr routing header. |
|
Binary with XPIF routing header |
Files in binary format that contain an XPIF Xerox Print Instruction Format XML header. You can use this option to retrieve information from the XML headers at the beginning of the job. The information retrieved may contain data that could be used by print operators or information used for tracking and accounting purposes. |
|
AFP |
Files in standard (raw) AFP format. (Fully composed AFP format is recommended.) |
|
Barr archive |
Files that were previously received by BHCS and then archived. You can use this option to route jobs from one Barr Host Communications Suite to another. |
|
Mainframe IP record format |
Files in IBM's S/370 record format. Programs such as IBM's IP Printway and Levi Ray and Shoup's VPS/LCDS generate this format. Select this option when receiving data on an LPR or IP socket connection from one of these mainframe applications. This format is accepted by Xerox's EPS Acronym for Enterprise Printing System.. This format is recommended over ASCII because it preserves the mainframe carriage control and avoids data translation.
|
|
Fixed-length record |
Records that are a fixed length because each record is a fixed number of characters or bytes. |
|
Delimited record |
Records that are variable length and terminated with a delimiter. |
|
Custom |
Files in a custom format that require data conversion. If you think a conversion is necessary, please contact Barr Systems Technical Support to ensure the data is converted properly.
|
Format button
If the Custom file type is selected, use this option to select the custom DCO (Data Conversion Object) chain on the Chain Selection dialog box. This is not necessary for most users. If you think this conversion is necessary, please contact Barr Systems Technical Support to ensure the data is converted properly.
This option is only available if a custom
DCO (Data Conversion Object) chain has been created.
Wrap in NJE format
Available for files in Binary (raw) format. When selected, headers are added to the files and the files are sent to BHCS without modifying their text.
Mark data as text
If the file type VBM and Xerox formats is selected, use this option if source data contains line or text data. This option should not be selected for Xerox Metacode or Xerox resources.
Spur carriage control
Select to emulate the behavior of a spur box. Incoming data will be converted to spur carriage control format. This option can be used by those upgrading from BARR/RJE DOS.
Discard header data
If the Barr DOS (ASCII or S/370) file type is selected, use this option to discard the header data.
Decompress
Select if the data is compressed. This is only available for files in the Barr archive format.
Decrypt
Select if the data is encrypted. This is only available for files in the Barr archive format.
Key name – The key name was configured in the Encryption Key Manager for both the sending and receiving Barr Host Communications Suite computer. The key name is used to encrypt and decrypt a packet of information as it is transferred over the network to another computer.
Record length
If the Fixed-length record file type is selected, specify the length of the fixed records. The valid range is from 1 to 32767. The default value is 133.
Delimiter
If the Delimited record file type is selected, enter one or two bytes of hexadecimal data. The default value is 0x0d,0x0a.
Carriage control
If the Delimited record or Fixed-length record file type is selected, select ASA, Machine, or None as the carriage control type. The default type is ASA.
ASA - Records contain an ASA carriage control character.
Machine - Records contain a 3211 machine carriage control character.
None - Records do not contain a carriage control character.
Specifies the beginning and ending JCL files for raw data files. These options provide the same functionality as the LAN device in the BARR/RJE DOS software. You can provide a beginning and ending JCL file, which is wrapped around each data file that is read from the input directory.
If you are sending a file that is a JCL file, leave these fields blank.
Begin
The beginning JCL file that is sent immediately before each data file. This feature is often used to send JCL with files that will be submitted to the host as jobs. The begin file must be in a separate directory from the data file. Click the folder button to select the file, or enter the path and file name in the text box.
End
The ending JCL file that is sent immediately after each data file. For example, you can send JCL at the end of a job. The end file must be in a separate directory from the data file. Click the folder button to select the file, or enter the path and file name in the text box.
Mode
Determines the format of the data. The following are the available send modes:
A - ASCII, which is the default if you do not specify a send mode. ASCII mode indicates that the file consists of data lines ending in a carriage return character. As BHCS sends the JCL and data files, it converts them from ASCII to EBCDIC. Before you transfer data that includes packed decimal fields, use a separate program to unpack the data. Packed decimal data gets corrupted during translation from ASCII to EBCDIC with any file transfer program.
Annn - ASCII with a maximum reader length. For nnn, substitute a maximum reader length from 1 to 254. As BHCS sends the JCL and data files, it converts them from ASCII to EBCDIC.
B - Binary or unknown format. BHCS sends data as 80-byte records without carriage control. The data is not translated.
Tn - Transfer files. Use this send mode to transfer files PC to PC or remote to remote. Or use it to transfer files between the PC and the host with the BARR/TRAN mainframe program. See the Barr File Transfer (BFT) send mode Help topic for more information.
V - Variable ASCII lines. Each ASCII line is sent as one or more 80-character lines. You can use this send mode to send files that contain variable-length lines or lines with more than or less than 80 characters. Vertical bars are added to signal the end of the original record. You must use a program at the host to rebuild the lines into their original records.
1-9 - N ASCII lines. Use this send mode to send fixed-length lines that contain an even multiple of 80 characters. For records that are not an even multiple of 80 characters or contain more than 720 characters, Variable ASCII lines (V) is a better choice. Each ASCII line is sent as n lines of 80 characters, where n is a number from 1 to 9. You must use a program at the host to rebuild the specified number of lines into their original records.
Length
The record length that can be specified in the following send modes: A, TF, TDF, and TBF. The default value is 80.