Rocket® COBOL

Problem: A customer wanted to know how comptible .int code really was: for example, could he take an .int file compiled as 64-bit on net Express 5.0, and then run it on a UNIX box? Also, would this have to be a 64-bit UNIX system? Resolution: A 64-bit .int built on Net Express will run on a 32- or a 64-bit UNIX box. Old KB# 4560

Problem: When compiling an executable on SCO v6.0.0, with Server Express v4.0, the above error is displayed. Resolution: The full library name is libintl.so and is the library that provides Native Language Support.  On SCO 6, it is found in /usr/gnu/lib, which when added to the PATH corrects the problem Old KB# 4492

Problem: Load error : file '$JAVA$CallVendorServices' error code: 198, pc=93, call=1, seg=0 198          Load failure Resolution: If your Environment Settings are correct, test this by trying to make a direct call to your Java application. You need to run this as a multithreaded application by using the cobjrun. Old KB# 4530

Problem: Cobol program's being animated using COBSW= A set will not start up in the animator, but will just execute. Resolution: This problem can be caused by the environment variable DISPLAY being set. When the DISPLAY environment variable is set the Server Express product will try to create a new X-Term window for the Animator screen and user interface. If the user is not using an X-Windows session, this operation fails and the Animator screen is never displayed. Ensure that the environment varaible DISPLAY is not set. If DISPLAY is set, unset and then animate. example: echo $DISPLAY DISPLAY="information" unset DISPLAY Old KB# 4516

Problem: When trying to run a Unix script that invokes a Cobol program, it runs fine when manually running it from the shell. So you are able to run the script as the user from a menu. However, when running the script from a cron as the same user it won't work - the error "could not obtain latest contract from popen(3C): No such process" appears. Resolution: The problem here was the "popen" error message seemed to be a generic error message. This particular program had "display" in it - running it in the cron caused the above "popen" error - when commented the displays out the error no longer appeared. It was identified as a Solaris error and they can provide a fix for this. Old KB# 4526

Problem: Release 4.0: Server Express install breaks with message libc not found on a Linux System. Resolution: Please ensure that you have the gcc component installed because gcc is not a standard Package for the most Linux Systems and must be installed separately. Old KB# 4559

