Call failed to find program

  Explanation:  The program specified in the CALL statement is not
  part of the run-unit, and the CALL statement does not include an
  ON OVERFLOW or ON EXCEPTION phrase.

  User Action:  You must take one or more of the following actions:

      a. If you think that the program specified in the CALL
         statement may not be part of the run-unit, add an
         ON OVERFLOW or ON EXCEPTION phrase to the CALL
         statement.

         If the program named in the error message is part of
         the run-unit, check the scope of names rules.  The
         named program may not be in a scope that is visible
         to the calling program.

      b. Check to see if the DCL LINK command produced any
         undefined symbol warnings.  Executing a CALL statement
         to a program named in an undefined symbol warning
         results in the CALL_FAILED error at run time.

      c. Check to see if the object file containing the called
         program was properly linked into the run-unit.  Specify
         /MAP/FULL/CROSS with the LINK command to produce a listing
         map that shows the object files and the programs within
         the object files that are part of the run-unit.

      d. Verify the spelling of the named program.