Skip to content

Repair ERR0417 Prior Release Version Regression

If a component in your current release is also in a prior release, ERO audit requires that the meta data for the component be consistent with the following:

  • The component in the current release was checked out from that prior release.

  • No changes were made to the prior release component after checkout to the current release package.

When ERO audit finds data that indicates that these requirements are not met, it yields an ERR0417! error and RC=12.

As with other audit errors, the code in the prior release and current release components may be what you want (for example, you have changed both versions to fix a newly discovered defect), but you must take some action to make the meta data pass the tests applied by ERO area audit.

You have two options to resolve an ERR0417!

  • Check out the component again from the prior release.

  • Use the ERO release version compatibility confirmation facility to help you find, research, and resolve prior release version regression without repeating the checkout from prior release.

Check Out Component And Reapply Changes

To resolve an ERR0417 in area audit, you can check out the component again from the prior release and reapply the changes you made previously in the current release. Assuming that the code in the prior release component and the code in the current release component is what you want, you can to execute the following procedure:

  1. Save the current release component to a file outside of ZMF.

  2. In the current release package, use C3-Checkout and option 3 - Checkout from Prior Release to overlay the current release component in the package staging library.

  3. Edit the component in the current release package and overlay the checked-out code with the code you saved outside of ZMF.

  4. Verify the current release component code using the compare report as you exit the edit-in-stage session.

  5. Checkin the current release package component into the current release starting area.

  6. Checkin the component to higher release areas, overlaying the component that gave you ERR0417!

Use Prior Release Version Compatibility Confirmation Facility

The prior release version compatibility confirmation facility was introduced in ZMF 7.1.2 to help you resolve prior release version regression without making you check out the component again from prior release and reapply your changes in the current release. Using this facility, you can:

  1. Find the prior release component that makes the current release version a potential regression.

  2. Compare the prior release component to the version in your current release to see code that might require forward-fitting into the current release version.

  3. After verifying that the code in the prior release component and the code in the current release component are what you want, reset the metadata for the component to eliminate the ERR0417!

Find Prior Release Component Causing ERR0417

Execute these steps to find the prior release component that makes ERO audit flag a current release component with ERR0417:

Important

The services that power this facility are resource intensive. The most efficient way to discover multiple prior release regressions is to run ERO audit. If components that were checked out from a prior release have been checked in to higher release areas, run an area audit with Ignore Higher Areas set to Yes.

  1. The prior release version compatibility function is an option on the Release Management Checkout Options panel. Follow these steps to access the prior release version compatibility function:

    1. Type =7 on the Command or Option line of any panel in ChangeMan ZMF, then press Enter.

    2. Type release selection criteria in fields on the Release List Specifications Parameters panel, or leave the fields blank, and press Enter.

    3. The Release List panel is displayed.

       CMNRMRLF           Release List            Row 1 to 2 of 2
 Command ===>                               Scroll ===> CSR

     Release Sta Install  Work request      Dept    Aud Creator Pkgs
     FIN6410 DEV 20160328 WR 9010       FINANCE     USER015 00001
     FIN6430 DEV 20160328 WR 9030       FINANCE     USER015 00004
 ******************************* Bottom of data *******************************

      The Release List panel shows releases that:

      • Satisfy the selection criteria you typed on the Release List Parameters panel.

      • Have change packages attached to them.

    4. On the Release List panel, type line command PK on the release row to select the current release that contains the component that ERO audit flagged with ERR0417! Press Enter, and the release - Release Package List panel is displayed.

       CMNRMPLF       FIN6430 - Release Package List      Row 1 to 1 of 1
 Command ===>                                       Scroll ===> CSR
     Package    Sta Area    Install DT/TM Last Promotion    Aud Chkd In
     ACTP000032  DEV ACCTPAY 20160429 2359 SERT6   S6P1IT 20        N
 ******************************* Bottom of data *******************************

      The panel shows all packages that are attached to the release that you selected.

      The fields on the release - Release Package List panel are described in step 2 of Accessing Release Packages and Components.

    5. On the release - Release Package List panel, type C3 in the line command of the package that contains the component that ERO audit flagged with ERR0417! and press Enter. The Release Management Checkout Options panel is displayed.

       CMNRCKOP Release Management Checkout Options
 Option ===>

        Package: ACTP000032     Release: FIN6430    Area: ACCTPAY

     1 Checkout from current package release and area
     2 Checkout from current package release other areas
     3 Checkout from a prior release
     4 Checkout latest components from consolidated list
     5 Confirm prior release version compatibility

    6. On the Release Management Checkout Options panel, choose 5 - Confirm prior release version compatibility and press Enter. The Prior Release Component Query Criteria panel is displayed.

       CMNRQC90       Prior Release Component Query Criteria
 Command ===>
     Package: ACTP000032    Release: FIN6430    Area: ACCTPAY

 Component name . . . .
 Component type . . . .

 Enter "/" to select option
     / Mixed case

      This table describes the fields on the Prior Release Component Query Criteria panel.

      Field Description
      Command Type a command, or leave Command blank.
      CANCEL    Return to the previous panel without processing. (Abbreviation: C)
      Package: Displays the name of the current package.
      Release: Displays the Release ID of the current release.
      Area: Displays the name of the starting area for the package.
      Component Name Type a full component name or a pattern.
      Component Type Type the library type of the component.
      Mixed case This field is used to determine the processing of lower case input in the Component Name field.
      Omit to fold Component Name input to upper case regardless of the case that you type.
      Select to process Component Name input exactly as you type it, upper and lower case.

  2. On the Prior Release Component Query Criteria panel, type the component name and library type of the component that ERO audit flagged with ERR0417! in your current release.

    Note

    You can type a pattern in the Component Name field, but processing multiple components may consume excessive resources and elapsed time.

    Press Enter and the Prior Release Version Regression Component List panel is displayed.

    CMNCKO90    Prior Release Version Regression Component Lis  Row 1 to 1 of 1
