VAX DIBOL-compatible functionality
WTSupported in traditional Synergy on Windows
USupported on UNIX
VSupported on OpenVMS
System option #35 provides VAX DIBOL-compatible functionality for certain Synergy DBL features. If you set system option #35, the following changes to Synergy DBL behavior occur:
- WAIT I/O statement qualifier: If you specify a value of 0 for the WAIT I/O statement qualifier, it indicates “wait forever” instead of “no wait.”
- Quit mapping: The quit character is mapped to the interrupt character.
- Appending to a nonexistent file: If you open a file that does not exist in append mode, a “File not found” error is generated.
- CRT mode: Synergy DBL assumes that terminal I/O is I/O to or from a CRT.
- Invalid key checking: Invalid key checking is enabled (as if you had set system option #45). An error is generated if the key is not correctly specified.
- BEGFL subroutine: The BEGFL subroutine resets the key of reference to zero for an ISAM file. (Windows, UNIX)
- PARSE subroutine: The PARSE subroutine stops at the semicolon (;) and doesn’t include it in the filename or file extension. (Windows, UNIX)
- TT: on the OPEN statement: If you open TT: while running from a command procedure, you only get input from the terminal, not the command procedure. Synergy DBL no longer opens both SYS$INPUT: and SYS$OUTPUT:. (OpenVMS)
- O:P mode on the OPEN statement: If you open print files in O:P mode, Synergy DBL uses sequential files with no carriage control, as opposed to sequential VFC. This implementation is more efficient if you’re outputting a large print file to a laser printer with escape sequences and graphics data, rather than standard carriage-return/line-feed records. (Each DISPLAY or WRITES statement for a VFC file incurs two bytes of overhead.) (OpenVMS)
- O:S mode on the OPEN statement: If you open a file in O:S mode with RECSIZ specified, Synergy DBL creates a fixed-length file. (OpenVMS)
- UNLOCK statement: The UNLOCK statement removes all locks on the channel.
- Echoing control characters: Synergy DBL echoes just the control symbol (^) by default, not control characters (for example, ^A and ^G). (OpenVMS)
- Line feeds on the FORMS statement: The FORMS statement on a channel opened to a file with carriage return carriage control outputs one extra line feed, advancing the paper one space more than the number specified in the FORMS statement. For example,
open(chn, o, "file.ddf")
results in <CR><LF><LF> (three extra lines) if option #35 is set or <CR><LF> (two extra lines, as specified) if option #35 is not set. (OpenVMS)
- RENAM subroutine: The RENAM subroutine no longer works the same as the DCL command RENAME. Instead, it operates as in the following example:
If you have three files named FILE.A;1, FILE.A;2, and FILE.B;1, and you use the RENAM subroutine as follows:
xcall renam("FILE.A", "FILE.B")
Synergy DBL deletes FILE.B;1 and renames FILE.A;* to FILE.B;*. If flag 3 of the FLAGS subroutine is set, the existence of FILE.B;1 causes a “Cannot supersede existing file” error ($ERR_REPLAC). (Normally, FILE.A;2 is renamed to FILE.B;2 by default.) (OpenVMS)
RUNJB detached process: The process created by the RUNJB subroutine is detached. However, if the RUNJB subprocess argument is present, or if the io_flag argument has a nonzero value, option #35 is ignored. (OpenVMS)
- Message returned from ERTXT subroutine: The returned message includes the facility, severity, and mnemonic, and the position argument is loaded with the starting position of the message text. If option #35 is not set, the text does not include the facility, severity, or mnemonic, and position has a value of 1. (OpenVMS)
When you set option #35, options #5, #16, #38, #39, and #45 are also set. See system option #45 for an important note.
If system option #35 is not set, Synergy DBL handles the above functions as they are documented in their respective sections.