Rocket® COBOL

Created On:  10 August 2011 Problem: The error message "can not create temporary directory" appears when compiling a program, or when executing a utility (such as Micro Focus's mfsupport utility). Resolution: Here are a few items to check in resolving this problem:Is the TMPDIR environment variable set?  Micro Focus follows the value of this environment variable when creating temporary files. If TMPDIR is set, does the directory pointed to by TMPDIR exist?  If so, do you have permission to write in that directory?  You can test this by using a UNIX command to create or "touch" a new file in that directory.If TMPDIR is not set, Micro Focus uses default locations of /tmp or /var/tmp.  Is there a permissions problem, or a disk space problem, in these locations?To solve the problem, you could set the environment variable TMPDIR to a location having adequate permissions and disk space. Old KB# 34324

Created On:  26 July 2011 Problem: The problem occurs on the Windows 7 64-Bit platform using AcuBench V9.0 Screen Designer when creating a new AcuBench product. When using screen designer and adding a GRID, Notice its completely blank and has no grid patterns etc. This issue is only linked to this platform configuration. Resolution: You simply create a separate Windows .bat file to execute AcuBench .Within this you just set PATH=(Setting the PATH to nothing and executing AcuBench - the grid (columns and rows) displays). Old KB# 34275#GRIDBLANKACUBENCH

Created On:  02 August 2011 Problem: Is it possible to do the following:- Move the cursor between entry-fields, using events- Return to the main screen and show the cursor on a new screen control- Move focus between grids Resolution: The attached samples show how to do this.Program1.cbl shows:- how to move between entry-fields;- how to open a new screen, close it and return to a third entry-field.Grid.cbl shows how to move from Grid1 to Grid2, using events and exceptions.Both samples are provided standalone and within an Acubench 9.0.1 project. Incident #2530249 Attachments Grid.cblProgram1.cblaccept-control-4.zip Old KB# 34300

Created On:  01 August 2011 Problem: Working with AcuBench projects that are sitting in a server where they can be reached from several developers, there are occasions when we will get the following message: “AcuBench has detected a corruption in one of your Project's files. Acubench will restore your project from your most recent Auto-Save.” It points to a temporary file, which does not exist. This results in not being able to work at all with the project. The project can be opened from other machines without any problems. Resolution: As the normal procedure when working with AcuBench, it generates some temporary files and registry keys related with those temporary files. When AcuBench closes a project, it removes those files and registry keys. When it starts over, it checks those registry entries and if the value is different to 0 it is when it sends this message. The registry key in question is: \\\\CurrentUser\\\\SOFTWARE\\\\CASEMaker\\\\AcuBenchxxx\\\\Tem

Created On:  01 August 2011 Problem: Commencing on version 9.0.0, there is a new location of the installation and the licenses on Windows platforms. Resolution: New Installation location on Windows:The Windows installation directory structure for all extend products has changed. In particular the former directory "Acucorp" has been renamed to "Micro Focus". For example, version 8.x of ACUCOBOL-GT is installed here: C:\\Program Files\\Acucorp\\Acucbl800\\AcuGT Now, version 9.0.0 and higher is installed here: C:\\Program Files\\Micro Focus\\Acucbl900\\AcuGT Windows license file location changes:Version 9.0 now follows the Microsoft guidelines for license file locations. When using a standard ACUCOBOL-GT installation and License Activator you should see no change in behavior. However, license files are no longer created in the installation directory (C:\\Program Files\\Acucorp\\Acucbl900, by default on Windows XP). Instead, license files are created in an a

Created On:  02 August 2011 Problem: Using runtime 8.1.1 or earlier on Windows 7, no Font dialog box opens when called. A CALL "W$FONT" USING WFONT-CHOOSE-FONT returns value -1. Resolution: Windows 7 manages the Font dialog box in a different way than Windows XP. It is now mandatory for it to call the native API comctl32.dll. However, setting WIN32_NATIVECTLS to 0 (the default value) causes the exclusion of the said dll. So, a workaround may be to turn WIN32_NATIVECTLS configuration variable ON, using runtime 8.1.1 or earlier.  From runtime 8.1.2, this is no longer necessary and the Font dialog box is shown correctly, regardless of the value of WIN32_NATIVECTLS.See ECN-3976 for further information about this issue. Incident #2530193 Old KB# 34299

Created On:  05 August 2011 Problem: In which version of Acu4GL for Oracle was Oracle 11G R2 supported? Resolution: Although Oracle 11G has been support by Acu4GL for Oracle since version 8.1.0, support for Oracle 11G R2 did not begin until version 8.1.2.1. Incident #2526126 Old KB# 34311

Created On:  04 August 2011 Problem: I have a Visual Cobol Solution, that contains two projects each with a Windows Form. One Windows Form has a button and the other a textbox control.How can a value (string) be sent across projects, for example, if I click on Button on Form1 I want it to populate the textbox1 on Form2 with some text.Would the line of code look something like the following for the btnSend_Click method:        set form2::textbox1::text to "this is a test". How can I reference components on other forms that are in other projects but in the sane solution? Resolution: Add a reference in the Form1 project to the Form2 project.Form 1 needs to define a data item to hold the instance of Form2.In this example Form2 will be instantiated from within Form1.       class-id testtextspace.Form1 is partial                 inherits type

Created On:  09 August 2011More Visual COBOL results at kb.microfocus.com Problem: While attempting to install Visual COBOL 2010 you receive the top message below or while attempting to install COBOL 2010 Runtime you receive the bottom message below:What does this mean? Resolution: These error messages are correct in that Visual COBOL for Visual Studio and COBOL 2010 Runtime products cannot be installed on the same computer.  Visual COBOL is the development environment which integrates into Visual Studio 2010. It has all the components of the COBOL 2010 Runtime product installed with it so that you can test your applications on the development computer without the requirement of a production runtime license. The COBOL 2010 Runtime product is for production use and it contains all of the files necessary to run the developed applications on a computer where Visual COBOL is not installed.  These products each are licensed separately.  Where you might h

Created On:  29 July 2011 Problem: There is a problem with the Visual COBOL R4 documentation for using the RM compatible C$RERR routine.The documentation states:Configuring the RM/COBOL File Handler  In acurmfm.cfg, set the file handler. DEFAULT_FILESYSTEM RMFMTo retrieve RMFM file status codes or call C$RERR in your COBOL programs: In acurmfm.cfg, set the following environment variables. set CONVERTSTATUS=rmstatset COBCONFIG=cobconfig.cfg  *> cobconfig.cfg is your MF COBOL run-time configuration file.In cobconfig.cfg, set the following environment variable: set ACU_LIBRARY=TRUE-------------------------------------------------------This does not work. Resolution: The COBCONFIG and CONVERTSTATUS environment variables must actually be set in the computers environment instead of in the acurmfm.cfg file.  If you follow the instructions in the documentation you will get a Runtime Error 173 on the call to C$RERR.If the COBCONFIG and CONVERTSTATUS envir

Created On:  26 July 2011 Problem: When running Thin Client from a Windows XP machine, you get the message "Connection failed. Server failed to start remote process. Check message on server."The trace file on the server (Windows 2008 server) shows a message "Trying to create Process" ... and at end of message "failed: 267). Resolution: The Error 267 in Windows environment means Invalid Directory.  An invalid directory path/name or inadequate permissions on one of the directories or sub directories causes this error.  Ensure the working directory specified in the Alias entry is correct. Check the permissions for all leading directories to both the runtime and object files.  Check the AcuRCL configuration file (acurcl.cfg) to ensure the correct path specification is set for SERVER-RUNTIME.  This must be set if the remote runtime is installed in a different directory than AcuRCL. Old KB# 34286

Created On:  01 August 2011 Problem: Users have the utility called CHKLOG to periodically clear the event.log, but there is no utility to clear the connect.log file.  How is this done? Resolution: You can go ahead and delete the connect.log as it will create a new one for the next log entry. If you receive an error message when trying to delete it you will need to stop the server first. You can disable the creation of the connection log by deleting the "InstallDirectory" entry from the [SimbaServer] section of the odbc.ini file, which is located in the Relativity Data Server installation directory. Incident #2530278 Old KB# 34296

Created On:  26 July 2011 Problem: Using CBL_DELETE_FILE for large and small files on Windows and UNIX. It successfully removes files less than 2GB on both Windows and Solaris, and removes files larger than 2GB on Windows. But it is failing (with status code 1) to remove files 2GB or larger on Solaris. Resolution: This should be resolved by setting the environment variable below:USE_LARGE_FILE_API=1  export USE_LARGE_FILE_APIOn UNIX systems, this variable allows you to turn on or off file system API support for very large files (greater than 2 gigabytes). Support for large files is enabled when USE_LARGE_FILE_API is set to "1" (on, true, yes). Some UNIX systems do not support files greater than 2 gigabytes in size. In those situations, setting this variable to the default of "0" (off, false, no) causes the runtime to use the standard 32-bit file system API. This variable has no effect on Windows platforms. Old KB# 34282#deletelarge2GB

Created On:  08 August 2011 Problem: Users have both data files, with and without extension. Using AcuXDBC, there is a file-suffix variable they can set into the configuration file, but it will not find any that do not have a suffix. Needs to be able to see both. Resolution: Multiple suffixes are not support by AcuXDBC; but there are two workarounds that users with the same issue have implemented: a) Use multiple acuxdbc.cfg configuration files and point these in separate DSN's. b) Setting Up File Aliases, as we mentioned in our AcuXDBC User's Guide: Chapter 5:Installing AcuXDBC; 5.5 Loading the System Catalog with Your XFDs; 5.5.1 Setting Up File Aliases. In this last approach you do not have to use the FILE-SUFFIX variable in the acuxdbc.cfg fil; but you will need to add the files to the System Catalog using the following syntax: xfdname#tablename#filename.dat (or whatever is the suffix you are using or none). This way AcuXDBC will link the table name with the fi

