IBM Support

II11062: MULTIPLE ABEND806 AFTER TCP/IP STARTUP IF MVPTTRML IS NOT IN LPA

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • TCP/IP has a number of modules that are required to reside in
LPA.  When TCP/IP is started with these modules NOT residing in
LPA, an abend806 occurs as expected.  However, this does not
happen until AFTER the TCP/IP resource manager MVPTTRML has
been defined to MVS.  If MVPTTRML is one of the modules that
was not included in LPA, this results in multiple abend806 on
every task or address space termination in the system,
eventually necessitating an IPL.
-
See also II05646.
-
In the reported scenario, the TCP/IP LPA modules were in a
separate dataset that was inadvertently left out of the LPALST
concatenation.
Logrec records showed abend806 in IEAVTR2D and IEAVTRSR.

Local fix

  • Customers should insure that all required LPA-resident TCP/IP
modules are present in the LPA before attempting to start
TCP/IP.

Problem summary

  • 



Problem conclusion


    

  • 



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    II11062
    • 

  • Reported component name
    V2 LIB INFO ITE
    • 

  • Reported component ID
    INFOV2LIB
    • 

  • Reported release
    001
    • 

  • Status
    INTRAN  
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    1998-02-18
    • 

  • Closed date
    • 

  • Last modified date
    1998-02-23
    • 





    

  • 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            23 February 1998
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback