Rocket® COBOL

This article explains that a COBOL entry point cannot be the same as a C API. Problem: When writing a COBOL program called main and running it, the 114 runtime error was returned. Why is this? Resolution: If you write a COBOL program called main and try running it, you will get the message 114 Attempt to access item beyond bounds of memory (Signal 11). If you specify the suffix, for example cobrun main.intit will work, however if you just type cobrun main having written nothing, you will also get the error. You cannot have a COBOL entry point the same as a C API. Therefore, main, exit, printf, etc., cannot be used. Otherwise the operating system will get confused and return unexpected results such as a 114 or 115 error. Old KB# 14483

This article explores the licensing error ASLM - You need to rerun as root (No Error Number). Problem: This message was received after a reboot and when trying to run a program. The message does not include any error number as with a similar message relating to the semaphore file /var/aslmfsem. Resolution: This error is caused by the absence of or incorrect permissions pertaining to the file /var/.mng2sys. > ls -la /var/.mng2sys -rw-rw-rw- 1 root root 56 Jun 29 15:32 /var/.mng2sys The problem can be resolved by running a program as 'root'. For example: > cobrun hello ASLM: You need to rerun as root > echo $COBDIR /home/products/9i.T4.40.03 > su Password: # export COBDIR=/home/products/9i.T4.40.03 # export PATH=$COBDIR/bin:$PATH # export LD_LIBRARY_PATH=$COBDIR/lib # cobrun hello hello # exit exit > cobrun hello hello Old KB# 14485#COBOL#Licensing#ServerExpress

This article explains what to do when Animator starts in an X window and the font size is too small. Problem: Background information: Animator will start in an X window under the following circumstances: When you are using Server Express on UNIX or Linux, and When the DISPLAY environment variable specifies a valid X terminal, and When starting Animation using: the “cobanim” command, or the COBSW= A environment variable, or just-in-time debugging, or CBL_DEBUGBREAK, or Debugging Services and Applications on Enterprise Server using the cobesdebug utility The problem is that the Animator window may be too small for practical use. Resolution: Animator opens “xterm” in an X terminal window. Animator does not specify any particular font, so xterm will use the default font configured within X. To change this X default, you could edit/create a file named .Xresources in your home directory. It should resemble t

How can you create a batch file transfer using RUMBA AS400 File transfer? Problem: Users of RUMBA AS400 File transfer want File Transfer sessions to run unattended. They may do so by taking advantage of the Batch File Transfer feature in Rumba. Resolution: You can create a File Transfer from/to an AS/400 that runs in batch mode from the command line, with no input required. Batch File Transfers can be scheduled to run at certain times of day. To create a Batch File Transfer: Configure an AS/400 File transfer profile, including the query that selects the information you need. Test to ensure it works properly. Save this profile. By default, the file extension is .RTO. From the AS/400 File Transfer window, go to Transfer > Batch... Click on the Add Transfer button (this can be found next to the X and the up and down arrows), and select the .RTO file you created on step 2. Click Save As... to save the batch transfer. This will create a file

This article explains how to use the MS Word printout automation object from COBOL. Problem: The printout automation method in Microsoft Word allows you to print out specific page ranges from your application. However there are a lot of different options available for this method and most are not relevant for page ranges. How can you call this from COBOL ? Resolution: You can use OLE Named Parameters with the printout method to print a page range. An example of this is: mftech***** Use OLE Named parametersmftech invoke olesup "setNamedParameters" using by value 4 size 4mftech set wdPrintFromTo of ws-range to truemftech invoke theDocument "PrintOut"mftech using by reference z"Background"mftech by value -1mftech by reference z"Range"mftech by value ws-rangemftech by reference z"From"mftech by reference "1"mftech by reference z"To"mftech by reference "2" Before you use the “PrintOut

This article describes how to use AcuXDBC to connect a string from an ASP project. Problem: Using AcuXDBC to connect a string from an ASP project sometimes generates the following error message: "Microsoft OLE DB Provider for ODBC Drivers error '80004005'[TOD][ODBC Driver]VISION: 'GENESIS_HOME' environment variable not found." Resolution: The key points to success in this process are the following: The installer sets the GENESIS_HOME variable in the USER environment, not the SYSTEM; you need to manually set GENESIS_HOME as a SYSTEM variable (copy it from the USER variable). Create a System DSN, using the AcuXDBC driver; name it “MY_DSN," and leave all options at their default settings, including configuration files set to “acuxdbc.cfg.” Create a virtual directory within IIS, leaving all defaults except "Execute Permissions:"; set this to "Scripts only".In that direc

