Reliant for VSE CSI-JOURNAL … · CSI-JOURNAL is a proprietary product of CSI International, Inc....

(COPYRIGHT © 2003, CSI INTERNATIONAL, INC.)

CSI-JOURNAL 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)without the express prior written permission.

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

C S I - J O U R N A L

VSAM BATCH JOURNALING

INSTALLATIONAND

OPERATIONS GUIDE

Release 3.0

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

TABLE OF CONTENTS

GETTING STARTED ............................................................................................................................1Introduction ......................................................................................................................................3

Benefits of CSI-JOURNAL .......................................................................................................4What is Recovery?.....................................................................................................................4Which Part is provided by CSI-JOURNAL?..........................................................................4Which Part is provided by CSI-RECOV?...............................................................................5Features of CSI-JOURNAL ......................................................................................................5

Migration Requirements .................................................................................................................6Installation.........................................................................................................................................8Customizing CSI-JOURNAL ..........................................................................................................11

CSIJRNDJ (Default Journal I/O module) ..............................................................................12CSIJRNDX (Journal I/O module for dual extents)...............................................................13Generating a custom I/O module ..........................................................................................14

USING CSI-JOURNAL .........................................................................................................................17Considerations..................................................................................................................................19Using VSAM Managed SAM for Batch Journals .........................................................................23Restrictions........................................................................................................................................26Compatibility ....................................................................................................................................27Activating CSI-JOURNAL ..............................................................................................................28Deactivating CSI-JOURNAL ..........................................................................................................30Option Table for CSI-JOURNAL....................................................................................................31Execution Time Overrides for CSI-JOURNAL.............................................................................37Commands and Operands ..............................................................................................................39

Syntax .........................................................................................................................................39Commands.................................................................................................................................40

DATASET Command........................................................................................................41JOURNAL Command .......................................................................................................44IDENTIFY Command........................................................................................................47CONTROL Command.......................................................................................................49START Command..............................................................................................................53STOP Command ................................................................................................................54GENERATE Command.....................................................................................................55EXEC Command ................................................................................................................56OPTION Command...........................................................................................................57SELECT Operand...............................................................................................................58

MESSAGES .............................................................................................................................................63

APPENDIX A ..........................................................................................................................................85How to Code Commands (Syntax) ................................................................................................87

APPENDIX B...........................................................................................................................................91Journal Record Format ....................................................................................................................93

CSI-JOURNAL/VSE INSTALLATION AND OPERATIONS GUIDE

Page 1

GETTING STARTED


Introduction Page 3

Introduction

CSI-JOURNAL is a system designed to provide your batch programs with thetype of journaling support for VSAM datasets that is provided by CICS for youron-line programs. This is a companion system to CSI’s CICS VSAM recoverysystem CSI-RECOV. The journals created by CSI-JOURNAL can be input to CSI-RECOV along with CICS created journals to provide total recovery for your on-line and batch systems.

YourApplicationPrograms

VSAMCSI-JOURNAL

BATCHJOURNALS

OptionalMessages

VSAMDATASETS

JournalOptionTable

"CSIJRN00"

LoadLibrary

Overview of CSI-JOURNAL


Page 4 Introduction

Benefits of CSI-JOURNAL

• You do not have to modify or re-compile your application programs to getBatch Journaling support when you use CSI-JOURNAL.

• You will not have to re-run batch jobs because an on-line VSAM dataset hasto be recovered. Batch updates can be merged with on-line updates fordataset recovery, archival or reporting purposes.

• Any number of VSAM datasets can be journaled concurrently to one or morebatch journals, which simplifies JCL and reduces storage requirements.

• Each journal can be defined as a single dataset which allows for the use ofsecondary allocation, or as a primary and secondary extent with automaticswitching, similar to CICS.

• Journaling messages can be generated to provide visual assurance that thejournaling process is working properly. You won't get to the end of a jobbefore finding out that no journal has been created.

• Batch journaling is controlled by a single Option Table. You have completecontrol over which VSAM datasets are journaled, and when and where theyare journaled.

In summary, CSI-JOURNAL, when used with CSI-RECOV, will save yourcompany time and money when a VSAM dataset is lost or damaged.

What is Recovery?

Forward Recovery is a process that restores a damaged dataset to the state it wasin prior to the point of damage.

Damage may be caused by hardware or software failure, or by human error, andthe extent of the dataset damage can vary from a single record in one dataset tomany datasets in several systems. Accordingly, the recovery process could bedifferent each time a failure occurs.

Which Part is provided by CSI-JOURNAL?

CSI-JOURNAL provides the facility to record VSAM dataset changes made bybatch programs to separate datasets called journals. These journals can be usedby a recovery package such as CSI-RECOV to perform the actual datasetrecovery.


Introduction Page 5

Which Part is provided by CSI-RECOV?

CSI-JOURNAL will not use these journal records to re-apply changes when adataset has been destroyed. This is where CSI-RECOV comes in. After you haverestored the damaged VSAM dataset (or datasets) from the latest backup tape,CSI-RECOV will re-apply changes made since the latest backup using thejournaled records created by CSI-JOURNAL and/or CICS.

Features of CSI-JOURNAL

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

• Complete selection control over which VSAM datasets will be journaledfrom which programs.

• No modifications required to any application programs.

• Journals can be created on Disk or Tape. Disk journals can be SAM or VSAMManaged SAM.


Page 6 Migration Requirements

Migration Requirements

The following sections cover the changes in the installation of CSI-JOURNALthat may be required if you are migrating from an earlier release.

Changes for Release 3.0

• You must regenerate your Journal Option Table to change its name toCSIJRN00.


• The internal format of the Journal Option Table has changed. You mustregenerate your CSIJRN00 table for this release of CSI-JOURNAL.

• A new VSAM interface architecture has been designed for the VSE/ESAplatform. This new interface intercepts VSAM Open/ Close calls to allowsystem wide services to make decisions on support requirements for thecurrently accessed VSAM file at the open rather than at access time, reducingresource requirements and logic path at access time significantly. This newarchitecture parallels the MVS platform interface allowing more integrationof common modules. The new architecture is called the BIM VSAMROUTERS (BIMVSR). Specifics on using the VSAM ROUTERS will bepresented later in this manual.

• With the introduction of the VSAM ROUTERS the older interface moduleCSIJRN10 has been replaced with CSIJRNIP. Activation requirements forCSI-JOURNAL have changed to incorporate the activation of the VSAMROUTERS. CSIJRNL still controls the activation/deactivation execution forCSI-JOURNAL.


• If you have jobsteps that open more than one journal dataset, you will needto review the ddnames assigned to these journals. CSI-JOURNAL nowrequires that journal ddnames be unique within the first 5 characters, if morethan one will be required within the same jobstep.


Migration Requirements Page 7

• CSI-JOURNAL now supports journals defined with a primary and alternateextent. This provides an automatic switching facility for full journal files,similar to CICS.

If you wish to use this new feature, and you have generated your own I/Omodules using the CSIIOGEN macro, you will need to regenerate themusing the CSIIOGEN macro from this release of CSI-JOURNAL. You mustalso add the following operand to your CSIIOGEN options: EOXPT=YES.


• CSI-JOURNAL supports a user exit point that can be used to alter thenormal journaling activity. Refer to source member A.CSIJRNXP foradditional information.


• Release 1.3 supports the new VSE/ESA Operating System. CSI-JOURNALcan journal the VSAM activity from programs running in “Dynamic” and/or“Static” Partitions.

Changes from Release 1.1

• CSI-JOURNAL can now create journals in one of two formats. A newoperand (FORMAT) has been added to the JOURNAL command to specifywhich format is to be created. The default is to use the new shorter format.Our VSAM Recovery Product, CSI-RECOV, can input this new format,without any parameter changes. If you are using any other program toprocess your batch journals, you will need to add the operandFORMAT(LONG) to the JOURNAL command(s) in your Journal OptionTable.

• The CSI-JOURNAL module CSIJRN20 has been combined with moduleCSIJRN11. This reduces the partition space requirements by 20k. You candelete the old module CSIJRN20 from your load libraries.

• The I/O module generation macro CSIIOGEN has been changed. If you havegenerated any of your own I/O modules, you must re-assemble them withthe new macro.

• Two new operands have been added, STARTCODE and STOPCODE. Thesecan be used to prevent unauthorized starting and stopping of CSI-JOURNAL.


Page 8 Installation

Installation

The CSI-JOURNAL programs described in this manual run under VSE, and aredistributed on an unlabeled tape or cartridge. When this tape is loaded into yourReader Queue, there will be one POWER job which will catalog the followingmodules to your libraries:

Source Modules

E.CSIIOGEN I/O Module Customization MacroA.CSIJRNDJ Journal I/O Module Sample Macro CallA.CSIJRNDX Journal I/O Module Sample for dual extentsA.CSIJRN00 Journal Option Table SampleA.CSIJRNXP User Exit Parameter DefinitionsA.CSIJRNXS Copybook for (short) format journal recordsA.CSIJRNXL Copybook for (long) format journal records

Note: In a VSE/SP or VSE/ESA library, these members are namedmember.sublib (eg. CSIIOGEN.E).

Load Modules

CSIJRNL Batch journaling control moduleCSIJRN01 Override anchor moduleCSIJRNIP SVA module to trigger journalingCSIJRN11 Journaling moduleCSIJRNDJ Default Journal I/O Access ModuleCSIJRNDX Journal I/O Access Module with dual extent supportBIMVSRCM Routing Facility command moduleBIMVSROP Routing Facility Open SVC routerBIMVSRCL Routing Facility Close SVC routerBIMVSRPO Routing Facility Post Open handlerBIMVSRPC Routing Facility Post Close handlerBIMVSRTB Routing Facility product tableBIMVSRJE Routing Facility end-of-job handlerBIMVSROE Routing Facility SVC 14 interceptBIMVSRSC Routing Facility storage anchor for CloseBIMVSRSO Routing Facility storage anchor for Open


Installation Page 9

Installation Step 1.

Mount the distribution tape on a tape drive and enter the followingPOWER/VSE command on the console:

S RDR,cuu

where “cuu” is the address of the tape drive.

Installation Step 2.

Alter the POWER job (CSIJRNL) that was loaded in the reader queue to run in apartition that has labels established for linkediting. This job has a pausestatement that allows you to enter a “LIBDEF” statement if necessary.

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

Installation Step 3

When job CSIJRNL starts up, it will pause allowing you to enter “// LIBDEF”statements. You must enter a “// LIBDEF” statement with the “TO=“ option forload and source libraries unless they have already been set using permanentLIBDEFs.

The modules for CSI-JOURNAL must be cataloged into a library that is in eachpartition's permanent search chain.

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/SP AND ABOVE, USE THE FOLLOWING >>>>* // 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.


Page 10 Installation

• 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-JOURNAL” starting on page 11 todetermine if the I/O module CSIJRNDJ cataloged in the Load Library in step 3 issuitable for your environment. If it is not, make the necessary changes to thedefault module and generate any additional modules that may be required ifyou need journals for more than one device type or block size.

Installation Step 5

Review the section “USING CSI-JOURNAL” starting on page 17 for an overviewof batch journaling and for assistance in generating your Journal Option Table.


Customization Page 11

Customizing CSI-JOURNAL

CSI-JOURNAL uses customizable I/O modules to write to the journals. Adefault I/O module has been provided in both source and object form.Customization of this module may be required to change device type, blocksize,or other options defined below.

Macro CSIIOGEN has been provided to customize the default I/O module or togenerate additional I/O modules to be used for varying the formats of journalscreated by CSI-JOURNAL. If you are generating additional I/O modules, thenames used for your I/O modules should NOT begin with the letters CSI. If theydo, CSI-JOURNAL may mistake your module name for one of its internalmodules.


Page 12 Customization

CSIJRNDJ (Default Journal I/O module)

Module CSIJRNDJ is the default I/O module used by CSI-JOURNAL to accessjournal datasets. The MODNAME operand of the JOURNAL 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 you may decide to write your journals directly to tape. To changethe default I/O module, generate a custom module and catalog it as CSIJRNDJ.

Listed below are the operands that were used to generate module CSIJRNDJ:

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

OPSYS=VSE, XBLKSIZE=32767, XIOAREAS=NO, XDEVICE=DISK

This macro call and its associated JCL is supplied in member A.CSIJRNDJ. 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.CSIJRNDJ, be sure to change thedefault values as required for your system.



CSIJRNDX (Journal I/O module for dual extents)

Module CSIJRNDX is a pregenerated I/O module that can be used with theMULTIPLE operand of the JOURNAL command to generate a journal withprimary and alternate extents. The MODNAME operand of the JOURNALcommand is used to provide the name of this module.

Listed below are the operands that were used to generate module CSIJRNDX:

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

OPSYS=VSE, XBLKSIZE=32767, XIOAREAS=NO, XDEVICE=DISK, XEOXPT=YES

This macro call and its associated JCL is supplied in member A.CSIJRNDX. Tochange its' options, or to generate other I/O modules with dual extent support,you may move this member to your text editor or code it manually as shown inthe example later on.



Generating a custom I/O module

To generate an I/O module, use the CSIIOGEN macro described below. Anexample of how 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.

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

OPSYS=VSE, XBLKSIZE=32767|nnnnn, XIOAREAS=NO|YES, XDEVICE=DISK|TAPE, XEOXPT=NO|YES, XSYSNBRO=SYS005|SYSnnn, XLABEL=NO|STD, 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 journal. 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 DISK journals, you must specify theBLKSIZE as 8 greater than you actually want. This is aVSE DTF requirement.

CSI-JOURNAL creates single extent journals in VBSformat (variable blocked spanned) which allows logicalrecords to span multiple blocks. CSI-JOURNAL createsdual extent journals in VB format which does not allowlogical records to span multiple blocks. The recordformat in the DTF is “undefined”, and CSI-JOURNALdoes its own blocking.

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 journaldataset.

EOXPT=NO|YES

Specifies that dual extent support is desired. Thissupport is required if the MULTIPLE operand isspecified in the JOURNAL command.



SYSNBRO=SYS005|SYSnnn

For tape journals. This is the SYSnnn to be used foraccessing the tape drive during Output operations. Thisvalue can be overridden by the JOURNAL command.

LABEL=NO|STD

For tape journals. This option defines whether or not thetape is labeled (specify NO for unlabeled tapes and STDfor standard labeled tapes).

REWINDO=UNLOAD|REWIND|NORWD

For tape journals. 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 unloading

it.• NORWD will leave the tape positioned as is.

EXAMPLE:

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

// JOB jobname// OPTION CATAL PHASE CSIJRNDJ,*// EXEC ASSEMBLYCSIJRNDJ CSIIOGEN, X

