Reliant for VSE CSI-RECOVjournal records for both your VSAM and DL/I datasets in a single CSI-RECOV Journal Backup dataset. In summary, CSI-RECOV can save your company time and money

(COPYRIGHT © 2003, CSI INTERNATIONAL, INC.)

CSI-RECOV is a proprietary product of CSI International, Inc. It cannot be reproduced, changed,copied, or stored in any form (including, but not limited to, copies on magnetic media) withoutthe express prior written.

R e l i a n t f o r V S E

C S I - R E C O V

CICS VSAM RECOVERY

INSTALLATIONAND

OPERATIONS GUIDE

Release 4.0

Original Printing .......................04/01/2003Last Revised ...............................04/01/2003

TABLE OF CONTENTS

GETTING STARTED ............................................................................................................................1Preface................................................................................................................................................3

How Should I Use This Manual? ............................................................................................3Disclaimer ..................................................................................................................................3

Introduction ......................................................................................................................................5What is Recovery?.....................................................................................................................7What Part is provided by CICS? .............................................................................................7What Part is provided by CSI-JOURNAL?............................................................................7What Part is provided by CSI-RECOV?.................................................................................7What Part is provided by CSI-ARMAN?...............................................................................7What Part is provided by DL/I? .............................................................................................8Will the Process work when I need it? ...................................................................................8Features of CSI-RECOV ...........................................................................................................9Terminology...............................................................................................................................11

Migration Requirements .................................................................................................................13Installation.........................................................................................................................................16

Customizing CSI-RECOV ........................................................................................................19CSIRECDJ (Default CICS Journal I/O module)....................................................................20CSIRECDB (Default Journal Backup I/O module) ..............................................................21CSIRECDD (Default DL/I Log I/O module)........................................................................22Generating a Custom I/O Module .........................................................................................23

PREPARING CICS FOR RECOVERY................................................................................................27Overview of CICS Journaling.........................................................................................................29

Journal Functions of CICS........................................................................................................30Journal File Alternatives ..........................................................................................................30

One Journal Dataset vs Two.............................................................................................31Disk vs Tape Journals........................................................................................................32One Journal vs Many.........................................................................................................33

CICS Journal Recommendations....................................................................................................34Installing Journaling in your System.............................................................................................36

Defining your Journal Control Table (JCT) ...........................................................................36Initializing your Journal File for CICS ...................................................................................40Activating Automatic Journaling (CICS FCT) ......................................................................42Add Journal Support to the CICS PCT, PPT and SIT Tables ..............................................43Add Journal File JCL to your CICS Startup Jobstream........................................................44Writing an EOF Mark on Tape Journals ................................................................................46

USING CSI-RECOV ..............................................................................................................................47Considerations..................................................................................................................................49

Accumulating Journal Data .....................................................................................................49A Typical Failure/Recovery Cycle .........................................................................................50Recovery with Non-journaled Batch Updates ......................................................................51VSAM Share Option 4 ..............................................................................................................52Coordination of Data File Backups and Journal Files..........................................................52VSAM Recovery Scenario (Manual).......................................................................................53VSAM Recovery Scenario (Using CSI-ARMAN) .................................................................54DL/I Recovery Scenario...........................................................................................................55

TABLE OF CONTENTS

Journal Backup JCL ......................................................................................................................... 57Recovery JCL.................................................................................................................................... 59Commands and Operands ............................................................................................................. 61

Syntax......................................................................................................................................... 61Commands ................................................................................................................................ 63

INPUT Command ............................................................................................................. 64OUTPUT Command ......................................................................................................... 72SELECT Command ........................................................................................................... 81SORTOPTION Command................................................................................................ 91ATTRIBUTE Command ................................................................................................... 100AUTO Command .............................................................................................................. 104

Reports generated by CSIRECOV ................................................................................................. 105Parameter Edit Report ............................................................................................................. 107Output Print Report ................................................................................................................. 108Summary Reports..................................................................................................................... 109VSAM Output Error Report.................................................................................................... 117

VERIFICATION SYSTEM................................................................................................................... 121System Components........................................................................................................................ 123Compiling the Verification Programs........................................................................................... 125Modifying CICS Tables for Verification Testing......................................................................... 128Modifying CICS Startup JCL ......................................................................................................... 131Modifying Verification JCL............................................................................................................ 132Run Jobstream CSIRECV2.............................................................................................................. 133Run On-line Verification Program................................................................................................ 134Run Jobstream CSIRECV3.............................................................................................................. 135Problem Determination for Verification System......................................................................... 136

MESSAGES ............................................................................................................................................ 139

APPENDIX A.......................................................................................................................................... 165How To Code Commands (Syntax) .............................................................................................. 167

APPENDIX B .......................................................................................................................................... 173Journal Backup Record Formats.................................................................................................... 175

CSI-RECOV/VSE INSTALLATION AND OPERATIONS GUIDE

Page 1

GETTING STARTED


Preface Page 3

Preface

This manual is written to help you install, verify, and implement CSI-RECOV,the CICS VSAM Recovery System from CSI International, Inc.

How Should I Use This Manual?

If you already have CICS Journaling installed you can skip the section"Preparing CICS for Recovery". However, we feel that it would be to youradvantage to quickly review this section.

If you are now using a previous release of CSI-RECOV, please refer to the section"Migration Requirements". To implement the enhancements provided in thisrelease, you may need to change some of your existing JCL.

Once CICS journaling has been installed you may install and customize CSI-RECOV. This is covered in the section "Installation".

Once CICS journaling and CSI-RECOV have been installed, we strongly suggestthat you verify the entire process, as explained in the section "Verification andTesting".

Then prepare a recovery Jobstream as outlined in the section "Using CSI-RECOV" so that you will be prepared for recovery of one or more files whennecessary.

Disclaimer

The techniques and procedures outlined in this manual have been thoroughlytested on our development site. However, you should check all procedures indepth and modify them as needed for your own installation.


Introduction Page 5

Introduction

CSI-RECOV is a system designed to recover VSAM files updated by CICS/VS orbatch applications, if VSAM changes are journaled. Journal files created byCICS/VS (SMF or standard format) or CSI-JOURNAL, the VSAM BatchJournaling system from CSI International, Inc. can be used as input to CSI-RECOV. This system can be used to recreate a file's condition prior to a diskfailure, head crash or file deletion, using a file backup and the appropriatejournals.

CSI-RECOV can also be used to manage DL/I journal records. DL/I journalrecords from your CICS System Journal and batch DL/I journal logs from batchDL/I programs can be combined with VSAM journal records and maintained ona single journal backup file until such time as a DL/I recovery or "change-accum" process is required. CSI-RECOV can then generate a single DL/I logdataset that can be input to your standard DL/I utilities.

CSI-RECOV

CICSJOURNALS

JOURNALBACKUPS JOURNAL

REPORTS

VSAMDATASETS

JOURNALBACKUPS

DL/ILOGS

DL/ILOGS

BATCHJOURNALS

Overview of CSI-RECOV


Page 6 Introduction

These are the benefits that you get from using CSI-RECOV:

• You do not have to code custom recovery routines. CSI-RECOV will recreateany VSAM file, provided that a current backup and journal are available.

• Users will not have to re-enter data after a failure.

• One or more VSAM files can be recovered at the same time.

• Complete reporting ensures accuracy and verification.

• CSI-RECOV can be used in conjunction with CSI-ARMAN, the AutomatedRecovery Manager from CSI International, Inc. to provide integrated controlof your VSAM Backup and Recovery processing.

• The application programmers need not include specialized "change-log"logic in their CICS/VS programs if the IBM-supplied automatic journalingfeature of CICS is used. This feature, along with CSI-RECOV, is all that isneeded to provide VSAM file recovery.

• If you have both VSAM and DL/I datasets, you can backup and manage alljournal records for both your VSAM and DL/I datasets in a single CSI-RECOV Journal Backup dataset.

In summary, CSI-RECOV can save your company time and money when aVSAM dataset is lost or damaged. Recovery can be a manageable process, whenit is planned for, and CSI-RECOV makes the process easy.


Introduction Page 7

What is Recovery?

Recovery is a process that restores a damaged file to the state it was in prior tothe point of damage.

Damage may be caused by hardware or software failure, or by human error, andthe extent of the file damage can vary from a single record in one file to manyfiles in several systems. Accordingly, the recovery process could be differenteach time a failure occurs.

What Part is provided by CICS?

CICS provides the facility to record file change data in separate datasets calledjournals. The section "Preparing CICS for Recovery" will give you detailedinstructions on how to prepare your CICS system for this facility.

A companion product, CSI-JMASTER, from CSI International, Inc. can be used toprovide automatic backup, and overwrite protection for your CICS journals.

What Part is provided by CSI-JOURNAL?

CSI-JOURNAL provides a batch journaling facility that is analogous to CICSjournaling. It allows you to recover the VSAM updates made in a batchenvironment without re-running the batch jobs. Refer to the CSI-JOURNALInstallation and Operations Guide for more information.

What Part is provided by CSI-RECOV?

CICS will not use these journal records to re-apply changes when a file has beendestroyed. This is where CSI-RECOV comes in. After you have restored theVSAM file (or files) from the latest backup tape, CSI-RECOV will re-applychanges made since the latest backup.

What Part is provided by CSI-ARMAN?

CSI-ARMAN maintains a "Recovery Control File", containing all of theinformation necessary to generate the jobstreams required to perform thefollowing:


Page 8 Introduction

• VSAM backups• CICS journal backups• Journal accumulations• VSAM Recoveries

The companion products; CSI-RECOV, CSI-JOURNAL, and CSI-JMASTERcommunicate with CSI-ARMAN, providing the the necessary information to theRecovery Control File, to enable the required jobstreams to be generated.

Together, these four products provide an integrated, and automated VSAMRecovery System.

What Part is provided by DL/I?

CSI-RECOV can be used to backup and managed journal records generated byDL/I, however, CSI-RECOV does not perform the actual recovery of your DL/Idatasets. You still use the standard DL/I recovery utilities. When a DL/Irecovery is required, you use CSI-RECOV to extract the required DL/I journalrecords from your CSI-RECOV Journal Backup dataset to a separate DL/I logdataset that can be used by your DL/I recovery and/or "change-accum" utilities.

Will the Process work when I need it?

After you have installed CSI-RECOV it may be a long time before you need touse it, if ever, and you may therefore not get around to testing CSI-RECOV or theCICS journaling process. To help you verify that the entire recovery process willwork, we have provided you with software and procedures that will ensure thecorrect execution of all the steps involved in this recovery process: the CICSjournaling, your backup and restore system, and the CSI-RECOV software.

This verification process should be run after you have installed CSI-RECOV, andwhenever a new release of CICS is installed. The section "Verification andTesting" describes this process in detail.


Introduction Page 9

Features of CSI-RECOV

• Single program execution for all CSI-RECOV functions.

• Any number of CICS journals or journal backups can be input to CSI-RECOV. Sorting requirements can be specified for any combination ofinputs.

• The sort is invoked from within CSI-RECOV reducing I/O to journal files.

• Any or all input journal records can be printed, written to journal backupfile(s) or used to recover VSAM datasets during a single execution of CSI-RECOV.

• CSI-RECOV provides comprehensive journal management support,including: printing, copying, merging, and automatic aging/purging ofjournal records.

• Multiple journal records for the same VSAM key are logically combinedduring recovery to reduce I/O to your VSAM datasets.

• CICS journals can be in standard or SMF format. If SMF format is used, theCICS release and APPLID will automatically be extracted by CSI-RECOV.

• Backward or 'BACKOUT' recovery can be specified to replace the 'before'images on your VSAM datasets.

• A 'NOUPDATE' mode can be used to simulate a recovery without actuallyupdating your VSAM datasets.

• Forward, Backout and Noupdate recovery can all be performed againstdifferent VSAM datasets during a single execution.

• All types of VSAM datasets can be processed, KSDS, RRDS, ESDS, includingEmpty files.

• Complete selection control over which journal records will be processed.

• CSI-RECOV can be used in conjunction with CSI-ARMAN, the AutomatedRecovery Manager from CSI International, Inc. to provide integrated controlof your VSAM Backup and Recovery processing.


Page 10 Introduction

• Journal records generated by DL/I can be backed up and managed by CSI-RECOV. When a DL/I recovery or "change-accum" is required, a DL/I logdataset can be generated by CSI-RECOV to be used by your standard DL/Irecovery utilities. Batch DL/I logs can be standard sequential, VSAM-managed-SAM, or VSAM ESDS datasets.

• CSI-RECOV provides extensive statistical and error reporting for all of itsJournal Management and VSAM Recovery functions.

• CSI-RECOV can generate a "reduced" Journal Backup format containing onlythe data changed in the "before" and "after" image journal records. Thisfeature is intended to improve journal transmission efficiency for off-sitearchiving or simply to save disk space.

• A complete verification system is supplied with CSI-RECOV to test yourCICS journaling installation and VSAM file Backup/Restore processing. Itwill give you the confidence that recovery WILL work when it is needed.

• Step by step instructions are provided in the CSI-RECOV documentation toassist you in adding journaling support to your CICS systems.


Introduction Page 11

Terminology

The following terms are used throughout this documentation to define specificitems or processes.

CICS Journal

Any Journal dataset created by CICS in either standardor SMF format. This can also be a copied image of aCICS Journal dataset as long as its format is the same asthat created by CICS. These datasets are input to CSI-RECOV via an INPUT JOURNAL Command.

Batch Journal

A Journal dataset created by CSI-JOURNAL. Thesedatasets have the same format as OUTPUT BACKUPfiles created by CSI-RECOV. Therefore, Batch Journalsare input to CSI-RECOV via an INPUT BACKUPCommand.

DL/I Log

Any dataset created by CSI-RECOV by the use of anOUTPUT DLILOG Command, or by a batch DL/Iprogram. This does not have the same format as a CICSJournal dataset, and can only be used as input to CSI-RECOV via an INPUT DLILOG Command.

A DL/I Log generated by CSI-RECOV can be used asinput to any of your standard DL/I recovery utilities.

Journal Backup

Any dataset created by CSI-RECOV by the use of anOUTPUT BACKUP Command. This does not have thesame format as a CICS Journal dataset, and can only beused as input via an INPUT BACKUP Command.

Forward Recovery

The process of updating one or more VSAM datasetswith the 'after' images created by CICS automaticjournaling. The purpose of Forward Recovery is toreturn a VSAM file to the state is was in prior to a Diskloss.


Page 12 Introduction

Backout Recovery

The process of updating one or more VSAM datasetswith the 'before' images created by CICS automaticjournaling. The purpose of Backout Recovery is to returna VSAM file to the state is was in prior to the updatingperformed by one or more CICS transactions. Thisprocess is NOT the same as CICS dynamic transactionbackout. This process will NOT automatically determine'inflight' transactions.


Migration Requirements Page 13

Migration Requirements

This section describes the changes you need to consider if you are migratingfrom an earlier release of CSI-RECOV. The changes are grouped by release level.You will not need to consider the changes for releases older than the one you arecurrently using. You will need to consider changes for all releases since therelease you are currently using.

Changes from Release 3.0

• The load module names have been changed to a CSI prefix.


• The INPUT JOURNAL Command default for the CICS release has beenchanged from 1.6 to 1.7. This new default will work correctly for all releasesof CICS from 1.7 and above. If you are using CICS release 1.6 or below, youmust change you INPUT JOURNAL Commands to include the 1.6 Operand.

• CSI-RECOV contains an integrated interface to CSI-ARMAN, the AutomatedRecovery Manager from CSI International, Inc. to provide integrated controlof your VSAM Backup and Recovery processing.

• A new Command, AUTO has been added. This is used to activate theinterface to CSI-ARMAN. New Operands have also been added to theINPUT and OUTPUT Commands to support this new interface.

• New Operands have been added to the SORTOPTION Command to specifythe desired sorting sequence. These new Operands can be used for DL/Irecovery, and for VSAM recovery that includes updates through a path or analternate index.


Page 14 Migration Requirements


• CSI-RECOV can now generate a "reduced" format of the OUTPUT BACKUPdataset. The "reduced" record format contains only those bytes of data thatwere different between the "before" and "after" image journal record. Thisfeature can provide as much as a 30% space reduction. During recovery, CSI-RECOV automatically detects whether you are using "full" or "reduced"formats and proceeds accordingly.

Refer to the FORMAT Operand of the OUTPUT BACKUP Command formore information.

• CSI-RECOV can now support VSAM ESDS DL/I log files. A new Operand,ESDS has been added to the INPUT DLILOG Command. You must specifyESDS for each DL/I log that is VSAM ESDS. This Operand is requiredbecause CSI-RECOV cannot distinguish between VSAM ESDS and VSAM-managed-SAM datasets.

• A new SELECT Operand, DATETIME has been added to simplify thespecification of starting and/or ending ranges that involve both a Date and aTime.


• The format of the Journal Backup dataset created using an OUTPUTBACKUP Command has changed. CSI-RECOV will accept Journal Backupdatasets from all earlier releases, however, Journal Backups created by thisrelease of CSI-RECOV cannot be read by earlier releases.

• CSI-RECOV can now manage DL/I journal records. If you are using CSI-RECOV to backup VSAM journal records from a CICS System Journal thatalso contains DL/I journal records, you may need to review your SELECTCommands to make sure that only the records you want are backed up byCSI-RECOV.

CSI-RECOV will automatically read and select all VSAM and DL/I journalrecords found on a CICS System Journal unless specifically excluded via aSELECT or EXCLUDE Command or Operand. Refer to section "Commandsand Operands" for more information.

• Two new Commands have been added to support DL/I Journalmanagement. The INPUT DLILOG Command can be used to read DL/I logscreated by batch DL/I programs. The OUTPUT DLILOG Command can beused to create a DL/I log for use by any of DL/I's standard recovery utilities.


Migration Requirements Page 15

• A new Operand (WRAP) has been added to the INPUT JOURNALCommand. This new Operand specifies whether or not CSI-RECOV shouldextract journal records from beyond the "wrap-point" of a CICS Journal. Thedefault is to not extract journal records from beyond the "wrap-point". If youhave CICS Journals that can wrap, and you need CSI-RECOV to extract alljournal records from those journals, you must specify the WRAP Operand.

• The default for Operand (MAXKEY) of the SORTOPTION Command hasbeen changed from 234 to 232. Refer to the SORTOPTION Command todetermine if you need to specify this Operand.


Page 16 Installation

Installation

The CSI-RECOV programs described in this manual run under VSE, and aredistributed on a 1600 BPI tape. When this tape is loaded into your Reader Queue,there will be one POWER job which will catalog the following modules to yourlibraries:

Source Library Modules:

E.CSIIOGEN I/O Module Customization Macro

A.CSIRECDB Backup I/O Module Sample Macro CallA.CSIRECDD DLILOG I/O Module Sample Macro CallA.CSIRECDJ Journal I/O Module Sample Macro Call

C.CSIRECVI Verification Program Source to Initialize FilesC.CSIRECVU Verification Program Source to Update FilesC.CSIRECVC Verification Program Source to Check Files

A.CSIRECV0 Verification CICS FCT EntriesA.CSIRECV1 Verification CICS JCT EntriesA.CSIRECV2 Verification JCL to Create FilesA.CSIRECV3 Verification JCL to Recover Files

A.CSIRECJ1 Prototype Recovery JCL

Note: In a VSE-SP library, these members are named member.sublib (eg.CSIIOGEN.E).

Core Image Library:

CSIRECOV Forward Recovery ModuleCSIRECDB Default Backup I/O Access ModuleCSIRECDD Default DLILOG I/O Access ModuleCSIRECDJ Default Journal I/O Access ModuleCSIRECVI Verification Program to Initialize FilesCSIRECVU Verification Program to Update FilesCSIRECVC Verification Program to Check Files


Installation Page 17

Minimum library space required:

Source Statement Library: FBA Blocks = 380LIBR Blocks = 190

Core Image Library: FBA Blocks = 560LIBR Blocks = 280

Installation Step 1

Mount the distribution tape on a tape drive and enter the following POWERCommand on the console:

S RDR,cuu

(cuu = tape drive address)

This will load the POWER job CSIRECOV into your Reader Queue.

Installation Step 2

Alter the POWER job (CSIRECOV) that was loaded in the reader queue to run ina partition that has labels established for linkediting. This job has a pausestatement that allows you to enter a "LIBDEF" statement if necessary.

A RDR,CSIRECOV,DISP=D,CLASS=?

Installation Step 3

When job CSIRECOV starts up, it will pause allowing you to enter "// LIBDEF"statements. You must enter a "// LIBDEF" statement with the "TO=" option for acore image and source statement libraries unless they have already been setusing permanent LIBDEFs.


Page 18 Installation

The following LIBDEF prompts are displayed on the System console:

* <<<< FOR VSE 1.3.X USE THE FOLLOWING LIBDEFS >>>>* // LIBDEF CL,TO=USRCL?* // LIBDEF SL,TO=USRSL?** <<<< FOR VSE 2.1.X USE THE FOLLOWING LIBDEF >>>>* // LIBDEF *,CATALOG=LIB?.SUBLIB?,SEARCH=LIB?.SUBLIB?** RE-ENTER LIB?.SUBLIB? IN RESPONSE TO VSE MESSAGES* L032I LIBDEF MISSING FOR TO LIBRARY ....* L146I ENTER THE LIBRARY.SUBLIBRARY .....// PAUSE ENTER ABOVE LIBDEFS AS REQUIRED

When the installation job is complete, review the printed output for errors.Common problems that may occur during the installation job are:

• One of the libraries has filled up and requires condensing.

• A LIBDEF statement was omitted or improperly declared.

• Install job was run in a partition not set up for Link Editing.

Installation Step 4

Review the section "Customizing CSI-RECOV" to determine if the objectmodules cataloged in the Core Image Library in step 3 are suitable for yourenvironment. If they are not, make the necessary changes.

Installation Step 5

Verify the entire Journaling and Recovery process, as described in the section"Verification and Testing".


Customization Page 19

Customizing CSI-RECOV

CSI-RECOV uses customizable I/O modules to access CICS journals, to read andwrite Journal Backup files and to read and write DL/I log files. Default I/Omodules have been provided in both source and object form. Customization ofthese modules may be required to change Device types, Blocksizes, or otheroptions defined below.

Macro CSIIOGEN has been provided to customize the Default I/O modules or togenerate additional I/O modules to be used for varying the formats of Journalsand Journal backups created by CSI-RECOV. If you are generating your ownI/O modules for multiple formats of journals or journal backups, the names usedfor your I/O modules should NOT begin with the letters CSI. If they do, CSI-RECOV may mistake your module name for one if its internal modules and errormessage CSIRECOV-13 or CSIRECOV-23 will result.


Page 20 Customization

CSIRECDJ (Default CICS Journal I/O module)

Module CSIRECDJ is the default I/O module used by CSI-RECOV to accessCICS journal files. The MODNAME Operand of the INPUT Command can beused to provide the name of a different I/O module.

The default I/O module provided on the installation tape may not be suitable foryour system. For example, the block size may be too large for the type of DASDyou have, or your CICS journals may be on tape. To change the default I/Omodule, generate a custom module and catalog it as CSIRECDJ.

Listed below are the Operands that were used to generate module CSIRECDJ:

10..16..20...25...30...35..........72CSIIOGEN , X

OPSYS=VSE, XBLKSIZE=32767, XIOAREAS=YES, XDEVICE=DISK, XSYSNBRI=SYS004, XLABEL=NO, XREWINDI=UNLOAD

This macro call and its associated JCL are supplied in member A.CSIRECDJ. Youmay move this member to your text editor or code it manually as shown in theexample later on. If you use the prototype in A.CSIRECDJ, be sure to change thedefault values as required for your system.



CSIRECDB (Default Journal Backup I/O module)

Module CSIRECDB is the default I/O module used by CSI-RECOV to create andaccess journal backup files. The MODNAME Operand of the INPUT andOUTPUT Commands can be used to provide the names of different I/Omodules.

The default I/O module provided on the installation tape may not be suitable foryour system. For example, the block size may be too large for the type of DASDyou have, or you may decide to write your Journal Backup files to disk. Tochange the default I/O module, generate a custom module and catalog it asCSIRECDB

Listed below are the Operands that were used to generate module CSIRECDB:

10..16..20...25...30...35..........72CSIIOGEN , X

OPSYS=VSE, XBLKSIZE=32767, XIOAREAS=YES, XDEVICE=TAPE, XSYSNBRI=SYS004, XSYSNBRO=SYS005, XLABEL=STD, XREWINDI=UNLOAD, XREWINDO=UNLOAD

This macro call and its associated JCL are supplied in member A.CSIRECDB.You may move this member to your text editor or code it manually as shown inthe example later on. If you use the prototype in A.CSIRECDB, be sure to changethe default values as required for your system.



CSIRECDD (Default DL/I Log I/O module)

Module CSIRECDD is the default I/O module used by CSI-RECOV to create andaccess DL/I log files. The MODNAME Operand of the INPUT DLILOGCommand can be used to provide the name of a different I/O module. Thismodule is not required for VSAM ESDS DL/I log files.

The default I/O module provided on the installation tape may not be suitable foryour system. For example, the block size may be too large for the type of DASDyou have, or you may decide to write your DL/I log files to disk. To change thedefault I/O module, generate a custom module and catalog it as CSIRECDD

Listed below are the Operands that were used to generate module CSIRECDD:

10..16..20...25...30...35..........72CSIIOGEN , X

OPSYS=VSE, XBLKSIZE=32767, XIOAREAS=YES, XDEVICE=TAPE, XSYSNBRI=SYS004, XSYSNBRO=SYS005, XLABEL=STD, XREWINDI=UNLOAD, XREWINDO=UNLOAD

This macro call and its associated JCL are supplied in member A.CSIRECDD.You may move this member to your text editor or code it manually as shown inthe example later on. If you use the prototype in A.CSIRECDD, be sure to changethe default values as required for your system.



Generating a Custom I/O Module

To generate an I/O module, use the CSIIOGEN macro described below. Anexample of a job to generate and catalog an I/O module is shown at the end ofthis section.

The following pages provide a detailed explanation of the CSIIOGEN macro andits Operands.

How to enter

10..16..20...25...30...35............72CSIIOGEN , X

OPSYS=VSE, XBLKSIZE=32767|nnnnn, XIOAREAS=NO|YES, XDEVICE=DISK|TAPE, XSYSNBRI=SYS004|SYSnnn, XSYSNBRO=SYS005|SYSnnn, XLABEL=NO|STD, XREWINDI=UNLOAD|REWIND|NORWD, XREWINDO=UNLOAD|REWIND|NORWD

