Release 1

Release 1.4	Added support for z/OS CICS Transaction Server 3.1 and beyond, by recompiling all CICS programs with the Enterprise COBOL compiler for z/OS.
	Withdrew support for MVS CICS/ESA releases 4.1 and below.

Release 1.3	Made Year 2000 Compliant.

Release 1.2	Maintenance and a slight enhancement release.
	Includes new viewer directory which uses more stable and faster type DN/DL/DD records instead of temp storage. Refresh (PF2) on the viewer screen is almost instantaneous now vs. potentially long waits on and 1.1. PF9 causes a refresh similar to the old slow refresh where the whole queue is scanned. PF9 is not documented on the screen since it is rarely necessary.
	Includes patches ADH1101 through ADH1119.
	Includes enhanced duplicate detail suppression logic.
	Includes support for new COUNT=nnnnnnn,SKIP=nnnnnnn parameter which allows users to limit the number of records processed by the report job. These parms work just like the IDCAMS COUNT() and SKIP() parms. These parms must be manually entered at this time. They also only work on single file report jobs at this time.
	Resolved 0C4's in MVS when using freeform conditions.
	Resolved several small freeform related problems.

Release 1.1	A significant amount of maintenance was applied.
	MVS QSAM disk and tape support has been added, including support for RECFM=VBS files such as SMF datasets. File types QSAM and MVST support disk and tape, respectively. Sample SMF record layouts are provided for record types 04, 05, and 60. These records provide information regarding step termination, job termination, and VVDS update, respectively. The member names for the supplied records are SMF## where ## is the record type. MVS tape support is limited to STANDARD LABEL tapes.
	Datasets, support for sequential/tape.
	VSE sequential disk and tape support has been added. File types SEQL and VSET support disk and tape, respectively. VSE tape support is limited to NON-LABELED tapes.
	Workaround for OCCURS DEPENDING ON support OCCURS DEPENDING ON support is better documented. Full occurs depending on support is not provided, but a workaround method is explained.
	PF2/14 on the field selection screen now causes ADHOC to refresh field characteristics from the ADHPIC file so that your report reflects format and location changes made via ADHJ100 or option 9 on the ADHOC administration menu.
	Several new field formats were added: YYDDD Date in the format YYDDD where YY is year and DDD is day of year HHMMSS Time stored as HHMMSS, will be displayed as HH:MM:SS AM or HH:MM:SS PM HHMMSS24 Time stored as HHMMSS, will be displayed as HH:MM:SS HHMM Time stored as HHMMSS, will be displayed as HH:MM AM or HH:MM PM HHMM24 Time stored as HHMMSS, will be displayed as HH:MM Gregorian dates SERDATE Date in the format nnnnnnn where nnnnnnn is a numerical representation of the number of days since Dec 31, 1899. Jan 1 1900 = 1, Oct 29 1995 = 35000, etc. SERDATE dates are displayed in Gregorian form. SSN Social Security Number. Causes a field of this type to be printed as ###-##-####. SMFTYPE SMF record type. A 1 byte binary field representing a value from 0 to 255. This field type is necessary to allow you to perform compares on SMF record type fields, such as IF SMF-REC-TYPE = 60... This field type can also be used to work with any 1 byte binary field that contains a numeric value (logically). SMFTIME Time stored as a binary full word containing the number of 100ths of seconds elapsed since midnight. The standard SMF record time format, ADHOC displays these fields as HH:MM:SS.hh. SWITCH A one byte binary field which normally contains x'00' or X'FF', this field will display as ON (X'FF') or OFF (X'00').
	Reports composed of MacKinney Systems' Data Processing Manager (DPM) records MUST contain a condition. This was implemented to force use of the DP?-?-RECORD-TYPE fields that uniquely identify each DPM record type.