Rocket® COBOL

Created On:  19 October 2011 Problem: When testing the record lock behavior in a Visual COBOL application that is accessing RM/COBOL indexed files, I find that the behavior is different than that of RM/COBOL.  In RM/COBOL when I try to access a record that is currently locked by another program, the read will wait until the lock is released before returning to the program.In Visual COBOL accessing a locked record returns immediately with a locked record file status.  How can I change this behavior? Resolution: You can change this behavior so that it works like the default RM/COBOL behavior by using the RM directive in addition to the CALLFH("ACUFH") directive to compile the program.  Then if a locked record is attempted to be read in a second program it will automatically wait until the record is released by the program holding the lock.You can also use the RETRYLOCK directive instead of the RM directive

Created On:  24 October 2011 Problem: When attempting to animate a program from within a project open in the Net Express IDE by double-clicking on the program name or selecting Start Animating option from the Animate menu, the Animator never opens the programs source but instead simply displays a command prompt window.The program doesn't appear to be running and the only thing that you can do is close the command prompt which stops the Animation.  Why does this happen? Resolution: This problem can occur if your PATH or COBDIR environment variables contains a folder name which has an older copy of the COBOL run-time cblrtss.dll in it. If this older copy is picked up during the Animation process then the Animation will fail as described here.Always ensure that you do not have multiple copies and different versions of cblrtss.dll on your computer, especially in your project folder.If you have multiple versions of Net Express installed on the same computer then th

Created On:  18 October 2011 Problem: For Visual COBOL R4 Update 2 and R5 a new version (8.4) of the SafeNet licensing software will be used.  For local servers there is nothing to worry about as we will be installing a new client (Visual COBOL) and a new server on the same machine.  However, if you have a network server you should update that first as new clients (on 8.4) cannot talk to old license servers (on 8.2). Resolution: The new version of the license server software should be available for download nearer the time from the SupportLine web site at: http://supportline.microfocus.com/websync/SLM.aspx. Old KB# 34956#COBOL

Created On:  18 October 2011 Problem: I am having problems accessing SQL Server on a remote server on the network. Resolution: If you are running the AcuSQL interface to Microsoft SQL Server, you must have the SQL Server client software from Microsoft. To see if the SQL Server client software from Microsoft is on your system, Open the Query Analyzer. (For information on opening the Query Analyzer see SQL Server client documentation.) If the Query Analyzer opens and you are able to connect to the database, the client libraries are most likely all present. Your SQL Server data source may be hosted on one (or more) of the following environments: So now you should be able to access the server on the network....Ensure that you set - ACUSQL_RUNTIME_DLL to asqlsrvr.dll**  asqlsrvr.dll is the DLL specifically for connecting to MSSQL.** esqllib.dll is not supported for connecting to MSSQL.When using asqlsrvr.dll the CONNECT statement must specify the MSSQL Server, rather t

Created On:  10 January 2012 Problem: It appears that the Acu XDBC 64bit server can be selected when doing a Windows install, but the modules do not get copied onto the machine. Resolution: AcuXDBC does get installed on the machine, but gets installed into the default location of "C:\\Program Files\\Micro Focus\\Acucbl910\\AcuGT\\bin\\". If you want the files in another location there are five steps you need to perform to be able to use 64-bit AcuXDBC from the new location. The steps require that you have administrator rights to the local machine. 1. Copy the files from "C:\\Program Files\\Micro Focus\\Acucbl910\\AcuGT\\bin\\" to .2. Set GENESIS_HOME= .3. Change the properties of XDBC Query 64-bit shortcut so the target now points to .4. Run regedit and locate the HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI\\extend9 AcuXDBC (64-bit) entry. The Driver and Setup keys need to be changed to the following: Driver=\\bin\\acuxdbc.dllSetup=\\bin\\AcuXDBCSet

Created On:  21 October 2011 Problem: Are ACU runtime and other programs of the suite extend 9 compliant with Windows 2000?These are some of the problems encountered during an installation of 9.1.0 on a Windows 2000 Server:- InstallShield Wizardextend(R) Version 9.1.0 requires that the following requirements be installed on your computer prior to installing this application. Click Install to begin installing these requirements: MSXML 6.0 SP1- InstallShield 1210: Setup requires Windows Installer version 3.0 or higher to install the Microsoft .Net Framework version 2.0.- dotNetFx40_Full_x86_x64.exe is not a valid Win32 application.- acuthin.exe is not a valid Win32 application. Resolution: Windows 2000 is not supported with extend suite 9.x.The supported Microsoft Operating Systems for 9.x are:Windows XP, Windows Vista, Windows 7, Windows 2003, Windows 2007, Windows 2008 R2. Incident #2542799 Old KB# 34993

