Rocket® COBOL

Problem: When trying to link a program with Server Express on Solaris a number of messages are printed: ld: warning: global symbol '' has non-global binding:         (file /opt/lib/cobol/lib/libcobrts.so value=LOCL); ld: warning: global symbol '' has non-global binding:         (file /opt/lib/cobol/lib/libcobcrtn.so value=LOCL); ld: warning: global symbol '' has non-global binding:         (file /opt/lib/cobol/lib/libcobmisc.so value=LOCL); Resolution: These warnings can be safely ignored. When Micro Focus creates libcobrts it is necessary to "hide" symbols. Solaris does not provide options to do this so the attributes of symbols are changed in the dynamic symbol table. The symbol names are NULL, hence the '' in the error message. Old KB# 7231

Problem: A customer encountered this error when trying to open a relative file.  There was  an open on an I/O relative file and then in a subsequent subprogram a further open on it which results in it being already locked hence the 9/065 (or 9A). The customer then pointed out that this worked without problems in OCDS so why not in Server Express? Resolution: File locking in OCDS did not take into account the fact that you might have two opens on the same file and so did not handle locks between the two opens.  Under Server Express this is correctly handled.  However, you can put the incorrect OCDS locking back in. For compatibility with OCDS you can use the same_proc_excl_detection tunable. same_proc_excl_detection The same_proc_excl_detection tunable has been superseded by the intra_process_record_locking tunable. However, it can still be used for backward compatibility purposes. Note that we recommend that you

Problem: AIX customer upgraded to Server Express 4.0 and got this error when running a CICS application. The actual error is caused by a STRING...DELIMITED BY <literal> statement. This does not happen when the program is compiled to .int, only .gnt and executable. Resolution: A STRING statement is optimised to use the system commands memmove, memcmp and memcpy. However these are not picked up automatically in Server Express 4.0 and 4.0 SP1. The solution is to add entries in the liblist for executable programs (which Micro Focus did in SP1) and to rebuild the runtime, adding the appropriate programs with the -I (upper case letter between 'H' and 'J'), e.g. -I memmove -I memcpy -I memcmp. Unfortunately this isn't the whole story! As CICS works by demanding that everything is compiled into it, you also need to edit the cicsmkcobol script and run it. This rebuilds CICS and the Micro Focus runtime so that they work together. Micro Focus ca

Problem: Assembler messages: Error: Can't open Z for reading. Z: No such file or directory Z:0: Error: Can't open DA1.1 for reading. Z:0: DA1.1: No error cob32: error(s) in assembling /var/tmp/cobAAAa29655/ldtab.s Resolution: Check to see if you have the Operating System's ANSI C compiler and GCC compiler installed. The GCC compiler also installs its own assembler and will reference some of its own header files for C instead of using the Operating System's.   So ensure that it uses the right assembler, the Operating System's assembler, either by un-installing the gcc components or ensure that the gcc components are at the end of PATH searches and that it looks for the Operating System's ANSI C compiler first.     Old KB# 7214

Problem: In Server Express, when a record is read with lock and then within the same process another attempt is made to read the record the extended file status code 9/068 will be returned. This would typically happen where a program reads a record with lock, then calls another porgram and attempts to read the same record. In Object COBOL this lock is ignored and a file status of  '00' is returned but in Server Express 9/068 is returned. This only happens if the access takes place within the one process. Normal record locking applies to both products for for records lockded in another process. Resolution: It may be that you want Server Express to behave the same as Object COBOL Developer Suite, particularly in the case of legacy applications where the activation of the record lock is not expected. To disable the record lock and have a file status of '00' returned on the read of a record that has previously been read with lock within th

Problem: It would be useful if there were a way for Micro Focus COBOL to retrieve the user-id from the UNIX operating system --  the same user-id that the UNIX "id" command would show. Resolution: Micro Focus COBOL can call C routines directly, if the C routines have been linked with the COBOL run-time system.  A programmer would use the CALL statement, and put the name of the C routine in quotes. The UNIX system library "libc.a" (or "libc.so") has already been linked with the run-time system, so COBOL can directly call any of the UNIX system calls contained in "libc".  On most platforms, the intro(2) man page shows a complete list of these calls. getuid(2) is a system call contained in "libc", so COBOL can call it directly.  Consider the following program:         01 uid-ws pic 9(8) comp-5.      &nb

Problem: Investigating 173 error on calls to COBOL callable shared objects (CSO) and third party products Resolution: The first thing to look at is to check that the third party product is 32-bit if you are using the 32-bit version of the COBOL product or 64-bit if you are using the 64-bit version of the COBOL product. If your application uses more than one third party product, cut it down to a version that only includes the third party product that is giving you problems.  Once that is working you can start adding other products to your application. Check the third party documentation for libraries that have to be linked to your application. Sometimes your third party product provides 2 versions, one threaded and one non-threaded. Choose carefully the one that matches your application. If you are migrating from .int/.gnt code to callable shared objects, please notice that callable shared objects are executables to the OS and unlike .int or .gn

