Rocket® COBOL

Problem: A web browser control has been added to a screen. The web browser control displays a web page that requires some information to be keyed in and a "submit" button to be clicked. Some users prefer not to use a mouse, but when the button is selected, it doesn't recognize the "ENTER" key. It seems it only recognizes a mouse click. Resolution: Add the "USE-RETURN" style to the browser's screen section definition.  In AcuBench, add it manually in "Additional Properties". The USE-RETURN style allows the enter key to be active on the web page being viewed.  Pressing enter shouldl submit the form. Old KB# 3175

Problem: When executing a write on one specific table MSSQL raises an error "Invalid character value for cast specification" and the program halts with file status 9D,00 Resolution: The error occurs when the data does not match the database definition for that column.  Specifically in this case the problem was due to a file that contained multiple record formats.   To correctly handle multiple record formats add the WHEN directive to the FD to cause the XFD to be generated in a way that the database will recognize multiple record formats.  For example, the following file definition has three distinct record formats each identified by a separate WHEN directive:        FD  SAMPLEFILE.       $XFD WHEN REC-01-TYPE<5        01  REC-01.           &n

Problem: What steps should be followed to deploy AcuXDBC Server to end users using Windows clients? Resolution: Client side considerations 1) Install the AcuXDBC client on the end users Windows machines 2) Activate the AcuXDBC client licenses 3) Create a DSN to point the AcuXDBC Server Server side considerations 1) Install AcuXDBC Server on the target server platform 2) Activate the AcuXDBC Server license 3) Modify the AcuXDBC Server configuration file (acuxdbc.cfg by default), if necessary 4) Create a new system catalog or copy an existing* system catalog to the location specified in the AcuXDBC Server configuration file 5) Start AcuXDBC Server *Note: If an existing system catalog is being copied to another system, please see Knowledge Base Item 25896 or refer to Section 5.3 of the AcuXDBC User's Guide Version 8.0. Old KB# 3154

Problem: If an XFD file has been updated and it has already been loaded into the system catalog (syscat), is it necessary to delete the syscat and recreate it from scratch? Resolution: Although, the syscat can be deleted and recreated from scratch, this is not always convenient to do so. Since each XFD is represented as a table in the syscat, a "drop table" command can be issued to drop the corresponding table using the asql.sh script or directly through the xdbcquery utility. Once the drop has been completed, use the addfile.sh script or use the xdbcutil utility to add the modified XFD to the existing syscat. Old KB# 3155

Problem: If the WITH ENCRYPTION phrase is used, vutil won't extract information, but can encrypted files be viewed by tools such as ALFRED? Resolution: ALFRED is capable of reading files with encryption. For further information on ALFRED may be found at: ACUCOBOL-GT User's Guide Version 8.0 Chapter 3: Debugger and Utilities > 3.5 Acucorp's Indexed File Record Editor (alfred)   Old KB# 3179

Problem: Applied the Citrix Hotfix Rollup Pack PSE450W2KR02  for Citrix Presentation Server 4.5 ACUCOBOL-GT v 5.2.1, 6.0.0 & 6.1.0 all worked with the new citrix patch. ACUCOBOL-GT v7.1.3 using acuthin from the citrix server to connect to a Sun Solaris 5.8 UNIX box gave the error message: - acuthin.exe - Application Error The application failed to initialize properly (0xc06d007e). Click on OK to terminate the application. Once the system had been rolled back to pre citrix fix all was OK again. ACUCOBOL-GT v 5.2.1, 6.0.0 & 6.1.0 all worked with the new citrix patch it was just 7.1.3 that gave the error message. Resolution: This is a Citrix issue: - The 'application failed to initialize properly' tend to happen before any code is executed (i.e. Windows has a problem starting the app). Go to the following site which outlines the problem:- http://support.citrix.com/forums/thread.jspa?forumID=137&threadID=101062&tstart=0 The recommendation to

