Rocket® Visual COBOL®

Good morning, I am again with this old problem, I need to convert this program done in Net EXpress to Visual Cobol, noting que the program works Correctly in NetExpress but in Visual Cobol can not load the DLL. The dll this installed in windows \\ system32 folder. Thank you.

I have a Base64 string how do I convert to text. PENGZT48aW5mQ0ZlIElkPSJDRmUzNTE1MTEwODcyMzIxODAwMDE4NjU5OTAwMDA0ODEwMDAwMDQwNDEzNzc1NSIgdmVyc2FvPSIwLjA2IiB2ZXJzYW9EYWRvc0VudD0iMC4wNiIgdmVyc2FvU0I9IjAxMDAwMCI PGlkZT48Y1VGPjM1PC9jVUY PGNORj40MTM3NzU8L2NORj48bW9kPjU5PC9tb2Q PG5zZXJpZVNBVD45MDAwMDQ4MTA8L25zZXJpZVNBVD48bkNGZT4wMDAwNDA8L25DRmU PGRFbWk MjAxNTExMTI8L2RFbWk PGhFbWk MTYyNTU1PC9oRW1pPjxjRFY NTwvY0RWPjx0cEFtYj4yPC90cEFtYj48Q05QSj4xNjcxNjExNDAwMDE3MjwvQ05QSj48c2lnbkFDPlNHUi1TQVQgU0lTVEVNQSBERSBHRVNUQU8gRSBSRVRBR1VBUkRBIERPIFNBVDwvc2lnbkFDPjxhc3NpbmF0dXJhUVJDT0RFPnBocUY1SHNQQnpTM2I5TEN2amhocTU4SXI0K2pMN0V6NFlPeGVlVVBCTG9RK0ttU29jblZsQ1lYQ0poQVFzWmJRZnE2VFB1U3NlSkRxYVdhOWJrMUV4TURsT1h6OWhLd3RHWWpsWEkwSWpSbmVNaEhUb2Y0dFVVcW4xbkNwd3ZYcndJOTZoRTJyc1hwZVRzOWd6cUZlRURIbVIwZ2kyQXJCZ3dCZ1RmbHdicDdhQS82cXlOVlkwczlvRGVRQ3hJVlNnQ0F4NXNhYXViWlhxMzhacU55OVdwSXM1Zjh5UjQ1Y1pwdVhST1JOaVhRNWdRb3RUMU5Yb1dtamN0NTkrMTJmWU1GZVRrMnUxNGN6R3g3cGhIVTdESnBDRmtmUXh6SVZuOHJxN1MxdFBwd0ZXaytQeGkvZEovMTFxeThpaHE

I tried to connect to MySQL in Visual Cobol 2.2, but I can't do it. my project -> property -> SQL -> OpenESQL -> <ADD> -> Select <DBMAN> ->  After that, I can't select ODBC, so I can't use ODBC. In addition, when I use "Tools menu -> Micro Focus COBOL -> ADO.NET Connection Editor", I get error message "This provider does not support generic ADO configuration method". I have already installed ADO.NET driver and ODBC driver for MySQL. I really want to study COBOL again. #MySQL#connection

Error 179 - MFRUN.gnt cant be found on COBOL Server for Windows I have looked at previous post on this subject which seemed to be cleared by simply restarting server community.microfocus.com/.../9268.aspx. We have compiled a simple program to gnt through Visual COBOL 2012 and I can run successfully from CMD prompt by - RUN PROG1 The gnt is then transferred to a Production Server but whenever we try to run as above we get - Error 179 - MFRUN.gnt cant be found. Also tried RUNW etc. On the Prod server we don't seem to have CREATEENV.bat as on Dev Server. We created one of those to set up the environment. I don't believe it is ever getting to our application program. However, we have some other programs called from C which appear to get called successfully - so the cobol run time appears to be working ok. #Error179

Hi, I am new to visual cobol and 3 yrs exp to Visual Studio. We have requirement where we need to design a win forms using VS and write a cobol program which will call these win forms. We will set some values in copy book from the cobol program and pass that copy book to win forms for displaying data to user. The Cobol Program is the entry point which will invoke win forms based on certain condition. The cobol program should be of native project type and win forms should be of manged type. I did some googling and was able to call win forms but when I add copy books as parameter to a method I am not able to make a call. I am getting error  saying "The parameter name is incorrect". I have added a sample project file of my work.#COBOLVISUALCOBOLMIGRATION#FormVisualCobol#MicroFocusVisualCobol#MicroFocus

I'm having trouble opening an RM/COBOL indexed file. This program is a very simple example of the issue. It opens an indexed file and then writes the file status from that open step to an output flat file. When this program is run in Visual Studio the file status is 00 but when the exe is run (either by double clicking the exe file or by running it in command prompt) it is 30. I tried running Process Monitor (technet.microsoft.com/.../processmonitor.aspx) with a filter for any path containing "c:\\temp\\in-file". Leaving that while running the test program in Visual Studio, I see many processes show up. But then if I keep the monitoring going while running the exe, it shows no processes trying to access the input file, almost as if it never even tries to open the file. What could be different about running this program in Visual Studio vs running the compiled exe?       $SET CHECKNUM      $SET DIALECT"RM" 

