Rocket® COBOL

Problem: A screenset is created in Dialog System on a monitor set at a resolution of 1024 x 768.  However, when the programs are run on a monitor set at 800 x 600 the fonts and bitmaps present in the screenset change size etc. There is, however, a way to prevent this from happening.      Resolution: Multiple Resolution and Dynamic Window Sizing Both the multiple resolution and dynamic window sizing features are enabled by a CALLOUT to "dsrtcfg" with a flag of 9 and an identifier that tells Dialog System what resolution the screenset was defined in. Dialog System uses Panels V2 generic coordinates, which provides a basis for cross-resolution support and compatibility with differing graphics adapters. This results in differing coordinate values for what otherwise appear to be the same resolution value. To check the value you need for your definition platform, a verification program is supplied with Dialog Sy

Problem: Is there a CodeBridge wrapper for Windows FindFile functions? Resolution: Attached to this solution is a zip archive containing the necessary CodeBridge template, a test COBOL program, and a pre-built DLL. Attachments: rmfindfile.zip Old KB# 4697

Problem: What is the maximum size of master field for Dialog System's Multiple Line Entry (MLE) field? Resolution: The maximum size for a master field is 65535 bytes (64K - 1 byte). In other words, PIC X(65535) is the maximum size. Therefore, that is the same maximum size for a master field to be associated with MLE. It is worth to note that the 64K limit that is specified in the documentation is for the size of the Data Block in 16-bit environment only. There is no limit for the Data Block size in 32-bit environment. Old KB# 5014

Problem: The message "Variable Syntax", and not the usual AppTrack options, may be returned when running apptrack in Application Server. Resolution: If you are running apptrack from csh try instead from sh and this should solve the problem. Old KB# 5006

Problem: How can I export a large number of repeating data elements in XML? Resolution: Some uses of XML manipulate large documents that consist of a large number of repetitions of a few data items.  An example of this is the ability of many relational database packages to output result sets as rows encoded in XML.   One very straightforward way to create these large documents is to use the LINE SEQUENTIAL file access method and COBOL procedural statements such as STRING to create text records.  For simple applications where requirements are well understood and stable, this approach should work well. The attached example uses a different approach.  The output is segmented into pieces that can be conveniently accommodated in a COBOL array (using the OCCURS clause).  These pieces are then exported, using XML EXPORT FILE, into a temporary XML documents.  Finally, when all the pieces have been exported, the temporary d

Problem: What is causing an Error 28[14] in LoadDocument during XML Import? Resolution: One main cause of this is that the schema file (.xsd extension) is among the model files.  If the schema is present, the LoadDocument validates the input document against the schema.  Unfortunately, most input documents are not schema-valid at this time, so the LoadDocument fails. Old KB# 4710

Problem: Problems  still exist with running the service packs for the silent install of application server for Net Express 4.0 with .NET Resolution: Steps to do Silent Install of Application Server for Net Express 4.0 with .NET including the service packs. Step 1. On the machine you plan to do the Silent Install of Application Server, run the MFSUPPORTINFO utility and check to see if any Net Express development products are installed. Note: the MFSUPPORTINFO utility is located at www.microfocus.com at the top , click on Support login to Supportline on the left under Self-Service , click on Net Express Examples and Utilities click on Samples click on Utilities scroll down until you see MFSupporInfo.zip Step 2. From the Application Server for Net Express with .NET cd,  copy the Application Server folder down to a temporary folder on your machine ( c:\\apsne40 ) The installation for application server will then

Problem: An application with a splash screen will need to pause to allow the users to see the splash screen. Resolution: In the splash screen's WINDOW-CREATED event, a TIMEOUT function can be used to pause for certain time. The syntas is as follows: TIMEOUT time procedure-name where time is in 1/100th of a second where procedure-name will be executed after reaching the amount of time Example: WINDOW-CREATED             TIMEOUT 1000 TERMINATE-WIN      TERMINATE-WIN             TERMINATE *This procedure times out for 10 seconds and terminates the window Old KB# 5010

Problem: Is there an example on how to use C$MemoryAllocate? Resolution: Yes. Please see attached. Attachments: build-data-items.cbl Old KB# 4693

Problem: How can I read/write from/to a UNIX named pipe? Resolution: See the attached source code examples. Old KB# 4682

Problem: How can I do a ProtocolTrace on the Windows client side? Resolution: You can enable TCP/IP protocol tracing on the client side with the following: 1. Back up your registry, then with regedt32 add a key to HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI\\ named "Simba Client" 2. In the "Simba Client" key add these String Values: ProtocolTrace and TraceOutput 3. Set ProtocolTrace equal to 7 4. Set TraceOutput to the desired trace file name (ex: C:\\temp\\trace.log) in the same section. Produce the output and send the log file to Liant support.      Old KB# 4649