COMMAND ===>                                                Scroll ===> CSR

Current - Package: ACTP000040 Release: S4712050 Area: ACCTPAY Libtype: JCL

Component       ---------------------- PRIOR ----------------------------
                Release    Area     Package     Changed             User
_ ACPJCL10      + S4712010 ACCTPAY  ACTP000037  2015/12/09 02:43:33 USER239
******************************* Bottom of data ********************************

    This panel displays a list of components that have version regression issues with prior releases.

    This table describes the fields on the Prior Release Version Regression Component List panel.

    Field Description
    Line Command S    Show prior release regression details.
    C   Compare the prior release component to the current release component.
    P   Process and resolve the prior release regression.
    Current Package Displays the name of the package in the current release. Release Displays the Release ID of the current release. Area Displays the name of the starting area for the package in the current release. Libtype Displays the library type of the component in the current release.
    Component Displays the component name of the prior release version regression.
    Prior Release    Displays the Release ID of the prior release.
    Area   Displays the name of the starting area for the package in the prior release.
    Package   Displays the name of the package in the prior release.
    Changed   Displays the date and time that the component was changed in the prior release.
    Userid   Displays the user ID of the person who checked in the component into the starting area of the prior release.

    On the Prior Release Component Query Criteria panel, type one of the following line commands on a listed component:

Show Prior Release Regression Details

When you use line command S on a component listed on the Prior Release Version Regression Component List panel, the Prior Release Version Regression Component Details panel is displayed.

CMNCKO91        Prior Release Version Regression Component Details
Command ===>                                            Scroll ===> CSR

    Component: ACPJCL10 +
    Libtype: JCL

            Prior                   Current
Release:    S4712010                S4712050
Area:       ACCTPAY                 ACCTPAY
Package:    ACTP000037              ACTP000037
Hash token: 216E93EE000004CE        E830C9970000047C
User:       USER239                 USER239
vv.mm:      02.03                   03.01
Changed:    2012/10/09 02:43:33     2012/10/08 16:53:51
Checked in: 2012/10/09 02:43:51     2012/10/08 16:54:32

This panel expands on the information displayed on the Prior Release Version Regression Component List panel, showing you attributes of the selected component in the current release and in the prior release. For each field type, the values for the prior release version are displayed on top of the values for the current release version.

Note

This panel is for information only. You will not use this panel to decide what action to take for a potential prior release regression.

All fields except Package and Hash token compare values for the current area component to values for the prior release component as they are right now. The prior values for the Package and Hash token fields are for the component in the prior release right now, but the current values are the values that existed when the component in the current area was last checked out.

The information in the Package and Hash token fields is what ERO audit uses to detect potential prior release version regression.

Compare Prior Release Regression Components

When you use line command C on a component listed on the Prior Release Version Regression Component List panel, the Prior Release Version Regression Comparison panel is displayed.

