Not sure what it does nor where the source is, but ES/PI has it. It seems to take JCL and without it, the first thing is does is renames a file \;_^RSV > to \;_^RSV SAVE. Not finding that file, it exits. But if there does exist such a file, it invokes EMACS on that file (after having renamed it). So it appears to edit the default file (of JCL-specified file) after having made a backup. It doesn't edit the file as XXX >, but rather XXX \ where \ is the latest version (>). Thus, it allows you to edit the latest version of file without, when you save, creating a new version, but still having a backup of the one you edit.
Or something like that. I just did a little debugging to see what it would do.
Actually, when I exited emacs, there was no _^RSV SAVE file, so perhaps this is deleted after emacs is exited.
My guess is this is kind of a "create me a file" program, which launches emacs on the specified file. Not sure what this buys you over just invoking emacs with jcl, but maybe it is the version handling.
Not sure what it does nor where the source is, but ES/PI has it. It seems to take JCL and without it, the first thing is does is renames a file \;_^RSV > to \;_^RSV SAVE. Not finding that file, it exits. But if there does exist such a file, it invokes EMACS on that file (after having renamed it). So it appears to edit the default file (of JCL-specified file) after having made a backup. It doesn't edit the file as XXX >, but rather XXX \ where \ is the latest version (>). Thus, it allows you to edit the latest version of file without, when you save, creating a new version, but still having a backup of the one you edit.
Or something like that. I just did a little debugging to see what it would do.
Actually, when I exited emacs, there was no _^RSV SAVE file, so perhaps this is deleted after emacs is exited.
My guess is this is kind of a "create me a file" program, which launches emacs on the specified file. Not sure what this buys you over just invoking emacs with jcl, but maybe it is the version handling.