Rocket® COBOL

Problem: Can a COBOL Application create PostScript files? Resolution: The Server Express COBOL system doesn't contain any PostScript features or functionality however it is possible to generate a PostScript file from within a COBOL application by using Server Express' ability to pipe output to external commands/applications. Create a SELECT statement like the following SELECT OUTPUTFILE ASSIGN TO ">  enscript -r -Picl2 -o out.ps" Organization LINE SEQUENTIAL. Then create an FD for the file: FD OUTPUTFILE. 01  OUT-RECORD  PIC X(256). In the procedure division: OPEN OUTPUT OUTPUTFILE MOVE "SOME TEXT" to OUT-RECORD WRITE OUT-RECORD . . . CLOSE OUTPUTFILE. . . . Ths should produce a file named out.ps that us a PostScript file suitable for printing or use with PostScript friendly applications. Note: If the enscript command is not available , there are several suitable altern

Problem: When using the Inteface Mapping toolkit to expose a COBOL application to Java you can specify a package name for the generated Java. If you use native in the package name then you get an error in the generated Java. For example using "com.microfocus.test.native" would result in an error in the Java. Resolution: This is a restriction of Java. "native" is a keyword in Java and cannot be used in a package name. You need to avoid native in the Java package name. Old KB# 3159

Problem: WrapPack 8 (ALL08N40.EXE) fails with the following error: "Net Express with .NET will not be installed because: Microsoft Visual Studio .NET is not installed" Resolution: The error above indicates that the WrapPack detected Net Express with .NET, and it cannot install the newer version because Microsoft Visual Studio .NET is not installed. The resolution is then to uninstall Net Express with .NET from Add or Remove Programs and re-apply the WrapPack. How could Net Express with .NET be installed without Microsoft Visual Studio .NET? This can be done by having both Net Express with .NET and Microsoft Visual Studio .NET at one point and then uninstalling Microsoft Visual Studio .NET only. The uninstall of the Microsoft product does not automatically remove Net Express with .NET.Old KB# 3000

Problem: cob -iav INTERACT.cbl which creates .idy and .int in the current directory Move source to /home/mysource anim INTERACT Following error receicved Animate INTERACT.int  Level=01  Speed=5   Ins  Caps   Num  Scroll F1=help FILE BELOW NOT FOUND -  Stop run Retry Alter path Zoom INTERACT.cbl Is there something other than COBDATA that must be set for animator to find the source? Resolution: Export COBCPY=/home/mysource COBCPY Specifies the directory or directories that the Compiler and Animator searches COBDATA Specifies the directory or directories that the run-time system is to search Old KB# 3141

Problem: The following XFD FILE directive caused an "Unknown XFD directive" error message to be generated by the ACUCOBOL-GT compiler: $xfd  file=vxml.xml Resolution: The error may be resolved by adding quotes around the full file name as in this example: $xfd  file="vxml.xml" Or by removing the file extension as in this example: $xfd  file=vxml For more information on the XFD FILE directive can be found in the ACUCOBOL-GT User's Guide Version 8.0, Chapter 5: File Processing > 5.3 XFD Files > 5.3.3 Syntax >5.3.3.6 FILE directive. Old KB# 3171

Problem: Applied the Citrix Hotfix Rollup Pack PSE450W2KR02  for Citrix Presentation Server 4.5 ACUCOBOL-GT v 5.2.1, 6.0.0 & 6.1.0 all worked with the new citrix patch. ACUCOBOL-GT v7.1.3 using acuthin from the citrix server to connect to a Sun Solaris 5.8 UNIX box gave the error message: - acuthin.exe - Application Error The application failed to initialize properly (0xc06d007e). Click on OK to terminate the application. Once the system had been rolled back to pre citrix fix all was OK again. ACUCOBOL-GT v 5.2.1, 6.0.0 & 6.1.0 all worked with the new citrix patch it was just 7.1.3 that gave the error message. Resolution: This is a Citrix issue: - The 'application failed to initialize properly' tend to happen before any code is executed (i.e. Windows has a problem starting the app). Go to the following site which outlines the problem:- http://support.citrix.com/forums/thread.jspa?forumID=137&threadID=101062&tstart=0 The recommendation to

Problem: Are you trying to launch acuthin from the client, but the runtime on the server hangs up and does not start? Do you see only a splash screen on the client? Resolution: Check on the server if there's a NOD32 antivirus installed. acurcl has problems with NOD32 and the only way to let him work is to DISABLE the IMON process of NOD32. We have experienced the same problems with PANDA antivirus. In this case, you must have a 2007 PANDA installation at minimum. Then you can select wrun32 and acurcl within PANDA setup, telling antivirus to not block or scan their processes. Old KB# 3092

