A remote process does not inherit the CHARGE task attribute value of its parent. If no CHARGE value is explicitly assigned to the remote process, it runs without a charge code. However, the remote process runs with a CHARGE value if one is explicitly assigned by a statement in the parent process. Note that usercode definitions in the USERDATAFILE can specify the range of CHARGE values that are valid for processes with a given usercode. If the CHARGEREQ attribute is set in the usercode definition at the remote host, then the remote task must have one of the CHARGE values defined by the CHARGECODE usercode attribute at the remote host.

The ACCESSCODE task attribute also is not inherited by remote processes, but it can be assigned. However, if it is assigned, it must be assigned a value that is allowed for the remote process usercode on the remote host.