Rocket® COBOL

Created On:  14 March 2011 Problem: Is there any way to reorder sessions in Rumba 8.0 desktop profile? Resolution: Rumba sessions can be reordered in a desktop profile by editing the RDPS file in a text editor such as Notepad. This can be achieved by using the following steps: Launch Windows Explorer and navigate to the folder where you have saved your Rumba desktop profile (RDPS file). Now open the .rdps file in Notepad. All Rumba sessions are contained inside the session tag as shown in the attached example. The tabs appear in the same order as these tags are saved in the rdps file. Reordering these tags will change the order of the tabs in a desktop profile. Please note a new feature has been incorporated in Rumba 8.1 that allows a user to drag and drop the tabs to reorder the sessions in a desktop profile. Incident #2494835 Old KB# 33672#Rumba

Created On:  16 March 2011 Problem: After installing Server Express on an AIX RS6000 server using Oracle's makefile and trying to compile the following errors are returned: Ld: 0706-006 Cannot find or open library file: -lm ld: open(): no such file or directory Resolution: Oracle’s makefile "env_precomp.mk" includes the following line: MATHLIB=-lm This option "-lm" tells the system linker to bring in the standard system math library “libm.a" which is usually found in /usr/lib. When "ld" reports it "Cannot find or open library file -l m" the linker is indecating it can't find the standard math library. Ensure the libm.a is installed in /usr/lib. Incident #2426123 Old KB# 33707#linker#0706-006#ld

Created On:  14 March 2011 Problem: ACUCOBOL-GT runtime 8.1.0 64-bit fails to start on a Windows 64-bit machine.  When launched, wrun32.exe causes an Application Error popup window to appear.  The error window contains this message:"The application was unable to start correctly (0xc000007b). Click OK to close the application."Other executables in the BIN directory start correctly. Resolution: Upgrade to 8.1.1 or later or apply the attached patch. Incident #2507187 Attachments 810_64bit_fix-to-setup.zip810_64bit_Application_Error.jpg Old KB# 33667

Created On:  11 February 2011 Problem: There is no uninstall script to remove the Server Express development product. How is this done? Resolution: Depending upon the version of the Server Express (SE) products, the default path to these subfolders could be different and also some of the earlier versions of Server Express does not have ESLM and MFDS components.   -  Logon as the ES Admin user and stop any running Enterprise Servers either via the ES Admin webpage  or the "casstop" command:        casstop -rESNAME          or          casstop /rESNAME                 where ESNAME is the name of the enterprise /to stop.-  Logon as root and stop the License Manager, the "mflm_manager" process, by running the command:&nbsp

Created On:  03 March 2011 Problem: How can I limit the size and amount of CTF trace files to be generated during a CTF trace? Resolution: There are 2 emitter properties that can be used to control the size and amount of CTF files that are produced during a CTF Trace. The two properties are MAXFILESIZE and MAXGENERATION.MAXFILESIZE sets the size of each trace file and MAXGENERATION sets the number of trace files to generate.For example, one could set the properties as follows:mftrace.emitter.binfile#MAXFILESIZE=0x00002800   (use hexadecimal format; this example is for 10Mb)mftrace.emitter.binfile#MAXGENERATION=3 (this will produce a total of 3 log files) When the max size is reached a new file will be started up until the number set in maxgeneration is reached.The file generation will then start again by overwriting the first file generated and so on.A sample ctf.cfg file may look like this:mftrace.level=debugmftrace.dest=BINFILE## Emitter BINFILEmf

Created On:  04 March 2011 Problem: A client added a compiler directive (in this instance SPZERO) in their COBOL Environmental Variable file "CompileCob64.sh" on Server Express. But, when we tried to compile any program it returned the error - " Cobol Compiler Argument exceed 128 bytes limit".  UNIX systems can restrict the maximum length of the operating system's command line, which can be as low as 128 bytes. Resolution: One way round this is to place system-wide cob parameters in a text file  $COBDIR/etc/cobopt. If you do it this way it means all compiles will pick up that directive (plus any others set in $COBDIR/etc/cobopt). Setting it here means this is a global directive, therefore if some parts of the application must be compiled without this directive you would not put it here.The file $COBDIR/etc/cobopt should already exist and is just a text file. You’ll see that each directive is set on a separate line and so all you’d do is add