Created On:  19 October 2011 Problem: Is it possible on a system with dual monitors to determine and ensure which screen the output appears on? Resolution: Since the Runtime was never developed with dual monitors in mind, the output will always be displayed on the primary monitor. There isn't any other option. Since changing this would require enourmus efforts, an enhancement is not likely. Incident #2542225 Old KB# 34962#primary#output#dualmonitors#screen#runtime#ACU

Created On:  21 October 2011 Problem: The program uses a line sequential file with fixed length records.  However, when writing records to the file the trailing spaces are removed.  For this application the trailing spaces are necessary and should not be removed.  Why are the trailing spaces removed? Resolution: Print files always have trailing spaces removed.  Somewhere in the program there is a WRITE statement that includes the ADVANCING phrase.  Even though this file is not specifically defined as a print file, the ADVANCING phrase causes it to be handled as a print file.  Removing the ADVANCING phrase from all write statements for this file will resolve the issue. Old KB# 34999

Created On:  25 October 2011 Problem: Since the release of extend version 8.0, Micro Focus released a 64-bit Windows native port for the extend product suite. The new installer for this port can lead to some misunderstandings about installation paths. Resolution: Usually, all Windows 64-bit programs are installed under "C:\\Program Files\\" while 32-bit programs are installed under "C:\\Program Files (x86)\\".Launching a 64-bit setup installer provides an option to select a different path where Acu product will be installed. A "Path" field can be filled to provide the new directory path.The path you provide will be the location for 32-bit libraries only. All 64-bit libraries will be placed under "C:\\Program Files", regardless of the drive and path chosen in the Path field.For example, if you choose to install Acu products on drive D:\\, you can enter this location in the Path field:D:\\Program Files (x86)\\Acucorp\\Acucbl811 This wil

Created On:  21 October 2011 Problem: After the installation of runtime 9.1.0, no bitmap or jpeg image is displayed inside the application.  W$BITMAP returns an invalid handle. Resolution: This is caused by the lack of the correct library inside extend setup 9.1.0 for Windows 32-bit.  Either copy the missing library ajpg32.dll from an existent 9.0.1 installation, or extract the attached zip file into the newly installed 9.1.0 BIN directory. Incidents #2542782, #2542215 Attachments ajpg32-901-32bit.zip Old KB# 34988

Created On:  17 October 2011 Problem: While running AcuXDBC you get an error message, for example: Too many columns 369 (max:256) Resolution: You can increase this limit by modifying the DSN that was created for the AcuXDBC data source. See Chapter 5.8.3 AcuXDBC Setup: Advanced Tab of the AcuXDBC User's Guide for more information: Here are some limits to be aware of that are imposed by Microsoft: Excel: Worksheet size 65,536 rows by 256 columns column width 255 characters. Access: Number of fields in a table 255 Old KB# 34945#ToomanyColumns#AcuXDBC

Created On:  19 October 2011 Problem: How do you change the text item of a tree view control? Resolution: In version 9.0.1 there is an enhancement that enables the user to change the text of a tree-view item. This feature is controlled by a new runtime configuration variable TV_EDITLABELS. When this variable is set to "1" (on, true, yes) you can change the value of the tree-view item by clicking it with the mouse (just like with Windows Explorer). When the variable is set to "0" (off, false, no) text changes are not allowed. The default value of TV_EDITLABELS is "0". To keep track of the changes, two additional messages are generated from the tree-view to the COBOL program: MSG_TV_BEGINEDITLABEL and MSG_TV_ENDEDITLABEL. MSG_TV_BEGINEDITLABEL is sent to the COBOL program when the user begins the edit. EVENT-DATA-1 is always 0, and EVENT-DATA-2 contains the handle of the item being modified. The program can prevent the modification by setting EVE

