The following topic lists issues with the remote mainframe development functionality.
- Port not saved after restarting Eclipse
- Sometimes, after the first connection definition, the port you use to connect to the Mainframe is not saved. To work around this issue:
- After you have defined your mainframe connection, explicitly connect and disconnect from the Mainframe.
- After the first restart of Eclipse, ensure that the port is correct.
- The tree view in MVS Explorer does not open
- You receive an internalGetChildren error when you try to open the tree view in MVS Explorer. To resolve this problem:
- Verify your filter definition, disconnect and then connect to the Mainframe.
- If this does not solve the problem, restart Eclipse.
- Exceptions after loading a new model
- To work around this problem:
- 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.
- ISPF Dialog Applications do not work
- To resolve this problem:
- Clear the Dialog process list from the application context menu.
- Disconnect, then connect to the Mainframe and restart Eclipse.
- 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.
Application Workflow Manager
- 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.
- The global editor actions do not work for releases of Eclipse 4.n before Eclipse 4.2.2.
- 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).