Created On:  03 March 2011 Problem: Program is using a SQL Server ODBC connection and is receiving a sqlcode -207 error when executing the following singleton SELECT statement:    EXEC SQL       SELECT           A.Dealer          ,A.Name       INTO          :TEST-Dealer         ,:TEST-Name:TEST-Name-NULL       FROM TEST A       WHERE (A.Dealer = TEST-Dealer)    END-EXECsqlcode -207 means "Invalid Column Name TEST"Why is this being returned? Resolution: This error is caused by the missing colon character ":" in front of the host variable name TEST-Dealer in the WHERE clause.It should look like this instead:       EXEC SQL

Created On:  10 March 2011 Problem: How do I create a custom owner drawn ToolTip for a Windows Form Control in Visual COBOL 2010? Resolution: A demonstration program is attached, testTooltip.zip which shows you how to create a customer owner drawn ToolTip for controls on a Windows Form (WinForm) in Visual COBOL.Unzip testTooltip.zip onto your C: drive retaining the directory structure in the zip file.Using Visual COBOL 2010 R3 or higher open up the solution in C:\\testTooltip\\testTooltip\\testTooltip.sln.The form has three buttons on it, each with its own type of Tooltip.Run the program by pressing F5.Hover the mouse over each of the buttons to see the Tooltip that is created for it.Button1 uses a 3-D look and feel, Button2 uses a painted Tooltip with custom font and Button3 will display an image file stored in LOGO.GIF.Look at the source code behind to see how each is being drawn. Attachments testTooltip.zip Old KB# 33650#WinForm#WindowsForms#tool

Created On:  14 March 2011 Problem: Windows Operating Systems allow User Names to be 20 characters long at maximum.  These cannot be used as the "Client" or "Local User Name" in the Access User control panel of AcuConnect Thin Client.  Is there a way to solve this issue? Resolution: The limit of 16 characters still exist in AcuConnect control panel for User Name, even with the release of extend 9.0.  This is due to the fact that AcuConnect is designed for use on multiple operating systems some of which have such a limit. Windows has no such limit and those usernames longer than 16 characters can prevent connection. Incident #2503589 Old KB# 33668

Created On:  09 March 2011 Problem: When using Terminal Services, you can encounter the following error:  "Error invoking unauthorized copy of Runtime: Use count exceeded (Loc 518)"  This error can occur even if you have the correct number of named user licenses. Resolution: If you encounter a "Use count exceeded" message when using RM/COBOL through Terminal Services, but, you have not actually exceeded your named user license count, please contact Micro Focus Customer Care (support@microfocus.com), or, your Micro Focus Sales Account Manager.  This is a known issue that can be addressed through core based licensing. Old KB# 33641

Created On:  11 February 2011 Problem: There are no uninstall scripts to remove the Application Server for Server Express or Server for COBOL products on any of the UNIX platforms.  Resolution: Depending upon the version of the Application Server for Server Express (AS) or Server for COBOL products, the default path to these subfolders could be different.  The earlier versions of the Server product was named Application Server for Server Express, however, the later versions have now been renamed as Server for COBOL. -   Delete the $COBDIR product directory and its subdirectories.     The default directory for the "cobol" installation varies between versions of Server products:    From v1.0 to v2.2 SP1, the default COBOL directory is                 AIX:  /usr/lpp/cobol         

Created On:  09 March 2011 Problem: When installing RM/COBOL on a 64-bit distribution of Linux, the install.sh script can fail with a "floating point exception" error. Resolution: This is a known issue caused by the fact that it is not always possible to execute binaries built with a newer version of the Linux kernel on a older version of the kernel.  Below is the kernel version information (uname –k) from the system that we use to build the 64-bit RM/COBOL Runtime:  2.6.18-53.1.13.el5From this output you can determine that the Linux kernel that the Runtime was built on is 2.6.18.  If your Linux system is running an older kernel than 2.6.18, then, you might not be able to use the 64-bit port of RM/COBOL.If this is the case, then, you can try the 32-bit Linux port instead.  RM/COBOL for 32-bit Linux is built on an older Linux kernel and, therefore, it might work on your machine.**Executing 32-bit binaries on a 64-bit Linux distribution might require addit

