Endevor element transfer error while deleting the element

[sREEKANTH GU]

Hi Team,

Hope you are doing well. 

We are trying to delete elements from endevor which are not used from many years but endevor is trying to archive these elements.

We created a package to delete elements from Endevor and executed the package, the element is deleted from Endevor library but still in Endevor because of the Archive error. We do not want to archive. Is there any Endevor utility program available which wont archive the elements during deletion process? Please help me. Thank you.

Error:

04:00:17  C1G0202I  ACTION #1 / STMT #1                                                                             

04:00:17  C1G0203I     TRANSFER ELEMENT XXXXXXX                                                                     

04:00:17  C1G0204I        FROM ENVIRONMENT: PROD     SYSTEM: CEC      SUBSYSTEM: PCTL     TYPE: CNTL     STAGE ID: P

04:00:17  C1G0204I        TO   ENVIRONMENT: ARCH     SYSTEM: CEC      SUBSYSTEM: PCTL     TYPE: CNTL     STAGE ID: 1

04:00:17  C1G0232I        OPTIONS:  OVERRIDE SIGNOUT, BYPASS ELEMENT DELETE, WITH HISTORY, SYNCHRONIZE, SIGNIN      

04:00:17  C1G0232I                  CCID: xxxxx                                                                 

04:00:17  C1G0232I                  COMMENT: XXXXXX                                                              

04:00:17  C1G0265I  PROCESSOR GROUP UTLNNPNN FOR THIS ELEMENT WAS OBTAINED FROM PRIMARY ELEMENT RECORD              

04:00:17  C1E0107I  USER XXXXX RESTRICTED FROM FUNC ADD RESOURCE $ENDVR.ARC1.TRANSFER                             

04:00:17  C1E0105E  A SECURITY VIOLATION HAS OCCURRED. ACTION DENIED.                                               

04:00:17  C1G0200I  ELEMENT ACTION REQUEST PROCESSING COMPLETED, HIGHEST ENDEVOR RC WAS 0012                        

I'm not sure what $ENDVR.ARC1.TRANSFER refers to. It's not a dataset that i see in Mainframe. I don't even see a *.ARC1.TRANSFER dataset.

Thanks,

Sreekanth

[John Scott]

Hello Sreekanth,

The user does not have access to TRANSFER to the ARCH environment. 

$ENDVR.ARC1.TRANSFER refers to a security resource that Endevor is checking on behalf for the user.

The user does not have sufficient access to do a TRANSFER action affecting ARC1 and Endevor issues the message.

The format of the security resource being checked is set up by the Endevor administrator in the BC1TNEQU table.

The access to the security resources (controlling who can do what in Endevor) will probably be defined by a security administrator. 

 

[sREEKANTH GU]

Hi John,

Thank you for the information.

We do not want to transfer/ARCH to ARCH environment because these elements are not used again (Application decommissioned).

Is there any way to skip the transfer/ARCH? Please let me know. Thank you.

[Joseph Walther]

There is a way to skip the transfer/ARCH, by using a TRANSFER with this syntax:

TRANSFER ELEMENT FROM .... TO DDNAME  'VAPOR' ....  OPTIONS ......  .

Then in your JCL, you can include:

//VAPOR    DD DUMMY

The result is the removal of the element, with no dependency on an ARCH environment. Plus, you have the option to BYPASS DELETE PROCESSOR. 

With this kind of Transfer/Deletion, you do not have an easy method for putting it back if you change your mind.  That is where the transfer/ARCH procedure has an advantage.

[sREEKANTH GU]

Thank you for the information Joseph. Transfer is not an option in my scenario.

[John Scott]

If you have control over the SCL being used in the package you could request a DELETE action instead of a TRANSFER action. 

[sREEKANTH GU]

Hi John,

Thank you for your quick reply. We are using Delete only inside Package like below. Still the Endevor is trying to transfer to ARCH environment. I can see the particular element was deleted from Endevor library but not from Endevor because of ARCH issue.

DELETE ELEMENT 'XXXXXXXX'                                         
  FROM ENVIRONMENT 'PROD' SYSTEM 'CEC' SUBSYSTEM 'PCTL'           
    TYPE 'PROC' STAGE P                                           
  OPTIONS CCID 'XXXXX' COMMENTS "XXXXX" OVERRIDE SIGNOUT
 .                                                                

[John Scott]

If you are not explicitly specifying the TRANSFER in your package then it is likely it is being included by some additional customisation of Endevor that is specific to your site. (and you do not have access to do the transfer to the arch environment). In that case the customisation for the transfer was likely included by design choice at your site so the element is available after the delete from prod. 

Could you request the necessary access to the arch environment as an alternative to trying to bypass the transfer that has been included ?  

[sREEKANTH GU]

