search cancel

Why ACF2 ROLE change results in ACF67048 WARNING ROLETYPE Change

book

Article ID: 242595

calendar_today

Updated On:

Products

ACF2 - z/OS ACF2 ACF2 - MISC

Issue/Introduction

ACF2 issues the following message via line command change for a XROL that includes either GROUP or ROLE:

t x(rol)

change a rep group include(b)                                                         
 ACF67048 WARNING - THE XROL ROLETYPE MAY CHANGE. ENTER Y TO CONTINUE OR N TO CANCEL
                                                                                    
--or--

change a rep role include(b)                                                        
 ACF67048 WARNING - THE XROL ROLETYPE MAY CHANGE. ENTER Y TO CONTINUE OR N TO CANCEL

 

Doing the same change command without ROLE and GROUP change is good:


change a rep include(b)         
 ACF6D071 1  RECORD(S) CHANGED                          

 

When running the same commands in ACFBATCH no message is put out:


00040000 T X(ROL) MSYSID(-)            
00050001 CHANGE A REP GROUP INCLUDE(B) 
ACF6D071 1  RECORD(S) CHANGED          


1)  Why is there a difference between issuing the command via ACF line command
 and ACFBATCH?   

2)  Is there a way to suppress the ACF67048 WARNING?

Environment

Release : 16.0

Component : ACF2 for z/OS

Resolution

Anytime ROLE or GROUP is specified on an X(ROL) CHANGE command within TSO ACF, the ACF67048 message will be issued. This is a warning message to alert that when a ROLETYPE is changed, the usage of the record changes. This was an enhancement made in ACF2 R15. To avoid receiving this message when issuing a CHANGE command in TSO ACF, the ROLETYPE (ROLE or GROUP) should not be specified. It only needs to be specified when truly attempting to change a ROLE record to a GROUP record or vice versa.

ACFBATCH suppresses the ACF67048 message and other various types of warning prompt messages such as ACF67046 when a DEL LIKE(-) is issued. If this wasn't the case, then there wouldn't be a way of responding to the prompt and the command would fail. It is a limitation of running a command in batch as opposed to a TSO command.