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

Document ID:  TEC1058094
Last Modified Date:  06/30/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Endevor Software Change Manager

Releases

  • CA Endevor Software Change Manager:Release:18.0

Components

  • CA Endevor Software Change Manager:ENDBAS
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).

Question:

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

Answer:

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.    

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >