Rocket® COBOL

Problem: Compiling a SQL application as follows : cob -V myapp.cbl -C anim "P(COBSQL) MAKESYN CSQLT=ORACLE DEB end-c DECLARE_SECTION=YES COMP5=NO VARCHAR=YES p(cp) endp endp" the following error is returned:     28     EXEC SQL INCLUDE SQLCA END-EXEC. * 149-S******** **    No SQL directives have been set Resolution: There are two issues here: 1. The Cobsql precompiler ships in lower case on UNIX. 2. Cob will manipulate options delimited with "=" characters, as documented within the Server Express User's Guide, Chapter 9, within the section entitled "Specifying cob Options". To resolve these issues : 1. Specify Cobsql in lower case 2. Delimit the Cobsql and Pro*COBOL options with ==, rather than = Therefore, the correct command line to use is : cob -V myapp.cbl -C anim "P(cobsql) MAKESYN CSQLT==ORACLE DEB end-c DECLARE_SECTION==YES COMP5=

Problem: When you have a 'read only' field and you jump from one field to the next within your program, the cursor will still jump into this 'read only' field as well and not to the next field. Is it possible to jump over the read only field straight to the next read/write field? Resolution: This behaviour is as expected. It's part of the Windows functionality. Even thought you cannot change data in a 'read only' field, you still might want to be able to copy the data inside and therefore you need to be able to got in this field for copy purposes. If you really would like to jump over this field to the next read/write field, you need to change this to for example a 'read only' display field. That way it will only 'display' the contents. However you won't have a box/frame so you might want to draw it around yourself. Old KB# 3765

Problem: How can you run animserv and animserv_t on a specific port, rather than using the default? Resolution: Use the syntax animservXX port=xxxxx or animservXX_t port=xxxxx(where XX is either 64 or 32) N.B. do not use ports from 0-1023. This are privileged ports only accessible by root.Old KB# 3704

Problem: All of the features of FSVIEW are available to you as a command line utility. The commands you specify on the command line define the operation to be carried out by FSVIEW. Information is returned as a scrolling screen output Resolution: In order to get dynamic file tracing for fileshare running in background, you should start fileshare with tracing and then switch it off To get a trace to file from Fileshare, you need to start fs with the options -tr f e.g. fs -s glen -sc -tr f -pf glen.pf will start a server called glen, using password file glen.pf, trace to a file and run synchrounously. To enable and disable fileshare tracing using FSVIEW use admin logon FSVIEW MFTEST server set GLEN trace toggle exit This will produce a text file fsscreen.lst in the fs start directory To get a filehandler trace for fileshare us fsview command as follows admin logon FSVIEW MFTEST server set GLEN xfhtrace toggle

Problem: If you are generating a XML document using the Net Express 4.0 or later COBOL XML extensions and if your XML document becomes very big, you will notice that while the document is being generated the performance is good, but when it comes to the last WRITE XML-stream and the file is CLOSED, it can take quite a long time depending on how big the document is and on how much memory the machine has. Resolution: Our XML extensions use a DOM-based parser (Document Object Model). A DOM-based parser, as supposed to an event-based parser, instead of events being fired, a tree is built up which describes the document and which can then be traversed by methods which access the nodes of the tree. So when you create an XML with our COBOL extensions, a tree is being built in memory and, therefore, the tree can not be flushed to disk until it is completed because when you write a node, you also have to write all the sub-nodes. This ensures that you create a proper

Problem: A customer has migrated to Server Express SuSE SLES 9 X86_64 from OCDS and is re-linking their application.  They receive the following error regarding a file BS.o cob32: error reading: BS.o Resolution: This is a portability issue and actually related to more than just the one object file.  The first file to be processed threw the error.   On examination, the object origin was from a different chipset; MIPS ELF not INTEL ELF. # cob -xve "" -o myrts BS.o cob32 -C nolist -xve  -o myrts BS.o cob32: error reading: BS.o # file BS.o BS.o: ELF 32-bit MSB MIPS-I relocatable, MIPS, version 1 (SYSV), not stripped Using the locking demo: # file stockioa.o stockioa.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped # cob -xve "" -o myrts stockioa.o cob32 -C nolist -xve  -o myrts stockioa.o Entry points defined in module: stockioa.o  &

Problem: When trying to use XML it produces the following error: Load error : file 'MFCHK_XMLGENERATE' error code: 173, pc=1F9, call=1, seg=0 173     Called program file not found in drive/directory Resolution: The problem is that the product used is not the supporting xml generate. You can easily check this out if the following xml modules exist or not: XMLCHK XMLCHKE XMLCHKP XMLCHKEP If not then an upgrade is necessary. It is supported as of Server Express 4.0 SP3. Old KB# 3696

Problem: Running cob, cobrun or similar on SCO Unix 5 you get a message of the type: Dynamic Linker : /cobol/bin/rts32_t  can't set protections on segment of length 0*602 at 0*804800 Resolution: This error occurs if you are trying to run the Server Express product in SCO Openserver 5. Server Express is not available for this platform. Please see http://supportline.microfocus.com/productreleaselevels/unix.asp for available products. Currently (Server Express 4.0 SP2 & Server Express 5.0) can only run on SCO UnixWare 7.1.3/7.1.4/Open Server 6.0. Old KB# 3678

