Browse all forums dedicated to the Rocket® COBOL product family.
Recently active
Problem: The ODBC trace is somewhat difficult to decipher. Are there any other diagnostic capabilities available from OpenESQL? Resolution: Yes, you can compile your applicaion with the SQL(TRACELEVEL=n) directive. Notes : 1. The trace filename is actually OpenESQLTrace.processID.log . If your application is compiled with the SQL(DBMAN=ADO) directive, the trace filename will be ADOTrace.processID.rununitID.log . 2. If the OpenESQL application is executing under the auspices of ASP.NET, the effective user ID under which the application invokes is not your Windows user ID -- instead, the ASPNET user ID -- hence the location of the trace file may not be where you expect it. 3. If you have installed the ESQ08N40.EXE FixPack, or ALL06N40.EXE WrapPack , OpenESQL will write out trace files to the current directory. If the process doesn't have write permissions to the current directory, the trace file will get written to the directory specified by the TEMP
Problem: To be able to control a ListView via the keyboard you need to set focus on the control. Is there a way of doing this? Resolution: Unfortunately the Dialog System SET-FOCUS function does not work with ListView controls. So, it is necessary to look at the control program and add the following code: ... PROCEDURE DIVISION. ... when "SET-FOCUS" invoke Object-Reference "SetFocus" ... This new function is then called from the screenset via the following code: ... SET OBJECT-REFERENCE(1) LVIEW MOVE "SET-FOCUS" call-function(1) CALLOUT "lviewctl" 3 $NULL ... Functions can also be added for hiding and showing the ListView control if required. Old KB# 7122
Problem: If it is desired to debug .NET code (C# or VB .NET) that is invoked from an unmanaged COBOL program, please try the following: In the Visual Studio .NET Project Properties menu, select Configuration Properties, Debugging. Make sure that "Enable Unmanaged Debugging" is set to true and that "Start Application" specifies the name of the COBOL executable (or the runw.exe trigger program if using .int or .gnt code). The "Debug Mode" property should be "Program". When debugging, the COBOL program should run and execution should stop at the breakpoint you set in the .NET code. Resolution: If it is necessary to debug .NET code (C# or VB .NET) that is invoked from an unmanaged COBOL program, please try the following: In the Visual Studio .NET Project Properties menu, select Configuration Properties, Debugging. Make sure that "Enable Unmanaged Debugging" is set to true and that "Start Application&qu
Problem: Normally, when inserted the Net Express CD starts automatically by Autostart.The setup.exe in the root directory is started and launches the Internet Explorer to start this process. How can be the Micro Focus Net Express Setup.exe started when this is failing? Resolution: 1. You may try to copy the CD to your c: drive and start the setup.exe from there. 2. if this also fails: - start a CMD prompt - insert the CD into the drive - change the actual directory to the root directory of your CD drive - enter: \\setup\\setup.exe /ini=\\setup\\nxsetup.ini to start the Micro Focus Net Express setup. Old KB# 7100
Problem: MQ Series and SQL calls in the same program produce this error: Creating library DEBUG\\MQsqlACD.lib and object DEBUG\\MQsqlACD.exp MQsqlACD.OBJ : error LNK2001: unresolved external symbol _ODBCRW32 DEBUG\\MQsqlACD.exe : fatal error LNK1120: 1 unresolved externals Rebuild complete with errors Resolution: Normally MQSeries COBOL programs require the LITLINK directive, however when you use sql you cannot use this directive as it causes link errors. You need to remove the litlink directive and use a procedure pointer to load the mqseries dll like follows: Use the Procedure-Pointer method, which will permit the same program to be run on a machine running MQSeries Client, or the MQSeries Server. This does not require the addition of MQMCB32.LIB or MQICCB32.LIB when creating EXE or DLL. IDENTIFICATION DIVISION. PROGRAM-ID. 'MQODBC
Problem: When attempting to apply the clu01all.exe licensing fix can cause the installation process to hang. Resolution: Occasionally this happens when attempting to apply the fixes from the Net Express 4.0 CD-ROM. Downloading and running the fix from the Micro Focus Supportline web site (http://supportline.microfocus.com) avoids this problem. Old KB# 7144
Problem: Use an environment variable for the compiler directive OUTDD($OUTDDENV) The $ is used to let the runtime know that it is to read this environement variable when the program does the first DISPLAY. Resolution: $SET INITCALL(MFEXTMAP) OUTDD($OUTDDENV) * * TO CHANGE THE CONTENTS OF AN ENVIRONMENT VARIABLE, * MFEXTMAP MUST BE LOADED. * IDENTIFICATION DIVISION. ************************************************************** * PROGRAM-ID. OUTDDENV. * ******************************************
Problem: FAQ Net Express 4.0 old runtime availablity Resolution: On November 24 2004 the back level wrappacks for the Enterprise server for Net Express 4.0 and Application server for Net Express 4.0 were made available on the support website just under the current level of the runtime patches. http://supportline.microfocus.com Old KB# 7118
Problem: We have done web service development using VB and C# in the .NET environment, and would like to incorporate COBOL. However, it appears that the University edition of COBOL .NET restricts the creation of a web service. It compiles, and is visible in IIS, but the required files to reference the web service are missing. Resolution: You cannot deploy a Web Service created with Net Express UE, as it does not include Enterprise Server and its associated facilities. You will need a Server installation to create and deploy a Web Service. Old KB# 7102
Problem: Which 'User rights' are needed when running Net Express in general? Resolution: Net Express must be run under a user account with a user-ID that has write access to the registry structure under HKEY_LOCAL_MACHINE, HKEY_CLASSES_ROOT, and HKEY_CURRENT_USER so the installation software can set the environment for running Net Express. To uninstall Net Express, the same user-ID must be used as when you installed it. Especially, apart from this you should check the registry as follows: HKEY_LOCAL_MACHINE\\SOFTWARE\\MICRO FOCUS HKEY_CURRENT_USER\\SOFTWARE\\MICRO FOCUS Old KB# 7124
Problem: Is it possible to configure how Net Express searches COBDIR to locate programs ? Resolution: The COBOL runtime which is responsible for the loading of programs is configurable using runtime tunables. The locations searched for during the call of a program is configurable using the "program_search_order" runtime tunable. Old KB# 7117
Problem: The documentations state the following suggestions: "Provide a login on the UNIX system, and configure the .rhosts file to enable transparent login without requiring a password. See your UNIX documentation for details on how to do this." Resolution: Look at the "Alternative Security Mechanism: SCP Daemon Method" to enhance security. This topic can be found from the Net Express Help at Contents\\Using Net Express\\UNIX Option\\UNIX Option Guide\\A: Installing Samba and SCP\\Configuring SCP\\Alternative Security Mechanism: SCP Daemon Method This will force the user to key in valid user id and password in order to deploy on Unix. It is important that the user who starts the daemon from the Unix side has a root access. Old KB# 7132
Problem: Can I specify Microsoft's linker options like -version:<major>.<minor> using CBLLINK? Resolution: No, CBLLINK does not forward options to Microsoft's link.exe. The options -version:<major>.<minor> can be specified by a different syntax in a .RC file, which can be included into the link process after being compiled to a .RES file. Alternatively start CBLLINK using options -V and -K -V means 'verbose' -K means 'keep temporary linker files' Rerun the link.exe with additional parameter -version:<major>.<minor> Old KB# 7095
Problem: These two errors occur because the programs are linked with different threading models. Runtime DLL 'CBLRTSM', version 3.1, entry point mF_ld_dynlnk_lib_check not recorded in registry, not found or incompatible with requirements of dynamically bound COBOL program. Dynamic binding of RTS requires: Runtime DLL 'CBLRTSS', at least Version 3.1 Runtime DLL 'CBLRTSS', version 3.1, entry point mF_ld_dynlnk_lib_check not recorded in registry, not found or incompatible with requirements of dynamically bound COBOL program. Dynamic binding of RTS requires: Runtime DLL 'CBLRTSM', at least Version 3.1 The version numbers and entry point name will vary depending on the application. Resolution: These errors occur when a calling program has been created with one threading model and the called DLL has been created with a different threading model. The fix is to rebuild the application programs and use a consistent th
Problem: ODBC errors when accessing data using Intelliview and an XDB ODBC Driver Resolution: These errors are caused by having the "XDB" check box option set in the ODBC Server configuration. Changing this to DB2 resolves the problem. The XDB is for use with old versions of the XDB Server. Old KB# 7125
Problem: How to use the data file editor for files with non DAT extensions? Resolution: The extensions must be added before the file is added to the project. If you have a data file with an extension of XYZ that you would like to use the data file editor within a Net Express project you will need to set the extension XYZ to data. PROJECT menu Extensions Add XYZ Data Select the OK button and then the Close button Now, by adding the file to the project, it will be setup as a data file. Old KB# 7090
Problem: Is it possible to load multiple COBOL source files in to the same instance of the Net Express IDE by double clicking on files in Explorer? Resolution: It is not possible to configure the Net Express IDE in this manner. It would require Micro Focus to add a DDE/OLE interface layer and this is something that is not currently present. Alas, it is not the sort of functionality that will be added given our strategy of further Visual Studio integration in the future. Old KB# 7121
Problem: Many developers find that older COBOL applications or those written for other COBOL compilers like WANG or DEC, demonstrate numeric entry that seems simpler than what Micro Focus COBOL expects. Fewer keystrokes are needed to complete the entry and decimal alignment of edited numeric fields doesn't require the entry of a final period (.) in order to complete the ACCEPT command. Here's a trick that works for all versions of Micro Focus COBOL, whether you are using UNIX products like Server Express or Object COBOL Developer Suite or the PC products like Net Express or the older COBOL Workbench. Resolution: Using this short demonstration example: Program-ID. Numtest. WORKING-STORAGE SECTION. 01 MY-NUMBER PIC 9(09).
Problem: Net Express was recently installed on a computer. When trying to run it, a Semaphore failure error is reported. It is necessary to uninstall Net Express 4.0, clean up registry and previous installed folders, reboot, and reinstall Net Express 4.0 Resolution: step 1) control panel -> administrative tools-> services stop micro focus directory server stop micro focus xdb server step 2) control panel -> add/remove programs and uninstall Micro Focus Net Express 4.0 step 3) start -> run -> regedit if net express is the only micro focus product you have installed then search and delete "micro foc
Problem: Net Express 3.0 installation on Windows 2000 service pack 3, Error duing installation of service pack 1, error 255 when trying to install compiler fixpack. Resolution: Uninstall Net Express 3.0 and prepare machine for reinstall. Suggest installing Net Express 3.0 into a folder with no spaces, for example-> c:\\ne30 step 1) uninstall Net Express 3.0, retain license step 2) make sure no folders exist from previous installation attempts step 3) set tmp and temp environment variables in both system variables and user variables to c:\\temp How to set temp and tmp: goto My Computer and right mouse click and select properties &nbs
Problem: Is Net Express 4.0 compatible with Windows XP SP2? Resolution: Net Express 4.0 has been tested on SP2 and the results did not show any problems. Full support will be announced from the WebSync released in November 2004 (ALL04N40.EXE). Old KB# 7113
Problem: A web application may appear to be able to create an output file from the development machine with the Solo webserver. Once deployed on an IIS server, the output file may not be created. Resolution: Make sure the output file is created in a directory where the application has permissions. Since the application in some instances is executed by IIS, which has its own user id to execute the web application or access some allowed resources, make sure it has access to the directory where the appplication will create the file. Old KB# 7126
Problem: The customer was making a CALL to a subprogram in the form of an external DLL. He was attempting to use the ON EXCEPTION clause of the CALL statement by using ON EXCEPTION CONTINUE. He did not have a NOT ON EXCEPTION phrase nor did he have an END-CALL or a period to end the CALL statement. He could not figure out why none of his statements following the CALL were being executed since he knew that the CALL was being executed successfully. The following is the sytax that he used: 100-TEST. IF WS-TEST-TRUE MOVE "PROG2" TO WS-NEXT-PROG CALL WS-NEXT-PROG USING RFVCODES RETRN-CD ON EXCEPTION CONTINUE CANCEL WS-NEXT-PROG &nbs
Problem: Trying to use Net Express 4.0 Help via IDE returns an error similar to: "Internet Explorer script failure" or "object does not support methods and properties" It is completely impossible to run the Net Express 4.0 Help via IDE. Resolution: There is a related Microsoft Knowledgebase article to resolve this problem if you have included some additional cumulative patches for Internet Explorer after Feb 2003: HTML Help Update to Limit Functionality When It Is Invoked with the window.showHelp( ) Method Microsoft Knowledge Base: Q811630: http://support.microsoft.com/default.aspx?scid=kb;en-us;811630 Old KB# 7106
Problem: Is there a variable (or function), similar to file status code, that can be queried to find out if a file was opened for input / i-o etc ? Resolution: You can use the "fcdreg" compiler directive, the "FH--FCD" special register and the "xfhfcd.cpy" copy book to gain access to the "fcd" file descriptions compiled into your program. Define your "fcd" in your linkage section (1 myFcd.) followed by a copy statement retrieving the "xfhfcd.cpy" COBOL copy book delivered with your development system. In your procedure division set addressability to your "fcd" in your linkage section with a set statement. Compile your program with the "fcdreg" and "qual" compiler directives. 000010$ set fcdreg qual 000020 file-control. 000030 select myLogicalFile assign 'MYDATA.DAT' ... 000040 linkage section. 000050 1 myfcd. 000060 copy xfhfcd.cpy. 000070 procedure division. 00008
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.