Rocket® COBOL

At the company where I work we use RMCobol; In the help-file I can consult I can't find a way to make it possible to set the cursor-position in a multiline edit-box. Is there anybody who knows how to do that?#COBOL

I have experienced some problems I want to share.Keep logged in doesn't work, when returning I was asked to log in again.Today it was possibel to quit and return but is there a time-out? Shouldn't be. When asked to recover pw last week no mail arrived, worked today.Mail should mention user ID.Couldn't log in as I forgot ID and asumed it was the mail-address. after several tries I managed to login. Login should be simple and transparent, place for improvements maybe?#login

Visual COBOL R4 Installer Technology For the Visual COBOL R3 product set a new shell script and pax file installer was created.  This revolutionised the installation of the UNIX product making the process simple for users and resolving a lot of technical debt, maintainability and limitations found in the Server Express installers. For the release of Visual COBOL R4 we wanted to push the install technology even further.  One downside of the R3 installer was that it consisted of two files:  the shell script installer and the product pax file.  This meant two files had to be copied about and kept together. New for R4 For the R4 release a new binary wrapper has been created.  This wraps the install scriptand product pax file into a single file.  This means that only one file now needs to be downloaded or copied to the destination machine.  The wrapper has the ability to check the installation environment and make sure the product is being installed on the

Attachment - testTooltip.zip Please download and unzip the attachment called testTooltip.zip into your C: drive, retaining the folder structure in the zip file. Open Visual Studio 2010 and open the solution C:\\testTooltip\\testTooltip\\testTooltip.sln. Build and run the demonstration by pressing the F5 key.Hover over each of the buttons to see the Tooltip that is displayed for each. - Button1: Tooltip is displayed in a 3-D manner- Button2: Tooltip is graphically painted- Button3: Tooltip displays an image file Click the Exit button when done. To debug the project, start it by pressing F11.      #VisualStudio#language#VisualCOBOL#HowTo-BestPractice#COBOL#.net

SmartLinkage – what does it do? Prior to R4, if you wanted to call a COBOL program from another language, you had to create wrapper functions to convert the COBOL data items to managed types. SmartLinkage does that for you, so you can access COBOL linkage data from other managed languages transparently.– No hand-written wrapper classes needed– No changes required to the original code– COBOL data shown in C#/Java/COBOL intellisense  Easy configuration steps • Project1 (COBOL) – Create a managed project and add COBOL code– Compile with the ilsmartlinkage directive• Project2 (eg C#)– Create a C# project in the same solution– Add a project reference to Project1– Add a reference to MicroFocus.COBOL.Runtime (unless Project2 is COBOL)– Now you can access Project1’s linkage data directly  Customisation • Default– hyphens are removed from COBOL data names and the following letter upper-cased   eg lnk-details is accessed from C# as lnkDetails • ilcutprefix(x) direc

Visual COBOL for Eclipse R4 is GA today! This is the first Micro Focus release which includes a full GA version of COBOL for JVM... (a pre-release add-in was available with Visual COBOL R3.) So where to start? You could Look at the samples - familiarise yourself with some of the new syntax features by looking at the JVM COBOL sample code provided with the product             or Create a new application using the templates provided             or Import your existing application to a JVM COBOL project Let’s look at these options in more detail... JVM COBOL Sample Code JVM COBOL samples are included with the product. If running on Windows there is a SamplesBrowser, which you can access from the Start Menu. Windows The samples are installed in subfolders under C:\\Users\\Public\\Documents\\Micro Focus\\Visual COBOL 2010\\Samples. Note: On older versio

Download attachment VCCOMDemo.zip    VCCOMDEMO  This demonstration program shows how a Visual COBOL .NET managed class can be called from a Net Express (or Visual COBOL) native program. The technology used is part of the .NET Interop technology and is known as COM Callable Wrapper or CCW.  Basically what happens is that the .NET class is registered as a COM server so that the native COBOL program can call it as such using the COM support available in Net Express. Actually this is not limited to being called by a Net Express application as any COM enabled client can call this server.  The demonstration consists of two parts, a managed Visual COBOL project called VCCOMServer and a native Net Express project called NXCOMClient. Please unzip the attached file VCCOMDemo.zip onto your C:\\drive, retaining the folder structure of the zip file. VCCOMServer: This class becomes a CCW by turning on the option Register for COM Interop which is found at the bottom

Contents: Problem Sandcastle Steps for integration Remarks Known limitations for Visual COBOL Sandcastle.Targets file Watch Video Demo Problem: You want to generate automatically MSDN style help when building managed COBOL applications. Sandcastle: Sandcastle is a documentation compiler tool for managed Class Libraries. It produces accurateunderstandable, MSDN style documentation by reflecting over the source assemblies and optionally integrating XML Documentation Comments. The tool can be downloaded and installed from http://sandcastle.codeplex.com/.  Sandcastle includes a few components that need to be executed in order to generate the help file: MrefBuilder.exe – Parses managed assemblies and generates XML output file with reflection information. XslTransform.exe – Applies XSL transformations to an XML file. BuildAssembler.exe – Creates HTML topics with generated syntax from the XML input. ChmBuilder.exe – Generates an hpp file from the collected information which is needed

What are Watchpoints ? Watchpoints are a special kind of breakpoint available when debugging native COBOL code. Rather than being associated with a specific line of code in your application they are associated with a COBOL data item. They allow you to break every time a data item's value changes. Without watchpoints you would have to set a breakpoint on each line where the item, or any redefinition of the item, was used in order to monitor changes to that item. In a simple program that may not be a problem but for a large, complex application that would not be practical as it may not be obvious where the item is used. Setting a watchpoint Let's assume that in the following program we want to track when the value of item2 changes.        identification division.       program-id. Program1.        environment division.       confi

  The article will review the common properties of the CheckBox control. These are the name, text, checked and checkstate properties. We’ll also review the use of events associated with a CheckBox.  An event when it occurs invokes or calls a method to handle the situation that has just occurred. For those unfamiliar with the term ‘method’, a method is a piece of code that is executed when called, kind of like a small program. We’ll go into methods more in a little bit. WinForm We’ve already created the WinForm we’ll be using. Remember, the intent is to learn how to manipulate CheckBoxes, not create WinForms. Our WinForm was specifically designed to be simple and present only the basic information. It appears as:   Pretty simple, right? At the top we have a Label that provides some information about Check Boxes. We also have a button on the screen that says “Reset” and we have the Check Boxes contained within a group item titled “Color Selection”. There are actually more

In my last entry I gave an overview of how we test the core component for the Visual COBOL product. In this entry I will cover how we test the Visual Studio and Eclipse integration. Testing of the Visual Studio IDE is kicked off using an in house tool called ‘TestCat’. This tool simply monitors for the availability of a batch script, which is created during the overnight build of the product. The TestCat tool runs the script, which has a number of commands contained – it starts Hyper-V machine instances, copies the build onto the virtual machine and kicks off the IDE tests after installing the test build. Tests cover the basic functions of the IDE, but also more advanced testing such as various project and debugging scenarios. The results are then assembled in HTML reports and published. The Eclipse IDE is tested in a very similar manner. The tests are kicked off overnight, and test failures are reported through a web page and via email notifications.  This process runs several th

Attachment: GridTooltip.zipVisual COBOL 2010 R3 Winform project.  This demo shows how to display a Tooltip image for a dataGridView control which is dependant on the row in the control over which the mouse is currently hovering. Each time the mouse is moved to a different row the image to display will be changed to reflect the new row. Please download and unzip the attachment called GridTooltip.zip into your C: drive, retaining the folder structure in the zip file. Open Visual Studio 2010 and open the solution C:\\GridTooltip\\GridTooltip\\GridTooltip.sln. Build and run the demonstration by pressing the F5 key.Hover over each row in the dataGridView control to see the Tooltip that is displayed for each. Click the Exit button when done. To debug the project, start it by pressing F11.  #.net#VisualCOBOL#COBOL#HowTo-BestPractice#development#VisualStudio

