LDM0521E RC=64 Reason=140 received in Lserv started task joblog, what actions to take.


Article ID: 52714


Updated On:


CA Bundl CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom CA DATACOM - AD CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM) 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 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 Datacom/AD



This document will detail the steps to take when receiving LDM0521E RC=64 Reason=140 in the Lserv started task joblog.

Note: Lserv is used (most often) to manage Endeavor vsam files. This Knowledge Document takes the above into account.


The LDM0521E RC=64 Reason=140 message (most commonly) indicates an out-of-synch condition.

We typically see this when the Lserv address space is recycled while some Endevor users are active (but possibly dormant). On the restart of Lserv, the user has continued Endevor processing but is no longer recognized by Lserv as its token has been lost on the restart. The Reason Code X'140' means 'session not active for this user'.

The solution is to recycle Lserv again, after first ensuring that no users are using Endevor.

In the event the above is not the case, please contact CA Support.


Component: CCS390