Rocket® COBOL

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: Is there any way to know the name of the program that is currently running, besides calling another program and in that program using the "C$CALLEDBY" routine? Resolution: In version 6.2.0 the following C$MYFILE library routine was introduced. This routine returns the filename of the disk file containing the currently executing program.    Here is an example of how to use it:        WORKING-STORAGE SECTION.        77  PROGRAM-NAME pic x(80) value spaces.        77  CALL-STATUS pic s99 value 0.        Main Section.                 CALL "C$MYFILE"                  USING PROGRAM-NAME     &nbs

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: 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: 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: During the installation of a version 8.0.1 patch file (8.0.1.1012.msp) a message box was displayed with the following message: Error: 1334: The file 'ccbldll.dll' cannot be installed because the file cannot be found in cabinet file 'PCW_CAT_FAMILY00'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package. Resolution: The patch file that was being installed was cummulative and already contained in a prior patch that had already been applied to the target machine.   Using Windows "Add or Remove Programs" (check "Show updates") dialog box ("Installed Updates" of "Program and Features" on Windows Vista) to uninstall the previously applied patch (version 8.0.1.1001) allowed the new patch file (version 8.0.1.1012) to be installed on the target machine. Old KB# 3178

Problem: Often, it is necessary to get a file trace of a lengthy program, and the file can get rather large. Usually, the size of the trace file can be controlled by using the configuration variable MAX_ERROR_LINES. Sometimes, however, a full trace file is needed. Here is a way to get a compressed file trace on UNIX by using Gzip. Resolution: On the run command add the -g and then the error filename with the extentsion: runcbl -g -lex myerror.gz myprogram.acu To view the fiile use the gunzip command: gunzip myerr.gz Old KB# 3186

Problem: After creating a grid by using the Drag-and-Drop interface the the (Name) property of this grid could not be changed. Resolution: This behavior is fixed in version 7.2.1 and higher by ECN-WB849. Old KB# 3162

Problem: How can I modify NO-AUTOSEL property for entry-field in ACUCOBOL-GT? MODIFY S1CG01003-T-CAU, NO-AUTOSEL = TRUE or MODIFY S1CG01003-T-CAU, NO-AUTOSEL IS TRUE give compile errors. Resolution: The right syntax is: modify Screen1-Ef-1, NO-AUTOSEL to activate this property or modify Screen1-Ef-1, not NO-AUTOSEL to de-activate it. Old KB# 3183

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: 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: The following XFD FILE directive caused an "Unknown XFD directive" error message to be generated by the ACUCOBOL-GT compiler: $xfd  file=vxml.xml Resolution: The error may be resolved by adding quotes around the full file name as in this example: $xfd  file="vxml.xml" Or by removing the file extension as in this example: $xfd  file=vxml For more information on the XFD FILE directive can be found in the ACUCOBOL-GT User's Guide Version 8.0, Chapter 5: File Processing > 5.3 XFD Files > 5.3.3 Syntax >5.3.3.6 FILE directive. Old KB# 3171

Problem: The Autofix facility enables you to automatically correct your common typing mistakes. By specifying a list of words that you sometimes mistype, and the correct spellings for them, you can type the misspelled versions and have them automatically corrected. Not only is this tool good for catching your common typos, but you can use it to quickly type out long variable names by assigning your own custom abbreviations. For instance: WS-MAINMODULE-VARIABLES-PROGRAMX-COUNTER-3 Could be abbreviated: COUNTER3 or 'long-data-item-name-12' could be abbreviated 'L12' Resolution: You can find the Autofix options by going to Options>Edit>Autofix tab. You will need to add some entries and check the box 'Monitor my typing' to get started. Now whenever you type something that is in the "If I type this" column, it will automatically be converted to the text in the "Change it to this" column. Remember that this utility is case-sensitive.Ol

