After I went through all the malarkey a couple of years ago, repeatedly 
losing exit points (due to an IBM API bug), I wrote the following CL 
program:
  PGM
  DCL        VAR(&YYYYMMDD) +
             TYPE(*CHAR) +
             LEN(8)
  DCL        VAR(&SAVF) +
             TYPE(*CHAR) +
             LEN(10)
  RTVDAT     CCYYMMDD(&YYYYMMDD)
  CHGVAR     VAR(&SAVF) +
             VALUE('EP' *CAT &YYYYMMDD)
  CRTSAVF    FILE(JEFF/&SAVF) +
             TEXT('Save of QUSRSYS/QUSEXRGOBJ  *EXITRG')
  SAVOBJ     OBJ(QUSEXRGOBJ) +
               LIB(QUSRSYS) +
               DEV(*SAVF) +
               OBJTYPE(*EXITRG) +
               SAVF(JEFF/&SAVF) +
               DTACPR(*MEDIUM)
  ENDPGM
It simply creates a save file (EPyyyymmdd) in my private test library 
and saves the exit points there.  The job scheduler runs it every 
Thursday at 9am.  Since I'm continually in that library, I regularly 
notice these and delete all but the last couple of them.
Since writing this program, I've never lost the exit points.  Murphy 
lives. <g>
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.