CFACCESS Example

This section provides you a sample of CFACCESS configuration.

For example, take the following CFACCESS configuration:

USERID=ACCTUSER,                    
NODE=NYNODE,                   
   SEND_HLQ="ACCT.SEND",          
   RECEIVE_HLQ="ACCT.RECEIVE",       
   SUBMIT_HLQ="ACCT.SUBMIT.JCL",  
   SEND_OPTION=ROOT,            
   RECEIVE_OPTION=FORCE,         
   COMMAND_OPTION=NEVER,         
   SUBMIT_OPTION=ROOT

When a file transfer request comes in from user ACCTUSER on node NYNODE, a match is found on this entry. Based on the following file transfer file names, the actual file name used is shown:

File receive is detected. The transfer file name is ACCT.RECEIVE.TAX.DATA. Because RECEIVE_OPTION=FORCE is specified, and the HLQ defined in the RECEIVE_HLQ matched the data in the file name, no changes are made to the file name. The file name used is ACCT.RECEIVE.TAX.DATA
File receive is detected. The transfer file name is TAX.DATA.Y2002. Because RECEIVE_OPTION=FORCE is specified, and the HLQ defined in the RECEIVE_HLQ does not match the data in the file name, the transfer file name is appended to the RECEIVE_HLQ file name. The file name used is ACCT.RECEIVE.TAX.DATA.Y2002.
File send is detected. The transfer file name is AUDIT.NY. Because SEND_OPTION=ROOT is specified, the transfer file name is appended to the SEND_HLQ file name. The file name used is ACCT.SEND.AUDIT.NY.
Command execution is detected. Because COMMAND_OPTION=NEVER is defined, the request is terminated with errors.
File submit is detected. The SUBMIT_HLQ parameter is ignored, because the remote user transmits the JCL to z/OS where it is written directly into the internal reader.
PPA submit is detected. The PPA data is JOB1. The PPA data becomes the member name, and the SUBMIT_HLQ is the dataset name. The file name used to submit the JCL is ACCT.SUBMIT.JCL(JOB1).