Rocket® COBOL

Problem: How do you merge an Enterprise Link 3.1 cfg file to version 5.0? Resolution: EnterpriseLink for Solaris keeps configuration settings in a file config/EnterpriseLink.cfg in the EnterpriseLink configuration directory. When installing EnterpriseLink 5.0 it will install EnterpriseLink.cfg with all of the settings needed for correct EnterpriseLink 5.0 operation.  It will not copy your EnterpriseLink 3.1 configurations, you must make changes manually either using the web page interface through http://machine-name/stadmin or using a text editor such as "vi" on Solaris. For example, the default EnterpriseLink 5.0 config file will be: [Server] DatabaseType=ODBC DataStreamFile=elhome/logs/Server.rep DebugLogFile=elhome/logs/Server.log ErrorDirectory=elhome/errors DisconnectPage=SSDISCONNECT RepositoryDSN=ELRepository RepositoryPassword= RepositoryUser= TerminalType=IBM-3278-2 MaxSessErrMsg= AdvanceBackward=4 ConnectionTimeout=10 Deb

Problem: Invalid Procedure Name P224 / DSRUN Error 8,0,0 Resolution: Move the Screenset datablock from Working Storage into the Linkage Section. Old KB# 6572

Problem: DSRUN error 17,920,3 -- The bitmap '12345678.bmp'could not be found Resolution: It seems in 32bit, a byte should be allocated for the null character I.E.: if the filename with the dot and extension is 12 bytes, then the field to contain this filename should be 13 bytes. Otherwise, the DSRUN error 17,920,3 will occur (e.g. The bitmap '12345678.bmp' could not be found.) Therefore, make sure the field that contains the bitmap file names is one byte bigger than the actual size of the bitmap filename including its dot and extension. Old KB# 6564

Problem: Application Server appears to have been installed incorrectly. Resolution: The Application Server licensing directory should contain a file called semfile, with full access permissions to all users. Old KB# 6536

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: 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: Sometimes it is useful to generate a .cpb (copybook) file for a screenset via batch processing. How can I do this? Resolution: Open a Net Express command-line and go to the folder to find the related screenset. You should enter now: dswin /g screenset-name This produces the .cpb file related to screenset. Old KB# 6556

Problem: How to get  Message Box to stay on top Resolution: right mouse click on message box and click on properties On the general tab there is a Parent selection field If you select $WINDOW , then the message box will stay on top. Old KB# 6557

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: 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: Applications initially developed with COBOL WorkBench use the OEM format for data when Net Express ( and Dialog System of Net Express) use ANSI format. How to correctly display OEM characters under Dialog System? Resolution: Add the following Function at the Global Dialog SCREENSET-INITIALIZED       CALLOUT-PARAMETER 1 CONFIG-FLAG $NULL       CALLOUT-PARAMETER 2 CONFIG-VALUE $NULL       MOVE 16 CONFIG-FLAG       MOVE 1 CONFIG-VALUE       CALLOUT "dsrtcfg" 3 $PARMLIST this dsrtcfg call is documented in Dialog System: Display Character Set Conversion By default, the Dialog System run-time assumes that data passed to it is encoded for correct display in Windows environments, that is, the passed data will have a correct visual representation when Windows displays the characters using the ANSI

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

Problem: Calling the aslmpclocate the error:  "fail 0000000099" appears even after entering the key in the registry. Resolution: This error message means that there is/was a problem with the Admin rights on this machine/server. You need Admin-rights for the Registry Key SOFTWARE before it will function properly. Old KB# 6538

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: How do I sort relative files? Resolution: See the attached source code example. Attachments: sortrel.cbl Old KB# 6144

Problem: How can I get correct positioning with DISPLAY in pop up windows? Resolution: The LINE / POSITION is relative to the popup window, not the runtime window. Old KB# 6129

Problem: How can I use C$SCRD to create a print file? Resolution: See the attached source code example. Attachments: scrd.cbl Old KB# 6140

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: 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: How do Isearch a HEX table? Resolution: See the attached source code example. Attachments: searchx.cbl Old KB# 6143

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

Problem: How can I use ACCEPT to test for an escape key with a SCREEN SECTION? Resolution: See attached source code example. Attachments: scrntst.cbl Old KB# 6141

Problem: Is there a line draw graphics example? Resolution: See attached source code example. Attachments: linedraw.zip Old KB# 6133

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

Problem: Why are my bitmaps not displaying in my WOW Thin Client application? Resolution: The WOW bitmap control invokes the Windows API.  Since WOW Thin Client calls the Windows API on the client machine, any bitmap file that you wish to display needs to be accessible to the client machine. *The WOW bitmap control can use the RUNPATH environment variable/synonym to locate files on the client PC.      Old KB# 6447