IBM Support

SE74795 - OSP-OTHER-F/IOOBJECTASP-T/QYASPPG1-MSGMCH5203 MSGMCH5203 DURING
VARY ON OF AN IASP USING A NON-MATCHING *DEVD AND RESOURCE NAMES

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 (Authorized Program Analysis Report)

Abstract

OSP-OTHER-F/IOOBJECTASP-T/QYASPPG1-MSGMCH5203 MSGMCH5203 DURING
VARY ON OF AN IASP USING A NON-MATCHING *DEVD AND RESOURCE NAMES

Error Description

A user may originally create an IASP with a particular device  
description name. They may later decide that the device        
description name does not make sense and would like to use a    
different name instead, so a second device description is      
created but points to the original resource name.              
Example:                                                        
Device description MYIASP is originally created and points to  
resource MYIASP.                                                
Later the user wants the device description to be called        
IASP01, however there is no way to rename an IASP resource, so  
the user creates device description IASP01 and points it to    
resource MYIASP. Then attempts to vary on IASP01, it will fail  
with MSGMCH5203 if both device descriptions exist.              
                                                               
Code will be modified to allow more than one IASP device        
description to exist while pointing to a single IASP resource.  
                                                               
Work around:                                                    
Vary off the original device description (MYIASP), make sure    
that no other device descriptions point to MYIASP resource,    
then rename the MYIASP *DEVD to a new name (IASP01) and vary on
IASP01.                                                        

Problem Summary

A user may originally create an IASP with a particular device  
description name. They may later decide that the device        
description name does not make sense and would like to use a    
different name instead, so a second device description is      
created but points to the original resource name.              
Example:                                                        
Device description MYIASP is originally created and points to  
resource MYIASP.                                                
Later the user wants the device description to be called IASP01,
however there is no way to rename an IASP resource, so the user
creates device description IASP01 and points it to resource    
MYIASP. Then attempts to vary on IASP01, it will fail with      
MSGMCH5203 if both device descriptions exist.                  
                                                               
Code will be modified to allow more than one IASP device        
description to exist while pointing to a single IASP resource.  
                                                               
Work around:                                                    
Vary off the original device description (MYIASP), make sure    
that no other device descriptions point to MYIASP resource, then
rename the MYIASP *DEVD to a new name (IASP01) and vary on      
IASP01.                                                        

Problem Conclusion

Operating system code has been modified to allow an IASP        
resource to be varied on by one or more device descriptions,    
though the IASP can only be varied on by one device description
at a time.                                                      

Temporary Fix

Comments

Circumvention


PTFs Available

R720 SI78581  1000

R730 SI79856  1000

R740 SI76213  1238

Affected Modules


         
         

Affected Publications

Summary Information

Status............................  CLOSED PER
HIPER.............................  No
Component.........................  5770SS100
Failing Module....................  RCHMGR
Reported Release..................  R720
Duplicate Of......................  




IBM i Support

IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0; 7.3.0; 7.4.0","Product":{"code":"SWG60","label":"IBM i"},"Component":"5770SS1","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
20 May 2022