This article helps resolve the error message received when installing EntperiseLink. Problem: We are receiving the following error when trying to install EnterpriseLink: Setup previously required to reboot. You must do this before running setup. Resolution: If you get this error after rebooting, this can be resolved by deleting the ENTSetup key in the registry under HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce. Old KB# 14507#Rumba#EnterpriseLink

This article provides an example of intrinsic functions NATIONAL-OF and DISPLAY-OF in a COBOL unstring statement. Problem: How are the intrinsic functions NATIONAL-OF and DISPLAY-OF used in a COBOL unstring statement? Resolution: See the COBOL code pasted below: $SET NSYMBOL(NATIONAL)working-storage section. 01 v1 pic X(10). 01 v2 pic X(10). 01 v1v2 pic X(20). 01 v1N pic N(10). 01 v2N pic N(10). 01 v1v2N pic N(20). procedure division. move "v1 v2" to v1v2 initialize v1 v2 unstring v1v2 delimited by space into v1 v2 move "v1N v2N" to v1v2N initialize v1N v2N unstring v1v2N delimited by space into v1N v2N move "v1 v2" to v1v2 initialize v1N v2N unstring FUNCTION NATIONAL-OF(v1v2) delimited by space into v1N v2N move "v1N v2N" to v1v2N initialize v1 v2 unstring FUNCTION DISPLAY-OF(v1v2N) delimited by space into v1 v2 move "v1N v2N" to v1v2N initialize v1 v2 unstring FUNCTION DI

This article provoide more information about the Database Connectors Error. Problem: I can be difficult to determine from the file status the reason why an error has occurred. How can I get more information on a problem. Resolution: The Database Connector has been enabled for CTF (Consolidated Trace Facility). To obtain additional output you need to add the eprintf entry as a trace entry. An example trace config file that is enabled for the Database Connectors component is: mftrace.level=info mftrace.emitter.textfile#location=c:\\temp\\logs mftrace.emitter.TEXTFILE#FORMAT=$(TIME) $(COMPONENT) $(THREAD) $(EVENT) $(LEVEL)$(DATA) ## Component Run-time System mftrace.level.mf.rts=INFO mftrace.comp.mf.rts#all=false mftrace.comp.mf.rts#eprintf=true mftrace.comp.mf.rts#memory=false To enable CTF you need to add an environment variable MFTRACE_CONFIG that points to the config file. Incident Number: 2266679 Old KB# 14482

This article explains how you use the Infomgr utility to view, print, and execute the demonstration programs. Problem: How do you use the Infomgr utility to view, print, and execute the demonstration programs? Resolution: Please see the attached step-by-step document that uses the Standard System Test using tictac.cbl. Old KB# 14371

This article explains why the ViewNow X server does not honor the –geometry parameter when starting X clients. Problem: When X clients are started with the –geometry parameter, ViewNow X server doesn’t honor the position information given. Why is this? Resolution: In ViewNow X, the –geometry flag is overridden by settings in the server which are intended to prevent windows from inadvertently obscuring each other. These settings can be changed to prevent this behavior by performing the following steps: Launch the ViewNow X control panel. From the Start menu, go to Start > Programs > ViewNow > X Windows > Control Panel. Alternatively, launch \\Program Files\\NetManage\\APPS\\X\\CPanel.exe from the command line. From the Options menu, select “Window…” On the Window Management dialog, uncheck the “Cascade Windows” option. Click OK to dismiss the dialog. Re-launch the ViewNow XServer. Subsequent invocations of X clients with the –geometry parameter present will now appe

This article explains how to create and print a hardcopy compilation listing using TBOX / SDE developers tool. Problem: One of the options within SDE during program compilation is to create a listing file. This option is enabled by using F4 while the compilation command menu is displayed. By default this listing is not automatically sent to a printer. How can you get the SDE or TBOX integrated development tools send listing to a printer? Resolution: In order to have the SDE or TBOX integrated development tools send a listing to a printer, the environment needs to be set to force the listing output to a system printer. Before starting SDE or TBOX set an environment variable named DD_LST so that it contains the command needed to ‘pipe’ output to the system’s ‘lp’ command. For example: export DD_LST=”> lp”.Then start the development tool SDE. This will cause the listing created during the compile to be routed to the system print

How to capture network packets using WireShark. Problem: In order to troubleshoot certain types of issues, it may be necessary to take a network trace. Also known as a 'sniffer trace', this captures all communication to and from the workstation, providing a low-level view of network traffic. Resolution: To take a network trace using WireShark: Install the WireShark network sniffer. WireShark can be downloaded from http://www.wireshark.org/download.html When the installation completes, start WireShark. Select Capture > Interfaces from the menu. Click the Options button for the desired interface. Configure the capture options: Capture packets in promiscuous mode. This option allows for the capture of packets with destinations other than the workstation where WireShark is running. Normally, this should be left checked. Limit each packet to. This option should be left unchecked to allow all packet data to be captured. Capture Filter. This