Problem: Is there an option that allows you to type in data in the first line of a drop down list box? It seems it always protects it. Resolution: A Dialog System list object that has an entry field at its top part is a Selection Box, not a List box. With Selection Box, you can make it Simple, Drop Down, or Drop Down List. If you make it as Drop Down List, the first line or the entry field will be in read-only. You will need to change the option to Drop Down to allow you to type in data from the entry field. Old KB# 3763

Problem: I am trying to animate a process on another machine, using dynamic attachment, but it says I don't have permission to access the application.  I am using the same user ID on both machines - why is it not working? Resolution: The user ID was the same on both machines, but the group ID was different.  Changing the group ID solved the problem. Old KB# 3677

Problem: Installing ServerExpress on SuSE SLES Resolution: If you are want to install ServerExpress on a SuSE SLES you need to install the gcc package before ServerExpress. gcc is not a package in the SuSE Standard installation and must be choosen separately. Old KB# 3705

Problem: Why is the C Compiler and C Compiler needed for Server Express? Resolution: The C language development system and tools are required on all UNIX systems, in order to create linked executables using Micro Focus COBOL Developers Suite products.  The COBOL product utilizes the C language development tools, such as the link editor and the system assembler, when building these executables.  The C development tools used by Micro Focus for adapting and testing the COBOL Developers Suite product are the tools supplied by the Operating System vendor.  This defines the 'Reference Environment' used by Micro Focus in reproducing and correcting defects reported by users. Some vendors supply the C development system as a part of the Operating System, and others sell the development tools as a separate piece of software.  If the user does not intend to create linked executables of any kind, then there is no requiremen

Problem: The demonstration shows the four methods of specifying directives to the Cobol compiler("cob" ccommand) Resolution: BUILD W/RELEASE:     Any version of Server Express or Object Cobol Developer Suite INTRODUCTION ========== The demonstration shows the four methods of specifying directives to the Cobol compiler ("cob" command) SOURCE FILES: ========== Note: All required files are in copydemo.tar Program Files       Description ----------------       -----------------------------------------------------------=    picpy*.cbl            Slightly modified versions of $COBDIR/demo/debug/pi.cbl Copy Files: ----------------       ----------------------------------------------------------- COPYFILE.CPY    

Problem: Release 4.0: A customer upgraded from OCDS to Server Express 4.0 SP2 and run into problems with cobtidy and cobexit. Running a c program calling Cobol programs and doing cobtidy before the exit(0) of the C program results in hanging. The problem is that the C program is hanging just after the cobtidy() and waiting forever.Having tried cobexit() instead of normal C exit and removed cobtidy, this time it hangs with cobexit()! Resolution: Solution is to compile with -t for multi threaded. OCDS and Server Express are not the same products and multi threaded (-t) is one of them. With Server Express you have to specifically include this in the compile command. Old KB# 3698

Problem: In KB 19658 the following line: "Micro Focus Server Express v4.0 SP1and above supports  UTF-8 in a PIC X field. You do not have to do anything special. That is, you do not have to specify any directives. The character is held in one byte." appears to be incorrect when using Oracle. UTF-8 database name conatins a letter that is not ANSI.  The letter is like an uppercase O with a forward slash on top of it.   The COBOL program gives a "?" for that character. Is there any setting  that will proper translate this character? Resolution: Please refer to Oracle's Pro*COBOL Programmer's Guide and also their Globalization Support Guide or consult with Oracle. Environment variables NLS_LANG and LANG should be specified. NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252 LANG=en_US.UTF-8 Note: The data is stored as UTF-8, so not all the characters are displayable (some are, some are not) if COBOL receives the characters

Problem: =========================================== Mono-Threaded COBOL Socket client & server. =========================================== related KB: Multi-Threaded COBOL socket's server & MonoThreaded COBOL client. http://supportline.microfocus.com/mf_kb_display.asp?kbnumber=23143 Resolution: =========================================== Mono-Threaded COBOL Socket client & server. =========================================== The program server.cbl  is the socket's server ( written in COBOL ) The program client.cbl  is the socket's client ( written in COBOL ). This sample was mainly tested on AIX 5.2.0.0 with Server Express 4.0 SP2 32bits. To Compile and link the sample ============================== To compile and link  server.cbl & client.cbl, launch cl.sh cl.sh:  cob -xag server.cbl cob -xag client.cbl To run the sample ================= To run the sa

Problem: The ab command can correct your common typos in vi automatically. Resolution: Vi  can be initialized by a list of initializations in a file called .exrc  located in your home directory.   .exrc holds map, set and ab commands The file is read by vi and ex on startup.  The ab command takes the form of ab [abbreviation] [expansion] This can be used to correct typos on the fly by using ab  [typo]  [correction] For example: ab teh the ab preform perform .exrc can be created by vi.  Add your mappings and abbreviations to this file as you find you need them. Old KB# 3708