NOTE: If you use a Disk/Tape Management System, you may be able to specifysome of the CSIIOGEN options via the Management System's JCL.



Explanation:

OPSYS=VSE

Must be set to the Operating System in use (in this caseVSE).

BLKSIZE=32767|nnnnn

Maximum Blocksize of the dataset. This can be anyvalue up to the track capacity of your device, (if CKD).

The maximum that can be specified for any device typeis 32767.

For CICS journals, this field must contain the largest"BUFSIZE" value specified in the CICS JCT for thejournal(s) to be processed by this I/O module. CSI-RECOV creates its journal backup datasets in VBSformat (variable blocked spanned) which allows logicalrecords to span multiple blocks. The record format in theDTF is "undefined", and CSI-RECOV does its ownblocking.

IOAREAS=NO|YES

Specifies whether or not to generate internal I/O areas.

For VSE 1.3.5 or later, specify "NO" for DISK and "YES"for TAPE.

Prior to VSE 1.3.5, specify "YES" for both DISK andTAPE devices.

If you are using the MVT Operating System fromSoftware Persuits, specify "YES" for both DISK andTAPE devices.

DEVICE=DISK|TAPE

Specifies the type of device containing the journal file.

SYSNBRI=SYS004|SYSnnn

For tape datasets. This is the SYSnnn to be used foraccessing the tape drive during Input operations. Thisvalue can be overridden by the INPUT Command.



SYSNBRO=SYS005|SYSnnn

For tape datasets. This is the SYSnnn to be used foraccessing the tape drive during Output operations. Thisvalue can be overridden by the OUTPUT Command.

LABEL=NO|STD

For tape datasets. This option defines whether or not thetape is labeled (specify STD for standard labeled tapesand NO for unlabeled tapes).

REWINDI=UNLOAD|REWIND|NORWD

For tape datasets. This option defines the action to occurwhen the tape is closed after Input operations.

• UNLOAD will rewind and unload the tape.

• REWIND will rewind the tape without unloadingit.

• NORWD will leave the tape positioned as is.

REWINDO=UNLOAD|REWIND|NORWD

For tape datasets. This option defines the action to occurwhen the tape is closed after Output operations.

• UNLOAD will rewind and unload the tape.

• REWIND will rewind the tape without unloadingit.

• NORWD will leave the tape positioned as is.



EXAMPLE:

The following example can be used to customize CSIRECDJ for VSE:

// JOB jobname// OPTION CATAL PHASE CSIRECDJ,*// EXEC ASSEMBLYCSIRECDJ CSIIOGEN, X

OPSYS=VSE, XDEVICE=TAPE, XBLKSIZE=32767

END/*// EXEC LNKEDT/&

A complete macro prototype is provided in member A.CSIRECDJ.


Page 27

PREPARING CICS FOR RECOVERY


Preparing CICS for Recovery Page 29

Overview of CICS Journaling

The points covered in this section are:

• Journaling Description and Considerations

• CICS Journal Recommendations

• Installing Journaling in your System

The information in this section has been summarized from the followingmanuals. You may want to refer to these manuals for further information.

• CICS Resource Definition Guide - Journal Control Table

• CICS Resource Definition Guide - File Control Table

• CICS Resource Definition Guide - System Initialization Table

• CICS Installation and Operations Guide - Journal Data Sets

• CICS Performance Guide - Logging and Journaling.

Note: The information presented in the following pages deal mostly withDisk Journals. If you choose to use Tape Journals, please refer to theIBM Manuals listed above.


Page 30 Preparing CICS for Recovery

Journal Functions of CICS

CICS provides three types of Journaling functions:

1. Automatic Logging2. Automatic Journaling3. User Journaling

Automatic Logging means logging done to the System Log, Journal ID is "01".This logging is for the Emergency Restart processing performed by CICS after asystem abend. The log records, generated by Automatic Logging, are not usedfor Forward Recovery processing. Automatic Logging is specified via the "LOG"Operand of the CICS FCT.

Automatic Journaling is a function of CICS File Control that creates "Beforeand/or After Images" of all records added, updated, or deleted. These journalrecords are written to any CICS Journal 01 - 99. Although the System Log(journal 01) can be used for Automatic Journaling, we recommend that aseparate journal be used (02 - 99). The following sections will explain why. Therecords created by Automatic Journaling are the input to CSI-RECOVprocessing. Automatic Journaling is specified via the "JREQ" and "JID" Operandsof the CICS FCT.

User Journaling refers to journal records formatted, written, and used byapplication programs. User journal records are not used by CSI-RECOV,although they may be written to the same CICS journal as the AutomaticJournaling records if desired.

Journal File Alternatives

CICS provides a few basic alternatives when defining journal files, to allow youto tailor individual journals according to their use.



One Journal Dataset vs Two

Each logical journal file (01 - 99) can be defined as having either one or twojournal datasets, each referenced with a unique Dataset Name. A journal datasetmust consist of a single extent, and may not be defined as a VSAM ManagedSAM data set.

With One Journal Dataset - If the journal becomes full, CICS will start over atthe beginning, overwriting the data at the beginning of the journal. For theSystem Log, this is not a problem as long as the journal is large enough tocontain all records required to recover from an abend of the longest running taskthat updates "protected resources".

For journals required for Forward Recovery, this overwriting may not be aproblem either, as long as the journal is large enough to contain all file updatessince the previous backup of your dataset. Since the Forward Recovery Processnormally involves a larger number of records, the option for two journal datasetsis usually a better choice.

You must specify the WRAP Operand on all INPUT JOURNAL Commands thatare accessing CICS Journals that may have wrapped. If you do not specify theWRAP Operand, CSI-RECOV will stop reading the CICS Journal when the"wrap-point" is reached.

Note: For journals on FBA devices, using a single journal dataset is not anoption, because an end-of-file record is always written after each blockof journal records, making the remainder of the file inaccessible.

With Two Journal Datasets - When one journal dataset becomes full, CICS willswitch to the beginning of the other dataset. This gives you the opportunity tobackup the first dataset prior to the second dataset becoming full. When thesecond dataset becomes full, CICS will switch back to the first dataset. ForForward Recovery Journals, we recommend you define two journal datasetswith the first dataset large enough to hold 1.5 times the number of updatescreated between dataset backups, with a second smaller dataset as a "Safety Net".This second dataset should be large enough to allow CICS to continuefunctioning without filling the dataset while the first dataset is being backed upand initialized. After CICS switches back to the first dataset, backup andinitialize the second dataset. The first dataset should be maintained at a size thatrequires the second dataset to be rarely used.



Disk vs Tape Journals

The first decision you will need to make is whether to use disk or tape journals.The following points should be considered:

• The System Log (Journal 01) is used for CICS Emergency Restart. Thismeans that when CICS restarts after an abend, the log is read backwards tofind all changes made by the tasks that were in-flight. The relatively slowspeed of tape processing would thus delay the availability of CICS after asystem abend.

• Tape is infinitely large. The journal can extend from volume to volumewithout overwriting any data. If you are expecting large amounts ofjournaled updates and have a limited amount of disk space, this may beimportant.

• A "one-dataset" tape journal implies a single drive, not a single volume.However, when a volume is filled, CICS update activity is suspended whilethe tape rewinds so that another volume can be mounted. You should neveruse a single tape journal if all your updates cannot fit on a single tapevolume.

• A "two-dataset" tape journal implies that two tape drives are dedicated tothe journal. When the first volume becomes full, CICS switches to thesecond drive and rewinds/unloads the first so that a new volume can bemounted. This is more efficient than the one-dataset tape, but requires twotape drives.

• Reliability of the device or media is also an important consideration. Tapesare not always as reliable as disks.

• Space utilization characteristics of some disk drives make them not verysuitable for journals. A system log with its typically short blocks can requirealmost twice the disk space on a 3380 disk drive as it would on a 3350 diskdrive. This is because a 3380 has a large overhead associated with eachphysical block that makes it very wasteful for small block sizes.



One Journal vs Many

CICS Emergency Restart requires the definition of a system log (Journal ID 01).The system log can also be used for journaling, but the following points shouldbe considered:

• If journaling is combined with logging, Emergency Restart times can beincreased due to the journal records that must be skipped to find the logrecords.

• Forward Recovery Journals are easier to keep in sync with dataset backups ifthey are reinitialized each time a backup is done. If system logs areinitialized, CICS WARM STARTS and EMERGENCY RESTARTS cannot beperformed.



CICS Journal Recommendations

The following recommendations are based on the assumption that you will beusing Automatic Logging for CICS Emergency Restart, and AutomaticJournaling for forward recovery. They are also based on experience with manydifferent systems, and will suit the requirements of most installations. Specialsituations (such as extremely high transaction rates) may require differenttechniques. These recommendations are intended to be used as a starting point,to be fine tuned as needed.

• The System Log

If you are not using DL/I, we recommend defining a single dataset for theSystem Log. This should be initialized when first defined and then neverreinitialized unless it is being moved or changed in size. This provides themost stable environment for CICS Warm Starts and Emergency Restarts.

If you are using DL/I, refer to the CICS Installation and Operations Guidefor instructions for creating and initializing the appropriate journalingenvironment for DL/I.

• Separate Journals for Forward Recovery

The journal(s) used for Automatic Journaling should be separate from thesystem log. If you are using a disk, you should have two journal datasets(JTYPE=DISK2), with the first dataset large enough to hold 1.5 times thenumber of updates created between dataset backups. The second dataset canbe smaller, and is a "safety net" to allow the primary dataset to be backed upand initialized if it becomes full.

• A Tape Journal Can be OK For Forward Recovery Journals Under TheFollowing Conditions:

All journaled activity can be contained on a single volume, or two drives canbe allocated to the journal to allow switching to occur without causingperformance problems.



• Placement of Journal Datasets:

Since recovery may be required due to a DASD failure, we recommend thatthe journal datasets and the VSAM files reside on two different physicaldevices.

JOURNALS JOURNALS

VSAMDATASETS

VSAMDATASETS

If all of your disk devices have VSAM files requiring journaling, you must havemultiple journal datasets to ensure that a VSAM file can be recovered after aDASD failure.



Installing Journaling in your System

The steps covered in this section are the following:

1. Defining your Journal Control Table (JCT)

2. Initializing your Journal File for CICS

3. Activating Automatic Journaling (CICS FCT)

4. Adding Journal Support to the CICS PCT, PPT and SIT Tables

5. Adding Journal File JCL to your CICS startup Jobstream

6. Writing EOF Mark on Tape Journals

Defining your Journal Control Table (JCT)

The CICS Journal Control Table (JCT) is the means by which you describe thephysical journal files and their characteristics to CICS. The JCT is defined withthree macro types:

DFHJCT TYPE=INITIAL First Section of Table

DFHJCT TYPE=ENTRY Occurs once for each journal file

DFHJCT TYPE=FINAL Last Section of Table

DFHJCT TYPE=INITIAL,SUFFIX=xx:

Defines this table to CICS. The Value "xx" is specified in the System InitializationTable (SIT) on the "JCT=xx" Keyword. This allows multiple JCTs to exist on thesame Load Library.



DFHJCT TYPE=ENTRY:

Defines each logical journal file to CICS.

JFILEID=NN

Gives a unique "ID" to each journal (02 - 99).JFILEID=SYSTEM is specified for Journal 01. This "ID" isused in the File Control Table (FCT) to designate whichfiles should be logged to which journal. This "ID" is alsoused by CICS to form the DLBL for the JCL.

JTYPE=DISK2

Defines type of Journal:

- DISK or TAPE

- ONE FILE or TWO FILES(for example: DISK1, DISK2, TAPE1, TAPE2)

If only one disk file is used, CICS will wrap the filewhen full, overwriting the old journal records.However, for journals on FBA devices, using one diskfile only is not an option, because an end-of-file recordis always written after each journal record.

If two disk files are used, CICS will flip/flop betweenthem allowing your operators time to backup one filewhile the other is being used by CICS.



BUFSIZE=4089

Defines the largest block that can be written to thisjournal. This size must be determined by you, using thefollowing criteria:

(The minimum you can specify is):

80 + Largest Record Key + Largest Data Record for CICS1.5 and 1.6

84 + Largest Record Key + Largest Data Record startingwith CICS 1.7

The largest size is:

• 32767 for tape

• 32761 for FBA

• Tracksize or 32767 for CKD

(whichever is smaller)

For FBA devices the CISIZE for the journal must be atleast 7 bytes larger than this value and must be amultiple of 512 if less than 8193 or a multiple of 2048 ifgreater than 8192.

The recommended size is 2 to 2.5 times the averagejournal record, as long as this would provide room forthe minimum (see above). The average size for a journalrecord is:

80 + average record key + average data record for CICS1.5 and 1.6

84 + average record key + average data record startingwith CICS 1.7

BUFSUV=4089

Normally not needed for Recovery Journals. If omitted,will default to value specified for "BUFSIZE".



JOUROPT=RETRY

Defines the actions taken by CICS upon encountering anerror or a FULL condition on this journal. Any or all ofthe following options may be coded (in parentheses ifmore than one is specified):

PAUSE Should be specified cautiously. Itmakes CICS wait for an Operatorresponse prior to overwriting a journal.

RETRY Causes CICS to switch journal datasetsif an I/O error occurs.

CRUCIAL Causes CICS to abend if an I/O erroroccurs and:• this is a single dataset journal• retry was not specified, or• an I/O error also occurred on the

other dataset

INPUT Is required for Dynamic TransactionBackout and Emergency Restart. Thisspecifies that input operations areallowed.

OPEN=INITIAL

Specifies that this journal should be opened at startup.

DEVADDR=(SYSnnn,SYSmmm)

Specifies the logical units for the first and second journalfiles

DFHJCT TYPE=FINAL

Defines the end of the JCT Table.



Initializing your Journal File for CICS

Each journal file must be initialized before CICS can use it. This function is onlyrequired prior to the first use, but we recommend that it be done after eachbackup of the journal so that the contents of the journal will not be duplicatedbetween journal backups.

If "DISK2" or "TAPE2" is specified for "JTYPE", both journal files must beinitialized.

Disk Journals

The JCL needed for initializing disk journals is as follows:

// JOB INIT// DLBL JOURNAL,'your.journal.name',0,SD,CISIZE=ccccc// EXTENT SYSnnn,vol-id,1,0,rel-trk/blk,nbr-trks/blks// ASSGN SYSnnn,DISK,VOL=vol-id,SHR// LIBDEF CL,SEARCH=PRDCLB// EXEC DFHJCJFP,SIZE=AUTO/&

NOTES:

• For FBA devices, the CISIZE must be at least 7 bytes larger than the JCTBUFSIZE and must be a multiple of 512 if less than 8193, or a multiple of2048 if greater than 8192.

• For CKD devices, omit the CISIZE Operand.



Tape Journals

The JCL needed for initializing tape journals is as follows:

// JOB INIT// ASSGN SYS010,CUU TAPE DRIVE// LIBDEF CL,SEARCH=PRDCLB// EXEC DFHFTAP/&



Activating Automatic Journaling (CICS FCT)

You can activate automatic journaling by specifying the following Operands inthe File Control Table (DFHFCT TYPE=DATASET) for each file that is to haveForward Recovery Support:

JID=nn

Where nn is the 'JFILEID' value of the journal file to beused for this dataset. Multiple files can share the samejournal. The choice of how many journals to use shouldbe based on the amount of update activity occurring andthe resulting loss of performance from the contentions oftoo many updates being funnelled to the same journal.

JREQ=(ASY,RU,WU,WN)

Specifies the type of file operations to be written to thejournal. Only the Update (WU) and Add (WN)functions are required for forward recovery. They causethe "after" images to be journaled.

The (RU) option causes the "before" images to bejournaled. This option is only required if you intend touse the FORMAT(REDUCED) Operand of the OUTPUTBACKUP Command, or if you want to be able toperform BACKOUT Recovery.

The (ASY) option will cause the journal records only tobe written when the buffer is full. This reduces theoverhead related to journaling, but does not ensure thatall updates are journaled prior to the dataset beingaltered. Omitting the (ASY) will guarantee that allupdates will be written to the journal first, but will causelonger response times, and shorter journal blocks. (ASYshould be used only for very high activity journals).



Add Journal Support to the CICS PCT, PPT and SIT Tables

Make sure that the following entries are in your CICS PCT and PPT.:

DFHPCT TYPE=GROUP,FN=JOURNAL

DFHPPT TYPE=GROUP,FN=JOURNAL

If you are using the CICS RDO facility, the above definitions are contained inGROUP DFHJRNL.

The following entry must be added to your CICS SIT. The "xx" is the valuespecified for the SUFFIX=xx in the DFHJCT TYPE=INITIAL macro entry:

DFHSIT JCT=xx,

The following entries are only required in your CICS SIT if you are running CICSrelease 1.6 or earlier:

DFHSIT JCP=1$, 'AUTOJRN' support

DFHSIT FCP=A$, 'AUTOJRN' support



Add Journal File JCL to your CICS Startup Jobstream

The Journal File JCL that you need to add to your CICS startup jobstream isshown below.

// DLBL DFHJnnA,'your.journal.diska',0,SD,CISIZE=nnnn// EXTENT SYSnnn,vvvvvv,....

// DLBL DFHJnnB,'your.journal.diskb',0,SD,CISIZE=nnnn// EXTENT SYSmmm,vvvvvv,....

NOTES:

• nn in DFHJnnA is the two digit number from 'JFILEID=' in JCT'.

• DFHJnnB is only required if 'DISK2' is specified for 'JTYPE' in the JCT.

• For FBA devices, CISIZE must be at least 7 bytes larger than JCT BUFSIZEand must be a multiple of 512 if less than 8193, or a multiple of 2048 ifgreater than 8192.



For Tape Journals

// ASSGN SYSnnn,CUU First dataset drive// ASSGN SYSmmm,CUU Second dataset drive

NOTES:

• SYSnnn and SYSmmm are the values specified in 'DEVADDR' in the JCT.

• SYSmmm is only required if 'TAPE2' is specified in 'JTYPE'.



Writing an EOF Mark on Tape Journals

If a CICS abend or system failure should cause a non-system log journal tape tonot be closed properly, a special CICS supplied program must be used to findthe end of the journal and write an ending EOF mark. If this is not done, an I/Oerror or invalid data could be input to the Forward Recovery Program.

The JCL to use to write EOF mark is shown below:

// JOB EOFTAPE// ASSGN SYS010,CUU TAPE DRIVE// LIBDEF CL,SEARCH=PRDCLB// EXEC DFHTEOF/&


Page 47

USING CSI-RECOV


Using CSI-RECOV (Considerations) Page 49

Considerations

Before the description of the actual Recovery process, we have listed a number ofissues to consider. Some of these issues may influence your approach torecovery, and we strongly recommend that you read the following section beforesetting up your Recovery JCL.

Advance Preparations

Recovering a lost file requires that you are prepared in advance. This means thatCICS Journaling and CSI-RECOV have already been installed and tested, andthat you have Recovery JCL ready before it is needed.

Accumulating Journal Data

The recovery process uses all journal records that were created after the time ofthe last VSAM file backup or DL/I image copy. The journal files themselves maybe defined to be large enough to contain all of the update activity for this periodof time, but if this is not feasible, each time CICS fills a journal file, the journaldata must be archived to another dataset before it is overwritten.

CICS journals can be backed up by CSI-RECOV by using the INPUT JOURNALand OUTPUT BACKUP Commands. A companion product, CSI-JMASTER, fromCSI, can be used to automatically submit the backup JCL each time CICS fills ajournal file. CSI-JMASTER will also protect your journal data from beingoverwritten by CICS prior to the backup completing.

If your CICS journal contains DL/I records that you want backed up, you eitheruse the OUTPUT BACKUP Command or the OUTPUT DLILOG Command forgenerating your journal backup. The OUTPUT DLILOG Command generates aDL/I log dataset that can be read by any of the DL/I recovery utilities. TheOUTPUT BACKUP Command generates a CSI-RECOV journal backup that cancontain both VSAM and DL/I journal records.

You can use the OUTPUT BACKUP dataset to manage all of your journalrecords until they are needed for a VSAM recovery or a DL/I change-accumprocess.


Page 50 (Considerations) Using CSI-RECOV

A Typical Failure/Recovery Cycle

A complete cycle of events would often look like this:

1. Backup of data files

2. Journaled CICS updates

3. ••••• File damage •••••

(At this point, the recovery process would begin)

4. Restore files from backup

5. Use CSI-RECOV to re-apply journaled updates to your damaged VSAMdataset(s)

The file has now been restored to the condition it was in just before damageoccurred (point 3. above).



Recovery with Non-journaled Batch Updates

The recovery process gets more extensive if the journals do not include allupdates to the files needing recovery. This could happen if non-journaled batchupdates are involved. The cycle of events would look as follows:

1. Data files are backed up

2a. Journaled CICS updates

2b. Batch updates (not journaled)

2c. More journaled CICS updates

3. ***** File damage *****

4. Restore files from backup

5a. Use CSI-RECOV to re-apply journaled updates from 2a. above

5b. Re-run batch updates

5c. Use CSI-RECOV to re-apply journaled updates from 2c. above.

The file has now been restored to the condition it was in just before damageoccurred (point 3. above).

The above process can be simplified by journaling the VSAM updates made bybatch programs. CSI International has a companion product, CSI-JOURNAL,that provides the Batch Journaling function without modification to any of yourapplication programs. Contact us for more information if you have a need forthis capability.



VSAM Share Option 4

If non-journaled updates are allowed to occur parallel with journaled updates(VSAM share option 4), the value of the journal for recovery purposes is negated,since it will be impossible to re-apply journaled and non-journaled updates inthe correct sequence. The recovery process must precisely follow the originalsequence of updates.

Even if the batch updates are journaled, the time-stamp on CICS journal recordsis accurate only to one tenth of a second. This is not accurate enough toguarantee the correct sequencing of updates during forward recovery if the sameVSAM records are updated by CICS and batch programs during the same tenthof a second.

Coordination of Data File Backups and Journal Files

The recovery process is based on the concept of re-applying all updates thatoccurred after the time of the data file backup, excluding updates that occurredbefore the data file backup. The most straight-forward way to ensure that thistakes place is to always backup and reformat the journal file(s) each time thedata files are backed up. In this way, you simply restore the data files(s), and useall journals created since the backup as input to the recovery process. Werecommend that program CSIRECOV be used to backup your journals using theINPUT JOURNAL Command to access your CICS journals and OUTPUTBACKUP and/or OUTPUT DLILOG Commands to generate backups of yourVSAM and/or DL/I journal records.

Note: A file should be closed in CICS while it is being backed up, to ensurethat all updated buffers have been written to the file, and to preventfurther updates from taking place during the backup process. If the fileremains open in CICS, the file will not be in a "known state" at the timeof the backup.

If a journal contains updates for multiple data files that are backed up atdifferent times, the time span covered by a given journal file may include someupdates which occurred before a data file backup, and some which occurredafter the backup. In other words, the data file backups and journal file backupsmay occur asynchronously.

CSI-RECOV handles this situation by allowing you to specifyINCLUDE/EXCLUDE parameters with starting dates and times, along withother criteria, for each VSAM file to be recovered. This will cause all journalrecords prior to this date and time to be bypassed.



VSAM Recovery Scenario (Manual)

If you backup file A on Monday, file B on Tuesday, file C on Wednesday, and if,on Friday afternoon, someone runs an "initialize disk" job that wipes out all theseVSAM files, you would follow a process as shown below:

1. Restore each VSAM file from its latest backup.

2. Modify the recovery job as follows:

a. ADD an INPUT JOURNAL Command for each CICS journal that wasused to journal the updates for files A, B, and C. Note that if the journalfile is on the same disk (physical and/or logical) as the data files, thiswould not be possible in some circumstances. If CICS is still up, youwould have to close or switch these journals to back them up, or elsebring CICS down. Include the SORT Operand for each INPUTJOURNAL Command for which the CICS journal may have wrapped.

b. ADD an INPUT BACKUP Command for each journal backup filecontaining journal records created after the earliest data file backup thatis being restored (file A: Monday).

c. ADD a SELECT Command using the DATASET, DATE and TIMEkeywords to:

• specify file A to be recovered from Monday• specify file B to be recovered from Tuesday• specify file C to be recovered from Wednesday

3. Run the recovery job

4. If the data file errors brought CICS down, bring CICS back up. (If yoursystem has emergency restart, it will back out any transactions that were in-flight at the time of the error.)

If the damaged files did not bring CICS down, just re-open the files. In thiscase, CICS will not initiate any form of dynamic transaction backout.



VSAM Recovery Scenario (Using CSI-ARMAN)

CSI-ARMAN, when used in conjunction with CSI-RECOV, CSI-JMASTER andCSI-JOURNAL, has the capability to capture all change record data locations andother information necessary to ensure complete file integrity upon recovery.

If CSI-ARMAN has been operational throughout the recovery time period, thefollowing JCL is all that is required to perform a VSAM recovery:

* $$ JOB JNM=RECOVERY// JOB RECOVERY// LIBDEF *,SEARCH=your.lib// EXEC CSIARMAN,SIZE=(AUTO,32K) BUILD RECOV(vsamid1,vsamid2,...) - APPLID(urapplid)/*/&* $$ EOJ

The command structure will generate the JCL and CSI-RECOV Commandsnecessary to include all current change information since the last recordedVSAM file backup for the identified VSAM files (vsamid1, vsamid2).

For additional information on more complex recovery situations, see the CSI-ARMAN Installation and Operations Manual.



DL/I Recovery Scenario

CSI-RECOV does not recover lost or damaged DL/I datasets. CSI-RECOV doesprovide journal backup and management support for DL/I journals. A typicalDL/I recovery should include the following actions:

1. Restore your damaged DL/I datasets from their latest image copies.

2. Use a CSI-RECOV job to generate a DL/I log file to be used for the actualDL/I recovery:

a. ADD an INPUT JOURNAL Command for your CICS System journal.Specify the SORT Operand to cause the journal records to be sorted intothe proper DL/I sequence.

b. ADD an INPUT BACKUP Command for each journal backup filecontaining DL/I journal records created after the earliest image filebackup that was restored in step 1. If your INPUT BACKUP was notgenerated using sorted input journals, specify the SORT Operand.

c. ADD an INPUT DLILOG Command for each batch DL/I log file that hasbeen generated since the earliest image file backup that was restored instep 1. Specify the SORT Operand to cause the journal records to besorted into the proper DL/I sequence.

d. ADD an OUTPUT DLILOG Command to generate a combined DL/I logfile to be used for the actual recovery process.

e. ADD a SELECT Command using the DATASET, DATE and TIMEkeywords to:

