Troubleshooting Adabas Event Replicator on z/OS Command Code A1 Error 77 Subcode 11

Introduction

This guide will cover the cause and the solution of “Command Code A1 Error 77 Subcode 11”, as well as provide some tips on how to prevent it from happening again. By following the steps, you will be able to resolve the error and continue using ADABAS smoothly.

Pre-requisite

Product:	Adabas Event Replicator Server
Version:	3.8.1
Platform:	Mainframe
Operating System:	z/OS

Problem

When using Replicator on the mainframe with EntireX and PSI (Persistent Store) in the Adabas file.

Adabas command code A1 received Error 77 Subcode 11 as per below:

Diagnostic Values: 
ADABAS response code 77 
ADABAS command code A1 Error 77 Subcode 11 
WRITE failed 
Diagnostic Values: 
ADABAS CMD A1 RSP 77 SUBCODE 0x0000000B (UPD MSG)         

Under EntireX the following error messages are seen:

Diagnostic Values:                                                                                                                                                                                
ADABAS response code 77                                                                                                                                                               
ADABAS command code A1 Error 77 Subcode 11                       
WRITE failed
Diagnostic Values:
ADABAS CMD A1 RSP 77 SUBCODE 0x0000000B (UPD MSG)       

Resolution

In this scenario, the recommendation is to instruct the client to run an ADAREP on the PSI database to determine the size of the database, the size of the PSTORE file, the use of blocks on the PSTORE file, and the amount of empty space on the database for ASSO and DATA.

To solve the issue, you can:

1. Try rebuilding the FST of the PSTORE DB using the software ADADBS RECOVER. The RECOVER function recovers allocated space by rebuilding the free space table (FST). The RECOVER function subtracts file, DSST, and alternate RABN extents from the total available space.
2. If it does not solve the error, the recommendation is: a) Increase the size of the database, and b) take action to reduce the number of records on the file.

Additional tips

• Make sure that DSREUSE is turned on so that the file is setup optimally for Broker.

• Investigate utilizing the ADABAS functionality to automatically increase ASSO and DATA. See:
  
  – AUTOINCASSOSIZE Parameter: Associator Automatic Database Increase Size
  
  – AUTOINCASSOTHRESHOLD Parameter: Associator Space Threshold
  
  – AUTOINCASSOTOTAL Parameter: Associator Space Maximum Size
  
  – AUTOINCDATASIZE Parameter: Data Storage Automatic Database Increase Size
  
  – AUTOINCDATATHRESHOLD Parameter: Data Storage Space Threshold
  
  – AUTOINCDATATOTAL Parameter: Data Storage Space Maximum Size

• A new ASSO or DATA component can be formatted to utilize the ADADBS ONLADD utility and add the new component while the Adabas nucleus is still active. This allows to add more space without shutting the database down
  
  – ONLADD: Allocating New ASSO or DATA Space Dynamically

• The ADADBS ONLREORFDATA utility can be used to reorder the file while activity is ongoing. The ONLREOR* utilities does not change any of the existing extents but does move records around within the existing extents in order to free up fragmentation. There is also an ONLREORFILE (for ASSO and DATA) and ONLREOFASSO.
  
  – ONLREORFASSO: Start Online Reorder Associator for Files
  
  – ONLREORFDATA: Start Online Reorder Data for Files

Useful links | Relevant resources

The RECOVER function subtracts file, DSST, and alternate RABN extents from the total available space. Read more:

• RECOVER: Recover Space

Read full topic