Created On:  28 July 2011 Problem: What is the difference between system time and total user time? Resolution: Total user time: This is the total number of seconds used by all the programs in the executed run. It is shown under the Program Summary in the report. System time: This is the number of milliseconds of CPU time spent processing system code on behalf of the profiled process. Incident #2529788 Old KB# 34288#SystemTime

Created On:  22 June 2011 Problem: When attempting to compile the Server Express demo program $COBDIR/demo/c-cobol/cobsub1.cbl, the module "cmain1.cpy" cannot be found in any of the demo directories. Resolution: Copy the $COBDIR/demo/c-cobol directory contents into a working directory and then run the script ccob1.sh. This should create cmain1.cpy. Incident #2508072 Old KB# 34184

Created On:  24 June 2011 Problem: This article details how to run Micro Focus LMF, ASLMF and ESLMF licensing as a non-root user.  The following instructions assume that the Server Express and Server products are being installed on a clean machine. The instructions do contain some steps to remove files if they are present from a previous installation. Resolution: LMF LicensingStep 1.Install Micro Focus product.  See product install notes that came with product for full details. During the installation you will be taken into the LMF installation.   Text will appear as….This product is protected using the Micro Focus License Management Facility (LMF). Please refer to the Development System Licensing Guide for information relating to the installation of the licensing system and licenses.If you do not have LMF installed or want to upgrade to the latest version, we recommend you install it now.Would you like to install LMF now? (y/n):yEnter the directory name