Problem: A program encounters file status 9/007 (which means "disk space exhaused") on a record sequential file open for output.  At the point of error, the file size is 512 bytes beyond 1 GB that is, 1073741312 bytes. Resolution: This file size limitation is not imposed by Micro Focus.  It is probably imposed by the UNIX system.    The default ulimit on AIX 5.2 is 2097151, as can be seen by entering the following command:    ulimit This amount 2097151 is specified in units of 512-byte blocks.  In bytes the value is 2097151 * 512 = 1073741312.   That's one block short of exactly one gig.   2^30 = 1073741824 = 1 gig           So, the default AIX ulimit is 1 GB even on 64-bit systems.   This seems low by today's standards.  This default 2097151 might even be the "hard" limit, and if so, root privi

Problem: To determine the format of a Micro Focus executable file, use the Server Express cobfile command.  The cobfile command is available in Server Express 2.0 and later. Resolution: This command checks for intermediate code files (.int files), generated code files (.gnt files) Animator information files (.idy files), and library files (.lbr files) produced on Server Express (32-bit and 64-bit) and OCDS Version 4.1 and later.  It also checks for screen output recording files (.scn files, where n is a hexadeximal digit between 1 and F) and keystroke files (.key files). The cobfile command takes the following format: cobfile file [file] ... where file is the filename of a Micro Focus executable file. For example: cobfile myprog.int displays one of the following: myprog.int: Micro Focus 32-bit intermediate code file myprog.int: Micro Focus 64-bit intermediate code file If the cobfile command does not recognise a a file

Problem: When software is delivered in binary form only, how can the COBOL version used to build the software be identified. Resolution: This is possible although identifying the point-release of a product would be very time consuming and only possible by Micro Focus technicians. Binaries built using Object COBOL can be differentiated from those built under Server Express  by looking at the library dependencies. Use "ldd $binary_name" Binaries built under Object COBOL  will have a dependency on libcobol, binaries built under Server Express will have a dependency on  libcobrts. On AIX 4 use "dump -Hv $binary_name" 'ldd' lists dynamic dependencies of executable files or shared libraries. So, using ldd on 'demo' when it's been compiled with Server Express returns the following: Note that the 'grep' command is used to filter the output.   ldd demo | grep l

Problem: If you are migrating from an Object COBOL Developer Suite (OCDS) v4.1 release to a Server Express v2.x release, then there are some points you should have keep mind. Resolution: Source Code from OCDS should compile cleanly with Server Express. So, you should only need to move over your source files, recompile, and re-link your application. However, as you can no longer link your application as a static executable, you might need to change how your application is built.  The following describes some of the changes pertinent to those moving applications from OCDS to Server Express. Cob flags now obsolete in Server Express: There are some cob flags that are no longer supported with in the Server Express product.  These are: Cob flag Description -B mode[=lib] Select the system linker binding mode B mode[=lib] Select the system linker binding mode and pass to system linker after COBOL libraries -F Create an RTS quickly F

Problem: When Animating a program, a 191 error ('Terminal type not defined') error occurs when making a call to something like ADIS, even though the terminal type has been defined (by setting TERMINFO) Resolution: This error only occurs if a customer is using a different terminfo directory or has deleted some files from the Micro Focus provided one. When a process is being debugged by Animator, if the application then has to display a screen, there are of course two screens running; these are referred to as the 'Animator' and 'debuggee' screens. If they share the same terminal, then the TERM setting of the debuggee process is set to "mfdebug".  The application will, therefore, search for an 'mfdebug' terminfo; if the m/ folder and/or the files below it cannot be found in the terminfo structure, this error will occur. Solution: if you are using a different terminfo, copy the m/ directory and its contents into it

Problem: Micro Focus run time system error 114 - attempt to access item beyond the bounds of memory - can be one of the most difficult problems to troubleshoot.  However, there are only a few common reasons for the error and Server Express offers more debugging options than previous Micro Focus products.  Occasionally, the problem will be obscure and difficult to find, but those instances are relatively rare.  This article will discuss how to approach diagnosing RTS 114 errors within the Server Express and Application Server environment. Resolution: The most common reason for RTS 114 errors reported on UNIX systems came into being with the ability to create and use callable shared objects.  On hardware which has the capability, Server Express can compile your COBOL source to either 32 bit or 64 bit code.  However, the UNIX operating system cannot handle a mixture of 32 and 64 bit code in the same application. Whe

