SET BFSLINE
Purpose
Use the BFSLINE option to change the value specified (or defaulted) by the XEDIT BFSLINE option. This affects the file when it is written back out to the byte file system (BFS). It does not change the file (by reinterpreting end-of-line characters) as it is displayed in the current XEDIT session. It also does not affect a file being written to SFS or a minidisk.
Operands
- lrecl
- indicates the file should be treated as a fixed record format file (RECFM=F) with no interpretation of records based on end-of-line characters. No end-of-line characters are added to the file when it is written back out to the BFS if BFSLINE lrecl is still in effect. The lrecl is limited to eight characters.
- NL
- indicates the new line character (X'15') should be used to delineate lines when writing a BFS file.
- CRLF
- indicates that carriage return/line feed (X'0D25') should be used to delineate lines when writing a BFS file.
- CRNL
- indicates carriage return and new line characters (X'0D15') should be used to delineate lines when reading or writing a BFS file.
- /string/
- allows the user to specify 1 - 2 characters that are used to delineate lines when reading or writing a BFS file. These characters are translated to uppercase before they are utilized. The slash character (/) may not be one of these characters (in other words, you cannot enter ///).
- /hexstring/
- specifies a hexadecimal string of 2 or 4 characters that defines the value to be used for BFSLINE. The hexstring must be in the format X'nnnn' or X'nn'. You must not specify any spaces in the string, and there must be 2 or 4 hexadecimal characters in the string.
Initial Setting
The initial setting is BFSLINE NL (or as specified in the XEDIT command or the
LOAD subcommand).
Usage Notes
- Changing the BFSLINE value affects how the file is stored in the BFS. For example:
- If you begin the XEDIT session with a value of BFSLINE NL, all new line characters (X'15') are stripped from the file while in the XEDIT session. Changing to BFSLINE 80 and entering FILE would save your file; no end-of-line characters would be reinserted in the file. If RECFM is still variable (V), trailing blanks are stripped from each line of the file. If RECFM has been changed to F, no trailing blanks are removed and each line is padded with blanks up to the length of the LRECL value.
- If you begin the XEDIT session with a value of BFSLINE 40, no end-of-line characters are
stripped from the file. It is presented as it is stored in the BFS, broken into 40 character records. If you change to
BFSLINE CRLF, X'0D25' will be inserted after each 40 characters when the file is written to
the BFS. If RECFM is V, trailing blanks are
stripped from each line.
When specifying a BFSLINE value for use on files containing DBCS characters, ensure you use a value that will not conflict with DBCS characters. The hexadecimal code for a DBCS character must be X'00', X'40', or in the range of X'41' to X'FE'.
As you can see, changing the RECFM setting also affects how the file is stored in the BFS.
- BFSLINE has no effect when a PUT, PUTD, GET, FILE, or SAVE subcommand is used to read or write an SFS or minidisk file when NAMETYPE CMS is in effect.
Messages and Return Codes
- 520E
- Invalid operand: operand [RC=5]
- 545E
- Missing operand(s) [RC=5]
- 554E
- Not enough virtual storage available [RC=104]
where return codes are:
- 0
- Normal
- 4
- Insufficient storage
- 5
- Invalid operand
- 6
- Subcommand rejected in the profile due to LOAD error, or QUIT subcommand has been entered in a macro called from the last file in the ring