OPSYS=VSE, XDEVICE=TAPE, XBLKSIZE=32767

END/*// EXEC LNKEDT/&

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


Page 17

USING CSI-JOURNAL


Using CSI-JOURNAL (Considerations) Page 19

Considerations

Before the description of how to set up and use CSI-JOURNAL, we have listed anumber of things to consider. Some of these issues may influence your approachto batch journaling, and we recommend that you read the following sectionbefore setting up CSI-JOURNAL on your system. Only batch journaling isdiscussed here, as CICS journaling and dataset recovery is fully covered in thedocumentation for CSI-RECOV (VSAM Recovery system).

Purpose of journaling

Journaling itself does not have any benefit. CSI-JOURNAL is designed to be usedwith CSI-RECOV to provide VSAM dataset recovery. However, the journalrecords that it creates can also be used by programs you may write to suit otherneeds. CSI-JOURNAL is totally independent of the application programs thatactually update the VSAM datasets. This makes it ideal to use for implementing“add-on” applications that are driven by the journaled updates of existingsystems.

What to journal

CSI-JOURNAL can selectively journal any type of VSAM I/O: read only, readfor update, update, add, delete. The type of I/O that you want journaled isdescribed to CSI-JOURNAL in a control table, on a dataset-by-dataset basis ifnecessary. Forward Recovery requires only updates, adds and deletes to bejournaled, but if you use the journal for other purposes, you may need to journalthe read requests also. If you journal read for update requests, CSI-JOURNALwill normally journal only the records which are actually updated or deleted.This prevents batch programs, which usually update a small percentage of therecords they read, from filling the journal with unneeded records.

What the journal looks like

The journals created by CSI-JOURNAL can be either SAM or VSAM ManagedSAM datasets (disk or tape). They contain variable-length spanned blockedrecords. The journal record format created by CSI-JOURNAL is the same formatproduced by CSI-RECOV's OUTPUT BACKUP. The journal record format isdescribed in “APPENDIX B” on page 93.


Page 20 (Considerations) Using CSI-JOURNAL

Journal dataset management

You must create a separate journal dataset for each partition that will be usingCSI-JOURNAL. The SAM access method does not support concurrent journalingfrom multiple partitions.

Since you probably will have multiple job steps creating journal records that youwant grouped together, you need to implement a method for combining thesejournal records. CSI-RECOV can be used to merge CSI-JOURNAL (and CICS)journal records into a single “journal backup” dataset. A standard sort/mergeutility could also be used to combine multiple CSI-JOURNAL datasets.

Another alternative is to define each partitions journal dataset as a VSAMManaged SAM dataset, using IBM's VSAM Space Management for SAM Feature.This allows new records to be added to the end of an existing dataset,eliminating the need to merge several datasets together. The next section in thismanual provides step-by-step procedures for using VSAM Managed SAMjournals. Refer to IBM publication “Using the VSE/VSAM Space Managementfor SAM Feature” SC24-5192 for additional information. (Other DASDmanagement systems may provide similar functions.)

The methods described above could be used in combination. For example, eachupdate step in a job could create a “work” journal dataset (standard SD orVSAM Managed SAM), and CSI-RECOV (or a sequential file copy utility) couldbe executed after each update step to copy the “work” journal to the end of aVSAM Managed SAM dataset, thus accumulating the journal records of eachsuccessful update step.

Primary / alternate extent journals

CSI-JOURNAL incorporates the ability to manage multiple journal extents for asingle journal entity much as CICS manages its journals. Command operandsallow users to define a journal with two extents eliminating the possibility thatthe application job will be terminated if a journal fills. With dual extents defined,the user has the ability to offload the filled extent while the application job isrunning. By archiving the data on the filled extent, the user frees the journal to beoverwritten when the alternate or second extent has been filled and CSI-JOURNAL requests authority to switch back to the other extent.

Console messages to the operator requiring responses, allow the operator tocontrol the use of the journals defined for the application's job. There is a dangerthat the operator may fail to start an archive job to offload the filled journalextent, and merely allow CSI-JOURNAL to overlay the previous extent's journalrecords. This danger is not minimized by any built-in controls in CSI-JOURNAL.The intent of this feature is to eliminate the loss of time and resources when jobsfailed because available journal space was insufficient.


Using CSI-JOURNAL (Considerations) Page 21

There is a caveat in the dual extent journal scheme. The BSAM logic used towrite to the journal has no support for secondary extents allocated to the filespace defined. This means that the dual extents of the journal can only handlethe primary space allocated to the file. Therefore, sufficient primary space mustbe available on the DASD device to allow a sufficiently large journal extent to bedefined for both the first and second extents of the dual extent journal.

Dual extent journals cannot be used by more than one step in a multi-step job,unless the journals are archived between application steps. CSI-JOURNAL doesnot have adequate controls to carry journal extent status information across stepboundaries. Therefore, for multiple step jobs, a separate set of dual journalextents must be setup to handle each step of the job.

CSI-JOURNAL creates single extent journals in a VBS format (variable spannedblocked). This allows single records to span multiple blocks. Dual extent journalscannot allow this, because a single record could begin in one extent, and end inanother. Therefore, dual extent journals are created in a VB format (variableblocked). This means that you must choose a BLKSIZE for your dual extentjournals that will be large enough to contain the largest VSAM record to bejournaled, plus the journal record prefix generated by CSI-JOURNAL. Refer toAppendix B of this manual for the formats and lengths of the journal recordprefix.

This feature is activated via the MULTIPLE, PSUFFIX and ASUFFIX operands ofthe JOURNAL command. This feature is not available on systems prior toVSE/SP2.

Journal dataset labels

When CSI-JOURNAL opens a journal dataset, a DLBL or TLBL must be providedin the JCL or in standard labels. Since most journaling will go to the samedatasets, you can save a lot of JCL changes by putting the DLBL/TLBL in thestandard label area. If you need to override the label information for a particularjob step, you can put the required DLBL/TLBL in the job step.

Alternate indexes

CSI-JOURNAL processes an alternate index as a Key Sequence Data Set (KSDS).The name of the PATH that the application program opens is the dataset nameused by CSI-JOURNAL. The alternate key, used by the application program toaccess the data records, is the key that is recorded in the journal.


Page 22 (Considerations) Using CSI-JOURNAL

VSAM Share Option 4

Concurrent updates between Batch programs and CICS transactions cannot berecovered properly, even with VSAM share option 4, because the time-stamp onCICS journal records is accurate only to one tenth of a second. This is notaccurate enough to guarantee the correct sequencing of updates during recoverywhen the same VSAM record is updated by CICS and a Batch program duringthe same tenth of a second.


Using CSI-JOURNAL (VSAM-Managed-SAM) Page 23

Using VSAM Managed SAM for Batch Journals

The easiest way to create and manage Batch Journals for CSI-JOURNAL is todefine them using IBM's VSAM Managed SAM feature. The following stepsdescribe how to define and use this feature. Refer to IBM publication “Using theVSE/VSAM Space Management for SAM Feature” SC24-5192 for additionalinformation.

1. Define Journals to VSAM

The first step is to use IDCAMS to define your batch journals. CSI-JOURNALrequires a separate journal file for each partition. This is easy to do using VSAMManaged SAM:

DEFINE CLUSTER ( -NAME(CSIJRNL.FILE.BG) -VOLUMES(volser) -RECORDS(pri sec) -RECORDSIZE(4096 32761) -RECORDFORMAT(U) -REUSE -NOALLOCATION -NONINDEXED ) -

CATALOG(your.cat.name)

• You will need a DEFINE CLUSTER command for each partition that will beusing CSI-JOURNAL.

• Note that the Cluster name must end with the partition ID as shown in thisexample.

CSIJRNL.FILE.BGCSIJRNL.FILE.F9CSIJRNL.FILE.F8etc.

• The RECORDS operand specifies the primary and secondary spaceallocation in terms of number of records.

• The RECORDSIZE operand specifies the average and maximum record sizeto be written to the journal. This must agree with the options you selected inthe CSIIOGEN customization process.


Page 24 (VSAM-Managed-SAM) Using CSI-JOURNAL

• CSI-JOURNAL creates journals using a DTF with a RECORDFORMAT ofundefined (U).

• The NOALLOCATION operand causes the Clusters to be defined, but nospace is allocated until they are opened.

2. Add Journal labels to Standard Labels

You can add the following DLBL to your Standard Labels:

// DLBL JOURNAL,'%CSIJRNL.FILE',,VSAM,CAT=ucat, - DISP=(OLD,KEEP)

• The '%' in the first position of the dataset name will cause a “partitiondependent” name to be generated. These dataset names will be the same asthe ones defined in step 1 above.

• The DISP=(OLD,KEEP) will cause the first journaled job to allocate spaceand physically create the journal. The following journaled jobs will extendthe journal, adding the new journal records to the end of the extent.

• The same DLBL can be used to access and create/extend the journal dataset.

3. Backing up and/or Merging Journal Datasets.

At the end of each day, you will probably want to combine all of your batchjournals into a single backup file and reset the information contained in thejournals.

The following is a sample of the type of job that you could use to combine thejournals from each partition into a single journal backup:

// DLBL JRNBG,'CSIJRNL.FILE.BG',,VSAM,CAT=ucat,DISP=(OLD,KEEP)// DLBL JRNF9,'CSIJRNL.FILE.F9',,VSAM,CAT=ucat,DISP=(OLD,KEEP)// DLBL JRNF8,'CSIJRNL.FILE.F8',,VSAM,CAT=ucat,DISP=(OLD,KEEP)// TLBL OLDBKUP,'JOURNAL.BACKUP'// ASSGN SYS004,180// TLBL NEWBKUP,'JOURNAL.BACKUP'// ASSGN SYS005,181// EXEC CSIRECOV,SIZE=AUTOINPUT BACKUP(JRNBG,JRNF9,JRNF8) SORTINPUT BACKUP(OLDBKUP/SYS004)OUTPUT BACKUP(NEWBKUP/SYS005)/*/&


Using CSI-JOURNAL (VSAM-Managed-SAM) Page 25

4. Re-Initializing Batch Journals.

After you have backed up your Batch Journals, you will want to reset them sothat future journaling will start at the beginning of each partitions journaldataset.

Your Journal Datasets can be reset in one of two ways:

1. You can access the Journal Dataset for backup specifying aDISP=(OLD,DELETE) on the DLBL.

This will cause the file to be reset after a successful close.

2. The second way to reset the Journal Dataset is to use IDCAMS to DELETEand DEFINE the Journal Dataset as shown in step 1.

The first reset option can cause the Journal Dataset to be reset prior to successfulbackup if your backup product closes the input prior to creating the output. Thiscan happen with CSI-RECOV.


Page 26 (Restrictions) Using CSI-JOURNAL

Restrictions

CSI-JOURNAL is designed to journal the VSAM activity of batch applicationprograms. Nearly all types of VSAM access are supported without modificationof user programs. There are, however, a few situations in which journaling is notsupported.

• CICS. Since CICS has its own journaling facility, CSI-JOURNAL specificallyexcludes all VSAM requests made by CICS. This also applies to any datasetthat is opened by a program executing in the same partition as CICS, such asa program in an ICCF interactive partition.

• Control Interval Access. Any VSAM dataset requests that use controlinterval access will not be journaled. Control interval access does not dealwith logical records, and therefore cannot be journaled. This will normallyaffect only system utility programs.

• Chained RPLs. This method of issuing VSAM requests is available only toassembler language programs, and is normally used only by system utilityprograms. CSI-JOURNAL will journal only the request specified by the firstor only RPL.

• VSAM share option 4 cannot be relied on to provide recovery for concurrentupdates between batch programs and CICS transactions because the time-stamp on CICS journal records is accurate only to one tenth of a second. Thisis not accurate enough to guarantee the correct sequencing of updatesduring recovery when the same VSAM record is updated by CICS and abatch program during the same tenth of a second.

• VSAM Managed SAM. CSI-JOURNAL cannot journal these types ofdatasets.


Using CSI-JOURNAL (Compatibility) Page 27

Compatibility

CSI-JOURNAL generally works with most other VSAM file support products.However, care must be exercised when initiating the products to ensure that theorder of support functions is logical. Generally, VSAM compressors and othersimilar products should be initiated before CSI-JOURNAL.

Softwork’s VSAM compression package, “Capacity Plus for VSAM”, uses aVSAM “registry” control file that should be excluded from journaling by CSI-JOURNAL. Add a “DATASET” command for the registry control file to yourJournal Options Table specifying “JREQ(NONE)”. This will prevent problemsduring VSAM open requests when CSI-JOURNAL is active. Refer to the section“Option Table for CSI-JOURNAL” on page 31.

LEGENT's file compression product, “Extend-DASD”, will only work with CSI-JOURNAL for VSAM files that are both journaled and compressed. That is, bothEXTEND-DASD and CSI-JOURNAL are “managing” the file. If EXTEND-DASDdoes not manage a VSAM file, CSI-JOURNAL will lose control of it during fileopen. This is because EXTEND-DASD “unhooks” CSI-JOURNAL for VSAM filesthat are not compressed.


Page 28 (Activating) Using CSI-JOURNAL

Activating CSI-JOURNAL

CSI-JOURNAL is activated as an independent extension of the operating system.From this vantage point, it monitors the opening of each VSAM dataset (exceptin CICS partitions), and interrogates an option table to determine if the datasetis to be journaled. CSI-JOURNAL is activated system-wide, that is, it is in effectfor all partitions of a VSE system.

Before CSI-JOURNAL can be activated, the modules on the installation tapemust be cataloged into a library that is in each partition's permanent searchchain. In addition,several modules must be loaded into the Shared Virtual Area(SVA):

// JOB CSIJRNL LOAD SVA PHASES FOR CSI-JOURNAL/* THIS JOB MUST EXECUTE IN PARTITION BG// OPTION LOG// LIBDEF PHASE,SEARCH=USRLIB1.CSIJRNL SET SDL BIMVSROP,SVA BIMVSRCL,SVA BIMVSRPO,SVA BIMVSRPC,SVA BIMVSRTB,SVA BIMVSRCM,SVA BIMVSRJE,SVA BIMVSR0E,SVA (‘0’ IS A ZERO) CSIJRN00,SVA (optional, see note below) CSIJRNIP,SVA/*/&

Note: The journal option table CSIJRN00 can be added to the SVA forimproved VSAM open performance. If it is not loaded into the SVA, itwill be loaded into the partition GETVIS area.

It is recommended that after testing has been completed and CSI-JOURNAL hasbeen moved into production, that this JCL be incorporated into your ASI PROC.

Once the SVA has been loaded, execute program CSIJRNL followed by a STARTcommand (Refer to the section “START Command” on page 53 for details).


Using CSI-JOURNAL (Activating) Page 29