The attached Visual COBOL project contains a .NET managed code Windows Forms application that demonstrates how to allow a user to click on a button and automatically display a Print Preview Dialog or to send the image of the current form to the default printer for printing. $set ilusing"System.Text"$set ilusing"System.Drawing.Printing"$set ilusing"System.Windows.Forms" class-id screenprintvc.Form1 is    partial inherits type System.Windows.Forms.Form. working-storage section.01 PrintDoc1 type PrintDocument value new PrintDocument.01 PPDlg1 type PrintPreviewDialog value new PrintPreviewDialog.method-id NEW.procedure division.   invoke self::InitializeComponent   set PPDlg1::Document to PrintDoc1   set PrintDoc1::OriginAtMargins to true   invoke PrintDoc1::add_PrintPage(new System.Drawing.Printing.PrintPageEventHandler (self::pDoc_PrintPage))   goback.end method.method-id pDoc_PrintPage private.local-storage section.01 bmp type

Our examples will focus on a single control. We’ll show you how to manipulate the properties of that control programmatically. We may have to include one additional control but the focus on each project will be on a single control with a supporting role for the additional control. This article is about the Button control. In a previous article we introduced the Label control and also used the Button control in a ‘supporting’ role to the Label. The Button is what I like to refer to as an ‘initiator’, that is when the button is clicked or pushed it starts something. Buttons are made to tell the application that “I’m done entering something please go process it”. The Button therefore not only has properties that we can change (color, text, etc.) programmatically but methods that we can call when an event occurs. There are numerous events associated with a Button but we’ll concentrate on the main events. An event when it occurs invokes or calls a method to handle the situation that has ju

  The DateTimePicker control, along with the namespaces System.DateTime and System.TimeSpan can however save a COBOL developer a significant amount of time where date validation and manipulation is concerned. The DateTimePicker control restricts the input of data to valid dates, it can contain proper formatting and be set to ensure data ranges are valid before any data is accepted into the application. The System.DateTime namespace provides the developer with a set of properties and methods geared specifically towards date and time manipulation. The System.TimeSpan namespace allows us to determine the amount of time between two points in time as days, hour, or minutes. As we’ll see in the article existing date calculations that used to require numerous lengthy paragraphs to determine can now be handled with one or two lines of code. The DateTimePicker example will show several different methods of determining date values and how they can be used with existing code. WinForm We’ve

Visual COBOL and COBOL for .NET Language Introduction Visual COBOL Demo Sample Application files The Visual COBOL product family offers a high level introduction into the COBOL for .NET programming language and using Visual COBOL in the Visual Studio IDE.This provides provides a look into Visual COBOL concepts and features, and how existing code can be migrated to take full advantage of COBOL for .NET. To open the document, click on the Visual COBOL and COBOL for .NET Language Introduction link and open it using Acrobat Reader.Download the attached demonstration application files from the Visual COBOL Demo Sample Application files link to a location where it be accessed using Visual COBOL R3. Then open the application's solution in Visual COBOL. The demonstration application includes code that helps you walk through the material in the introduction.As always, we are keen to get any feedback that would help improve this document. Let us know what you would like to see in the Visual COBO

  Our examples will focus on a single control. We’ll show you how to manipulate the properties of that control programmatically. We may have to include one additional control but the focus on each project will be on a single control with a supporting role for the additional control. Our first control is the Label. While maybe not a glamorous control, the Label provides a very important function for the developer: It enables the developer to present content, instructions or images to the user. Without the Label presenting information to the user all we’d have is a form with a bunch of boxes or circles without any idea what they were for. So let’s begin by looking at how to work with Labels. WinForm We’ve already created the WinForm we’ll be using. Remember, the intent is to learn how to manipulate Labels, not create WinForms. Our WinForm was specifically designed to be simple and present only the basic information. It appears as:   Pretty simple, right? At the top we have a L

