CPF Flow for ACF2

Products

• ACF2
• ACF2 - MISC
• ACF2 - z/OS
• COMMON SERVICES FOR Z/OS

Issue/Introduction

This article describes the flow of information between ACF2 and Common Services component CAICCI for Command Propagation Facility (CPF).

Environment

ACF2 R16

Common Services R15

Resolution

1. User issues command to be executed on one or more nodes. Command is sent to CA-ACF2 address space.
   
   
2. If command is executed on HOME node, it is executed prior to sending command to remote nodes.
   
   
3. CA-ACF2 encrypts command buffer and sends it to CAICCI.
   
   
4. CAICCI writes buffer to CAICCI LOGGER database. CAICCI gets command even if VTAM connections are not established.
   
   
5. CA-ACF2 is notified that CAICCI has written buffer to LOGGER database. If asynchronous request, go to step 21. Other steps still execute, but user is freed up to issue another command. If synchronous request, go to step 6 and wait until command executes on remote node(s).
   
   
6. Journal the request to appropriate CPF journal file(s)
   
   
7. CAICCI sends command to requested nodes. If a remote node is not active, command sits on LOGGER database until node becomes active or request times out.
   
   
8. Remote CAICCI receives request and writes it to its LOGGER database.
   
   
9. Remote CAICCI communicates with originating CAICCI to indicate that request has been received and that originating CAICCI can remove request from its LOGGER database.
   
   
10. CAICCI passes request to CA-ACF2.
    
    
11. CA-ACF2 journals request to appropriate CPF journal file.
    
    
12. CA-ACF2 executes command and formats a response.
    
    
13. CA-ACF2 passes response to CAICCI to return it to originating node.
    
    
14. CA-ACF2 journals response to appropriate CPF journal file.
    
    
15. CAICCI writes response to its LOGGER database.
    
    
16. CAICCI returns response to originating node.
    
    
17. Originating CAICCI writes response to its LOGGER database.
    
    
18. CAICCI communicates with remote node CAICCI to indicate response has been received and that remote CAICCI can remove response from its LOGGER database.
    
    
19. Response is returned to CA-ACF2.
    
    
20. CA-ACF2 journals response to appropriate file.
    
    
21. If request was asynchronous, message indicating that request was queued to CPF is returned to user. If request was synchronous, response is returned to user.