Useful SCL by Mike Fleming
Over the years, I've written a fair few SCL procedures. Here are a few which I've found of use, with the most useful first:
|Allows various actions on a list of files in a user, group or library. You can page up and down through the list, produce a list of marked file names, mark (and unmark) files for deletion, and specify your own SCL to be executed on a file.||Source|
|A group and library manager. It allows various actions on groups and libraries within a user, including executing MFM and MTREE on them.||Source|
|This supersedes MCRRH [see below], and allows you to create, browse,
and edit files using a file definition. Fields may be display, binary
or packed, and may be validated on creation and editing.
The difference between this and MCRRH is that MCRRH generates an SCL procedure for each record type defined, while MRH uses the record definitions directly to access the files.
|Allows SCL to be used to edit one file to another, to give more complex editing than is possible through the standard VME editors.||Source|
|An edit for COBOL programs, so that mnemonics can be used in the DATA DIVISION for format effectors. The edit then replaces these with FILLERs with the appropriate length and value.||Source|
And of occasional use:
|Finds records which are common to two (sorted) files, which may have keys in different places||Source|
|Combines files by using logical operators on key values to determine which records should be written to the output file.||Source|
|Converts a compile listing to a COBOL program source.||Source|
|Removes duplicate records from a file, where duplicates are adjacent. The column range to be used for determining duplication can be specified.||Source|
|Propagates the contents of a record through successive records. Any space characters in a record are replaced by the most recent propagated character in that column.||Source|
|[Now superseded by MRH, see above]
Generates SCL to allow you to create, browse, and edit files. The generated SCL displays each record as a set of fields which you define. Fields may be display, binary or packed, and may be validated on creation and editing.
I have left this in, despite the fact that it is now superseded, as the code and the techniques used to generate SCL from within SCL may be of interest.