Problem: Programs that accept data from command line return different results when run from cobrun or cobjrun. ex. cobrun proga parm1 With cobrun, 'parm1' is returned when doing an ACCEPT ws-var FROM COMMAND-LINE. with cobjrun, 'proga parm1' is returned instead. Resolution: This is the expected behavior...The problem is that when using cobrun, the command line is being passed directly to the COBOL run-time system.  When using cobjrun, the command line is passed to the JAVA Virtual Machine.  In this case, the JVM turns around and creates a new command line to invoke the COBOL run-time system. When using cobrun, argument 0 is the program name itself and your command line parameters start with argument 1 to argument n... When using cobjrun, argument 0 becomes the cobrun command inserted there by the JVM to invoke your COBOL program, argument 1 becomes the program name and your command line parameters start with argumen

Problem: BAD MAGIC NUMBER WITH C PGM INCLUDING COBOL Resolution: There is no way to mix 32-bit and 64-bit objects in the same executable.   Using the -q64 option of "cc" invariably creates 64-bit objects, but this COBOL product application consists of 32-bit objects, and the two object types cannot be linked. Old KB# 7181

Problem: The Net Express project file (.APP) is several MBytes large. Is there a possibility to get it smaller? Resolution: The Project file (.APP)  is formatted as an ISAM IDXFORMAT"8"-file. Therefore, the Net Express ISAM-rebuild command-line can be used: REBUILD.EXE  INFILE.APP, OUTFILE.APP to delete unused records from the APP-file within. Old KB# 7145#RMCOBOL#COBOL#AcuCobol#netexpress#ServerExpress

Problem: Why must a person be logged in as root in order to install Server Express? Resolution: When the user is prompted where to install the Server Express product (and could answer any arbitrary directory), the install script must have the power (permissions) to create that directory anywhere on the machine.  The same idea applies to the creation/installation of the "drivers". The install script must be able to create new (or modify existing) license systems, for both development and Application Server licenses.  The license systems must be owned and administered by root, because they are critical (common users must not have permission to disturb them). The install script must be able to modify the system file /etc/inittab, and to create a file in the system directory /etc,  in order to set up the "auto-start at boot time" feature of the License Manager. The files in $COBDIR (the COBOL system files) are

Problem: You can create the same behaviour as using a @mylist.lnk with Net Express with Server Express by using a cat command as part of your cob command.   The cob command includes a 'cat filename' where filename contains a list of files to be submitted to the cob command, seperated by spaces.   Resolution: echo tictac.cbl > list.lnk You can then submit tictac.cbl to the cob command by simply typing cob 'cat list.lnk' tictac.cbl gets compiled.  So if you have a file which contains a list of files to be submitted to the cob command you could use this method. NB. the cat command needs to be contained between backquotes. Old KB# 7191

Problem: Is c-isam a specific or generic file type? Resolution: Release: 2.0   C-isam is a specific proprietary file organization from Informix. Micro Focus products interface with this file type in its elementary version. Old KB# 7155

Problem: Undefined Symbols messages are telling you that your code contains references to entry points which the generator is not able to resolve at link time. As the generator will create direct references to these entry points they need to be resolved at link time. Resolution: The options are: 1. Link in the code which contains the missing entry points into the executable. 2. Tell cob that the entry points will be dynamically loaded at run-time by adding: "-d entrypointname" option to the cob line. 3. Let cob work out they need to be dynamically loaded at run-time by adding "-U" to the cob line. Old KB# 7198

Problem: error 9/253 chk.gnt not found trying to compile through sde Resolution: Change the PATH to $COBDIR/bin:$PATH Old KB# 7185

Problem: Error while trying to compile a COBOL program: Load Error 'cobcheck.1.so' Resolution: Set LIBPATH to include $COBDIR/lib Old KB# 7158

Problem: When a COBOL application in INT or GNT is executed in a shell from a Visual Basic program, it does not usually get the focus by simply doing the following:      Shell "run MyPgm.gnt" Resolution: Here is the Shell function syntax: processID=Shell(pathname[, windowstyle]) In the scenario involved to run INT or GNT, use vbNormalFocus for windowstyle.     Shell "run adsamp.gnt", vbNormalFocus Old KB# 7153

Problem: Copy members and called subroutines not found after porting source of working Windows Cobol program to Unix. Resolution: Unix treats case as significant in file names.  Use FOLDCOPYNAME and FOLDCALLNAME directives to assist resolution. Old KB# 7157

Problem: cob not finding include files for cc, error 1506-296 (S) #include file <oci.h> The script which compiles a mixed language application, uses the syntax -CC -I /pathname to include c header files. Resolution: The cob command returns the error 1506-296 include file not found because there is a space between the -I and pathname. When the space is removed the cob command compiles the cobol and c programs without error. Old KB# 7171