Rocket® COBOL

Created On:  26 January 2012 Problem: When printing through your COBOL application the user receives an error message indicating:User aborted print jobThe print job does not reach the printing queue. Resolution: This error is generated when the application cannot find the default printer or the drivers of the printer have not been installed.  You will need to install your printer or update the drivers so that it is recognised by your application. Incident #2552994 Old KB# 35414

Created On:  02 January 2011 Problem: When using LIKE in a WHERE clause that references a column type of VARCHAR or NVARCHAR the correct rows are returned if a literal is used in the comparison but not if a host variable is used.Example:This works:EXEC SQL    DECLARE mycursor CURSOR FOR SELECT DISTINCT        A.EMPL_NO       ,A.EMP_NAMEFROM EMPLOYEES AWHERE ( A.EMP_NAME LIKE N'%JAMILA%' )END-EXECThis fails:MOVE N'%JAMILA%' to EMP-NAMEEXEC SQL    DECLARE mycursor CURSOR FOR SELECT DISTINCT        A.EMPL_NO       ,A.EMP_NAMEFROM EMPLOYEES AWHERE ( A.EMP_NAME LIKE :EMP-NAME )END-EXECWhy? Resolution: The problem is that the space padding in the host variable causes the comparison to be false if the actual column data does not also have those spaces.You can get around this by padding the data ite

Created On:  26 January 2012 Problem: When compiling a .exe application to 64 bit you get the following error message in the compilation output:* Starting code generation* 006-R Read failure on input file. Not intermediate code or wrong versionERROR: (9) Program indicated failure Resolution: A common cause for this error message is when you try to compile an executable to 64 bit on a 32 bit machine.Please note that although you can use the P64 directive (which compiles applications to 64 bit using a 32 bit machine), you can only compile to intermediate ( .int ) code to 64 bit on a 32 bit machine.The only way that you can build a 64 bit EXE or DLL is to use Net Express on a 64 bit machine. Incident #2548035 Old KB# 35418

Created On:  24 January 2012 Problem: COBOL application batch programs which is processing a high volume of detail records and after several hours they abort with a COBOL File error 34 on SORTWK1. Resolution: The runtime SORT temporary files were limited to 2GB of data each on UNIX ports.  Since all the data is eventually merged into one temporary file, this meant that the total amount of data that could be sorted was limited to less than 2GB.  An error 34 during the SORT was the usual indication that this limit had been reached. In version 7.1.1 it was a change that enables large file support on those UNIX systems which support it.    The USE_LARGE_FILE_API configuration variable controls this support, just as it does for relative and sequential files.On UNIX systems, this variable allows you to turn on or off file system API support for very large files (greater than 2 gigabytes). Support for large files is enabled when USE_LARGE_FILE_API is set t

Created On:  17 January 2012 Problem: Associating .acu extension with 32-bit 9.1.0 Runtime is not working on 64-bit Windows. The installation was made from the 9.1.0 64-bit ACUCOBOL-GT archive as there was a need for 64-bit AcuXDBC.  However, the COBOL application requires the 32-bit Runtime. When double-clicking the .acu program file it gives an error about a missing Runtime license.  There are licenses for 64-bit AcuXDBC and 32-bit Runtime. The Windows file association was made again manually and specifying .acu files open with C:\\Program Files (x86)\\Micro Focus\\Acucbl910\\AcuGT\\bin\\wrun32.exe.  However, when double-clicking the .acu program file, Task Manager shows that it is still starting the 64-bit Runtime in C:\\Program Files\\Micro Focus\\Acucbl910\\AcuGT\\bin\\wrun32.exe. Resolution: The file association apparently only takes the executable name and then gets the path from the registry entry here: HKEY_CLASSES_ROOT\\wrun32.exe\\Shell\\Open\\Comm