I'm at a loss...  We have some legacy applications that are compiled with Object COBOL 4.0.32 which was installed on an older desktop.  The desktop recently died and I'm now trying to install the compiler on a newer machine.  The machine is WinXP SP3 with 1GB RAM.  Nothing is running on it and I've disabled NAV, the firewall and everything in the BIOS set-up that looked like it might get in the way.  I was able to install COBOL 4.0.07 and the WinSDK without a problem, but trying to run the 4.0.32 Update keeps throwing an error when it gets to "Checking Configuration...": Execution error: file 'UPDATE' error code: 114, pc=0;call=1,seg=0 (Signal 11) I have tried running it in Compatibility mode and unchecking the "Protect my files" option under "Run As" as well as running it as Administrator.  I have also tried Safe Mode in XP, a Win98 Virtual machine, running it from the command prompt, and I removed a 512MB

[Migrated content. Thread originally posted on 20 December 2011]Hello,I am migrating to VisualCobol some RMCOBOL programs , and I have found some problems. I wanted to know if there is some kind of solution for these problems, or if it will be corrected in future VisualCobol versions1)When we want to verify that a file exists, some programs perform the following instructions ..                      ....            SELECT OPTIONAL FICHSEC ASSIGN TO RANDOM LOC-FICHSEC                  ORGANIZATION LINE SEQUENTIAL                  ACCESS IS SEQUENTIAL                  FILE STATUS IS STAT-FICHSEC.        ....           OPEN INPUT FICHSEC.                     I

[Migrated content. Thread originally posted on 11 May 2011]Does anyone have any experience with a Cobol source Code Control System? which one? I have been trying to understand TortoiseSVN and TortoiseHg but thought there mught be a better system out there somewhere.ThanksDavid

[Migrated content. Thread originally posted on 23 February 2011] Hi Everybody i am faceing Storage violation issue in CICS.I am looking for following information if any body can help.a) My Dump say "Shared memory: Unlocked"b)DUMPCODE: Violatedc)Shared memory: Unlocked , DUMPCODE: ViolatedI am also attching the dumps i had.I will be really thank full is somebody can understand this dump and let me know , what its trying to say.Thanks and RegardsCheeta L Please find the code here

[Migrated content. Thread originally posted on 16 February 2012]The Micro Focus Developer Conference 2012 is a free event for the COBOL community, being held at the Crowne Plaza Hotel, Downtown Dallas, Texas on 16, 17, 18 April, 2012.The conference theme is 'The future of Enterprise Application Development', and this is a must attend event for anyone interested in COBOL application development and those generally interested in keeping up-to-date with the latest COBOL news and views.For details of the agenda, venue and to reserve your place, visit the conference webpage.

[Migrated content. Thread originally posted on 20 August 2007]We are currently looking for a programmer/developer for our small IT based company providing on-line debt recovery services in Lancashire, England. If you know someone who might be interested please email me at nick@colsys.net

[Migrated content. Thread originally posted on 11 February 2011]In case you missed it (which is easily done!) we announced the latest update to RM/COBOL this week. This release addresses over 40 customer-reported stability, and enhancement requests. This is the second WebSync release for RM/COBOL 12 and delivers on our previous commitment for continued support for our RM/COBOL customers. officially, it's RM/COBOL 12.06 and can be downloaded via the Micro Focus Supportline site.

[Migrated content. Thread originally posted on 05 June 2012]thers is an aid: cblcored, As I understand it it sets registry key values in [HKEY_LOCAL_MACHINE\\SOFTWARE\\Micro Focus\\NetExpress\\3.1\\COBOL\\3.1\\Config]"core_on_error"=dword:00000002These values are documented as in documentation.microfocus.com:8080/.../index.jspBut what about "debug_on_error"=dword:00000080In documentation it only has value 0 or 1 but on my system it has 128?