Hi John,

Thank you for helping me. It seems they did some customization where no one can delete/Transfer without ARCH. I will check internally again. 

[Karen Turner]

It sounds like your delete processor(s) contain a c1bm3000 step to do the transfer to archive action.  We have similar functionality, but we perform the archive action, plus back up all associated output components for safe keeping.  If the elements are all the same type and use the same processor group, you could update the proc group definition to use a delete processor that does not contain the archive action, or add a Y/N if-then-else, (or EXECIF) switch around the archive logic. this way you could do a processor group override for that switch for this batch of deletes then reset it back to Y. 

//* PARAMETERS FOR ARCHIVING PRODUCTION ELEMENTS BEING DELETED     *         
//        ARCEXEC=Y,    

.

.

.                                                    
 //IFARCH  IF (('&C1STAGE(2,4)' ='PROD') AND                            
 //            (&ARCEXEC =  Y))  THEN                                   
 //*------------------------------------- START DARCEXE INCLUDE --------
 //*********************************************************************

------------------------------
Karen
[JobTitle]
[CompanyName]
[State]
------------------------------

[sREEKANTH GU]

Hi Karen, 

Thank you for the inputs but i did not see the mentioned step in my JCL. Can you please check my JCL once and recommend. 

//PRDSWEEP EXEC PGM=NDVRC1,DYNAMNBR=1500,PARM='ENBP1000'                
//C1MSGS1   DD SYSOUT=*                                                 
//C1MSGS2   DD SYSOUT=*                                                 
//EN$TRESI  DD SYSOUT=*                                                 
//JCLIN     DD DSN=NDVR.XXX.ADMP.PRMLIB(JOBCARD),DISP=SHR               
//ENPSCLIN  DD *                                                        
 EXECUTE PACKAGE WK*                                                    
     OPTIONS WHERE PACKAGE STATUS IS APPROVED                           
 .                                                                      