CMNCKO93        Prior Release Version Regression Comparison
Command ===>                                            Scroll ===> CSR
    Prior release version (SYSUT1):

    CMNTP.S4712010.ACCTPAY.ACTP.JCL(ACPJCL10)                       +

    Current release version (SYSUT2):

    CMNTP.S4712050.ACCTPAY.ACTP.JCL(ACPJCL10)                       +

This panel shows the area libraries and members in the prior release and the current release that will be compared.

Note

The comparison report on the next panel will show only the temporary ZMF datasets where the members are copied to execute the compare. You can record the library and member names on the Prior Release Version Regression Comparison panel if you want to execute a compare outside of ZMF.

Press Enter to proceed to the comparison report, or type END or press PF3 to return to the Prior Release Version Regression Component List panel without executing the compare.

ISRBROBA  CMNTP.A0191.#CA4ADF1.#6033A1B.OUTLIST     Line 00000000 Col 001 080
Command ===>                                                Scroll ===> CSR
********************************* Top of Data **********************************
        S E R C M P A R    (MVS - 862 - 20111202) 2    TEXTONLY    TUESDAY OCTOB
SYSUT1=CMNTP.A0191.#CA4ADED.#6359804.STG,SYSUT2=CMNTP.A0191.#CA4ADED.#67B6E69.ST
. . .
        //* PACKAGE GENL000005 S4.V710T19
        //* PACKAGE ACTP000004 S4.V711
        //* PACKAGE ACTP000027 S4.V71201T4
++++++++<+++.++++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7+>
D       //* PACKAGE ACTP000027 S4.V71201T4 2ND EDIT
--------|---.----1----.----2----.----3----.----4----.----5----.----6----.----7--
I       //* PACKAGE ACTP000040 S4.V71201T4
++++++++<+++.++++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7+>

        //*
        //JCLSTEP1 EXEC ACPPRC10
        //JCLSTEP2 EXEC PGM=ACPSRC50
SER71I - END OF TEXT ON FILE SYSUT1
SER72I - END OF TEXT ON FILE SYSUT2
SER75I - RECORDS PROCESSED: SYSUT1(15)/SYSUT2(15),DIFFERENCES(1)
SER80I - TIME OF DAY AT END OF JOB: 03:18:26 - CONDITION CODE ON EXIT: 4

Use the comparison report to ensure that differences between the prior release component and the current release component are intentional.

Resolve Prior Release Regression

When you use line command P on a component listed on the Prior Release Version Regression Component List panel, the Prior Release Version Regression Confirmation panel is displayed.

CMNCKO92        Prior Release Version Regression Confirmation
Command ===>                                                Scroll ===> CSR

    Component: ACPJCL10 + Libtype: JCL Release: S4712050 Area: ACCTPAY

    When this component was last checked out, the version identifying values
    for the component in the 'first found' prior release were

    Package: ACTP000037 Hash token: E830C9970000047C

    Since it was checked out the prior release version of this component has
    been updated and now has the following values

        Package: ACTP000037 Hash token: 216E93EE000004CE

    To confirm that the current area component is 'up to date' with all changes
    made to the prior release simply press enter, else hit pf3 to cancel.

    Enter will cause the first set of values to be replaced by the second.

The panel text explains what you are seeing.

If you are certain that the version the component in the current release and the version of the component in the prior release are what you want, press Enter to reset the meta data to eliminate the area audit ERR0417!

Caution

When you press Enter on the Prior Release Version Regression Confirmation panel, you are taking responsibility for any code differences between the prior version and the current version. If you are unsure about those differences, rerun the comparison report. See Compare Prior Release Regression Components.

When processing is complete, you are returned to the Prior Release Component Query Criteria panel, where the short message "Update complete" is displayed.

CMNRQC90    Prior Release Component Query Criteria          Update complete
Command ===>

    Package: ACTP000040 Release: S4712050 Area: ACCTPAY

Component name . . . . ACPJCL10
Component type . . . . JCL

Enter "/" to select option
    Mixed case

Enter the Component Name and Component Type for the next component that ERO audit flagged with ERR0417!, or press PF3 repeatedly to return to the ERO panel you want.

Note

When you adjust meta data for a component using the Prior Release Version Regression Confirmation panel, the meta data is changed in the starting area of the current release (the area that the package is attached to). You must check in the component to higher areas to propagate the adjustment.