Problem: ========================================================== Multi-Threaded COBOL socket's server & MonoThreaded COBOL client. ========================================================== Related KB: Mono-Threaded COBOL Socket client & server. http://supportline.microfocus.com/mf_kb_display.asp?kbnumber=23142 Resolution: ========================================================== Multi-Threaded COBOL socket's server & MonoThreaded COBOL client. ========================================================== The program server.cbl  is the socket's server ( written in COBOL ) The program client.cbl  is the socket's client ( written in COBOL ). This sample was mainly tested on AIX 5.2.0.0 with Server Express 4.0 SP2 32bits. To Compile and link the sample ============================== To compile and link  server.cbl & client.cbl, launch cl.sh cl.sh:   cob -xagt &

Problem: Map is one of the lesser known and most useful commands. You may find when you're editing that you are repeatedly using a command sequence or maybe a very complex sequence.  The map command allows you to define a macro for the editor's command mode.  In other words, you can issue it while you type; as soon as you hit the mapped key, the keystroke is replayed Resolution: The command format is map to display currently mapped keys map mykey sequence    to map mykey with a sequence of commands unmap key to remove the map. As map is used in command mode, you need to know the key not used in command-mode and are available for your use.  These are: G K q V v ^A ^K ^O ^T ^W ^X _ * \\ = Example 1 Initiate vi and type the following: Micro World Focus 2007 Enter command mode by pressing colon (:) and type the following map g dwwP dw delete word (delete actual

Problem: This error occurs  because the the program has not been  compiled properly for using the profiler.  The cobprof command cannot be used until the the program has been compiled with the PROFILE compiler directive. Resolution: Step 1 the program must be compiled for debugging adding the -a flag for .int or -g flag for .gnt, .o, shared object or executable also specify the compiler directive -C PROFILE. Example:  cob -xg -C PROFILE  pgmname.cbl Step 2 is to execute the program ./pgmname  this will create the pgmname.ipf file. Step 3 is run the profiler reports Example: cobprof  pgmname   LIST This will display the profile information on the screen.  If you do not set the LIST Profiler directive, then by default the output is produced in a file called pgmname.prf. Documentation on using the COBOL Profiler can be found in the Server Express Utilities G

Created On:  02 March 2008 Problem: How do you setup rsh on SuSE SLES? Resolution: First it is recomended that you install the rsh package from yast. The r-tools are not a default package in the SuSE Standard installation. After installing the rsh package you need to edit /etc/xinet.d/rsh. Set the Option Disable from yes to no and modify the default Server args from -aL to -L. Then restart the xinetd with rcxinetd processes. Check with netstat -an |grep '514' to find out if rsh is listen on the port. Remote Publish only needs rsh, not rlogin. Incident #23364 Old KB# 3703

Problem: Is it possible to have text appear horizontally on the left or right sided tabs? Resolution: Unfortunately it is not possible to have a 'literal text' horizontally in the tabs, not only in Dialog System but also in Panels2 API. In the past one could do this with OS/2 but then the tabs appeared to be rather big. The only way to do this is to create a bitmap with a horizontal text and place this on the tab, instead of a 'literal text'. Old KB# 3766

Problem: Receive the following error message An error was detected while installing c:\\windows\\MFUnweb.exe The installer will attempt to undo any changes it has made to your system. Resolution: When looking at the log produced by the websync install in the temp directory it was discovered that the customer was attempting to run the the wrappack from a network drive when the directory containing the wrappack started with a $. The WebSync technology doesn't allow $ in network locations.  Placing the WrapPack in a standard location on their network and not a hidden one or copying it locally will resolve the problem. Old KB# 3521

Problem: How do I find files larger than a specified number of blocks? Resolution: The following script shows how one might use -size to return a full listing of files in a recursive find. We display the owner, size and location. support 1884712 ./products/SX50EAP/lib/libcobcheck.so support 1884712 ./products/SX50EAP/lib/libcobcheck.so.2 #! /bin/sh # largerthan # find a standard file from current directory, larger than n-bytes if [ $# -lt 1 ] ; then     echo "usage:  largerthan  nunmber-of-bytes   [user] "     exit 1 fi if test $2 then     USR=" -user $2 " fi find . -size $1c -type f  $USR -print | xargs ls -l | awk '{ print $3 "\\t" $5 "\\t" $9 }' Old KB# 3712

Problem: I can't use REMOTE DEBUGGING when the operating system of the remote machine is SuSE 9 . A error message about the rm command is displayed Resolution: It is necessary to modify the file $COBDIR/bin/cobrps . The command who am i  must be modified to whoami The cobrps file must be : : #------------------------------------------------------------------------------- # @(#)cobrps   1.0 # # $Revision:   1.3  $ # $Date:   29 Jul 1999 15:59:10  $ # $Author:   RHS  $ # # Remote process list #  Output: <processid><tab><other information><newline> # # N.B. #   This script must not make ANY assumptions about the environment in which it #   executes: in particular, it must not assume that COBDIR, PATH, LIBPATH, #   LD_LIBRARY_PATH, etc., are set. #-------------