I've been trying to run down why the Micro Focus product help for Visual COBOL for Visual Studio 2013 displays as raw HTML in the Windows Help Viewer 2.1 on my domain-joined Windows 7, IE 11 PC for a month now.  So far I've been told/have read that it has something to do with my account "inheriting" enablement of IE ESC from the servers on our network.  Since the **ONLY** symptom of enabled IE ESC on my PC is the display of the VCVS help content in Help Viewer as raw HTML, no pop-up dialogs about blocked sites or IE ESC warnings, I wanted to try the commonly suggested work around of adding the location of the help files to either the Local Intranet or Trusted Sites zones in IE.  But all I can find are the HTML help files for Enterprise Server. So where are the HTML help files for the rest of VCVS put when you do a default install?

New to using Relativity and being told that there is no way to do a TOP command. How do the rest of you handle situations like this and also deal with temp files that grow to more than 4 times the size of the actual Visual Cobol data file? Any other helpful guidelines welcomed as we are trying to stop using a different ODBC application and stick with MicroFocus.#Relativity#top

Problem When trying to debug into the Cobol SQL CLR stored procedure, you may get the errors below: 1. Get error "Unable to debug .NET code. Could not attach to SQL Server process on xxx". 2. The debugger just steps over the EXEC SQL CALL statement, you cannot step into the stored procedure. Resolution: For the first error, you need to run Visual Cobol for Visual Studio as administrator. For the second issue, please double check the following: 1. The Calling program's project property, debug tab, the Enable SQL Server debugging option is set. 2. In Visual Studio SQL Server Object Explorer, right click the SQL Server instance, and ensure that the Allow SQL/CLR Debugging option is checked. 3. If you have rebuilt the SQL Server Database Project, you need to re-Publish the stored procedure to SQL Server before starting debugging. Please check Tutorials: SQL Server COBOL Stored Procedures in our documentation for step by step procedure on how to work with Cobol

hi, I have a jcl that allocate vsam, but the data file have only dat and don't create the IDX file. in Server Administration I have in Configuration Information [ES-Environment]ESP=D:\\ED\\progetti\\eclipse\\IF00\\SYSTEMMF_CHARSET=Aextfh=$ESP\\cfg\\extfh.cfg and in extfh.cfg file I have IDXFORMAT=8 (default!): [XFH-DEFAULT]FILEMAXSIZE=8IDXFORMAT=8BASENAME=ONRELDATBUF=65000SEQDATBUF=512000INDEXCOUNT=65000IDXDATBUF=65000STRIPSPACE=OFF when I run jcl that allocate vsam it store data only on phisical file with extension "DAT" instead on MFE its allocate data in DAT and IDX file. why?

In traditional COBOL, if a Menu program (or say "PROGA") CALLs a sub-program (or say "PROGB") and doesn't CANCEL it upon return, the next time it CALLs it, PROGB may have its variables in the state that they were in - left over from the earlier CALL, instead of being in their initial state (let's ignore the INITIAL key word for this discussion).  My understanding is that most all the time this type of situation can result in hard-to-debug-and-maintain programs and that the general recommendation is to always follow a CALL with a CANCEL and design the subprograms accordingly (i.e., don't ever use this as a "feature"). OK, but what about Managed non-procedural programs (classes) using WinForms or WPF and such?  These are not being CALLed; they are being INVOKEd, right?  Is there an equivalent of a CANCEL that we should be doing after it returns to the INVOKEing program? Thanks

How can i create text file and are saved in utf-8 format?

Hi Chris, thanks for your previous replies re windows 10 and pc_print_file. We now have up to 100 users with the run-times installed on lots of machines so wondering how simple upgrading is? Do we just run a new run-time install exe for 2.3 on each machine on top of existing 2.2? Are their implications re. other things, licensing for example? Thanks, Linden 

Is there some way we could get a copy of the VC 2.3 Release Notes (including Resolved Issues, New Features, etc.) PRIOR to downloading the entire VC 2.3 ??? ... for planning purposes and as an appetizer...  :-)

Hi all, Many thanks for all the useful posts over the last while which let me pick up some great hints and tips. We ported our application from Net Express to Visual Cobol and made various changes to some programs that interface with Excel. I have been unable to figure out how to release Excel from memory in the Visual Cobol code though and would be very grateful if anyone can help. The earlier Net Express code let me release Excel by cycling through the used objects with invoke Worksheet "finalize" returning Worksheet and so on, but I am not sure what the equivalent is in Visual Cobol. Many thanks, John 

We are migrating a native Windows application from Net Express 5.1.  In it we use several of the file handling call-by-name library routines and we've hit a snag with the first program that uses one, specifically CBL_CHECK_FILE_EXIST.  The scenario: User environment variable dd_CNV defined with a value of C:\\NEAS\\Files\\CNV.  The COBOL source code is "CALL "CBL_CHECK_FILE_EXIST" USING JOIN-BUFFER, FILE-DETAILS."  At the time of execution in both the Net Express 5.1 and Visual COBOL 2.2 IDEs the value JOIN-BUFFER is "CNV\\WYP46D01.228     ", and a file WYP46D01.228 exists in C:\\NEAS\\Files\\CNV.  Net Express 5.1 works, returning zero in RETURN-CODE.  Visual COBOL 2.2 gets a non-zero value in RETURN-CODE that translates to 9/13, RTS error/file not found. Do the file handling call-by-name library routines NOT do file mapping in Visual COBOL like they do in Net Express?

Below are instructions to enable remote debugging using a specific port: 1) Start the ViewNow X application 2) In Eclipse, choose the dropdown menu named ‘Run’ 3) Next, choose ‘Debug Configuration’ 4) Fill in the COBOL Project and the Remote Host 5) Check the box for ‘Specify the port on which the cobdebugremote process will listen…’ 6) For ‘cobdebugremote port’ enter the port number that you wish to use on the remote Unix system 7) In the box ‘Start Options’ enter (in caps): REMOTERDO 8) Click ‘Apply’ then ‘Run’ buttons

Hi guys, I tried installing Visual COBOL (Visual COBOL for Visual Studio Personal Edition v2.2 0), but I get the following errors on install.  Any idea what is going wrong? [179C:1C08][2015-10-29T10:47:44]i000: Registry value not found. Key = 'SOFTWARE\\JavaSoft\\Java Runtime Environment', Value = 'Java7FamilyVersion'[179C:1C08][2015-10-29T10:47:44]i000: Setting string variable 'Netfx35FullVersion' to value '1'[179C:1C08][2015-10-29T10:47:44]i000: Setting string variable 'Netfx4FullVersion' to value '4.5.50938'[179C:1C08][2015-10-29T10:47:44]i000: Registry key not found. Key = 'SOFTWARE\\Micro Focus\\Visual COBOL\\2.2'[179C:1C08][2015-10-29T10:47:44]i000: Registry key not found. Key = 'SOFTWARE\\Micro Focus\\Visual COBOL\\2.1'[179C:1C08][2015-10-29T10:47:44]i000: Registry key not found. Key = 'SOFTWARE\\Micro Focus\\Visual COBOL\\2.2'[179C:1C08][2015-10-29T10:47:44]i000: Registry key not found. Key = 'SOF

Hello! I have 2 problems with an event handler. 1: I am implementing the interface ICommand and Visual Stuido tells me that the interface member CanExecuteChanged or one of its overloads is not implemented. 2: I know how to write custom set and get methods for properties in cobol, in c# I can do the same for properties but also can I write custom add and remove methods for event handlers, but how can i achieve this in cobol? My C# code i want to translate to cobol code: class RelayCommand : ICommand     {         private readonly Action<object> _execute;         private readonly Predicate<object> _canExecute;         public RelayCommand(Action<object> execute)             : this(execute, null)         {         }         public RelayCommand(Action<object> execute, Predicate<object> canExecute) &n

Am I reading the VC 2.3 Release Notes correctly? In order to upgrade from VC 2.2.2 to VC 2.3 I must first uninstall 2.2.2 and then install 2.3? Is this how its going to be for any and all updates (x.y.z) also, or does this apply to only major and minor version upgrades (x and x.y)?

Hi, I'm migrating from Net Express to Visual Cobol for Eclipse, for now I'm only testing things to understand how this Visual COBOL for Eclipse works.I created a JVM COBOL Project and I copy and paste one of our Net Express COBOL programs, when I set the compiler directive CALLFH(FHREDIR) but I get the error message "COBCH0865S Failed to find system program 'FHREDIR'", after a few searches on this forum, I found that File Handler is not supported yet for Manage Cobol programs, only for Native, and I need to ask to you, to and to , if this is still not supported. I have a lot of questions, this is one of many. Thanks in advance, #fileshare#callfh#VisualCOBOL#netexpress#fhredir

I'm needing to show a message wait, searched the web but only found in C # using Threads, does anyone have an example of how to do?

hi, why "Oracle pro*COBOL(COBSQL)" In Enterprise Developer  for eclipse in missing while In Enterprise Developer  for Visual Studio in present.? in the project properties is missing but it's work when i compile from command line with this sql directive settings: "P(cobsql) MAKESYN KEEPCBL CSQLT=ORACLE end-c COMP5=NO SQLCHECK=SEMANTIC USERID=cs3/cs3@CRIOS MODE=ORACLE DBMS=V8 VARCHAR=YES UNSAFE_NULL=YES CLOSE_ON_COMMIT=YES END_OF_FETCH=100 DYNAMIC=ANSI TYPE_CODE=ANSI p(cp) endp" thanks bye

Dear Sir, I installed Visual Cobol for Eclipse 2.3 and now I get No editor descriptor for id org.eclipse.ui.internal.emptyEditorTab when I try to edit any Cobol Program.

Do P.E. users have access to Supportline web site?  I would like to access the examples and I have not had a response from the Supportline regarding my registration.