The following example could be put in your ASI PROC, or used in a separate job,to activate CSI-JOURNAL:

// EXEC PGM=CSIJRNL,SIZE=CSIJRNL START STARTCODE('authcode')/*

After CSI-JOURNAL has been activated, the option table and any JCL-suppliedoverrides will determine which VSAM datasets are to be journaled.


Page 30 (Deactivating) Using CSI-JOURNAL

Deactivating CSI-JOURNAL

CSI-JOURNAL will not have to be deactivated under normal circumstances. Theoption table and JCL overrides should provide all the flexibility needed forcontrolling the operation of CSI-JOURNAL. For system maintenance ordebugging severe VSAM problems, however, it may be necessary to totallyremove CSI-JOURNAL from your system. To stop CSI-JOURNAL, executeprogram CSIJRNL followed by a STOP command (Refer to the “STOPCommand” on page 54 for details). The following example will accomplish this:

// JOB jobname// EXEC PGM=CSIJRNL,SIZE=CSIJRNL STOP STOPCODE('authcode')/*/&

After CSI-JOURNAL has been deactivated, any batch journaling already inprogress will continue until the VSAM dataset is closed, but CSI-JOURNAL willno longer receive control when VSAM opens datasets. CSI-JOURNAL andVSAM will be returned to the state they were in before CSI-JOURNAL wasactivated. To re-activate CSI-JOURNAL, simply execute CSIJRNL with theSTART command.

BIMVSR Deactivation

The VSAM Routers can be manually deactivated to remove them from theOpen/Close logic trail. This should be done only after all products that are usingthe router services have been already deactivated. The following Job Stream willremove all system “hooks” implanted by the router activation initiated by CSI-JOURNAL or any of the other BIM/CSI products.

// JOB jobname RESET SDL/SVA// EXEC BIMVSRCM,PARM=‘SHUT11’/*/&


Using CSI-JOURNAL (Option Table) Page 31

Option Table for CSI-JOURNAL

CSI-JOURNAL uses an option table to control the journaling of VSAM activity.When a VSAM dataset is opened, CSI-JOURNAL searches the option table forentries with selection criteria that match the dataset name and the environment(job name, program name, etc.). You code the option table and compile it usingCSIJRNL, then catalog it to a load library as phase CSIJRN00 using the standardlinkage editor. The option table can then be optionally loaded into the SVA forfaster access during VSAM opens.

The option table consists of four types of entries: DATASET, JOURNAL,IDENTIFY, and CONTROL. There may be any number of each type of entry, andentries of different types may be intermixed in any convenient order. However,for two of the types, DATASET and IDENTIFY, the sequence of the entries of thesame type may be important.

The DATASET table entries are searched in the same order as they were coded,and if more than one table entry matches the dataset being opened, the first onefound is the one that is used. The DATASET table entry refers to a JOURNALtable entry, which defines the attributes of the journal dataset to be used.

The JOURNAL table entries may be specified in any order, and are selected bythe Journal ID (JID) from the previously selected DATASET table entry. EachJOURNAL table entry contains the ddname and other attributes of the physicaljournal dataset.

The IDENTIFY table entries are searched only if the dataset is to be journaled.The IDENTIFY table entries are searched in the same order as they were coded,and if more than one table entry matches the selection criteria, the first one foundis the one that is used. The IDENTIFY table entry provides information to beused to identify the source of the journal records (equivalent of CICS TRANID,TERMID, etc.).

The CONTROL entries are used to specify optional messages you wantdisplayed for certain VSAM and/or journaling events. The CONTROL tableentries are treated somewhat differently than the DATASET and IDENTIFYentries. To allow you to trace VSAM activity without journaling, the CONTROLtable entries are searched even if the dataset being opened is not going to bejournaled. You probably will not specify trace messages in the option table fornormal situations, but the facility may be useful for debugging systems withoutchanging programs or JCL.


Page 32 (Option Table) Using CSI-JOURNAL

The other unique feature of CONTROL entries is that instead of using theoptions from the first entry that matches the SELECT criteria, the options fromall entries that match are combined. This could be used, for example, to allowone set of criteria (such as dataset name) to determine which messages todisplay, and another set of criteria (such as job name) to determine thedestinations to which the messages should be routed.

The following example shows how to generate and catalog the CSI-JOURNALoption table, CSIJRN00. Comments are shown in lower case for clarity. ProgramCSIJRNL requires DLBLs and EXTENTs for system files IJSYS01 and IJSYSLN.These can be the same system files that are normally defined in standard labelsfor your regular compile and link jobs.

// JOB CSIJRN00 catalog option table// LIBDEF CL,TO=... define library for lnkedt// OPTION CATAL set catalog option PHASE CSIJRN00,*,SVA name and type of phase// EXEC CSIJRNL,SIZE=CSIJRNL GENERATE /* create option table */ - STARTCODE('authcode') - STOPCODE('authcode') DATASET NAME(...) - JID (...) - JREQ(...) JOURNAL JID (...) - DDNAME(...) IDENTIFY ... CONTROL .../*// EXEC LNKEDT catalog into library/&

If you are using a disk space manager product, you may be required to supplyspecific DLBLs and EXTENTs for IJSYS01 and IJSYSLN. This is required if anyerror occurs opening one of these files.

Note that any partitions that have open VSAM datasets will not be affected bythe new version. Also, if you have loaded a previous version of CSIJRN00 intothe SVA, you must re-load it into the SVA before the new version will take affect.If you choose not to have the option table SVA-resident, the new version willtake effect at the first VSAM open of the next job step in each partition.

If CSI-JOURNAL detects any errors in the table, it will not produce an optiontable module, and the link edit will not catalog a new version of CSIJRN00. Totest a new version of the table before loading it into the SVA, run your test jobswith a “LIBDEF CL,SEARCH=(...,SDL)” JCL statement, where “...” represents thelibrary containing the new CSIJRN00 to be tested. This will cause the SDL (SVApointers) to be searched after library “...”, which prevents the old version ofCSIJRN00 from being used.



Example Journal Option Table

Shown below is an example of a complete Journal Option Table. Following theexample is a description of each of the entries specified:

12345678910111213141516171819202122232425262728293031323334

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8

GENERATE - STARTCODE('STARTIT') - STOPCODE('STOPIT') DATASET NAME(*) - JREQ(NONE) - SELECT(INCLUDE(PROGNAME(CSIRECOV IDCAMS))) DATASET NAME(CSI.KSDS.DATA/RLNKSDS - CSI.ESDS.DATA/RLNESDS) - JID (01) - JREQ(ALL) DATASET NAME(CSI.KS.* CSI.ES*) - JID (01) - JREQ(ALL) - SELECT(INCLUDE(PROGNAME(CSIPROG1))) DATASET NAME(CSI.KS* CSI.ES*) - JID (02) - JREQ(RU WU WN WD) - SELECT(EXCLUDE(PROGNAME(CSIPROG2))) JOURNAL JID (01) - DDNAME(CSIJRNL) - MODNAME(CSIJRNDJ) JOURNAL JID (02) - DDNAME(CSIJRNL) - MODNAME(CSIJRNDJ) IDENTIFY - SELECT(INCLUDE(DATASET(CSI.KS* CSI.ES*) - PROGNAME(CSIPROG*)) - APPLID('SPECIAL') IDENTIFY - SELECT(INCLUDE(DATASET(*))) - APPLID(JOBNAME) CONTROL - SELECT(INCLUDE(DATASET(*))) - STATS(DEST(CONSOLE) JOPEN JCLOSE)

Notes on example Journal Option Table

Lines 1 through 3:The GENERATE command instructs CSI-JOURNAL to build aJournal Option Table. This command also provides passwords tobe used for activating and de-activating CSI-JOURNAL. TheSTARTCODE and STOPCODE specified here must also bespecified on the START and STOP commands..

Lines 4 through 18:This example contains four DATASET commands. The sequenceof the individual commands can be very important. CSI-JOURNAL will use the first DATASET command that matchesthe NAME operand, and any SELECT requirements.



You normally want to place the most restrictive DATASETcommands first, and the least restrictive commands last.

DATASET commands that use specific VSAM cluster namesshould usually appear before commands that use generic clusternames, unless very specific SELECT operands are specified, suchas the first example shown in Lines 4 through 6.

The contents of the SELECT operand should also be used whenyou are determining the order of your DATASET commands.SELECT operands that INCLUDE specific jobs or programsshould usually be placed before DATASET commands thatEXCLUDE specific jobs or programs.

Lines 4 through 6:The first DATASET command uses a generic dataset name (*) tocause all datasets to match the entry. The SELECT operandlimits the matches to only include programs CSIRECOV andIDCAMS.

The JREQ(NONE) specifies that no journaling should occur forany VSAM datasets processed by programs CSIRECOV andIDCAMS.

This DATASET command is specified first to prevent any otherDATASET commands from possibly matching, and causingjournaling to occur for these specific programs.

Lines 7 through 10:The second DATASET command specifies two specific VSAMdataset names.

Since no SELECT operand has been specified, any job orprogram referencing either of these two VSAM cluster will havejournaling performed.

The JREQ(ALL) specifies that all I/O requests against thesedatasets should be journaled to the journal dataset defined byJID(01) which is defined by the JOURNAL command in Lines 19through 21.

The cluster names are followed by a ddname RLNKSDS andRLNESDS. This causes CSI-JOURNAL to uses these names asthe ddnames in the journal records. If these operands areomitted, CSI-JOURNAL will use the ddnames defined in theapplication program. This option should be used if your batchprograms are accessing datasets used by CICS, but usingdifferent ddnames than CICS.



Lines 11 through 14:The third DATASET command specifies two generic VSAMdataset names. These will match any clusters with namesstarting with 'CSI.KS' or 'CSI.ES'.

The SELECT operand specifies that this DATASET commandshould only be used for dataset activity from programCSIPROG1.

The JREQ(ALL) specifies that all I/O requests against thesedatasets from program CSIPROG1 should be journaled to thejournal dataset defined by JID(01) which is defined by theJOURNAL command in Lines 19 through 21.

Lines 15 through 18:The fourth DATASET command specifies the same two genericVSAM dataset names as the third DATASET command. Thesewill also match any clusters with names starting with CSI.KS' or'CSI.ES'.

The SELECT operand specifies that this DATASET commandshould match the dataset activity from any program exceptCSIPROG2.

The JREQ operand specifies that read-for-updates, updates,adds, and deletes against these datasets should be journaled tothe journal dataset defined by JID(02) which is defined by theJOURNAL command in Lines 22 through 24.

Lines 19 through 24:This example contains two JOURNAL commands. The first forJID(01) and the second for JID(02).

Both of these commands reference the same journal ddname(CSIJRNL). and instruct CSI-JOURNAL to access the journalusing I/O module (CSIJRNDJ) which happens to be the defaultI/O module. The updates for each of these “logical journals”will be written to the same “physical journal”. Each journalrecord will be identified with the JID of the “logical journal”.

You can journal all of your updates to the same journal, asshown in this example, or you can specify separate journals forspecific combinations of VSAM datasets. Each “physical journal”must have a unique ddname.



Lines 25 through 31:IDENTIFY commands provide information for CSI-JOURNAL touse when creating journal records. Batch programs do not havethe same characteristics as CICS transactions. They do not haveAPPLIDs, Tran IDs, or Term IDs, as in CICS. The IDENTIFYcommand allows you to specify to CSI-JOURNAL whatinformation you want to appear in each of these fields.

Just as with DATASET commands, the sequence that you specifyyour IDENTIFY commands is important. The same general rulesfor placement apply here. Refer to the notes for Lines 4 through18.

Lines 25 through 28:The first IDENTIFY command specifies that the character string'SPECIAL' is to be used for the APPLID of all journal records fordatasets whose names begin with 'CSI.KS' or 'CSI.ES' that aregenerated from programs whose names begin with 'CSIPROG'.

Lines 29 through 31:The second IDENTIFY command specifies that each jobs jobname is to be used for the APPLID of all journal records otherthan those matching the first IDENTIFY command. Since this isthe last IDENTIFY command, and it applies to all datasets, theSELECT operand could have been omitted.

Lines 32 through 34:CONTROL commands determine which trace and/or statisticalmessages CSI-JOURNAL will generate, if any.

This example command specifies that a message should begenerated on the System Console each time a journal dataset isopened or closed. Since this the only CONTROL command, andit applies to all datasets, the SELECT operand could have beenomitted.


Using CSI-JOURNAL (Execution Time Overrides) Page 37

Execution Time Overrides for CSI-JOURNAL

The option table (CSIJRN00) should be designed to handle all your productionjobs. However, there may be special cases, such as testing or debugging, whenyou want to override the option table for the duration of a program. This iseasily accomplished by executing CSIJRNL, giving it override table entries and acommand to execute your application program. The following page shows anexample of how to do this.

The EXEC command of CSI-JOURNAL causes the DATASET, JOURNAL,IDENTIFY and CONTROL commands to be processed as they would with theGENERATE command, but the table is left in memory instead of being written toa link edit file.

When a program that is executed by CSIJRNL opens a VSAM dataset, theoverride table entries for DATASET, JOURNAL and IDENTIFY are searchedfirst, followed by the entries in the option table CSIJRN00 (if it exists).

CONTROL table entries are treated differently. If any CONTROL overrides exist,the option table CSIJRN00 will not be searched. This avoids having anyCONTROL table entries in the option table CSIJRN00 combined with those in theoverrides. If they were combined, there would be no way to “turn off” the effectsof a CONTROL table entry in CSIJRN00.


Page 38 (Execution Time Overrides) Using CSI-JOURNAL

Original Test Job

// JOB TESTJOB normal test job • • •// EXEC TESTPROG,SIZE=(AUTO,100K) note size parameterTEST RECORD 1TEST RECORD 2/* end of data for TESTPROG/&

Same Job, with Journal Overrides Added

// JOB TESTJOB job with journal override • • •// EXEC CSIJRNL,SIZE=(TESTPROG,100K) note size parm EXEC TESTPROG /* from original exec card */ DATASET NAME(...) - JID (...) - JREQ(...) - JOURNAL JID (...) - DDNAME(...) IDENTIFY ... CONTROL .../* end of journal parametersTEST RECORD 1TEST RECORD 2/* end of data for TESTPROG/&

An important note regarding the SIZE parameter of the EXEC CSIJRNLstatement: the CSIJRNL program requires a minimum effective SIZE parameterof 64k. If you have EXEC statements which use a SIZE parameter that results in avalue smaller than 64k, you must change the SIZE parameter so that CSIJRNLhas at least 64k. For programs larger than 64k, you must make sure that the SIZEparameter is appropriate for that program.


Using CSI-JOURNAL (Commands) Page 39

Commands and Operands

Parameter cards are supplied to program CSIJRNL to create the journalingoption table 'CSIJRN00'. This table specifies the names of the VSAM datasets tobe journaled, along with the conditions that must be met to cause the journalingto occur. CSIJRNL can also be used to specify overrides to the journal optiontable for a single execution of a particular program. The following sectionsdefine each of the supported commands.

Syntax

The syntax of CSI-JOURNAL's commands is the same as the one used by theIBM utility 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-JOURNAL commands and operandsshould be 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

Refer to “APPENDIX A” on page 87 for a more complete description of how tocode commands and operands.


Page 40 (Commands) Using CSI-JOURNAL

Commands

The commands that are used in CSI-JOURNAL are the following:

1. DATASET Define datasets to journal2. JOURNAL Define journal dataset attributes3. IDENTIFY Define source of record identification4. CONTROL Define journaling message requirements5. START Activate CSI-JOURNAL6. STOP Deactivate CSI-JOURNAL7. GENERATE Generate CSI-JOURNAL Option Table8. EXEC Execute an application program with override

parameters9. OPTION Set processing options for CSIJRNL

Please see the following pages for detailed descriptions of allcommands/operands.


Using CSI-JOURNAL (DATASET Command) Page 41

DATASET Command

The DATASET command is used to specify the cluster names of the VSAMdatasets to be journaled by CSI-JOURNAL.

Any number of DATASET commands can be specified. Each DATASETcommand provides a list of one or more VSAM cluster names, optional selectioncriteria used to qualify the conditions required to cause journaling of thespecified cluster(s), a list of the types of activity against the cluster(s) that shouldbe journaled, and the logical Journal ID that the updates should be written to.You can make the VSAM cluster names generic by specifying an “*” to mean anynumber of characters, or “+” to mean any “single” character. The logical JournalID is defined by the JOURNAL command.

How to enter

DATASET -NAME(cluster.name/ddname, ...) -JREQ(RO,RU(ALL),WU,WD,WN, - ALL,UPDATE,BACKOUT,NONE) -[JID(nn)] -[SELECT(...)]

Explanation

NAME(cluster.name/ddname, ...)

Required. Specifies a list of one or more VSAM clusternames to be considered for Batch Journaling.

Optional SELECT criteria can be supplied to limit theuse of these VSAM cluster names.

Each cluster name can be followed by an optionalDDNAME to be used as an override for whateverDDNAME is specified by the application program. Thismay be used to force the journaled records to have thesame DDNAME as used in your CICS FCT.

You can make the VSAM cluster names generic byspecifying an “*” to mean any number of characters, or“+” to mean any “single” character.


Page 42 (DATASET Command) Using CSI-JOURNAL

If generic cluster names are used with the optionalDDNAME, then the same DDNAME will be used for allVSAM clusters that satisfy the generic name.

JREQ(RO,RU(ALL),WU,WD,WN,ALL,UPDATE,BACKOUT,NONE)

Required. Specifies a list of one or more functions thatare to be journaled for the VSAM clusters specified bythe NAME operand.

RO Read only. (Not required for Recovery.)RU Read for Update. (Only required for

Backout Recovery.) If ALL is not specified,only the read for updates that arefollowed by some type of update will bejournaled. If RU(ALL) is specified then allread for updates will be journaled even ifno update is performed by the applicationprogram

WU Write Update. (Replace). If WU isspecified, WD is also assumed (same asthe CICS FCT). If you want WU but notWD, specify “WU,NOWD”.

WD Write Delete.WN Write New. (Add.)ALL All requests will be journaled.UPDATE Same as JREQ(WU,WD,WN). These are

the update requests needed for ForwardRecovery.

BACKOUT Same as JREQ(RU,WU,WD,WN). Theseare the requests needed for backoutrecovery.

NONE No journaling will take place, and noother DATASET table entries will besearched. This may be used in a “dummy”DATASET table entry which is used onlyto exclude one or more datasets fromjournaling.

Journaling options can be specified in any combinationdesired. To negate selected functions from UPDATE,ALL or BACKOUT, specify the negated functionpreceded with “NO”. The following specifications willhave the same result:

JREQ(UPDATE)JREQ(ALL,NORO,NORU)


Using CSI-JOURNAL (DATASET Command) Page 43

JID(nn)

Required unless JREQ(NONE) is specified. Specifies thelogical Journal ID to which the journaled activity will bewritten. A JOURNAL command must be specified foreach JID value specified in a DATASET command. Anyvalue from 0 to 255 can be specified.

SELECT(...)

Allows the specification of selection criteria that will beused to qualify when the VSAM clusters specified viathe NAME operand will be journaled. Refer to thesection “SELECT Operand” on page 58 for completeformat and rules.


Page 44 (JOURNAL Command) Using CSI-JOURNAL

JOURNAL Command

The JOURNAL command is used to specify the physical characteristics of thejournal for each logical Journal ID (JID). One JOURNAL command is requiredfor each unique JID value specified on a DATASET command.

How to enter

JOURNAL -JID(nn) -DDNAME(ddname[/SYSnnn])] -[FORMAT(SHORT|LONG) -][MODNAME(CSIJRNDJ|cccccccc) -][MULTIPLE|NOMULTIPLE -][PSUFFIX(xx) -][ASUFFIX(xx) -][USEREXIT(xxxxxxxx,| |

IGNOREABEND ,| |

FORCEOPENDEFEROPEN )]