• specify the DBD names of the datasets needing recovery• specify the date and time of the image file backup for each DBD

name

f. ADD a SORTOPTION Command using the DLIRECOV keywords tocause CSI-RECOV to sort the DLI log file into the correct sequence forDL/I.

3. Use the DL/I log file created in step 2 as input to the standard DL/I recoveryprocess. If you have a large number of journal records, you will probablywant to start your recovery with a DL/I change-accum process.



Note: When using a DL.I log file as created in step 2 as input to thestandard DL/I recovery process, a blocksize parameter must beentered into col 31 of the L1 control card to override the DL/Idefault of 1100. The blocksize parameter should reflect the sizespecified in the CSIRECDD I/O module.


Using CSI-RECOV (Journal Backup JCL) Page 57

Journal Backup JCL

CSI-RECOV can be used to backup your CICS journals when journal extents arefilled, or daily to cover periods between VSAM dataset backups. Any number ofCICS journals can be backed up at one time. They can be written to one ormultiple Journal Backup files depending on the OUTPUT BACKUP Commandsand SELECT Operands provided. The CICS Journal files can be merged into aprevious Journal Backup file.

The following JCL is an example of how a Journal Backup is specified to CSI-RECOV:

* $$ JOB JNM=BACKUP,DISP=D,CLASS=A,PRI=3// JOB BACKUP** BACKUP CICS JOURNAL FILES*// LIBDEF CL,SEARCH=usrcl?// DLBL dfhj02a,'your.cics.journal.a'// EXTENT SYSxxx,volxxx// DLBL dfhj02b,'your.cics.journal.b'// EXTENT SYSxxx,volxxx// TLBL oldbkup,'your.backup.name'// ASSGN SYS004,181// TLBL backup1,'your.new.backup.name1'// ASSGN SYS005,182// TLBL backup2,'your.new.backup.name2'// ASSGN SYS006,183// SORTWK1,'your.sort.work.file'// EXTENT SYSnnn,volxxx// EXEC CSIRECOV,SIZE=(AUTO,100K)INPUT JOURNAL(dfhj02a dfhj02b) SORTINPUT BACKUP (oldbkup) - SELECT ( GE-DATE(-7) )OUTPUT BACKUP(backup1/SYS005 backup2/SYS006)/*/&* $$ EOJ

The Commands and JCL required will vary depending on your needs, thefollowing points describe the backup JCL shown above:


Page 58 (Journal Backup JCL) Using CSI-RECOV

• The INPUT JOURNAL Command specifies the CICS journal files to bebacked up. The list of DLBL/TLBL names following JOURNAL specifies thattwo CICS journal files are to be read in the specified sequence. You canspecify any number of CICS Journal files in this list as long as they can all beread with the same MODNAME. The modname specifies the device type,DISK or TAPE, and maximum blocksize characteristics. The SORT Operandspecifies that all records from the specified list of CICS Journals are to besorted prior to being backed up. The sort sequence can be overridden via theFIELD Operand of the SORTOPTION Command. A SELECT Operand can beadded to restrict which journal records are backed up. In this example, alljournal records are kept.

• The INPUT BACKUP Command, without a SORT Operand, specifies thatthe CICS journal files are to be merged with a previous Journal Backup filecreated by CSI-RECOV. The SELECT Operand specifies that all JournalBackup records that were created more than 7 days ago are to beautomatically purged.

• The OUTPUT BACKUP Command specifies that a Journal Backup file is tobe created by CSI-RECOV by merging the sorted CICS journal files and theselected records from the previous Journal Backup. The two TLBL namesfollowing BACKUP specifies that dual Backup files are to be created, the firston SYS004 and the second on SYS005. If Disk backups were used, theSYSnnn values would be omitted.

• This sample job illustrates how CSI-RECOV can be used to archive yourCICS journal records for any time period desired.


Using CSI-RECOV (Recovery JCL) Page 59

Recovery JCL

Prototype JCL is provided in Source member A.CSIRECJ1 and contains 2 steps,as described below and in the following JCL sample.

Step 1 - Restoring lost files:

In this manual, we have not included instructions on how to do this step(restoring from backup tape) because no two installations have the sameprocedures. As this is a very critical step, however, you will have to be preparedto selectively restore one or more files, when needed.

Step 2 - Recover VSAM Files

Use CSI-RECOV to apply the journaled updates to the file(s) being recovered.The sample jobstream will INPUT two CICS journals, sorting them intoFilename, Record key, Date and Time sequence, and then merge the sortedrecords with three journal backups created previously by CSIRECOV.

Depending on circumstances at the time of a failure, you will have to change JobStep #2 of the prototype JCL in the areas listed below:

• Tape drive cuu (if backups are to be input).

• DLBL/TLBL for each Journal Backup to be input. (A MODNAME parm maybe required on the INPUT BACKUP Command if the Backup format doesnot match the Default module CSIRECDB.)

• DLBL for each VSAM file being recovered (if not in standard labels).

• Modify the INPUT JOURNAL Command to include all CICS Journals to beread.


Page 60 (Recovery JCL) Using CSI-RECOV

• Modify the INPUT BACKUP Command to include all CSI-RECOV Journalbackups to be read. Include a separate INPUT BACKUP Command for eachseries of backups that covers the same time period (Note: files within a singleCommand are processed serially, files on multiple INPUT Commands aremerged).

• Modify the SELECT Command to include only the DDNAMEs of the files tobe recovered and the DATE/TIME period desired. (Refer to the section onRecord Selection for additional options.)

You will also need to supply program CSIRECOV with Commands andOperands as shown later in this section.

The following JCL is provided in Source member A.CSIRECJ1.

* $$ JOB JNM=RECOVER,DISP=D,CLASS=A,PRI=3// JOB RECOVER** JOB STEP 1 INSERT YOUR RESTORE JCL HERE** JOB STEP 2 RECOVER VSAM FILES*// LIBDEF CL,SEARCH=USRCL?// DLBL DFHJ01A,'your.cics.journal.A'// EXTENT SYSxxx,volxxx// DLBL DFHJ01B,'your.cics.journal.B'// EXTENT SYSxxx,volxxx// SORTWK1,'your.sort.work.file'// EXTENT SYSnnn,volxxx// TLBL BACKUP1,'your.backup.name1'// TLBL BACKUP2,'your.backup.name2'// TLBL BACKUP3,'your.backup.name3'// ASSGN SYS004,181// DLBL DDNAME1,'your.vsam.file1',,VSAM,CAT=xxxxxxx// DLBL DDNAME2,'your.vsam.file2',,VSAM,CAT=xxxxxxx// EXEC CSIRECOV,SIZE=(AUTO,32K)INPUT JOURNAL(dfhj01a dfhj01b) SORTINPUT BACKUP (backup1 backup2 backup3)SELECT FILE(ddname1 ddname2) GE-DATE(yyddd)OUTPUT VSAM/*/&* $$ EOJ

Note: ddname1 and ddname2 must be the same names contained in yourCICS FCT for the datasets being recovered.


Using CSI-RECOV ( Commands) Page 61

Commands and Operands

Parameter cards must be supplied to program CSIRECOV to specify whichINPUT journals are to be processed and which OUTPUT operations are to beperformed. At least one INPUT Command must be specified. All otherCommands are optional.

Syntax

The syntax of CSI-RECOV's Commands is the same as the one used by the IBMutility IDCAMS:

• A Command followed by keyword Operands, with the value to be assignedto a keyword specified in parentheses.

• Blanks or commas are used to separate Operands from the Command andfrom other Operands.

• Continuation is specified by coding a dash as the last non-blank on the lineto be continued.

• Comments may appear before, between, and/or after Operands.

• A comment starts with the characters "/*", is ended by the characters "*/",and may be continued to multiple lines as needed.

In the following instructions, the CSI-RECOV Commands and Operands shouldbe interpreted as follows:

• UPPER CASE = the exact characters to be entered

• lower case = values to be supplied by you

• boldface/underlined keywords or values = default values

• Vertical bar "|" separates mutually exclusive Operands

• [values enclosed in brackets] are optional


Page 62 (Commands) Using CSI-RECOV

Refer to Appendix A for a more complete description of how to code Commandsand Operands.


Using CSI-RECOV ( Commands) Page 63

Commands

The Commands that are used in CSI-RECOV are the following:

1. INPUT Defines the input journal datasets to be read by CSI-RECOV.

2. OUTPUT Defines the output destinations for the selected inputjournal records read from the INPUT datasets.

3. SELECT Defines the selection criteria that INPUT records mustmeet to be passed to the OUTPUT destinations.

4. SORTOPTION Provides sorting and sequence checking options.

5. ATTRIBUTE Provides special processing needs of individual VSAMdatasets.

6. AUTO Activates the interface between CSI-RECOV and CSI-ARMAN.

Please see the following pages for detailed descriptions of allCommands/Operands.


Page 64 (INPUT Command) Using CSI-RECOV

INPUT Command

The INPUT Command is used to specify the source of the journal records to beused by CSI-RECOV.

Any number of INPUT Commands can be specified. If more than one isspecified, the journal records from each INPUT Command will be merged withthe records from the other INPUT Commands. The merge key is determined bythe FIELDS Operand of the SORTOPTION Command. The default merge key isFilename, Record key, Date and Time.

Three sources of Input are supported by CSI-RECOV:

INPUT JOURNAL - CICS journal files (standard or SMF format)

INPUT BACKUP - Journal Backup files created by CSI-RECOV via theOUTPUT BACKUP Command or batch journalscreated by CSI-JOURNAL.

INPUT DLILOG - Journal logs created by batch DL/I programs, or byCSI-RECOV via the OUTPUT DLILOG Command.

You will need at least one INPUT Command for each source of input, and atleast one INPUT Command for each device type. (disk or tape). The MODNAMEOperand of the INPUT Command is used to specify the I/O module to use forthe specific device type.


Using CSI-RECOV (INPUT Command) Page 65

How to enter

INPUT JOURNAL(ddname[/SYSnnn],...) -1.5|1.6|1.7|2.1 -[APPLID(cccccccc)] -[ATTR(...)] -[MODNAME(CSIRECDJ|cccccccc)] -[NOREPORTS|REPORTS(ALL(FULL|TOTALS|NONE) - SELECTED(FULL|TOTALS|NONE) - )] -[SELECT(...)] -[SORT|NOSORT] -[TITLE('optional report title')] -[WRAP|NOWRAP]

INPUT BACKUP(ddname[/SYSnnn],...) -[APPLID(cccccccc)] -[ATTR(...)] -[MODNAME(CSIRECDB|cccccccc)] -[NOREPORTS|REPORTS(ALL(FULL|TOTALS|NONE) - SELECTED(FULL|TOTALS|NONE) - )] -[SELECT(...)] -[SORT|NOSORT] -[TITLE('optional report title')]

INPUT DLILOG(ddname[/SYSnnn|ESDS],...) -[APPLID(cccccccc)] -[BLKSIZE(1024,SPANNED|VARIABLE)] -[DBERR(STOP|SKIP|SEQERR|DATAERR)] -[ESDS|NOESDS] -[MODNAME(CSIRECDD|cccccccc)] -[NOREPORTS|REPORTS(ALL(FULL|TOTALS|NONE) - SELECTED(FULL|TOTALS|NONE) - )] -[SELECT(...)] -[SORT|NOSORT] -[TITLE('optional report title')]



Explanation

BACKUP(ddname[/SYSnnn],...)JOURNAL(ddname[/SYSnnn],...)DLILOG(ddname[/SYSnnn|ESDS],...)

Required. Specifies which source of input is to beprocessed via this INPUT Command, and provides a listof DLBL/TLBLs to be read, one at a time.

For tape input, an optional SYSnnn can be provided foreach TLBL that will override the SYSnnn specified in theI/O module specified via the MODNAME Operand.

Specify JOURNAL if the input is a CICS journal instandard or SMF format.

Specify BACKUP if the input was created by CSIRECOVby an OUTPUT BACKUP Command or is a BatchJournal created by CSI-JOURNAL, our Batch VSAMJournaling system.

Specify DLILOG if the input was created by CSIRECOVwith an OUTPUT DLILOG Command or is a BatchJournal created by a DL/I application program.

If any of the ddnames are for VSAM ESDS DL/I BatchJournals, specify the ddnames for those journals as:

ddname/ESDS

If this INPUT DLILOG contains more than one ddname,and all ddnames are for VSAM ESDS logs, you canspecify the ESDS Operand as:

INPUT DLILOG(dd1, dd2,...) ESDS

The ESDS Operand is required because CSI-RECOV isunable to distinguish between a VSAM ESDS and aVSAM-managed-SAM dataset.

1.5|1.6|1.7|2.1

Only used for INPUT JOURNAL. Specifies the CICSrelease that created the journal.

CICS 1.5 and CICS 1.6 created the same format journal,therefore either value can be specified.



Journals created by CICS 1.7 and above are NOT thesame as CICS 1.5 and 1.6 journals.

If the wrong value is specified here, the wrong Recordkeys will be extracted from the CICS journal causingincorrect sorting and eventually, message CSIRECOV-56. An attempt will be made by CSI-RECOV to detect ifthis value is incorrectly specified, but unfortunately thiscannot be done until recovering VSAM files.

This Operand is not required and is not used by CSI-RECOV if SMF format journals are used because theCICS release is recorded in the SMF header.

APPLID(cccccccc)

If the AUTO Command has not been specified, then thisOperand is only used for INPUT JOURNAL and INPUTDLILOG. It allows the specification of a CICS APPLID tobe included with each Journal Backup record createdfrom the INPUT Command. This allows selection basedon originating APPLID.

The CICS APPLID is NOT available directly from astandard CICS journal however, it is available from anSMF format CICS journal. Any value specified here willoverride the APPLID found in the SMF journal.

If the AUTO Command has been specified, then thisOperand is also used on the INPUT BACKUPCommand.

This Operand is required if the AUTO Command hasbeen specified. It provides CSI-ARMAN with the Applidof the records contained on the associated INPUT.

ATTR(...)

Allows the specification of VSAM file attributes that areunique to journal records read from this INPUTCommand. Specification of VSAM filename(s) withattributes via this Operand will COMPLETELYOVERRIDE any attributes specified via the ATTRIBUTECommand for the same VSAM filename(s).



The NEWNAME attribute can be used on inputCommands to change the names of specified VSAM filesprior to being sorted and passed to the OUTPUTCommands. Refer to the ATTRIBUTE Command forcomplete format and rules for attribute usage.

BLKSIZE(1024|nnnnn,SPANNED|VARIABLE)

Specify this Operand only if all of the following are true:

• This is an INPUT DLILOG Command.

• One or more of the input ddnames specified for theDLILOG Operand are for VSAM ESDS DL/I logs.

• The format of Your DL/I Log does not match thedefaults of 1024 and SPANNED.

The BLKSIZE Operand provides information CSI-RECOV needs to be able to process your VSAM ESDSDL/I logs.

The first value specifies the maximum block size of yourDL/I log. The current maximum supported by DL/I is1024.

The second value specifies whether your DL/I log isvariable-blocked or spanned-blocked. The currentformat supported by DL/I is spanned-blocked.

Refer to the DLILOG Operand for more informationabout VSAM ESDS DL/I logs.

DBERR(STOP|SKIP|SEQERR|DATAERR)

Specifies the error action that CSI-RECOV shouldperform if a problem is detected processing DL/Ijournal records.

These actions will only affect what CSI-RECOV will dofollowing the error conditions defined by messagesCSIRECOV-65 through CSIRECOV-69.

STOP is the default action. CSI-RECOV willterminate processing if any errors aredetected.

SKIP CSI-RECOV will print the journalrecord in error, and skip the record.



SEQERR CSI-RECOV will ignore sequence errorsdetected with DL/I's log recordsequence numbers. This is not the samesequence checked that is controlled bythe SEQERR Operand of theSORTOPTION Command.

DATAERR CSI-RECOV will ignore errors normallyassociated with messages 68 and 69.

ESDS|NOESDS

Specify this Operand only if both of the following aretrue:

• This is an INPUT DLILOG Command.

• All of the input ddnames specified for the DLILOGOperand are for VSAM ESDS DL/I logs.


Refer to the DLILOG Operand for more informationabout VSAM ESDS DL/I logs.

MODNAME(CSIRECDJ|CSIRECDB|CSIRECDD|cccccccc)

Specifies the name of the I/O module to be used toaccess each input file specified in the DLBL/TLBL list.

CSIRECDJ is the default name for INPUTJOURNAL Commands.

CSIRECDB is the default name for INPUT BACKUPCommands.

CSIRECDD is the default name for INPUT DLILOGCommands.

This Operand is not used if all of the ddnames refer toVSAM ESDS DL/I log datasets.

You can customize your own I/O modules and providethe name via this Operand. Refer to "Customization ofCSI-RECOV" for how to create your own I/O modules.



NOREPORTS|REPORTS(ALL(FULL|TOTALS|NONE) SELECTED(FULL|TOTALS|NONE) )

Specifies the types of summary reporting that CSI-RECOV is to generate for each INPUT Command.

ALL Specifies the format of the SummaryReport showing statistics for "all" inputrecords.

SELECTED Specifies the format of the SummaryReport showing statistics for "selected"input records.

FULL Specifies that a full Summary Report isto be generated, with statistics for inputrecords from each VSAM dataset.

TOTALS Specifies that a Summary Report is to begenerated, with only the totals for theinput records. Individual VSAM datasetstatistics will not be generated.

NONE Specifies that no Summary Report is tobe generated.

Specifying NOREPORTS is the same as specifying:

REPORTS(ALL(NONE) SELECTED(NONE))

Refer to section "Reports Generated by CSI-RECOV" formore information.

SELECT(...)

Allows the specification of selection criteria that areunique to journal records read from this INPUTCommand. Refer to the SELECT Command for completeformat and rules for SELECT Operands.

CSI-RECOV will automatically select all VSAM andDL/I journal records found in the specified INPUTsources unless specifically excluded via the SELECTOperand or Command.



SORT|NOSORT

Specifies whether or not the selected journal recordsfrom this INPUT Command are to be sorted prior tobeing merged with selected records from other INPUTCommands and passed to the OUTPUT Commands.Refer to the SORTOPTION Command for rules on whenSORT should or must be specified.

TITLE('optional report title')

Specifies an optional report title (85 characters max) toappear on the Summary total reports created for thisINPUT Command. Without this title, the total reportscan only be identified by DLBL/TLBL names, and bythe relative position of this INPUT Command withinALL INPUT Commands.

WRAP|NOWRAP

Specifies whether or not processing will extend beyondthe "current" set of journal records on a particular CICSJournal Extent.

The default is NOWRAP which means that CSI-RECOVwill stop reading from a CICS Journal when it finds aDate/Time that is less than the previous journal record.

If you specify WRAP, CSI-RECOV will read all recordsfrom the CICS Journal, ignoring drops in Date/Time.

If you have "Single-Extent" CICS Journals that have thepossibility of wrapping, you should specify WRAP.


Page 72 (OUTPUT Command) Using CSI-RECOV

OUTPUT Command

The OUTPUT Command is used to specify the destination of each of the journalrecords selected from the INPUT Commands. Any number of OUTPUTCommands can be specified. If more than one is specified, each selected journalrecord from each INPUT Command will be directed to the destination definedby each OUTPUT Command, subject to any OUTPUT selection criteria.

Four types of Output destinations are supported by CSI-RECOV:

OUTPUT VSAM - UPDATED VSAM file(s). This is used forforward/backout recovery of VSAM datasets.

OUTPUT BACKUP - Journal Backup files containing VSAM and/or DL/Ijournal records to be saved for a future INPUTBACKUP Command.

OUTPUT DLILOG - DL/I log file to be merged with other DL/I logswith a future INPUT DLILOG Command, or to beused as input to DL/I's change-accum processing.

OUTPUT PRINT - Detail listing of selected journal records.


Using CSI-RECOV (OUTPUT Command) Page 73

How to enter

OUTPUT BACKUP(ddname1[/SYSxxx] [ddname2[/SYSyyy] ]) -[APPLID(cccccccc)] -[FORMAT(SHORT|LONG|REDUCED)] -[MODNAME(CSIRECDB|cccccccc)] -[NULLFILE(RC(0|nnn) NOEOF|EOF)] -[NOREPORTS|REPORTS(FULL|TOTALS|NONE)] -[SELECT(...)] -[TITLE('optional report title')]

OUTPUT DLILOG(ddname1[/SYSxxx] [ddname2[/SYSyyy] ]) -[BLKSIZE(1024,SPANNED|VARIABLE)] -[ESDS|NOESDS] -[MODNAME(CSIRECDD|cccccccc)] -[NULLFILE(RC(0|nnn) NOEOF|EOF)] -[NOREPORTS|REPORTS(FULL|TOTALS|NONE)] -[SELECT(...)] -[TITLE('optional report title')]

OUTPUT PRINT(SYSLST|SYSnnn) -[ATTR(...)] -[FIELDS(...)] -[DATA(32767)|NODATA] -[KEYS(256)|NOKEYS] -[NOREPORTS|REPORTS(FULL|TOTALS|NONE)] -[SELECT(...)] -[TITLE('optional report title')]

OUTPUT VSAM -[ATTR(...)] -[UPDATE|NOUPDATE] -[FORCE|NOFORCE] -[BACKOUT|NOBACKOUT] -NOERRORS|ERRORS( - [PRINT(SYSLST|SYSnnn)] - [DATA(32767)|NODATA] - [KEYS(256)|NOKEYS] - [SELECT(...)] - ) -[NOREPORTS|REPORTS(FULL|TOTALS|NONE)] -[SELECT(...)] -[TITLE('optional report title')]



Explanation

VSAMPRINT(SYSLST|SYSnnn)BACKUP(ddname1[/SYSxxx] [ddname2[/SYSyyy] ])DLILOG(ddname1[/SYSxxx] [ddname2[/SYSyyy] ])

Required. Specifies which type of output destination isto be used for this OUTPUT Command.

For OUTPUT BACKUP and DLILOG, ddname1 isrequired and provides the DLBL/TLBL to be used towrite to the output file. For tape devices, SYSxxx can beprovided to override the SYSnnn specified in the I/Omodule specified via the MODNAME Operand.

ddname2 and SYSyyy can also be supplied to provide a'mirror' image output. Either SYSxxx and/or SYSyyymust be specified for 'mirror' image backups, if theMODNAME specifies an I/O module generated for tapeoutput. If these Operands are omitted, the backup willbe written twice to the same tape.

For OUTPUT PRINT, specify the SYSnnn of the printerto which the selected journal records should be sent. Ifomitted, SYSLST is used.

For OUTPUT VSAM, the PRINT keyword can bespecified within the ERRORS keyword to cause theVSAM error report to be printed on a specific printer. Ifomitted, the error report will be printed on SYSLST.

APPLID(cccccccc)

This Operand is required for the OUTPUT BACKUPCommand if the AUTO Command has been specified. Itprovides CSI-ARMAN with the Applid of the recordscontained on the associated OUTPUT.

ATTR(...)

Allows the specification of VSAM file attributes that areunique to journal records sent to this OUTPUTCommand. Specification of VSAM filename(s) withattributes via this Operand will COMPLETELYOVERRIDE any attributes specified via the ATTRIBUTECommand for the same VSAM filename(s).



Refer to the ATTRIBUTE Command for complete formatand rules for attribute usage.

BLKSIZE(1024|nnnnn,SPANNED|VARIABLE)

Specify this Operand only if all of the following are true:

• This is an OUTPUT DLILOG Command.

• You wish to generate a VSAM ESDS DL/I log.

• The format of Your DL/I Log does not match thedefaults of 1024 and SPANNED.

The BLKSIZE Operand provides information CSI-RECOV needs to be able to process your VSAM ESDSDL/I log.

The first value specifies the maximum block size of yourDL/I log. The current maximum supported by DL/I is1024.

The second value specifies whether your DL/I log isvariable-blocked or spanned-blocked. The currentformat supported by DL/I is spanned-blocked.

Refer to the DLILOG and ESDS Operands for moreinformation about VSAM ESDS DL/I logs.

ESDS|NOESDS

Specify this Operand only if both of the following aretrue:

• This is an OUTPUT DLILOG Command.

• You wish to generate a VSAM ESDS DL/I log.


Refer to the DLILOG and BLKSIZE Operands for moreinformation about VSAM ESDS DL/I logs.



FIELDS(...)

Only used for OUTPUT PRINT Commands. Allows thespecification of a list of field names to be included in thejournal detail report. The fields will be printed in theorder specified.

Some of these fields are not available for DL/I records,and some fields contain different values in VSAMjournal records then in DL/I journal records.

The following field names can be specified:

FILENAME VSAM dataset name or DL/I DBDname

KEY record key field (first 16 bytes)

KEYL record key length

DATE Date activity occurred

TIME Time activity occurred

TRAN CICS Tran ID (VSAM only)

TERM CICS Term ID (VSAM only)

TASK CICS task number (VSAM only)

FUNC CICS file control function

RECL record length

JBLK Journal block number for VSAM, orDL/I log record sequence number

JREC Journal record number in block(VSAM only)

JID Journal ID

APPLID CICS APPLID

SRCE Source of journal record"FC" CICS VSAM"BJ" CSI-JOURNAL"DB" DL/I

DBID File ID of the physical dataset withinthe DBD name. (DL/I only)

DBLOGTYPE DL/I internal record type (hex)

REC# Relative record of the selected recordsbeing output from CSI-RECOV



The default printed report will contain:

FIELDS ( -REC# -FILENAME -DATE -TIME -TERM -TRAN -TASK -FUNC -RECL -KEYL -KEY -

)

FORMAT(SHORT|LONG|REDUCED)

Only used for OUTPUT BACKUP. Specifies the backuprecord format to be generated.

The default is SHORT, which will generate the smallestrecords without requiring both "before" and "after"images.

FORMAT(REDUCED) will generate journal backuprecords that contain only the "differences" between the"before" and "after" images. This options requires thatboth "before" and "after" images are journaled, and thethe input is SORTED using the standard CSI-RECOVsorting sequence. If you specify REDUCED, and theinput is not sorted, or both "before" and "after" imagesare not present, CSI-RECOV will generate aFORMAT(SHORT) journal backup.

If you intend to read the CSI-RECOV backup files byCOBOL application programs, you may want to specifyFORMAT(LONG).

Refer to Appendix B for the formats generated by eachoption.

MODNAME(CSIRECDB|CSIRECDD|cccccccc)

Only used for OUTPUT BACKUP and DLILOG.Specifies the name of the I/O module to be used toaccess the output file(s) specified by ddname1 andddname2.



