Rocket® COBOL

This article provides step-by-step instructions for setting up AcuXDBC Server on a UNIX operating system. Problem: This article clarifies the documentation with specific instructions for setup, testing, and implementation of AcuXDBC Server on UNIX systems with Windows clients. Resolution: AcuXDBC/AcuXDBCS Installation on UNIX The installation should look like this — ensure that all of these files are in the /bin directory (dates and permissions vary): $ ls -latotal 35664drwxr-xr-x 2 techsup staff 4096 May 14 06:20 .drwxr-xr-x 7 techsup staff 256 May 13 11:15 ..-rwxr-xr-x 1 techsup staff 286332 May 13 10:32 activator-rwxr-xr-x 1 techsup staff 1078462 May 13 10:32 acurcl-rwxr-xr-x 1 techsup staff 843430 May 13 10:32 acuserve-rwxr-xr-x 1 techsup staff 416882 May 13 10:32 acushare-rwxr-xr-x 1 techsup staff 667958 May 13 10:32 acusort-rwxr-xr-x 1 techsup staff 671442 May 13 10:32 acusql-r

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 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 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

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 discusses the following error: RM-AddOnInit failed in the wow Runtime dll and WOW MFC Runtime (wowmfcrt.dll) load failure Problem: When attempting to run a WOW Extensions v12 application on Windows 2000 (thick or thin client) you experience the following errors: RM-AddOnInit failed in the wow Runtime dll” and “WOW MFC Runtime (wowmfcrt.dll) load failure Resolution: Deploy the attached uxtheme.dll into the directory containing the wowmfcrt.dll. This DLL provides stubs for the theme functions used by the WOW runtime. Note: The un-themed WOW runtime references these function but does not attempt to call them as Microsoft doesn’t provide theme support on Windows 2000. Incident Number: 2284518 Old KB# 14451

This article describes a scenario that uses the XFD_MAP variable and provides an example for using one XFD for more than one file or table. Problem: In this scenario, the use of a single XFD is desired rather than many XFDs, one for each of several different tables. The table names have the pattern "???MYHIS" where each "?" represents a variable character in the table name. However, putting "*MYHIS=[abcmyhis.xfd]" in the ACUFH configuration file (mfdbc.conf) does not work. What values should be in the SELECT for the ASSIGN TO and the $XFD FILE= directive in the FD for this to work properly? Resolution: The following is a step-by-step explanation: The program has a SELECT for a file ABCMYHIS, with a variable assigned, something like this:SELECT ABCMYHIS ASSIGN TO WS-ABCMYHIS-NAME ... Immediately before the FD, there is an XFD FILE directive, which is required because of the variable ASSIGN:$XFD FILE= ABCMYHI

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 –geometr

This article provides instructions on how to extract the installation media from the downloaded UNIX gunzip tar archive. Problem: After downloading a UNIX gunzip tar deliverable, follow the steps below to decompress the deliverable and create the installation components. These instructions assume that gunzip has already been installed. The gunzip tool is available at www.gzip.org, both in source form and as executable files. This tool runs on a number of platforms, including Windows. Note that other Windows ZIP tools can also decompress a gunzip tar file; however, you should be careful when extracting files from the resulting tar file. Make sure that any tar file CR/LF conversion option is turned off. Resolution: Save the License Certificate attached to the electronic delivery email. Following the download, change the working directory to the directory that contains the deliverable. The deliverable will have a name in the form deliverable.tar.gz, w

This article describes how to enable Windows XP and Vista themes. Problem: WOW Extensions has a default look and feel based upon Windows 98 controls. This can make an application developed using WOW Extensions to look quite dated. Resolution: Windows XP and Vista interface provides a more modern look and feel, i.e. themes. You can enable the theme support by simply replacing the existing wowmfcrt.dll with the one attached in this article. Note: Theme support has been provided via Microsoft’s manifest technique. This technique has some known problems with redrawing certain controls and container controls. It is highly recommended to backup your existing wowmfcrt.dll and aggressively test your application to ensure that the interface behaves as you expect, changes may be required to provide workarounds for unwanted behavior. Theme support is provided “as is”. This DLL is only suitable for version 12. Incident Number: 2282338 C:\\wowmfcrt.zipDate: Name: Description of change: Date:

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 describes a possible reason for the run-time system error 9/107 and a potential work around. Problem: COBOL programs were compiled using the CREATEXFD and CALLFH (ACUFH) directives as required for Database Connectors. An XFD file was generated. The database being accessed was Oracle 10g.The program received a 9/107 error on OPEN OUTPUT, but a table was created in the database. The Consolidated Trace Facility (CTF) log (rts32.textfile.PID.log) revealed the following generated SQL: CREATE TABLE ... succeedsALTER TABLE MYTABLE ADD CONSTRAINT iMYTABLE_0 PRIMARY KEY () ... fails: ORA-00936: missing expression Resolution: Examining the COBOL program source revealed that the VAR-LENGTH XFD directive had been misplaced, causing the Compiler to generate an invalid XFD file. Note the difference in the position of the VAR-LENGTH directive in the examples below. Example 2 shows the correct location. Example 1 03 MY-SERVICE REDEFINES MY

