Endevor ESI to disallow TRANSFER FROM subsystem.stage 1 TO subsystem2.stage 1

book

Article ID: 220753

calendar_today

Updated On:

Products

CA Endevor Software Change Manager (SCM)

Issue/Introduction

Our site uses SUBSYSTEMS in stage 1 for concurrent dev paths.  The merge is done using the TRANSFER to Subsystem STD stage 1 and then a MOVE to STD stage 2.

But the TRANSFER to Subsystem STD stage 1 really serves no functional purpose so users would like to TRANSFER right to Subsystem STD stage 2.  Can ESI be used to stop the TRANSFER to SBS2 in STG1? 

Environment

Release : 18.1

Component : CA Endevor Software Change Manager

Resolution

Yes ESI can be used to stop the transfer into STG1 SBS2. Here is an example of the ESI Calls that are made at SUBS1 (the source location) and SUBS2 (the target location) that you want to stop. 

ESI CALL For Transfer from subs1 stg1 - check at source location 

Format=0004 Pass=0000 Auth=CNTL ACEE=00000000 C1BM4210 XXT1
Class=DATASET  Log=NONE   Func=DELETE                      
Entity=C1.TESTENV.D.SYSTEM1.SUBS1.DECLINK.ELEMENT1         
User PILRO01  access is allowed  from SAF  in WARN mode    
RACROUTE RC=0000 RACHECK RC=0000 Reason=0000  

            
Format=0005 Pass=0000 Auth=CNTL ACEE=00000000 C1BM4210 XXT1
Class=DATASET  Log=NONE   Func=DELETE                      
Entity=C1.F5.TESTENV.D.SYSTEM1.SUBS1.DECLINK.TRANSFER      
User PILRO01  access is allowed  from SAF  in WARN mode    
RACROUTE RC=0000 RACHECK RC=0000 Reason=0000

ESI CALL For Transfer to stg1 subs2 - check at target location 

Format=0004 Pass=0000 Auth=UPDT ACEE=00000000 C1GTI000 CAX1
Class=DATASET  Log=NONE   Func=ADD                         
Entity=C1.TESTENV.D.SYSTEM1.SUBS2.DECLINK.ELEMENT1         
User PILRO01  access is allowed  from SAF  in WARN mode                        
RACROUTE RC=0000 RACHECK RC=0000 Reason=0000      

        
Format=0005 Pass=0000 Auth=UPDT ACEE=00000000 C1GTI000 CAX1
Class=DATASET  Log=NONE   Func=ADD                         
Entity=C1.F5.TESTENV.D.SYSTEM1.SUBS2.DECLINK.TRANSFER      
User PILRO01  access is allowed  from SAF  in WARN mode    
RACROUTE RC=0000 RACHECK RC=0000 Reason=0000  

To do this block the users from the format 5 call -  c1.f5.env.stg.sys.subs.type.TRANSFER 

Rules will need  to be specific because if a wildcards are used  it will stop tthe users from any env, stg, sys, subs, type ...