Problem: The report must have underlined characters and non-underlined characters on the same line.  How is this accomplished with AcuCOBOL-GT? Resolution: It is possible to print regular and underlined characters on the same line.  Here's one way using the WIN$PRINTER and W$FONT library routines. This requires the Windows Runtime. First, call the W$FONT library routine to load a regular font and an underlined font. Then write the line in pieces using WIN$PRINTER to specify the font for each piece of the line, and using the WITH NO ADVANCING phrase on the WRITE statements. The attached sample program, print1.cbl, demonstrates this method. Attachments: Print1.cbl Old KB# 3180

Problem: If an XFD file has been updated and it has already been loaded into the system catalog (syscat), is it necessary to delete the syscat and recreate it from scratch? Resolution: Although, the syscat can be deleted and recreated from scratch, this is not always convenient to do so. Since each XFD is represented as a table in the syscat, a "drop table" command can be issued to drop the corresponding table using the asql.sh script or directly through the xdbcquery utility. Once the drop has been completed, use the addfile.sh script or use the xdbcutil utility to add the modified XFD to the existing syscat. Old KB# 3155

Problem: How can I modify NO-AUTOSEL property for entry-field in ACUCOBOL-GT? MODIFY S1CG01003-T-CAU, NO-AUTOSEL = TRUE or MODIFY S1CG01003-T-CAU, NO-AUTOSEL IS TRUE give compile errors. Resolution: The right syntax is: modify Screen1-Ef-1, NO-AUTOSEL to activate this property or modify Screen1-Ef-1, not NO-AUTOSEL to de-activate it. Old KB# 3183

Problem: A web browser control has been added to a screen. The web browser control displays a web page that requires some information to be keyed in and a "submit" button to be clicked. Some users prefer not to use a mouse, but when the button is selected, it doesn't recognize the "ENTER" key. It seems it only recognizes a mouse click. Resolution: Add the "USE-RETURN" style to the browser's screen section definition.  In AcuBench, add it manually in "Additional Properties". The USE-RETURN style allows the enter key to be active on the web page being viewed.  Pressing enter shouldl submit the form. Old KB# 3175

Problem: Often, it is necessary to get a file trace of a lengthy program, and the file can get rather large. Usually, the size of the trace file can be controlled by using the configuration variable MAX_ERROR_LINES. Sometimes, however, a full trace file is needed. Here is a way to get a compressed file trace on UNIX by using Gzip. Resolution: On the run command add the -g and then the error filename with the extentsion: runcbl -g -lex myerror.gz myprogram.acu To view the fiile use the gunzip command: gunzip myerr.gz Old KB# 3186

Problem: The AcuCOBOL-GT program is executed by an MPE batch job. The program ACCEPTs input from the batch job like this:      !JOB MYPROG,MGR.ACUCOBOL;OUTCLASS=LP,2      !MYPROG.PUB.ACUCOBOL      data-to-be-accepted      !EOJ But when executed the program receives no data. The program is compiled with -Cp and -Ca. Resolution: The Runtime configuration variable ACCEPT_AUTO must be set to 1 either in the Runtime configuration file or in the environment.  This applies to AcuCOBOL-GT 7.3.0, or earlier versions which have been patched with ECNs 3212 and 3309. Old KB# 3182

Problem: When executing a write on one specific table MSSQL raises an error "Invalid character value for cast specification" and the program halts with file status 9D,00 Resolution: The error occurs when the data does not match the database definition for that column.  Specifically in this case the problem was due to a file that contained multiple record formats.   To correctly handle multiple record formats add the WHEN directive to the FD to cause the XFD to be generated in a way that the database will recognize multiple record formats.  For example, the following file definition has three distinct record formats each identified by a separate WHEN directive:        FD  SAMPLEFILE.       $XFD WHEN REC-01-TYPE<5        01  REC-01.           &n

Problem: After creating a grid by using the Drag-and-Drop interface the the (Name) property of this grid could not be changed. Resolution: This behavior is fixed in version 7.2.1 and higher by ECN-WB849. Old KB# 3162

Problem: Is there any way to know the name of the program that is currently running, besides calling another program and in that program using the "C$CALLEDBY" routine? Resolution: In version 6.2.0 the following C$MYFILE library routine was introduced. This routine returns the filename of the disk file containing the currently executing program.    Here is an example of how to use it:        WORKING-STORAGE SECTION.        77  PROGRAM-NAME pic x(80) value spaces.        77  CALL-STATUS pic s99 value 0.        Main Section.                 CALL "C$MYFILE"                  USING PROGRAM-NAME     &nbs

Problem: While using AcuXML to read (parse) XML records the data returned by the runtime on a read of the XML file was only the data for a single field with no file error being generated. The data for each subsequent field was accessible only by doing another read operation. This is the COBOL source from the FILE SECTION: FD  my_xml. 01  my_xml_record.        03  fx1                        PIC X(50).        03  fx2                        PIC X(50).        03  fx3                     &nbsp