Created On:  27 January 2012 Problem: When compiling a COBOL program that uses the DB2 directive on a Windows 7 computer, the following error occurs:COBDB0006S Required DB software: 'db2agapi' could not be found.This occurs even though the location of db2aprep.dll, C:\\program files (x86)\\IBM\\SQLLIB\\BIN is specified in the system PATH.  The same program works fine on a Windows XP computer. Resolution: This problem occurs when the Net Express project file resides on a mapped network drive instead of on the local drive.  Try the following: 1. Open the project in the Net Express IDE and select Project > Properties and click the IDE button 2. Add the environment variable PATH with the following value:        c:\\program files (x86)\\ibm\\sqllib\\bin;%PATH% 3. Do not place quotes around the value 4. Try to rebuild again Note: If your DB2 installation is in a different folder than the default shown above then please subst

Created On:  27 January 2012 Problem: When trying to read indexed ISAM files the user receives a file status code 37.037 File access denied (Fatal)Your attempt to access a file has been denied by the operating system. You might have tried to write to a write-protected file or you could have tried to read from an output device. Resolution: Alter the access permission on the relevant file. Access can be read-only, if you just want to read the contents of the file without making any changes, or it can be read and write in which case you can alter its contents. Is this file using LOCKTYPE=2? When using LOCKTYPE(2) the File Handler creates a separate data file with the extension .LCK, against which record locks will be held. When a COBOL program closes a file, the File Handler attempts to delete the lock file as it is no longer required. The problem arises when this delete operation coincides with another process that is attempting to open the same data file. If this process a

Created On:  24 January 2012 Problem: Net Express has been installed on a new machine and when Animating a program we can position the cursor on a data item and select Examine for the item but when we select the Change option the popup screen does not provide for any data entry/and does not show existing value. Why is this? Resolution: This looks like an OCX is not registered to Windows so it cannot be used by the product.  The Net Express product install and update must be performed with Administrator rights with write permissions to the registry for both HKEY_CLASSES_ROOT and HKEY_LOCAL_MACHINE\\SOFTWARE in order that the Windows registry can be correctly updated during the installation process.   The product contains two OCX's that need to be registered to Windows, VALUEEDITNX.OCX used during Animation and for opening a file as Binary and HEX6.OCX used for hex display in the Data File Editor. Open up a command prompt as Administrato

Created On:  23 January 2012 Problem: I have downloaded and installed the Dialog System AddPack for Visual COBOL from the Supportline Product Updates site at: http://supportline.microfocus.com/websync/VisualCobolAddpacks.aspxWhere do I find the version of the Dialog System Addpack that will install into the COBOL2010Runtime product? Resolution: There is only one Dialog System Addpack that can be installed for both the Visual COBOL Development product and the COBOL2010Runtime production product.The installer will determine which product is installed and will install the Addpack accordingly.It can be found on the Supportline Product Updates site at:http://supportline.microfocus.com/websync/VisualCobolAddpacks.aspx Old KB# 35406

Created On:  27 January 2012 Problem: If copybook or COBOL program has other extension e.g. .pro or .mam then when debugging the code in Visual COBOL won't colourise. This also makes it difficult to watch fields/see status codes. Resolution: Currently .cbl, .cob, .rc and ,cpy will be fully recognised in Visual COBOL.  You can rename the files to the recognised file extensions. Old KB# 35423

Created On:  27 January 2012 Problem: You may find that a project converted from Net Express to Visual COBOL does not build, it shows errors saying that words such as HEADING, BOOLEAN,ATTRIBUTE are reserved words. In Net Express all built without error. Resolution: These words such as: HEADING,BOOLEAN,ATTRIBUTE are reserved words in Visual COBOL, you can use the REMOVE directive  in the additional directives textbox , found in the project properties in your Visual Cobol project, to exclude these as reserved words, allowing for a successful build in Visual COBOL. For example, REMOVE "HEADING" Old KB# 35422

Created On:  26 January 2012 Problem: The Status of Solo is continually showing "Waiting for connection on port 81" when you select "Animate CGI." Resolution: This message is shown when Net Express cannot communicate with the SOLO webserver. A common problem is that the Windows Firewall intercepts the port communication.  You will need to open the port that you are using with SOLO or disable any firewall that you may have installed. Incident #2550833 Old KB# 35416

Created On:  27 January 2012 Problem: How do you set environment variables in Visual COBOL? Resolution: In your Visual COBOL Project right click on on the loaded project in the solution explorer > add new item > Add a new Application Configuration File > Once added to the project right click on the App.config file and choose edit from the menu in the solution explorer window > Now you will see an Environment tab which allows you to add environment variables as needed > Once you have added the environment variables click ok. Old KB# 35421

Created On:  28 December 2011 Problem: How do I set compiler directives for Server Express?  How many possible ways are there? Resolution: The Compiler searches for directives in the following sequence of locations: 1.  COBOL system default directives in the file cobol.dir.  The system will look for this file first in the current directory, then in $COBDIR 2.  System default directives contained in cob options in the file $COBDIR/etc/cobopt 3.  User default directives contained in cob options in the environment variable COBOPT 4.  Compile-time directives contained in cob options on the cob command line     (to use this method, the syntax is “cob –C directive”) 5.  Program-specific directives in $SET statements in the source code file of each program.You can further customize the Compiler's behavior by creating your own directives file.  You can specify the DIRECTIVES on the command line, in a $SET statement

Created On:  22 December 2011 Problem: This is a general article for help with UNIX License issues.  Other KB articles are referred to for more information. Typical issue:  License manager not found, not running, or giving an error message. Resolution: During Server Express installation, the lmfinstall script installs the LMF License Manager.  However, there is an option not to install.  You can execute the lmfinstall script after installation. The script resides in $COBDIR/lmf, (where $COBDIR is the directory in which Server Express is installed). If an older version of the LMF is already installed, make sure the license manager is running (verify this using the 'lmfgetpv' command), so the lmfinstall script will recognize the existing version.  Then, when you run lmfinstall, the screen will say:A possibly older version of License Manager than this one is currently running on the system. It is installed in [location] It is recommended that you upgra

Created On:  04 January 2012 Problem: The following compiler directive has to be set in order to enable the C$Century call (or some other RM/COBOL subroutine like C$DevEnv,...) to return a value:RM "GIVING"But if this compiler directive is used, the Visual COBOL subroutines don't work. For example, the CBL_GET_PROGRAM_INFO subroutine doesn't work; when I use it in a program, it doesn't work correctly or it returns a RTS error 114 on the call.When the compiler directive RM "GIVING" is not used, then the CBL_GET_PROGRAM_INFO subroutine works correctly.I need to use RM/COBOL subroutines and Visual Cobol subroutines in the same program. How can this be done? Resolution: The RM"GIVING" directive changes the default call-convention that is used from Visual COBOL to RM.In order to call Visual COBOL subroutines in a program that has the RM"GIVING" directive on you need to specify a call-convention of 0 when calling the Visual

Created On:  21 December 2011 Problem: When using mflmadm (or option 2 from mflicense) the utility does not start.  In the case of mflmadm, DS Error 0003 is returned.  In the case of choosing option 2 from the mflicense menu, the menu just recycles and shows the menu again. Resolution: 1.  Download and install HotFix 1 for WrapPack 6.  To get a link for the HotFix, you need to request it from SupportLine.          Instructions to install a hot fix:As root, with COBDIR set, execute the file. You will now have a tar file containing the Fixpack. Extract the FixPack, e.g. tar xvf filename. To install the FixPack, first ensure that no application is running under that COBDIR (i.e check that $COBDIR/eslm is not running on the machine) and then execute the installation script: sh ./install.2.  Re-run the LMF install to update files in the mflmf directory.      cd $COBDIR/lmf &n

Created On:  14 December 2011 Problem: The application is deployed with version 8.1.3.1 so there is a need to compile for that version but the -Z81 compile option is not available.  The -Z80 compile option is there but is not appropriate as there is a fix for an issue with the date entry control that requires compiling for 8.1 or later. Resolution: AcuBench 9.0 is missing the -Z81 compatibility option in the Project Settings, Compiler, Miscellaneous Options, “Program can be run by the version” list.  The resolution is to not select “Program can be run by the verion” item.  Instead, enter -Z81 in the “Additional Options” box on the Compiler tab.  The same is true of the Project Settings, Compiler, Compatibility Options, “Version compatibility mode”, -C81 option.  The resolution is the same, add -C81 in “Additional Options”. Old KB# 35326

