Back To LeighWeb Mainframe Utilities Page

 APPLCMPR is designed to compare a CSP application which is currently in the
 DEVL environment in ENDEVOR with the same application (element-for-element) as
 it exists in its next-most-recent form in the ENDEVOR promotion map.

 APPLCMPR operates in ISPF and is invoked as follows:

 COMMAND ===> TSO APPLCMPR xxxxx {edit} {class(l)}

 Where:

 "xxxxx" = The CSP application name

 EDIT is a keyword parameter which indicates that the JCL which is created is to
      be edited instead of automatically submitted.

 class(l) is a parameter which indicates that instead of using job class 5, (the
          default), job class L should be used.  Note: The job which is created
          will not run in class 1 due to the amount of processing necessary.

 The output from the compare job consists of five sequential files named:

 userid.APPLCMPR.applicationname.APPL
 userid.APPLCMPR.applicationname.MAPG
 userid.APPLCMPR.applicationname.PROC
 userid.APPLCMPR.applicationname.RECD
 userid.APPLCMPR.applicationname.SGRP

 These files hold SUPERCE compare output for the application element, any map
 group elements, any process elements, any record elements, and any statement
 group elements.  An explanation of how APPLCMPR works may aid in the
 understanding of its value and its outputs.

 First, when you invoke APPLCMPR with an application name, it invokes ENDEVOR in
 "foreground batch" to get the LISTAD element associated with that application.
 This brings up a good point, an application needs to have been generated in
 ENDEVOR at least once prior to running APPLCMPR so that a valid LISTAD element
 exists.  APPLCMPR then uses the contents of the LISTAD to build JCL
 which will do the following:

 1. Retrieve (NOSIGNOUT) each element from ENDEVOR twice; first beginning  the
    search for the element from the DEVL stage, and then beginning the search
    for the element from the QUAL stage.  This results in a pair of each element
    in the application; one which is the most recent and one which is the next
    most recent copy.  Note: if a given element has not changed, this retrieval
    will get the same copy for each one of the pair.  Since the elements are CSP
    elements, they must be retrieved directly into an MSL (temporary MSLs are
    created by APPLCMPR for this purpose).  Note: since this portion accesses
    ENDEVOR directly while you're in TSO, you CANNOT be in ENDEVOR in either of
    your split screens and execute APPLCMPR.  It WILL abend if you are in
    ENDEVOR.

 2. Export the elements from the MSL in ESF format into a set of paired PDSs to
    contain the old/new APPL/MAPG/PROC/RECD/SGRPs.

 3. Compare the paired PDSs with SUPERCE and store the compare output in the
    five sequential datasets listed previously.  Note: these datasets are stored
    on PERMANENT DASD.  It is the programmer's responsibility to discard these
    datasets when no longer needed.