Rocket® COBOL

Problem: How do I compensate for different printer's printable area's? Resolution: See attached example (POffset.zip) Attachments: POffset.zip Old KB# 6128

Problem: Is there a normalize data file example? Resolution: See attached source code example. Attachments: normal.cbl Old KB# 6136

Problem: Is there a POP-UP window example? Resolution: See the attached source code example. Attachments: window.cbl Old KB# 6147

Problem: shmem Checksum error Resolution: This message indicates a shared memory  problem. The only recourse is to reboot. Old KB# 6534

Problem: No Applicaton Server licenses available, but there is an adequate supply of licenses which are not in the "system" (timeout) state. The directory to which COBDIR points is not the actual directory but a soft link to it. Resolution: Although not officially supported, experience has shown that users' COBDIR value may be to a soft link rather than the actual Micro Focus product installation directory.  However, this does not hold true for the license installation via apptrack.  The user who runs apptrack to install the Application Server license(s) must have COBDIR set to the actual directory name, not the name of a soft link. In general, Application Server licenses are bound to the COBDIR-specified directory at the time the licenses are installed.  On systems with multiple product installations, care must be used in the setting of COBDIR relative to the prodoct for which the licenses are intended. &nbsp

Problem: Is there an index file handling example? Resolution: See attached source code example. Attachments: ismalt.cbl Old KB# 6132

Problem: How can I prevent or terminate disconnected WOW Thin Client Server process? Resolution: Use the Server configuration option under the [ServerConfig] section of the Server rpcplus.ini file: InactiveLimit This option specifies the maximum amount of time a server will wait for an already connected client to make another remote program call. Also, try UseKeepAlive, also in the [ServerConfig] section of the Server rpcplus.ini file. This option checks for connection terminations at the TCP/IP level. For it to work, the TCP/IP parameters KeepAliveTime and KeepAliveInterval must be set in the Windows system registry or the UNIX/Linux kernel. The Windows default is 2 hours. If you want to set a shorter time period, use regedit and go to: HKLM\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters Add two DWORD Parameters named "KeepAliveTime" and "KeepAliveInterval". The values depend on what time you'd like. For example: if you use 600000 (ms

Problem: How do I round numeric data? Resolution: See the attached source code example. Attachments: round.cbl Old KB# 6139

Problem: 173 on CBL_NLS_GET_MSG when trying to run an EXE Resolution: This error may be caused by only doing one call to DSRUN on a DS Screen push button. The Push Pop demo shows that in some cases you have to do one call to DSRUN to Quit Set, and another call to Continue. Old KB# 6573

Problem: Is there an example LINAGE clause code? Resolution: See attached example source code. Attachments: linage1.cbl Old KB# 6134

Problem: When you save the screenset how does it know what STYLENAME to use? Resolution: If you specify a font side file and save a screenset, the characteristics of each defined style are saved in a text file with a .dft extension whenever the screenset is saved. The screenset can contain fonts defined in more than one environment. In this case entries are generated for each environment. If the file already exists, the styles are appended. For example, if you use a style name of "Heading1" to represent a typeface of Helvetica (Helv under Windows) bold 12 points, Dialog System saves the following definition in the .dft file: [WINDOWS] FONT-RECORD     STYLENAME Heading1     ATTRIBUTES BITMAPPED, PROPORTIONAL     POINTSIZE 12     TYPEFACE "Helv" END-RECORD Old KB# 6570

Problem: Do you have any split key examples? Resolution: Yes, please see the two attached source code examples. Old KB# 6145

Problem: How do I print rotated text? Resolution: Use the "P$SetFont" call with the LF-EscapementParam parameter.  See attached example POrient.zip Attachments: POrient.zip Old KB# 6127

Problem: How can I return a value to the O/S upon termination? Resolution: See the attached source code example. Attachments: returnc.cbl Old KB# 6138

Problem: How can I test a field to see if it is alphanumeric? Resolution: Please see the attached source code example. Attachments: alpnmtst.cbl Old KB# 6131

Problem: This is a result of using the wrong program for the List View. Resolution: Make sure the assosiated program for the List View is actually the generated program for it.  Just verify the properties of the List View control from the screenset to know the exact program name. Old KB# 6552

Problem: Is there a way to copy a file to/from a UNC path from a COBOL program? Resolution: You could do a CALL "SYSTEM" or use the BinaryFileCopy.zip attached. The library it contains will copy a file from a network UNC to a printer via a UNC from RM/COBOL. The attachment includes the C source, the CodeBridge template and a COBOL example. Disclaimer This is not an official Liant Software Corporation product and is therefore unsupported although enhancements and fixes will be considered time permitting.  Please forward any queries to the London office of Liant Software at support@liant.co.uk.      Attachments: BinaryFileCopy.zip Old KB# 6130

Problem: On some instances, the focus mark on a radio button is not seen. The radio button can be selected, but the focus mark is not seen. This behavior only occurs in Windows 2000 and Windows XP. Resolution: This is not a bug, but it is actually an operating system setting issue. To be able to see the focus mark on the radio buttons, the "Hide underlined letters for keyboard navigation until I press the Alt key" option must be unchecked from "Display Properties > Appearance > Effects" in Windows XP and from "Display Porperties > Effects" in Windows 2K. You can get to Display Properties by right-clicking on your desktop and clicking on Properties -OR- by going to Start > [Settings] > Control Panel > Display. Old KB# 6571

Problem: What is the correct way to configure/debug WOW Thin Client on a UNIX system? Resolution: First, make sure that you are using the version of WOW Thin Client on the Windows system that matches the version of the runtime. You cannot mix versions. Next, make sure you are using a Runtime Plus version or Development version of the runtime on the UNIX/Linux system. The Runtime Plus and Development versions support Thin Client, while the regular Runtime does not. If unsure, contact Support and give us the serial number; we can check for you. For normal execution: 1. Make sure the rpcstart script has execute permissions. For this example, it is located in the /usr/rmcobol directory and should look like this: #!/bin/sh # TERM=dumb; export TERM RM_LOAD_WOW_CLIENT=yes; export RM_LOAD_WOW_CLIENT cd /usr/rmcobol && runcobol ./helowrld.cob k (You can locate the rpcstart script anywhere, but make sure the rpcplus.ini file is in the same directory, and have the script change to th

Problem: Moving Dialog Systems screensets from UNIX to Windows Resolution: Dialog System's screensets that were created under UNIX can also be used on Windows with the 32-bit Dialog System character runtime. There is an important consideration in how to build those screensets. Under UNIX, the names can be in upper, lower, or mixed case. Windows Dialog System is expecting upper case. It's important to build your screensets under UNIX using upper case names. Old KB# 6560

Problem: How do I correctly specify the inetd.conf entry for WOW Thin Client? Resolution: The /etc/inetd.conf (UNIX systems) entry for WOW Thin Client should read: rpcplus stream tcp nowait root /bin/sh rpcplus /usr/rmcobol/rpcstart The "rpcplus" part of this entry will show up in a process table listing (ps command). The "root" part of the entry may be changed to which ever account you wish to run the service. The beginning of the usr/rmcobol/rpcstart file (or where ever the rpcstart file is located), should have the following as the first line: #!/bin/sh Remember to do a kill -HUP on the process ID of inetd whenever you have changed the configuration file. This will save you having to reboot the system.      Old KB# 6438

Problem: Dialog starts but the toolbar and shortcuts are white and the menu bar function doesn't do anything. Resolution: Check your system for the runtime modules Pan2nt.dll. If it is in a directory other than the cobol32\\exedll or Net Express\\base\\bin, delete it and reboot the machine. Old KB# 6555

Problem: Sample Scenario: When a user clicks on a bitmap they may have the option to go out to MS Paintbrush and change the bitmap. However, if they select the bitmap again while still in that same run unit it will display the original bitmap prior to being changed. It is not until they exit the screenset and re-load that the changed bitmap will be displayed. Resolution: To dynamically change a bitmap you should associate a master field with the bitmap object first. This means that you just need to populate the PIC X(..) master field with the path to the bitmap and then then do a REFRESH-OBJECT on the bitmap control. Old KB# 6568

Problem: An application that is running in Net Express using the COBCONFIG_ variable to point at a .cfg file that contains the entry: "set printer_redirection=TRUE" This correctly sends the output to the spooler rather than the LPT port. However, when the application is deployed against Net Express Application Server the output goes straight to LPT1 rather than the spooler. Resolution: The cobconfig_ setting isn't linked in any way to the application. When deploying you need to set cobconfig_ as a system environment variable to point at the .cfg file that you have created that contains the printer_redirection=TRUE in order for it to be picked up by the application. Old KB# 6539

Problem: Dialog System Error 3, 52, 55 on RETC. Error 4/007 on a read. Resolution: This error occurs as a result of application processing which causes a change of directory for the current process. Unless Control bit 3 is set (DS-NO-NAME-INFO) then each RETC will result in the screenset being reloaded to retrieve the name details for the currently active object when the RETC occurs. If the screenset is not on COBDIR or the full screenset file path name is not specified, then the file open will fail as a result of the change in directory. This subsequently causes the file read fail 47. Old KB# 6565