Explanation

JID(nn)

Required. Specifies the logical Journal ID being defined.Can be any value from 0 through 255. One JOURNALcommand must be specified with a JID for each JIDvalue specified in a DATASET command.

DDNAME(ddname[/SYSnnn])

Required. Specifies the DLBL/TLBL to be used to accessthis logical JID.

If the MULTIPLE operand is specified, the ddname mustbe exactly 5 characters long, and is used in conjunctionwith the PSUFFIX and ASUFFIX operands to form theactual ddnames of the primary and secondary extents ofthe journal.

If more than one JOURNAL command specifies addname with the same first 5 characters, the firstJOURNAL command referenced at execution time willcause the journal to be opened, and all other JOURNALcommands with the same first 5 characters will bewritten to that journal dataset.


Using CSI-JOURNAL (JOURNAL Command) Page 45

For tape journals, an optional SYSnnn can be providedfor each TLBL that will override the SYSnnn specified inthe I/O module named in the MODNAME operand.

FORMAT(SHORT|LONG)

Specifies the journal record format to be generated. Thedefault is SHORT, which will generate the smallestrecords. If you intend to read the journal datasets byCOBOL application programs, you may want to specifyFORMAT(LONG). Refer to Appendix B for the formatsgenerated by each option.

MODNAME(CSIJRNDJ|CSIJRNDX|cccccccc)

Specifies the name of the I/O module to be used to writeto the journal dataset.

CSIJRNDJ is the default journal module.

CSIJRNDX is a pregenerated module that supports dualextent journals.

You can customize your own I/O modules and providethe name via this operand. Refer to “Customization ofCSI-JOURNAL” for how to create your own I/Omodules.

MULTIPLE|NOMULTIPLE

Specifies that the physical journal is to have a primaryand alternate extent.

Journaling will begin on the primary extent, and willautomatically switch to the alternate extent if theprimary extent fills. Switching back and forth willcontinue until the batch jobstep completes.

Messages will be generated on the CONSOLE at eachswitch, and a message requiring operator response willbe displayed before CSI-JOURNAL will overwrite anextent.

The PSUFFIX and ASUFFIX operands are required ifMULTIPLE is specified.

The MODNAME operand must also specify an I/Omodule that has been generated with EXOPT=YES.


Page 46 (JOURNAL Command) Using CSI-JOURNAL

PSUFFIX(cc)

This operand is required if the MULTIPLE operand hasbeen specified. It provides the characters to be appendedto the 5 character DDNAME to form the complete DLBLname of the primary journal extent.

ASUFFIX(cc)

This operand is required if the MULTIPLE operand hasbeen specified. It provides the characters to be appendedto the 5 character DDNAME to form the complete DLBLname of the alternate journal extent.

USEREXIT(xxxxxxxx,| |IGNOREABEND ,| |

FORCEOPENDEFEROPEN )

Specifies the name and processing options for a user exitto be called while processing this JOURNAL.

Refer to source member CSIJRNXP for completeinformation on writing and using a user exit.

xxxxxxx The phase name of the user exit. Thismodule will be loaded (CDLOAD) byCSI-JOURNAL.

IGNORE If the phase 'xxxxxxxx' cannot beloaded, issue warning messageCSIJRNL-251 , but continue. This isthe default.

ABEND If the phase 'xxxxxxxx' cannot beloaded, issue error message CSIJRNL-250 and terminate.

FORCEOPEN Open the journal at the first request ofany type by the application program.This is the default.

DEFEROPEN Defer the open of the journal until it isrequired. If the user exit handles alljournal requests, it will never beopened.


Using CSI-JOURNAL (IDENTIFY Command) Page 47

IDENTIFY Command

The IDENTIFY command is used to specify identifying information to beincluded in the journal records. This is information that is provided in CICSjournals but does not have equivalent information in a batch environment.

Any number of IDENTIFY commands can be specified. The SELECT operand isused to specify the conditions to be met before a particular IDENTIFY commandis used. The IDENTIFY commands are searched in the sequence specified; thefirst IDENTIFY command with matching SELECT criteria will be used.

How to enter

IDENTIFY -[APPLID(JOBNAME|PROCNAME|PROGNAME|'cccccccc')] -[TRANTERM(PROGNAME|PROCNAME|JOBNAME|'cccccccc')] -[TASK(0|nnnnn)] -[SELECT(...)]

Explanation

APPLID(JOBNAME|PROCNAME|PROGNAME|'cccccccc')

Specifies the value to be inserted in the APPLID field ofthe journal record.

