IBM Support

SE70858 - RDARS-INCORROUT HANDLE BLANK EXIT NAME IN QRLMMONQ DATA AREA

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

RDARS-INCORROUT HANDLE BLANK EXIT NAME IN QRLMMONQ DATA AREA

Error Description

When a directory monitor is started by using the Start Monitor  
(STRMONOND) command, and the QRLMMONEXT data area exists and    
contains a blank value in the universal directory monitor exit  
name field and a non-blank value in the universal output queue  
monitor exit name field, the monitor will incorrectly try to    
call the universal directory monitor exit.  The call fails with
message CPF0001 because the program name is blank.              
                                                               
The same problem exists for output queue monitors when the      
QRLMMONEXT data area exists and contains a blank value in the  
universal output queue monitor exit name field and a non-blank  
value in the universal directory monitor exit name field.      

Problem Summary

When a directory monitor is started by using the Start Monitor  
(STRMONOND) command, and the QRLMMONEXT data area exists and    
contains a blank value in the universal directory monitor exit  
name field and a non-blank value in the universal output queue  
monitor exit name field, the monitor will incorrectly try to    
call the universal directory monitor exit.  The call fails with
message CPF0001 because the program name is blank.              
                                                               
The same problem exists for output queue monitors when the      
QRLMMONEXT data area exists and contains a blank value in the  
universal output queue monitor exit name field and a non-blank  
value in the universal directory monitor exit name field.      

Problem Conclusion

The STRMONOND command has been corrected.  If the QRLMMONEXT    
data area exists and contains a blank value in the universal    
monitor exit name field that corresponds to the requested      
monitor type, no attempt is made to call a universal monitor    
exit, and attribute-specific monitor exit rules are followed.  
The QRLMMONEXT data area can be placed in the instance library  
or the QUSRRDARS library.  If it exists in both the instance    
library and QUSRRDARS, the data area in the instance library is
used.                                                          
                                                               
The Output queue (OUTQ), Error output queue (ERROUTQ), Processed
output queue (PRCOUTQ), and Directory (DIR) parameter values of
the STRMONOND command are now validated before the monitor is  
started.  For output queue monitors, the specified output queues
must exist and different values must be used for each of the    
OUTQ, ERROUTQ and PRCOUTQ parameter values.  For directory      
monitors, the specified directory must exist, and the user must
have read, write and execute (*RWX) data authorities for that  
directory.                                                      
                                                               
A new keyword, Message logging (LOG), has been added to the    
STRMONOND command.  The help for this keyword will be added in a
future release, and will read as follows:                      
                                                               
               Message logging (LOG) - Help                    
                                                               
Specifies whether the monitor job sends detailed messages      
to the job log.  This can be helpful when implementing a        
new monitor to ensure that reports are loaded into the          
expected application groups and applications according to      
the specified parameters and monitor user exit programs.        
                                                               
*NO                                                            
    Do not send detailed messages to the job log.              
*YES                                                            
    Send detailed messages to the job log.                      

Temporary Fix

Comments

Circumvention


PTFs Available

R720 SI69452 PTF Cover Letter   9297
R730 SI69451 PTF Cover Letter   9311
R740 SI69450 PTF Cover Letter   9151

Affected Modules

         
         

Affected Publications

Summary Information

Status............................................ CLOSED PER
HIPER........................................... No
Component.................................. 5770RD100
Failing Module.......................... RCHMGR
Reported Release................... R740
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 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15Q","label":"APARs - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R2M0;V7R3M0;V7R4M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16E","label":"APARs - IBM i 7.2 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R2M0;V7R3M0;V7R4M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16G","label":"APARs - IBM i 7.3 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R2M0;V7R3M0;V7R4M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SS9QQS","label":"IBM i 7.4"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R2M0;V7R3M0;V7R4M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 November 2019