/*                                                                      
//********************************************************************* 
//JCLOUT   DD SYSOUT=(A,INTRDR),                                        
//            DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)                      

-----------------------

VIEW       NDVR.XXX.ADMP.PRMLIB(JOBCARD) - 01.09           
Command ===>                                               
****** ***************************** Top of Data **********
000001 //ENDVOR   JOB 0768,                                
000002 //            'CORP.ENDEVOR MC:14740',              
000003 //            CLASS=X,                              
000004 //            NOTIFY=SYSID,                         
000005 //            MSGCLASS=H,                           
000006 //            REGION=4096K                          
000007 //*JOBLIB   DD DSN=SYSACS.ENDEVOR.CSIQLOAD,         
000008 //*            DISP=SHR                             
****** **************************** Bottom of Data ********

[Karen Turner]

Hi Sreekanth,

My pleasure to help...It's not in your package jcl it is a result of the DELETE actions coded in your package.  Delete actions kick off delete processors (which look like jcl).  Can you attach the full C1MSGS1 of the job getting the security violation?  My guess is the transfer is coded in the delete processor. If not, it's coming from an exit.  If we can see the full sysout we'll be better able to help you narrow down the origin of the Transfer action.

Karen

------------------------------
Karen
[JobTitle]
[CompanyName]
[State]
------------------------------

[sREEKANTH GU]

Hi Karen,

Thank you. I can see "c1bm3000" in other user's spool job.

Please find the spool job attached. Please review the job and recommend the changes to the jcl.

Attachment(s)

Endevor Delete JCL.txt   50 KB 1 version

[Karen Turner]

1. Delete of element of TYPE CBL from inventory area PROD/COR/@EAF/P (from SCL)

2. The CBL element in question uses processor group COBIBLNN (from statement: 

C1G0265I  PROCESSOR GROUP COBIBLNN FOR THIS ELEMENT WAS OBTAINED FROM PRIMARY ELEMENT RECORD

3. Delete processor for COBIBLNN is DXFR (note XFR is an obvious abbreviation for Transfer)

 BEGINNING EXECUTION OF DELETE PROCESSOR DXFR OF GROUP COBIBLNN

4. DXFR contains Transfer scl:

                     C1G0249I  //*--------------------------------------------------------------------

                     C1G0249I  //*

                     C1G0249I  //*  Transfer the base element --AND-- copy the associated

                     C1G0249I  //*  output component(s)... to the ARC environment.

                     C1G0249I  //*    Stage 1 - ARC1 (Archive)

                     C1G0249I  //*    Stage 2 - ARC2 (Processor Change)

                     C1G0249I  //*

                     C1G0249I  //*  The ARC2 Stage will be chosen during a MOVE to PROD/PRDU when the

                     C1G0249I  //*  following message is issued in the C1MSGS1 output:

                     C1G0249I  //*

                     C1G0249I  //*  C1G0012W   PROCESSOR GROUP CHANGE - EXECUTING DELETE PROCESSOR

                     C1G0249I  //*             FOR GROUP &C1PRGRP.

                     C1G0249I  //*

                     C1G0249I  //*--------------------------------------------------------------------

                     C1G0249I  //ARCHBASE EXEC PGM=C1BM3000,

                     C1G0249I  //            PARM='SCLIN,MSGOUT1',

                     C1G0249I  //            MAXRC=8,

                     C1G0249I  //            COND=(0,LT)

                     C1G0249I  //MSGOUT1  DD SYSOUT=*,

                     C1G0249I  //            FREE=CLOSE

                     C1G0249I  //SCLIN    DD *

                     C1G0249I   TRANSFER  ELEMENT     '&C1ELEMENT'

                     C1G0249I     FROM    ENVIRONMENT '&C1EN'

                     C1G0249I             SYSTEM      '&C1SY'

                     C1G0249I             SUBSYSTEM   '&C1SU'

                     C1G0249I             TYPE        '&C1TY'

                     C1G0249I             STAGE       '&C1STGID'

                     C1G0249I     TO      ENVIRONMENT '&ARCENV'

                     C1G0249I             STAGE        &ARCSTG

                     C1G0249I     OPTIONS CCID        '&C1CCID'

                     C1G0249I             COMMENTS    '&C1COMMENT'

                     C1G0249I             BYPASS ELEMENT DELETE

                     C1G0249I             OVERRIDE SIGNOUT

                     C1G0249I             SIGNIN

                     C1G0249I             WITH HISTORY

                     C1G0249I             SYNCHRONIZE

                     C1G0249I    .

                     C1G0249I  /*

 

Which is where you are getting the security violation.

 

 

                                 PROC  NDVR   +------------  INVENTORY  INFORMATION  -----------+  ACTION   ACTION   STMT    SCL

           ACTION    ELEMENT      RC    RC    ENVIRONMENT   SYSTEM    SUBSYSTEM   TYPE     STAGE    TIME    NUMBER  NUMBER WRITTEN

 *FAILED*  TRANSFER  XXXPRGM1          0012   PROD          COR       @EAF        CBL        P    16:53:23       1       1

1   Endevor     Version 19.0.00        Copyright (C) 2022      Broadcom. All Rights Reserved.      04MAR25 16:53:24     PAGE     1

                                      E N D E V O R   A C T I O N   S U M M A R Y   R E P O R T

 REQUESTED BY: USER1

 

 

                                 PROC  NDVR   +------------  INVENTORY  INFORMATION  -----------+  ACTION   ACTION   STMT    SCL

           ACTION    ELEMENT      RC    RC    ENVIRONMENT   SYSTEM    SUBSYSTEM   TYPE     STAGE    TIME    NUMBER  NUMBER WRITTEN

 *FAILED*  DELETE    XXXPRGM1    0012  0012   PROD          COR       @EAF        CBL        P    16:53:22       1       2

 

Since the imbedded transfer fails, the delete fails.

 

Possible Solutions:

 

1) If you are the endevor admin, use the Endevor panels to temporarily replace DXFR with *NOPROC*:

choose PROD from Environment Selection list, then 4 for Environment, 6 for processor group

Specify PROD,COR,CBL,COBIBLNN,P in the appropriate fields and hit enter.

On the next panel change DXFR to *NOPROC* and press enter

Run the delete

Put DXFR back.

 

2) edit DFXR to add an ITE switch as I suggested earlier:

On the Proc statement create a new processor symbolic -- BYPXFR perhaps ? 

ex:  //    BYPXFR=N,

 

Then insert I-T-E test around the xfer step:

 

//IFBYPXFR  IF (BYPXFR=N) THEN

//ARCHBASE EXEC PGM=C1BM3000,

.

.

.                    

             BYPASS ELEMENT DELETE

             OVERRIDE SIGNOUT

             SIGNIN

             WITH HISTORY

             SYNCHRONIZE 

           .

/*

//IFBYPXFR ENDIF

 

Then anytime you want to skip the transfer, you follow the same steps in option 1, but instead of replacing the processor you can just override this symbol to Y, run the delete then put it back.

 

If you don't want to deal with processor group overrides, you could pass a literal as part of the CCID or COMMENT and use that for your ITE test:

ex: //IFBYPXFR  IF ('&C1CCID(1,6)' NE 'BYPXFR') THEN 

[comment syntax '&C1COMM(1,6)' NE 'BYPXFR') THEN ]

 

It has to be a negative test (ie = N, or NE value, since this is an exception to the default process of always transferring to the ARCH env.

 

Hope this helps.

 

Karen

------------------------------
Karen
[JobTitle]
[CompanyName]
[State]
------------------------------