Problem: Typically ACUCOBOL-GT files can be moved from one system to another without any issues. Is the same true of the system catalog (syscat)as well or are there exceptions? Resolution: AcuXDBC User's Guide Version 8.0 Chapter 5: Installing AcuXDBC > 5.3 Creating a System Catalog and Views If there are plans to port the system catalog to multiple hardware platforms, be aware of the byte order format for both the machine on which the system catalog was created on and the deployment machine. The machine's byte order format is commonly referred to as big endian or little endian. A system catalog created on a machine that uses little endian (Intel for example) will not be portable to a machine that uses big endian (Motorola for example). In this case, it will be necessary to create a system catalog once on each type of machine (big endian and little endian) and then port the appropriate catalog to the appropriate target machine.

Problem: An attempt was made to modify Vision data by an update query executed on a linked table in MS Access via AcuODBC.  The error returned was:   Update on linked table xxxx failed.   [Acucorp, Inc.][AcuODBC Driver][ISAM][No data found (#1). Resolution: This error is seen when attempting to update data in a key column.  The data in the key has changed so the SQL processor can no longer locate the row to be updated.  The result is the error "No data found". Key columns cannot be modified.  The correct way to handle it would be to insert a complete new row with the desired data, including the new key data, and then delete the old row. Old KB# 3094

Problem: The application is multi-threaded with the threads communicating via messaging (SEND, RECEIVE).  After running for a certain period of time the application halts and the Runtime reports "Deadlock in messaging system". Resolution: The deadlock message appears in two scenarios: 1. Two threads are waiting for messages from each other. 2. All threads are waiting, either for messages or for space in the message queue. The message queue is dynamically resized, as needed, to hold large messages. However, it is not resized to hold multiple messages (instead, the sending threads wait until the queue empties).   It is likely that messages are being sent by one thread but are never received by another.  Perhaps threads are stopping without processing their messages, stranding those messages in the queue.  When this happens, the message queue eventually fills up and messages can no longer be sent until the

Problem: A user is trying to create a custom daemon process that invokes a COBOL program from a C program.  The C process listens on a port for incoming socket communication.  When a new request is received, the C process invokes the Solaris fork() system function to spawn a child process. That child process parses the information read from the socket and calls another C function.  Within that C function calls to acu_initv() and acu_cobol() functions are made to run a COBOL program.  When the COBOL program returns, the child process sends a response back to the client and the child process ends.   These steps work fine for a period of time.  Eventually, however, one of these child processes will hang.  It appears to get stuck in acu_initv(). Resolution: There was an infinite loop in the socket layer code between the runtime libraries and AcuShare that causes this behavior. ECN-3836 whi

Problem: Questions related to  AcuXDBC on 64-bit systems. 1) Does it work on a 64-bit pc?   2) Are there any 64-bit systems that do not work? 3) Are there any changes that must be done? 4) Are there any differences between how AcuXDBC work on 32-bit systems versus 64-bit systems? 5) Are there any known problems experienced wiith 64-bit systems and AcuXDBC? Resolution: 1)  AcuXDBC is supported on 64bit from V7.4 onwards through V8.0. 2) AcuXDBC (Client) is only available as a 32 bit binary. 3) AcuXDBC will install and work on a 64 bit PC but will install and work as a 32 bit. 4) There are no differences between the 64 and 32 bit versions as it only works as a 32 bit. 5) There are no known problems although people taking 64 bit are mentioning Windows Vista which has more security. Old KB# 3151

Problem: The error message was encountered when opening a file. The progam opened files as expected until the 17th (33rd for Vision 3) file was opened or the program was only able to open a lesser number of files than had previously been accessible. Resolution: Modify MAX_FILES in the runtime configuration. --------------------------------------------------------------------------------------------------------------------- ACUCOBOL-GT Appendices Version 8.0 Appendix H: Configuration Variables > H.2 Configuration variables > MAX_FILES This variable sets the maximum number of files that can be opened by the runtime system. The default value is "32". Keeping this value small conserves memory. Many operating systems limit the number of files that can be opened by a single process, so you may have to make some adjustments there too. The maximum value of MAX_FILES is 32767. -----------------------------------------------------------

