IBM Support

II03405: MSGHMA3190 MSGHMA3821 APPLY OF CICS MAINTENANCE CAUSES POTENTIAL REGRESSION DUE TO MISSING PRE-REQ/SUP INFO ( UPDATED II00028 )

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • APPLICATION OF CICS MAINTENANCE (BOTH PTF'S AMD APAR'S)
    CAN RECEIVE SMP4 MESSAGES:
     HMA3190 : SYSMOD DOES NOT PRE OR SUP UMID  XXXXX
     HMA3821 : ID CHECK PROCESSING SYSMOD
    SMP4 ENDS WITH RETURN CODE OF FOUR (4).
     APPLICABLE TO RELEASES 1.4.0, 1.4.1, 1.5.0, R140 R141 R150
                            1.6.0, 1.6.1, 1.7.0, R601 R602 R612
                            R613 R702 R703 RF12 RF13 RG02 RG03
    
     5740XX100 5744SC130 5740 XX 100 5744 XX 130 SMP
     MSGHMA319 MSGHMA382 AR140 AR141 AR150 HMA319 HMA382
     SMP/E MSGGIM3190 MSGGIM3821 GIM3190 GIM3821
     MSGGIM38201W MSGGIM31902I
    

Local fix

Problem summary

  • * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
     THIS ENTRY DESCRIBES THE REASONS WHY SMP4 MSGS HMA3190 AND
      HMA3821 MAY BE PRODUCED DURING CICS/OS/VS MAINTENANCE.
    CICS/OS/VS MAINTENANCE, BOTH CORRECTIVE (APAR) AND PREVENTIVE
    (PTF) WAS REPACKAGED TO TAKE ADVANTAGE OF THE SOURCE MAINTENANCE
     ENHANCEMENTS WITHIN SMP4.  BOTH APARS AND PTFS ARE NOW SUPPLIED
     IN UPDATE (++MACUPD) FORMAT. THE ONLY DIFFERENCE BETWEEN A PTF
     AND THE APARS IT FIXES BEING THE PROVISION OS A PRE-ASSEMBLED
     TEXT DECK WITHIN THE PTF.
    SMP4 ALLOWS MULTIPLE UPDATES TO THE SAME SOURCE CODE ELEMENT TO
    EXIST SIMULTANEOUSLY AND TRACKS THESE UPDATES VIA THE UPDATE
    MODIFICATION IDENTIFIER (UMID) STRING WITHIN THE SMP CDS DATASET
     CICS/OS/VS APAR FIXES ARE TRADITIONALLY INDEPENDENT ENTITIES
    PRODUCED WITHOUT UNNECESSARY PRE-REQUISITE REQUIREMENTS. THIS
    GIVES THE ABILITY TO SELECTIVELY INSTALL A SINGLE APAR FIX WHEN
    REQUIRED.
     THE PROBLEM OCCURS WHEN AN APAR OR PTF IS APPLIED ON A SOURCE
    ELEMENT WHICH HAS ALREADY BEEN UPDATED BY MAINTENANCE (APARS,
    PTFS OR BOTH).  SMP4 SUCCESSFULLY INSTALLS THIS FIX WITHOUT THE
    NEED OF "FORCE" (SMP3 ONLY) OR BYPASS(ID).
     IT DOCUMENTS MODIFICATIONS TO THE SAME ELEMENT VIA TWO MESSAGES
         HMA3821  ID CHECK PROCESSING SYSMOD XXXXX  MACUPD  EDFHXYZ
         HMA3190  SYSMOD XXXXX DOES NOT PRE OR SUP SMPCDS ELEMENT
         UMID YYYYY
          WHERE XXXXX IS THE FIX BEING INSTALLED
                YYYYY IS THE PREVIOUS MAINTENANCE
    HMA3190 IS REPEATED FOR EVERY ITEM OF PREVIOUS MAINTENANCE YYYYY
     THE SMP APPLY STEP SUCCESSFULLY ENDS WITH A RETURN CODE OF 4.
     THE ABOVE MESSAGES ARE FACTUAL AND ESSENTIALLY INFORMATIONAL.
     THEY DETAIL THE FACT THE FIX BEING INSTALLED HAS NO SPECIFIED
     RELATIONSHIP WITH THE PREVIOUS MAINTENANCE.
     THIS IS CORRECT AND IS THE WAY SERVICE IS DESIGNED...
    HOWEVER, SMP MUST REPORT THE ABOVE IN THE APPLY TIME
    REGRESSION REPORT. THIS IS ACCEPTABLE BECAUSE SMP CANNOT
    DETERMINE WHETHER THE FIXES PHYSICALLY OVERLAP OR HAVE
    LOGICAL INTERRELATIONSHIPS.
    IT MUST BE STRESSED THAT THE ABOVE MESSAGES ARE PRODUCED
    WHENEVER MAINTENANCE IS APPLIED ON A PREVIOUSLY HIT
    ELEMENT. IT IS NOT SIMPLY A QUESTION OF MISSING PTF PRE-
    REQS ON APAR FIXES.
    THERE ARE SOME GUIDELINES TO FOLLOW WHEN DETERMINING
    WHETHER A REGRESSION SITUATION EXISTS AFTER RECEIVING
    THE ABOVE SMP MESSAGES DURING MAINTENANCE APPLICATION.
    REGRESSION IS DEFINED HERE AS THE PHYSICAL REMOVAL OF THE
    EFFECT OF A FIX BY ANOTHER.
    1. WHEN APPLYING AN APAR..
       THE SMP MESSAGES COULD OCCUR DUE TO THE PREVIOUS APAR(S)
       AND/OR PTF(S) BEING INSTALLED ON THE ELEMENT BEING
       UPDATED.  IN THIS SITUATION NO PROBLEM EXISTS. IF
       THERE IS A CODE OVERLAP OR OTHER DEPENDENCY BETWEEN
       APARS (A PTF IS JUST A COLLECTION OF APARS), THEN THAT
       DEPENDENCY IS DEFINED BY THE CHANGE TEAM PROGRAMMER USING
       SMP PRE-REQ STATEMENTS.  FAILURE TO CORRECTLY DO THIS
       MEANS THE APAR IS IN ERROR AND SHOULD BE REPORTED IN THE
       NORMAL WAY.  BECAUSE OF THE WAY SMP PROCESSES CICS
       UPDATE-TYPE SERVICE USING THE SMP MTS DATASET, THE PRE-
       VIOUS FIXES TO AN ELEMENT ARE NOT LOST.  THE USER NEED
       TAKE NO FURTHER ACTION - HIS APAR IS CORRECTLY INSTALLED.
    2. WHEN APPLYING A PTF..
       THE SMP MESSAGES COULD OCCUR DUE TO THE PREVIOUS APAR(S)
       BEING INSTALLED ON THE ELEMENT BEING UPDATED.  PTFS SHOULD
       PRE-REQ THEIR PREDECESSORS SO NO PTF TO PTF PROBLEM SHOULD
       OCCUR.  IN THIS SITUATION REGRESSION MIGHT EXIST BECAUSE
       IF THE PTF DOES NOT SUPERCEDE THE APAR(S) ALREADY INSTALLED,
       THEN THESE APARS ARE BY DEFINITION AT A HIGHER LEVEL THAN
       THE PTF.  THE PTF COULD THEREFORE PHYSICALLY REMOVE SOME
       APAR CODE.  THIS IS A REGRESSION SITUATION COMMON TO ALL
       PRODUCTS WHERE PREVENTIVE SERVICE APPLICATION REMOVES HIGHER
       LEVEL CORRECTIVE SERVICE.  THIS PROBLEM SHOULD BE LEGITI-
       MATELY REPORTED THROUGH THE IBM SUPPORT STRUCTURE FOR
       RESOLUTION.  IF LINES OF CODE HAVE BEEN REMOVED OR
       INVALIDATED, THEN THE CORRECTIVE FIX SO REMOVED CAN BE
       SIMPLY REINSTALLED ON TOP OF THE PTF. THE USER SHOULD STILL
       HAVE THIS FIX STORED ON HIS SMP PTS DATASET.  OCCASIONS
       REQUIRING USER ACTION AS DETAILED ABOVE SHOULD BE
       MINIMAL.
    NOTE THAT SMP4 WILL ALWAYS DO AN ASSEMBLY IF MESSAGES HMA319,
    HMA382 ARE ISSUED.  THEREFORE, THERE IS NO EXPOSURE DUE TO SMP
    TOTALLY REPLACING A USER'S MODULE BY TAKING THE PRE-ASSEMBLED
    OBJECT DECK FROM THE PTF.
    

Problem conclusion

Temporary fix

Comments

  • THIS PROBLEM IS CAUSED BY THE FACT THAT CICS MAINTENANCE
    CONSISTS OF INDEPENDENT UPDATSES TO THE SOURCE CODE.
     PRE-REQ RELATIONSHIPS ARE NOT SPECIFIED EXCEPT IN THE CASE OF
    TRUE LOGICAL CODE DEPENDANCIES.
    

APAR Information

  • APAR number

    II03405

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1988-06-02

  • Closed date

    1988-06-02

  • Last modified date

    1992-02-11

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
13 December 2020