Rocket® COBOL

Hello, I am trying to use Relativity with a JOIN command and getting the error "Literal not allowed in ON condition".  To build the key info on the join I have the following LEFT OUTER JOIN     INVXRF_RECORD ON     IXTYPE = 1   AND IXITEM = CREOITEM   AND IXCUST = CREOCNBR I know the value of IXTYPE for the records I am searching for will always be a value of 1 in this case. All of my assigned keys to the file INVXRF contain IXTYPE as PIC 9. This is normally a very quick query and I can kind of fool the system by saying IXTYPE = CBSTMT (which is another PIC 9 field in a different table that is part of the select), but it still takes way too long and then I have to be sure that for the records I am looking at that setting is always a 1. Any thoughts on how to get around this? It is really critical to our operation as we are switching from one ODBC connector to Relativity and this is kind of a show stopper.#RELATIVITYGROUPS

Problem: Error when starting a Fileshare Server: "FS077-S A Fileshare Server of the same name has already been defined" Resolution: The end-user was trying to start more than one Fileshare Server having the same name, though on different machines.  They were running ccitcp2 processes on each machine, and were not setting the CCITCP2 environment variable on any machine.  This conflicts with the design intention of Fileshare and CCITCP2.  The ccitcp2 process is a registration process, similar to a nameserver, and the intention is that just one machine in the network will run the registration process and act as the nameserver, while on all other machines, the environment variable CCITCP2 will be set to the name of the machine where the ccitcp2 process is running, so all machines will use one registration process. When the CCITCP2 environment variable is not set, the assumption is that the ccitcp2 process running on the local machine is the intended registration pr

Problem: Under Visual COBOL, the tool named FaultFinder appears to be absent. Resolution: The FaultFinder tool, which had been available in Server Express and Net Express, has been removed from Visual COBOL on both Windows and Linux/UNIX.  Here is a documentation link mentioning this (scroll down to "Diagnostic tools"): https://www.microfocus.com/documentation/visual-cobol/vc50/EclUNIX/GUID-8AD22EC0-B0B0-4D14-A16A-B4D6CEE5A9E3.html Net Express and Server Express, and also Visual COBOL, are sold in two forms of product that might be called the "development" product and the "runtime" product. The chart below shows product names: "Development" Product Name "Runtime" Product Name Net Express Server for COBOL for Net Express, or Application Server for Net Express Server Express Server for COBOL for Server Express, or Application Server for Server Express Visual COBOL COBOL Server   A "development" product

Problem: While trying to run the Micro Focus License Administration utility /var/microfocuslicensing/bin/cesadmintool.sh, the following error appeared:  Micro Focus License Administration ================================== Java not present on PATH(or wrong version). A 32bit Java 1.5 runtime is required to run the license administration tool. Please add java to your PATH and retry. At the time of the error, the Java version was reported as follows: # java -version openjdk version "1.8.0_71" OpenJDK Runtime Environment (build 1.8.0_71-b15) OpenJDK 64-Bit Server VM (build 25.71-b15, mixed mode) Resolution: As explained in the Release Notes, the Visual COBOL product and the Micro Focus License Administration utility require Oracle's Java Platform, Enterprise Edition (Java EE) 7 or Java 8.  The Visual COBOL product was not tested or certified with OpenJDK. The solution is to download Oracle's Ja

Problem: When compiling a program, the following error is reported by the compiler: Operand time-of-day is not declared Resolution: In both the Server Express documentation and the Visual COBOL documentation, the special register TIME-OF-DAY is documented as being applicable to the OSVS dialect. In addition, the documentation generally says:  TIME-OF-DAY    9(6) DISPLAY The TIME-OF-DAY special register contains the value of the current time of day (24-hour clock) (as supplied by the COBOL execution environment), in the form: hhmmss where hh =hour, mm=minutes, and ss= seconds.  TIME-OF-DAY is valid only as the sending area of a MOVE statement. Based on the above, here is a sample program I wrote to test this: 000001 IDENTIFICATION DIVISION.000002 PROGRAM-ID. TOD-TEST.000003 ENVIRONMENT DIVISION.000004 CONFIGURATION SECTION.000005 DATA DIVISION.000006 WORKING-STORAGE SECTION.000007 01 TIME-OF-DAY-WS PIC 9(6).000008 PROCEDURE DIVISION.000009   &nbsp

