Release 2

Release 2.3	The previous behavior of printing a separate “hit” line on the report for every occurrence of the scan string within the same line has been changed. Beginning with this release, only one report line per input record should be printed. See item 2 below to revert GSRMAIN to the previous behavior.
	Two new “Print Matching String” option values (options record, column 11) have been added: ‘F’ Print 'F'irst matching line only. This value will cause scanning to stop with the first record that contains any of the scan strings. When used in combination with the 'C' "Print Option" setting (in column 7), 'F' in column 11 will cause only one line per member to be printed, and only for those members that contain the scan string. 'E' Print 'E'very match found. If 'E' is specified, then the output report will contain a line for each occurrence of the scan string, even if there are multiple occurrences on the same input record.

Release 2.2	A new version of GSRMAIN is included, named GSRMAINL. GSRMAINL can scan members up to 20,000 lines in size before writing the member to the CHANGED file. This prevents updating members that are not really changed unless they are greater than 20,000 lines long.
	A new “userid” option for ICCF members allows you to specify the userid to be used when an ICCF member is changed. (This prevents the DTSUTIL ADD from failing after the DELETE when the previous userid is no longer valid.)
	The limit on the number of programs that can be INCLUDEd or EXCLUDEd is increased from 100 to 1000.
	The "line" numbers of members are now printed under the member name, making it easier to identify the line being displayed.
	A new option to print a specified number of lines of the member after each matched line allows you to see the lines affected in context.
	GSRMAIN and GSRMAINL are compiled using COBOL/VSE. (If you do not have COBOL/VSE, continue to run release 2.1.)
	The RETURN-CODE variable ($RC or $MRC in the JCL) is now set to 0 if there are members to update, 1 if there are not, or a higher number if there was an error. This allows you to bypass the update step if there are no updates to perform.

Release 2.1	Changed the password update method. Eliminated requirement to compile GSRMAIN.

Release 2.0	Initial MVS release with PDS support. Changed the VSE release number to match MVS version.

Release 1.5	Added three option card fields (and enhanced a fourth) to identify input/output types and lengths. This will simplify installation procedures.
	Added password protection.

Release 1.4	If there is a non-blank in position 72 (continuation character) and a replacement causes data to be shifted to the right, shifting stops at position 71.
	If a replacement causes data to be shifted to the left and position 72 is non-blank (continuation character) and position 71 is not a blank and not a ',' (comma), a truncation error message is printed.

Release 1.3	When an unchanged member is written to the CHANGED file, a message is written to the print file (see item 4 under release 1.1 changes below).
	When COMPRESSED members are written to the CHANGED file, a DTSBATCH job is created to issue a SQUEEZE command for each of those members to recompress them after they are reloaded with DTSUTIL.
	A DELETE option was added to allow deleting any line that matches a given character string (NEW=$DELETE-LINE$).

Release 1.2	A new option to scan PHASE entries in VSE libraries has been added. It can be used to find programs that use certain modules (CICS programs using CURRENT-DATE, TIME OF DAY, etc.).
	Show line number where match found.

Release 1.1	The output file containing scanned/changed members is not opened unless the input scan table contains at least one "NEW=" entry indicating a REPLACE will be attempted. If you are only scanning, you do not need JCL for the 'CHANGED' file and you should not run the RELOAD or DTSUTIL job to reload the CHANGED file.
	The 'blank' wildcard character (see OPTION CARD, column 10) can now be used as a place holder in a replacement character string to allow it to end with one or more spaces.
	A new print option (column 11 of the OPTION CARD) will reduce the volume of print by not printing the line which shows the matching character string.
	Only changed members and members longer that 5000 lines are written to the output file. A table (400,000 bytes) was added to GSRMAIN to store members as they are processed until we do a replace or the table gets full. GSRMAIN needs a partition large enough to run a 490K program.