When a process initiates an external task, the NAME task attribute of the task specifies the title of the object code file to be initiated. The USERCODE and FAMILY attributes of the task have no effect on the search for the object code file; instead, the USERCODE and the FAMILY of the initiating process affect the search for the object code file. For example, consider the following WFL job:

BEGIN JOB;
  USERCODE = DADA/DALI;
  FAMILY DISK = MYPACK OTHERWISE YOURPACK;

  RUN OBJECT/EPSILON;
      USERCODE = RENE/MAX;
      FAMILY DISK = AMAST OTHERWISE BMAST;
END JOB

In this job, the phrase RUN OBJECT/EPSILON implicitly assigns “OBJECT/EPSILON” to the NAME attribute of the task. When executing this RUN statement, the system uses the USERCODE and FAMILY of the job, not those of the task. Therefore, the system searches for OBJECT/EPSILON in the following locations, in the order listed:

(DADA)OBJECT/EPSILON ON MYPACK;
*OBJECT/EPSILON ON MYPACK;
(DADA)OBJECT/EPSILON ON YOURPACK;
*OBJECT/EPSILON ON YOURPACK;

However, once OBJECT/EPSILON is initiated, it runs under usercode RENE. When OBJECT/EPSILON attempts to access files, the system applies the value FAMILY DISK = AMAST OTHERWISE BMAST to the file search.