Problem: How can I convert a 6 digit date to an 8 digit date? Resolution: Please see the attached Cobol program sample code. Attachments: cnvtdate.cbl Old KB# 4684

Problem: How can I use JDBC with Relativity on Windows XP? Resolution: The JDBC client application needs to communicate with a server, so you must be running Relativity Data Server, not Relativity Data Manager, on Windows XP.  JDBC clients have no mechanism to connect to Relativity Data Manager other than the use of a JDBC-to-ODBC bridge, which is not recommended. Old KB# 4645

Problem: To whom should I direct questions about Cobol-RPC? Resolution: While Liant does support Cobol-RPC that is purchased through us, England Technical Services (ETS) provides direct support for the product/versions purchased from them, or through their distributors. Old KB# 4671

Problem: How do I highlight / select all the text in an edit box automatically? Resolution: Simple, use... Call SendMessage Using Win-Return edit2-H Em-SetSel 0 -1. See the attached example.      Attachments: 27236.zip Old KB# 4652

Problem: How can I convert an alpha string to uppercase? Resolution: See the attached source code example. Attachments: upper.cbl Old KB# 4683

Problem: How can I fix a slowly query problem on Linux ES4 (CentOS 4)? Resolution: There is a known problem with version 11 (and previous versions).  However, there is a service pack available on ftp.liant.com.   Here are the instructions to install it: 1) ftp ftp.liant.com 2) Login with anonymous, using your email address as the password. 3) cd pub/rel/outgoing 4) binary 5) get reldbsrv1100SP2LNX.zip 6) bye 7) Unzip reldbsrv1100SP2LNX.zip.  The password is '30Nov07'.  Extract the contained file reldbsrv1100SP2LNX.tar. 8) Binary ftp reldbsrv1100SP2LNX.tar to the RelRM11.00 on the machine running the Data Server. 9) Login as root to the machine running the Data Server. 10) Change directory to the RelRM11.00 directory. 11) mkdir save 12) mv reldbsrv save 13) mv reldbsrv.rm save 14) mv relfm_rm.o save 15) tar xvf reldbsrv1100SP2LNX.tar 16) ln reldbsrv.rm reldbsrv 17) ./STOP 18) If the Dat

Problem: How do I convert Gregorian to Julian dates (and vice versa)? Resolution: See the attached source code example. Attachments: julian.cbl Old KB# 4681

Problem: How can I minimize record locking issues? Resolution: Please see the attached zip file for a procedure and supporting example program. Attachments: RecordLocking.zip Old KB# 4688

Problem: What is ODBCtest, and how can I get it? Resolution: Microsoft ODBC Test is an ODBC-enabled application that you can use to test ODBC drivers and the ODBC Driver Manager. To get it, go to: http://www.microsoft.com/downloads and search for MDAC. You should find a page where you can download the latest version of this product, of which ODBCtest (ODBCTE32.EXE) is a part: Microsoft Data Access Components (MDAC)      Old KB# 4651

Problem: How can you change the columns and rows for the runtime display? Resolution: You can use a configuration file and setup a TERM-ATTR configuration record and define the COLUMNS and ROWS which will be displayed on the terminal screen. A sample configuration file is in the installation folder, called WINDOWS.CFG. Old KB# 4660

Problem: Can my COBOL program call a Windows DLL? Resolution: Yes, it can - if you construct a COBOL-callable DLL that in turn calls the non-COBOL DLL.   The CodeBridge capability that comes with the RM/COBOL development system makes that task very easy in most cases.  Little or no DLL programming is required if CodeBridge can be used.      Old KB# 4643

Problem: Will Relativity Data Server work with an MF Application server? Resolution: No, the MF Application Server does not supply the necessary files to relink the Relativity Data Server. You must have a MF Development system to do the relinking. Due to licensing issues RM must be able to relink the Relativity Data Server with the customer's MF development system.      Old KB# 4648

Problem: How can I pass environment variables to the COBOL runtime? Resolution: See the attached source code example. Attachments: cpass.cbl Old KB# 4639

Problem: Why doesn't licverifyall on Unixware work with my v8 license? Resolution: If you get the error message: "The platform in the license does not match the platform of the product." It is because with the version 10 release, we replaced the Unixware platform code (60) with the same code as is being used for SCO OpenServer 6 (67) and the version of licverifyall on the website reflects this. Use the version of licverifyall from our v9 release instead (attached).      Attachments: V9Unixware-licverifyall.zip Old KB# 4676