Some remote tasks may need information to be passed to them at runtime, and may need to pass information back to the requesting client. The ExecuteSetDataIn statement allows workareas to be passed back to the requesting client after the task has finished.

When the remote client runs, it logs in using the same user id as the requesting client, so workareas are set to their default startup values, recorded from the last time that the user logged out. System workareas are given their normal values. Then the remote client reads any workareas from the RMC file, specified by ExecuteSetData and by ExecuteSetDataOut. When the task has finished, the workareas specified by ExecuteSetData and by this statement are written to the RMC file.

After the remote task has finished, the requesting client must call ExecuteFalTorPan in order to load the final values of the workareas. If the same workareas need to be transferred out and in, use the ExecuteSetData statement.

The workarea list is additive and any workareas can be listed. However these workareas are normally local ones. Temporary workareas are not transferrable, and public workareas are obviously already available. System workareas may be included, but this will not normally be necessary.

If no workarea list is supplied then all local workareas are transferred, removing any list that may currently be in place.