Highlighted
Absent Member.
Absent Member.
661 views

Migration from Mainframe Cobol using MF Enterprise Server

Jump to solution

In case of Migration from Mainframe Cobol using MF Enterprise Server, if the user want to migrate from CICS screen to JSP for example,  does the call action from Cobol need to be change to Visual Cobol  provided by MicroFocus syntax or can remain the same syntax as in legacy Mainframe.

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Migration from Mainframe Cobol using MF Enterprise Server

Jump to solution

I'm afraid your question is not entirely clear.

Visual COBOL supports a number of COBOL dialects, including the "MF" dialect and various mainframe dialects. The dialect being used is independent of whether CICS APIs are invoked.

If you are migrating CICS applications that use BMS to communicate with TN3270 clients, and you wish to modernize those applications so they are no longer accessed through plain terminal sessions, there are various possibilities.

  1. You can use a TN3270 "screen-scraping" product to translate between TN3270 datastreams and some other form of UI, typically a web page. Some products in the Micro Focus Connect portfolio provide this sort of feature.
  2. You can write applications that use the EHLLAPI feature to automate TN3270 datastream processing, and deal with that data in whatever manner you wish. Again, see the Connect portfolio.
  3. You can change your CICS applications to use some communications method other than BMS. This might include using the COMMAREA, or web-enabling the application using CICS Web Interface. This can be relatively straightforward, particularly if the business and presentation logic are separate. If you change the application to use the COMMAREA, you can then use the Interface Mapping Toolkit to create a service interface for it, or invoke the program using EXCI (External Call Interface).

View solution in original post

0 Likes
1 Reply
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Migration from Mainframe Cobol using MF Enterprise Server

Jump to solution

I'm afraid your question is not entirely clear.

Visual COBOL supports a number of COBOL dialects, including the "MF" dialect and various mainframe dialects. The dialect being used is independent of whether CICS APIs are invoked.

If you are migrating CICS applications that use BMS to communicate with TN3270 clients, and you wish to modernize those applications so they are no longer accessed through plain terminal sessions, there are various possibilities.

  1. You can use a TN3270 "screen-scraping" product to translate between TN3270 datastreams and some other form of UI, typically a web page. Some products in the Micro Focus Connect portfolio provide this sort of feature.
  2. You can write applications that use the EHLLAPI feature to automate TN3270 datastream processing, and deal with that data in whatever manner you wish. Again, see the Connect portfolio.
  3. You can change your CICS applications to use some communications method other than BMS. This might include using the COMMAREA, or web-enabling the application using CICS Web Interface. This can be relatively straightforward, particularly if the business and presentation logic are separate. If you change the application to use the COMMAREA, you can then use the Interface Mapping Toolkit to create a service interface for it, or invoke the program using EXCI (External Call Interface).

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.