Problem: Using Visual COBOL, a program that opens an indexed file for OUTPUT creates just one file on disk, as opposed to the behavior in earlier versions of MF COBOL, where two disk files were created: a data file and an .idx file. Resolution: In Visual COBOL, the default IDXFORMAT is now IDX8, which creates just one disk file holding both the data and the index.  To override this default behavior and configure Visual COBOL to create IDX4 files instead, a person can specify idxformat=4 in the File Handler Configuration file, or use the IDXFORMAT"4" compiler directive, or specify $set idxformat"4" in source code.

Problem: When attempting to start AcuServer version 9.2 on a Linux server there is an error message "unable to add users" and it fails to start. Solution: The "unable to add users" message is actually coming from AcuShare (the license and shared memory manager).  This means Acushare is not running properly.  Do the following to get it back to normal; once AcuShare is running normally AcuServer will start. Execute "acushare" (no option).  If that responds with the usual acushare report then it is running so do "acushare -kill". Execute "ps -ef | grep acushare" to make sure the acushare process has terminated.  If it hasn't then do "kill -9" on the AcuShare PID. Execute "acushare -clean". Execute "acushare -start". Lastly, start AcuServer.

I post here this link with an example using pdfcreator 2.4.0 com interface this example print 2 reports in one PDF file  before run the example install pdfcreator 2.4.0 I suggest using command line pdfcreator-2_4_0-setup /Silent and restart your machine before run the example https://drive.google.com/file/d/0B6CfTLgUpUXgTXNGajRaY0FTNzA/view?usp=sharing Regards. #PDFCreator#ActiveX

Problem: When using an ADO.NET application to query a Relativity data source, all, returned decimal data is truncated. Resolution: Microsoft's ADO (ActiveX Data Objects), which is used to access ODBC from VB, C#, SQL Server, etc..., does not work with the standard Relativity driver. To avoid this issue, a Relativity ODBC driver has been introduced that is optimized for ADO. This new driver is automatically installed with the Relativity Data Manager, Relativity Data Client (32-bit), and Relativity Data Client (64-bit). The driver names are: Relativity for ADO (*.rcg) Relativity Client for ADO Relativity Client for ADO (64-bit) This new ADO-compliant driver is available in Relativity v12.13, and above.

Problem: If you are installing separately licensed RM/COBOL Development, and Runtime, System products on the same UNIX machine, and, into the same directory, then, you will need to combine those licenses into the same vault file (license.vlt). Resolution: In order to install separately licensed RM/COBOL Development, and Runtime, System products, you only have to install the Development system, as that includes a Runtime.  Once the Development System has been installed, then, you can add the higher Use Count Runtime license to the existing license vault using the Liant License Utility(licverifyall).The licverifyall program ships with the latest versions of our products, and may be found under the SupportTools directory of the product installation.You can use licverifyall to add the Runtime *.lic to the current license.vlt (that already has the Development System license in it) with the following procedure:  Make a backup copy of the existing license.vlt file.  Chan

Problem: After upgrading to version 10 some report programs are crashing.  Troubleshooting revealed that it is the SORT statement which is crashing the Runtime.  Solution: Version 10 introduced major changes in the SORT verb.  These changes eliminated the SORT_FILES Runtime configuration and added new ones.  Setting A_SORT_REGIONS to half the value of the previous setting of SORT_FILES will achieve the same effect with the new SORT.  We recommend testing with A_SORT_REGIONS=0 to see if this new mode of operation yields better performance in a given system. Following is the full description of the changes to SORT.  Please study this information carefully and test to determine the best settings for your system and application: The internals of the Runtime SORT verb have been updated to provide a new mode of operation for SORT that avoids a significant amount of file I/O and may provide better performance for large SORT operations.  A new method of manag

