I am trying to compile an APPCLU profile record, but the record is too large. How do I implement NEXTKEY records. The compiler does not accept $PREFIX in the NEXTKEY record.
search cancel

I am trying to compile an APPCLU profile record, but the record is too large. How do I implement NEXTKEY records. The compiler does not accept $PREFIX in the NEXTKEY record.

book

Article ID: 12364

calendar_today

Updated On:

Products

ACF2 ACF2 - DB2 Option ACF2 for zVM ACF2 - z/OS ACF2 - MISC PanApt PanAudit

Issue/Introduction



How can I implement nextkey processing in a large APPCLU profile record?

Environment

Release:
Component: ACF2MS

Resolution

To implement NEXTKEY processing you simply add a rule line in the profile record that references the NEXTKEY profile record.

For Example 

$KEY(NODEx)
LU0.- SESSION(xxxxxLU0)
LU1.- SESSION(xxxxxLU1)
LU2.- SESSION(xxxxxLU2)
LU3.- SESSION(xxxxxLU3)
LU4.- SESSION(xxxxxLU4)
 -.-   NEXTKEY(NODExext)  

$KEY(NODExext)
LU5.- SESSION(xxxxxLU5)  
LU6.- SESSION(xxxxxLU6)  
LU7.- SESSION(xxxxxLU7)  
LU8.- SESSION(xxxxxLU8)  
LU9.- SESSION(xxxxxLU9)   

The continuation of the node list for NODEx is in  NODExext 
there is no need to include a $PREFIX statement in NODExext.