B97RLD: Reload batch utility

Overview

The reload batch utility (B97RLD) processes all existing reload requests. It reloads archived lists that have been marked for reload from the archive into the Adabas Audit Data Retrieval online spool. All indexes of these lists are reloaded into the Adabas Audit Data Retrieval index spool.

Online retention period after reloading

By default, reloaded lists and indexes remain in the Adabas Audit Data Retrieval online spool and index spool respectively for 5 days.

You can change this retention period by using these LST parameters:

  • B97_CLEANUP_RELOAD_LIST=n
    where n is the retention period of reloaded lists in days
  • B97_CLEANUP_RELOAD_INDEX=n
    where n is the retention period of reloaded indexes in days

The retention period of reloaded indexes should not be shorter than the retention period of reloaded lists.

Running B97RLD

You should run this utility at regular intervals during the day to ensure that the lists that users have marked for reloading are actually reloaded from the archive.

Tailored JCL for this job can be found in member B97RLD in the BETA97.CNTL.

You can also submit this batch utility online via option S.3.2. This will generate JCL from member SE97RELO of the BETA97.ISPSLIB (skeleton library).

Reload order

If a list and its indexes are available on several archive media, the archive medium used is determined by the value in the Order for Reload field of the archive pool definition. If reloading from one archive medium fails, other media are used according to their reload order.

By default, the Order for Reload field has the value ASIS (as is), which means that the reload batch utility uses archive media in the order specified in the archive subpool definitions.

For more information, see "Example: Overriding default order for reload".

JCL

+--------------------------------------------------------------------+
|jobcard |
|//B97RLD EXEC PGM=BST01RFF,REGION=0M,PARM=('S=97', |
|// 'PGM=B97RLD', |
|// 'B01LST=xx', |
|// 'B97LST=xx', |
|// 'SIGNON=YES') |
|//* |
|//STEPLIB DD DISP=SHR,DSN=BETA97.LOAD |
|// DD DISP=SHR,DSN=BSA.LOAD |
|//* |
|//SFFPARM DD DISP=SHR,DSN=BETA.PARMLIB |
|//B97DEF DD DISP=SHR,DSN=BETA97.DB.DEF |
|//* |
|//SFFFDUMP DD SYSOUT=* |
|//SYSABEND DD SYSOUT=* |
|//SYSPRINT DD DUMMY |
|//IRMPRINT DD SYSOUT=* |
|//IRMLIST DD SYSOUT=* |
|//IRMLOG DD SYSOUT=* |
|//IRMERROR DD SYSOUT=* |
|//* |
+--------------------------------------------------------------------+

Return codes

0

The program terminated normally.

4

The program did not find any data to be reloaded;
the program terminated normally.

>4

One or several errors occurred during processing.
Please check the job log for details.

Some return codes are program-specific. Others are standard return codes which can also be modified. More information on standard return codes can be found in "Return codes".

IRMPRINT

DD IRMPRINT contains a summary log displaying the lists, which were reloaded successfully, as well as the reload requests which could not be carried out. It contains the following information:

  • DATE / TIME: Creation date and time of the list/report
  • FORM / EXTENSION / REPORT: Name of the list
  • PAGES: Number of pages
  • Status: OK or error code

    For more information on the error codes returned by the OBJ server, see "Database codes" in BSA Messages and Codes.

+--------------------------------------------------------------------------------------+
|Date: 18.03.2020 Product: Beta 97 RELOAD UTILITY Page: 1 |
|Time: 15:48:52 Version: V7R2 |
| |
| |
|Date Time Form Extension Report Pages Status |
|---------- -------- -------- ---------------- ---------------- -------- ------- |
|10.03.2020 14:12:46 REJ TRADE 00000015 OK |
|10.03.2020 14:19:48 REJ TRADE 00000015 OK |
|10.03.2020 14:22:49 REJ INVENTORY 00000009 OK |
|11.03.2020 16:28:34 REJ TRADE 00000015 OK |
+--------------------------------------------------------------------------------------+

IRMLOG

A processing log is written to DD IRMLOG.

+-----------------------------------------------------------------------------------------------+
|IRM1561I PROGRAM: B97RLD VERSION: V7R2M00 PTFLVL: level COMPILED: date, time |
|IRM2800I RELOAD PROCESSING STARTED - DATE: 18.03.2020, TIME: 15:48:52 |
|IRM1801I ************************************************************************************* |
|IRM1801I 000004 RELOAD REQUEST(S) SELECTED |
|IRM1801I 000004 RELOAD REQUEST(S) SUCCESSFULLY PROCESSED |
|IRM1801I ************************************************************************************* |
|IRM2899I RELOAD PROCESSING ENDED - DATE: 18.03.2020, TIME: 15:48:52, RC: 0000 |
+-----------------------------------------------------------------------------------------------+

Automatic reloading

Automatic reloading means that the Adabas Audit Data Retrieval started task checks the number of reload requests that are waiting in the reload queue. If the specified limit has been exceeded, the STC calls a procedure, which in turn submits a reload job in order to process the reload requests with status WAITING.

Automatic reloading is controlled via the following LST parameters:

Parameter name

Value

Description

Default

B97_AUTORLD_ENABLED

YES | NO

Activates or deactivates automatic reloading

NO

B97_AUTORLD_INTERVAL

1..1440

Reload check interval in minutes

At the specified interval, the STC checks the reload queue for waiting reload requests. The STC starts the autoreload procedure if at least one of the following is true:

  • The number of reload requests with status WAITING exceeds the B97_AUTORLD_ REQUEST_ LIMIT_ LOW value.
  • The number of reload check repeats has reached the B97_AUTORLD_ SETTLE_ COUNT value.

60

B97_AUTORLD_REQUEST_LIMIT_LOW

1..99

At reload check, the STC starts the autoreload procedure if the number of reload requests with status WAITING exceeds the specified low limit.

10

B97_AUTORLD_SETTLE_COUNT

0..99

At reload check, the STC starts the autoreload procedure if the number of reload check repeats has reached the specified value. The STC starts counting the reload check repeats when reload requests with status WAITING are present, but their number is less or equal to the low limit.

You can use this parameter to limit the maximum waiting time of reload requests in the reload queue.

The value 0 disables this function.

1

B97_AUTORLD_PROCEDURE

name

Name of the RFF procedure that starts the reload job (required if B97_AUTORLD_ ENABLED=YES)

The procedure (default name: B97RLDA) is tailored during installation and then copied to the specified procedure library. Automatic reloading is deactivated if no name is specified.

Required: APF authorization

The steplibs of the reload procedure must be APF-authorized to enable the initialization of the new address space.

Instead of using a reload procedure, the STC can submit the reload jobs directly in its own address space. If you want this, code:

B97_AUTORLD_PROCEDURE = ##NONE##

none

Example

The following LST parameters are active:

B97_AUTORLD_ENABLED = YES
B97_AUTORLD_INTERVAL = 5
B97_AUTORLD_ REQUEST_ LIMIT_ LOW = 3
B97_AUTORLD_SETTLE_COUNT = 1
B97_AUTORLD_PROCEDURE = B97RLDA

The STC checks the reload queue at five-minute intervals. The activity of the STC depends on the number of reload requests at this moment:

0

There is no autoreload activity until the next reload check.

>3

The STC starts the autoreload procedure because of the low limit value.

<=3

The STC increases the reload check repeat counter by 1. At the next reload check, the STC will start B97RLDA because the reload check repeat counter has reached the B97_AUTORLD_ SETTLE_ COUNT value.

This means that the maximum waiting time of a new reload request is 10 minutes.