Why doesn't ALLOC=LMAP/PMAP always work in a CA Endevor Processor ? It works for some systems, but not others.

book

Article ID: 14541

calendar_today

Updated On:

Products

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)

Issue/Introduction

We are using LMAP for our lib concatenation. When we compile/link in one of our systems (EFT)the LMAP stops at the pre production stage (INTG) and doesn't include the prod stage libs. But the LMAP works in a different system (INTERN).



Why doesn't ALLOC=LMAP/PMAP always work in a processor ? It works for some systems, but not others.  

Environment

Release:
Component: ENDBAS

Resolution

Check that the mapping is complete. Check that type, system, subsystem are all mapped. It is possible to use the Comma Separated Value to check mapping. Also, run with the trace dd, '//EN$TRIMR  DD SYSOUT=*',  to see if there are any errors. Under current releases, mapping must be complete.