Hi We are upgrading an application from Visual Cobol 2.1 on Windows XP to Visual Cobol 2.3 on Windows 10.  The application consists of windows forms projects and native code programs compiled as managed code.  We have been using VS 2010 Shell on Windows XP.  A couple of queries: I installed VS 2015 Community on a new Windows 10 pc and registered for the 30 day trial of VC 2.3.  In the link sent back, Step 1 - Useful Download Details, states that there are two versions of Visual Cobol available to download, VC for VS 2012 and VC for VS 2013, yet under the Software/Licenses section at the bottom VC for VS 2015 is also available for download, so this is the one I chose.  Are the instructions on the link out of date?  I assume it was safe to download VC for VS 2015 if VS 2015 Community is installed? The target framework for the VC 2.1 version of the app is either .NET framework 4 Client Profile for the windows forms projects, or .NET framework 4 for the non wi

Hello, I need to call Windows API function from managed COBOL. In native COBOL I'd write something like environment division. special-names. call-convention 74 is WAPI. ... working-storage section. 01 VersionInfoEx.   03 dwEVersionInfoSize        DWORD.   03 dwEMajorVersion           DWORD.   03 dwEMinorVersion           DWORD.   03 dwEBuildNumberFull.      05 dwEBuildNumber         USHORT.      05 dwEMajorAndMinor       USHORT.   03 dwEPlatformId             DWORD.   03 szECSDVersion             pic x(128).   03 wEServicePackMajor        WORD.   03 wEServicePackMinor        WORD.   03 wESuiteMask               WORD.   03

I'm having trouble reading a xml, which contains the identification of tags at the root of which possesses 31 IDs (namespace). I can not change the file because it is a layout I get in a query.I did several tests, and identified that 29 leaving only the cobol can make reading, leaving with 30 or 31 -9 error occurs (that is not in XML format) read routine.Under a program I made an example and an example of XML.----------------------------------------------------example.cbl---------------------------------------------------- $set preprocess(prexml) warn endp IDENTIFICATION DIVISION. PROGRAM-ID. TESTE. ENVIRONMENT DIVISION. CONFIGURATION SECTION. INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT XML-FILE ASSIGN TO "file.xml" ORGANIZATION IS XML DOCUMENT-TYPE IS OMITTED FILE STATUS IS XML-FILE-STATUS. DATA DIVISION. FILE SECTION. XD XML-FILE. 01 ROOT IDENTIFIED BY "root" COUNT IN ROOT-COUNT. 03 TAG1 IDENTIFIED BY "tag1" COUNT IN TAG1-COUNT. 05 DET1 PIC X IDENTIFIED BY "det1" COUNT IN DET1-COUNT.

Hi all, We have Acuserver running on a Windows 2003 server. Our application is an ERP. Is it possible to check what files Acuserver handles when running the application from the same physical server and not from any client? I suppose it should be something in the FILE_PREFIX entry of the configuration file. Thanks

I have been testing Visual Cobol against an older Cobol main frame system and just have a question about Z Zero Suppression Here's a sample program IDENTIFICATION DIVISION. PROGRAM-ID. EXAMPLE. ENVIRONMENT DIVISION. INPUT-OUTPUT SECTION. DATA DIVISION. WORKING-STORAGE SECTION. 01 TEST-RECORD. 05 PR-NUM PIC 99v99. 05 PR-NUM1 PIC ZZ.99. PROCEDURE DIVISION. PARA-1. Display "Enter number" ACCEPT PR-NUM move PR-NUM to PR-NUM1 DISPLAY PR-NUM1 STOP RUN. When I run the program in Micro Focus Cobol and enter in the following data 0328 I get 28.00 which is not right. When I run the program in our older mainframe and enter in the following data 0328 I get 3.28 which is to be expected the leading zero is suppressed. Not sure how to get Zero Suppression working in Micro Focus Cobol

To use activex pdfcreator-2.4.0 should generate the .DEF file as follows AXDEFGEN PDFCreator.PDFCreatorObj PDFCREATOR.DEF This is due to a change in the com interface not seen since the version 2.0.0Greetings.

Problem How to deploy native applications built with Visual COBOL 2.3 to 6.0 on the network? Solution The following instructions are based on a 64-bit Windows environment where: the 32-bit software is installed in C:\\Program Files (x86) Windows keeps the 32-bit system files in C:\\Windows\\SysWOW64 Windows keeps the 64-bit system files in C:\\Windows\\System32. On a 32-bit Windows environment, the software is installed in C:\\Program Files, and Windows keeps the system files in C:\\Windows\\System32. Development requirements: Compile the native COBOL programs with the dynamic link setting. Click Properties under project Click the Link property Select Dynamic checkbox Rebuild solution There are two series of preparations to be done on both server and client sides to allow the COBOL applications to be launched from client machines. Server setup: 1. Install COBOL Server and its Patch Update (PU) at the same level or higher as the one on Visual COBOL.2. Go to Start > All Programs &

Problem: How to deploy native applications built with Visual COBOL 2.2 Update 1 and Update 2 on the network? Solution: The following instructions are based on a 64-bit Windows environment where: the 32-bit software is installed in C:\\Program Files (x86) Windows keeps the 32-bit system files in C:\\Windows\\SysWOW64 Windows keeps the 64-bit system files in C:\\Windows\\System32. On a 32-bit Windows environment, the software is installed in C:\\Program Files, and Windows keeps the system files in C:\\Windows\\System32. There is a new method of running an application over the network since Visual COBOL 2.2 Update 1. It consists of using the "runtime launch configuration file", which does not require to run mfcesd.exe explicitly from a .bat file from the client machines. Development requirements: Compile the native COBOL programs with the dynamic link setting.   - click Properties under project   - click the Link property   - select

Problem: How to deploy native applications built with Visual COBOL 2.2 on the network? Solution: The following instructions are based on a 64-bit Windows environment where: the 32-bit software is installed in C:\\Program Files (x86) Windows keeps the 32-bit system files in C:\\Windows\\SysWOW64 Windows keeps the 64-bit system files in C:\\Windows\\System32. On a 32-bit Windows environment, the software is installed in C:\\Program Files, and Windows keeps the system files in C:\\Windows\\System32. There are two series of preparations to be done on both server and client sides to allow the COBOL applications to be launched from client machines. Server setup: 1. Install COBOL Server for the intended Visual Studio version (cs201x_22.exe)2. Go to Start > All Programs > Micro Focus License Manager > License Administration3. Install the license4. Click Options > Advanced Configuration5. Change the value for License Server with the current server's na

I'm trying to set the data file path for an mf cobol project. I've tried setting COBDATA in App.config but that get a fil status 35 on the file. If I move the file to the object code directory the file reads no problem. Is there maybe another variable to set in MF cobol

I have a dialog screen with a text entry field (class library field). After the first character I start a search and display a listview. So far so good. I want to have back the focus on that text entry field.   After the statement   SHOW-WINDOW WIN-MAT   I have the following statements   MOVE “SET-FOCUS” call-function(1) CLEAR-CALLOUT-PARAMETERS $NULL CALLOUT "matxtfld" 0 $NULL    (matxtfld is the modified efdemotxtfld.cbl) It doesn’t work, maybe I have to add the Statement SET OBJECT-REF(1) , but to what? Can someone give me a hint Regards, Georg

Please, have example how to insert rows in JTable, or how implement DefaultTableModel, in a Managed Cobol#JTable#VisualCOBOL

Hi all, I use NE 5.1 and want to use fileshare. What is the best Approach?