This article describes a potential solution for the error ORA-01000. Problem: A COBOL program that performs numerous file operations (OPEN, READ, WRITE, DELETE, REWRITE, CLOSE, and so on) has the potential to create a large number of cursors if no COBOL COMMIT exists in the program code. If left unmanaged, it is possible to run out of cursors and receive an Oracle error "ORA-01000: maximum open cursors exceeded" as shown in the run-time trace below. 23:35:50.384 0 MF.RTS 51 1 : "ERROR CODE = [1000]"23:35:50.384 0 MF.RTS 51 1 : "ORA-01000: maximum open cursors exceeded" Resolution: There are two ACUFH configuration variables that may be helpful in managing cursors counts. Note: Both of these variables may require some experimentation and discussion with your Database Administrator to determine what works best for your application and system. The first variable is A_ORA_MAX_FILE_CURSORS, which by default is set to “0

This article provides information on the location of the vutil error code table and an example of using the table in problem resolution. Problem: When performing a file operation using vutil or vutil32, an error may be encountered. For example, the following vutil command vutil -info MYFILE may result in the following error: MYFILE: File broken (code 69) Understanding what “code 69” means would be helpful in resolving this error. Resolution: Vutil error codes are the same as the Vision file secondary error codes for error 98. The list of error codes may be found in the ACUCOBOL-GT Appendices Version 8.1, Appendix E: File Status Codes, E.3 Vision Secondary Error Codes for Error 98s. For this example, the entry in the list of errors would be: 69 A Vision 4 or 5 index segment is not found during an open. This error code is specific to Vision 4 or 5 files that consist of two parts, a data segment and an index segment. T

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 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 explains what to do if OEM font special characters don't display correctly in Microsoft Access or Excel. Problem: When reading from a file in which data was written using OEM font information (usually from an old DOS character-based system), special characters like $ and £ do not display correctly in Microsoft Access and Excel. The special characters display correctly, however, when using the AcuXDBC utilities asql or odbcsql. Previously, AcuODBC had an option that allowed the character set to be chosen (ANSI or OEM); this option is not available in AcuXDBC. Resolution: AcuXDBC does not have the character map functionality that AcuODBC had. The resolution to this issue is to convert the OEM font data to ANSI font data, which will display correctly in Windows-based business intelligence tools. Old KB# 14512

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 article describes how to retrieve UNIX time values and translate them to COBOL style values using C language functions. Problem: UNIX dates and time are frequently stored as a single integer containing the number of seconds since January 1, 1970. It is a convenient way for C language functions to store date and time stamps. The COBOL system uses a different scheme to keep track of date and time and there are times when a bit of translation from one representation to another is required. What special handling is required to transform this time to a useful and readable format? Resolution: UNIX time values can be retrieved and translated to COBOL style values by using C language functions which call the ctime() family of functions to manipulate the date and time to and from UNIX time formats. The attached example program uses this method to get the current date and time in UNIX Time form and then translate it to a human readable format. Extract the source fi

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 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:

When a program is selected in the Browse tool, the .idy file of the program is locked. Problem: When a program is selected in the Browse tool, the .idy file of the program is locked. Therefore, the .idy file cannot be deleted or moved. Resolution: This problem is present in all versions before Net Express 5.1, and has been resolved in Net Express 5.1. Incident Number: 2125448 Old KB# 14382

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 the changes required to run multiple instances of OnWeb server on an iSeries. Problem: When multiple instances of OnWeb Server are required to run on the same iSeries configuration changes are necessary to avoid resource contention. What are these? Resolution: You can install multiple OnWeb Servers on an iSeries system byperforming the following steps: Specify a different HTTP Server directory Install the second instance of OnWeb Server into a different BaseLibrary and installation directory on the IFS. During theinstallation make sure you specify a unique Internal Server Portnumber Due to restrictions in the operating system, it is only permissibleto have one active subsystem with the same name. When installingmore than one server on the same iSeries, you will have to renamethe subsystem of the subsequent server(s) from OnWeb to a differentname. Enter the following commands:RNMOBJ OBJ(Base_Library/ONWEB)OBJTYPE(*SBSD) NEWOBJ(Subsystem_Name) CHGDTAARA DT

This article explains what to do if the message No license AS GLOBAL occurs. Problem: After a new installation or upgrade of Server Express, we are unable to run compiled programs and receive the following No license AS GLOBAL error message. Why is this happening? /var/mfaslmf > cat USERLOG Mon Jan 28 06:40:41 PST 2008: No license AS GLOBAL Resolution: This error occurs because there are no valid Developer Usage licenses in a Server Express product. Either the licenses don't exist or they are expired. There may be a number of Application Server or Server CPU licenses installed. The most common cause for this is installing the Server Express product instead of Server for COBOL. If no compiling will be done on this machine, remove the entire $COBDIR directory and install the correct product. Also remove any /etc/mflmrcscript files. Make sure $COBDIR points to a Server for COBOL product directory. If Server Express is also to be used on t