Problem:

A sample WFL (WorkFlow Process) file contains the statement

    RUN SASB2000/SFA/P/B/34 on SASB [FB34]

When analyzed, this statement is actually trying to run the program FB34 under a defined entry point - SASB2000/SFA/P/B/34. 

When the WFL (WorkFlow Process) file is verified, the relationship “Runs Program Entry Point” is unresolved to SASB2000.SFA.P.B.34.

How can this be resolved?

Resolution:

This is caused because there is no automatic resolution to the entry point in the current version of the product.

There are 2 ways to work around this unresolved "Program Entry Point".

1.  Before verifying the .WFL (WorkFlow Process) file,

-    Amend the WFL (WorkFlow Process) file statement

          RUN SASB2000/SFA/P/B/34 on SASB [FB34]

      to

         RUN FB34 on SASB [FB34]

-     Re-verify the WFL (WorkFlow Process) file to produce the correct relationship “Runs Program Entry Point” and resolve it to the program FB34

2.  Before verifying the COBOL file (FB34.cbl), set the workspace option as follows..

-    Open Workspace Options >  Verification tab > Settings tab > Cobol

-    Check the “Create Alternative Entry Point” option ON

-    Add the Conversion Pattern    =(FB34*)=\\SASB2000.SFA.P.B.34

    ( NOTE : the run statement has \\ the entry point will resolve to . )

-    Re-verify the Cobol file FB34.cbl and the .WFL (WorkFlow Process) file

 NOTE : If this option is chosen, the Conversion Pattern MUST be changed before every program effected is verified.

Incident # 2610452