We are currently a Micro Focus 6.0 Sp2 SEE user. We use it for development and prod. We have a new Cobol application that the vendor requires Visual Cobol 2.3 Update 1. We are being asked to put it on the same server as the current development and production versions. How can this be accomplished? What are the ramifications of different levels of support being required by the OS other products and the possibility that there may be issues with backward compatibility with our current release.
We are currently a Micro Focus 6.0 Sp2 SEE user. We use it for development and prod. We have a new Cobol application that the vendor requires Visual Cobol 2.3 Update 1. We are being asked to put it on the same server as the current development and production versions. How can this be accomplished? What are the ramifications of different levels of support being required by the OS other products and the possibility that there may be issues with backward compatibility with our current release.
What is the OS that you are currently using, Windows or Linux/Unix?
The Product Availability Matrix can be found here.
For the most part the Visual COBOL/COBOL Server products can be installed side-by-side with earlier MF COBOL products residing on the same machine. You just need to be careful about setting environment variables like PATH and COBDIR so they point to the right product.
The SEE 6.0 product supports mainframe technologies such as CICS and the Visual COBOL product does not. If you are looking for mainframe compatibility then you should be looking at Enterprise Developer instead of Visual COBOL.
BTW, VC 2.3 Update 1 is a couple of releases old. The latest product offering is VC 3.0.
Thanks.
We are currently a Micro Focus 6.0 Sp2 SEE user. We use it for development and prod. We have a new Cobol application that the vendor requires Visual Cobol 2.3 Update 1. We are being asked to put it on the same server as the current development and production versions. How can this be accomplished? What are the ramifications of different levels of support being required by the OS other products and the possibility that there may be issues with backward compatibility with our current release.
We are currently a Micro Focus 6.0 Sp2 SEE user. We use it for development and prod. We have a new Cobol application that the vendor requires Visual Cobol 2.3 Update 1. We are being asked to put it on the same server as the current development and production versions. How can this be accomplished? What are the ramifications of different levels of support being required by the OS other products and the possibility that there may be issues with backward compatibility with our current release.
The product Release Notes document provides information on installing into a separate directory. As an example, I've attached a copy of the Release Notes document for Visual COBOL Development Hub 2.3 Update 1. Please see the section titled "Micro Focus Visual COBOL Development Hub Installation Options". You will need to set the environment variables COBDIR, PATH, and LD_LIBRARY_PATH differently to point to the product you currently wish to use.
mfvisualcobol_2D00_developmenthub_2D00_23u1_2D00_release_2D00_notes.pdf
We are currently a Micro Focus 6.0 Sp2 SEE user. We use it for development and prod. We have a new Cobol application that the vendor requires Visual Cobol 2.3 Update 1. We are being asked to put it on the same server as the current development and production versions. How can this be accomplished? What are the ramifications of different levels of support being required by the OS other products and the possibility that there may be issues with backward compatibility with our current release.
We are currently a Micro Focus 6.0 Sp2 SEE user. We use it for development and prod. We have a new Cobol application that the vendor requires Visual Cobol 2.3 Update 1. We are being asked to put it on the same server as the current development and production versions. How can this be accomplished? What are the ramifications of different levels of support being required by the OS other products and the possibility that there may be issues with backward compatibility with our current release.
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.