Created On:  04 March 2011 Problem: You may receive the following error when attempting to access data in the LINKAGE SECTION in a called program: 114     Attempt to access item beyond bounds of memory (Signal 11)You will receive this error if you access LINKAGE data that has not been assigned correctly. For example, assume program Call1 calls program Call2. But the LINKAGE SECTION in Call2 is larger (i.e. has more characters defined) than the parameters being passed by Call1.Program Call1Working-Storage Section.01  Link-Param-1               Pic X(10).Procedure DivisionCall “Call2” Using Link-Param-1Program Call2Working-Storage Section.01  Work-Field-1               Pic x(20).Linkage Section.01  Link-Data.       05  Lnk-Data-1      &nbsp

Created On:  03 March 2011 Problem: When calling an unmanaged COBOL .dll from an ASP.NET Web Service or Web Site application an HTML error 500 is returned from the call. Resolution: ASP.NET runs under control of a Web Server, either IIS or a local file system Web Server available in Visual Studio. This Web Server is actually run as a Windows Service.In order for a call to an unmanaged COBOL .dll to be able to resolve the location of the .dll it is necessary to add the location of the .dll to the systems PATH environment variable.Example:If your web site and your unmanaged COBOL .dll are in the following folder:      C:\\inetpub\\wwwroot\\mysiteThen you need to modify the PATH to include this using Control Panel->System->Advanced Settings->Environment Variables:Change PATH to include C:\\inetpub\\wwwroot\\mysite.Because the Web Server is running as a Windows Service you will need to reboot the computer before the change will b

Created On:  10 March 2011 Problem: In C# one can use the following OR operator to do bitwise operations on flag fields.TextFormatFlags sf = TextFormatFlags.VerticalCenter |                                     TextFormatFlags.HorizontalCenter |                                     TextFormatFlags.NoFullWidthCharacterBreak;How does one do a similar thing in Visual COBOL? Resolution: The b-or operator can be used to achieve this effect as follows:In C#TextFormatFlags sf = TextFormatFlags.VerticalCenter |                    &n

Created On:  09 March 2011 Problem: Is there any traning available for Visual COBOL? Resolution: Yes. There is a web based training course available here:http://www.microfocus.com/education-services/course-catalog/courses.aspx?ComponentUri=199403&keyword=tcm:6-174766-1024It's also available as a 3 day instructor led training course, please contact your local sales representative. Incident #2506407 Old KB# 33640

Created On:  04 March 2011 Problem: An issue arose when a client was migrating an application from an older version of COBOL to Server Express. They wanted to know why the behaviour changed in Server Express for numeric fields that had not been initialized. Take the following program as an example, where no initialization is applied:WORKING-STORAGE SECTION.*SET HOSTNUMCOMPARE 01 num-fld pic 9(01). Procedure Division. If num-fld = 0    Then         Display "THEN num-fld-->["num-fld"]"    Else         Display "ELSE num-fld-->["num-fld"]"End-if.When they compiled the program to object code (i.e. .gnt, .so or executable) in Server Express, with the default compiler directives, the 'THEN' logical path was taken. This meant that the non-initialized numeric field was treated as equal to zero.But when they recompiled with the HOSTNUMCOMPARE compiler dir

Created On:  09 March 2011 Problem: In order to control the printer formatting directly using PCL codes, escape sequences, etc..., you need to bypass the Windows Printer driver. How do you do this? Resolution: You can bypass the Windows printer drivers and write directly to the printer from an RM/COBOL program by setting RAW MODE. There are three ways to do this:1. Registry configuration - Using rmconfig.exe, set the "Printer Enable Raw Mode" on the Control tab to True. 2. In a configuration file, change the Define-Device record for the printer by adding RAW=yes 3. Use the P$SetRawMode subprogram as outlined in the User's Guide. This sets raw mode only on the next printer opened, while it is open for output. If you close the print file and release the print job, the printer reverts back.**Keep in mind that using RAW MODE limits the P$ routines that you can use in the program. See the User's Guide for a list of these routines. Old KB# 33642#PCL#escapesequences

Created On:  23 February 2011 Problem: A COBOL developer wanted to obtain a compiler listing fie (.lst) including both the data cross-reference and the source code listing.  The compiler directive XREF was specified in the "cob" compilation command.   When the resulting .lst file was examined, the cross-reference was present, but the source code was not included.The "cob" compilation command specified a directives file, like so:cob -C directives=/directory-path/site/cobol.dir -C XREF -uvP helloworld.cblThe file /directory-path/site/cobol.dir was discovered to include the compiler directive ERRLIST, which was preventing the source code from being included in the .lst file.  Testing at Micro Focus showed that changing ERRLIST to ERRLIST"EMBED" would give the desired behavior, requiring no other changes to the "cob" compilation command.However, due to policies at the site, users were not authorized to modify the /dire

Created On:  23 February 2011 Problem: An issue was encountered when running Server Express on both HP-UX PA-RISC 11.11 and 11.23 whereby running the ‘anim’ command produced a core file. This error only occurred when COBMODE=32 was set. When this happened the core_on_error=1 configuration option had been set. Core_on_error had been set in order to produce a core file for a program that was abending when being started using the ‘cobrun’ command. As the program was genuinely faulty a core file was generated, as expected. However, with core_on_error=1 set they then attempted to animate a different program, which was a ‘clean’ program that did not abend. This program had previously run correctly to completion when activated using the ‘cobrun’ command and core file was produced. But, when they then tried to animate the program (anim progname), it instantly produced a core file, even though the program had previously run to completion. A core file ‘should’ only be created when yo

Created On:  23 February 2011 Problem: It's possible that when compiling a very large program you may receive the following error:Compilation error: Maximum number of data items exceeded.S* Compiling progname.cbl* 808-S                 (   0)****    Maximum number of data items exceeded.cob32: error(s) in compilation: progname.cblCompilation incomplete Resolution: This is a restriction and therefore the only option is to reduce the number of data items – as stated in the error message produced:COBCH0808 Maximum number of data items exceededThe compiled program contains more than 64,000 data items.To resolve this, eeduce the number of data items then recompile your program. The most obvious way to reduce the number of data items is to create sub programs for code and data items that can be isolated and called separately. But of course this is never a simple task with

Created On:  24 February 2011 Problem: When executing ‘cobrun A progname’ or ‘cobanim progname’ the program runs instead of passing to the animator. For example, let’s assume you’re attempting to use cobanim to animate the demo program ‘tictac’ from the $COBDIR/demo/tictac/ directory. You can activate ‘cobanim’ either directly or via the ‘cobrun A’ commands. For example the command 'cobanim tictac' or 'cobrun A tictac' runs the program (as if 'cobrun tictac' had been entered) instead of opening the animator. Resolution: When you run either of these commands, if you find that instead of activating the animator and allowing you to step through the code it runs the program exactly as if you had entered ‘cobrun tictac’, then one thing to look for is to make sure that you are not attempting to animate from the Server for COBOL (Application Server) runtime environment. You cannot animate programs from the runtime environment, you can only animate from

Created On:  16 February 2011 Problem: After installing Net Express 5.1 WrapPack 5 a compiler error is displayed for a Dialog System application that used to compile without error.The error is:COBCH0666S Reserved word used as data name or unknown data description qualifier  : and points to a copyfile (.cpb) which was generated by Dialog System that contains the following:          03 FUNCTION-DATA.             05 WINDOW-HANDLE                PIC x(4) COMP-5.             05 OBJECT-REFERENCE OBJECT REFERENCE.          *>Error points to this data item.             05 CALL-FUNCTION      

Created On:  21 February 2011 Problem: AcuSort external tool writes all execution information in a log text file called SYSOUT. Is it possible to prevent the creation of this file? Resolution: The only environment variable about SYSOUT file is "dd_SYSOUT". This setting allows changing the default name SYSOUT to a more personalized one.i.e.: set dd_SYSOUT=my-sysout-fileThis variable can be also used to redirect the AcuSort log information to a nul queue, thus avoiding the creation of an undesidered file.This is the syntax to use in any Windows environment: set dd_SYSOUT=nuland this on a Linux/UNIX platform:export dd_SYSOUT=/dev/nullThe dd_SYSOUT is an environment variable and is not recognized when set inside a runtime configuration file.If the AcuSort tool is used within a COBOL program and executed via C$SYSTEM, use this statement before the C$SYSTEM, instead:SET ENVIRONMENT "dd_SYSOUT" TO &quo

Created On:  25 February 2011 Problem: Inability to launch server application. Resolution: This error indicates the inability to launch server runtime on a UNIX server. 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. The permissions for the runtime should be executable. Old KB# 33536