Problem: Can a COBOL Application create PostScript files? Resolution: The Server Express COBOL system doesn't contain any PostScript features or functionality however it is possible to generate a PostScript file from within a COBOL application by using Server Express' ability to pipe output to external commands/applications. Create a SELECT statement like the following SELECT OUTPUTFILE ASSIGN TO ">  enscript -r -Picl2 -o out.ps" Organization LINE SEQUENTIAL. Then create an FD for the file: FD OUTPUTFILE. 01  OUT-RECORD  PIC X(256). In the procedure division: OPEN OUTPUT OUTPUTFILE MOVE "SOME TEXT" to OUT-RECORD WRITE OUT-RECORD . . . CLOSE OUTPUTFILE. . . . Ths should produce a file named out.ps that us a PostScript file suitable for printing or use with PostScript friendly applications. Note: If the enscript command is not available , there are several suitable altern

Problem: Can Net Express run on a 64-bit operating system? Can 32-bit applications be built and still run on a 64-bit operating system? Resolution: When Net Express is installed, it automatically detects the bittage of the operating system. For instance: if the operating system is 64-bit, the 64-bit version of Net Express will be automatically selected and installed. There is no prompt or notification of this event. By default, 64-bit Net Express will still produce 32-bit run-times. If 64-bit run-times are desired, this setting can be changed in the Project Properties. If Net Express is installed on a 32-bit operating system, the applications that get built can still run on a 64-bit operating system. Windows has always come with a component called WOW (Windows on Windows) emulation. It was originally used to allow 16-bit programs to run on 32-bit versions of Windows. WOW64 allows 32-bit applications to run on 64-bit Windows operating systems. This means that any

Problem: When using the Inteface Mapping toolkit to expose a COBOL application to Java you can specify a package name for the generated Java. If you use native in the package name then you get an error in the generated Java. For example using "com.microfocus.test.native" would result in an error in the Java. Resolution: This is a restriction of Java. "native" is a keyword in Java and cannot be used in a package name. You need to avoid native in the Java package name. Old KB# 3159

Problem: WrapPack 8 (ALL08N40.EXE) fails with the following error: "Net Express with .NET will not be installed because: Microsoft Visual Studio .NET is not installed" Resolution: The error above indicates that the WrapPack detected Net Express with .NET, and it cannot install the newer version because Microsoft Visual Studio .NET is not installed. The resolution is then to uninstall Net Express with .NET from Add or Remove Programs and re-apply the WrapPack. How could Net Express with .NET be installed without Microsoft Visual Studio .NET? This can be done by having both Net Express with .NET and Microsoft Visual Studio .NET at one point and then uninstalling Microsoft Visual Studio .NET only. The uninstall of the Microsoft product does not automatically remove Net Express with .NET.Old KB# 3000

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: 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: The extend 8 Runtime and Acu4GL for MSSQL were installed and when executing a program a window pops up with a message that the wrun32.2lc license is missing. Wrun32.2lc is the license for the AcuSQL Runtime but that product was not selected during install. How can the Runtime be stopped from displaying that message? Resolution: There is a defect with the Version 8.0 installation which caused it to install an extra dll, one for AcuSQL.  At execution the Runtime sees the dll, checks for the license, then displays the message  about the missing license. The solution is to navigate to the bin directory of your extend 8 installation and delete asqlsrvr.dll. Old KB# 3103

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: After applying Fixpack 10 for Server Express v5.0 WP4 on AIX (contained in the file SXFixpack50.04_10_dev.tar.encr), then dynamic debugging of Enterprise Server might begin to fail.  The following error might appear in response to "cobesdebug type=cics": "the specified region is not enabled for debugging" despite the fact that the appropriate "enable debugging" box is checked in the ES admin screens. Also, the error "CASSI1807I Dynamic debug initialisation failed" might appear in the ES Console log. Such problems are often solved by following the advice in Knowledgebase article 25576, but in some cases the problem might persist even after KB 25576 is considered and acted upon. Resolution: This is a known problem with Fixpack 10 for SX v5.0 WP4 for AIX.  The problem has been fixed in the Server Express v5.1 release.  The solution is to upgrade to SX v5.1. Old KB#

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: 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