Problem: Application invokes a call to sql.acu to set user to specific value and receives a -1 return code when trying to run the executable with the OCI version of Acu4GL for Oracle. Using Oracle's automated login capability works correctly with older, non-OCI, version of Acu4GL for Oracle. Resolution: In earlier versions of Oracle's OCI interface, it was possible to use OS Authenticated Logon (commonly known as OPS$ logon) using the OCILogon function. In later versions of their OCI interface, they removed this ability.  This would result in the user enncountering an error 9D,1017 which has the definition "ORA-1017: Invalid Username and Password.". The ability to use OS Authenticated Logon has been restored in version 8.1.0 by using the more complex login procedures and credentials in the OCI interface. Please note in later versions of the Oracle database software, OS Authenticated Logon must be turned on.  By defa

Problem: Trying to migrate a large project using the GUI (HTML) Migrate interface from the Admin page and after a while the screen goes blank or you receive a CGI Timeout error. Resolution: This is a known problem where the migrate operation takes longer than the CGI timeout set on the web server.  Once this timeout is encountered, the web server kills the migrate process as it thinks it's no longer responding. For large projects, it is suggested to use the command-line migrate tool. The syntax is: migrate [-b] project-name [from-repository] [to-repository] -b is used for backward compatibility when migrating from an old (v3.x) elink database. project-name: The name of the project you want to migrate from-repository: The name of the source repository (ex. ELRepository) to-repository: The name of the target repository (ex. ELMasterRepository) Old KB# 3104#EnterpriseLink#Rumba

Problem: When trying to use any of the features in the Web Author's pages: Could not connect to database ELRepository with user and password ; returned -1. Database Error: SQL Error State:S1000, Native Error Code: FFFFFBF8, ODBC Error: [Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data. Resolution: This is a Microsoft Jet error message. When Jet needs to write to a temporary file, it tries to do so in the Windows Temp directory (C:\\Windows\\Temp or whatever your TEMP or TMP environment variable is set to). If the current user does not have write access to that directory, the above message is displayed. Solution is to make sure the user has write access to the Windows Temp directory. Old KB# 3105#EnterpriseLink#Rumba

Problem: Are you trying to launch acuthin from the client, but the runtime on the server hangs up and does not start? Do you see only a splash screen on the client? Resolution: Check on the server if there's a NOD32 antivirus installed. acurcl has problems with NOD32 and the only way to let him work is to DISABLE the IMON process of NOD32. We have experienced the same problems with PANDA antivirus. In this case, you must have a 2007 PANDA installation at minimum. Then you can select wrun32 and acurcl within PANDA setup, telling antivirus to not block or scan their processes. Old KB# 3092

Problem: The report must have underlined characters and non-underlined characters on the same line.  How is this accomplished with AcuCOBOL-GT? Resolution: It is possible to print regular and underlined characters on the same line.  Here's one way using the WIN$PRINTER and W$FONT library routines. This requires the Windows Runtime. First, call the W$FONT library routine to load a regular font and an underlined font. Then write the line in pieces using WIN$PRINTER to specify the font for each piece of the line, and using the WITH NO ADVANCING phrase on the WRITE statements. The attached sample program, print1.cbl, demonstrates this method. Attachments: Print1.cbl Old KB# 3180

Problem: An error is recieved when there are 128 or more OR's in the SQL query be submitted to AcuXDBC. The error message is: Internal Error : CGE O OP: Too many OR 's and gives the line number producing the Error. Resolution: The limits for the AcuXDBC SQL processor are: 128 ORs 512 ANDs The resolution is to use a range in the query using the WHERE, e.g.: select * from table_name where column_name is >= 1 or column_name is <=200 instead of: select * from table_name where column_name is = 1 or column_name is = 2 or column_name is = 3 ... and so on until the error is encountered.  Changing the query to the first type will also have a beneficial performance impact and is a more well formed query than the problematic query. Old KB# 3153