Created On:  30 June 2011 Problem: Trying to install Server Express on Solaris gives an error message as follows:Enter the absolute path to the directory where Server Express should be installed.   Press return to use (/opt/microfocus/cobol)/home/support/products/opt/microfocus/cobol Installation directory /home/support/products/opt/microfocus/cobol does not exist.Do you want to create it? (y/n): y Installing into /home/support/products/opt/microfocus/cobol Do you want to continue? (y/n): yCopying files. This can take several minutes. Please wait....tar: ././@LongLink: typeflag 'L' not recognized, converting to regular filetar: ././@LongLink: typeflag 'L' not recognized, converting to regular filetar: ././@LongLink: typeflag 'L' not recognized, converting to regular filetar: ././@LongLink: typeflag 'L' not recognized, converting to regular filetar: ././@LongLink: typeflag 'L' not recognized, converting to regu

Created On:  22 June 2011 Problem: The COBOL application loops continously until an operator terminates the application.  It first connects to a database and reads transactions from a table, then goes into an idle mode wherein the application is just incrementing a counter until it reaches a specific value.   It then connects to an external database and updates an external table, goes back into idle mode, and the whole cycle begins again. During this idle period the CPU usage is very high as measured by Task Manager. The application is just counting and there is no I/O yet the CPU usage spikes during this time. Is there a parameter somewhere that we can change to lower the CPU usage without changing the code? Resolution: If the application is incrementing a counter then it is still utilizing the CPU.  You should instead call the library routine CBL_THREAD_SLEEP or the winapi Sleep function to actually relinquish the time sli

Created On:  16 June 2011 Problem: For certain programs, it may be desirable to use the CHAINING phrase as part of the PROCEDURE DIVISION header. While the AcuBench documentation discusses the automatic generation of the USING phrase, there does not appear to be a way to incorporate the CHAINING phrase. Resolution: AcuBench does not have a way to automatically insert the CHAINING phrase into a generated program. This can be worked around with a manual modification and changing one of the settings in AcuBench.The two AcuBench tags below in the .cbl file are removed then the CHAINING phrase is inserted with the parameter desired as shown below.*{Bench}linkpara <---- remove     PROCEDURE DIVISION CHAINING MY-PARAMETER. *{Bench}end      <---- removeBefore regenerating, AcuBench must be configured not to regenerate the tags that were removed. From the Tools menu, select Options, Code Generator, check the Regenerate tagged a

Created On:  01 July 2011 Problem: When running an ACUCOBOL program, can you get the name of the configuration file that was passed to the runtime? Resolution: With ACU, there are a number of ways for the runtime to pick up the configuration file that it will use, so it can be useful to get the name of the configuration file that is being used. The name of the configuration file is stored within the runtime, but is not directly available to the programs in the run unit. As part of the information that is put into the runtime log file, which is generated by the –lex option, is the name of the configuration file together with the options that were used. The line that holds the configuration file name is of the format:                  Configuration file = '' Within a Cobol program it is possible to define a line sequential file and open up the log file to get the name of the configuration file. T

Created On:  27 June 2011 Problem: Having the runtime installed in a primary machine, like:my-firstmachine:C:\\Program Files\\Micro Focus\\Acucbl900\\AcuGT\\bin.The .NET DLL is sitting in this same folder as well.There is a programs folder in a second machine which is been mapped as Z: drivemy-secondmachine:C:\\objectsChanging to the mapped drive and executing the following command, it works perfectly, creating the object.Z:>"c:\\Program Files\\Micro Focus\\Acucbl900\\AcuGT\\bin\\wrun32" my-program But, doing:Z:>\\\\my-firstmachine\\c\\"Program Files\\Micro Focus\\Acucbl900\\AcuGT\\bin\\wrun32" myprogramIt executes the cobol program but when it trys to create the object it generates an error "There was a problem with one of .NET support libraries.NET assemblies cannot be loaded"This same error happens if the cobol object is copied to the /bin directory, then maping the Acu/bin directory of my-firstmachine from a third one as Y: like: &quo

Created On:  08 July 2011 Problem: If you have a Visual Studio Solution which contains managed code projects that call into native code projects you cannot simply step through the managed program into the native program using the debugger.You can step through the managed code but when the call is made into the native program, the native program will run at full speed and control will return to the debugger as soon as it returns from the native program.How is it then possible to debug the called native portion of the application? Resolution: The following instructions are for customers who have Visual Studio Solutions containing managed projects with Console, Winforms, WebForms and WPF front ends that call programs in native projects that are packaged in .dlls. In order to debug the called native code it is necessary to do the following: If you have a native program that you want to debug and it is NOT a web application you can: 1. Modify the start program under the debug ta

Created On:  29 June 2011 Problem: When using Pro*COBOL with Oracle in Net Express it was possible to pass COBOL arrays as parameters to a stored procedure by using the EXEC SQL EXECUTE ...END-SQL construct. Pro*COBOL is not supported in a managed code environment so how can I still pass arrays as parameters to an Oracle stored procedure when using ADO.NET? Resolution: This is currently not supported directly using embedded EXEC SQL or EXEC ADO statements as these only work with generic ADO classes that are not bound to a particular database vendors product.It is however supported by using the .NET Framework classes along with the Oracle Data Provider class Oracle.DataAccess as shown below.The source for the stored procedure appears after the sample program and it must be run using Oracle PL/SQL or some other tool before the application can be run.The following is source code for a Visual COBOL 2010 managed console project:       $set ilusing"S

Created On:  29 June 2011 Problem: With Visual COBOL for Visual Studio you can tell what version is installed by clicking on Help-->About Microsoft Visual Studio from the IDE and then clicking on the Visual COBOL product in the list of installed products.Version numbers will show as:Visual COBOL 2010 R4 Version 1.3.00046.So how does one tell what version of the COBOLRuntime 2010 product is installed on a production computer under Windows where Visual Studio 2010 in not installed? Resolution: You can tell what version of the COBOLRuntime 2010 product is installed by using Windows Control Panel-->Add/Remove Programs and clicking on Micro Focus COBOL 2010 Runtime in the list.Then click on the link for: Click here for support information:Version information will appear as 1.n.nnnnn where:1.1.nnnnn = R2 release1.2.nnnnn = R3 release1.3.nnnnn = R4 releaseetc. Old KB# 34208