Resolution:
Description:
============
After the upgrade to R5.2 the error in the title can be experienced using a map table that did not fail in R5.0.

Environment:
============
o all z/OS OSB customers upgrading to R5.2

Symptoms:
=========
The symptoms  are rules failures with the above error msg.

Cause:
======
The cause of this error is a correction of the map storage validation routines to now detect programs trying to access storage beyond the range they have access to. In earlier releases it was possible to read beyond the limit of your storage and possibly read bad data or have the rule fail, eventually, with an S0C4 abend.

Resolution:
===========
Correct your code to only access storage it has requested authorisationto access. This can be by adding a recurrance limit to a recurring map table or correct the length of the map table if too big.

An attempt was made to access unregistered memory for MAP table xxxxxxxxxxafter upgrade to R5.2.