CA Common Services L-Serv stopped Address Space Unavailable.

book

Article ID: 16893

calendar_today

Updated On:

Products

CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu

Issue/Introduction

Every Sunday L-Serv is stopping and coming up with the following error:
IEF352I ADDRESS SPACE UNAVAILABLE

Last week we raised a change to up the region size from 64M to 128M however we are still getting the above error.

Is there any issues with this?

It starts straight back up once it has ended, would you recommend increasing the region size again?


 



Why do I have the message IEF352I ADDRESS SPACE UNAVAILABLE when L-Serv stops?

 

 

Environment

CA COMMON SERVICES 14.1 - LSERV 14.0 - z/OS supported releases -

Resolution

Here are the information about this message:

IEF352I ADDRESS SPACE UNAVAILABLE

z/OS issues the message when an address space uses space-switching PC routines.

When ending a batch job, started task, or TSO user, the initiator/terminator found that this address space had been used to provide services to other address spaces through space-switching PC routines.

In order to maintain system integrity, the address space is ended and is marked as unavailable.
This does not necessarily indicate an error in the program or in the initiator.

LSERV uses space switching PC routines so this message is issued when LSERV is shut down.
It's normal for LSERV, the message doesn't cause any problem.

Additional Information

CA L-SERV documentation can be read at the following link:

https://docops.ca.com/ca-common-services-for-z-os/14-1/en/installing/ca-l-serv-configuration-tasks