If omitted, module CSIRECDB will be used for OUTPUTBACKUP and module CSIRECDD will be used forOUTPUT DLILOG.

You can customize your own I/O modules and providethe name via this Operand. Refer to "Customization ofCSI-RECOV" for creating your own I/O modules.

This Operand is not used if the ESDS Operand isspecified for an OUTPUT DLILOG.

NULLFILE(RC(0|nnn) NOEOF|EOF)

Only used for OUTPUT BACKUP and DLILOG.Specifies the actions, if any, that CSI-RECOV shouldtake when no input records have been selected foroutput.

RC CSI-RECOV can set a special JobstepReturn/Condition Code. By default, noReturn Code will be set. If more than oneOUTPUT BACKUP or DLILOG has beenspecified with the RC option, and more thanone OUTPUT BACKUP or DLILOG isempty, when CSI-RECOV completes itsprocessing, it will return to VSE with thelargest of the RC values.

EOF CSI-RECOV can force an end-of-file. IfNOEOF is specified, or allowed to default,CSI-RECOV will not open an output fileunless at least one record will be written toit.

NOREPORTS|REPORTS(FULL|TOTALS|NONE)

Specifies the type of summary reporting that CSI-RECOV is to generate for each OUTPUT Command.

FULL Specifies that a full Summary Report isto be generated, with statistics foroutput records from each VSAMdataset.

TOTALS Specifies that a Summary Report is to begenerated, with only the totals for theoutput records. Individual VSAMdataset statistics will not be generated.




Specifying NOREPORTS is the same as specifyingREPORTS(NONE)


SELECT(...)

Allows the specification of selection criteria that areunique to this OUTPUT Command. The SELECTOperand can also be specified within the ERRORSspecification to select which VSAM errors should causejournal records in error to be printed. Refer to theSELECT Command for complete format and rules forSELECT Operands.

TITLE('optional report title')

Specifies an optional report title (85 character max) toappear on the Summary total reports created for thisOUTPUT Command. This title is also used for thejournal record list produced by an OUTPUT PRINTCommand and any error report produced by anOUTPUT VSAM Command. Without this title, thereports can only be identified by DLBL/TLBL names,and by the relative position of this OUTPUT Commandwithin ALL OUTPUT Commands.

DATA(32767)|NODATA

Specifies the maximum number of bytes of JournalRecord data to be printed.

For OUTPUT PRINT, the default is NOT to print thejournal data records.

For the ERRORS keyword within the OUTPUT VSAM,the default is to print the full journal data records.

KEYS(256)|NOKEYS

Specifies the maximum number of bytes of journal datarecord keys to be printed.

For OUTPUT PRINT, the default is to print the first 16bytes of each record key.



For the ERRORS keyword within the OUTPUT VSAM,the default is to print the full record key.

NOERRORS|ERRORS(...)

Only used for OUTPUT VSAM. Specifies whether or notto print journal data records that cannot be processeddue to an error such as 'no record found'. SpecifyNOERRORS if you do not want errors printed. Thefollowing keywords can be specified as options of theERRORS keyword to further qualify the error printing:

PRINT(SYSLST|SYSnnn) - directs the error printing to aspecific printer.

DATA(32767)|NODATA - specifies whether or not todump the data record in error.

KEYS(256)|NOKEYS - specifies whether or not to dumpthe data record key in error.

SELECT(...) - Provides selection criteria for determiningwhich errors should be printed. Refer to the SELECTCommand for complete format and rules for SELECTOperands.

FORCE|NOFORCEBACKOUT|NOBACKOUTUPDATE|NOUPDATE

Only used for OUTPUT VSAM Commands. Providesglobal defaults for the FORCE, BACKOUT andUPDATE VSAM file attributes for any VSAM file forwhich these attributes were NOT supplied via theATTRIBUTE Command or Operand. Refer to theATTRIBUTE Command for complete format and rulesfor using these attributes.


Using CSI-RECOV (SELECT Command) Page 81

SELECT Command

The SELECT Command is used to specify the criteria to be met to have VSAMand/or DL/I journal records selected from one or more of the specified INPUTCommands and sent to one or more of the specified OUTPUT Commanddestinations.

CSI-RECOV will automatically select all VSAM and DL/I journal records fromall specified INPUT sources unless specifically excluded via the SELECTCommand or Operand.

Selection criteria can be specified in any of several places within CSI-RECOV andwill have different results for each location:

SELECT Command - As a Command, journal records fromevery INPUT Command must 'match' theselection criteria to be selected for Outputprocessing.

INPUT Command Operand - Only journal records from the INPUTCommand containing the SELECTOperand must 'match' the selectioncriteria to be selected for Outputprocessing. They must also 'match' theSELECT Command.

OUTPUT Command Operand - After all Input selection is performed andrequired input is sorted, Output selectioncan be specified to limit output tospecified OUTPUT Commanddestinations.

Input journal records that do not matchany of the OUTPUT Command SELECTOperands will be dropped by CSI-RECOVprior to sorting.


Page 82 (SELECT Command) Using CSI-RECOV

How to enter as a Command

SELECT selection-criteria-Operands

How to enter as an Operand on an INPUT or OUTPUT Command

INPUT . . . SELECT ( selection-criteria-Operands )OUTPUT . . . SELECT ( selection-criteria-Operands )

How to enter selection-criteria-Operands

format 1 - field1(list1) [field2(list2) ...]format 2 - EXCLUDE( field1(list1) [field2(list2) ...] )… -

[INCLUDE( field3(list3) [field4(list4)...] ) …]



Explanation

The 'field(list)' Operands represent the names of the VSAM and/or DL/I journalfields to test and data to be compared. Not all fields are valid for both VSAMand DL/I.

Field name Keywords:

DATASET(string ...) VSAM dataset name or DL/I DBD name(1 - 8 characters)

TRANID(string ...) Tran ID (VSAM only)(1 - 4 characters)

TERMID(string ...) Term ID (VSAM only)(1 - 4 characters)

DATETIME(yyddd, hhmmsst) Compares the Date and Time created againstthe specified values. The Times are onlycompared if the Dates are equal. Only a singleDate and Time can be specified for thisKeyword.

DATE(number ...) Date created (yyddd or yy/ddd)TIME(number ...) Time created (hhmmsst or hh:mm:ss.t)TASK(number ...) Task number (VSAM only)FUNC(string ...) Function (2 characters)

'RO' - read'RU' - read for update'WN' - write new (add)'WU' - write update'WD' - write delete

JID(number ...) Journal ID (01 - 99)APPLID(string ...) APPLID from INPUT Command

(1 - 8 characters)KEYL(number ...) Record key length (1 - 256)KEY(string ...) Record keyRECL(number ...) Record length (1 - 32767)RECORD(string ...) Record dataJBRECL(number ...) Journal backup record lengthJBREC(string ...) Journal backup record formatSRCE(string ...) Source of journal record (2 characters)

'FC' - VSAM from CICS'BJ' - VSAM from CSI-JOURNAL'DB' - DL/I

DBID(string ...) Physical File ID within DBD name(1 - 256). Contains zero for VSAM

DBLOGTYPE(string ...) DL/I's internal log record type(x'2F', x'51', x'50')

VSAMFUNC(string ...) VSAM function causing error (see below)



VSAMSTAT(string ...) VSAM error description (see below)

Field name Relational Operators:

Field name keywords can be prefixed by a 'relational operator' to change themeaning of a 'match' with the strings or numbers in the specified list.

EQ-field(...) (default) match if field is equal to any one value in listNOT-field(...) match if the field is equal to NONE of the values in listNE-field(...) match if the field is not equal to the string or numberGT-field(...) match if the field is greater than the string or numberGE-field(...) match if the field is greater than or equal to the string or

numberLT-field(...) match if the field is less than the string or numberLE-field(...) match if the field is less than or equal to the string or

number

Format 1 Selection criteria:

• Any number of 'field(list)' Operands can be specified.

• If more than one 'field(list)' Operand is specified, ALL fields must be'matched' for the journal record to be selected.

Format 2 Selection criteria:

• One or more format 1 selection criteria lists can be combined under'INCLUDE' and/or 'EXCLUDE' Operands.

• Any number of INCLUDE and/or EXCLUDE Operands can be used, in anysequence. They are processed in the sequence specified.

• If only EXCLUDE Operands are specified, then all journal records areselected unless specifically excluded. If one or more INCLUDE Operands arespecified, then NO journal records are selected unless at least one INCLUDEOperand is 'matched'.



(list) formats and rules:

• Selection 'lists' can contain any number of data values to be tested againstthe journal record 'field'. If more than one value is specified, 'matching' anyONE value 'matches' the list.

• Data values can be 'numbers' or 'strings' depending on the 'field' being used.Refer to the "Field name Keyword" list above.

• Any or all Data values within a 'field' list can be qualified by specifying a'format 2' selection criteria.

field1( value1 (INCLUDE ( field (list) …) …) value2 …)

If 'value1' matches the test for 'field1' then the format 2 selection criteriaspecified following value 1 will be tested, and if that selection criteria'matches', then the 'field1' list is 'matched'. If the format 2 selection criteriafor 'value1' does NOT match, then 'value1' is considered NOT a match and'value2' will then be tested.

Format 2 selection criteria can be nested up to a limit of 30 '(' from the start ofthe Command containing the select Operand(s).

Rules for numbers as values:

• 'numbers' cannot contain commas or periods, but can be preceded by a '+' or'-'. (See special rules for DATE and TIME values).

• 'numbers' must be specified in the exact format defined for the 'field' beingused. Refer to the "Field name Keyword" list above.

Rules for DATE and TIME keyword numbers:

• dates can be specified as either yyddd or yy/ddd. If the value is preceded byeither a '+' or '-' it is assumed to be an adjustment from the 'current' systemdate. Example - if today is 87/001 and DATE(+10) is entered, thenDATE(87/011) is used. If DATE(+1/000) is entered, then DATE(88/001) isused.

• times can be specified as either hhmmsst or hh:mm:ss.t. Portions not enteredare assumed to be zero. Example - if TIME(12:30) is entered, thenTIME(12:30:00.0) is used.



Rules for strings as values:

• 'strings' can be any character string. If it contains any blanks, commas,quotes or parenthesis, enclose the string in single quotes. If the stringcontains any quotes, specify them as (2) single quotes.

• 'strings' can contain special 'generic' operators.

'*' represents ANY number of characters.

'+' represents ANY single character.

If you need to specify a string with an '*' or '+' and you want to test for thosecharacters, specify the string as - C'string'

• 'strings' can be specified as Hexidecimal values - X'hhhhhhhh'.

• 'strings' can be specified such that they represent a portion of the Journal'field' by specifying them in the following format:

string/offset/length

where 'offset' is the number of bytes from the start of the 'field', relative tozero, and 'length' is the number of bytes to be tested. If only 'offset' isspecified, the length of the 'string' is used for 'length'.



Special Fields VSAMSTAT and VSAMFUNC:

Two special fields 'VSAMSTAT' and 'VSAMFUNC' have been provided to allowspecial selection processing at the 'ERRORS' Operand of the OUTPUT VSAMCommand. These fields will NOT test properly if used for selection in any otherCommands.

These fields can be used to test for certain error conditions that you may notwant to have printed. An example is 'DUPLICATE RECORD' during an ADD,which can occur if application programs do not issue a READ prior toattempting the add.

VSAMSTAT can be tested for any of the following strings:

'DUPLICATE RECORD''NOT FOUND''WRONG RBA FOR WN''VSAM SYSTEM ERROR'

VSAMFUNC can be tested for any of the following strings:

'RO' - read'RU' - read for update'WN' - write new (add)'WU' - write update'WD' - write delete'LDRD' - empty file access

The required combinations of VSAMSTAT and VSAMFUNC can be determinedby running a sample OUTPUT VSAM with the NOUPDATE option andchecking the "VSAM Output Error" report for the error conditions that you maynot care to see in a production recovery.



Abbreviations and Alias names:

Many of the keywords and field names used in the SELECT Command can beentered in more than one format. The following table provides the standardname along with all of the variations:

Keyword VariationsDATASET FILEEXCLUDE X, EINCLUDE SELECT, S, IKEY RIDFLDKEYL KEYLENGTHRECL RECLENGTHRECORD RECSELECT INCLUDE, S, ITASK TASKIDTERMID TERMTRANID TRAN, TRANSID



SELECT Command Examples:

Assume that CICS datasets 'FILEA', 'FILEB' and 'FILEC' are to be recoveredexcept for the 'FILEC' activity created by CICS Tranids 'XXXX', 'YYYY' and'ZZZZ'. Only updates made on or after 86/001 and before 86/004 at 12:01:00.0are to be selected.

Each of the following examples will produce the same result:

EXAMPLE 1

SELECT -INCLUDE( - GE-DATE(86001) - LE-DATETIME(86004, 1201000) - DATASET(FILEA - FILEB - FILEC(EXCLUDE(TRANID(XXXX YYYY ZZZZ))) - ) - )

EXAMPLE 2

SELECT -INCLUDE( - GE-DATE(86001) - LE-DATE(86003 86004(INCLUDE(LE-TIME(1201000)))) - DATASET(FILEA - FILEB - FILEC(EXCLUDE(TRANID(XXXX YYYY ZZZZ))) - ) - )



EXAMPLE 3

SELECT -EXCLUDE( - DATASET(FILEC) - TRANID(XXXX YYYY ZZZZ) - ) -EXCLUDE( - EQ-DATE(86004) - GT-TIME(1201000) - ) -INCLUDE( - GE-DATE(86001) - LE-DATE(86004) - DATASET(FILEA FILEB FILEC) - )


Using CSI-RECOV (SORTOPTION Command) Page 91

SORTOPTION Command

The SORTOPTION Command is used to specify the sequence of journal records,and to tailor the parameters that are passed to your installation's sort program.The SORTOPTION Command can also be used to force all input files to besorted.

Only one SORTOPTION Command can be specified. If more than one isspecified, an error will be generated.

The FIELD Operand of the SORTOPTION Command can be specified to controlthe sequence for sorting and sequence checking. The default sequence used byCSI-RECOV is:

• Dataset/DBD name• DL/I Physical File ID(x'00' for VSAM)• DL/I log record type (x'00' for VSAM)• Record key• Date created• Time created• CICS Journal Block number or DL/I internal sequence number• CICS Journal Record number within block (VSAM only)

The SORTOPTION Command is primarily used to provide options to be usedfor sorting and sequence checking.

Unless the SORTALL Operand is specified, it does NOT cause sorting to occur.To specify sorting for individual input files, refer to the SORT Operand of theINPUT Command.

When to use SORT

Sorting in default sequence is REQUIRED in the following situations ...

• When the BACKOUT or NOUPDATE attribute options are specified.

• When the FORMAT(REDUCED) Operand is specified.

• When your journals are a wrap-around type.

• When you are merging inputs via multiple INPUT Commands.


Page 92 (SORTOPTION Command) Using CSI-RECOV

• When using the OUTPUT DLILOG Command to generate a log file to beinput to the DL/I recovery program. Sorting is not required if the input hasalready been sorted by CSI-RECOV in a prior job.

• Any time that you cannot be sure that the journal data being read is in atleast chronological sequence.

Sorting by the default sequence will usually improve recovery performancebecause CSI-RECOV will only update the VSAM files once for each record keychange. Therefore, if you have a file with many updates to the same records,specifying the SORTOPTION SORTALL Command or the SORT Operand on theINPUT Command(s) will reduce the number of VSAM I/Os.

How to enter

SORTOPTION -[SORTALL] -[DEFAULT|DLICUM|DLIRECV|CHRONO|AIX] -[FIELDS(...)] -[MAXKEY(232|n)] -[WORK(DA|string)] -[SORTRECL(8192|n)] -[RECORDPARM('string')] -[SORTPARM('string')] -[OPTIONPARM('string')] -[NOREPORTS|REPORTS(ALL(FULL|TOTALS|NONE) - SELECTED(FULL|TOTALS|NONE) - )] -[SEQERROR( - [STOP(n)|NOSTOP] - [PRINT(0|n)] - )]

Explanation

SORTALL

Specifies that all selected journal records from ALLINPUT Commands are to be sorted. If omitted, only theselected journal records from INPUT Commandscontaining the SORT Operand will be sorted.

DEFAULT|DLICUM|DLIRECV|CHRONO|AIX

Specifies the sequence that CSI-RECOV will use for thesort. This Operand is ignored if the FIELDS Operand isalso specified.

DEFAULT



DLICUM Either of these names can be used to usethe default sort sequence. This sequenceis valid for a standard VSAM recovery,or for generating a DLILOG to be usedfor change accum processing:

• Dataset/DBD name• DL/I Physical File ID• DL/I log record type• Record key• Date created• Time created• CICS Journal Block number or DL/I

internal sequence number• CICS Journal Record number within

block (VSAM only)

AIXCHRONO Either of these names should be

specified if you want to perform arecovery in chronological sequence.

This is required if you are performing arecovery that includes updates via anAlternate Index Path:

• Date created• Time created• CICS Journal Block number• CICS Journal Record number within

block

DLIRECV This sequence should be specified if youare generating an OUTPUT DLILOG tobe used for DL/I recovery processing:

• DBD name• Date created• Time created• DL/I internal sequence number



FIELDS(...)

Allows the specification of a list of field names whichrepresent the desired sorting sequence. Sequencechecking and merging of multiple INPUT files will bebased on this sequence. If SORT is specified for anyINPUT files, the field names specified here will controlthe sort parameter that is passed to your installation'ssort package. The following field names can bespecified:



FILENAME VSAM dataset name or DL/I DBDname

KEY record key field (first 16 bytes)

KEYL record key length

DATE Date activity occurred

TIME Time activity occurred

TRAN CICS Tran ID (VSAM only)

TERM CICS Term ID (VSAM only)

TASK CICS task number (VSAM only)

FUNC CICS file control function

RECL record length

JBLK Journal block number for VSAM, orDL/I log record sequence number

JREC Journal record number in block(VSAM only)

JID Journal ID

APPLID CICS APPLID

SRCE Source of journal record"FC" CICS VSAM"BJ" CSI-JOURNAL"DB" DL/I

DBID File ID of the physical dataset withinthe DBD name. (DL/I only)

DBLOGTYPE DL/I internal record type (hex)

CSI-RECOV will automatically append fields DATE,TIME, JBLK and JREC to the FIELDS list if you do notspecify them. These fields are required to uniquelyidentify sort record segments created as a result of theSORTRECL Operand.



The default sort sequence is:

FIELDS ( FILENAME -DBID -DBLOGTYPE -KEY -DATE -TIME -JBLK -JREC )

MAXKEY(232|n)

Specifies the maximum VSAM key length to allow for inthe sort key. This Operand is only needed if you haveVSAM files with keys greater than 232 bytes. This valuewas chosen because it results in a sort key size of 256bytes which is the maximum allowed with the IBM sortpackage. If you are using the IBM sort and have VSAMkeys greater than 232 bytes long, sorting will not beexact, and the BACKOUT and NOUPDATE functionscannot be used.

WORK(DA|string)

Specifies a string of characters to be used as an overridevalue for the "WORK=" Operand of the SORT parameterthat is internally generated by CSI-RECOV. Check yourSORT manual to determine what to use for thisOperand. The default is:

WORK=DA

The maximum length string allowed is 16 bytes.

SORTRECL(8192|n)

This value is used to limit the length of the recordspassed to your SORT package. If any journal recordsexceed this length, they will be passed to SORT insegments which are re-assembled by CSI-RECOV beforebeing processed by any OUTPUT Commands.

The minimum value allowed is 1000. The maximum isonly limited by your sort package. Normally themaximum will be 32767 or the track capacity of yourdisk.



RECORDPARM('string')

Allows the specification of a complete replacement forthe RECORD Command internally generated by CSI-RECOV and passed to your sort package. For CKD sortwork devices, the record length parameter passed toSORT must not exceed the track capacity. For FBA, itmust not exceed 32767. These limits are based on therequirements of IBM's SM2 sort program. Othervendors' sort programs may have different limits. If youdo not specify this parameter, the default is:

RECORD TYPE=V,LENGTH=nnnnn

where "nnnnn" is the value specified in the SORTRECLOperand. If you specify a different length value here,you should also provide the length via the SORTRECLOperand. The maximum length string allowed is 256bytes.

SORTPARM('string')

Allows the specification of a complete replacement forthe SORT Command internally generated by CSI-RECOV and passed to your sort package. You may needto also specify the FIELD Operand to provide the propersequence checking. The default is:

SORTFIELDS=(7,10,A,19,232,A,275,14,A),FORMAT=CH,WORK=DA


OPTIONPARM('string')

Allows the specification of a complete replacement forthe OPTION Command internally generated by CSI-RECOV and passed to your sort package. The default is:

OPTION PRINT=CRITICAL


NOREPORTS|REPORTS(ALL(FULL|TOTALS|NONE) SELECTED(FULL|TOTALS|NONE) )

Specifies the types of summary reporting that CSI-RECOV is to generate as a result of any input recordsthat are sorted.



ALL Specifies the format of the SummaryReport showing statistics for "all" sortedrecords.

SELECTED Specifies the format of the SummaryReport showing statistics for "selected"sorted records. The sorting process cancause records to be dropped if they aredetermined to be duplicates.

FULL Specifies that a full Summary Report isto be generated, with statistics for sortedrecords from each VSAM dataset.

TOTALS Specifies that a Summary Report is to begenerated, with only the totals for thesorted records. Individual VSAMdataset statistics will not be generated.


Specifying NOREPORTS is the same as specifying:

REPORTS(ALL(NONE) SELECTED(NONE))


SEQERROR(...)

Allows the specification of options to be used by CSI-RECOV in handling sequence errors (not in the sortingsequence defined by FIELDS above). The default is todisplay message CSIRECOV-32 and terminateprocessing. The STOP and PRINT keywords can be usedto alter that processing.



STOP(n)|NOSTOP

Sub-Operand of SEQERROR keyword. Allows thespecification of whether or not to stop processing if aninput sequence error is detected. You can optionallyspecify how many sequence errors you will acceptbefore stopping, by providing the count as a sub-Operand of the STOP keyword. The default will be NOTto stop on sequence errors if only one INPUT Commandis specified, and no OUTPUT VSAM Commands arespecified. If more than one INPUT Command or anyOUTPUT VSAM Commands are specified, the defaultwill be to stop on the first sequence error (eg. STOP(1) ).

PRINT(0|n)

Sub-Operand of SEQERROR keyword. Allows you tospecify how many sequence errors should be printed.The first (nnn) errors will be printed. This Operand willonly function correctly if the STOP keyword has a countequal to or greater than the PRINT count. The printingwill be accomplished by generating messageCSIRECOV-32 on SYSLST.


Page 100 (ATTRIBUTE Command) Using CSI-RECOV

ATTRIBUTE Command

The ATTRIBUTE Command is used to specify optional processing options forindividual VSAM datasets. These options can be supplied via an ATTRIBUTECommand, which will apply to all INPUT and OUTPUT Commands, or they canbe supplied via ATTR Operands of individual INPUT and/or OUTPUTCommands.

Any VSAM file attributes supplied via the ATTR Operand of an INPUT orOUTPUT Command will COMPLETELY OVERRIDE all attributes specified viathe ATTRIBUTE Command for the same VSAM dataset name(s).

How to enter as a Command

ATTRIBUTE ddname1[/password](attribute-Operands) -[ ddname2[/password](attribute-Operands) ]

How to enter as an Operand on an INPUT or OUTPUT Command

ATTRIBUTE ( - ddname1[/password](attribute-Operands) -[ ddname2[/password](attribute-Operands) ... - ] )

How to enter attribute-Operands

[FIXED|VARIABLE] -[EMPTY] -[UPDATE|NOUPDATE] -[FORCE|NOFORCE] -[BACKOUT|NOBACKOUT] -[DOSISAM] -[NEWNAME(cccccccc)] -[DELETE(offset,string)] -


Using CSI-RECOV (ATTRIBUTE Command) Page 101

Explanation:

ddname

VSAM dataset name to which the attribute Operandsapply. This must be the same name used in the CICS FileControl Table (FCT), but it is not checked by CSI-RECOV.

password

VSAM dataset password. Only required for OUTPUTVSAM Commands.

FIXED|VARIABLE

Only used by OUTPUT VSAM Commands. Specifieswhether the VSAM dataset has been defined in the CICSFile Control Table (FCT) as fixed or variable format.This determines whether or not the CICS journal recordshave been prefixed by an 'LLBB' field. If this Operand isomitted, CSI-RECOV will attempt to automaticallydetermine whether the 'LLBB' field is present. In raresituations, CSI-RECOV will be unable to determine thecorrect format. This will cause most of the OUTPUTVSAM processing to be rejected in error due to wrongrecord lengths, or 'NO RECORD FOUND' conditions. Ifthis occurs, you must determine from your CICS FCTwhich of these options to specify.

EMPTY

Only used by OUTPUT VSAM Commands. Specifieswhether the VSAM dataset has been defined in the CICSFile Control Table (FCT) as an 'empty' or 'reusable' file.This will cause CSI-RECOV to open the VSAM file inoutput only mode with the reset option to delete anyexisting records. When the first non-add journal recordis encountered, the VSAM file will automatically beclosed and re-opened in update mode.

If this Operand is omitted, the file will automatically beplaced in 'output only' mode if it is determined that thefile is already EMPTY. Otherwise, it will be opened inupdate mode.


Page 102 (ATTRIBUTE Command) Using CSI-RECOV

UPDATE|NOUPDATE

Only used by OUTPUT VSAM Commands. Specifieswhether the VSAM dataset should be updated by CSI-RECOV. If NOUPDATE is specified, a simulation runwill be made to determine if any errors would occur ifthe VSAM datasets were updated. CSI-RECOV must beable to open the VSAM datasets with update intent, todetermine the type of datasets, and to verify certainfunctions. The input must be SORTED if this option isselected.

FORCE|NOFORCE

Only used by OUTPUT VSAM Commands. Specifieswhether or not CSI-RECOV should attempt to correcterrors encountered during the recovery process. IfFORCE is specified, the following correction functionswill be performed:

• If a CICS 1.7 journal is input with a 1.5 or 1.6keyword on the INPUT JOURNAL Command, theproper key value will be extracted for 'WD'functions, however, the records will NOT be in thecorrect sort sequence which could cause problemsfor the BACKOUT and NOUPDATE attributeoptions.

• An error message will not be printed when an addto an ESDS file results in an RBA that is differentthan the RBA found in the CICS Journal record.

• A 'duplicate record' error on an add will beconverted to an update.

• A 'no record found' error on an update will beconverted to an add.