Created On:  25 October 2011 Problem: When compiling in Net Express for Eclipse you get an error message indicating:109     Your product license has expired Resolution: Even though your Eclipse addpack may be fully licensed, this error message is shown when your Net Express product is not licensed or the license key has become corrupt.You will need to apply a valid license to Net Express to be able to compile using Eclipse.To do this you will have to send the 24 digit Request Key to supportline@microfocus.com and you will then receive a Response Key once it has been processed. Incident #2541676 Old KB# 35015#COBOL

Created On:  18 October 2011 Problem: In specifically the Linux environment, we encounter the following error transaction error 05, 02 when invoking a program that contains rollback functionality. Resolution: This is the breakdown of the error codes 05,02 you are receiving: 05 This indicates an operating system error that is not otherwise covered by one of the standard error conditions.  You can determine the exact nature of this error by examining the value of the secondary code.In Linux the secondary codes are held in errno.h (/usr/include/asm/errno.h). The code equates to - #define ENOENT 2 /* No such file or directory */You can find out more details by running a trace for example: - runcbl –c config.cfg –lxe error.log program Old KB# 34955#AcuCobolLinuxError

Created On:  24 October 2011 Problem: Application runs on the mainframe, using DB2 for Z/OS.The application is using the following SQL command on a dynamic statement:  EXEC  SQL                                                    PREPARE  SEL FROM  :STMTBUF                          END-EXEC.                                                 MOVE  3