Problem: This error has been encountered when running Server Express 4.0 SP2 on AIX 5.3 (64 bit) with Websphere Queue Manager 6.0.1.1. Load error : file 'MQCONN' error code: 173, pc=0, call=1, seg=0 173     Called program file not found in drive/directory Resolution: It is infact a problem with the Technology Level package 5300-04 for AIX 5.3 causing Informix 4GL and SQL products to fail. When you apply Technology Level package 5300-04 on the AIX® 5.3 operating system, 64-bit versions of IBM® Informix® 4GL (and SQL) 7.32 will no longer work. Example $ fglgo -V Could not load program fglgo:           $ truss fglgo -V                                   execve("/usr/informix/4gl7

Problem: Release 4.0: /usr/lib/libc unable to find socket.lib install error check disk space permissions and try again Resolution: If you get this message during the installation of Server Express 4, please make sure that the gcc is installed on your system. Old KB# 4550

Problem: Rebuild -f:c63d5 <file-name> returns the followin error: -f:c63d5 <file-name>          ^ REBUILD aborted - Invalid option Resolution:   This Rebuild validatation command is no longer valid.  The correct sytax is: rebuild -f:c9 <file-name> The -f performs a full integrity cheeck on a file, display all possible information The -c  Specifies the validation performed. You can select any combination of checks 1, 2 and 8 by adding the appropriate numbers together. (The more checks you perform, the longer the validation takes.) The default is 11. 1 Checks the data file structure and counts the number of records. 2 Checks the structure of the free space list (FSL).   8 Checks the index file structure.   256 Checks the data file structure and counts the number of records with the file open for sharing in another process. You cannot

Problem: A program, including the routine CBL_READ_SCR_CHATTRS, is generated using NetExpress and runs correctly on a Windows platform.  However, when porting this application to a UNIX platform under Server Express, the routine no longer works in that it no longer reads the screen attributes (backgound colours) of the screen. Resolution: The problem can be solved by inserting CBL_SCR_SET_PC_ATTRIBUTES at the beginning of the program. Old KB# 4546

Problem: How can I get information about input and output files? Resolution: Rebuild  -i <file-name> Displays information about the input and output files, including record lengths, file type and key structure. If you only want to see the information and do not want to perform any other operation, use the -n option instead. Old KB# 4554#COBOL#ServerExpress#netexpress#AcuCobol#RMCOBOL

Problem: A customer had a script called (say) ggg, and a program (say) ggg.cbl. The script was in a directory pointed at by PATH, and the program was in a directory pointed at by COBPATH. If he typed 'anim ggg', then Animator picked up the script, rather than the program. Why was this? Resolution: Animator can debug .int, .gnt, .so, executables, core files and running processes.  So when you type      anim nnn the animator will first check to see if 'nnn' is number and, if so, see if it can dynamically attach to a process with that pid.  Next, it will search for exes, down $PATH.  It that fails, it will search using the standard RTS rules (using $COBPATH and the program_search_order tunable, etc).  Finally, it checks to see if it's been asked to debug a core file. In this case, as a script is an executable, it was be picked up first. The ideal solution is not to have s

Problem: How do you use the h2cpy utility to convert pstat.h to pstat.cpy Output is not aligned correctly with 64 bit application using the following command to create: h2cpy /usr/include/sys/pstat.h -I /usr/include -e lp64 h2cpy /usr/include/sys/pstat.h -I /usr/include -e ilp64 Resolution: The pstat_ functions is used to obtain system and process information. Create  pstat.cpy with the following command: h2cpy /usr/include/sys/pstat.h -I /usr/include -D_PSTAT64 It will create pstat.cpy with the following: 01  pst-status        is typedef.         02 pst-idx           usage l-long.         02 pst-uid           usage l-long.         02 pst-pid   &n

Problem: I can't run the XML tutorial . Cob2xml command can't create files and displays errors about undefined functions . Resolution: Server Express 5.0 is validated with the version 7 of the C compiler . It is necessary to install this version. To verify the version : Login : root lslpp -L vac.C   must display the line : vac.C   7.0.0.0 Old KB# 4562

Problem: Which compiler flag should I use in order to have the objects to be created in a directory other than the current one? Resolution: Use the -Ngnt flag then specify the file location for the output file. cob -u -Ngnt="/tmp/testxx/tictac.gnt" tictac.cbl This example causes tictac.gnt file to be written to the /tmp/testxx directory. Old KB# 4522

Problem: If the database connection criteria is being passed to Pro*COBOL via a compiler directive, is there a way to prevent this from being displayed on the console? Note the line: * CSQL-I-005: Passing userid=abcd/wxyz@INST1 to ORACLE Precompiler in the output of a compilation of an Oracle COBOL program.. Resolution: These messages are actually coming from the COBSQL portion of the COBOL compiler * CSQL-I-005: Passing userid=abcd/wxyz@INST1 to ORACLE Precompiler This message is only displayed if the CONFIRM directive is set. Removing the CONFIRM directive should resolve the problem. Old KB# 4517

Problem: The following message is displayed : << *** This script must not be run from     inside the product directory. exiting ... >> Resolution: To install a fixpack , it is necessary to create a temporary directory. This directory must not be $COBDIR and, also, must not be a subdirectory of $COBDIR. Old KB# 4529

Problem: Compile step receives I-O error:idy file renamed to .$dy extension Resolution: This error will occur: 1.When the user does not have write permissions on the directory the .idy files are to be written to. 2.If  a  .idy already exist in the current directory when compile is exeucted and and user does not have write permission and is attempting to create the idy again. Remove any files created from previous compile attempt. Old KB# 4544

Problem: A customer had an application written in C and distributed on HP/UX PA-RISC platforms as shared libraries.  This application could be invoked from either C or COBOL by linking the libraries to a C or COBOL main program.  The libraries themselves depended on other libraries, and were originally built with -L and -l specifying the dependant libraries.  The 32-bit linker in HP/UX PA-RISC remembers -L locations as absolute paths, so at runtime the dependant libraries could be found even if SHLIB_PATH did not include their location.  Here is an example: Cmain or COBmain calls sub1 which calls sub2: > cat Cmain.c int main(int argc, char **argv) {     sub1(); } > cat COBmain.cbl         CALL "sub1". > cat sub1.c int sub1(){     disp_hello();     return(0); } > cat hide/sub2.c int disp_he

Problem: Opening a file in a "MAIN" program and reading its records in another program "SUB" which is called by "MAIN" results in a file status=47 means: "A READ or START operation has been tried on a file not opened INPUT or I-O." Must the file be opened in each program? Resolution: NO! Please specify in the FD the EXTERNAL clause and add this FD to the SELECT in each program which uses the file. BTW: The variables of the FD are external variables and have the same value in each program where specified. The core of the attached 4 files: ------------------------------------        program-id. Sub.        copy SEL.        copy FD.        display "read: " REC(1:20)        read MyFile.        display "read: " REC(1:20) ---------------------

Problem: The following rebuild results in an error. $ cat F.seq AAAA0001  AAAAAAAAAA AAAA0002  AAAAAAAAAABBBBB AAAA0003  AAAAAAAAAA AAAA0004  AAAAAAAAAADDDDD AAAA0005  AAAAAAAAAA AAAA0006  AAAAAAAAAA1234567890 BBBB0001  BBBBBBBBBBAAAAAA BBBB0002  BBBBBBBBBB BBBB0003  BBBBBBBBBBCCCCCC BBBB0004  BBBBBBBBBB BBBB0005  BBBBBBBBBBEEEEEE $ rebuild --v F.seq,F1.ism -o:lseq,ind -I -k:1 8 -r:v20-30 RBD 102.14.445 21APR05         File                             :   F1.ism         Organization                     :&

Problem: What are the differents ways of debugging my applications ? Resolution: INTRODUCTION Animator enables you to debug Micro Focus Cobol applications. You can debug all types of application: single-threaded, multi-threaded, with Language C, created in intermediate code file, created in generated code file, callable shared object or system executable code file. This document is to help you to start the debugging. The manual Debugging Guide describes the Animator and debugging. PREPARING FOR ANIMATION To animate the application, you must compile and generate your application with the directives and the options required. The directive of the compilation is ANIM, and the option of the generation is g. By default, the directive ANIM is setting. When a program is compiled or generated to be animated, the file with name of the program as basename is created with the extension .idy. This file contains additional information required by Animator. 

Problem: An application moved cursor focus to a group field when pressing a specific key.  i.e. to the index 9  in an array of 12.   This apparently worked OK on a pre 4.0 version of OCDS but not on Server Express. Resolution: The dialog (local code associated with a panel) pertaining to the group field TOGGLE is shown below.  This is the field to jump to when pressing END (that doesn't work).  It's a 12 member array of 7 bytes, the application jumps to index 9.       PANEL GROUP PRE-GRP VERTICAL           LINE 13 COLUMN 59 HEIGHT 9 WIDTH 7           TYPE DATA ACC-EXIT BAR           SELECT BAR               LENGTH 7      &n

Problem: How to 'OPEN EXTEND'  a Line Sequential file in shared mode? "shared mode" meaning than more processes will be able to open the same Line Sequential at the same time. This KB applies to Server Express and Net Express. Resolution: Just add in the SELECT clause the LOCK MODE clause, as pasted  and attached  below        IDENTIFICATION DIVISION.        PROGRAM-ID. wfilsEXT.        ENVIRONMENT DIVISION.                                                            INPUT-OUTPUT SECTION.    

Problem: A customer reported a problem that after upgrading from OCDS 4.1.40 to SX 4.0 SP2, the application which writes to a line sequential file the records couldn't be seen - it's as if the buffer on the file is far too big. In this particular problem a number of MQ interface programs write to logfiles. These interfaces allow the application to communicate with other systems on other servers. The interface programs are running in the background all day long and the only way to see if they are active/working is to check the logfiles which are updated every 15 seconds. On OCDS this worked, viz. the files got updated regularly. However with SX the logfiles are not being updated directly and it can be 30 minutes before the physical file is updated - which sounds like stuff is still in the buffer. Is there a way to get the old functionality back? I looked at SEQDATBUF, but the default is 4096, and the SX 5.0 docs say that the *minimum* is 4096, so I can't see a way of dro