JOBNAME Current VSE job name.(From // JOB)

PROCNAME Procedure name.(From // EXEC PROC=)

PROGNAME Program name.(From // EXEC PGM=)

'cccccccc' Specific character string.(8 characters max.)

TRANTERM(PROGNAME|PROCNAME|JOBNAME|'cccccccc')

Specifies the value to be inserted in the TRAN andTERM fields of the journal record. The first four bytes gointo the TRAN field, the second four bytes go into theTERM field.

JOBNAME Current VSE job name.(From // JOB)


Page 48 (IDENTIFY Command) Using CSI-JOURNAL

PROCNAME Procedure name.(From // EXEC PROC=)

PROGNAME Program name.(From // EXEC PGM=)

'cccccccc' Specific character string.(8 characters max.)

TASK(0|nnnnn)

Specifies a number from 0 - 99999 to be placed in thejournal Task ID field.

SELECT(...)

Allows the specification of selection criteria that will beused to qualify when the IDENTIFY command shouldbe used. Refer to the section “SELECT Operand” onpage 58 for complete format and rules.


Using CSI-JOURNAL (CONTROL Command) Page 49

CONTROL Command

The CONTROL command is used to specify that messages are to be generatedfor statistics and/or trace information.

Any number of CONTROL commands can be specified. The SELECT operand isused to specify the conditions to be met before a particular CONTROL commandis used. All message options from matching CONTROL commands arecombined for each opened VSAM dataset. If conflicting destinations arespecified, the destination from the first matching CONTROL command isused.The CONTROL commands are searched in the sequence specified.

Different CONTROL options can be specified for each VSAM cluster, if desired,by specifying the appropriate SELECT operands.

How to enter

CONTROL -NOSTATS|STATS( -

[DEST(SYSLST|CONSOLE|SYSnnn[,SYSnnn])] -[NOOPEN|OPEN] -[NOCLOSE|CLOSE] -[NOJOPEN|JOPEN] -[NOJCLOSE|JCLOSE] -) -

NOTRACE|TRACE( -[DEST(SYSLST|SYSnnn)] -[NOENTRY|ENTRY] -[NOACB|ACB|ACB(SNAP)] -[NORPL|RPL|RPL(SNAP)] -[NOGET|GET] -[NOPUT|PUT] -[NOERASE|ERASE] -[NOARG|ARG] -[NODATA|DATA] -[NOJWRITE|JWRITE|JWRITE(SNAP)] -) -

[SELECT(...)]


Page 50 (CONTROL Command) Using CSI-JOURNAL

Explanation

NOSTATS|STATS

Specifies that selected statistics messages are to begenerated. These are messages with numbers 200through 209. Additional operands on this keywordsupply the destination and options for the messages thatare desired.

DEST(SYSLST|CONSOLE|SYSnnn[,SYSnnn])

Specifies the destination(s) for the STATS messagesbeing generated. Specify the SYSnnn of the printer towhich the selected messages should be sent. Twodestinations can be provided. One of the destinations forSTATS can be 'CONSOLE' which will cause the outputto be sent to the System Console.

SELECT(...)

Allows the specification of selection criteria that will beused to qualify when the CONTROL command shouldbe used. Refer to the section “SELECT Operand” onpage 58 for complete format and rules.

NOOPEN|OPEN

STATS option to specify that message 201 is desired.This message is generated at the first request for aVSAM ACB for which journaling has been specified.This message provides the name of the journal beingused, and lists the type of VSAM dataset activity thatwill be journaled.

NOCLOSE|CLOSE

STATS option to specify that message 202 is desired.This message is generated when the VSAM ACB isclosed. This message provides the number of recordsjournaled and individual counts by type of activity.

NOJOPEN|JOPEN

STATS option to specify that message 200 is desired.This message is generated at the time a journal dataset isopened. This message provides the dataset name of thejournal being used.


Using CSI-JOURNAL (CONTROL Command) Page 51

NOJCLOSE|JCLOSE

STATS option to specify that message 203 is desired.This message is generated when a journal dataset isclosed. This message provides the number of recordsjournaled and individual counts by type of activity.

NOTRACE|TRACE

Specifies that selected trace messages are to begenerated. These are messages with numbers 290through 299. Additional operands on this keywordsupply the destination and options for which tracemessages are desired.

DEST(SYSLST|SYSnnn)

Specifies the destination(s) for the TRACE messagesbeing generated. Specify the SYSnnn of the printer towhich the selected messages should be sent. For STATS,two destinations can be provided. for TRACE, only onedestination can be supplied.

NOENTRY|ENTRY

TRACE option to specify that message 290 is desired.This message is generated each time program CSIJRN20is entered with a VSAM request from an applicationprogram. This message identifies the type of VSAMrequest, and the addresses of the VSAM ACB and RPLin the application.

NOACB|ACB|ACB(SNAP)

TRACE option to specify that message 291 is desired.This message is generated the first time each VSAMACB is passed to program CSIJRN20. This messagedisplays various information about the VSAM dataset. If(SNAP) is specified, a snap dump of the actual ACB isalso generated.

NORPL|RPL|RPL(SNAP)

TRACE option to specify that message 292 is desired.This message is generated after every request has beenprocessed by VSAM. This message displays variousinformation about the VSAM request. If (SNAP) isspecified, a snap dump of the actual RPL is alsogenerated.


Page 52 (CONTROL Command) Using CSI-JOURNAL

NOGET|GETNOPUT|PUTNOERASE|ERASE

TRACE options to specify that message 293 is desiredfor the specified type(s) of VSAM requests. This messageis generated after every request has been processed byVSAM. This message displays various informationabout the VSAM request. If the ARG and/or DATAoperands are specified, snap dumps of the key and/ordata areas will also be generated.

NOARG|ARG

TRACE option to specify that the VSAMKEY/RBA/RRN field is to be displayed in a snap dumpformat each time message 293 is generated. Refer tooperands GET, PUT and ERASE defined above.

NODATA|DATA

TRACE option to specify that the VSAM data record isto be displayed in a snap dump format each timemessage 293 is generated. Refer to operands GET, PUTand ERASE defined above.

NOJWRITE|JWRITE|JWRITE(SNAP)

TRACE option to specify that message 294 is desired.This message is generated each time a record is writtento the journal. This message displays variousinformation about the record being written to thejournal. If (SNAP) is specified, a snap dump of theactual journal record is also generated.


Using CSI-JOURNAL (START Command) Page 53

START Command

The START command is used to activate CSI-JOURNAL for system wideprocessing. This function activates the BIMVSR VSAM Router system and causesinternal tables to be generated to provide product routing during VSAMOpen/Close processing. After the START command, any VSAM Open or Closecall will be directed through the BIMVSR routers and to any active BIM/CSIproduct using their services. CSI-JOURNAL will determine if the currentaccessed file is eligible for journaling by examining the Journal Options Tableand if the file is protected will change the VSAM's ACB address for the accessmethods module so that all service requests are directed to CSI-JOURNAL andits journaling module. CSIJRNIP the interface module will automatically excludeany VSAM open in any partitions running CICS.

The START command must be the only command specified for this CSIJRNLexecution. Refer to the section “USING CSI-JOURNAL” starting on page 17 foradditional information.

How to enter

START [STARTCODE('authorization code')]

Explanation

STARTCODE('authorization code')

Specifies the 1 to 8 character authorization code requiredto use the START command. The authorization codespecified here must be the same as the code defined forthe STARTCODE operand of the GENERATE command.If the wrong value is specified here, the START functionwill be rejected.


Page 54 (STOP Command) Using CSI-JOURNAL

STOP Command

The STOP command is used to de-activate CSI-JOURNAL from system wideprocessing. This function will flag the BIMVSR router tables with appropriateinformation that the JOURNAL VSAM Open/ Close interface will no longer becalled during Open/Close processing. The BIMVSR routers will remain activeand will continue to intercept the Open/Close calls and will continue support forany other active BIM/CSI product.

The STOP command must be the only command specified for this CSIJRNLexecution. Refer to the section “USING CSI-JOURNAL” starting on page 17 foradditional information.

How to enter

STOP [STOPCODE('authorization code')]

Explanation

STOPCODE('authorization code')

Specifies the 1 to 8 character authorization code requiredto use the STOP command. The authorization codespecified here must be the same as the code defined forthe STOPCODE operand of the GENERATE command.If the wrong value is specified here, the STOP functionwill be rejected.


Using CSI-JOURNAL (GENERATE Command) Page 55

GENERATE Command

The GENERATE command is used to create a new Journal Option Table(CSIJRN00). This function will create an object module containing all optionsspecified via DATASET, JOURNAL, IDENTIFY and CONTROL commands. Theobject module will be written to SYSLNK and/or SYSPCH, according to the VSECATAL, LINK, and DECK options. The object module can then be link-edited tocatalog phase CSIJRN00. This will completely replace the previous JournalOption Table. Refer to the section “USING CSI-JOURNAL” starting on page 17for a sample jobstream for the GENERATE command.

How to enter

GENERATE -[STARTCODE('authorization code') -][STOPCODE('authorization code') ]

Explanation

STARTCODE('authorization code')

Specifies the 1 to 8 character authorization code requiredto use the START command.

If an authorization code is specified here, then theSTARTCODE operand of the START command must bespecified with the same value, or the START functionwill be rejected.

STOPCODE('authorization code')

Specifies the 1 to 8 character authorization code requiredto use the STOP command.

If an authorization code is specified here, then theSTOPCODE operand of the STOP command must bespecified with the same value, or the STOP function willbe rejected.


Page 56 (EXEC Command) Using CSI-JOURNAL

EXEC Command

The EXEC command is used to provide temporary journaling options for theexecution of a specific application program. It allows the specification ofoverride journaling options for DATASET, JOURNAL and IDENTIFYcommands, and replacement options for CONTROL commands. The overridesare applied to the Journal Option Table (CSIJRN00) by logically placing theoverrides BEFORE the entries in CSIJRN00. Any CONTROL commandsspecified will completely replace the CONTROL commands contained inCSIJRN00.

This function is implemented by replacing the // EXEC statement for theapplication program by a // EXEC PGM=CSIJRNL. Refer to the section “USINGCSI-JOURNAL” starting on page 17 for a sample jobstream for the EXECcommand.

How to enter

EXEC [PGM=]progname

Explanation

[PGM=]progname

Required. Specifies the name of the program to beexecuted.


Using CSI-JOURNAL (OPTION Command) Page 57

OPTION Command

The OPTION command is used to specify special processing options forCSIJRNL.

How to enter

OPTION-[NOSUSPEND|SUSPEND] -[NOTOLERATE|TOLERATE(12|nn)]

Explanation

NOSUSPEND|SUSPEND

SUSPEND specifies that no journaling is required for thecurrent application program. This option is only validwhen used with the EXEC command. It causes theJournal Option Table to be ignored for the currentexecution of the application program.

NOTOLERATE|TOLERATE(12|nn)

NOTOLERATE causes CSIJRNL to terminate processingif any errors are detected in the input commands.

TOLERATE allows processing to continue in CSIJRNLeven if errors are detected in the input commands. If atolerate value is specified, it represents the maximumcondition code that will allow processing to continue.Each error message has an associated condition code.Refer to the section “MESSAGES” starting on page 63.


Page 58 (SELECT Operand) Using CSI-JOURNAL

SELECT Operand

The SELECT operand is used to specify the criteria to be met to have DATASET,IDENTIFY and CONTROL commands selected for processing.

How to enter

Command ... SELECT( selection-criteria-operands )

How to enter selection-criteria-operands

INCLUDE|EXCLUDE( field1(list1) [field2(list2)…] )…


Using CSI-JOURNAL (SELECT Operand) Page 59

Explanation

The “field(list)” operands represent the names of the fields to test, and the datato be compared.

Field name Keywords

CPUID(string ...) Last 6 digits of your CPU serial number(Virtual CPU ID on a VM system)

PARTITION(string ...) Two character partition ID (BG,F1,F2,...)JOBNAME(string ...) Job name from // JOBPROGNAME(string ...) Program name from // EXEC PGM=PROCNAME(string ...) Procedure name from // EXEC PROC=DDNAME(string ...) DDNAME from current VSAM ACBDATASET(string ...) 44-character VSAM cluster nameCATALOG(string ...) 44-character VSAM catalog nameJSEL(string ...) Y/N flag if any journaling specified (valid

for IDENTIFY and CONTROL commands)JREQ(string ...) 5-character Y/N flag. Each position

represents whether or not the correspondingjournaling function (RO, RU, WN, WU,WD) has been specified. It is valid forIDENTIFY and CONTROL commands.

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

Field name Relational Operators

EQ-field(...) (default) match if field is equal to any one stringNOT-field(...) match if the field is equal to NONE of the stringsNE-field(...) match if the field is not equal to the stringGT-field(...) match if the field is greater than the stringGE-field(...) match if the field is greater than or equal to the stringLT-field(...) match if the field is less than the stringLE-field(...) match if the field is less than or equal to the string


Page 60 (SELECT Operand) Using CSI-JOURNAL

Selection Rules

• 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 SELECT or EXCLUDE to be matched.

• Any number of INCLUDE and/or EXCLUDE operands can be used, in anysequence. They are processed in the sequence specified. As soon as anINCLUDE or EXCLUDE is matched, selection processing stops, and theINCLUDE or EXCLUDE takes effect.

• If only EXCLUDE operands are specified, then SELECTs are consideredmatched unless specifically excluded. If one or more INCLUDE operands arespecified, then the SELECT is not considered matched unless at least oneINCLUDE operand is matched.

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

Rules for strings

• '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 if they are being tested for anEQ-, NE- or NOT- condition.

'*' 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'.


Using CSI-JOURNAL (SELECT Operand) Page 61

SELECT Operand Example

In this example, the SELECT operand is used to define when to journal anydataset with a name that begins with “PROD.VSAM”. Journaling is to take placeonly if all of the following criteria are met:

• The program name is not “PROD001” or “PROD002”

• The program name starts with “PROD”

• The program is executed in BG, F4, F5 or F6

The following DATASET command will produce this result:

DATASET -NAME(PROD.VSAM.*) -JID(01) -JREQ(WU WN WD) -SELECT ( - EXCLUDE( - PROGNAME(PROD001 PROD002) - ) - INCLUDE( - PROGNAME(PROD*) - PARTITION(BG F4 F5 F6) - ) - )


Page 63

MESSAGES


Messages Page 65

CSIJRNL-1 PROCESSING COMPLETED,HIGHEST CONDITION CODE WAS 0This message is displayed on SYSLST at end of job. It indicates the OperatingSystem Return/Condition code that the Jobstep ended with.

CSIJRNL-2 A START, STOP, GENERATE OR EXEC COMMAND HAS ALREADYBEEN SPECIFIED - THIS COMMAND IS IGNOREDCONDITION CODE = 12This message is displayed on SYSLST if more than one of the listedcommands was entered in the same execution of CSIJRNL. The START,STOP, GENERATE and EXEC commands are mutually exclusive in function.The condition code for the command is set to 12.

CSIJRNL-3 DUPLICATE JOURNAL ID - DEFINITION IGNOREDCONDITION CODE = 12This message is displayed on SYSLST if more than one JOURNAL commandis entered with the same JID value. The condition code for the command isset to 12.

CSIJRNL-4 JOURNAL ID nn DEFINED BUT NOT REFERENCEDCONDITION CODE = 4This message is displayed on SYSLST if any JID values specified inJOURNAL commands have not been specified in DATASET commands. Thecondition code for the command is set to 4, unless it has already been set to ahigher value.

CSIJRNL-5 JOURNAL ID nn REFERENCED BUT NOT DEFINED CONDITIONCODE = 4This message is displayed on SYSLST if any JID values specified inDATASET commands do not have corresponding JOURNAL commandswith the same JID value. The condition code for the command is set to 4,unless it has already been set to a higher value.

CSIJRNL-6 'xxxxxxxx' IS NOT A VALID PROGRAMMER LOGICAL UNIT NUMBERCONDITION CODE = 12This message is displayed on SYSLST when a value not conforming to therules of VSE programmer logical units is entered for the DEST operand.Valid programmer logical units for DEST are SYSLST and SYSnnn wherennn is a number from 000 to 254. The condition code for the command is setto 12.

CSIJRNL-7 DATASET, JOURNAL, IDENTIFY, AND CONTROL COMMANDS ARENOT ALLOWED WITH START OR STOPCONDITION CODE = 12This message is displayed on SYSLST when a START or STOP command isentered along with one or more of the listed commands. The listed


Page 66 Messages

commands can only be included with GENERATE or EXEC commands. Thecondition code for the command is set to 12.

CSIJRNL-8 'nnn' IS NOT A VALID JOURNAL ID NUMBERCONDITION CODE = 12This message is displayed on SYSLST when a JID value outside the validrange of 0 through 255 is entered. The condition code for the command is setto 12.

CSIJRNL-9 OUTPUT FILE IS NOT AVAILABLE FOR GENERATE COMMANDCONDITION CODE = 12This message is displayed on SYSLST when a GENERATE command isentered, but neither an OPTION DECK nor an OPTION CATAL/LINK hasbeen specified. Refer to the section “USING CSI-JOURNAL” starting on page17 for sample JCL to use with the GENERATE command. The condition codefor the command is set to 12.

CSIJRNL-10 SPECIFIED PARAMETERS REQUIRE nnnnn BYTES, MAXIMUM IS65,535CONDITION CODE = 12This message is displayed on SYSLST when an individual command wouldrequire more than 65,535 bytes to be stored in the Journal Option Table.Separate the command into more than one command to reduce the storagerequired. The condition code for the command is set to 12.

CSIJRNL-11 THE xxxxxxxx PARAMETER CANNOT CONSIST OF BOTH DATA ANDA KEYWORDCONDITION CODE = 12This message is displayed on SYSLST if more than one value is entered forthe APPLID or TRANTERM keywords of the IDENTIFY command. Thecondition code for the command is set to 12.

CSIJRNL-12 NO START, STOP, GENERATE, OR EXEC COMMAND GIVEN - NOACTION TAKENCONDITION CODE = 4This message is displayed on SYSLST if none of the listed “action”commands have been supplied. Add the command for the action you hadintended. The condition code for the command is set to 4, unless it hasalready been set to a higher value.

CSIJRNL-13 PROGRAM NAME 'xxxxxxxx' EXCEEDS 8 CHARACTERSCONDITION CODE = 12This message is displayed on SYSLST if a program name is supplied on theEXEC command that exceeds the maximum size for a valid name. Thecondition code for the command is set to 12.


Messages Page 67

CSIJRNL-14 JID(...) PARAMETER IS MISSING - JID(0) ASSUMEDCONDITION CODE = 4This message is displayed on SYSLST if the JID keyword is missing from aDATASET or JOURNAL command. This is a required keyword unlessJREQ(NONE) is specified. The condition code for the command is set to 4,unless it has already been set to a higher value.

CSIJRNL-15 JREQ(...) PARAMETER IS MISSING - JREQ(NONE) ASSUMEDCONDITION CODE = 8This message is displayed on SYSLST if the JREQ keyword is omitted from aDATASET command. DATASET commands are only required for datasetsintended for journaling. DATASET commands are not required if onlytracing is required. Trace options are specified via the CONTROL command.The condition code for the command is set to 8, unless it has already been setto a higher value.

CSIJRNL-16 'SUSPEND' OPTION IGNORED - ONLY VALID WITH EXECCOMMANDCONDITION CODE = 8This message is displayed on SYSLST if OPTION SUSPEND is specified witha command other than EXEC. The condition code for the command is set to8, unless it has already been set to a higher value.

CSIJRNL-17 CSI-JOURNAL IS ALREADY ACTIVE IN THE SYSTEMCONDITION CODE = 12This message is displayed on SYSLST and the System Console if a STARTcommand is executed when CSI-JOURNAL is already active due to aprevious START. A START is only required after an IPL of your system or apreceding STOP command. The condition code for the command is set to 12.

CSIJRNL-18 CSI-JOURNAL IS NOT ACTIVE IN THE SYSTEMCONDITION CODE = 12This message is displayed on SYSLST and the System Console if a STOPcommand is executed when CSI-JOURNAL is not active. The condition codefor the command is set to 12.

CSIJRNL-19 xxxxxxxx CANNOT BE FOUND IN SYSTEM DIRECTORYCONDITION CODE = 12This message is displayed on SYSLST and the System Console if program(xxxxxxxx) cannot be found when attempting to START or STOP CSI-JOURNAL. The condition code for the command is set to 12.

CSIJRNL-20 CSI-JOURNAL SUCCESSFULLY ACTIVATEDThis message is displayed on SYSLST and the System Console after a STARTcommand has been successfully executed.


Page 68 Messages

CSIJRNL-21 CSI-JOURNAL SUCCESSFULLY DEACTIVATEDThis message is displayed on SYSLST and the System Console after a STOPcommand has been successfully executed.

CSIJRNL-22 NAME(...) PARAMETER MISSING - DEFINITION IGNOREDCONDITION CODE = 12This message is displayed on SYSLST if the NAME keyword is omitted froma DATASET command. This is a required keyword. If no dataset names arespecified, the DATASET command will have no effect. The condition codefor the command is set to 12.

CSIJRNL-28 INVALID OR MISSING AUTHORIZATION CODE,START/STOP FUNCTION REJECTEDThis message is displayed on SYSLST and the System Console if aSTARTCODE and/or STOPCODE has been specified on the GENERATEcommand and the matching code has not been provided on the START orSTOP command. The START or STOP function is rejected, and the jobstep isabended.

CSIJRNL-29 JOURNAL OPTION TABLE (CSIJRN00) NOT FOUND,START/STOP FUNCTION REJECTEDThis message is displayed on SYSLST and the System Console if a START orSTOP command has been specified and no Journal Option Table can belocated. The START or STOP function is rejected, and the jobstep is abended.

CSIJRNL-30 CSI-JOURNAL IS NOT ACTIVE IN THE SYSTEM - EXECUTEDPROGRAM WILL NOT BE JOURNALEDCONDITION CODE = 8This message is displayed on SYSLST and the System Console if an EXECcommand is used when CSI-JOURNAL is not active (has not been started). Ifyou want the EXEC function to continue, you must include an OPTIONTOLERATE(8) command.

CSIJRNL-31 JOURNAL OPTION TABLE (CSIJRN00) RELEASE LEVEL ISINCOMPATIBLE, START FUNCTION REJECTEDCSIJRNL=x.xx, CSIJRN00=x.xxThis message is displayed on SYSLST and the System Console if a STARTcommand has been specified and the Journal Option Table is determined tobe from an incompatible release of CSI-JOURNAL. The START function isrejected, and the jobstep is abended. Regenerate your Journal Option Tablewith the current release of program CSIJRNL.

CSIJRNL-32 JOURNAL OPTION TABLE (CSIJRN00) RELEASE LEVEL ISINCOMPATIBLE, JOURNALING WILL NOT BE ACTIVATEDCSIJRNL=x.xx, CSIJRN00=x.xxThis message is displayed on SYSLST and the System Console if an EXECcommand has been specified and the Journal Option Table is determined to


Messages Page 69

be from an incompatible release of CSI-JOURNAL. The EXEC function isprocessed, but no journaling will be performed. Regenerate your JournalOption Table with the current release of program CSIJRNL.

CSIJRNL-34 SUFFIX NOT SPECIFIED FOR PRIMARY EXTENT OF JOURNAL SET.MULTIPLE EXTENT WAS SPECIFIED. CHECK PARAMETERS ANDRESTART. CONDITION CODE = 8This message is displayed on SYSLST and the System Console when theprimary suffix information is missing when multiple extents has beenrequested. Suffix information for the primary extent must be provided eitheras a separate entry in PSUFFIX or as part of the base DDNAME entry

CSIJRNL-35 SUFFIX NOT SPECIFIED FOR ALTERNATE EXTENT OF JOURNALSET. MULTIPLE EXTENT WAS SPECIFIED. CHECK PARAMETERSAND RESTART. CONDITION CODE = 8This message is displayed on SYSLST and the System Console when thealternate suffix information is missing when multiple extents has beenrequested. Suffix information for the alternate extent must be provided withan ASUFFIX operand and value.

CSIJRNL-37 PRIMARY AND ALTERNATE SUFFIX ARE THE SAME VALUE,UNIQUE SUFFIXES ARE REQUIRED. CHECK PARAMETERS ANDRESTART. CONDITION CODE = 8This message is displayed on SYSLST and the System Console when thealternate suffix and the primary suffix values provided are the samecharacters. Unique suffix values are required to create unique ddnames foreach dataset of a dual extent journal set.

CSIJRNL-38 DDNAME DOES NOT HAVE 5 CHARACTERS IN IT. MULTIPLEEXTENTS REQUIRES A 5 CHARACTER DDNAME BASE. CHECKPARAMETERS AND RESTART. CONDITION CODE = 8This message is displayed on SYSLST and the System Console when the baseDDNAME value does not contain the necessary 5 characters that will fill theconcatenation variable completely in order to ensure that blanks do not fallwithin the ddname when the suffix data is concatenated to the base.

CSIJRNL-39 MULTIPLE EXTENTS ARE IMPLIED BY PRESENCE OF SUFFIXDEFINITIONS, YET ‘MULTIPLE’ PARAMETER IS NOT PROVIDED.CHECK PARAMETERS AND RESTART. CONDITION CODE = 8This message is displayed on SYSLST and the System Console when CSI-JOURNAL encounters a parameter error in the journal definition duringgeneration of the Journal Option Table. If multiple extents are desired, theMULTIPLE or MULT keyword must be specified.


Page 70 Messages

CSIJRNL-41 ROUTER INITIATION//LOADING HAS FAILED RETURN CODE=nn,SEE ABOVE MESSAGES FOR POSSIBLE REASONS.CONDITION CODE = 12This message is displayed on SYSLST and the System Console when CSI-JOURNAL has attempted to START journaling and has encountereddifficulties with the initiation of the BIMVSR routers. Messages issued by theBIMVSR routers will indicate what the difficulties are. Generally this willresult from a lack of space, or a phase missing from the SVA.

CSIJRNL-42 STARTUP OF ROUTERS HAS FAILED RETURN CODE=nn,SEE ABOVE MESSAGES FOR POSSIBLE REASONS.CONDITION CODE = 12This message is displayed on SYSLST and the System Console when CSI-JOURNAL has attempted to START journaling and has encountereddifficulties with the initiation of the BIMVSR routers. Messages issued by theBIMVSR routers will indicate what the difficulties are. Generally this willresult from a lack of space, or a phase missing from the SVA.

CSIJRNL-100 SHOWCB-xxxxxxxx ERROR,RC=X'nn'(nn), EC=X'nn'(nn),ACB=A(aaaaaaaa),PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if a VSAM SHOWCB erroroccurs during Journal selection processing. xxxxxxx describes the type ofSHOWCB being attempted, RC and EC are the VSAM return and error codesin hex and decimal. Processing is terminated with a Jobstep abend code of100.

CSIJRNL-101 JOURNAL ID nnn CANNOT BE LOCATED IN OPTION TABLE,DATASET NAME 'cluster.name',PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if no JOURNAL entry canbe located in module CSIJRN00 (or execution-time overrides) for the JIDspecified in the DATASET entry matching the VSAM cluster specified in themessage. This error indicates a logic error in program CSIJRNL. Thissituation should be detected in the GENERATE or EXEC functions before theapplication program is executed. Processing is terminated with a Jobstepabend code of 101.

CSIJRNL-102 TESTCB-xxxxxxxx ERROR,RC=X'nn'(nn), EC=X'nn'(nn),ACB=A(aaaaaaaa),PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if a VSAM TESTCB erroroccurs during Journal selection processing. xxxxxxx describes the type ofTESTCB being attempted, RC and EC are the VSAM return and error codesin hex and decimal. Processing is terminated with a Jobstep abend code of102.


Messages Page 71

CSIJRNL-103 xxxxxxxx IS NOT AT THE SAME PRODUCT RELEASE LEVEL ASyyyyyyyyJOURNALING WILL NOT BE ACTIVATEDThis message is displayed on the System Console if all of the CSI-JOURNALprograms and tables are not part of the same product release level. xxxxxxxis the program or table that was found to be in error. yyyyyyy is the programthat made the check. Journaling will not be activated.

CSIJRNL-104 JOURNAL OPTION TABLE (CSIJRN00) RELEASE LEVEL ISINCOMPATIBLE, JOURNALING WILL NOT BE ACTIVATEDCSIJRNL=x.xx, CSIJRN00=x.xxThis message is displayed on the System Console if the Journal Option Tableis determined to be from an incompatible release of CSI-JOURNAL. Nojournaling will be performed. Regenerate your Journal Option Table with thecurrent release of program CSIJRNL.

CSIJRNL-200 JOURNAL FILE 'xxxxxxxx', SUCCESSFULLY OPENED,DATASET NAME 'data.set.name'This message is displayed on up to two destinations defined by the DESToperand of the STATS keyword on the CONTROL command. It is generatedif the JOPEN operand of the STATS keyword is specified on a selectedCONTROL command. It indicates that a journal dataset has been opened.'xxxxxxxx' is the DDNAME, and 'data.set.name' is from the DLBL/TLBL.

CSIJRNL-201 JOURNALING ESTABLISHED FOR 'xxxxxxxx' AS 'yyyyyyyy' DATASETNAME 'cluster.name'JOURNAL FILE 'jjjjjjjj'FUNCTIONS JOURNALED (RO RU WU WN WD)This message is displayed on up to two destinations defined by the DESToperand of the STATS keyword on the CONTROL command. It is generatedif the OPEN operand of the STATS keyword is specified on a selectedCONTROL command. It indicates that a VSAM dataset has been selected forjournaling. 'xxxxxxxx' is the VSAM DDNAME. 'yyyyyyyy' is the 'forced'ddname from the DATASET command. 'cluster.name' is the VSAM clustername. 'jjjjjjj' is the journal DDNAME. 'RO RU WU WN WD' is based on theJREQ parameter of the DATASET command.

CSIJRNL-202 DATASET 'xxxxxxxx' CLOSED,nnnnn REQUESTS JOURNALED TO 'jjjjjjjj',FUNCTION TOTALS (RO=nnn RU=nnn WU=nnn WN=nnn WD=nnn)This message is displayed on up to two destinations defined by the DESToperand of the STATS keyword on the CONTROL command. It is generatedif the CLOSE operand of the STATS keyword is specified on a selectedCONTROL command. It indicates that a VSAM dataset has been closed andshows the total number of records journaled to journal ddname 'jjjjjjjj'. It alsoprovides totals by each type of VSAM function.


Page 72 Messages

CSIJRNL-203 JOURNAL FILE 'jjjjjjjj' SUCCESSFULLY CLOSED,nnnnn REQUESTS JOURNALED,FUNCTION TOTALS (RO=nnn RU=nnn WU=nnn WN=nnn WD=nnn)This message is displayed on up to two destinations defined by the DESToperand of the STATS keyword on the CONTROL command. It is generatedif the JCLOSE operand of the STATS keyword is specified on a selectedCONTROL command. It indicates that a journal dataset has been closed andshows the total number of records journaled to journal ddname 'jjjjjjjj'. It alsoprovides totals by each type of VSAM function.

CSIJRNL-210 'DLBL/TLBL/DD' STATEMENT MISSING FOR JOURNAL 'jjjjjjjj',MODNAME 'pppppppp',PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if the required JCL forjournal 'jjjjjjjj' cannot be located. For VSE, the specified I/O module name isgiven. Processing is terminated with a Jobstep abend code of 210.

CSIJRNL-211 JOURNAL OPEN ERROR,... ERROR CODE - xx... FEEDBACK - xxxxxxxx... FUNCTION - xx... MODNAME - pppppppp... DDNAME - dddddddd... DATASET - cluster.namePROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if an error occurs while theprogram is attempting to open a journal dataset. Processing is terminatedwith a Jobstep abend code of 211.

ERROR CODE FEEDBACK FUNCTION01 GETMAIN/GETVIS failed Amount of GETMAIN(hex) 00 Open input02 FREEMAIN/FREEVIS failed 04 Open output03 FREEMAIN/FREEVIS wrong area 08 Close04 Bad block length field Blocklength and “LL” field 0C Sequential input05 Block to large Blocklength and “LL” field 10 Sequential output (buffered)06 Spanned record to large Blocklength and “LL” field 14 Sequential output (force write)07 VARBLK record to large Blocklength and “LL” field 18 Extent open output08 FIXBLK record to large Blocklength and “LL” field 1C Extent close09 FIXBLK invalid blocksize Blocklength and “LL” field 20 Build output block10 End of file 24 Write output block11 Misc write error 28 Test close12 OPEN/CLOSE error 2C Point13 EOX entered with rc0414 EOX entered with rc0820 File already closed


Messages Page 73

CSIJRNL-212 JOURNAL WRITE ERROR,... ERROR CODE - xx... FEEDBACK - xxxxxxxx... FUNCTION - xx... MODNAME - pppppppp... DDNAME - dddddddd... DATASET - cluster.namePROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if an error occurs while theprogram is attempting to write to a journal dataset. Refer to error number211 for a description of the returned information. Processing is terminatedwith a Jobstep abend code of 212.

CSIJRNL-213 JOURNAL CLOSE ERROR,... ERROR CODE - xx... FEEDBACK - xxxxxxxx... FUNCTION - xx... MODNAME - pppppppp... DDNAME - dddddddd... DATASET - cluster.namePROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if an error occurs while theprogram is attempting to close a journal dataset. Refer to error number 211for a description of the returned information. Processing is terminated with aJobstep abend code of 213.

CSIJRNL-220 SHOWCB-xxxxxxxx ERROR,RC=X'nn'(nn), EC=X'nn'(nn),RPL=A(aaaaaaaa), ACB=A(aaaaaaaa),PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if a VSAM SHOWCB erroroccurs during Journal output processing. “xxxxxxx” describes the type ofSHOWCB being attempted, RC and EC are the VSAM return and error codesin hex and decimal. Processing is terminated with a Jobstep abend code of220.

CSIJRNL-221 TESTCB-xxxxxxxx ERROR,RC=X'nn'(nn), EC=X'nn'(nn),RPL=A(aaaaaaaa), ACB=A(aaaaaaaa),PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if a VSAM TESTCB erroroccurs during Journal output processing. “xxxxxxx” describes the type ofTESTCB being attempted, RC and EC are the VSAM return and error codesin hex and decimal. Processing is terminated with a Jobstep abend code of221.


Page 74 Messages

CSIJRNL-230 MODNAME 'pppppppp' COULD NOT BE LOADED FOR JOURNAL'jjjjjjjj'PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if the MODNAME“pppppppp” specified in a JOURNAL command could not be loaded. Checkthe name specified, and the LIBDEF for the executing application. Processingis terminated with a Jobstep abend code of 230.

CSIJRNL-231 'pppppppp' IS NOT A VALID I/O MODULE FOR JOURNAL 'jjjjjjjj'PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if the MODNAME“pppppppp” specified in a JOURNAL command does not appear to be amodule created by macro CSIIOGEN. Check the name specified and verifythat the CSIIOGEN assembly worked properly. Refer to the section“Customizing CSI-JOURNAL” on page 11 for more information. Processingis terminated with a Jobstep abend code of 231.

CSIJRNL-232 ('jobname') END OF VOLUME FOUND FOR 'current' JOURNAL EXTENTON DSN 'dddddd.dddd' SWITCHING TO 'next' JOURNAL EXTENT.This message is displayed on the System Console when the journal managerdetermines that it has reached the end of the current journal dataset and hasswitched to the next extent of the defined journal set. The value of 'current'may be PRIMARY or SECONDARY. The value of 'jobname' will be theapplication Jobname. The value of 'next' will be either SECONDARY orPRIMARY.

CSIJRNL-233 ('jobname') OPEN FOR 'current' JOURNAL EXTENT WAS SUCCESSFUL,NOW JOURNALING ON 'current' JOURNAL EXTENT 'ddname'This message is displayed on the System Console when the journal managerhas successfully opened the 'current' extent of the journal set. The value of'current' will be PRIMARY or SECONDARY depending upon how manyswitches have been executed.

CSIJRNL-235 ('jobname') CLOSE FOR 'current' JOURNAL EXTENT WASSUCCESSFUL, JOURNAL DATA ON JOURNAL DATASET ' 'datasetname' MAY BE ARCHIVED.This message is displayed on the System Console when the journal managerhas successfully closed the 'current' extent of the journal set. The value of'current' will be PRIMARY or SECONDARY depending upon how manyswitches have been executed. The dataset named may be archived to anotherdataset name on DASD or tape to free the journal extent for the next possibleswitch to it.


Messages Page 75

CSIJRNL-236 ('jobname') JOURNAL DATA ON 'dataset.name' IS STILL PROTECTED,A SWITCH TO THE 'next', JOURNAL EXTENT IS HELD. IF DATA WASARCHIVED, RESPOND ACCORDINGLY ELSE ARCHIVE DATA ANDRESPOND OR REQUEST OVERLAY OF DATA OR ABORT THE JOB,ENTER ARCHIVED, OVERLAY, OR ABORT'This message is displayed on the System Console when the journal managerattempts to switch to a previously written extent of the journal set. Sincethere is no interface between any archive utility and the journal manager, theprotection switch is never altered except when the reply is “ARCHIVED” or“OVERLAY” A response to this message is required to allow the applicationjob to continue processing or to be terminated abnormally.

If the journal extent has not been archived yet, the journal manager will holdthe job until the operator can accomplish the archival of the data. When thearchival job completes satisfactorily, the operator may respond with“ARCHIVED”

If the operator responds “OVERLAY” without archiving the data containedon the journal extent protected, all the data will be overlayed, destroying anychance of using that data to support a recovery attempt.

CSIJRNL-237 ('jobname') CLOSE FOR 'current' JOURNAL EXTENT FAILED,PROGRAM IS TERMINATED CONDITION CODE = 8This message is displayed on the System Console when the journal managerhas attempted to close the 'current' extent of the journal set and has failed forsome reason. The data on the journal may be good up to the last recordblock, but the data set may not be properly closed and may not be useable.The job is terminated abnormally to prevent loss of recover capability.

CSIJRNL-238 ('jobname') OPEN FOR 'next' JOURNAL EXTENT FAILED, PROGRAM ISTERMINATED CONDITION CODE = 8This message is displayed on the System Console when the journal managerhas attempted to open the 'next' extent of the journal set and has failed forsome reason. The journal manager will not allow the application job to runwithout journal support. The job is terminated abnormally.

CSIJRNL-239 REPLY FROM OPERATOR 'reply'This message is displayed on the System Console when the operator replysto message CSIJRNL-236 as a means of tracking the response that wasentered to the request.

CSIJRNL-250 USEREXIT 'pppppppp' COULD NOT BE LOADED FOR JOURNAL'jjjjjjjj'PROCESSING WILL BE TERMINATEDThis message is displayed on the System Console if the USEREXIT“pppppppp” specified in a JOURNAL command cannot be loaded from anylibrary in the current LIBDEF search chain. Processing is terminated with aJobstep abend code of 250.


Page 76 Messages

CSIJRNL-251 USEREXIT 'pppppppp' COULD NOT BE LOADED FOR JOURNAL'jjjjjjjj', IGNORE OPTION HAS BEEN SPECIFIEDThis message is displayed on the System Console if the USEREXIT“pppppppp” specified in a JOURNAL command cannot be loaded from anylibrary in the current LIBDEF search chain. The IGNORE option has beenspecified, therefore the USEREXIT is ignored, and processing continues.

CSIJRNL-290 CSIJRN20 ENTRY, REQ=X'xx'(dddddd), RPL=A(rrrrrrrr),ACB=A(aaaaaaaa), DDN=nnnnnnnn, WS=wwwwwwwwThis message is displayed on the destination defined by the DEST operandof the TRACE keyword on the CONTROL command. It is generated if theENTRY operand of the TRACE keyword is specified on a selectedCONTROL command. It indicates that the journaling module CSIJRN20 hasbeen entered for the specified request (in hex and a descriptive name) withthe VSAM RPL and ACB addresses displayed. The DDNAME is shown afterthe first request for any given ACB. The WS is an internal work areaassociated with the ACB used by CSIJRN20.

CSIJRNL-291 CSIJRN20 ACB EXTRACT, ACB=A(aaaaaaaa), WS=wwwwwwww,DDN=nnnnnnnn, DSN=cluster.name, TYPE=xxDS, KEYLEN=000,RKP=000, LRECL=00000, CINV=00000, CIMODE=N, JFLAGS=nnnnnnThis message is displayed on the destination defined by the DEST operandof the TRACE keyword on the CONTROL command. It is generated if theACB operand of the TRACE keyword is specified on a selected CONTROLcommand. It is generated each time a new ACB is detected by CSIJRN20. Itdisplays various required information about the cluster. CIMODE is a Y/Nflag for whether the ACB is in Control interval mode. CSI-JOURNAL cannotjournal processing performed in Control internal mode. JFLAGS is a series ofsix Y/N flags. The first will be 'N' if NO journaling has been specified. Theremaining five indicate via the Y/N if each of the functions are to bejournaled (RO, RU, WU, WD, WN). The WS is an internal work areaassociated with the ACB used by CSIJRN20.

CSIJRNL-292 CSIJRN20 RPL EXTRACT, RPL=A(aaaaaaaa), DDN=nnnnnnnn,RECL=00000, RBA=X'00000000', AREA=X'aaaaaaaa', ARG=X'aaaaaaaa',UPD=n, LOC=n, CIMODE=nThis message is displayed on the destination defined by the DEST operandof the TRACE keyword on the CONTROL command. It is generated if theRPL operand of the TRACE keyword is specified on a selected CONTROLcommand. It is generated each time a VSAM request is completed. Itdisplays various required information from the RPL. RPL address,DDNAME, current record length, current RBA in hex, address of currentrecord (AREA), address of current key (ARG). UPD is a Y/N flag forwhether the RPL is in update mode (add versus replace). CIMODE is a Y/Nflag for whether the RPL is in Control interval mode. CSI-JOURNAL cannotjournal processing performed in Control interval mode.


Messages Page 77

CSIJRNL-293 CSIJRN20 rrrrrrrr PROCESSING, FC=cc, RC=x'rc', JFLAG=y,DDN=nnnnnnnn, ACB=A(aaaaaaaa), RPL=A(aaaaaaaa), RECL=00000,RBA=X'00000000', AREA=X'aaaaaaaa', ARG=X'aaaaaaaa', UPD=n, LOC=n,CIMODE=nThis message is displayed on the destination defined by the DEST operandof the TRACE keyword on the CONTROL command. It is generated if theGET, PUT or ERASE operands of the TRACE keyword are specified on aselected CONTROL command. It is generated each time one of the specifiedrequests is completed. It displays various required information from the RPLand Journal Option Table. FC is the function code for the journal(RO,RU,WU,WN,WD), RC is the VSAM return code for the request, JFLAGis a Y/N indicating whether the request is to be journaled, DDN is theddname,RECL is the current record length, RBA is the current RBA in hex,AREA is the address of current record, ARG is the address of current key,UPD is a Y/N flag for whether the RPL is in update mode (add versusreplace), LOC is a Y/N flag for whether the current request is in locate mode(versus move mode), CIMODE is a Y/N flag for whether the RPL is inControl interval mode. CSI-JOURNAL cannot journal processing performedin Control internal mode.

CSIJRNL-294 CSIJRN20 JOURNAL WRITE TO 'jjjjjjjj', FUNC=(fc),DATASET='dataset.name', RPL=A(aaaaaaaa), ACB=A(aaaaaaaa),JBXRPL=A(aaaaaaaa), JBXBAR=A(aaaaaaaa)This message is displayed on the destination defined by the DEST operandof the TRACE keyword on the CONTROL command. It is generated if theJWRITE operand of the TRACE keyword is specified on a selectedCONTROL command. It is generated each time a record is written to ajournal. It displays the journal ddname, FUNC is the function code for thejournal (RO,RU,WU,WN,WD). JBXRPL and JBXBAR are used internally byCSI-JOURNAL to allow RU records to be journaled only if an update occurs.If JBXBAR is not zero, the current record was held for the RPL at JBXRPL.

CSIJRNL-1000 'x' IS AN INVALID COMMANDThe 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 continuation onthe end of the previous line. If it is supposed to be part of a comment, checkfor the proper use of “/*” (start of comment),”;” (end of command), andcontinuation characters.

CSIJRNL-1001 'x' IS AN INVALID KEYWORD FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNOREDThe character string “x” was specified as a sub-parameter of “y”, and is not avalid 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 78 Messages

CSIJRNL-1002 'x' EXCEEDS THE NUMBER OF POSITIONAL PARAMETERSALLOWED FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNOREDPositional 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.

CSIJRNL-1003 'x' IS INVALID - NO PARAMETERS ALLOWED FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNOREDNo 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.

CSIJRNL-1004 'x' CAN BE SPECIFIED ONLY n TIMES FOR 'y'SUB-PARAMETERS FOLLOWING IT ARE IGNOREDA list of repeated sub-parameters (maximum of “n”) are allowed for “y”, but“x” exceeds this maximum. Any sub-parameters coded for “x” are ignored.If “x” was not intended to be a sub-parameter of “y”, check your use ofparentheses.

CSIJRNL-1006 'x' IS NOT A VALID NUMERIC VALUEThe character string “x” was coded where a numeric value is expected, but itis not a valid number. If “x” was not intended to be a number, it may bepositioned incorrectly in relation to other sub-parameters at the same level,or incorrect use of parentheses may have caused it to be associated with thewrong parameter.

CSIJRNL-1007 'x' EXCEEDS THE ALLOWED NUMBER OF n CHARACTERS/DIGITSFor a non-numeric positional parameter, “x” contains too many characters.For a numeric parameter, “x” is too large a number for the positionalparameter. If “x” is correct as coded, it may be positioned incorrectly inrelation to other sub-parameters at the same level, or the incorrect use ofparentheses may have caused it to be associated with the wrong parameter.

CSIJRNL-1009 DELIMITER 'x' IS INVALID FOLLOWING 'y', AND IS IGNOREDThe delimiter “x” was coded where it is not allowed. A “/” delimiter isallowed only after certain parameters, and a “(“ cannot immediately followanother delimiter.

CSIJRNL-1010 EXTRA RIGHT PARENTHESES FOLLOWING "x" IGNOREDMore right parentheses “)” have been found than are needed. Either a leftparenthesis “(“ is missing, or too many right parentheses were coded.


Messages Page 79

CSIJRNL-1011 MISSING n RIGHT PARENTHESES AT END OF COMMANDThe end of command has been reached, but “n” left parentheses “(“ have notbeen paired with right parentheses “)”. Either a continuation character ismissing (the next line will start a new command), or too few rightparentheses “)” were coded.

CSIJRNL-1012 COMMENT IS NOT TERMINATED WITH '*/', OR CONTINUATION ISMISSING ON THIS LINEA comment was started with “/*” but was not terminated properly.Comments follow the same continuation rules as parameters, and must beterminated by “*/”.

CSIJRNL-1013 STRING 'x' IS NOT TERMINATED WITH A QUOTE, ORCONTINUATION IS MISSING ON THIS LINEThe character string “x” was started as a quoted string, but an ending quote(') was not found.

CSIJRNL-1014 STRING 'x' IS NOT FOLLOWED BY A SEPARATOR CHARACTER, ORONE QUOTE WAS CODED WHERE TWO ARE REQUIREDThe 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).

CSIJRNL-1015 END OF INPUT REACHED - LAST INPUT LINE CANNOT BECONTINUEDThe 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.

CSIJRNL-1016 COMMAND NOT PROCESSED DUE TO SYNTAX ERRORS -CONDITION CODE nThe condition code set by previous errors for this command exceeds themaximum allowed. The highest condition code for all errors for thiscommand is “n”.

CSIJRNL-1096 PATCH HEX STRING CONTAINS ODD NUMBER OF DIGITSThe internal debugging facility has been invoked to patch a module. Ahexidecimal verify or replace string was coded which does not represent awhole number of bytes. For example, X'47F0' is valid; x'47F' is not valid.

CSIJRNL-1097 PATCH VERIFY ERRORThe internal debugging facility has been invoked to patch a module, but thedata being verified does not match what is in the module.


Page 80 Messages

CSIJRNL-1098 INTERNAL ERROR - CANNOT FIND TYPE=FINALAn internal logic error has occurred. Request assistance from a supportrepresentative.

CSIJRNL-1099 INTERNAL ERROR - CANNOT FIND TYPE=SEG FOR xxxxxxxxAn internal logic error has occurred. Request assistance from a supportrepresentative.

CSIJRNL-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 an errornumber which is not in any message tables. When requesting technicalassistance for this error, please state the full error message.

CSIJRNL-1101 (module+offset) function/macro INTERNAL ERROR - RETURN CODEX'xxxxxxxx'(n)An internal program function has issued an operating system macro whichfailed. The function was called at the location indicated by the module andoffset information. When requesting technical assistance for this error, pleasestate the full error message.

CSIJRNL-1102 (module+offset) function/macro INTERNAL ERROR - RETURN CODEX'xxxxxxxx'(n) WHILE ISSUING MESSAGE mmmmWhile attempting to issue message number “mmmm”, an internal programfunction issued an operating system macro which failed. The function wascalled at the location indicated by the module and offset information. Alsorefer to message “CSIJRNL-mmmm” which may help in determining thecause of the problem. When requesting technical assistance for this error,please state the full error message.

CSIJRNL-1103 GETMAIN(GM) / FREEMAIN(FM) STATISTICSGMCOUNT=n GMTOT=nFMCOUNT=n FMTOT=nCURRENT=n MAXIMUM=nLARGEST SINGLE GETMAIN=nAn internal debugging function has requested a display of the memorystatistics.

CSIJRNL-1104 (module+offset) function/macro PROGRAM 'xxxxxxxx' NOT FOUNDCSI-JOURNAL attempted to load program “xxxxxxxx”, but it was not foundin the load libraries available in the job step. The load function was called atthe location indicated by the module and offset information. This message isissued only if the program cannot be found; other load errors will producemessage CSIJRNL-1105 or CSIJRNL-1108


Messages Page 81

CSIJRNL-1105 function/macro REQUEST FOR n BYTES OF MAIN STORAGE FAILED.USE A LARGER PARTITION, OR A SMALLER SIZE PARAMETERThe 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 CSIJRNL in a larger partition (or use a smallerSIZE= parameter). If the problem persists, determine the cause of excessivemain storage use.

CSIJRNL-1106 (module+offset) function/macro INVALID PRINT FILE 'filename'CSI-JOURNAL was unable to open “filename” as a printer file. Check yourJCL and parameters. If you request technical assistance for this error, pleasestate the full error message.

CSIJRNL-1108 (module+offset) function/macro INTERNAL ERROR - ABEND CODEX'xxxx', REASON CODE X'xxxx'An internal program function has issued an operating system macro whichfailed. The function was called at the location indicated by the module andoffset information. The system abend code and reason code are displayed.When requesting technical assistance for this error, please state the full errormessage.

CSIJRNL-1150 (module+offset) xxxxxxxx FUNCTION HAS BEEN ENTEREDThe operating system interface module has been called from (module+offset)to perform a “xxxxxxxx” function. This message is issued only if the internaltrace has been turned on.

CSIJRNL-9998 WARNING - PRODUCT AUTHORIZATION EXPIRES IN 30 DAYS ORLESSThis message is displayed on the system console if the copy of CSI-JOURNAL you are using is about to expire. Contact your CSI product salesrepresentative for a new Expiration Password.

CSIJRNL-9999 PRODUCT AUTHORIZATION HAS EXPIREDCSI-JOURNAL is protected with an Expiration Password. This message isdisplayed on the system console if that Password has expired. Contact yourCSI product sales representative for a new Expiration Password.


Page 82 Messages

BIMVSR-nnn (Routing Facility)

The following messages are generated by the VSAM Routing Facility used byseveral BIM/CSI software products.

BIMVSR-001 xxxxxxxx MODULE NOT FOUNDThe module "xxxxxxxx" could not be found by the Router. Make sure that thelibrary containing program "xxxxxxxx" is accessible to all partitions.

BIMVSR-003 NO INIT PARMS (error description)Request technical assistance for this message.

BIMVSR-005 TABLE xxxxxxxx NOT FOUNDThe table "xxxxxxxx" could not be found by the Router. Make sure that thelibrary containing table "xxxxxxxx" is accessible to all partitions.

BIMVSR-006 BIMVSR NOT ACTIVERequest technical assistance for this message.

BIMVSR-009 MODULE xxxxxxxx FOR MOD yyyyyyyy SUBROUTINE ERRORRequest technical assistance for this message.

BIMVSR-010 GETMAIN ERROR (error description)Request technical assistance for this message.

BIMVSR-011 ROUTER ALREADY ACTIVEThe router has already been activated.

BIMVSR-015 FREEVIS ERROR (error description)Request technical assistance for this message.

BIMVSR-016 NO ENTRY IN TABLE BIMVSRTB FOR APPLRequest technical assistance for this message.

BIMVSR-017 CDLOAD FOR MODULE xxxxxxxx FAILEDRequest technical assistance for this message.

BIMVSR-018 MODULE xxxxxxxx NOT FOUND IN SVA, RC=xRequest technical assistance for this message.

BIMVSR-019 PRODUCT xxxxxxxx NOT FOUNDRequest technical assistance for this message.


Messages Page 83

BIMVSR-020 ERROR IN SRCSDL ROUTINE xxxxxxxx PART, SDSDSRC=xRequest technical assistance for this message.

BIMVSR-021 THE SVC TABLE COULD NOT BE FOUNDRequest technical assistance for this message.

BIMVSR-022 WACOMMON STORAGE NOT FOUNDRequest technical assistance for this message.


Page 85

APPENDIX A


APPENDIX A How to Code Commands Page 87

How to Code Commands (Syntax)

This section describes the rules for coding CSI-JOURNAL 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-JOURNAL-defined Command namefollowed by operands and comments. Each command is defined andprocessed by CSI-JOURNAL as a single entity, and may or may not berelated to other commands.

• KEYWORD Operand: Keyword operands are represented in commanddescriptions with upper-case letters, and indicate CSI-JOURNAL-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 other operands.The separator characters are: space, comma, left and right parentheses, slash,and semi-colon.

• COMMENTS: CSI-JOURNAL allows you to code comments in the SYSINfile. Comments are for your own documentation and are printed, but notprocessed, with the commands.


Page 88 How to Code Commands APPENDIX A

Coding CSI-JOURNAL Operands

CSI-JOURNAL 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 operands whichfurther define the action to be taken by the command. The operands which areallowed after the command-name are separated using one or more spaces. If anoperand requires one or more sub-operands, the sub-operands are coded inparentheses 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-operands followingPARM-2. The operands PARM-1, PARM-2, and PARM-3 are considered to be atthe same logical level, regardless of any sub-operands specified for each of them.operands and sub-operands of all logical levels follow 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.


APPENDIX A How to Code Commands Page 89

Coding Continuation

Any CSI-JOURNAL 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.

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'


Page 90 How to Code Commands APPENDIX A

Coding Comments

It is often useful to put comments with the operands. Since a semi-colon “;” endsthe operand processing of a command, anything coded after a semi-colon istreated as a comment. If continuation is specified after a semi-colon, thecommand 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 91

APPENDIX B


APPENDIX B Journal Record Format Page 93

Journal Record Format

The following record layouts describe the formats of CSI-JOURNAL Journalrecords. Journal datasets are created using variable-length spanned blockedrecords and are compatible with the INPUT BACKUP datasets used by ourVSAM recovery product CSI-RECOV.

The format is determined by the FORMAT operand of the JOURNAL 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 94 Journal Record Format APPENDIX B

FORMAT(LONG)

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) 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

Index

CSI-JOURNAL Page 95

- (continuation) ..............................................88

+

+ (continuation) .............................................88

A

ABENDJOURNAL Command............................46

ACBCONTROL Command...........................51

Activating CSI-JOURNAL............................28Alternate Extent.............................................20Alternate indexes...........................................21APPLID

IDENTIFY Command ............................47ARG

CONTROL Command...........................52ASUFFIX

JOURNAL Command............................46

B

BLKSIZE .........................................................15

C

Chained RPLs.................................................26CICS...........................................................19, 26

Journals....................................................19CLOSE

CONTROL Command...........................50Coding Operands ..........................................88Commands .....................................................39

Coding Syntax ........................................88Continuation Syntax ..............................88CONTROL Command...........................49DATASET Command ............................41EXEC Command ....................................56GENERATE Command.........................55IDENTIFY Command ............................47JOURNAL Command............................44OPTION Command ...............................57SELECT Operand ...................................58START Command ..................................53STOP Command.....................................54Syntax.......................................................39

Comments ......................................................87Comments (syntax) .......................................89Compatibility .................................................27

Continuation Syntax .....................................88CONTROL Command ..................................49

ACB ..........................................................51ARG..........................................................52CLOSE......................................................50DATA.......................................................52DEST...................................................50, 51ENTRY .....................................................51ERASE......................................................52GET...........................................................52how used .................................................31JCLOSE ....................................................51JOPEN ......................................................50JWRITE ....................................................52OPEN .......................................................50PUT...........................................................52RPL ...........................................................51SELECT ....................................................50STATS.......................................................50TRACE .....................................................51

Control Interval Access.................................26CSIJRN00 ........................................................31

example....................................................32CSI-RECOV ....................................................19Customizing CSI-JOURNAL .......................11

CSIJRNDJ.................................................12Operands

BLKSIZE ...........................................15DEVICE.............................................15EOXPT ..............................................15IOAREAS..........................................15LABEL...............................................16OPSYS ...............................................15REWINDO........................................16SYSNBRO .........................................16

Sample JCL............................................16CSIJRNDX ...............................................13

D

DATACONTROL Command ...........................52

DATASET Command ...................................41how used .................................................31JID.............................................................43JREQ .........................................................42NAME ......................................................41SELECT ....................................................43

DDNAMEJOURNAL Command............................44

Index

Page 96 CSI-JOURNAL

Deactivating CSI-JOURNAL....................... 30DEFEROPEN

JOURNAL Command ........................... 46DEST

CONTROL Command .................... 50, 51

E

ENTRYCONTROL Command .......................... 51

ERASECONTROL Command .......................... 52

Example Journal Option Table ................... 33EXCLUDE.operand ...................................... 60EXEC Command........................................... 56

PGM= ...................................................... 56Execution Time Overrides........................... 37

F

FORCEOPENJOURNAL Command ........................... 46

FORMATJOURNAL Command ........................... 45

Format, journal record ................................. 93Forward recovery ......................................... 19Forward Recovery

Introduction.............................................. 4

G

GENERATE Command ............................... 55STARTCODE.......................................... 55STOPCODE ............................................ 55

GETCONTROL Command .......................... 52

H

Hexidecimal Notation.................................. 89

I

IDENTIFY Command .................................. 47APPLID ................................................... 47how used................................................. 31SELECT ................................................... 48TASK ....................................................... 48TRANTERM ........................................... 47

IGNOREJOURNAL Command ........................... 46

INCLUDE operand....................................... 60Installation ....................................................... 8

Cataloging CSIJRNL ............................... 9

Load Modules .......................................... 8Source Modules........................................ 8

Introduction..................................................... 3Features ..................................................... 5What is Recovery ..................................... 4

J

JCLOSECONTROL Command .......................... 51

JIDDATASET Command............................ 43JOURNAL Command ........................... 44

JOPENCONTROL Command .......................... 50

Journaldataset type............................................. 19format ...................................................... 19label information.................................... 21record format.......................................... 93

JOURNAL Command .................................. 44ABEND.................................................... 46ASUFFIX ................................................. 46DDNAME ............................................... 44DEFEROPEN.......................................... 46FORCEOPEN ......................................... 46FORMAT................................................. 45how used................................................. 31IGNORE .................................................. 46JID ............................................................ 44MODNAME ........................................... 45MULTIPLE.............................................. 45PSUFFIX.................................................. 46USEREXIT............................................... 46

Journal Option TableExample................................................... 33

JREQDATASET Command............................ 42

JWRITECONTROL Command .......................... 52

K

Keyword operand......................................... 87

L

Lower Case Data ........................................... 89

M

Managed SAM............................................... 20Messages

Index

CSI-JOURNAL Page 97

BIMVSR-nnn ...........................................82CSIJRNL-0nnn ........................................65CSIJRNL-10nn.........................................77CSIJRNL-11nn.........................................79

Migration Requirements ................................6MODNAME

JOURNAL Command............................45MULTIPLE

JOURNAL Command............................45Multiple Extent Journals...............................20

N

NAMEDATASET Command ............................41

O

OPENCONTROL Command...........................50

OperandsCoding Syntax ........................................88Comments ...............................................89Continuation Syntax ..............................88Quoted Strings........................................89

OPTION Command ......................................57SUSPEND................................................57TOLERATE .............................................57

Option Table...................................................31example....................................................32

P

PGM=EXEC Command ....................................56

Positional operand ........................................87Primary Extent ...............................................20PSUFFIX

JOURNAL Command............................46PUT

CONTROL Command...........................52

Q

Quoted Strings ...............................................89

R

Recovery .........................................................19Restrictions .....................................................26

Chained RPLs .........................................26CICS .........................................................26Control Interval Access .........................26Share option 4 .........................................26

VSAM Managed SAM ...........................26RPL

CONTROL Command ...........................51RPLs.................................................................26

S

Sample JCLCSIJRNDJ.................................................16

SELECTCONTROL Command ...........................50DATASET Command ............................43IDENTIFY Command ............................48

SELECT operandSelection Rules ........................................60

SELECT Operand ..........................................58Example ...................................................61How to enter ...........................................58keywords .................................................59Relational Operators ..............................59Rules for strings......................................60

Separator character........................................87Share option 4 ..........................................22, 26Standard labels...............................................21START Command .........................................53

STARTCODE...........................................53STARTCODE

GENERATE Command .........................55START Command ..................................53

STATSCONTROL Command ...........................50

STOP Command ............................................54STOPCODE .............................................54

STOPCODEGENERATE Command .........................55STOP Command.....................................54

SUSPENDOPTION Command ...............................57

SyntaxCoding Operands ...................................88Comments ...............................................89Continuation ...........................................88Quoted Strings ........................................89Terminology............................................87

T

TASKIDENTIFY Command ............................48

TOLERATEOPTION Command ...............................57

Index

Page 98 CSI-JOURNAL

TRACECONTROL Command .......................... 51

TRANTERMIDENTIFY Command ........................... 47

U

USEREXITJOURNAL Command ........................... 46

Using CSI-JOURNAL................................... 19Activating ............................................... 28Deactivating ........................................... 30Execution Time Overrides.................... 37Option Table........................................... 31

V

VSAM Managed SAM............................ 20, 26

Reliant for VSE CSI-JOURNAL … · CSI-JOURNAL is a proprietary product of CSI International, Inc....

Documents

Transcript of Reliant for VSE CSI-JOURNAL … · CSI-JOURNAL is a proprietary product of CSI International, Inc....