• A 'no record found' error on a delete will notgenerate an error.


Using CSI-RECOV (ATTRIBUTE Command) Page 103

BACKOUT|NOBACKOUT

Only used by OUTPUT VSAM Commands. Specifieswhether CSI-RECOV should be in a 'forward' or'backward' recovery mode. If BACKOUT is specified,CSI-RECOV will use the "RU" (read for update, or"before" image) journal records created by CICS tobackout or "undo" the changes made to VSAM records.This is not the same as Dynamic Transaction Backout,and cannot be used to backout the activity of 'in-flight'transactions after a CICS abend unless YOU candetermine through SELECT parameters which journalrecords to use for the backout. The journal input must beSORTED in the default sequence if this option isselected.

DOSISAM

Only used by OUTPUT VSAM Commands. Thisattribute must be specified if the VSAM dataset has beendefined in the CICS File Control Table (FCT) with aRECFORM of "DOSISAM".

NEWNAME(cccccccc)

Only used by INPUT Commands. Specifies a newdataset name to be used for all journal records selected.This can be used if you have more than one CICS FileControl Table (FCT) entry referencing the same VSAMdataset. This happens when an empty file is processedthrough one FCT name for initial adds and through adifferent FCT name for the updates. When aNEWNAME is supplied, the input record's dataset nameis changed prior to input to the SORT, so that therecords will be sorted together and passed to theOUTPUT Commands as a single dataset name.

DELETE(offset,string)

Only used by OUTPUT VSAM Commands. Converts allDELETE requests for the specified VSAM dataset toUPDATE requests. Prior to the update, the 'string'specified as the second Operand will be moved to eachdata record at the 'offset' specified in the first Operand.The 'offset' is relative to zero. If the 'string' length plus'offset' extends beyond the end of the data record, anerror is generated. This Operand can be useful if aBACKOUT of an ESDS file is desired. 'string' can be anyformat character string: string, 'string with blanks',X'hexidecimal data'.


Page 104 (AUTO Command) Using CSI-RECOV

AUTO Command

The AUTO Command is used to activate the Automatic Recovery Interfacebetween CSI-RECOV and CSI-ARMAN.

Refer to the Installation and Operations Guide of CSI-ARMAN for informationon the requirements for using this Command.

The CSI-ARMAN partition must be active when executing any CSI-RECOVjobstream containing this Command.

How to enter

AUTO


Using CSI-RECOV (Reports) Page 105

Reports generated by CSIRECOV

CSI-RECOV produces several types of reports, which are controlled by theCommands and Operands you provide. Summary reports are generatedautomatically for input, output, and sort processing. Journal detail reports aregenerated by OUTPUT PRINT Commands. During actual VSAM datasetrecovery, an error report is generated if any errors occur.

The following list shows when each type of report is produced:

• PARAMETER EDIT REPORT: This report is always printed, and lists allinput Commands, as well as any related error messages.

• OUTPUT PRINT REPORT: If you specify one or more OUTPUT PRINTCommands, this report is generated for each OUTPUT PRINT Command.

• INPUT PROCESSING SUMMARY: Two summaries are produced for eachfile read by each INPUT Command. The first shows totals of all journalrecords read, and the second shows totals for the records which met theselection criteria. If any sorting is requested, two summaries are alsoproduced for all the records which passed through the sort. Two additionalsummaries are printed showing the combined totals for all INPUTCommands. The REPORTS Operand of the INPUT and SORTOPTIONCommands can be used to control the generation and format of these InputProcessing Summaries.

• OUTPUT PROCESSING SUMMARY: Each OUTPUT Command producesa summary of all records selected for that output. The REPORTS Operand ofthe OUTPUT Command can be used to control the generation and format ofthis summary.

• VSAM OUTPUT ERROR REPORT: If any errors occur during theprocessing of an OUTPUT VSAM Command, this report describes the error.The amount of detail is determined by the ERRORS(...) Operand on theOUTPUT VSAM Command.


Page 106 (Reports) Using CSI-RECOV

Each report indicates exactly which input or output it pertains to. In addition, theTITLE Operand of the INPUT and OUTPUT Commands allows you to specify atitle to be put on each report associated with the INPUT or OUTPUT Command.

If more than one detail report (OUTPUT PRINT or OUTPUT VSAM) isgenerated, you should direct each output to separate print files by specifying oneof the following Command formats:

OUTPUT PRINT(SYSLST|SYSnnn)OUTPUT VSAM ERRORS(PRINT(SYSLST|SYSnnn))

If more than one OUTPUT report is generated using the same print file, thereports will be intermixed. All summary reports are generated after all outputprocessing has been completed, so they will not interfere with the detail reports.

Report Formats

The reports are presented here in the same sequence as they are printed. Theformat of the various reports is shown, as well as the relationship between theinput Operands and the resulting reports.

All reports contain the CSI-RECOV release number, description of the report,time of day, and page number on the first line. The second line shows the currentdate in two formats, MM-DD-YY and YY/DDD, and the report TITLE.

The following pages describe the contents of the reports in detail.



Parameter Edit Report

This report shows all input Commands processed by CSI-RECOV, along withany syntax related error messages.

CSI-RECOV RELEASE x.xx CICS/VS FORWARD RECOVERY SYSTEM - PARAMETER EDIT REPORT 10.38 PAGE 101-07-87 87/007

/* - READ JOURNAL BACK-UP FILE NAMED 'BACKUP', AND SELECT - RECORDS FOR TRANSACTION CODE 'CSI7' WHICH WERE WRITTEN - TO THE JOURNAL BETWEEN 21:20:00.0 AND 21:26:40.8 - */

INPUT BACKUP (BACKUP) - SELECT (TRAN(CSI7) GT-TIME(2120000) LE-TIME(2126408))

/* - READ THE CICS JOURNAL FILE NAMED 'JOURNAL', AND SELECT - RECORDS WHICH AFFECT ANY DATA FILE WITH A NAME CONTAINING - A 'K', FOLLOWED BY ANY ONE CHARACTER, FOLLOWED BY A 'D' - IF THE JOURNAL RECORD WAS WRITTEN ON DAY 86/342. - SORT THE RECORDS, AND RENAME DATA FILE RLNKSDS TO RLNKSRU - */

INPUT JOURNAL (JOURNAL) - SELECT (FILE(*K+D*) - EQ-DATE(86342) - ) - SORT - ATTRIBUTE(RLNKSDS(NEWNAME(RLNKSRU)))

/* - FROM ALL RECORDS WHICH MEET THE INPUT SELECTION CRITERIA, - EXCLUDE THOSE WHICH WERE CREATED BY CICS READ FUNCTIONS. - */

SELECT EXCLUDE(FUNC(RO RU))

/* - OUTPUT A REPORT SHOWING ALL RECORDS WHICH PASSED INPUT - AND GENERAL SELECTION, EXCEPT THOSE WHICH WERE CREATED - AT A TIME OF DAY LESS THAN 09:31:13. - PUT THE TITLE 'CSIRECOV VERIFICATION LIST' ON THE - DETAIL REPORT, AND ON THE SUMMARY REPORT FOR THIS OUTPUT. - PRINT THE FIRST 100 BYTES OF DATA FROM EACH VSAM RECORD. - */

OUTPUT PRINT TITLE('CSIRECOV VERIFICATION FILE LIST') - DATA(100) - SELECT( - EXCLUDE( - LT-TIME(0921130) - ) - )



Output Print Report

The records which pass all selection criteria are listed in this report. Note that thesecond title line in the heading was produced by the TITLE Operand in theOUTPUT PRINT Command. The contents of the journal records are printedbecause of the DATA Operand. If multiple OUTPUT PRINT REPORTS aregenerated, the RECORD number on the various reports can be used to relateindividual journal records across reports.

The FIELDS Operand can be used to specify which fields from the journal are tobe printed.

CSI-RECOV RELEASE x.xx CICS/VS FORWARD RECOVERY SYSTEM - OUTPUT PRINT REPORT 10.38 PAGE 201-07-87 87/007 CSIRECOV VERIFICATION FILE LIST

RECORD FILENAME DATE TIME TERM TRAN TASK# FUNC REC LEN KEY LEN KEY FIELD (1ST 16 BYTES)

1 RLNESDS 86/147 21.26.407 CSI2 CSI7 46 WN 104 4 00000464

RECORD 0000 00680000 F0F561F2 F761F8F6 F0F2F1F2 F6F4F040 D9C5C3D6 D9C440E6 D9C9E3E3 *....05/27/860212640 RECORD WRITT* 0020 C5D540C2 E840C3C9 C3E24040 40404040 40404040 40404040 40404040 40404040 *EN BY CICS * 0040 40404040 40404040 40404040 40404040 40404040 40404040 40404040 40404040 * * 0060 40404040 * *

2 RLNESDS 86/147 21.26.408 CSI2 CSI7 46 WN 104 4 000004C8


3 RLNESDS 86/147 21.26.408 CSI2 CSI7 46 WN 104 4 0000052C


4 RLNKSRU 86/342 09.21.159 L043 CSIV 704 WD 0 4 00000001

5 RLNKSRU 86/342 09.21.161 L043 CSIV 704 WD 0 4 00000002

6 RLNKSRU 86/342 09.21.164 L043 CSIV 704 WD 0 4 00000003

7 RLNKSRU 86/342 09.21.166 L043 CSIV 704 WD 0 4 00000004

8 RLNKSRU 86/342 09.21.169 L043 CSIV 704 WD 0 4 00000005

9 RLNKSRU 86/342 09.21.177 L043 CSIV 704 WU 40 4 000003E9

RECORD 0000 00280000 000003E9 000F0001 00020003 00040005 00060007 00080009 000A000B *.......Z........................* 0020 000C000D 000E000F *........ *

10 RLNKSRU 86/342 09.21.174 L043 CSIV 704 WD 0 4 000003EA

11 RLNKSRU 86/342 09.21.131 L043 CSIV 704 WN 50 4 000003EC

RECORD 0000 00320000 000003EC 0014001F 00200021 00220023 00240025 00260027 00280029 *................................* 0020 002A002B 002C002D 002E002F 00300031 0032 *.................. *

12 RLNKSRU 86/342 09.21.152 L043 CSIV 704 WN 20 4 000003ED

RECORD 0000 00140000 000003ED 00050033 00340035 00360037 *.................... *

NUMBER OF JOURNAL RECORDS PRINTED = 12



Summary Reports

All summary reports have the same basic format. Their purpose is to list recordcounts for each VSAM and DL/I dataset processed. The dataset accumulatorsare dynamically allocated as new dataset names are encountered in the inputfiles (INPUT BACKUP, INPUT DLILOG or INPUT JOURNAL). The summaryreports corresponding to INPUT or OUTPUT Commands each have a detaileddescription of the INPUT or OUTPUT which generated the summary. Whenpresent, this description starts on the fourth line of the page.

Each summary contains a line, "INDIVIDUAL CICS FILE STATISTICS ...", thattells you which records are counted in the summary. Following this line are thecolumn headings for the body of the report.

Two lines are printed for each VSAM and DL/I dataset, to show the date/timeof the oldest and newest journal records, followed by the statistics for thedataset, and any attributes specified via an ATTRIBUTE(...) Operand whichapply to that dataset.

DL/I datasets are printed in DBDNAME/ID format, where the ID is the PhysicalFile ID within DBD name.

The REPORTS Operand of the INPUT, OUTPUT, and SORTOPTION Commandscan be used to control the format and generation of the Summary Reports.

ALL/SELECTED Reports

The Input Summary Reports can be generated as either one or two reports. Thefirst report contains statistics for "all" records read from the input, the secondreport contains statistics for records that have been "selected" for outputprocessing. If all records from an input are selected for output processing, the"selected" report will not be generated, and the "all" report will be generated as:

"FOR ALL/SELECTED RECORDS ..."

instead of

"FOR ALL RECORDS ..."



INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FROM THIS INPUT BACKUP

This is the first of two reports generated by the INPUT BACKUP Command. Itgives totals of all records read from the journal backup file named 'BACKUP'.

CSI-RECOV RELEASE x.xx CICS/VS FORWARD RECOVERY SYSTEM - INPUT PROCESSING SUMMARY 10.38 PAGE 301-07-87 87/007

INPUT 1 OF 2 TYPE ..... BACKUPDDNAME 1 OF 1 .......... BACKUPBACKUP DATASET NAME .... CSI.TEST.JOURNAL.BACKUP

INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FROM THIS INPUT BACKUP -------------------------------------------------------------

FILENAME/ID FIRST LAST TOT-RECS AVG-SIZE READ READ-UPD UPDATES ADDS DELETES ATTRIBUTES-----------

RLNESDS 86/107 86/295 95 85 14 2 4 75 0 12.55.123 11.41.104

RLNKSDS 86/107 86/295 54 24 15 11 1 15 12 12.55.092 11.41.097

RLNKSFL 86/107 86/295 54 20 15 11 2 15 11 12.55.136 11.41.128

CSIPANL 86/142 86/156 5 1,989 4 1 0 0 0 12.05.362 10.42.204

RLNRRDS 86/107 86/295 60 30 27 1 3 27 2 12.55.128 11.41.117

*TOTAL* 86/107 86/295 268 83 75 26 10 132 25 12.55.092 11.41.128

The *TOTAL* line gives totals for all CICS datasets listed in this summaryreport.



INDIVIDUAL CICS FILE STATISTICS FOR SELECTED RECORDS FROM THIS INPUTBACKUP

This is the second of two reports generated by the INPUT BACKUP Command.It gives totals of all records, read from the journal backup file named 'BACKUP',which have been selected to go to at least one OUTPUT. If all records are selectedfor output, this report is not generated. (Refer to the "ALL/SELECTED Report "discussed earlier in this section.)


INPUT 1 OF 2 TYPE ..... BACKUPDDNAME 1 OF 1 .......... BACKUPBACKUP DATASET NAME .... CSI.TEST.JOURNAL.BACKUP

INDIVIDUAL CICS FILE STATISTICS FOR SELECTED RECORDS FROM THIS INPUT BACKUP --------------------------------------------------------


RLNESDS 86/147 86/147 3 104 0 0 0 3 0 21.26.407 21.26.408

*TOTAL* 86/147 86/147 3 104 0 0 0 3 0 21.26.407 21.26.408

RECORDS DROPPED VIA INPUT SELECT(S) = 265RECORDS DROPPED VIA SELECT COMMAND(S) = 0RECORDS DROPPED VIA OUTPUT SELECT(S) = 0RECORDS DROPPED THAT WERE DUPLICATES = 0

After the *TOTAL* lines, this report indicates how many records were droppedfor each of the possible types of selection. Even though this report is for anINPUT Command, the number of records dropped because of SELECT andOUTPUT Commands is known.

It also shows the number of records that were dropped because they wereduplicates of journal records from other inputs. This can occur if a CICS journalfile is input to CSI-RECOV more than once without being re-formatted. Theduplicate record check compares the CICS dataset name, record-id field, date,time, physical journal block number, and position of the journal record withinthe block.



INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FROM THIS INPUT JOURNAL

This report summarizes all journal records read from the CICS journal filenamed 'JOURNAL'. Note that the NEWNAME attribute is shown forFILENAME RLNKSDS, which indicates that, after input selection, journalrecords for this CICS file will be treated as coming from FILENAME RLNKSRU.


INPUT 2 OF 2 TYPE ..... JOURNALDDNAME 1 OF 1 .......... JOURNALJOURNAL DATASET NAME ... CICS.JRNL02.TEST

INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FROM THIS INPUT JOURNAL ------------------------------------------------------------


RLNESDS 86/316 86/342 36 26 0 8 8 20 0 12.44.197 09.21.210

RLNKSDS 86/316 86/342 118 25 30 30 4 30 24 NEWNAME(RLNKSRU) 12.44.118 09.21.177

RLNKSFL 86/316 86/342 90 21 15 27 12 21 15 12.44.285 09.21.255

RLNKSRU 86/316 86/342 36 28 0 0 0 36 0 12.17.349 09.21.104

RLNRRDS 86/316 86/342 68 30 28 6 3 28 3 12.44.254 09.21.229

*TOTAL* 86/316 86/342 348 25 73 71 27 135 42 12.17.349 09.21.255

*OTHER* 0 0

TOTAL NUMBER OF JOURNAL BLOCKS READ = 205AVERAGE SIZE OF JOURNAL BLOCKS READ = 157

NUMBER OF TRACKS/FBA CI'S OCCUPIED = 9

After the TOTAL line on this report, the total number of "OTHER" journalrecords is shown. This value represents the journal records contained on theCICS journal that are not processed by CSI-RECOV. Only the following types ofCICS journal records are processed by CSI-RECOV:

• Journal records generated by CICS file control for VSAM datasets thatcontain the JREQ and JID operands in their FCT.

• DL/I journal records containing log-types of x'2F', x'50' and x'51'. These arethe record types required for DL/I forward recovery. CSI-RECOV does notcapture the DL/I records required for DL/I "backout".

This report also gives CICS journal file statistics, which can be used to tune yourjournals, and to determine how much DASD space the journal actually used.



INDIVIDUAL CICS FILE STATISTICS FOR SELECTED RECORDS FROM THIS INPUTJOURNAL:

The selected records from the INPUT JOURNAL Command are summarizedhere. If all records are selected for output, this report is not generated. (Refer tothe "ALL/SELECTED Report " discussed earlier in this section.)


INPUT 2 OF 2 TYPE ..... JOURNALDDNAME 1 OF 1 .......... JOURNALJOURNAL DATASET NAME ... CICS.JRNL02.TEST

INDIVIDUAL CICS FILE STATISTICS FOR SELECTED RECORDS FROM THIS INPUT JOURNAL -------------------------------------------------------


RLNKSDS 86/342 86/342 9 12 0 0 1 2 6 09.21.131 09.21.177

*TOTAL* 86/342 86/342 9 12 0 0 1 2 42 09.21.131 09.21.177


After the *TOTAL* lines, this report indicates how many records were droppedfor each of the possible types of selection. Even though this report is for anINPUT Command, the number of records dropped because of SELECT andOUTPUT Commands is known.

It also shows the number of records that were dropped because they wereduplicates of journal records from other inputs. This can occur if a CICS journalfile is input to CSI-RECOV more than once without being re-formatted. Theduplicate record check compares the CICS dataset name, record-id field, date,time, physical journal block number, and position of the journal record withinthe block.



INDIVIDUAL CICS FILE STATISTICS SUMMARY FOR ALL SORTED INPUT

This report shows how many records were actually sorted. It will include allselected journal records from INPUT Commands which specified the SORTOperand or, if the SORTOPTION ALL Command was specified, it will includeall selected journal records from all INPUT Commands.


INDIVIDUAL CICS FILE STATISTICS FOR ALL SORTED INPUT -------------------------------------------------------------------------------


RLNKSRU 86/342 86/342 9 12 0 0 1 2 6 09.21.131 09.21.177

*TOTAL* 86/342 86/342 9 12 0 0 1 2 6 09.21.131 09.21.177

INDIVIDUAL CICS FILE STATISTICS SUMMARY FOR SELECTED SORTED INPUT

Unless some duplicate records were dropped from the output of the sort, thisreport will not be generated and the "ALL SORTED" report will be generated asan "ALL/SELECTED SORTED" report.


INDIVIDUAL CICS FILE STATISTICS FOR SELECTED SORTED INPUT --------------------------------------------------------------------------


RLNKSRU 86/342 86/342 9 12 0 0 1 2 6 09.21.131 09.21.177

*TOTAL* 86/342 86/342 9 12 0 0 1 2 6 09.21.131 09.21.177




INDIVIDUAL CICS FILE STATISTICS SUMMARY FOR ALL RECORDS FROM ALL INPUTCOMMANDS

This report provides a "grand total" of all journal records read by CSI-RECOV.This report will only be generated if more than one INPUT Command isspecified, or more than one DDNAME is specified in an INPUT Command.


INDIVIDUAL CICS FILE STATISTICS SUMMARY FOR ALL INPUT COMMANDS ---------------------------------------------------------------------


RLNESDS 86/107 86/342 131 69 14 10 12 95 0 12.55.123 09.21.210

RLNKSDS 86/107 86/342 172 24 45 41 5 45 36 12.55.092 09.21.177

RLNKSFL 86/107 86/342 144 21 30 38 14 36 26 12.55.136 09.21.255

RLNKSRU 86/316 86/342 36 28 0 0 0 36 0 12.17.349 09.21.104

CSIPANL 86/142 86/156 5 1,989 4 1 0 0 0 12.05.362 10.42.204

RLNRRDS 86/107 86/342 128 30 55 7 6 55 5 12.55.128 09.21.229

*TOTAL* 86/107 86/342 616 50 148 97 37 267 67 12.55.092 09.21.255

INDIVIDUAL CICS FILE STATISTICS SUMMARY FOR SELECTED RECORDS FROM ALLINPUT COMMANDS

All journal records passed to CSI-RECOV output processors are summarizedhere. If all input records are selected for output, this report is not generated.(Refer to the "ALL/SELECTED Report " discussed earlier in this section.)


INDIVIDUAL CICS FILE STATISTICS SUMMARY FOR SELECTED INPUT COMMANDS ----------------------------------------------------------------


RLNESDS 86/147 86/147 3 104 0 0 0 3 0 21.26.407 21.26.408

RLNKSRU 86/342 86/342 9 12 0 0 1 2 6 09.21.131 09.21.177

*TOTAL* 86/147 86/342 12 35 0 0 1 5 6 21.26.407 09.21.177



INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FOR THIS OUTPUT PRINT

Only one summary report is produced for each OUTPUT Command (BACKUP,PRINT, VSAM, DLILOG), because only records matching all appropriateselection criteria are passed to the output processors.

If an OUTPUT PRINT(...) or OUTPUT VSAM ERRORS(PRINT(...)) specified aseparate print file, the corresponding output processing summary will be routedto that print file in addition to being generated on the same print file as the inputprocessing summaries.

CSI-RECOV RELEASE x.xx CICS/VS FORWARD RECOVERY SYSTEM - OUTPUT PROCESSING SUMMARY 10.38 PAGE 1101-07-87 87/007

OUTPUT 1 OF 1 TYPE ..... PRINT

INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FOR THIS OUTPUT PRINT --------------------------------------------------------------


RLNESDS 86/147 86/147 3 104 0 0 0 3 0 21.26.407 21.26.408

RLNKSRU 86/342 86/342 9 12 0 0 1 2 6 09.21.131 09.21.177

*TOTAL* 86/147 86/342 12 35 0 0 1 5 6 21.26.407 09.21.177



VSAM Output Error Report

The generation of this report is determined by the ERRORS Operand on theOUTPUT VSAM Command, and the occurrence of a VSAM dataset error. Sinceapparent "errors" may be caused by the file processing techniques used by someCICS application programs (such as ADDing a record which is likely to alreadyexist, without doing a READ first), the ERRORS Operand may be used toprevent such errors from printing, while allowing real errors to be reported here.All errors detected by VSAM, whether reported or not, are summarized in theassociated OUTPUT PROCESSING SUMMARY report.

The particular information displayed for errors depends on the error, and themanner in which it was detected. This is because CSI-RECOV groups all updatesfor each VSAM record, and decides what needs to be done to make the netchange to the VSAM file. For example, if CSI-RECOV processes a WRITE NEW,WRITE UPDATE, and WRITE DELETE for the same VSAM record, it assumesthat the record does not already exist on the file, and just issues a READ to makesure. If the record does exist, the error is reported, showing the last CICSfunction code (WRITE DELETE), the recovery function (DELETEVERIFICATION), and the VSAM function (READ). Depending on theERRORS(...) Operand in effect, the data record from the journal may bedisplayed.

The following example shows an error caused by an incorrect READ forUPDATE record key produced by CICS File Control during "generic delete"processing. In this example, we were testing the BACKOUT function, which usesthe "before" images to do the backout.

CSI-RECOV RELEASE x.xx CICS/VS FORWARD RECOVERY SYSTEM - VSAM OUTPUT ERROR REPORT 11.13 PAGE 101-07-87 87/007

CSIRECOV-53 THE FOLLOWING INPUT WAS NOT PROCESSED DUE TO AN ERROR

CICS APPLID ..................CICS JID ..................... 2FILE NAME(KSDS) .............. RLNKSDSDATE CREATED ................. 86/316TIME CREATED ................. 12.44.164CICS TRANID .................. CSIVCICS TERMID .................. L044CICS TASK-NBR ................ 101RIDFLD (KEY) ................. LENGTH=4, C'....' X'03000000'CICS FUNCTION ................ (RU) READ FOR UPDATERECOVERY FUNCTION ............ (WU) UPDATE EXISTING RECORDVSAM FUNCTION ................ (RU) READ FOR UPDATEVSAM STATUS .................. NOT FOUNDDATA RECORD LENGTH ........... 20

DATA RECORD ...... 0000 00140000 00000001 00050001 00020003 00040005 *.................... *



INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FOR THIS OUTPUT VSAM

The summary report for the OUTPUT VSAM Command prints an additional setof totals, which shows how many errors occurred. Also note that the BACKOUTattribute is displayed here. This summary appears following the input summaryreports, and if the VSAM OUTPUT ERROR REPORT is directed to a differentprint file, it also appears on that print file.

CSI-RECOV RELEASE x.xx CICS/VS FORWARD RECOVERY SYSTEM - OUTPUT PROCESSING SUMMARY 11.13 PAGE 201-07-87 87/007

OUTPUT 2 OF 2 TYPE ..... VSAM

INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FOR THIS OUTPUT VSAM ---------------------------------------------------------------

FILENAME/ID FIRST LAST TOT-RECS AVG-SIZE READ READ-UPD UPDATES ADDS DELETES ATTRIBUTES----------- /ERRORS /ERRORS /ERRORS /ERRORS

RLNESDS 86/316 86/316 9 26 0 2 2 5 0 BACKOUT 12.44.197 12.44.234 0 0 0 0

RLNKSDS 86/316 86/316 29 25 5 7 1 10 6 BACKOUT 12.43.247 12.44.185 1 0 0 0

RLNKSFL 86/316 86/316 30 21 5 9 4 7 5 BACKOUT 12.44.285 12.44.307 0 0 0 0

RLNRRDS 86/316 86/316 22 30 9 2 1 9 1 BACKOUT 12.44.254 12.44.268 0 0 0 0

*TOTAL* 86/316 86/316 90 25 19 20 8 31 12 12.43.247 12.44.307 1 0 0 0



DL/I Reporting

CSI-RECOV Summary Reports for DL/I journal records appear slightly differentthen the reports for VSAM journal records.

The Filename field contains the DL/I DBD name followed by the Physical File IDof the dataset within the DBD.

The statistical counts for types of requests show the type of DL/I requestperformed. "logical" and "physical" DL/I requests are combined for the sametype of request.

The "READ" column contains the number of "Database Open" requests. Theseare DL/I type x'2F' records are are required for DL/I recovery.


INPUT 1 OF 1 TYPE ..... DLILOGDDNAME 1 OF 1 .......... DLILOG1DLILOG DATASET NAME .... DLI.LOG.FILE

INDIVIDUAL CICS FILE STATISTICS FOR ALL RECORDS FROM THIS INPUT DLILOG -------------------------------------------------------------


DBTEST1/1 86/316 86/342 37 26 1 8 8 20 0 12.44.197 09.21.210

DBTEST1/2 86/316 86/342 89 25 1 30 4 30 24 12.44.118 09.21.177

DBTEST2/1 86/316 86/342 76 21 1 27 12 21 15 12.44.285 09.21.255

DBTEST2/2 86/316 86/342 37 28 1 0 0 36 0 12.17.349 09.21.104

DBTEST2/3 86/316 86/342 41 30 1 6 3 28 3 12.44.254 09.21.229

*TOTAL* 86/316 86/342 280 25 5 71 27 135 42 12.17.349 09.21.255

*OTHER* 0 0

After the TOTAL line on this report, the total number of "OTHER" journalrecords is shown. This value represents the journal records contained on theDL/I log that were not processed by CSI-RECOV. Only DL/I journal recordscontaining log-types of x'2F', x'50' and x'51' are processed by CSI-RECOV. Theseare the record types required for DL/I forward recovery. CSI-RECOV does notcapture the DL/I records required for DL/I "backout".


Page 121

VERIFICATION SYSTEM


Verification and Testing Page 123

System Components

A Verification System has been provided so that you can make sure yourForward Recovery environment has been established properly. This verificationprocess should be run after you have installed CSI-RECOV and whenever a newrelease of CICS is installed.

The verification system consists of the following components:

CSIRECVI Initialize Verification Files.(Cobol Source Program / batch)

CSIRECVU Update the Verification Files.(Cobol Source Program / on-line)

CSIRECVC Check the Recovered/Updated Files.(Cobol Source Program / batch)

CSIRECV0 File Control Table Entries

CSIRECV1 Journal Control Table

CSIRECV2 Define and Initialize Verification Files.(JCL)

CSIRECV3 Recover and Check Verification Files.(JCL)

The following pages will take you through the process required to install andrun the Verification System, as follows:

1. Compile the Verification Programs, if necessary.

2. Modify your CICS Tables and Startup JCL.

3. Modify the Verification JCL.

4. Run the Verification Jobstream CSIRECV2 to define and initialize theVerification Files.


Page 124 Verification and Testing

5. Run the on-line Verification Program to update the Verification Files andcreate the CICS Journal entries.

6. Run the Verification Jobstream CSIRECV3 to recover the Verification Filesand ensure that the Recovery has been completed.



Compiling the Verification Programs

Object Modules have been provided for the 3 verification programs. We havealso provided source code for these programs, in case you need to make source-level program changes.

CSIRECVI (Initialize Verification Files)

This batch program will generate several records in each of 4 VSAM files. Theserecords are formatted such that the updating and checking process can beperformed and verified.

4 file types are created by CSIRECVI:

KSDS KEYED SEQUENCE VARIABLE LENGTHESDS ENTRY SEQUENCERRDS RELATIVE RECORDKSFL KEYED SEQUENCE FIXED LENGTH

DLBLs/JCL Required for CSIRECVI:

ERROR MESSAGES SYSLSTVSAM FILE (KSDS) RLNKSDSVSAM FILE (ESDS) RLNESDSVSAM FILE (RRDS) RLNRRDSVSAM FILE (KSFL) RLNKSFL



CSIRECVU (Update the Verification Files):

This is an on-line Command level program that runs a set of updates againsteach of the file types. Every type of CICS file updating is performed (wherevalid) for each file type:

• empty file load (RLNKSRU)• generic deletes• specific record deletes• record adds• record updates

Dataset names (FCT) used by CSIRECVU:

• RLNKSDS• RLNKSRU (same dataset as RLNKSDS)• RLNESDS• RLNRRDS• RLNKSFL

These correspond with the FCT entries provided in Source MemberA.CSIRECV0.

Prior to CICS 1.7

The object module for CSIRECVU was compiled for CICS 1.7 and above. Youwill need to make source changes and re-compile it, if you are using an earlierrelease of CICS.

The required changes are found in source module C.CSIRECVU at paragraph"99200-FILE-MNGMT". Follow the instructions in the comment blockimmediately preceding this paragraph.



CSIRECVC (Check the recovered/updated files):

This is a batch program that reads each of the four verification files and checkstheir contents for a specific set of known records. Any deviation from this knownset indicates a problem in your recovery process.

DLBLs/JCL required for CSIRECVC:

ERROR MESSAGES SYSLSTVSAM FILE (KSDS) RLNKSDSVSAM FILE (ESDS) RLNESDSVSAM FILE (RRDS) RLNRRDSVSAM FILE (KSFL) RLNKSFL



Modifying CICS Tables for Verification Testing

The following CICS Table entries must be added before you can use theCSIRECOV Verification System.

CICS Program Control Table (PCT):

10..16..20...25...30...35..........72DFHPCT , X

TYPE=ENTRY, XTRANID=CSIV, XPROGRAM=CSIRECVU

Note: You can use any Tran ID you want.

CICS Processing Program Table (PPT):

10..16..20...25...30...35..........72DFHPPT , X

TYPE=ENTRY, XPROGRAM=CSIRECVU, XPGMLANG=COBOL

CICS System Initialization Table (SIT):

10..16..20...25...30...35..........72DFHSIT , X

JCT=xx, XJCP=1$, (CICS 1.6 and below) XFCP=A$ (CICS 1.6 and below)

Note: JCT=xx is the JCT suffix



Journal Control Table (JCT):

The verification testing Journal Control Table shown below uses a one-datasetjournal because few journal records are written. In production, we recommendusing a two-dataset journal (JTYPE=DISK2). If you already have a two-datasetjournaling system in place, use it for this test.

Source member A.CSIRECV1 contains the JCT entries required.

10..16..20...25...30...35........................72DFHJCT , X

TYPE=INITIAL, XSUFFIX=xx

DFHJCT , XTYPE=ENTRY, XJFILEID=02, (same as FCT JID=) XJTYPE=DISK1, XBUFSIZE=4000, (minimum is 505) XOPEN=INITIAL, XDEVADD=SYS024

DFHJCT , XTYPE=FINAL

Note: The TYPE=INITIAL and TYPE=FINAL are only required if you arecreating a new JCT.

CICS File Control Table (FCT):

Source Member A.CSIRECV0 contains the FCT entries required. If necessary,change 'JID=02' for each file to the value specified in your CICS JCT for'JFILEID='. All of the verification datasets are defined in the FCT asOPENED=DEFERRED. Progam CSIRECVU will issue the CEMT Commands toopen and close the files as required.

Notes:

• The verification system uses Generic Deletes as part of the update process.Therefore, LOG=YES cannot be added to the FCT entries in CICS releases 1.5and 1.6. If LOG=YES is added, an INVREQ error will result when runningprogram CSIRECVU with CICS 1.5 or 1.6.

• Dataset RLNKSRU is defined with the REUSE attribute and points to thesame physical dataset as RLNKSDS. Therefore, the FCT entries forRLNKSRU and RLNKSDS must not specify (or default to)SERVREQ=(SHARE). This would result in a VSAM open error.



For CICS 1.7 and above, add LSRPOOL=NONE to the FCT entries forRLNKSRU and RLNKSDS.



Modifying CICS Startup JCL

Add the DLBL/extent(s) for the journal files.

// DLBL DFHJ02A,'CSIRECOV.TEST.JOURNAL',0, SD// EXTENT SYS024,DISK01,1,0,500,500

Add the DLBL/extent(s) for the CSI-RECOV verification files.

Note: files RLNKSDS and RLNKSRU both specify the same VSAM datasetname.

// DLBL RLNKSDS,'CSI.KSDS.FILE',,VSAM,CAT=UCATxxx// DLBL RLNKSRU,'CSI.KSDS.FILE',,VSAM,CAT=UCATxxx// DLBL RLNKSFL,'CSI.KSFL.FILE',,VSAM,CAT=UCATxxx// DLBL RLNESDS,'CSI.ESDS.FILE',,VSAM,CAT=UCATxxx// DLBL RLNRRDS,'CSI.RRDS.FILE',,VSAM,CAT=UCATxxx



Modifying Verification JCL

You may need to make the following changes to the two jobstreams:

CSIRECV2:

• VSAM Data Set Names

• Volume Serial Numbers

• VSAM Catalog Name

• LIBDEF for Library containing CSIRECVI

CSIRECV3:

• VSAM Dataset Names

• CICS Journal DLBL and extents

• VSAM Catalog Name

• Sorting parameters may need to be modified for your particular sortpackage. Refer to the SORTOPTION Command documentation for details.



Run Jobstream CSIRECV2

When you run this Jobstream the following will happen:

Step 1 Will use IDCAMS to define the four verification files.

Step 2 Will use CSIRECVI to load the four verification files with knownrecords.

Check the messages from IDCAMS and CSIRECVI to make sure all initializationhas been completed. You should get message 'CSIRECVI-01 FILEINITIALIZATION COMPLETED OK.' If not, see sections "Messages" and"Problem Determination for CSIRECVI".



Run On-line Verification Program

This program should be run to update the verification files and create the CICSjournal entries. The steps to go through are the following:

1. Bring up CICS and make sure the CICS journal is open. The verification filesshould remain closed. Program CSIRECVU will issue CEMT Commands toopen the files.

2. Enter the Tran ID defined for program CSIRECVU. A series of messages willbe displayed during the update processing. These messages show theprogress of program CSIRECVU while it is opening, processing, and closingeach of the verification files. The final message displayed should be:

CSIRECVU-01 PROCESSING COMPLETED - TASKID(nnnnnnn)

The TASKID is the CICS Task number for this transaction. You can use thisnumber for journal selection in Jobstream CSIRECV3, if you need to run thistest more than once using the same journals. If you do not get this message,please refer to sections "Messages" and "Problem Determination forCSIRECVU".

3. The verification files should have been closed by CSIRECVU. Use CEMT toverify that they have been closed.

4. Close the journal file to ensure that the last block has been written.



Run Jobstream CSIRECV3

When you run this jobstream the following will happen:

Step 1 Will use CSIRECVC to verify that the on-line updates haveoccurred. Check for message 'CSIRECVC-01 VERIFICATIONCOMPLETED OK'. If you do not get this message, see sections"Messages" and "Problem Determination for CSIRECV3". Anyerrors here indicate that the on-line updating did not occur, orthat the files were not freshly initialized by CSIRECVI prior tothe on-line updates.

Step 2 Will reinitialize the four files in preparation for recovery.

Step 3 Will use CSIRECOV to recover the four verification files usingyour CICS journal as input. The selected journal records will besorted prior to attempting the recovery.

Step 4 Will use CSIRECVC to verify that the on-line updates have beenreplaced by the recovery step. Check for message 'CSIRECVC-01VERIFICATION COMPLETED OK.' If you do not get thismessage, see sections "Messages" and "Problem Determinationfor CSIRECV3". Any errors here indicate a problem with thejournaling and/or recovery process.



Problem Determination for Verification System

Problem Determination for CSIRECV3:

The following table indicates what actions are performed against each of the filetypes. Errors generated for specific keys within each file type will indicate theprobable type of error.

FILE KEY(RANGE) ACTION PERFORMEDKSDS 0001 - 0005 initial keys added via mass insert to empty

dataset RLNKSRUKSDS 1001 - 1005 addedKSDS 0001 - 0005 generic deleteKSDS 1001 updatedKSDS 1002 regular deleteESDS 0001 - 0007 initial keys (internal)ESDS 0010 - 0014 addedESDS 0003 updated (RBA 42)ESDS 0006 updated (RBA 140)RRDS 0001 - 0009 initial keys (internal)RRDS 0001 updatedRRDS 0002 regular deleteRRDS 0016 - 0024 addedKSFL 0001 - 0005 initial keysKSFL 1001 - 1005 addedKSFL 0001 deletedKSFL 0002 updatedKSFL 0003 updated, deleted, addedKSFL 0004 deleted, added, updatedKSFL 0005 deletedKSFL 1001 updatedKSFL 1002 deleted



Verify the INPUT Processing Totals

Check the Input Processing Summary for your CICS journal to determine if theproper number of journal records were found for each verification file type:

FILENAME TOT-RECS READ READ-UPD UPDATES ADDS DELETESRLNESDS 9 0 2 2 5 0RLNKSDS 24 5 7 1 5 6RLNKSFL 30 5 9 4 7 5RLNKSRU 5 0 0 0 5 0RLNRRDS 22 9 2 1 9 1

TOTAL 90 19 20 8 31 12

If the above report is correct:

• Check for errors produced by the OUTPUT VSAM processing.

• Make sure the journal is sorted via the SORTOPTION Command or SORTOperand in Jobstream #3 (CSIRECV3) Jobstep 3.

If the above report is not correct:

• Make sure CSIRECVU ran without errors, and that the journal was open foroutput during the updating.

• Make sure that the correct input journal was specified.

• If your journal is not initialized prior to the verification test, you may need tomodify the SELECT Command to select the proper DATE/TIME period.



Verify the OUTPUT Processing Totals

Check the CSIRECOV Output VSAM Processing Summary Report to determineif the proper number of journal records were processed for each verification filetype. The totals for each file should be the same as the Input Journal processingsummary. There should be no errors.

Any records that could not be processed by CSIRECOV will generate an errorpage indicating why. Any errors here would indicate that:

• The Verification files were not freshly initialized prior to the recovery.(Recovery run more than once).

• The CICS journals contain more than one set of updates from CSIRECVU.The CSIRECOV SELECT Command TIME and/or DATE Operands can beused to select the most recent journal update set.

Problem Determination for CSIRECVU

Any messages other than CSIRECVU-01 indicate that one of the following errorshas happened:

• The files have not been initialized properly with CSIRECVI

• The FCT definitions are not as specified in CSIRECV0

• The update process has been run more than once since the last timeCSIRECVI has been run


Page 139

MESSAGES


Messages Page 141

CSIRECOV-0 PROCESSING COMPLETED,0 ERRORS OCCURRED,0 SEQUENCE ERROR(S) ENCOUNTERED,CONDITION CODE IS 0

This message is displayed on the system console and on SYSLST at end ofjob. It indicates the number of error messages generated during OUTPUTprocessing, the number of sequence errors in the journal input, (ifNOSTOP specified), and the Operating System Return/Condition codethat the Jobstep ended with.

CSIRECOV-1 nnn PARAMETER ERRORS,CORRECT AND RE-SUBMIT,PROCESSING TERMINATED

This message is displayed on the system console and on SYSLST if anyerrors are detected in the Commands or parameters that were input toCSI-RECOV. Processing is terminated with a Jobstep Return/Conditioncode of 12.

CSIRECOV-2 NO INPUT COMMANDS SPECIFIED,PROCESSING TERMINATED

This message is displayed on the system console and on SYSLST if NOINPUT Commands are specified. CSI-RECOV cannot process unless atleast one INPUT Command is specified. Processing is terminated with aJobstep Return/Condition code of 12.

CSIRECOV-3 nnn SEQUENCE ERROR(S) ENCOUNTERED,PROCESSING TERMINATED

This message is displayed on the system console and on SYSLST if thenumber of journal sequence errors exceeds the number specified in theSTOP Operand of the SORTOPTION Command. Processing is terminatedwith a Jobstep Return/Condition code of 12.

CSIRECOV-5 PROCESSING TERMINATED AS REQUIRED BY PARM INPUT

This message is displayed on the system console and on SYSLST whenparameter input required a termination for processing errors found in theinput data. One for more messages indicating the exact reason for thetermination will precede this message. Processing is terminated with aJobstep Return/Condition code of 12.

CSIRECOV-10 INPUT TYPE REQUIRED (JOURNAL/BACKUP/DLILOG)

This message is displayed on the "Parameter Edit Report" if an INPUTCommand is specified without one of the JOURNAL, BACKUP andDLILOG Keywords. Processing continues until all Commands have beenedited, but then processing will be terminated with message CSIRECOV-1 and a Jobstep Return/Condition code of 4.


Page 142 Messages

CSIRECOV-11 DDNAME/SYSNNN REQUIRED FOR ALL INPUT COMMANDS

This message is displayed on the "Parameter Edit Report" if an INPUTCommand is specified without at least one DLBL/TLBL specified as asub-parameter for the JOURNAL, BACKUP or DLILOG keywords.Processing continues until all Commands have been edited, but thenprocessing will be terminated with message CSIRECOV-1 and a JobstepReturn/Condition code of 4.

CSIRECOV-12 INPUT MODNAME 'cccccccc' COULD NOT BE LOADED

This message is displayed on the "Parameter Edit Report" if an INPUTCommands MODNAME value could not be found in the specifiedLIBDEF. Processing continues until all Commands have been edited, butthen processing will be terminated with message CSIRECOV-1 and aJobstep Return/Condition code of 4.

CSIRECOV-13 'cccccccc' IS NOT A VALID INPUT I/O MODULE

This message is displayed on the "Parameter Edit Report" if an INPUTCommand's MODNAME value was not generated with the CSIIOGENcustomization macro. Check to see that you specified the correct name foryour I/O module. If you generated your own I/O module, the namemust be CSIRECDB, CSIRECDJ, CSIRECDD, or any name not startingwith CSI. Processing continues until all Commands have been edited, butthen processing will be terminated with message CSIRECOV-1 and aJobstep Return/Condition code of 4.

CSIRECOV-14 INVALID SYSNNN FORMAT FOR INPUT 'ddname'

This message is displayed on the "Parameter Edit Report" if an INPUTCommand's ddname Operand is entered in what appears to be the'ddname/sysnnn' format, but the 'sysnnn' either does not start with 'SYS'or end in a 3-digit number. Processing continues until all Commandshave been edited, but then processing will be terminated with messageCSIRECOV-1 and a Jobstep Return/Condition code of 4.

CSIRECOV-15 DLBL/TLBL/DD STATEMENT MISSING FOR INPUT 'ddname'

This message is displayed on the "Parameter Edit Report" if an INPUTCommand's ddname Operand does not have a DLBL/TLBL/DDstatement in the JCL for CSIRECOV. This check will not be made for VSEunlabeled tapes. Processing continues until all Commands have beenedited, but then processing will be terminated with message CSIRECOV-1 and a Jobstep Return/Condition code of 4.


Messages Page 143

CSIRECOV-16 DLIKEY MUST BE IN RANGE OF 1 TO 256 BYTES

This message is displayed on the "Parameter Edit Report" if a DLIKEYOperand is specified with a value of less than 1 or greater than 256.Processing continues until all Commands have been edited, but thenprocessing will be terminated with message CSIRECOV-1 and a JobstepReturn/Condition code of 4.

CSIRECOV-20 OUTPUT TYPE REQUIRED (BACKUP/VSAM/PRINT/DLILOG)

This message is displayed on the "Parameter Edit Report" if an OUTPUTCommand is specified without one of the BACKUP, VSAM, DLILOG orPRINT Keywords. Processing continues until all Commands have beenedited, but then processing will be terminated with message CSIRECOV-1 and a Jobstep Return/Condition code of 4.

CSIRECOV-21 PRIMARY DDNAME/SYSNNN REQUIRED FOR OUTPUTBACKUP/DLILOG

This message is displayed on the "Parameter Edit Report" if an OUTPUTBACKUP or OUTPUT DLILOG Command is specified without at leastone DLBL/TLBL. Processing continues until all Commands have beenedited, but then processing will be terminated with message CSIRECOV-1 and a Jobstep Return/Condition code of 4.

CSIRECOV-22 OUTPUT MODNAME 'cccccccc' COULD NOT BE LOADED

This message is displayed on the "Parameter Edit Report" if an OUTPUTCommand's MODNAME value could not be found in the specifiedLIBDEF. Processing continues until all Commands have been edited, butthen processing will be terminated with message CSIRECOV-1 and aJobstep Return/Condition code of 4.

CSIRECOV-23 'cccccccc' IS NOT A VALID OUTPUT I/O MODULE

This message is displayed on the "Parameter Edit Report" if an OUTPUTCommand's MODNAME value was not generated with the CSIIOGENcustomization macro. Check to see that you specified the correct name foryour I/O module. If you generated your own I/O module, the namemust be CSIRECDB, CSIRECDJ, CSIRECDD or any name not startingwith CSI. Processing continues until all Commands have been edited, butthen processing will be terminated with message CSIRECOV-1 and aJobstep Return/Condition code of 4.


Page 144 Messages

CSIRECOV-24 INVALID SYSNNN FORMAT FOR OUTPUT BACKUP/DLILOG

This message is displayed on the "Parameter Edit Report" if an OUTPUTBACKUP or OUTPUT DLILOG Command's ddname Operand is enteredin what appears to be the 'ddname/sysnnn' format, but the 'sysnnn' eitherdoes not start with 'SYS' or does not end in a 3-digit number. Processingcontinues until all Commands have been edited, but then processing willbe terminated with message CSIRECOV-1 and a JobstepReturn/Condition code of 4.

CSIRECOV-25 DLBL/TLBL/DD STATEMENT MISSING FOR OUTPUT 'ddname'

This message is displayed on the "Parameter Edit Report" if an OUTPUTCommand's ddname Operand does not have a DLBL/TLBL/DDstatement in the JCL for CSIRECOV. This check will not be made for VSEunlabeled tapes. Processing continues until all Commands have beenedited, but then processing will be terminated with message CSIRECOV-1 and a Jobstep Return/Condition code of 4.

CSIRECOV-30 ONLY ONE SORTOPTION COMMAND CAN BE SPECIFIED

This message is displayed on the "Parameter Edit Report" if more thanone SORTOPTION Command is entered. All Sort options must bespecified on a single SORTOPTION Command. Processing continuesuntil all Commands have been edited, but then processing will beterminated with message CSIRECOV-1 and a Jobstep Return/Conditioncode of 4.

CSIRECOV-31 ERROR DURING INPUT SORT, RC=nnn (X'hh')PROCESSING IS TERMINATED

This message is displayed on the system console and on SYSLST if anyerrors are detected during the input sort. The return code from your sortpackage is displayed in both decimal and hex. Processing is terminatedwith a Jobstep Return/Condition code of 12.


Messages Page 145

CSIRECOV-32 SEQUENCE ERROR ENCOUNTERED,PREVIOUS RECORD KEY ----... FILENAME - dataset,... KEYLENGTH - nnn,... KEY (CHAR) - C'ccccccccccc',... KEY (HEX) - X'hhhhhhhhhhh',... CREATE DATE - yy/ddd,... CREATE TIME - hh.mm.ss.t,... JOURNAL BLK - nnn,... JOURNAL REC - nnn,CURRENT RECORD KEY ----... FILENAME - dataset,... KEYLENGTH - nnn,... KEY (CHAR) - C'ccccccccccc',... KEY (HEX) - X'hhhhhhhhhhh',... CREATE DATE - yy/ddd,... CREATE TIME - hh.mm.ss.t,... JOURNAL BLK - nnn,... JOURNAL REC - nnn

This message is displayed on SYSLST if a sequence error is detected in theinput journal records and either the SEQERR(PRINT) or SEQERR(STOP)options have been specified. If the STOP condition has been met, messageCSIRECOV-3 is generated, otherwise processing continues, but theJobstep Return/Condition code will be set to 4.

CSIRECOV-33 INVALID RECORD SEGMENT-ID RETURNED FROM SORT... SEGMENT-ID - nnn... PREVIOUS - nnn

This message is displayed on the system console and on SYSLST if asegment sequence error is detected in the records returned from SORT.This indicates a program logic error. Request assistance from a supportrepresentative for this problem. Processing is terminated and the Jobstepis canceled with a Jobstep Return/Condition code of 12.

CSIRECOV-40 DUPLICATE ATTRIBUTE FILE NAME SPECIFIED 'ddname'

This message is displayed on the "Parameter Edit Report" if anATTRIBUTE Command is entered with the same VSAM ddnamespecified more than once. All attributes for a single VSAM ddname mustbe entered in the same sub-parameter on the ATTRIBUTE Commands.Processing continues until all Commands have been edited, but thenprocessing will be terminated with message CSIRECOV-1 and a JobstepReturn/Condition code of 4.


Page 146 Messages

CSIRECOV-50 DLBL/DD STATEMENT MISSING FOR FILE 'ddname' ALL INPUTFOR THIS FILE WILL BE IGNORED

This message is displayed on the "OUTPUT VSAM Error Report" if aDLBL/DD statement cannot be found for the VSAM file 'ddname'. Alljournal input for 'ddname' will be counted as errors. Processing continuesfor all other VSAM files, but the Jobstep Return/Condition code is set to8.

CSIRECOV-51 DLBL/DD STATEMENT FOR 'ddname' DOES NOT DESCRIBE AVSAM FILE, ALL INPUT FOR THIS FILE WILL BE IGNORED

This message is displayed on the "OUTPUT VSAM Error Report" if aDLBL/DD statement for VSAM file 'ddname' is not for a VSAM dataset.All journal input for 'ddname' will be counted as errors. Processingcontinues for all other VSAM files, but the Jobstep Return/Conditioncode is set to 8.

CSIRECOV-52 VSAM OPEN ERROR ON FILE 'ddname' FUNC=xxxxxxxxxxxx,RC=X'hh'(nnn), EC=X'hh'(nnn),ALL INPUT FOR THIS FILE WILL BE IGNORED

This message is displayed on the "OUTPUT VSAM ERROR REPORT" ifan open error is encountered on VSAM file 'ddname'. The VSAM returncode and error code are displayed in the message, along with a textdescription of the open sub-function to be performed by CSI-RECOV. Alljournal input for 'ddname' will be counted as errors. Processing continuesfor all other VSAM files, but the Jobstep Return/Condition code is set to8.

CSIRECOV-53 THE FOLLOWING INPUT WAS NOT PROCESSED DUE TO ANERROR

This message is displayed on the "OUTPUT VSAM Error Report" if anerror is encountered while a journal record is being processed. Refer tothe "Reports" section of this documentation for the printed outputassociated with this message. This message can be misleading for ESDSfiles. If WN functions to ESDS files result in a different RBA then wasused by CICS, this error will result, but the record in error has alreadybeen added to the ESDS file and there is no way for CSI-RECOV toremove it. Processing continues, but the Jobstep Return/Condition codeis set to 8.


