If I run two separate Endevor applications on different LPARs, it is using the same profile for both. How can I fix this situation?

Products

• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench

Issue/Introduction

I have two separate Endevor applications running.  One is Production located on LPAR1. The other is Test running
on LPAR2.  

My problem seems to be that I am picking up the wrong information from my stored profile.

What can I do to fix this so that each LPAR has its own profile?

Environment

Release:
Component: ENDBAS

Resolution

That some of the information is being saved in Endevor panels is also stored in our profile dataset located in USERID.ISPF.ISPPROF(CTLIPROF).  

To create multiple profile members during the startup of the production clist will look like this:

/* INVOKE ENDEVOR */                                       
"ISPEXEC SELECT PGM(C1SM1000) NOCHECK NEWAPPL(CTLI) PASSLIB"
/* CLEAN UP */  

Change the test clist to look like this:

/* INVOKE ENDEVOR */                                        
"ISPEXEC SELECT PGM(C1SM1000) NOCHECK NEWAPPL(CTLJ) PASSLIB"
/* CLEAN UP */          

 

This small change for CTLI to CTLJ will then cause two profile members to be created in the users CTLIPROF member.  Each logon will look only for the LPAR that they are running on even though they use the same CTLIPROF member.