IBM Support

II11661: MSGIEC614I RC08 04060020 PERFORMING A DELETE COMMAND OR MSGIEC614I RC08 0406001E PERFORMING A RENAME COMMAND

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

  • Customer tried to delete a data set but was unable to.
Rec'd MSGIEC614I RC08 04060020 performing a DELETE command or
MSGIEC614I RC08 0406001E performing a RENAME command.  They
ran a DIAGNOSE against the VVDS of the volume where the data
set was allocated. He got an RC=42 from the run of DIAGNOSE,
and in the dump record of the VVDS, data set showed being
cataloged to 'CAT1'.
Doing a LISTCAT for same data set, catalog showed it to be
cataloged to a different catalog ('CAT2').
On CAT1, the dataset was defined as SMS managed, but in CAT2
it was defined as NON-SMS managed.

To clear the inconsistency, issue a DELETE of the file against
CAT1 -with sms info-.
For example, from ISPF opt 3.4: DEL (/) catalog(CAT1).
File is deleted , VTOC record erased and VVDS record also.

The catalog entry in CAT2 -w/o SMS info- remains, but an
UNCATALOG could be done w/o any problem.

Local fix

  • 



Problem summary


    

  • 



Problem conclusion


    

  • 



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    II11661
    • 

  • 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
    1999-01-27
    • 

  • Closed date
    • 

  • Last modified date
    1999-01-27
    • 





    

  • 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:
            

            27 January 1999
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback