Rocket® COBOL

Problem: Load error 164 on cobdirect.so.2 Resolution: Set COBMODE=64. Old KB# 7176

Problem: /usr/lib/cmplrs/cc/ld: Can't locate file for: -lclntst8 Just upgraded from Oracle 8 to Oracle 9 and trying to compile program with embedded Oracle SQL Resolution: The system loader (ld) is looking for libclntst8.so in $ORACLE_HOME/lib. The client-side library has a different name for each major release of Oracle, i.e. libclntst8.*, libclntst9.*, libclntst10.*. Update the cob command line accordingly for the Oracle client version in use. Old KB# 7210

Problem: Dialog System  screensets are not found or loaded at run time Resolution: In order to use directories other than the directory containing the application program, the user needs to set COBDATA to point to the location containing the screensets - ie Dialog system treats the screenset files as data files to be read when the screenset is initialized. COPYFILES can be placed in other directories and the COBCPY variable is used to point to the locations to be searched by the COBOL compiler and Animator Old KB# 7164

Problem: Message comes from linker (ld) command near end of cob -x or cob -z Resolution: It is not possible to link 32 bit objects to 64 bit code and vice-versa.  Make sure all  dependent modules are compiled under the same COBMODE setting.  Make sure any compiled Cobol code is consistent with any object modules supplied by a third party.   Old KB# 7167

Problem: Cannot load CMDLINE.SAV Resolution: If the COBDATA environment variable is set, this error can be resolved by unsetting COBDATA or adding a colon (:) to the end of the contents of the COBDATA variable. Old KB# 7182

Problem: Using byte stream file handling and cbl_read_file is not returning any data. Return-code = 0 on  the cbl_open_file and receives Return_Code = 0 on the cbl_read_file but no data is received into his input buffer- Resolution: One of the parameters for the cbl_read_file is flags. This parameter can take the following values:           0 Standard read       128 Return the current file size in file-offset Need to make sure after the initial read to obtain the size of the file that the flags is set to 0 to do a standard read. Setting the flags to 0 resolved the no data returned in the input buffer issue. Old KB# 7148

Problem: Sometimes in COBOL applications there is a requirement for pausing execution of an application before continuing.  Most techniques for doing this involve tying up the processor (e.g. performing a large 'perform varying'), to the detriment of other users. Resolution: One method worth trying is to use  call "SYSTEM" and call a UNIX script containing a sleep statement.  e.g. working-storage section. 01 w-call-sleep.     03  filler pic x(7) value "sleep 5".     03  filler  pic x value x"00". procedure division.    ..........     ...........     call "SYSTEM" using w-call-sleep     ............    ............. The parameter for sleep is in whole seconds, and there may be OS discrepancies of up to one second

Problem: Using "cob -x" to rebuild an application that includes some C source code, a customer was getting error "cannot access cc". Resolution: The "cob -x" command, when given C source code (.c) as an argument, invokes the C compiler that comes with the UNIX operating system.  In the case of Solaris, this is the Forte product from Sun.   If the C compiler is not installed, or if the PATH environment variable is set such that the "cc" command cannot be found, then this error appears. The solution is to purchase and install the C compiler, or to update the PATH environment variable so the "cc" command can be found. Old KB# 7203

Problem: When compiling, you get the following error message:           cob32: can not execute CC Resolution: Use the command "which cc" or "which CC" to find out whether there's a "cc" or "CC" command on the path and if found, what directory is it in.  Also try the command "CC -V" or "cc -V" to give you some version information about your C or C compiler (respectively).  If those commands cannot find it, then the "cob" command won't find it either. It is possible that the system has no C (or C compiler) installed, which would obviously cause the "CC" command to fail The least likely, but another possible cause, is that the "CC" (or "cc") command is present in a directory specified on PATH, but the user lacks permission to run it. Old KB# 7163

Problem: How to specify SIGN=EBCDIC in cobopt Resolution: insert line containing: -C sign=ebcdic in the cobopt file using text editor of your choice Old KB# 7159

Problem: Earlier COBOL products for both Wiindows and Unix products contained a family  of Call-by-number routines to read and write characters and attributes to and from the screen. These are not available in Server Express Resolution: A lot of the call-by-number routines were replaced by call-by-name routines many years ago, but the call-by-number routines were kept in the product to assist migration.  They've now been removed entirely.  The replacements for x'B7' and x'B8' are as follows: B7 0 cbl_read_scr_chars B7 1 cbl_write_scr_chars B7 2 cbl_read_scr_attrs B7 3 cbl_write_scr_chars B7 4 cbl_write_scr_n_char B7 5 cbl_write_scr_n_attr B8 0 cbl_read_scr_chattrs B8 1 cbl_write_scr_charrts Refer to the product documentation for full details of how to use these calls. Old KB# 7187

Problem: What is the 'mfdebug' terminal setting? Resolution: When running under the control of the Animator any screen output is cached in memory. If you swap to the user screen (i.e. by pressing F2 or by executing an ACCEPT), the contents of the cached screen are displayed. The program has no terminal of its own because it's under the control of the animator. So, when the program writes to the terminal, it is actually passing terminal sequences to the animator to be decoded and cached. The Animator uses a generic terminal definition called 'mfdebug', which defines all the capabilities required. Because of this it is not recommended that the screen-swap Animator be used if a non-COBOL sub-program is performing a lot of screen I/O. A better solution is to use cross-session animation. This is documented in  the Debugging Handbook. Old KB# 7173

Problem: In Server Express, enter sde, for development environment. Press F3=compile, compile options are not displayed Resolution: If function keys do not appear to work as expected, enter the meta character / before the number of the function key. For example F3 would be /3 and the compile options would be displayed properly. From within sde enter /m for Keyboard Mapping Help for current mapped key assignments. Old KB# 7188

Problem: tar command reports a error while trying to extract COBOL product components: Resolution: This error occurred due to a lack of space in the target install directory. create a new, larger file partition and the problem is solved. Attachments: Relativity launch error 2009-02-19.doc Old KB# 7156

Problem: Byte stream I/O routine CBL_OPEN_FILE failes with error 194 when the file is large Resolution: Setting ACCESS-MODE = 65 corrects the problem - the call will fail if the underlying operating system does not support large files Byte Stream IO calls work with files up to 4 Gb,  Over 4 Gb there is a requirement  to set 1 of 2 flags to get the open to work: - bit h"40" of the open-mode field (second parameter) or; - bit h"10" of the sharing mode field (third parameter). Using method 1 you will get an error if the open is attempted on a system which does not support 64 bit file systems (e.g. Windows 95). Method 2 will give you a successful open in all operating systems, but tells the run-time that no locking calls will be attempted on the file.  Any call to e.g. CBL_GET_LOCK will result in an error if the file has been opened with this bit set. Old KB# 7184#netexpress#RMCOBOL#ServerExpress#COBOL#AcuCobol

Problem: During batch compiles  a 197 error is returned - The file referenced is inoc.gnt. Resolution: This error originates from the license manager trying to display "no licenses available" with no tty devices available for output. User can utilize the  LMFWAIT environment variable in order allow for licenses to properly checked back in to the license manager See the Development System Licensing Guide, Chapter 2. Administering the License Management Facility for more details. Old KB# 7170

Problem: What is the minimum hardware specification for our UNIX products? Resolution: The minimum required disk space to install the COBOL product is approximately Object COBOL: Development System: 40Mb Application Server: 20Mb Server Express: Development System: 50Mb without ODBC, 80Mb-100Mb with ODBC drivers Application Server: 40Mb There is no required minimum for physical memory, any system capable of running the UNIX operating system provides the minimum required memory for the COBOL product to execute. The minimum required memory for user applications really depends on the size of those applications and how they are used. It takes more memory to edit a 20,000 line program than it does to edit a 1,000 line program, for example. Applications that use INT and GNT code will take more memory than those using callable shared objects or executables because INT and GNT code is not shared between users. Large FD's and working-storage tables will als

Problem: Using either cob -ivt db2test.cbl -C "DB2(DB==SAMPLE)" or cob32 -C nolist -ivt db2test.cbl -C DB2(DB==SAMPLE) results in * Micro Focus Server Express         V2.2 revision 000           Compiler * Copyright (C) 1984-2003 Micro Focus International Ltd. URN RXCAI/AA0/00000 * Accepted - verbose * Accepted - reentrant * Accepted - nolist * Rejected - DB2(DB=SAMPLE) * 155-U 155     Illegal command line Resolution: One may see this error if 1. the DB2 ECM is not present- that means that the product does not support the precompiler on the specified platform. UDB isn't available on all UNIX platforms. Therefore, we only provide the DB2 ECM module on platforms where UDB is available, and IBM supports precompiling COBOL. Check to make sure that the platform supports UDB. 2. If the LIBPATH is not set correctly. Che

Problem: 198 load Failure with MQ Series Programs Resolution: Need to create a non-threaded verion of the MQ series module using the command:   cob -z -e "" -Q -bE:mq.exp pgm.cbl -lpthread -L/usr/lpp/mqm/lib -lmqmcb to create a callable shared object for MQ series. Old KB# 7161

Problem: If you are linking a Cobsql application with the Cobsql CSTOP option specified, the following error will be returned : ld: 0711-317 ERROR: Undefined symbol: .oraprot Resolution: The CSTART and CSTOP Cobsql directives are not supported on UNIX. More recent versions of Server Express will reject these options at compile-time. Old KB# 7204

Problem: The following demo shows the use of 'initialize' on a group field.  It returns a value of 'wwxxyy' whilst you may have expected a return of spaces.        working-storage section.        01 aa.            03 bb.               05 filler       pic xx occurs 10.            03 cc              pic x(10) value "wwxxyy".        procedure division.            move "ppqqrrss" to bb            initialize aa    &nbs

Problem: A programmer uses the REMOVE compiler directive to take a reserved word out of action, and they do this generally (for all programs), but in one certain program, they would like to restore this reserved word.   How can this be done? Resolution: Use the ADDRSV compiler directive, and put it in a $SET statement in the source code of the program in question.   Even though the REMOVE directive is specified on the "cob" command line,  $SET statements override settings made elsewhere, so $SET ADDRSV will restore the reserved word.   Here is an example: ---------------------  driving shell script --------------------------------- # compile the program with the reserved word SUBTRACT # removed from being a reserved word (compilation should # fail because the program uses SUBTRACT) cob -C REMOVE\\"SUBTRACT\\" -v  addrsv_not_there.cbl echo; echo; # Now try a

Problem: When trying to update the Net Express product it states that the DSY (Dialog System) Websync cannot be run because Dialog System is not installed. Resolution: During the initial install of Net Express if "Custom install" was not choosen, then the Dialog System option does not install. The installation CD can be reinserted and run again - choose custom and it will determine which components have not been installed and let you choose them. After installation is complete the websync can be run again. Old KB# 7146

Problem: When selecting "open" files in the IDE - showing the list alphabetized backwards. Resolution: Net Express displays listing topics the same way as it is set in Windows. Go to Windows Explorer, then go to the same directory as you are listing in the IDE. Click on the "name" title bar - this will sort - if it sorts backwards then click again until it is in the desired alphabetic order. Go to tools - folder options - view tab - click on button that reads "set like current folder" and click ok - get out - close Net Express and then reopen Net Express. Old KB# 7147

Problem: You get the following message on Sun Sparc Solaris with Server Express: /tmp/cobAAAmZaaPD/%cob0.s: Assembler messages: /tmp/cobAAAmZaaPD/%cob0.s:36: Error: Unknown segment type /tmp/cobAAAmZaaPD/%cob0.s:36: Warning: rest of line ignored; first ignored character is '"' cob32: error(s) in assembling /tmp/cobAAAmZaaPD/%cob0.s Resolution: Solution is copy the GNU Versions to another name like cp /usr/local/bin/as    /usr/local/bin/as.gnu cp /usr/local/bin/ld    /usr/local/bin/ld.gnu cp /usr/local/bin/make  /usr/local/bin/make.gnu Then the cob command get the assembler of the Sun C Compiler Old KB# 7211