CICS/Forward Recovery System for CICS files on the mainframe by MacKinney Systems, Inc.

5.88 - What's this?

When a VSAM file is corrupted or lost you need to recover it quickly and correctly. CICS' journal facility provides the data, but it is each installation's responsibility to have computer disaster recovery plans with recovery programs for each file which CICS updates. Most IBM mainframe installations have not done this. MacKinney Systems Forward Recovery System for CICS (CICS/FRS) fills this void.

Features

  • » eliminates the programming required for data recovery
  • » selects CICS journal records based on a variety of parameters (date, time, terminal, transaction, file)
  • » selectively updates your backup files to get your users on-line quickly
  • » recovers multiple files in a single run
  • » has a scan function which tells you the number of journal records which apply to each file eliminating the guesswork about the contents of various journal tapes
  • » journal print program produces an audit log of all or selected journal records
  • » works with all recent and current releases of VSE, z/OS, and CICS, including Transaction Server
French, German, Italian, Spanish, Japanese, Swedish, Danish, Dutch, English

Supported Technologies

VM/VSE, MVS(OS/390)
- Not Applicable -
COBOL
Software
Click on a technology to view similar products within this category.

Pricing

Other
$4,000 VSE to $5,000 z/OS
sales@mackinney.com
417 882 8012


pricing is purchase of site license. Maintenance after the first year of purchase is: $600-VSE, $750-z/OS

Additional software product description, benefits, features, and uses.

Additional Product Information


CICS/FRS runs as a batch job OUTSIDE of your CICS system. NO MODIFICATIONS are required to CICS or CICS programs.

CICS/FRS uses a procedure requiring a minimum of JCL to ease the effort involved in recovering a production KSDS, RRDS, or ESDS VSAM dataset.

Input to the procedure is a set of simple control records (commands) that identify the file involved, the transaction(s) involved, the beginning and ending time(s) and date(s), and the terminal(s) creating the changes to the file.

To identify which data is on a particular CICS Journal file, a CHECK (or scan) may be made where no data is moved, but a report is generated detailing the contents of the journal file.

This capability becomes very important in the case of corruption and can be invaluable when multiple files are involved.

Search within this category