How to address problems with insufficient LSQA in the Alchemist started task?
search cancel

How to address problems with insufficient LSQA in the Alchemist started task?

book

Article ID: 53740

calendar_today

Updated On:

Products

Alchemist TPX - Session Management Vman Session Management for z/OS

Issue/Introduction

ZDE9600I SR.RX{luname.request-id} PROCESSING unit-of-work
ZDE9006E SR.RX{luname.request-id} TASK ABENDED: S80A
IEW4004I FETCH FOR MODULE ZAASERV FROM DDNAME STEPLIB FAILED BECAUSE INSUFFICIENT LSQA STORAGE WAS AVAILABLE
IEW4005I FETCH FOR MODULE ZAASERV FROM DDNAME STEPLIB FAILED BECAUSE IEWFETCH ISSUED RC 0C AND REASON 04
CSV031I LIBRARY ACCESS FAILED FOR MODULE ZAASERV , RETURN CODE 24, REASON CODE 26080021, DDNAME STEPLIB
CSV028I ABEND106-0C JOBNAME=jobname STEPNAME=stepname

 

Environment

Release:
Component: ALCMST

Resolution

We do recommend REGION=0M as a starting point.

However, since every shop configuration is different we can't make absolute out-of-the-box predictions of what will be best for you.

0M will cause private used region to be high so that LSQA cannot grow and the ABEND106 occurs. By specifying a specific value such as 128M, this will cause less private region to be used, so LSQA can grow as needed and no abend.

Should you encounter this situation:

  1. Verify that you have all fixes in place that correct memory and storage problems.
  2. Open an issue with CA Support and provide a complete Alchemist started task log as well as an SVC dump for analysis.
  3. Try changing REGION to a specific value, such as 128M. This can be a temporary or permanent workaround. Dump analysis will identify if there are any other contributing factors.