Messages Page 147

CSIRECOV-54 VSAM ERROR ON FILE 'ddname' FUNC=xxxxxxxxxxxx,RC=X'hh'(nnn), EC=X'hh'(nnn),ALL REMAINING INPUT FOR THIS FILE WILL BE IGNORED

This message is displayed on the "OUTPUT VSAM Error Report" if aVSAM error is encountered on VSAM file 'ddname'. The VSAM returncode and error code are displayed in the message, along with a textdescription of the VSAM sub-function to be performed by CSI-RECOV.All remaining journal input for 'ddname' will be counted as errors. Thismessage will be preceded by message CSIRECOV-53. Processingcontinues for all other VSAM files, but the Jobstep Return/Conditioncode is set to 8.

CSIRECOV-55 THE FOLLOWING INPUT WAS NOT BACKED OUT BECAUSE THEFIRST CICS FUNCTION WAS NOT A READ

This message is displayed on the "OUTPUT VSAM Error Report" if theBACKOUT attribute option is being used, and the first CICS function fora record key is not a 'read' type request. No backout can be performedwithout a 'read' journal record. Check the CICS FCT to make sure that'before' journaling is being requested. Refer to the "Reports" section of thisdocumentation for the printed output associated with this message.Processing continues, but the Jobstep Return/Condition code is set to 8.

CSIRECOV-56 JOURNAL KEY LENGTH OF nnn FOR FILE 'ddname'DOES NOT MATCH VSAM KEY LENGTH OF nnn... CICS APPLID - applid,... CICS JID - nn,... CREATE DATE - yy/ddd,... CREATE TIME - hh.mm.ss.t,... JOURNAL KEY - C'kkkkkkkkk',

X'hhhhhhhhh',ALL REMAINING INPUT FOR THIS FILE WILL BE IGNORED

This message is displayed on the "OUTPUT VSAM Error Report" if ajournal record is detected with a record key length different from thatdefined to VSAM. All remaining journal input for 'ddname' will becounted as errors.

This error will also occur if the journal record originated from a release1.7 CICS system, but "1.7" was not specified on the INPUT JOURNALCommand. In this case, the key length on the journal record will be fourbytes longer that the actual VSAM key length. The "FORCE" attribute willhandle this situation by ignoring the first four bytes of the journal key,but the invalid key will also cause the records to be sorted incorrectly.

Processing continues for all other VSAM files, but the JobstepReturn/Condition code is set to 8.


Page 148 Messages

CSIRECOV-57 VSAM OPEN ERROR ON FILE 'ddname' FUNC=xxxxxxxxxxxx,RC=X'hh'(nnn), EC=X'hh'(nnn),PROCESSING IS TERMINATED

This message is displayed on the system console and SYSLST if an openerror is encountered on VSAM file 'ddname' while processing a VSAMESDS DL/I log dataset. The VSAM return code and error code aredisplayed in the message, along with a text description of the open sub-function to be performed by CSI-RECOV. Processing is terminated with aJobstep Return/Condition code of 12.

CSIRECOV-58 VSAM ERROR ON FILE 'ddname' FUNC=xxxxxxxxxxxx,RC=X'hh'(nnn), EC=X'hh'(nnn),ALL REMAINING INPUT FOR THIS JOURNAL WILL BE IGNORED

This message is displayed on the system console and on SYSLST if aVSAM error is encountered on VSAM file 'ddname' while processing aVSAM ESDS DL/I log dataset. The VSAM return code and error code aredisplayed in the message, along with a text description of the VSAM sub-function being performed by CSI-RECOV. All remaining journal input for'ddname' will be skipped. Processing continues for all other journals, butthe Jobstep Return/Condition code is set to 8.

CSIRECOV-60 INVALID KEY LENGTH ENCOUNTERED ON INPUT JOURNAL,PROCESSING IS TERMINATED... DDNAME - jrnddn,... DSNAME - jrn.dataset.name,... FILENAME - cicsname,... KEYLENGTH - nnn,... CREATE DATE - yy/ddd,... CREATE TIME - hh.mm.ss.t,... JOURNAL BLK - nnn,... JOURNAL REC - nnn

This message is displayed on the system console and on SYSLST if aninvalid key length is found in a CICS journal record. The key is the lastfield in the "system prefix" of the CICS journal record, and its length iscalculated by subtracting the length of the other system prefix fields fromthe "system prefix length" supplied by CICS. Starting with CICS release1.7, the system prefix is four bytes longer than before. The calculation willresult in a value less than 1 or greater than 256 if ...

• The INPUT JOURNAL Command specified (or defaulted to) "1.6",and the journal was created by CICS 1.7 or later, and the true keylength is greater than 252. In this case, the displayed key length willbe four bytes greater than the true key length.


Messages Page 149

• The INPUT JOURNAL Command specified "1.7", and the journalrecord was created by CICS 1.5 or 1.6, and the true key length is lessthan 5. In this case, the displayed key length will be four bytes lessthan the true key length. (RRDS and ESDS have a key length of four).

• A CICS application error resulted in a journal record without a keyfield. CICS journals the record with no key and then returns to theapplication program with an "ILLOGIC" error. These journal recordscan be bypassed by coding...

INPUT JOURNAL(jrnddn) -SELECT(EXCLUDE(DATASET(cicsname) -

LE-KEYL(0) ))

Processing is terminated with a Jobstep Return/Condition code of 12.

CSIRECOV-61 BACKUP 'ddname' WAS NOT CREATED BY CSI-RECOV,PROCESSING IS TERMINATED

This message is displayed on the system console and on SYSLST if anINPUT BACKUP Command specifies the ddname of a file that isdetermined to NOT be a valid journal backup file. This could happen if aCICS journal file is specified via an INPUT BACKUP Command.Processing is terminated with a Jobstep Return/Condition code of 12.


Page 150 Messages

CSIRECOV-62 ERROR OCCURRED IN INPUT MODULE,PROCESSING IS TERMINATED,... ERROR CODE - xx... FEEDBACK - xxxxxxxx... FUNCTION - xx... MODNAME - pppppppp... DDNAME - dddddddd... DSNAME - cluster.name

This message is displayed on the system console and on SYSLST if anerror occurs while the program is attempting to open an input journal file.Processing is terminated with a Jobstep Return/Condition code of 12.

ERROR CODE FEEDBACK

01 getmain/getvis failed amount of getmain (hex)02 freemain/freevis failed03 freemain/freevis wrong area04 bad block length field blocklength and "LL" field05 spanned record to large blocklength and "LL" field

FUNCTION is one of the following

00 open input04 open output08 close0C sequential input10 sequential output (buffered)14 sequential output (force write)

CSIRECOV-63 JOURNAL DOES NOT BEGIN WITH A VALID CICS JOURNALLABEL RECORD,PROCESSING IS TERMINATED... DDNAME - jrnddn,... DSNAME - jrn.dataset.name,

This message is displayed on the system console and on SYSLST if thefirst block on a CICS journal file does not begin with a "label record". Thisindicates that the file is not a CICS journal, or it was not formatted withDFHJCJFP. If the file is a logical copy of a CICS journal (not made by aCSIRECOV "OUTPUT BACKUP"), you must make sure that the firstrecord is a CICS label record. Processing is terminated with a JobstepReturn/Condition code of 12.


Messages Page 151

CSIRECOV-64 JOURNAL SPECIFIED AS RELEASE 1.6DSN RECORD FOUNDJOURNAL MUST BE 1.7 OR ABOVEADD 1.7 OPERAND TO INPUT JOURNAL COMMANDPROCESSING IS TERMINATED... DDNAME - jrnddn... DSNAME - jrn.dataset.name

This message is displayed on the system console and on SYSLST if a CICSdataset name record is found in the input journal, and the 1.7 Operandhas not been specified. Unfortunately, this detection cannot always occurat the start of the journal, therefore, processing is terminated with aJobstep Return/Condition code of 12 and you must change your INPUTJOURNAL Command to include the 1.7 Operand.

CSIRECOV-65 INVALID DATA FOUND IN INPUT RECORDJOURNAL LOG RECORD IS SNAPPED FOR DISPLAYRECORD WILL NOT BE PROCESSED... DDNAME - jrnddn... DSNAME - jrn.dataset.name... DBD/PSB ID - dmb name from log record... JOURNAL BLK - dbd sequence number... RECORD SEQ# - log record sequence number

This message is displayed on SYSLST if an invalid packed data field isfound in a DL/I log record. The contents of the log record is displayed incharacter and hex on SYSLST. The record in error is ignored andprocessing continues, however, the Jobstep Return/Condition code willbe set to 4.

CSIRECOV-66 SEQUENCE ERROR FOUND IN DL/I LOG RECORDSJOURNAL LOG RECORD IS SNAPPED FOR DISPLAY,RECORD WILL BE PROCESSEDJOURNAL DDNAME - jrnddnJOURNAL DSNAME - jrn.dataset.nameLOG DBD/PSB ID - dmb name from log recordJOURNAL BLK - dbd sequence numberPREV SEQ NBR - last good sequence numberTHIS SEQ NBR - sequence number of this record

This message is displayed on SYSLST if a DL/I log record sequencenumber does not progress by one from the previous log entry. Thecontents of the log record is displayed in character and hex on SYSLST.The record in error is processed, however, the Jobstep Return/Conditioncode will be set to 4.


Page 152 Messages

CSIRECOV-67 MULTIPLE SEQUENCE ERRORS FOUND IN LOG RECORDSJOURNAL LOG RECORD IS SNAPPED FOR DISPLAY, RECORDWILL BE PROCESSEDJOURNAL DDNAME - jrnddnJOURNAL DSNAME - jrn.dataset.nameLOG DBD/PSB ID - dmb name from log recordJOURNAL BLK - dbd sequence numberPREV SEQ NBR - last good sequence numberTHIS SEQ NBR - sequence number of this record

This message is displayed on SYSLST if a DL/I log record sequencenumber does not progress by one from the previous log entry in morethan five log records in a single input file. The contents of the log recordis displayed in character and hex on SYSLST. Processing is terminatedwith a Jobstep Return/Condition code of 12.

If the DBERR(SEQERR) Operand is specified on the INPUT DLILOGCommand, this error will be treated the same as message CSIRECOV-66,and processing will continue.

CSIRECOV-68 INVALID LOG RECORD RECORD DATA LENGTHJOURNAL LOG RECORD IS SNAPPED FOR DISPLAY... DDNAME - jrnddn... DSNAME - jrn.dataset.name... DBD/PSB ID - dmb name from log record... LOG DATA LN - length of data found in log

This message is displayed on SYSLST if the length of the data in a DL/Ilog record exceeds the DL/I maximum of 512 bytes. The contents of thelog record is displayed in character and hex on SYSLST. Processing isterminated with a Jobstep Return/Condition code of 12.

If the DBERR(DATAERR) Operand is specified on the INPUT DLILOGCommand, this error will be ignored and processing will continue.

CSIRECOV-69 DATE AND TIME SEQUENCE ARE INVALIDJOURNAL LOG RECORD IS SNAPPED FOR DISPLAY... DDNAME - jrnddn... DSNAME - jrn.dataset.name... DBD/PSB ID - dmb name from log record... PREV LOG DATE - last date still in sequence... CUR LOG DATE - date found in this log record... PREV LOG TIME - last time still in sequence... CUR LOG TIME - time found in this log record... JRNL SEQ NBR - log record sequence number

This message is displayed on SYSLST if the date and time in a DL/I logrecord does not progress in ascending date/time sequence. The contentsof the log record is displayed in character and hex on SYSLST. Processingis terminated with a Jobstep Return/Condition code of 12.


Messages Page 153

If the DBERR(DATAERR) Operand is specified on the INPUT DLILOGCommand, this error will be ignored and processing will continue.

CSIRECOV-72 ERROR OCCURRED IN OUTPUT MODULE,PROCESSING IS TERMINATED,... ERROR CODE - xx... FEEDBACK - xxxxxxxx... FUNCTION - xx... MODNAME - pppppppp... DDNAME - dddddddd... DSNAME - cluster.name

This message is displayed on the system console and on SYSLST if anerror occurs while the program is attempting to process an outputBACKUP or DLILOG file. Refer to error number 62 for a description ofthe returned information. Processing is terminated with a JobstepReturn/Condition code of 12.

CSIRECOV-73 VSAM ERROR IN OUTPUT MODULE,PROCESSING IS TERMINATED,... ERROR CODE - xx... FEEDBACK - xxxxxxxx... FUNCTION - xx... MODNAME - pppppppp... DLILOG ID - dddddddd... VSAM MSGS - xxxxxxxxxxxxxxxxxxxxx

This message is displayed on the system console and on SYSLST if anerror occurs while the program is attempting to process a VSAM ESDSDLILOG file. Refer to error number 62 for a description of the returnedinformation. Processing is terminated with a Jobstep Return/Conditioncode of 12.

CSIRECOV-74 VSAM WRITE ERROR ON DLILOG,PROCESSING IS TERMINATED,... DLILOG ID - dddddddd... ERROR CODE - xx... FEEDBACK - xxxxxxxx... FUNCTION - xx... VSAM MSGS - xxxxxxxxxxxxxxxxxxxxx

This message is displayed on the system console and on SYSLST if anerror occurs while the program is attempting to process a VSAM ESDSDLILOG file. Refer to error number 62 for a description of the returnedinformation. Processing is terminated with a Jobstep Return/Conditioncode of 12.


Page 154 Messages

CSIRECOV-124 INVALID FUNCTION CODE FOUND IN CROSS MEMORYREQUEST, PROCESSING FOR RECORD 'reckey' WAS ABORTED.

This message is displayed on SYSPRINT and SYSLOG when an invalidFunction Code is received by CSI-ARMAN. The information sent with therequest is discarded, and the request is aborted. Manual updates to theRecovery Control file will be required.

CSIRECOV-126 NO SEND/RECEIVE BUFFER FOUND IN WORK REQUEST,REQUEST FOR RCFM SERVICES ABORTED.

This message is displayed on SYSPRINT when CSI-ARMAN has lost theaddress of the send/receive buffer as a result of a processing exception. Asystem dump may be required to determine why the buffer address waslost or destroyed.

CSIRECOV-130 XMC RETURNED FOLLOWING MESSAGE: 'xxxxxxxxxxxxxxxxxxx"CONDITION CODE = 12.

This message is displayed on SYSPRINT and SYSLOG when the crossmemory manager of CSI-ARMAN has detected a processing exceptionand can not complete the transfer of buffers. This will normally occur ifone or the other sides terminates abnormally or if the RCFM has not beeninitiated.

CSIRECOV-135 MAX NUMBER OF SUBRECORDS EXCEEDED IN RECORD'keyname' BACKUP/ARCHIVE IS RECOMMENDED'.

This message is displayed on SYSPRINT and SYSLOG when CSI-ARMAN has found that the specified MAXSUBREC number for the sub-records has been exceeded. Some manual change management actionshould be taken to accumulate the changes on the sub-records of the entryif status is CURRENT or to cause the records with status PREVIOUS to bepurged from the entry on the next update.

CSIRECOV-155 REQUESTED FILE RECORD 'keyname' WAS NOT FOUND. A NEWSKELETON RECORD WAS GENERATED FOR THIS ENTRY. AMANUAL UPDATE OF SELECTED RECORD FIELDS SHOULD BECONDUCTED.

This message is displayed on SYSPRINT and SYSLOG when the actionrequested of CSI-ARMAN required a sub-record be created for a baserecord not found on the file. A skeleton base record has been created towhich the sub-record was written. Manual updates of the RCF must bedone to fill in the data required to complete the base record values or therecord should be deleted and the sub-record assigned to another baserecord.

This message is displayed only when the RCFM is in LEARN mode orwhen a mirror base record entry is created.


Messages Page 155

CSIRECOV-156 REQUESTED FILE 'type' RECORD 'keyname' WAS NOT FOUND

This message is displayed on SYSPRINT and SYSLOG when CSI-ARMAN can not find the requested "type" record "ddname", Type of RCFrecord.is (eg CLUSTER, JRNLBKUP).

CSIRECOV-158 DUPLICATE RECORD FOUND FOR 'type' RECORD 'keyname'

This message is displayed on SYSPRINT when CSI-ARMAN identifiesthe record about to be ADDED to the RCF as a duplicate of an existing'ddname' key.

CSIRECOV-173 ERROR ON CONTROL FILE 'ddname', RCF 'type' RECORD KEY WAS: 'keyname', VSAM SAID 'rrrrrr'.

This message is displayed on SYSPRINT and SYSLOG when CSI-ARMAN has detected a error on the RCF for the identified record.Manual action should be taken to ensure that the identified record isrecorded on the file properly.

CSIRECOV-175 UNEXPECTED RETURN CODE FROM CSIVSAMD -VSAM SAID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. PROCESSINGTERMINATED.

This message is displayed on SYSPRINT and SYSLOG when CSI-ARMAN detects an unexpected error on the RCF for the identifiedfunction. Messages as returned from VSAM will be displayed. Technicalassistance may be required for this problem.

CSIRECOV-1000 'x' IS AN INVALID COMMAND

The first word in the line, "x", is not a valid Command. If it is a parameterintended to be part of a previous Command, check for valid continuationon the end of the previous line. If it is supposed to be part of a comment,check for the proper use of "/*" (start of comment),";" (end of Command),and continuation characters.

CSIRECOV-1001 'x' IS AN INVALID KEYWORD FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNORED

The character string "x" was specified as a sub-parameter of "y", and is nota valid keyword for "y". Any sub-parameters coded for "x" are ignored. If"x" was not intended to be a sub-parameter of "y", check your use ofparentheses. If "x" is a Command, a previous Command may have beencontinued improperly.


Page 156 Messages

CSIRECOV-1002 'x' EXCEEDS THE NUMBER OF POSITIONAL PARAMETERSALLOWED FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNORED

Positional parameters are allowed for "y", but the maximum numberallowed had already been specified before "x" was found. Any sub-parameters coded for "x" are ignored. If "x" was not intended to be a sub-parameter of "y", check your use of parentheses. If "x" is a Command, aprevious Command may have been continued improperly.

CSIRECOV-1003 'x' IS INVALID - NO PARAMETERS ALLOWED FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNORED

No sub-parameters are allowed for "y", but "x" was coded as a sub-parameter. Any sub-parameters coded for "x" are ignored. If "x" was notintended to be a sub-parameter of "y", check your use of parentheses.

CSIRECOV-1004 'x' CAN BE SPECIFIED ONLY n TIMES FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNORED

A list of repeated sub-parameters (maximum of "n") are allowed for "y",but "x" exceeds this maximum. Any sub-parameters coded for "x" areignored. If "x" was not intended to be a sub-parameter of "y", check youruse of parentheses.

CSIRECOV-1006 'x' IS NOT A VALID NUMERIC VALUE

The character string "x" was coded where a numeric value is expected,but it is not a valid number. If "x" was not intended to be a number, itmay be positioned incorrectly in relation to other sub-parameters at thesame level, or incorrect use of parentheses may have caused it to beassociated with the wrong parameter.

CSIRECOV-1007 'x' EXCEEDS THE ALLOWED NUMBER OF n CHARACTERS/DIGITS

For a non-numeric positional parameter, "x" contains too manycharacters. For a numeric parameter, "x" is too large a number for thepositional parameter. If "x" is correct as coded, it may be positionedincorrectly in relation to other sub-parameters at the same level, or theincorrect use of parentheses may have caused it to be associated with thewrong parameter.

CSIRECOV-1008 'x' IS NOT A VALID TIME OF DAY VALUE

A time of day value of the format "HH:MM:SS.T" was expected where "x"was coded. If "x" is not intended to be a time of day value, it may bepositioned incorrectly in relation to other sub-parameters at the samelevel, or incorrect use of parentheses may have caused it to be associatedwith the wrong parameter.


Messages Page 157

CSIRECOV-1009 DELIMITER 'x' IS INVALID FOLLOWING 'y', AND IS IGNORED

The delimiter "x" was coded where it is not allowed. A "/" delimiter isallowed only after certain parameters, and a "(" cannot immediatelyfollow another delimiter.

CSIRECOV-1010 EXTRA RIGHT PARENTHESES FOLLOWING 'x' IGNORED

More right parentheses ")" have been found than are needed. Either a leftparenthesis "(" is missing, or too many right parentheses were coded.

CSIRECOV-1011 MISSING n RIGHT PARENTHESES AT END OF COMMAND

The end of Command has been reached, but "n" left parentheses "(" havenot been paired with right parentheses ")". Either a continuation characteris missing (the next line will start a new Command), or too few rightparentheses ")" were coded.

CSIRECOV-1012 COMMENT IS NOT TERMINATED WITH '*/', OR CONTINUATIONIS MISSING ON THIS LINE

A comment was started with "/*" but was not terminated properly.Comments follow the same continuation rules as parameters, and mustbe terminated by "*/".

CSIRECOV-1013 STRING 'x' IS NOT TERMINATED WITH A QUOTE, ORCONTINUATION IS MISSING ON THIS LINE

