Copyright © Cloud Software Group, Inc. All Rights Reserved

Specific Implementation Steps

Step 1: Customize Symbolic Parameters

Use the ISPF standard OSEMOD customization macro to customize the symbolic parameters for the JCL member BATJRNL.

Step 2: Modify JCL

Modify your utility JCL to conform to the BATJRNL member in the JCL data set distributed with TIBCO Object Service Broker. This involves several steps:

1.	Using step 1 of the BATJRNL as a sample, add JCL to allocate the batch journal.

Do not attempt to initialize batch journals (unlike with Data Object Broker journals).

2.	Add PARM='....,JOURNAL=Y' to the utility EXEC parameter.

3.	Add JCL to reference the batch journal data set in the utility step, for example:

//JOURNAL  DD  DISP=OLD,DSN=$HLQVSAM$.$SLQ$.BATCH.JRNL1

4.	Add subsequent job steps SPIN1, TESTSPN, and SPAWN to do the following:

−	SPIN1 to copy the batch journal data to a new SPINOUT GDG.

−	TESTSPN to check the number of generations of SPINOUT GDGs.

−	SPAWN to submit a SPINMRG job to consolidate the SPINOUT GDGs into a new SPINMRG GDG data set. This job step executes only if the number of SPINOUT GDGs found by step TESTSPN exceeds your generation limit.

Post Processing Requirements

After completing the previous steps, you must also do the following:

•	Copy the journaled images into your spin/merge process even if the utility does not terminate successfully.

•	Delete and redefine the batch journal data set, each time you run the utility.

•	As with all SPINs, ensure that all journaled images are first copied into your spin/merge process successfully. Failure to do so causes your spin merged backup to be incorrect.

•	Run S6BBRPTR (Batch Pointer Check) against your spin/merged backup on a regular basis.

Copyright © Cloud Software Group, Inc. All Rights Reserved