Custom Search

ENDEVOR MISCELLANEOUS CLEANUP WORK

MISCELLANEOUS CLEANUP WORK

Even if a system is in Endevor, you will still do development and testing outside of Endevor, therefore, it is still necessary to do this cleanup work.

COMMON(BATCH & ON-LINE)

• Delete any copybooks that went into production from 'OTXX94.COPYLIB.DATA'
Delete copylib member from located in the current implementation folder.

• Cleanup your own libraries of Source code, Copybooks, and DBRMS.

• If program has db2, delete any related DBRM's from 'OTXX94.LIB.DBRM'. OTDPIMSP, OTDPDB2P, OTDB2CLM, OTNICADP, and OTPOOL are the execptions to this rule. They are subprograms that get compiled/linked into both 'OTXX94.JOBLIBT' and 'PROD.OT.IMSLOADT' and bound into plans used by many link groups. If these members get deleted from the test DBRM library you will get a -818 timestamp error in any program accessing them. This is because the bind is using the production DBRM and the object module used to create the load member will still be the one from the last IMST compile/link. Therefore the timestamps in the OBJ and DBRM do not match, resulting in a DB2 return code of -818. Hence, don't delete these DBRMS (also, don't delete these load modules from 'OTXX94.JOBLIBT and 'PROD.OT.IMSLOADT').

• If a PSB was used in a new program or added to an existing program, update the PSB cross reference DB2 table, BATCHBOT.OTXPSBXT, with the production PSB information.

• Cleanup $avers after you get your jobs back. Be sure that all T, X and P jobs are deleted.

• If a new bind was either added or revised to use the IMS exit program or the DB2 exit program, update the DPROP Users Guide document by adding the bind to the List of Binds For IMS and DB2 Propagation under Nifty Things To Know in SERVER/PAL INFO/OVERVIEW/DPROP

• If a new bind was created, refer to Section XIII DB2 PROCEDURES Step D.

• If a new Follow-UP note was created, update the following documents:

SERVER/PAL INFO/OVERVIEW/FOLLOWUP/PGMTRACK.XLS
SERVER/PAL INFO/OVERVIEW/FOLLOWUP/WORKFLOW.XLS
SERVER/PAL INFO/OVERVIEW/FOLLOWUP/SEG VALUES.XLS

• If a new DB2 table, Database, ACES Table (TMS), Cobra File or Property File created update.
PAL INFO\DATABASE\ACES DATABASE & TMS SUMMARY