Problem: Questions related to  AcuXDBC on 64-bit systems. 1) Does it work on a 64-bit pc?   2) Are there any 64-bit systems that do not work? 3) Are there any changes that must be done? 4) Are there any differences between how AcuXDBC work on 32-bit systems versus 64-bit systems? 5) Are there any known problems experienced wiith 64-bit systems and AcuXDBC? Resolution: 1)  AcuXDBC is supported on 64bit from V7.4 onwards through V8.0. 2) AcuXDBC (Client) is only available as a 32 bit binary. 3) AcuXDBC will install and work on a 64 bit PC but will install and work as a 32 bit. 4) There are no differences between the 64 and 32 bit versions as it only works as a 32 bit. 5) There are no known problems although people taking 64 bit are mentioning Windows Vista which has more security. Old KB# 3151

Problem: An attempt was made to modify Vision data by an update query executed on a linked table in MS Access via AcuODBC.  The error returned was:   Update on linked table xxxx failed.   [Acucorp, Inc.][AcuODBC Driver][ISAM][No data found (#1). Resolution: This error is seen when attempting to update data in a key column.  The data in the key has changed so the SQL processor can no longer locate the row to be updated.  The result is the error "No data found". Key columns cannot be modified.  The correct way to handle it would be to insert a complete new row with the desired data, including the new key data, and then delete the old row. Old KB# 3094

Problem: Application invokes a call to sql.acu to set user to specific value and receives a -1 return code when trying to run the executable with the OCI version of Acu4GL for Oracle. Using Oracle's automated login capability works correctly with older, non-OCI, version of Acu4GL for Oracle. Resolution: In earlier versions of Oracle's OCI interface, it was possible to use OS Authenticated Logon (commonly known as OPS$ logon) using the OCILogon function. In later versions of their OCI interface, they removed this ability.  This would result in the user enncountering an error 9D,1017 which has the definition "ORA-1017: Invalid Username and Password.". The ability to use OS Authenticated Logon has been restored in version 8.1.0 by using the more complex login procedures and credentials in the OCI interface. Please note in later versions of the Oracle database software, OS Authenticated Logon must be turned on.  By defa

Problem: The extend 8 Runtime and Acu4GL for MSSQL were installed and when executing a program a window pops up with a message that the wrun32.2lc license is missing. Wrun32.2lc is the license for the AcuSQL Runtime but that product was not selected during install. How can the Runtime be stopped from displaying that message? Resolution: There is a defect with the Version 8.0 installation which caused it to install an extra dll, one for AcuSQL.  At execution the Runtime sees the dll, checks for the license, then displays the message  about the missing license. The solution is to navigate to the bin directory of your extend 8 installation and delete asqlsrvr.dll. Old KB# 3103

Problem: Trying to connect from Vista 64 bit machine with AcuXDBC client to a remote server where AcuXDBC Server is running,  "Connection error  SQL State 28000, ODBC driver errno 10061" error message is received. Resolution: This error message typically means there is a discrepancy between the port number specified in the DSN on the client machine and the actual port where AcuXDBC Server is running on the server machine. Changing the port number in the DSN to match the one AcuXDBC Server is running on resolves this problem.Old KB# 3156

Problem: A user is trying to create a custom daemon process that invokes a COBOL program from a C program.  The C process listens on a port for incoming socket communication.  When a new request is received, the C process invokes the Solaris fork() system function to spawn a child process. That child process parses the information read from the socket and calls another C function.  Within that C function calls to acu_initv() and acu_cobol() functions are made to run a COBOL program.  When the COBOL program returns, the child process sends a response back to the client and the child process ends.   These steps work fine for a period of time.  Eventually, however, one of these child processes will hang.  It appears to get stuck in acu_initv(). Resolution: There was an infinite loop in the socket layer code between the runtime libraries and AcuShare that causes this behavior. ECN-3836 whi

Problem: Can Net Express run on a 64-bit operating system? Can 32-bit applications be built and still run on a 64-bit operating system? Resolution: When Net Express is installed, it automatically detects the bittage of the operating system. For instance: if the operating system is 64-bit, the 64-bit version of Net Express will be automatically selected and installed. There is no prompt or notification of this event. By default, 64-bit Net Express will still produce 32-bit run-times. If 64-bit run-times are desired, this setting can be changed in the Project Properties. If Net Express is installed on a 32-bit operating system, the applications that get built can still run on a 64-bit operating system. Windows has always come with a component called WOW (Windows on Windows) emulation. It was originally used to allow 16-bit programs to run on 32-bit versions of Windows. WOW64 allows 32-bit applications to run on 64-bit Windows operating systems. This means that any

Problem: An error is recieved when there are 128 or more OR's in the SQL query be submitted to AcuXDBC. The error message is: Internal Error : CGE O OP: Too many OR 's and gives the line number producing the Error. Resolution: The limits for the AcuXDBC SQL processor are: 128 ORs 512 ANDs The resolution is to use a range in the query using the WHERE, e.g.: select * from table_name where column_name is >= 1 or column_name is <=200 instead of: select * from table_name where column_name is = 1 or column_name is = 2 or column_name is = 3 ... and so on until the error is encountered.  Changing the query to the first type will also have a beneficial performance impact and is a more well formed query than the problematic query. Old KB# 3153