Problem: A query was executed from MS Access against a linked table that was supposed to update the data in the underlying Vision file.  Instead it generated an error "Vision mode clash". Resolution: This error is seen when attempting to update a table that AcuODBC driver sees as read-only.   There are three items to check that will cause a file to be seen as read-only: 1. The AcuODBC license:  Make sure the license is not read-only.  Do that by opening the license, acuodbc.alc, with any text editor like Notepad or Wordpad.  The file exists in the bin directory of your Acucorp installation.  If the license contains this line:      #  Read only license then contact a Micro Focus Account Manager to obtain a non read-only license.    2. The DSN:  Open the DSN and examine the 'Advanced' tab.  Make sure the &#39

Problem: Can .GNT's built in NetExpress 4.0 (or earlier) be run in the Server for COBOL 5.0 runtime environment? Resolution: No.  Do not attempt to run .GNTs from NetExpress 4.0 (or earlier) with Server for COBOL 5.0 runtime.  They will have to be recompiled. Always be certain that the development and runtime environments are at the same version/release levels (i.e., NetEx 4.0, with Server 4.0 runtime). Old KB# 2865

Problem: WrapPack 5 (WS5) fails to install on top of WrapPack 4 (WS4). The log file reports MSI errors 2771 and 1603. Resolution: This is a known problem where WrapPack 5 was unable to uninstall some WrapPack 4's hotfixes. To resolve this issue, the hotfixes must be uninstalled prior to applying WrapPack 5. To uninstall hotfixes, follow the steps below: 1. Go to Add or Remove Programs 2. Make sure to check the 'Show updates' option - This will show all updates indented under each product 3. Select the HotFix under Micro Focus Net Express 5.0 4. Click the Remove button Old KB# 2867

Problem: What is EnterpriseLink Builder? Resolution: The EnterpriseLink Builder is the authoring tool that allows a WebMaster to transform or RePurpose the application into a new form.  Alternatate views of the application can be constructed for any number of reasons: Alternative views based on detail or header information Alternative audiences such as IntranetUsers, ExtranetUsers, InternetUsers Alternative devices such as browsers, phones, PDAs, WebClients Whereas Loader is used when the HostApplication is immediately available, the Builder may operate off-line.  However, it still requires the presences of the EnterpriseLink LicenseServer to validate the authors ability to modify the application. Old KB# 2916#Rumba#EnterpriseLink

Problem: Is it possible to track the scroll bar position in a ListView control? Resolution: By default the tracking of the vertical scroll bar is turned off in a ListView control.  It is possible to turn this on by making a modification to the ListView user control program. Load the ListView example in:      \\NetExpress\\Examples\\Dialog System\\COMMONCONTROLS\\LISTVIEW open the LVIEWCTL.CBL program and search for the following line:      01 Data-state         PIC X comp-5 value 0. change the value to 1 then tracking of the scroll bar position is enabled.  At runtime this will cause a callback in to the "Scrolling section" further on down in the program.  The variable called Numeric-Value will contain the row that has been scrolled to. Old KB# 2907

Problem: Application Server Net Express V3.1/4.0; Micro Focus Server 5.0: There is a problem running the application and not showing this Dialog System toolbar as expected, s.  'woToolbar.jpg' vs 'wToolbar.jpg' see attached. Resolution: It is strongly recommended to check the machine running the application whether the Micro Focus runtime PAN2NT.DLL (PanelsV2 for Win32) can be found more than once in different directories not related to the installation directory of the Micro Focus Application Server, for example it also exists in ..\\Windows\\System32. As part of the Micro Focus Application Server PAN2NT.DLL should be found only in the ..\\bin directory as iis installed, for example ..\\Micro Focus\\Server 5.0\\Bin. Attachments: woToolbar.JPG Old KB# 2860

Problem: With AcuXDBC created the system catalog without security, e.g. did not use the -pa option. When accessing the tables from Microsoft Access a prompt with the User/Password dialog is always dispalyed.  If they are left blank and enter is pressed it proceeds, so it does not need a username or password.   How can that popup be avoided? Resolution: The AcuXDBC driver is prompting because there is no username or password specified in the DSN. Even though the AcuXDBC system catalog doesn't use security the driver can't know that before it connects.  Since the username and password are empty it prompts for them.   The solution is to configure the DSN and add any value for Username and Password. Old KB# 2855