Created On:  16 January 2012 Problem: Prior to version 9.0, using Acu4GL Oracle or Acu4GL DB2 on UNIX it was a needed procees to relink the database libraries to the runtime. This process sometimes generated some errors. Resolution: Now, relinking is no longer necessary. For UNIX shared builds, Acu4GL Oracle and Acu4GL DB2 are now shared libraries, so all that needs to be done is to setting the appropriate environment variable (i.e LD_LIBRARY_PATH). Old KB# 35383

Created On:  14 December 2011 Problem: After an upgrade to version 9.1.0 the application no longer displays the jpeg images.  There are blank spaces where the images should be displayed. Resolution: The image handler, ajpg32.dll, was inadvertantly left out of the 9.1.0 32-bit installation.  It should be in the 9.1.0 AcuGT\\bin directory.  That is fixed with the 9.1.1 installer.  In the meantime the workaround is to copy the ajpg32.dll from a previous installation.  Or you may download the one attached to this article. Attachments ajpg32.zip Old KB# 35324

Created On:  06 December 2011 Problem: I am using Net Express 5.1 IDE to debug a program.  I begin animation by "stepping into" program.  Then right-clicked a variable in the procedure code that is defined alphanumeric in working storage with a VALUE clause and selected "Examine" from the context menu. "Examine List" dialog displays with variable name and contents displayed as expected.  I clicked "Change" button on "Examine List" dialog and "Change value of" dialog displays with name of variable in Title bar, but no data in pane.  I cannot change contents of variable. I clicked "Monitor" button on "Examine List" dialog and it disappears, but no monitor window displays. What could be the problem? Resolution: This looks like an OCX is not registered to Windows so it cannot be used by the product.  The product install and update must be performed with Administrator rights

Created On:  22 December 2011 Problem: In RM COBOL we use the following line of code and it works fine. IF (TEST-FIELD(1:1) IS LIKE CASE-INSENSITIVE “S”) In Visual COBOL this same statement causes an "Invalid Operand" error. Resolution: The UPPER-CASE intrinsic function can be used instead of the CASE-INSENSITIVE of RM.IF FUNCTION UPPER-CASE(TEST-FIELD(1:1)) = "S" Old KB# 35343

Created On:  12 January 2012 Problem: When starting Visual COBOL for Eclipse various plugin / java errors could be seen, indicating corrupted plugin files. Resolution: If plugins get corrupted in Eclipse you can start Eclipse with the -clean option. this rebuild/refreshes all the installed plugins.Sample usage:-Open a command prompt,-Navigate to C:\\Users\\Public\\Micro Focus\\Visual COBOL 2010\\eclipse\\,-Start Eclipse using eclipse -clean Old KB# 35377

Created On:  12 January 2012 Problem: When starting Visual COBOL for Eclipse you receive an error saying: "Initalizing: Cannot communicate with Licensing Daemon". Resolution: You should check that your MF CES Daemon service is started/running under Windows Services. If not started, start and make sure it is set to start automatically. Old KB# 35378

Created On:  22 December 2011 Problem: When workeing with Indexed Files in RM COBOL we use the following syntax:          START TEST-FILE KEY FIRST KEY-1                    or                    START TEST-FILE KEY LAST KEY-1But it doesn't work with Visual COBOLl. How can the first or last record of a particular key be read in Visual COBOL? Resolution: This syntax is not supported in Visual COBOL.  To get the same functionality you would need to do something like the following:MOVE LOW-VALUES TO KEY-1START TEST-FILE KEY >= KEY-1READ TEST-FILE NEXT RECORDMOVE HIGH-VALUES TO KEY-1START TEST-FILE KEY <= KEY-1READ TEST-FILE PREVIOUS RECORD Old KB# 35344#COBOL#netexpress#VisualCOBOL#Enterprise