This article addresses what to do when an XFD Directive does not check to ensure the Date mask matches the Picture clause. Problem: The Compiler $set createxfd (xfd-directory=C:\\...) Directive does not check to ensure that the Date mask matches the COBOL Picture clause. This results in parse errors with MFXDBC when loading the resultant XFD into the System Catalog. For example, the following will compile and build the XFD without an error reported. This generates a parse error with MFXDBUTIL.bat.: $xfd date=yyyymmdd 03 BMRT-PAYEE-DOB PIC 9(9) COMP. Resolution: In order to resolve this, either modify the Date directive or the COBOL Picture clause so that they match, as follows: $xfd date=yyyyymmdd 03 BMRT-PAYEE-DOB PIC 9(9) COMP. or $xfd date=yyyymmdd 03 BMRT-PAYEE-DOB PIC 9(8) COMP. Incident Number: 2278907 Date: 18 May 2009 Name: Angela Clark Description of change: Date: Name: Description of change: Old

This article identifies different behaviors of "call system" between UNIX environments. Problem: The user program makes a call to system, for example: call "system" using "ls -la" On one system this works as expected, whereas on another it is necessary to add x"00" to the end of the command-line. For example: 01 WORK-COMMAND. 03 COMMAND PIC X(050) VALUE "ls -la" . 03 FILLER PIX X(002) VALUE X" 00" . procedure division.CALL "SYSTEM" USING WORK-COMMAND. Why is this? Resolution: This behavior depends on the case used in the CALL statement. call "system" (all lower-case) calls the OS system utility. This is platform specific, and may give unexpected terminal display results. When you are using the MF function CALL "SYSTEM" (upper-case) you must use x"00" to terminate the command. Incident Number:

This article explains what you can do if you receive this error during compilation. Problem: This error may occur during compilation: “cobchecker64: fatal: relocation error symbol check: referenced symbol not found”. The text of the error message will resemble the following: ld.so.1: cobchecker64: fatal: relocation error: file /opt/cobolse5wp4_64/bin/cobchecker64: symbol check: referenced symbol not found. This is caused by a mistake in the library path environment variable. Resolution: On AIX, the name of the library path environment variable is LIBPATH. On 32-bit HP/UX, it is SHLIB_PATH, and on all other UNIX and Linux platforms, it is LD_LIBRARY_PATH. The environment variable is supposed to contain a colon-delimited list of directory locations where the system linker should look for libraries. When using Server Express, this must include $COBDIR/lib (where $COBDIR is an environment variable pointing to the install location of Serve

This article addresses the unpredictability of the value in the RETURN-CODE special register once COBOL has called an Oracle routine. Problem: In an application that uses Pro*COBOL, COBOL passes control to Oracle routines (for example, during a SQL CONNECT), after which the flow of control returns to COBOL. On one occasion the COBOL special register RETURN-CODE had been modified by Oracle and that it carried a large and meaningless value. This was despite the fact that the SQL statement had succeeded and the SQLCODE was zero. As a rule COBOL does not modify RETURN-CODE (except if the program contains RETURNING syntax or if a fatal runtime error occurs). A meaningless value supplied by Oracle will remained unmodified within COBOL. At the end of the program, COBOL will report this RETURN-CODE to the invoking shell. The shell can access it via "$?", for example: cobrun myprog if [ $? -ne 0 ] then echo "non-zero return code" fi On one occasion, a shell script noti

This article explains why Deletion of Service Interface fields with many subordinate fields hangs for a long period of time. Problem: The process to delete a large Service Interface field in Interface Mapping Toolkit consumes the CPU usage at 100% for a long period, and causes it to hang for a long period of time. This problem is an internal one where the deletion function is doing extra unnecessary manipulation of internal structures, especially when deleting a field that has many subordinate fields. Resolution: This problem was identified in Net Express 5.0, and has now been fixed in Net Express 5.1. Incident Number: 2154960 Old KB# 14380

This article explains how to display active sessions when using the Connection Viewer to monitor RSS clients. Problem: After installing and configuring RSS Server on Windows Server 2003, the Connection Viewer application doesn’t properly display the currently active sessions. Is this due to insufficient permissions granted to the account under which the Connection Viewer is running? If so, how can this be resolved? Resolution: To remedy the problem, find the account that is configured in IIS: On the IIS server where RSS is installed, open the IIS Services Manager Navigate to the Web server instance they are using.  Right click and select “Properties”. In the Web Site Properties dialog, select the “Directory Security” tab. Under the “Authentication and access control” section, click the “Edit…” button. If the “Enable anonymous access” checkbox is selected, make a note of the account in the “User Name” field. Check to see if “Integrated Windows

This article addresses what to do when an error occurs while installing Server Express 5.0 on LINUX. Problem: When installing Server Express version 5.0 on LINUX the following error occurs: "bin/cobconvstrtest: error while loading shared libraries: libstdc .so.6: cannot open shared object file: No such file or directory" Resolution: The Server Express version 5.0 product for LINUX is a dual mode product, meaning it supports both 32 bit and 64 bit COBOL applications. During installation of Server Express 5.0 the install script searches for the 32-bit gcc libraries (libstdc .so.6) located in /usr/lib. If the operating system on the target machine is 64-bit only, then the 64-bit gcc (libstdc .so.6) is installed in /usr/lib64 and the 32-bit libraries are not installed. This error message occurs when the target machine is setup to run only as 64-bit. That is, the target machine does not have the gcc 32-bit installed. The resolution is to download an

This article describes how to overcome the following error produced by the rebuild command: “***Error during sort operation - status 9-037”. Problem: While rebuilding data files with the ‘rebuild’ command, the following error appears: “***Error during sort operation - status 9-037”. What is it and how can it be resolved? Resolution: File status 9-037 indicates a permission problem. It means rebuild does not have permission to create a particular file. Check that the user has write permissions on the output file specified on the "rebuild" command. The rebuild command also creates temporary work files while it runs. By default it tries to create these temporary files in the current directory, so the user must have write permissions in the current directory. If the TMPDIR environment variable is set, rebuild will create its temporary files there, so the user must have write permissions there. In one historical case, an en

Attempting to launch the Web to Host configuration wizard on Windows Vista gives the error message: "No valid extensions are available for configuration!". Problem: When attempting to access a local installation of Web to Host on a Windows Vista PC the following error is encountered: ‘No valid extensions are available for configuration!’ Resolution: This is a result of the MIME type changes noted below and documented by Microsoft at http://support.microsoft.com/default.aspx?scid=kb;en-us;326965 For some reason .htpl files are not recognized by IIS server. After adding *(text/plain) to MIME types on IIS server, those files are read correctly. Old KB# 14431#Web-to-Host#Rumba#OnWeb#ProClient

This article explains how to use the OnWebLog to write information to a file as a script runs. Problem: When scripting in OnWeb at times it may be helpful to write information out to a file as the script runs. For example, if a variable from a previous step is not available to your script, you may wish to capture the value of the variable as the script runs. How is the OnWebLog() method used? Resolution: The syntax of the OnWebLog method is: OnWebLog ("string",["filename"], [iomode]) string Required. The string that you want to record in the log file. filename Optional. The name of the log file. iomode Optional. Either "a" (append) or "w" (replace). Default mode is “a” The default filename is OnWebJS.log and it is located under the bin directory in the OnWeb Server installation (For example: /QOpenSys/usr/OnWeb/bin/ or C:\\Program Files\\NetManage\\OnWeb Server\\bin\\). Date: Name: Description of change: Date: Name: Description of change: Old KB# 14418#Ru

This error occurs running a sample program from the addpack for ACU DataConnect Problem: When running a sample program from the addpack for ACU DataConnect using the following sequence of events, a 173 Called program file not found in drive/directory error can occur. This can be the results of the following sequence of events: The sample program is copied from the COBDIR directory using the following command: cp $COBDIR/sample/acu4gl/demo.cbl to a /tmp or user directory Use the following command to compile the program: cob -v demo.cbl Use the following command to run the program: cobrun demo The following error occurs:Load error : file 'acufh'error code: 173, pc=804, call=1, seg=0173 Called program file not found in drive/directory This error occurs because of the following $set statement: demo.cbl: $set callfh(acufh) The actual file is ACUFH that is, the file name is upper case on disk. Resolution:

This article addresses what to do if you receive a "Failed to load component vsxrte" message when applying the latest WrapPack of Net Express 4.0. Problem: During the install of the latest WrapPack of Net Express 4.0 (ALL08N40.EXE), the IDE FixPack is failing with the following error messages: Failed to load component vsxrte Invalid access to memory location [Abort] [Retry] [Ignore] The above is followed by the message: Microsoft Visual C Runtime Library Runtime Error! Program: This application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information.[OK] From this point, the WrapPack resumes the install with the rest of the FixPacks. At the end, it reports that the following FixPacks were not installed: RTS10N40.EXE, XFH10N40.EXE, and CMP10N40.EXE. Obviously, IDE11N40.EXE was not installed either. Resolution: 1. Stop the Micro Focus Directory Server service by going to Control Panel, Administrator