Rocket® COBOL

Problem: The Object COBOL Developer Suite (OCDS) manual states that if the HOST-NUMCOMPARE compiler directive is used it MUST have a value setting of 1 or 2.  (e.g $set HOST-NUMCOMPARE"1"). What is not stated is that if no value is set (i.e. $set HOST-NUMCOMPARE) it assumes the same behaviour as if HOST-NUMCOMPARE"1" were set. The Server Express manual make no mention of the values 1 or 2 being required. It states that the allowable settings are either NOHOST-NUMCOMPARE (default) or HOST-NUMCOMPARE. However, the behaviour for the setting $set HOST-NUMCOMPARE (without 1 or 2 set) differs in that in Server Express it assumes the same behaviour as if NOHOST-NUMCOMPARE were set. Resolution: To get the same behaviour in Server Express as in Object COBOL Developer Suite for the setting: If you have the following set in Server Express: $set HOST-NUMCOMPARE you should try the setting: $set HOST-NUMCOMPARE"1" e

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: 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 customer upgrading to a new version of Server Express, or rebuilding his/her runtime, may encounter problems when running CICS applications. Resolution: IBM supply a file mkcicscobol. Their documentation states that this must be run whenever a new version of a Micro Focus product is installed, whenever a new version of CICS is installed, or whenever a new version of any supported database product is installed. The script apparently creates a 'language message file' and a runtime library. Further IBM documentation states that this should also be done if the runtime is rebuilt. For specific technical information, Micro Focus would recommend that you contact IBM. Old KB# 7260

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: 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: 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: Error while trying to compile a COBOL program: Load Error 'cobcheck.1.so' Resolution: Set LIBPATH to include $COBDIR/lib Old KB# 7158

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

Problem: If you would like the exact attribute/colour combinations to be saved and restored using cbl_read_scr_chattrs and cbl_write_chattrs Resolution: You need to either: 1. Set-up the colours in the current palette.  A simple way of doing     this (and achieving consistent results on Windows and Unix     platforms) is to add the following call to the start of the program:         CALL "CBL_SCR_SET_PC_ATTRIBUTES" 2. Use the alternative set of calls, CBL_SCR_SAVE and CBL_SCR_RESTORE,     which were designed to overcome all the issues described above.     These are documented in the Creating UIs manual. Old KB# 7180

Problem: NFSFILELOCK causes the file handler to apply a lock in such a way that the application will gain exclusive access to a file against other applications.  It is not a good alternative to fileshare, since it provides no locking against applications not using NFSFILELOCK. Resolution: The functionality is available in all genesis products i.e. SX, NX and MFE. Old KB# 7169#COBOL#netexpress#RMCOBOL#AcuCobol#ServerExpress

Problem: Because changes to your ADIS configuration effect your whole environment how can you have more than one ADIS configuration on the same machine? Resolution: ADISCTRL is the name of the disk file that holds the ADIS configuration and this can be moved from one $COBDIR directory to another.   If you need two different configurations you can have two different ADISCTRL files in two different $COBDIR directories on the same machine and change the value of $COBDIR when you want to change between the two configurations. Old KB# 7189

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: 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: 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: How to specify a different ADISCTRL file Resolution: User has two custom  ADISCTRL files with different default configurations. The dd_ADISCTRL  environment variable can be used to point to the appropriate ADISCTRL file Old KB# 7174

Problem: Occurs when "cob" or "cobrun" command is issued to Server Express on a machine which has or had Object Cobol Developer Suite installed. Resolution: There are "cob" and/or "cobrun" triggers from an older version of a Micro Focus  product in a directory which is on PATH ahead of the directory where the current triggers were installed.  Run command "which cob" and "which cobrun" to find and remove unnecessary triggers. Attachments: 10897223.gif Old KB# 7154

Problem: Call x'91' function '69' HP Server Express implementation error, l-attributes Resolution: Not all functions of the  X'91' call are supported on UNIX. Many of the functions available under x'91' on DOS/Windows are not appropriate for UNIX systems This information is from  the Server Express File Handling manual: The only functions supported under Server Express are: x"91" function 46 Enables null insertion x"91" function 47 Disables null insertion x"91" function 48 Enables tab insertion x"91" function 49 Disables tab insertion x"91" function 52 Specifies use of two-byte record terminators x"91" function 53 Specifies use of one-byte record terminators Old KB# 7175

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: The Animator is considered to be a COBOL development system utilities.  The solution to this problem is to set COBDATA beginning with a colon. Resolution: The compiler and animator themselves are COBOL programs, and they need to open their own files just as any COBOL program would need to open files, but setting COBDATA interferes with this.   The documentation, in Appendix A of the User's Guide, indicates:         Setting COBDATA affects the compiler and other utilities.  During         compilation, for example, program source is regarded as a data file by the         compiler.  If you intend to use any COBOL development system utilities, we         recommend that the COBDATA value starts with a colon (:). Old KB# 7165

Problem: **    External Compiler Module message **    DB0009 MF DB2 Connect program reported error condition ' 1403'.This **    error prevents SQL processing from continuing - further EXEC SQL **    statements will be ignored. This error is produced when compiling a DB2 program under Server Express on AIX platform. The DB2 database resides on a different server than the one that it is being used to compile. Resolution: When you compile or run a DB2  program using Server Express DB2 compiler directive, it must first connect to the database.  With a local DB2 server, DB2 will attempt to use the logon information you used to logon onto that server if you do not provide ID/PASSWORD.  Generally, this works fine.  However, if the ID/PASSWORD on a remote server is different or non-existent, then the compile will fail with the 1403 error.&n

Problem: High watermark for monitoring Application Server licenses does not seem to be taking effect. Resolution: The high watermark file used to monitor Application Server licenses must be defined in upper case letters in $COBDIR/WATERMARK.  If the file is defined in lower case it is ignored. Old KB# 7205