LDM0521E RC=64 Reason=140 received in Lserv started task joblog

Products

• Bundl
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• Datacom
• DATACOM - AD
• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

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 Endevor VSAM files. This Knowledge Document takes the above into account.

Environment

Release:
Component: CCS390

Resolution

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

This typically happens when the L-Serv 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 L-Serv 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 L-Serv again, after first ensuring that no users are using Endevor.

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