Created On:  21 October 2011 Problem: After the installation of extend 9.1.0 on a Windows machine, an error occurs executing wrun32.exe (or acuthin.exe).The windows popup reports: wrun32.exe - Entry Point Not foundThe procedure entry point CLRCreateInstance could not be located in the dynamic link library mscoree.dll.The same message on an Italian operating system reports:wrun32.exe - Impossibile trovare punto di ingressoImpossibile trovare il punto di ingresso CLRCreateInstance della procedura nella libreria di collegamento dinamico mscoree.dll. Resolution: extend 9.1.0 requires .Net Framework 2.0 and 4.0.Check which version of .Net is installed on the machine and eventually install the missing Framework.I.e.:C:\\Windows\\Microsoft.NET\\Framework\\v2.0.50727C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319This error will be fixed in upcoming release 9.1.1.The DLLs will no longer link with mscoree.dll, and instead will load it dynamically when it is needed.(only in thi

Created On:  17 October 2011 Problem: How do you find in Acu4GL for MSSQL the unique SQL spid (process id)? Resolution: You can view the SPID in MSSQL using Activity Monitor etc or try using the function below.ACUCOBOL-GT Appendices Version 9.0.1 Appendix I: Library Routines > I.1 General Syntax and Library List > C$GETPID This routine returns the Process ID (PID) of the current process. This PID can be compared with the PID returned by the C$LOCKPID to determine if the current process is the one holding a file lock or record locked condition. Usage CALL "C$GETPID" GIVING PROCESS-ID. Parameters PROCESS-ID PIC 9(n) This contains a numeric data item large enough to hold a PID. On most platforms, PIC 9(5) is sufficient. On 64-bit systems, PIC 9(7) is recommended. Comments When called from a non-UNIX or non-Windows runtime, C$GETPID returns a PROCESS-ID of "0". This behavior should not be used for system identification. Use ACCEPT ... FROM SYSTEM-INFO

Created On:  21 October 2011 Problem: The users would like the date entry control to initially display blank but even when the "SHOW-NONE" style is applied the control displays the current date.  What is required to make the date entry control display a blank date? Resolution: Assigning the show-none style only affects the value that the control RETURNS when inquired on. If the check box is unchecked then inquiring the value will return zero for a date and all 9s for a time.  The control still must display a valid date.  Show-none does not affect the value displayed. The date entry control is actually an implementation of Microsoft's calendar control which must always display a valid date.  It cannot display a blank date as blanks are not a valid date.  When the date entry control detects a value that is not a valid date then it displays the current date.  This behavior cannot be changed.Note that most GUI applications have this b

Created On:  11 October 2011 Problem: How do you access windows printers from UNIX? Resolution: When we print on UNIX, we send the data to a device on UNIX and it is UNIX that does the printing. We send the printing to lp and it prints it.To make this work you need to set up the UNIX machine and the Windows machine, and once you are able to print from the command line on UNIX, you will be able to print from our runtime. The problem is a system issue and nothing to do with the runtime.Here is a link that talks about the configuration you need to setup:   http://support.microsoft.com/kb/324078 Old KB# 34898#AcuCobolPrinters

Created On:  07 October 2011 Problem: Calling the RM/COBOL subroutine, C$Century, in Visual COBOL (R4) does not return a value to the USING argument. Resolution: The following compiler directive has to be set in order to enable the C$Century call to return a value:RM "GIVING" Incident #2540577 Old KB# 34860#VisualCOBOL#RMCOBOL#Enterprise#COBOL

Created On:  07 October 2011 Problem: When running the runtime product Server for COBOL or Server Enterprise Edition the Micro Focus License Manager does not appear to want to start again.  When attempting to restart the Micro Focus License Manager service via the Control Panel, the following message is returned:"The Micro Focus License Manager on local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs" Resolution: The message is coming from mflmwin (Micro Focus License Manager). For some strange reason the machine gets into a state where the License Manager will not start. Due to the anti-hack code in the License Manager the only solution is to restart the machine in order to clear the processes and shared memory. Incident #2540805 Old KB# 34862#Enterprise#COBOL

Created On:  11 October 2011 Problem: I am having problems clarifying the results from the Profiler. Resolution: The ACUCOBOL-GT profiler is a sampling profiler, which means that it wakes up at regular intervals, and attempts to figure out what is executing at that moment. As such, the numbers reported are very rough estimates. And we have found that paragraphs with only CALL statements are not particularily good for such sampling.ECN 3441 offers more information about profiling, in particular a configuration variable that may allow more accurate profiling in some situations. SUBJECT: Profiling COBOL on WindowsChange Number: ECN-3441Status: CompleteType of Change: EnhancementPriority: MediumIncidents: NoneDate: 2006-04-05Product: ACUCOBOL-GTModule: runtimeNew Version: 8.0.0Machines Affected: WindowsKnown Versions Affected: All with profilingDESCRIPTION of problem or enhancement:The method we used to set a periodic timer on Windows (in order to profile COBOL progra

Created On:  11 Ocrober 2011 Problem: We installed Net Express 5.1 on a Windows 7 computer.  When clicking a screenset file with extension .gs in the IDE the following error occurs:Load error: file 'dspaint' error code:173, pc=0, call=1, seg=0 173 Called program file not found in drive/directoryA similar error occurs when trying to run a Dialog System application in the IDE on the call to DSGRUN. Resolution: This is a known issue with Net Express 5.1 and Windows 7.On Windows 7 the quotes that are placed around the PATH settings in the Net Express or Server for COBOL 5.1 registry settings is causing the PATH to be invalid so the search for DSGRUN and DSPAINT fails.The workaround is to remove the quotes from the PATH settings using regedit.There are two locations that need to be modified.The key names will depend on if this is Windows 7 32-bit or 64-bit.--------------------------------------------The fix for this is to make a few registry changes to handle t

Created On:  06 October 2011 Problem: How do I tell what exact version or update level of Visual COBOL is installed? Resolution: You can look in two locations under Windows.  Open Visual Studio 2010 and Sekect Help > About Microsoft Visual Studio.1.3.00046 indicates base release of Visual COBOL R4.1.3.00047 indicates R4 Update 1 release of Visual COBOL.You can also look in Control Panel > Programs.  Click on View Installed Updates link to see what Update level your product is at: Old KB# 34850

Created On:  10 October 2011 Problem: From v9.0 onwards there is no requirement to link the Runtime System in Acu4GL for Oracle. Resolution: It will pick up the file automatically (making life MUCH easier). You need to check to see if the files required by Acu4GL/Oracle are present. You can do this with the command: "ldd coba4ora64.so" for example or "ldd coba4ora32.so" in the 32 bit environment.Example machine, check the following: /lib directory > export LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH /lib directory> ls *ora* coba4ora64.so Makefile.ora /lib directory> ldd coba4ora64.so libfsi264.so => ./libfsi264.so (0x00002b410d66e000) libaxml64.so => ./libaxml64.so (0x00002b410d788000) libacvt64.so => ./libacvt64.so (0x00002b410d8c9000) libaregex64.so => ./libaregex64.so (0x00002b410d9dd000) libvision64.so => ./libvision64.so (0x00002b410dadf000) libacme64.so => ./libacme64.so (0x00002b410dc22000) libcobacme64.so => ./libcobacme64.so (0x00002b4