IBM Support

IV60018: PROVIDE ERRNO2 INFORMATION WHEN THREAD CREATION FAILS ON Z/OS PL ATFORMS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: Before the errno2 support code change : Failed to
create a thread: retVal -1, errno 565 (0x235)After the errno2
support code change : Failed to create a thread: retVal -1,
errno 565 (0x235), errno2 155 (0x9B)
.
Stack Trace: N/A
.

Local fix

  • 



Problem summary


    

  • Updated error message occurs when JVM fails to create a thread.

    



Problem conclusion


    

  • This APAR will be fixed in the following Java Releases:
   7 R1 SR1 FP1     (7.1.1.1)
   6    SR16 FP20   (6.0.16.20)
.
errno2 info is added to the thread creation failure message on
z/OS platforms.

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IV60018
    • 

  • Reported component name
    J9 COMMON CODE
    • 

  • Reported component ID
    620700127
    • 

  • Reported release
    270
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2014-05-01
    • 

  • Closed date
    2014-05-05
    • 

  • Last modified date
    2016-01-24
    • 





    

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

    • 

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

    • 



Fix information


    

  • Fixed component name
    J9 COMMON CODE
    • 

  • Fixed component ID
    620700127
    • 



Applicable component levels


    

  • R270  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            21 February 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback