Rocket® COBOL

Created On:  11 November 2010 Problem: Errors are produced when displaying signed fields in AcuXDBC. Resolution: The resolution for this is to amend the acuxdbc.cfg file and set the following configuration variable to:invalid_numeric_data truncate Incident #2484958 Old KB# 32460

Created On:  04 November 2010 Problem: When using Remote Desktop to run an ACUCOBOL-GT program on a Windows 2008 Terminal Server the print file using SPOOLER-DIRECT doesn't print.  There are no error messages but nothing comes out of the printer.  Printing using SPOOLER does print as expected. Resolution: Terminal Services Easy Print was introduced with Windows Server 2008. It is a proxy for every print action that simply redirects all printing-related work to the user's local machine without the need to install any print drivers on the Terminal Services server.  The client PC's printers are exposed to programs running on the server and are identified with "(redirected 3)" when viewing the printers available.  In that example the 3 is the Terminal Services session id.The Easy Print driver creates a print file in XPS format, then transfers it to the client PC where it is printed.  SPOOLER-DIRECT will not work with Term

Created On:  04 November 2010 Problem: Before upgrading from Runtime version 6.1 to 8.1.3, when the Unix Runtime process (runcbl) ended, the program's displays remained visible on the console.  Now with version 8.1.3 the program seems to run in a separate space and the displays vanish when the program exits. Resolution: Prior to ACUCOBOL-GT Version 6.2 the program displays from a character-based program did remain on the console after the Runtime exited, regardless of the type of display that the program did.  However in Version 6.2 a change was made to destroy all canvases when the Runtime exits.  That change was done to fix a memory leak due the canvases not being destroyed.  So in version 6.2 and later the program displays disappear when the Runtime exits, when using default display handling.The Windows Console Mode Runtime, crun32, also behaves this way.  The displays will remain on the console if all of these conditions are true:1. The

Created On:  10 November 2010 Problem: How can we restrict a cell of a Grid to accept only Numeric data? Is there any property available to achieve this? Resolution: Refer to the AcuCobol GT User Interface Programming manual, section 5.11.2 - Grid : Special Properties. This will show you how to set the Special Property DATA-TYPE, which you can apply to columns within your grid to define what type of data entry to allow and disallow. Old KB# 32454

Created On:  10 November 2010 Problem: The performance of queries on Vision files via AcuXDBC becomes slower the more concurrent queries are executed. Resolution: There are 4 variables within the AcuXDBC config file that can be set:LOCKS_PER_FILEMAX_FILESMAX_LOCKSV_BUFFERSThese are all well-documented in the Manual AcuXDBC User’s Guide.  However, what is not well-documented is that the XDBC process will inherit the spawning process’ environment, so any efficiency tweaking that can be done with variable setting within the normal config file will be reflected within the XDBC environment.  So, remember to review all the settings in the normal config file with a view to increasing performance throughout Acu products.  These are described in detail in the Manual “ACUCOBOL-GT Appendices”, Chapter “H.2 Configuration Variables”.Tip : check the setting of V_LOCK_METHOD Old KB# 32451

Created On:  04 November 2010 Problem: First, some background on .ipf files:.ipf files are created when using the Profiler facility in Server Express. This is the procedure to do that:1. Use the PROFILE compiler directive with the cob command when compiling the program. That directive can be set in a number of ways, such as usage in a directives file or by placement in the compile command after the -C flag, as in this example:    cob -xv -C PROFILE {program-name}This creates an executable which can then be used to create the .ipf file.(Note: .ipf files can also be created using .int, .gnt and .so files, not just when using executables. You would of course still use the PROFILE compiler directive as indicated in the compile commands used to create the .int, .gnt and .so files).2. The .ipf file is then created when you run the program:    cobrun {program-name}This results in a .ipf file being created in your current working directory. 

Created On:  01 November 2010 Problem: Mapping a shared drive on a Windows server either 2003 or 2008 to access a SQL server 2005, user can get a 9D,4060, which is the following SQL server error:42000 4060 - Cannot open database "db-name" requested by the login. The login failed. Resolution: The user must have the following variable added to the configuration file:  A_MSSQL_DEFAULT_CONNECTION Server-name Incident #2484619 Old KB# 32384

Created On:  11 November 2010 Problem: Acuserve start fails and the system returns this error message: "Unable to add user". Resolution: This error message is generated when acushare is not running and cannot be started.  Usually, acushare starts automatically when acuserver or acurcl are launched. If Acushare crashes for any reason, its shared memory queue may become corrupt which will prevent acushare from being able to restart.To solve this situation, Acushare clean must be executed before starting AcuServer, AcuConnect or executing other processes that require Acushare. Incident #2485786 Old KB# 32444

Created On:  29 October 2010 Problem: Receiving errors such as read-only files or "General File Transfer Error... ERR -3". Resolution: These are either a permissions error (make sure you have full access to the MicroFocus\\EnterpriseLink directory and it's children) or your AntiVirus/Firewall software might be preventing you from updating these files. Old KB# 32353#Rumba#EnterpriseLink

Created On:  29 October 2010 Problem: Python scripts do not seem to execute. There is no smartscript-stderr.log or smartscript-stdout.log created in the EnterpriseLink\\logs directory. Resolution: This is most likely a permissions issue. The userid that IIS (Internet Information Services) is running under (normally "Network Service") needs to have read/write access to the directories under the MicroFocus\\EntepriseLink directory.  The Python compiler needs to compile the source modules and create the compiled output (.pyc files) in these directories. Old KB# 32352#Rumba#EnterpriseLink

Created On:  29 October 2010 Problem: We want to deploy a Visual COBOL application on a network server and be able to have users running workstations on the network be able to run the application without the need for the COBOL 2010 Runtime product to be installed locally on each workstation. In Net Express this could be done by setting the environment variable ASLMFNET on each workstation to point to the location of the license database file on the server computer. Resolution: For managed code .NET applications the COBOL 2010 Runtime product needs to be installed on each workstation.For unmanaged native Windows applications you can set this up as follows:1. Install your application on the desired server computer.     For this example we will say that it is installed on:    -  //ServerA/appfolder    It must be accessible by the workstations that will be running the application.2. Install the COBOL 2010 Runtime product on

Created On:  29 October 2010 Problem: When using Net Express 5.1 or 6.0 in Windows 7 and moving the compiled files to a network drive, a runtime error 173 could show. Something like:Load error:file 'ADIS'error code:173, pc=0, call=1, seg=0173 Called program file not found in drive/directoryLocally all works ok, in Windows XP locally or from a network drive the same program runs normally. Resolution: Open the regisrty editor and go to the following keys and remove the " symbols.The fix for this is to make a few registry changes to handle this:-  HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Micro Focus\\NetExpress\\5.1\\Dialog System\\5.1\\Environment • Remove the “ (quotes) from the PATH setting HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Micro Focus\\NetExpress\\5.1\\Unix\\Environment   • Remove the “ (quotes) from the PATH setting The above keys are on a 64bit machine. You will need to remove the “Wow6432Node” for a 32bit machine. Incident #2

Created On:  19 October 2010 Problem: While installing AcuXDBC on 32-bit or 64-bit Windows, the installation appears to hang after the completion of 80% of the installation. Cancelling the installation allows the license activation screen to appear, but only the license file is found in the installation directory. Resolution: On Windows 7, Windows Server 2008, and Windows Vista check the status of User Account Control (UAC). UAC may need to be modified or disabled for the product to fully install. However, it should also be noted that permissions issues may persist even if UAC is not a consideration if the systems administrator has restricted access to users. Additionally, installations issues may arise if the user performing the installation is not a member of local machine administrators group or due to the activity of antivirus or other software. Incident #2444975 Old KB# 32112

Created On:  11 November 2010 Problem: After upgrade from 8.1 to 8.1.2 AcuServer crashes although the system remains unchanged apart from the update (sometims 9D103).  The server is Win2K-R2 SP2 with all patches, clients are Windows XP and Vista. Resolution: To resolve this, complete uninstall and then re-install. Incident #2448984 Old KB# 32166

Created On:  21 October 2010 Problem: This article details the differences between a ‘typical’ and ‘complete’ install in Rumba 8.0 Resolution: A Rumba 8.0 typical install excludes the following components: 1. The Rumba Menu Configurator. This utility is normally installed only on an Administrator’s machine and provides a method for modifying menus in legacy Rumba profiles. 2. The Profile Editor and documentation. This includes sample applications for the Profile Editor, which can be used to programmatically modify selected options in legacy Rumba profiles. 3. Legacy API support. This includes header files and high-level documentation for the legacy APIs, primarily HLLAPI. These items can be installed by selecting a ‘complete’ install, or selectively installed using the ‘custom’ install option and manually selecting each feature. Incident #2442805 Old KB# 32201#Rumba

Created On:  25 October 2010 Problem: Net Express 5.1 is installed on a 64-bit Windows system. If I develop my applications as 64-bit does this allow for larger indexed file sizes? Resolution: Net Express 5.1 supports the development of both 32-bit and 64-bit systems.The 32-bit components are always installed.The 64-bit components are only installed if the installer detects that a 64-bit OS is running.In the case that a 64-bit system is found then the folder:C:\\Program Files (x86)\\Micro Focus\\Net Express 5.1\\Base\\Bin\\WIN64 will be created which contains the 64-bit components andC:\\Program Files (x86)\\Micro Focus\\Net Express 5.1\\Base\\Lib\\WIN64will be created which contains the 64-bit version of the import libraries for linking.In addition a 64-bit Net Express command prompt will be available and a 64-bit check box will be available on project->properties.---------------------------------------File handling limitations have absolutely nothing to do with 32-bit

Created On:  22 October 2010 Problem: When using the Net Express IDE to generate client programs for a COBOL Web Service, the build might report errors like the following when attempting to build the clients for Winform and Webform programs.WSCalc-app.cblWSCalc-proxy.cblConsole client and proxy generation completedWSCalcProxy.dllcalcInput.cblcalcOutput.cblWSCalcHelper.dllWSCalcIntf.cblWSCalcIntf.dllWSCalcMain.cblWSCalcForm.cblWSCalcForm.Designer.cblWSCalcApp.exeWSCalc.aspxWSCalc.aspx.cblWSCalcProxyWrapperTrigger.cblWSCalcProxyWrapper.cblWSCalcProxyWrapper.tlbWSCalcProxyWrapper.tlb>>> Error executing program 'C:\\WINDOWS\\System32\\cmd.exe'c:\\WS_acctdemo\\WS_acctdemo\\Client\\WSCalc\\ProxyWrapper>set include=C:\\Program Files\\Micro Focus\\Studio Enterprise Edition 6.0\\Base\\INCLUDE;%INCLUDE%;c:\\program files\\micro focus\\studio enterprise edition 6.0\\base\\include ...midl : command line error MIDL1005 : cannot find C preprocessor cl.exeC:\\WINDOWS\\

Created On:  22 October 2010 Problem: This article describes the two Add-on components of Rumba 8.0: the TP Director and the Script Engine. Resolution: The Script Engine adds a VB-like scripting capability to the Rumba Display that allows script to be written that interact with the display. Scripts can do everything that macros typically do, but add the flexibility of a BASIC syntax and a lot more functionality. For example, Scripts can have more complex decision logic, manipulate files, create other applications objects, set timers, Pop up custom dialogs, and more. The trade off is that scripts are generally much more complex and require a knowledge of the language syntax, while macros are simple for most end users to create and use. The TP Director is a special utility that allows APPC programs to run correctly when one of the connection partners is running in a multi-user environment such as Windows Terminal Server. Since the APPC node is always the same for a client PC,

Created On:  19 October 2010 Problem: After installing and configuring the AcuXDBC client, the next step is to create a Data Source Name (DSN). This is done using the Windows ODBC Data Source Administrator dialog. However, clicking on the “Drivers” tab does not show an entry for the AcuXDBC driver (ACUXDBC.DLL) when the client machine is a 64-bit Windows system. Resolution: On 64-bit Windows systems, the default Windows ODBC Data Source Administrator is C:\\Windows\\System32\\odbcad32.exe which does not have an entry for the AcuXDBC driver. There is a second instance of the Windows ODBC Data Source Administrator (odbcad32.exe) located in the C:\\Windows\\SysWOW64 directory that has the expected entry for the AcuXDBC driver. Incident #2353020 Old KB# 32117

Created On:  20 October 2010 Problem: 4GL_WHERE_CONSTRAINT is an environment variable used to restrict the result of a query run on a database. In some situations it is very useful to improve performance. It can be declared in the cblconfi, or it can be set programmatically with a SET ENVIRONMENT statement. As soon as the START statement is executed, the 4GL_WHERE_CONSTRAINT appears empty and needs to be set again. Is this an expected behavior? Resolution: It is correct that the Acu4GL interface blanks out the variable after use, either this was set in the environment or in the program. This is useful (and explicitly requested) to limit the action of the WHERE-CONSTRAINT itself to the single following START. In the most common scenario, an application works on different database tables alongside with Vision files. A new operation on data that needs a new START would use probably wrong information. To avoid it, 4GL interface blanks aut

Created On:  21 October 2010 Problem: When using Micro Focus Net Express or Visual COBOL products for .NET managed code applications how does one determine which version of an assembly should be used when adding a project reference in the Visual Studio IDE?If multiple products are installed, such as Net Express 5.1 and Visual COBOL then multiple versions of assemblies such as MicroFocus.COBOL.Runtime, will be installed. Resolution: Each product version uses a different set of version numbers for the NET assemblies for its run-time files.Net Express 5.0                    Visual Studio 2005     MicroFocus.COBOL.Runtime 2.0Net Express 5.1                    Visual Studio 2008     MicroFocus.COBOL.Runtime 3.5Studio Enterprise Edition 6.0 Visual S

Created On:  19 October 2010 Problem: Although the Micro Focus Database Connectors User’s Guide documents the availability of the A4GL-WHERE-CONSTRAINT it has not yet been fully implemented. Resolution: Currently, the full implementation of the A4GL-WHERE-CONSTRAINT is scheduled for version 5.1 WebSync 4 (WS4) for Server Express and 5.1 WebSync 5 (WS5) for Net Express. Incident #2285746 Old KB# 32118#ServerExpress#netexpress#AcuCobol#COBOL

Created On:  21 October 2010 Problem: When trying to install a version a Net Express 5.0 or 5.1, the install reports the error:Execution error: file "   error code: 144, pc=0, call=1, seg=0  114  Attempt to access item beyond bounds of memory (Signal 11)But then the installation appears to finish alright.The same error can also occur when trying to start the Net Express IDE. Resolution: This error can happen if they have a Source Code Control System installed and it is not setup properly.The installation looks in the registry to find out the location of the Source Code Control interface DLL.It will then try to load it and initialize it.It is this initialization that is failing and it causes the IDE to display the reported error. If they are using the Source Code Control System installed, then the DLL supporting the Microsoft Common Source Code Control Interface isn’t working.This is most likely because the Source Code Control Sys

Created On:  20 October 2010 Problem: Within an AcuCobol form, you may wish to use Windows standard cut/copy/paste commands ctrl-c, ctrl-v, etc. Resolution: On the configuration file you position this (for example):KEYSTROKE EXCEPTION=1001 ^CKEYSTROKE EXCEPTION=1002 ^XKEYSTROKE EXCEPTION=1003 ^VAnd then on your program you set this SET EXCEPTION 1001 TO COPY-SELECTIONSET EXCEPTION 1002 TO CUT-SELECTIONSET EXCEPTION 1003 TO PASTE-SELECTION Old KB# 32130

Created On:  06 January 2011 Problem: Under Linux glibc 2.3, Acu-Version 7.2.0 the error 30;21 comes up. What does it mean? Resolution: Returncode "30" is described with "Permanent operation system error". The definition for the HP Unix Errno Code 21 is:#define EISDIR 21 /* Is a directory. Incident #2480091 Old KB# 32163