The character string "x" was started as a quoted string, but an endingquote (') was not found.

CSIRECOV-1014 STRING 'x' IS NOT FOLLOWED BY A SEPARATOR CHARACTER,OR ONE QUOTE WAS CODED WHERE TWO ARE REQUIRED

The character string "x" was started as a quoted string, and another quote(') was found which was not followed by a separator character (to end thestring).

CSIRECOV-1015 END OF INPUT REACHED - LAST INPUT LINE CANNOT BECONTINUED

The last line in the SYSIN file ended with a continuation character. Sincethere are no more lines to process, continuation is invalid. If you did notintend the SYSIN file to end at this point, check your input for "/*"appearing in the first position of a SYSIN line. This is treated as end-of-file, not the start of a comment.

CSIRECOV-1016 COMMAND NOT PROCESSED DUE TO SYNTAX ERRORS -CONDITION CODE n

The condition code set by previous errors for this Command exceeds themaximum allowed. The highest condition code for all errors for thisCommand is "n".


Page 158 Messages

CSIRECOV-1017 'x' IS NOT A VALID JULIAN DATE VALUE

A Julian date value in the format "YY/DDD" was expected where "x" wascoded. If "x" is not intended to be a Julian date value, it may be positionedincorrectly in relation to other sub-parameters at the same level, orincorrect use of parentheses may have caused it to be associated with thewrong parameter.

CSIRECOV-1096 PATCH HEX STRING CONTAINS ODD NUMBER OF DIGITS

The internal debugging facility has been invoked to patch a module. Ahexidecimal verify or replace string was coded which does not representa whole number of bytes. For example, X'47F0' is valid; x'47F' is not valid.

CSIRECOV-1097 PATCH VERIFY ERROR

The internal debugging facility has been invoked to patch a module, butthe data being verified does not match what is in the module.

CSIRECOV-1098 INTERNAL ERROR - CANNOT FIND TYPE=FINAL

An internal logic error has occurred. Request assistance from a supportrepresentative.

CSIRECOV-1099 INTERNAL ERROR - CANNOT FIND TYPE=SEG FOR xxxxxxxx

An internal logic error has occurred. Request assistance from a supportrepresentative.

CSIRECOV-1100 (module+offset) INTERNAL ERROR - INVALID MESSAGE NUMBERX'xxxxxxxx'(n)

An internal program error has occurred at the location indicated by themodule and offset information. The module has attempted to issue anerror number which is not in any message tables. When requestingtechnical assistance for this error, please state the full error message.

CSIRECOV-1101 (module+offset) function/macro INTERNAL ERROR - RETURN CODEX'xxxxxxxx'(n)

An internal program function has issued an operating system macrowhich failed. The function was called at the location indicated by themodule and offset information. When requesting technical assistance forthis error, please state the full error message.

CSIRECOV-1102 (module+offset) function/macro INTERNAL ERROR - RETURN CODEX'xxxxxxxx'(n) WHILE ISSUING MESSAGE mmmm

While attempting to issue message number "mmmm", an internalprogram function issued an operating system macro which failed. Thefunction was called at the location indicated by the module and offsetinformation. Also refer to message "CSIRECOV-mmmm" which may helpin determining the cause of the problem. When requesting technicalassistance for this error, please state the full error message.


Messages Page 159

CSIRECOV-1103 GETMAIN(GM) / FREEMAIN(FM) STATISTICSGMCOUNT=n GMTOT=nFMCOUNT=n FMTOT=nCURRENT=n MAXIMUM=nLARGEST SINGLE GETMAIN=n

An internal debugging function has requested a display of the memorystatistics.

CSIRECOV-1104 (module+offset) function/macro PROGRAM 'xxxxxxxx' NOT FOUND

CSI-RECOV attempted to load program "xxxxxxxx", but it was not foundin the load libraries available in the job step. The load function was calledat the location indicated by the module and offset information. Thismessage is issued only if the program cannot be found; other load errorswill produce message CSIRECOV-1105 or CSIRECOV-1108

CSIRECOV-1105 function/macro REQUEST FOR n BYTES OF MAIN STORAGEFAILED.USE A LARGER PARTITION, OR A SMALLER SIZE PARAMETER

The indicated internal function issued an operating system macro whichrequired more main storage than was available. If the number of bytesneeded is not known, the message will say "REQUEST FOR MAINSTORAGE FAILED." Execute CSIRECOV in a larger partition (or use asmaller SIZE= parameter). If the problem persists, determine the cause ofexcessive main storage use.

CSIRECOV-1106 (module+offset) function/macro INVALID PRINT FILE 'filename'

CSI-RECOV was unable to open "filename" as a printer file. Check yourJCL and parameters. If you request technical assistance for this error,please state the full error message.

CSIRECOV-1107 CANNOT LOAD SORT - ADD AT LEAST nK TO EXEC SIZE

CSI-RECOV Attempted to load the SORT program into the partition, butthe SIZE= parameter on the EXEC JCL statement is too small. The SIZEparameter must allow enough room for CSIRECOV, plus at least 64K forSORT.

CSIRECOV-1108 (module+offset) function/macro INTERNAL ERROR - ABEND CODEX'xxxx', REASON CODE X'xxxx'

An internal program function has issued an operating system macrowhich failed. The function was called at the location indicated by themodule and offset information. The system abend code and reason codeare displayed. When requesting technical assistance for this error, pleasestate the full error message.


Page 160 Messages

CSIRECOV-1150 (module+offset) xxxxxxxx FUNCTION HAS BEEN ENTERED

The operating system interface module has been called from(module+offset) to perform a "xxxxxxxx" function. This message is issuedonly if the internal trace has been turned on.

CSIRECOV-9998 WARNING - PRODUCT AUTHORIZATION EXPIRES IN 30 DAYSOR LESS

This message is displayed on the system console if the copy of CSI-RECOV you are using is about to expire. Contact your CSI product salesrepresentative for a new Expiration Password.

CSIRECOV-9999 PRODUCT AUTHORIZATION HAS EXPIRED

CSI-RECOV is protected with an Expiration Password. This message isdisplayed on the system console if that Password has expired. Contactyour CSI product sales representative for a new Expiration Password.


Messages (Verification System) Page 161

CSIRECVC-01 xxxx VERIFICATION COMPLETED OK

This is the only message that should be produced if everything is OK.One message will be generated for each file type (xxxx).

CSIRECVC-02 xxxx FILE OPEN ERROR, STATUS = ss

An open error ss (VSAM status for Cobol) has occurred for file type xxxx.Verification is terminated.

CSIRECVC-03 xxxx READ ERROR ON KEY - kkkkkkkk,STATUS = ss

A read error ss (VSAM status for Cobol) has occurred for file type xxxx.Verification is terminated.

CSIRECVC-04 xxxx FILE CLOSE ERROR, STATUS = ss

A close error ss (VSAM status of Cobol) has occurred for file type xxxx.

CSIRECVC-05 xxxx WRONG RECORD COUNT, IS nnnnnSHOULD BE nnnnn

The specified file (xxxx) does not have the proper number of records.This message will probably be preceded by one or more errors for the file.Refer to Problem Determination for errors.

CSIRECVC-06 xxxx GENERIC DELETE FAILED, RECORD = kkkkkkkk

Indicates a problem with the generic delete function. This messageindicates the specified record was not deleted by the Recovery Process.Refer to Problem Determination for errors.

CSIRECVC-07 xxxx SPECIFIC DELETE FAILED,RECORD = kkkkkkkk

This message indicates the specified record was not deleted by theRecovery Process. Refer to Problem Determination for errors.

CSIRECVC-08 xxxx UNKNOWN RECORD = kkkkkkkk

The specified record (kkkkkkkk) should never have been created by theVerification System. This error would indicate that some other programin your CICS system is creating journal records with one of the CSIverification file ID's.

CSIRECVC-09 xxxx RECORD ADD FAILED

This message follows one or more format error messages when they occuron a record that was added during the update process. Refer to ProblemDetermination for errors.


Page 162 (Verification System) Messages

CSIRECVC-10 xxxx RECORD UPDATE FAILED

This message follows one or more format error messages when they occuron a record that was updated during the update process. Refer toProblem Determination for errors.

CSIRECVC-11 xxxx OCCURS ERROR FOR KEY = kkkkkkkk, SHOULD BE nnnn, ISnnnn

Each record in each verification file has an OCCURS depending on valuefollowed by a series of fields based on the OCCURS value. This messageindicates a record that does not have the value it should have.

CSIRECVC-12 xxxx FIELD ERROR FOR KEY = kkkkkkkk,FIELD nnnn, SHOULD BE nnnn, IS nnnn

Each record in each verification file has an OCCURS depending on value,followed by a series of fields based on the OCCURS value. This messageindicates a record that does not have the value it should have.

CSIRECVI-01 xxxx FILE INITIALIZATION COMPLETED OK

This is the only message that should be produced if everything is OK.One message will be generated for each file type (xxxx).

CSIRECVI-02 xxxx FILE OPEN ERROR, STATUS = ss

An open error ss (VSAM status for Cobol) has occurred for file type xxxx.Initialization is terminated.

CSIRECVI-03 xxxx WRITE ERROR ON KEY - kkkkkkkk,STATUS = ss

A write error ss (VSAM status for Cobol) has occurred for file type xxxx.Initialization is terminated.

CSIRECVI-04 xxxx FILE CLOSE ERROR, STATUS = ss

A close error ss (VSAM status for Cobol) has occurred for file type xxxx.

CSIRECVU-00

RLNKSRURLNKSDSRLNESDSRLNRRDSRLNKSFL

-

OPEN DATASET

PROCESSINGCLOSE DATASET

These informational messages are displayed during the updateprocessing in program CSIRECVU. Each message is displayed prior toCSIRECVU performing the function described in the message. If an erroroccurs during the update process, the last message displayed will indicatewhere the error occurred.


Messages (Verification System) Page 163

CSIRECVU-01 PROCESSING COMPLETED - TASKID(nnnnnnn)

This message appears if all updates occurred ok. Any other errorsindicate an error condition. The TASKID is the CICS task number for theCSIRECVU transaction.

CSIRECVU-02 KSDS READ UPDATE ERROR ON KEY 1001

This message appears if an error occurs during a CICS read update forkey 1001.

CSIRECVU-03 KSDS COPY ERROR

This message appears if an error occurs during a copy of keys 0001 - 0005to keys 1001 - 1005.

CSIRECVU-04 ESDS READ UPDATE ERROR ON RBA 42

This message appears if an error occurs during a CICS read update forinternal key 0003.

CSIRECVU-05 ESDS READ UPDATE ERROR ON RBA 140

This message appears if an error occurs during a CICS read update forinternal key 0006.

CSIRECVU-06 RRDS READ UPDATE ERROR ON RECORD 1

This message appears if an error occurs during a CICS read update forkey 0001.

CSIRECVU-07 RRDS COPY ERROR


CSIRECVU-08 KSFL READ UPDATE ERROR

This message appears if an error occurs during a CICS read update.

CSIRECVU-09 KSFL COPY ERROR


CSIRECVU-10 KSRU ADD ERROR

This message appears if an error occurs during a mass insert of keys 0001- 0005 to the empty file 'RLNKSRU'.

CSIRECVU-11 KSFL ADD ERROR

This message appears if an error occurs while re-adding key 0003 or 0004after the delete of the same record.


Page 164 (Verification System) Messages

CSIRECVU-12 xxxxxxxx NOT OPEN

This message appears if CSIRECVU is unable to open file "xxxxxxxx".Look for a VSAM error message on SYSLOG.


Page 165

APPENDIX A


APPENDIX A How to Code Commands Page 167

How To Code Commands (Syntax)

This section describes the rules for coding CSI-RECOV Commands and theirOperands. The meaning and use of the Commands themselves are not describedhere. The examples given here are intended only to clarify the coding syntax, notto show how to use a particular Command or Operand.

Commands are coded as one or more lines in a SYSIN file. Each Command maybe continued using any number of lines.

A Command may contain comments, which can be coded anywhere within theCommand. Comments may also be coded separately, rather than as part of aCommand.

Terminology

The special terms defined below are used to describe the Command syntax.

• COMMAND: A Command is a CSI-RECOV-defined Command namefollowed by Operands and comments. Each Command is defined andprocessed by CSI-RECOV as a single entity, and may or may not be relatedto other Commands.

• KEYWORD Operand: Keyword Operands are represented in Commanddescriptions with upper-case letters, and indicate CSI-RECOV-definedwords which either identify sub-Operands that follow the keyword inparentheses, or modify the action taken during the processing of aCommand.

• POSITIONAL Operand: Positional Operands are represented in Commanddescriptions with lower-case letters, and indicate user-provided data neededby the Command.

• SEPARATOR CHARACTER: A separator character is used to end anOperand, and to indicate the relationship of that Operand to otherOperands. The separator characters are: space, comma, left and rightparentheses, slash, and semi-colon.


Page 168 How to Code Commands APPENDIX A

• COMMENTS: CSI-RECOV allows you to code comments in the SYSIN file.Comments are for your own documentation and are printed, but notprocessed, with the Commands.

Coding CSI-RECOV Operands

CSI-RECOV Commands all have this general structure:

COMMAND-NAME Operands ... ;

The semi-colon (;) is optional, and signals the end of the Command. Anythingcoded after a semi-colon is ignored. The Command-name must be the first wordin a Command, terminated by a space. It is normally followed by Operandswhich further define the action to be taken by the Command. The Operandswhich are allowed after the Command-name are separated using one or morespaces. If an Operand requires one or more sub-Operands, the sub-Operands arecoded in parentheses in this manner:

COMMAND PARM-1 PARM-2(SUB-A(...) SUB-B) PARM-3...

where PARM-1, PARM-2, SUB-A, SUB-B, and PARM-3 are valid keyword orpositional Operands defined for the Command named "COMMAND". OnlyOperands defined as valid for PARM-2 may be coded as sub-Operandsfollowing PARM-2. The Operands PARM-1, PARM-2, and PARM-3 areconsidered to be at the same logical level, regardless of any sub-Operandsspecified for each of them. Operands and sub-Operands of all logical levelsfollow the same coding rules.

The Command-name, Operands, and separator characters may be preceded orfollowed by any number of spaces. This can be used to make Commands morereadable, and easier to maintain.

Keyword Operands can be coded in any order, unless the description of aCommand states otherwise. Some keywords may be defined as having one ormore prefixes which alter the meaning of the keyword.

Positional Operands may be coded in a variety of ways, to allow you to specifyany type of data. If the data needed for an Operand contains separator charactersor non-printable characters, code the Operand as a quoted string or as ahexidecimal string. If an Operand is defined as a number, you may code it eitheras a decimal number, or use hexidecimal notation. The relative position of eachpositional Operand within the Command determines the sequence in which theyare acted upon.



Coding Continuation

Any CSI-RECOV Command may span any number of input lines, by codingeither a "+" or "-" as the last non-blank character of each line which is to becontinued to the line following it. If a "-" is used as the continuation character,the Command is continued starting at the left margin of the following line. If a"+" is used, the Command is continued starting with the first non-blankcharacter of the following line. All data on the line up to, but not including, the"+" or "-" is used. The following examples will all have the same result:

COMMAND PARM-1 PARM-2(SUB-A(DATA) SUB-B) PARM-3

COMMAND PARM-1 PARM-2(SUB-A(DA+ TA) SUB-B) PARM-3

COMMAND PARM-1 PARM-2(SUB-A(DA-TA) SUB-B) PARM-3

COMMAND PARM-1 - PARM-2( - SUB-A(DATA) - SUB-B - ) - PARM-3

Continuation works in the same way regardless of whether it takes place in themiddle of a word, within a quoted string or comment, between Operands, orafter a semi-colon (;). It takes place as the lines are read, before any othercharacters are interpreted.


Page 170 How to Code Commands APPENDIX A

Coding Quoted Strings

Quoted strings are valid for any positional Operand, to allow you to:

• Code data that contains separator characters - 'NOT FOUND'

• Code data that would otherwise be interpreted as a keyword.

• Code data in hexidecimal notation - x'C8C5E7'

• Code lower case data - 'This will remain lower case'

To specify the quote character within a quoted string, code two consecutivequotes:

'THIS STRING CONTAINS ''QUOTES'' IN IT'

Coding Date Operands

Some Operands require a Julian date to be coded. The general format isYY/DDD, where YY is the year, and DDD is the day number (January 1 = 001,February 1 = 032, etc.). You must code exactly three digits for the day number.Coding the slash character (/) is optional.

You may specify a date that is relative to the current date by coding a "+" or "-"as the first character of the date. The number of years (optional) and days arethen added to or subtracted from the current system date. When you code arelative date, the number of days must contain three digits, but it may be anynumber up to 999.

Coding Time Operands

Some Operands require a time of day value to be coded. The format isHH:MM:SS.T, where HH is the hour, MM is the minutes, SS is the seconds, andT is the tenths of seconds. The seconds and tenths of seconds are optional, soHH:MM or HH:MM:SS are also valid formats. If you code it without punctuation(HHMMSST), you must specify all seven digits.



Coding Comments

It is often useful to put comments with the Operands. Since a semi-colon ";" endsthe parameter processing of a Command, anything coded after a semi-colon istreated as a comment. If continuation is specified after a semi-colon, thecomment is continued to the next line.

A more flexible method of coding comments is provided. A comment mayappear at any point that a separator character is valid, by coding "/* comment*/". Any characters may appear between the "/*" and "*/", and the commentmay be continued to any number of lines by using the normal continuationmethod. If you do not end the comment, or code a continuation character on theline, an error message is issued. In the following examples, the lower casecharacters represent data that are treated as comments:

COMMAND PARM-1;parm-2(sub-a(data) sub-b) parm-3

COMMAND PARM-1 /* comment for parm-1 */ - PARM-2( /* comment for parm-2 */ - /* more comments */ - SUB-A(DATA) - ) - /* a single comment can becontinued */


Page 173

APPENDIX B


APPENDIX B Journal Backup Record Formats Page 175

Journal Backup Record Formats

The following record layouts describe the formats of CSI-RECOV Journal Backuprecords. Journal Backup datasets are created using variable-length spannedblocked records. The format is determined by the FORMAT Operand of theOUTPUT BACKUP Command.

FORMAT(SHORT)

OFFSET LENGTH DESCRIPTION

000 (000) 2 "LL" field - Length of record002 (002) 2 "BB" field - Set to x'0000'004 (004) 2 Prefix length (includes LLBB fields)006 (006) 2 Length of Key (following prefix)008 (008) 2 Length of data Record (following prefix)010 (00A) 2 (reserved)012 (00C) 8 Dataset ID (from FCT)020 (014) 4 Date (packed 00YYDDD)024 (018) 4 Time (packed HHMMSST)028 (01C) 8 Journal Block Number (hex xxxxxxxx)036 (024) 2 Relative Record in Block (packed nnn)038 (026) 1 Journal ID (binary JID value)039 (027) 2 Source of this record:

FC =VSAM File ControlBJ = Batch Journal (FSI-JRNL)

041 (029) 8 APPLID (from SMF or APPLID parm)049 (031) 4 Transaction ID053 (035) 4 Terminal ID057 (039) 3 Task number (packed nnnnn)060 (03C) 2 Function Code:

RO = Read OnlyRU = Read for UpdateWU = Write UpdateWN = Write NewWD = (Write) Delete

062 (03E) 1 (reserved)063 (03F) 1 (reserved)

------------ End of Prefix --------------064 (040) variable Key field (RIDFLD)064 (040) variable Record Data (follows Key field)


Page 176 Journal Backup Record Formats APPENDIX B

FORMAT(LONG)


000 (000) 2 "LL" field - Length of record002 (002) 2 "BB" field - Set to x'0000'004 (004) 2 Prefix length (includes LLBB fields)006 (006) 8 Dataset ID (from FCT)014 (00E) 1 (reserved)015 (00F) 1 (reserved)016 (010) 2 Key length018 (012) 256 Key field (RIDFLD), Left justified,

x'00' filled274 (112) 4 Date (packed 00YYDDD)278 (116) 4 Time (packed HHMMSST)282 (11A) 8 Journal Block Number (hex xxxxxxxx)290 (122) 2 Relative Record in Block (packed nnn)292 (124) 1 (reserved)293 (125) 1 Journal ID (binary JID value)294 (126) 2 Source of this record:

FC = VSAM File ControlBJ = Batch Journal (FSI-JRNL)

296 (128) 8 APPLID (from SMF or APPLID parm)304 (130) 4 Transaction ID308 (134) 4 Terminal ID312 (138) 3 Task number (packed nnnnn)315 (13B) 2 Function Code:

RO = Read OnlyRU = Read for UpdateWU = Write UpdateWN = Write NewWD = (Write) Delete

317 (13D) 1 (reserved)318 (13E) 2 (work area for FSIRECOV)320 (140) 2 length of data record322 (142) 44 (reserved)

------------ End of Prefix --------------366 (16E) variable Record Data


APPENDIX B Journal Backup Record Formats Page 177

FORMAT(REDUCED)


000 (000) 2 "LL" field - Length of record002 (002) 2 "BB" field - Set to x'0000'004 (004) 2 Prefix length (includes LLBB fields)006 (006) 2 Length of Key (following prefix)008 (008) 2 Length of data Record (following prefix)010 (00A) 2 (reserved)012 (00C) 8 Dataset ID (from FCT)020 (014) 4 Date (packed 00YYDDD)024 (018) 4 Time (packed HHMMSST)028 (01C) 8 Journal Block Number036 (024) 2 Relative Record in Block (packed nnn)038 (026) 1 Journal ID (binary JID value)039 (027) 2 Source of this record:

FC =VSAM File ControlBJ = Batch Journal (FSI-JRNL)

041 (029) 8 APPLID (from SMF or APPLID parm)049 (031) 4 Transaction ID053 (035) 4 Terminal ID057 (039) 3 Task number (packed nnnnn)060 (03C) 2 Function Code:

RO = Read OnlyRC = Read change recordRU = Read for UpdateWC = Write change recordWU = Write UpdateWN = Write NewWD = (Write) Delete

062 (03E) 1 (reserved)063 (03F) 1 (reserved)

------------ End of Prefix --------------064 (040) variable Key field (RIDFLD)064 (040) variable Record Data (follows Key field) If FunctionCode

is RC or WC, this is a "Change record".Refer to the description that follows.


Page 178 Journal Backup Record Formats APPENDIX B

Format of " Change record"


000 (000) 4 original LLBB area004 (004) 1 change type. x'01' - read, x'04' write005 (005) 3 future008 (008) 4 "checksum" of original record012 (00C) 2 length of original "before" record014 (00E) 2 length of original "after" record016 (010) 2 length of change descriptor fields

------------ start of change descriptor fields --------------018 (012) 1 length of change field / skipped area

if x'80' bit is on, this is length of area thatwas not changed, 1-127.if x'80' bit is off, this is length of changeddata, 1-127. Data follows this byte.

019 (013) variable change field------------ above field(s) repeated for each change in the record --------------

Index

CSI-RECOV Page 179

- (continuation) ............................................167

+

+ (continuation) ...........................................167

1

1.5INPUT Command ..................................65

1.6INPUT Command ..................................65

1.7INPUT Command ..................................65

2

2.1INPUT Command ..................................65

A

AIXSORTOPTION Command.....................91

APPLIDINPUT Command ..................................66OUTPUT Command ..............................73

Archiving journals.........................................58ATTR

INPUT Command ..................................66OUTPUT Command ..............................73

ATTRIBUTE CommandBACKOUT.............................................101DELETE .................................................101DOSISAM..............................................101EMPTY.....................................................99FIXED.......................................................99FORCE ...................................................100NEWNAME ..........................................101UPDATE................................................100VARIABLE ..............................................99

AUTO Command

B

BACKOUTATTRIBUTE Command ......................101OUTPUT Command ..............................79

Backout RecoveryATTRIBUTE Command

BACKOUT......................................101DELETE ..........................................101

OUTPUT CommandBACKOUT........................................79

Sorting Requirements ............................90Terminology............................................12

BACKUPINPUT Command ..................................65Output Command ..................................73

Batch Journaling ......................................51, 52Batch Journals ................................................11BLKSIZE


C

CHRONOSORTOPTION Command.....................91

CICS Journal Recommendations .................34CICS Journals .................................................11Coding Operands ........................................166Commands

ATTRIBUTE Command.........................98AUTO Command .................................102Coding Syntax.......................................166Continuation Syntax ............................167INPUT Command ..................................63OUTPUT Command ..............................71SELECT Command ................................80SORTOPTION Command.....................90Syntax.......................................................61

Comments (syntax) .....................................169Continuation Syntax ...................................167CSI-ARMAN ..............................54, 66, 73, 102CSI-JOURNAL ...........................................7, 11Customizing CSI-RECOV

CSIRECDBCSIRECDDCSIRECDJOperands

BLKSIZE ...........................................24DEVICE.............................................24IOAREAS..........................................24LABEL...............................................25OPSYS ...............................................24REWINDI .........................................25REWINDO........................................25SYSNBRI...........................................24SYSNBRO .........................................25

Sample JCL ..............................................26

Index

Page 180 CSI-RECOV

D

DATAOUTPUT Command.............................. 78

Date Operands ............................................ 168DBERR

INPUT Command.................................. 67DEFAULT

SORTOPTION Command .................... 91DELETE

ATTRIBUTE Command...................... 101DL/I Log........................................................ 11DL/I Recovery .............................................. 55DL/I Reporting ........................................... 117DLICUM

SORTOPTION Command .................... 91DLILOG

INPUT Command.................................. 65Output Command ................................. 73

DLIRECVSORTOPTION Command .................... 91

DOSISAMATTRIBUTE Command...................... 101

E

EMPTYATTRIBUTE Command........................ 99

ERRORSOUTPUT Command.............................. 79

ESDSINPUT Command.................................. 68OUTPUT Command.............................. 74

F

FIELDSOUTPUT Command.............................. 75SORTOPTION Command .................... 92

FIXEDATTRIBUTE Command........................ 99

FORCEATTRIBUTE Command...................... 100OUTPUT Command.............................. 79

FormatJournal Backup record ........................ 173

FORMATOUTPUT Command.............................. 76

Forward RecoveryIntroduction.............................................. 7Terminology ........................................... 11

H

Hexidecimal Notation ................................ 168

I

INPUT Command1.5 ............................................................. 651.6 ............................................................. 651.7 ............................................................. 652.1 ............................................................. 65APPLID ................................................... 66ATTR ....................................................... 66BACKUP ................................................. 65BLKSIZE.................................................. 67DBERR..................................................... 67DLILOG................................................... 65ESDS ........................................................ 68JOURNAL............................................... 65MODNAME ........................................... 68REPORTS ................................................ 68SELECT ................................................... 69SORT........................................................ 69TITLE....................................................... 70WRAP...................................................... 70

InstallationCataloging CSIRECOV ......................... 17Core Image Library ............................... 16Minimum Library Requirements ........ 17Source Library Modules ....................... 16

Installing Journaling in your SystemActivating Journaling............................ 42CICS startup JCL.................................... 44FCT .......................................................... 42Initializing Journals ............................... 40JCT ........................................................... 36PCT .......................................................... 43PPT........................................................... 43SIT ............................................................ 43

IntroductionFeatures ..................................................... 9Migration Requirements....................... 13Provided by CICS .................................... 7Provided by CSI-JOURNAL................... 7Terminology ........................................... 11What is Recovery ..................................... 7

J

JOURNALfile size..................................................... 34

Index

CSI-RECOV Page 181

INPUT Command ..................................65Journal Backup

record format ........................................173

K

KEYSOUTPUT Command ..............................78

L

Lower Case Data..........................................168

M

MAXKEYSORTOPTION Command.....................94

MessagesCSIRECOV-0nnn ..................................139CSIRECOV-10nn ..................................151CSIRECOV-11nn ..................................155CSIRECVC-nnnn ..................................158CSIRECVI-nnnn....................................159CSIRECVU-nnnn..................................159

Migration Requirements ..............................13MODNAME


N

NEWNAMEATTRIBUTE Command ......................101

NULLFILEOUTPUT Command ..............................77

O

OperandsCoding Syntax ......................................166Comments .............................................169Continuation Syntax ............................167Dates.......................................................168Quoted Strings......................................168Time........................................................168

OPTIONPARMSORTOPTION Command.....................95

Output CommandBACKUP..................................................73DLILOG ...................................................73PRINT ......................................................73VSAM.......................................................73

OUTPUT CommandAPPLID....................................................73

ATTR ........................................................73BACKOUT...............................................79BLKSIZE ..................................................74DATA.......................................................78ERRORS ...................................................79ESDS.........................................................74FIELDS .....................................................75FORCE .....................................................79FORMAT .................................................76KEYS.........................................................78MODNAME ............................................76NULLFILE...............................................77REPORTS.................................................77SELECT ....................................................78TITLE........................................................78UPDATE ..................................................79

P

Preparing CICS for RecoveryAutomatic Journaling ............................30Automatic logging..................................30Bibliography............................................29Disk vs Tape............................................32One or Two Journals ..............................31Recommendations..................................34User Journals...........................................30

PRINTOutput Command ..................................73SORTOPTION Command.....................97

Q

Quoted Strings .............................................168

R

RECORDPARMSORTOPTION Command.....................95

ReportsFormats ..................................................104Output Print Report .............................106Parameter Edit Report .........................105Summary Reports.................................107VSAM Output Error Report................115

REPORTSINPUT Command ..................................68OUTPUT Command ..............................77SORTOPTION Command.....................95

S

Sample JCL

Index

Page 182 CSI-RECOV

CSIRECDJ ............................................... 26CSIRECJ1 .......................................... 59, 60

SELECTINPUT Command.................................. 69OUTPUT Command.............................. 78

SELECT Command(list) format and rules ........................... 84Alias......................................................... 87Examples................................................. 88field(list).................................................. 82How to enter........................................... 81keyword VSAMFUNC.......................... 86keyword VSAMSTAT ........................... 86keywords ................................................ 82Relational Operators ............................. 83Rules for DATE keyword ..................... 84Rules for numbers ................................. 84Rules for string values .......................... 85Rules for TIME keyword ...................... 84Selection Criteria.................................... 83

SEQERRORSORTOPTION Command .................... 96

Share option 4................................................ 52SORT

INPUT Command.................................. 69SORTALL

SORTOPTION Command .................... 91SORTOPTION Command

AIX........................................................... 91CHRONO ............................................... 91DEFAULT ............................................... 91DLICUM ................................................. 91DLIRECV ................................................ 91FIELDS .................................................... 92MAXKEY ................................................ 94OPTIONPARM ...................................... 95PRINT...................................................... 97RECORDPARM ..................................... 95REPORTS................................................ 95SEQERROR............................................. 96SORTALL................................................ 91SORTPARM............................................ 95SORTRECL ............................................. 94STOP........................................................ 97WORK ..................................................... 94

SORTPARMSORTOPTION Command .................... 95

SORTRECLSORTOPTION Command .................... 94

STOPSORTOPTION Command .................... 97

SyntaxCoding Operands ................................ 166Comments............................................. 169Continuation......................................... 167Date Operand....................................... 168Quoted Strings ..................................... 168Terminology ......................................... 165Time Operands..................................... 168

T

Time Operands............................................ 168TITLE

INPUT Command.................................. 70OUTPUT Command.............................. 78

U

UPDATEATTRIBUTE Command...................... 100OUTPUT Command.............................. 79

Using CSI-RECOVJournal Backup JCL ............................... 57Sample JCL ....................................... 59, 60

V

VARIABLEATTRIBUTE Command........................ 99

Verification and TestingCSIRECV0............................................. 127CSIRECV1............................................. 127CSIRECV2............................................. 131CSIRECV3............................................. 133CSIRECVC ............................................ 125CSIRECVI.............................................. 123CSIRECVU............................................ 124Messages ............................................... 158Problem Determination ...................... 134

VSAMOutput Command ................................. 73

W

WORKSORTOPTION Command .................... 94

WRAPINPUT Command.................................. 70

Documents

Reliant for VSE CSI-RECOVjournal records for both your VSAM and DL/I datasets in a single CSI-RECOV Journal Backup dataset. In summary, CSI-RECOV can save your company time and money