Is it possible to change the SYSTEM and/or the SUBSYSTEM for a Endevor element at the production stage and reflect those changes in the object footprints?
Article ID: 38646
Updated On:
Products
Issue/Introduction
Can we change the Element's SYSTEM and/or SUBSYSTEM for Endevor Elements? Would the output objects footprints be changed also?
Environment
Release: all
Component: ENDBAS
Cause
require change to SYSTEM and/or SUBSYSTEM
Resolution
Two methods can do this. Each has advantages and disadvantages.
The first method is to add the source back to the lowest stage and promote it back to production. The advantage of this method is it's a standard way of doing things. So no processors are changed and the history would reflect what was done. The disadvantage of this method is if you are changing load objects(programs) the risk is that the programs would have changed. So testing of the programs would be required.
The next method is to TRANSFER the element from the old SYSTEM and/or SUBSYSTEM to the new SYSTEM and/or SUB system. You must TRANSFER with history and leave the GENERATE and DELETE processors active. The GENERATE processor must be altered to do a BSTCOPY of all output objects that are attached to the element. This would require a BSTCOPY to a temporary file and then BSTCOPY to the target file. This is because BSTCOPY does not allow a member to be copied to itself. The delete must be done so that output objects are not deleted only the old Element. The advantage with this method is that objects(programs) are not altered. Only the footprint gets updated with the BSTCOPY. The disadvantages with this method are that the setup time would be longer. This time would involve the research of each type and the writing of new processors. It is also recommended that after the method you run "CONRPT83: Footprint Exception Report" to check for errors.
Additional Information
It is recommended that you ask your auditors what method they would accept. They may not accept a direct change to production like in the TRANSFER method.
If you alter the Element SYSTEM and/or SUB SYSTEM using TRANSFER you must use generate. This is because both SYSTEM and SUB SYSTEM are in the object footprint. The generate would refresh the footprint thus avoiding footprint mismatch errors.
Before starting this process please call support. This is not a simple task to do.
SAMPLE PROCESSOR:
//************************************************************
//*
//*PROCESSOR TO BE USED WHEN CHANGING THE SUBSYSTEM / SYSTEM
//*
//* ALTER SYMBOLIC LOADLIB1
//*
//* ALTER UNIT, SPACE, DSNTYPE AND DCB FOR DD OUT1.
//*
//*
//CHGSUB PROC LOADLIB1='<LVL1>.<LVL2>.<LVL3>'
//************************************************************
//* COPY TO TEMPORARY PDSE
//************************************************************
//CPY1 EXEC PGM=BSTCOPY,MAXRC=04
//SYSPRINT DD SYSOUT=*
//SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(1,1))
//INDD DD DSN=&LOADLIB1,DISP=SHR
//OUTDD DD DSN=&&TEMPDSN,DISP=(NEW,PASS),UNIT=WORK,
// SPACE=(CYL,(5,5,44)),DSNTYPE=LIBRARY,
// DCB=(LRECL=0,BLKSIZE=32760,RECFM=U,DSORG=PO)
//SYSIN DD *
COPY OUTDD=OUTDD,INDD=((INDD,R))
SELECT MEMBER=&C1ELEMENT
//************************************************************
//* COPY TEMPORARY PDSE TO LOADLIB(CHANGING FOOTPRINT)
//************************************************************
//CPY2 EXEC PGM=BSTCOPY,MAXRC=04
//SYSPRINT DD SYSOUT=*
//SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(1,1))
//SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(1,1))
//OUTDD DD DSN=&LOADLIB1,DISP=SHR,MONITOR=COMPONENTS
//INDD DD DSN=&&TEMPDSN,DISP=SHR
//SYSIN DD *
COPY OUTDD=OUTDD,INDD=((INDD,R))
Feedback
