Issues with
Application Workflow Manager
The following topic lists issues with the
Application Workflow Manager functionality.
- If you receive exceptions after loading a new model:
- Use
Validate within the Model Editor to verify your model.
- Clear the cache from the application context menu.
- Clear the cache in the Navigator View.
- If your ISPF Dialog Applications do not work:
- Clear the Dialog process list from the application context menu.
- Disconnect, then connect to the Mainframe and restart Eclipse.
- If you receive an error when opening the Model Editor, this might be caused by a codepage problem - the model might have been saved with a codepage different from the one it was opened with.
- In an
Application Workflow Manager modelled action, you retrieve a file from the remote zOS system directly into a COBOL project, you must set the text file encoding of the COBOL project to UTF-8 in the project properties in order for the Compiler to correctly process the source code. To set the encoding, in the project properties of the COBOL project and on the
Micro Focus > Project Settings > COBOL, specify the
source-encoding(utf8) Compiler directive in the
Additional directives field.
- If you are using the
Application Workflow Manager with IBM's RDz and with Remote Server Explorer, the ISPF Dialog Support facility does not work.
- When using the
Application Workflow Manager with IBM's RDz and with z/Server as the server, remote copybook resolution is not supported in the editor.
- Global Workbench Actions do not work in Eclipse 4.n. This is caused by a known issue with the Eclipse IDE (search the Web site of the Eclipse Foundation for Bug 411765).
