Where an entry arose from a problem report, the report's number is given,
to enable Product Support to help you more quickly if you call. These numbers
are called Reported Product Issue (RPI) numbers.
The restrictions covered here are those that are not covered elsewhere in
the documentation, or that are of a temporary nature and may be removed in a
later product. Permanent limits are generally covered in the main help.
The notes below describe some known errors and restrictions in the
Net Express IDE and in unmanaged ( not .NET) code support:
For restrictions with Java software and J2EE application servers, see
Third Party
Software.
For restrictions with Enterprise Server, see
Known Errors and Restrictions in
Micro Focus Server.
If you have installed a WrapPack containing updates to your installation,
the fixes and any last-minute issues are documented in the
WrapPack
Readme. This is downloadable with the WrapPack from
the SupportLine Web site. For details of how to get the latest information see
Updates and
SupportLine
- When converting from COBOL to COBOL with XML syntax, level 88
conditions cause erroneous results.
-
COBSQL cannot process directives within a $SET statement. Any
of the COBOL directives that COBSQL processes should be placed either within
the build/project settings, or in a directives file (for example,
cobol.dir).
-
If an Embedded SQL statement has a comment in columns 73 - 80
and is not terminated by a period, the Oracle precompiler (Pro*Cobol) considers
the next COBOL line as part of the Embedded SQL statement and comments it out.
To prevent this making COBSQL hang, use the COBSQL directive
SQLDEBUG. Then, when COBSQL encounters such a line, it displays:
CSQL-W-040: Pro*Cobol commented out the following line
Note that the program logic is altered because Pro*Cobol has
commented out a COBOL line. It is recommended, therefore, that you do not
execute programs that produce this message. You should either remove the
comment text or terminate the Embedded SQL statement with a period.
-
Using sequence numbers inside Sybase Embedded SQL statements
causes COBSQL to lose its position in the source. This leads to the message
"Premature end of expanded source" being displayed and means the code cannot be
checked.
-
If an EXEC WHENEVER ... END-EXEC or an EXEC DECLARE ...
END-EXEC statement is the last statement in a paragraph or section, you may get
a compilation error on the name of the following paragraph. If this happens,
place an extra COBOL sentence (terminated by a period) after the WHENEVER or
DECLARE statement. For example:
CONTINUE.
-
In a program using object-oriented COBOL, in Working-Storage
declarations at the class level (allowed as an extension to the ISO2002
standard), VALUE clauses have no effect on items declared as floating-point or
fixed-point with more than 18 digits.
-
Long numeric items (those with more than 18 numeric positions)
cannot be used in a Screen Description or with enhanced ACCEPT/DISPLAY
statements.
-
When you use OOCTRL(+P), you may get a protection violation if
the program executes an INVOKE statement where an operand is an OCCURS
DEPENDING data item that does not contain a valid value or - if it is in the
Linkage Section - whose linkage has not been assigned.
-NWB46424
- The Euro symbol does not appear when entered in the Form Designer
editor.
- Enterprise Server does not support the use of Object-oriented COBOL
in CICS or JCL programs.
- When deploying a COBOL service program that uses Object-oriented
COBOL to an enterprise server, you must specify that any container used to run
the service is not reused. To do this, configure the deployment settings as
follows:
- In Net Express, click File > Open Service
Interfaces and navigate to the directory containing the service
interface you want to deploy.
- Double-click the .mpr file containing
your service interfaces.
- In the Service Interfaces pane, right-click the service you want
to deploy.
- Click Settings.
- Make sure that the Deployment Server tab is
selected.
- Check Enable enterprise server run-time
environment.
- Click Configure enterprise server run-time
environment.
- Click the Deployment Characteristics tab.
- Uncheck Reuse container after application
termination.
- Uncheck Reuse container after non-fatal run-time system
error.
- Click OK.
- Click OK.
-
Using Btrieve, a START operation cannot be performed with a
part-key. The whole key must be used.
- If you have a firewall on your machine, when you load a project into
the Net Express IDE the firewall might report that ….\net
express\bin\mfds.exe is trying to access your machine. You should
allow this access, and set your firewall to allow it permanently.
-
When you select a Select control by left-clicking the mouse,
the first click may not actually select the control, even though the selection
border appears around the control; in this case the Property Tree View
indicates that the previously selected object is still selected. If you click
on the Select control a second time it will become selected. This behavior may
result in you copying, cutting or deleting the wrong control. You can always
use the Undo command to return to the previous state.
-520313
-
Generating a server-side program for a form that contains a
Java applet can cause a protection violation if you leave the form open while
generating the program. You should close the form before starting the Internet
Application Wizard.
-512589
-
Ctrl-S, the accelerator key for
Save, does not work in Form Designer.
-
When loading a frameset into Form Designer only the actual
frameset can be edited and the internal frames cannot. No in-place editing is
allowed.
-
Projects created using Form Designer in Net Express 1.0
incorrectly built the CGI executables as graphical applications rather than
character mode applications, resulting in the COBOL text window appearing when
animating.
To correct this, you need to change the mode to character. With the
project loaded, select Generic Release Build, then
right-click on the executable file and click Build Settings.
Click the Link tab, and select Character.
Click Close and then rebuild the project.
This problem does not exist in projects created in Net Express
2.0.
-502232
-
On an HTML form at run time, data entered into a field
declared in Form Designer as alphabetic (COBOL PIC
A(n)) is not validated to ensure it is alphabetic.
-
The captions for entry fields on an HTML form do not display
as expected when previewed in your Web browser, if the form is used as an
output form for one or more CGI programs.
For example, if you create an entry field (the Input control under
HTML) on an HTML form, and preview the form in your Web browser, the caption
displays as ":f-Input1" regardless of the caption entered.
The HTML form contains substitution markers so that they can be
output by COBOL programs using Embedded HTML, and it is the substitution
markers which you see when displaying the form directly through a Browser. To
display the form correctly, display it by running the server-side program
associated with it.
-NWB45788
- Under Windows 2000 and later operating systems, if you receive an
error message when you try to open a topic in the Help, click No to the
question about wanting to debug.
To use the IBM IMS TM or IBM IMS DB compatibility features you must have
installed WrapPack 3 for Net Express 5.0, Server Express 5.0 and/or Micro Focus
Server 5.0. See
Updates and
SupportLine for information about finding updates.
The following list summarizes general restrictions with the support for
IMS:
- Support is only available for ASCII.
- There is no integrated debug support.
- Diagnostic tools are limited.
- There is no licensing specifically for IMS Support.
The following list summarizes known restrictions in IMS DB
functionality:
- JCL is supported except for GSAM/FastPath utilities.
- No migration tools are available.
- The RULES=HERE clause is not supported on a SEGM statement for
logical children. If such a clause is encountered it is changed to RULES=LAST
and warning DBDUT0W09W is displayed.
The following aspects of IMS TM behavior are not supported:
- /BROADCAST or /DISPLAY
- IMS Connect
- in-doubt transactions
- MFS commands
- MQSeries
- operator control
- segment exits
- SYSMSG HELD conversations
- unprotected terminals
The following list summarizes known restrictions in IMS TM
functionality:
- Models other than MOD2 have not been thoroughly tested.
- MFSGEN currently only gens for a single terminal model.
- TM semantic behavior is slightly different than on the host.
- Support is provided for a subset of commands (/FOR, /SIG, /HOLD,
/RELEASE, /RCL, /EXIT, /START (only tran), /STOP (only tran))
- Performance has not been optimized.
- Sign-on is mandatory, and queues are user-based.
- The null character is different in ASCII (0x1a) and EBCDIC (0x3f) so
you must make changes to any application that uses nulls.
-
If you are viewing source code in a text window, and you have
not compiled the program, a copyfile cannot be opened if the copyfile name is
on a different line from the COPY verb. If the verb and the copyfile name are
on the same line, but the rest of the statement is on other lines, the file
will be expanded immediately after the line containing the verb and filename.
-
If a class inherits with data, the IDE hangs if there is an
in-line comment at the end of the line containing the Object-Storage Section
header in the Class-Object.
-
Autofix has no effect when you have more than one view open on
a file.
- NWB42762
-
In the Configure Toolbar dialog box, you can't add an icon at
the end of the toolbar. The icon is always inserted above the current icon. You
can get around this by inserting an item and then moving it to the end.
-NWB42837
- Windows Form and Web Form test clients will not be generated if a
service interface contains nested input field groups. If nested input groups
are detected, a message to that effect will be displayed in the Output Window,
and the Windows Form and Web Form clients will not be generated.
- Each group field (i.e. field containing subitems) in a Java interface
must have a name that is unique across all operations of that interface. Where
this is not the case, client generation may fail.
- If you encounter an error message “>>> COBOL Interface
generation failed Could not find a part of the path <path>” when
generating test clients for service interfaces, the likely cause is that
Microsoft Internet Information Server (IIS) is not installed on your system.
See
Net Express Software
Requirements
-
When your application disconnects from a Sybase database after
retrieving data from it and displaying the data in a Web form, you may get RTS
error 114 (Attempt to access item beyond bounds of memory) against _SQLODBC.
To fix this, please obtain patch SWR7181 from Sybase.
- If you have Windows 20000 or NT configured to use large fonts, forms
created using the Internet Application Wizard have overlapping controls, and if
you load such a form into Form Designer the controls may appear in the top
left-hand corner. However, such forms appear correctly in Web browsers.
-
Entry fields on forms generated by the Internet Application
Wizard sometimes appear smaller than the data they hold. For example, an entry
field for a five-character column might sometimes scroll at four characters.
This is because browsers display the contents of entry fields using
proportional fonts, and set the physical size of the entry field using an
average value for the width of characters. So "11111" displays inside the entry
field without scrolling, but "WWWWW" does not.
-
The OpenESQL connectivity used by the Internet Application
Wizard does not support pooling of connections. If you convert a Internet
Application Wizard application for ISAPI or NSAPI, you can't share a database
connection between different threads. The database connection must be opened
and closed at the start and end of each transaction. The default code generated
for you does this.
If you convert to ISAPI/NSAPI you should compile with
SQL(THREAD=ISOLATE) to ensure that SQL resources used by threads are isolated
from each other. You should not use the SQL(CONNECTIONPOOL=) directive, as the
application server itself is responsible for managing connection pooling.
-
If you try to access data in floating point columns (SQL-REAL,
SQL-FLOAT, SQL-DOUBLE) that falls outside the range that can be represented by
pic 9(14)v9(4) comp-3, Data Wizard applications will report errors at run time.
-
Although Internet Application Wizard does not allow you to
include a path when you specify a filename in the Filenames dialog box, it
doesnt strip off the path if you do specify one. Instead, it displays a message
asking you to do so. (You cannot specify a path because Internet Application
Wizard always assumes the current project directory.)
Please either find the file by browsing, or strip off the path when
it is displayed in Internet Application Wizards Filenames dialog box.
-503055 & 503056
-
If your legacy program has an 01 parameter with an OCCURS
clause, the generated CGI app compiles with the following error on the call to
the legacy program:
1022-E Table item not subscripted or indexed. First occurrence
assumed.
You can suppress this error with the following compiler
directive:
$set change-message(1022 W)
This enables the application to be compiled and run.
- The documentation gives the wrong location of the resource adapters,
which are used for connecting J2EE application servers to Micro Focus Server.
The resource adapters are located in subdirectories of
base\bin\j2ee13 and base\bin\j2ee14
directories of your COBOL development system and also on the separate CD
containing Micro Focus Server. Each supported J2EE application server has its
own subdirectory, such as base\bin\j2ee13\beaweblogic8.
- 543541
- The documentation on the WebLogic startup script gives incorrect
paths to the mfcobolpure.jar and
mfconnector.jar files. Also the script works only if the
jar files are installed in locations with non-spacey paths. The instructions
should read:
If Micro Focus Server (or your COBOL development system) is
installed in a location that uses a spacey path, you need to copy the following
files to a non-spacey location:
- mfcobolpure.jar - This is by default in the
bin directory of your Micro Focus Server installation or
your COBOL development system installation.
- mfconnector.jar - This is by default in
the bin\j2ee-version\appserver directory of your Micro
Focus Server installation or your COBOL development system installation. You
need the jar file that corresponds to the WebLogic version that you are using,
such as j2ee13\beaweblogic8 or
j2ee14\beaweblogic9
Above the line @rem Call WebLogic Server, add the following lines:
set java_home=jdk-dir
set mf_home=mfcobolpure-dir
set classpath=%java_home%\lib\tools.jar;
%mf_home%\mfconnector-path\mfconnector.jar;
%mf_home%\mfcobolpure.jar
Where:
- jdk-dir is the location of your JDK installation for WebLogic.
You must not point this to any other JDK installation.
- mfcobolpure-dir is the directory containing mfcobolpure.jar.
- mfconnector-path is the path containing the required
mfconnector.jar. If you have copied this jar into the same directory as
mfcobolpure.jar, you don't need to specify this path.
- 543541
- If CICS programs are called from a service-based request that access
VSAM resources controlled by Fileshare then a 114 error in utils.lbr\fhrsub.gnt
might occur at task syncpoint processing. This error occurs only if Fileshare
has not be accessed by the SEP prior to the execution of a service-based EXCI
call. To avoid this, ensure that each SEP accesses Fileshare during phase two
Program List Table Post Initialisation (PLTPI) processing.
- If you have clients using the ECI interface with the CICS Transaction
Gateway to communicate with a CICS application running in Mainframe Transaction
Option (MTO), a client program might receive an ECI_ERR_TRANSACTION_ABEND
return code with an abend code of AZTY, indicating that several clients tried
to communicate with the system at the same time but not all requests could be
satisfied by MTO. The workaround for this issue is to set the environment
variable TX_UNICLI_SESSIONS to the required number of sessions in the
Configuration Information for the enterprise server as follows:
[ES-Environment]
TX_UNICLI_SESSIONS=<required-number-of-sessions>
The default is 4.
You should set "Maximum requests" in the Client Section of the CICS
Transaction Gateway configuration to the same value.
If you do this you will also probably need to change the client
program to ignore the ECI-ERROR_MAX_SESSIONS return code and retry the call.
For example
do
{
Rc = CICS_ExternalCall (&EciParms);
} while (Rc == ECI_ERR_MAX_SESSIONS);
If you do not make this modification, the client program might still
receive the ECI_ERR_TRANSACTION_ABEND return code.
- The Enterprise Server Administration\Micro Focus Directory Server
(MFDS) service is not restarted during Net Express 5.0 WrapPack 4 setup on
Windows Vista. As a consequence, the Micro Focus Directory Server service may
need to be manually stopped and restarted by a user with Administrator
privilege before the new WrapPack 4 executable version is loaded. This can be
done via the standard Windows service GUI, or by using "net stop mf_ccitcp2"
and "net start mf_ccitcp2" from the command line using the "Run as
administrator" option.
- 547044
- When you deploy a COBOL application as a Web Service or an Enterprise
JavaBean, then run it using the default configuration of Enterprise Server, it
can no longer open files across a network using drive mappings or UNC paths
(that is, file pathnames of the form \\server\share\path\to\file). This is the
result of Windows working the way it was designed to and there is no simple
workaround that is satisfactory for every customer.
When a program opens a file on another computer (the file server)
using a UNC path, Windows uses that program's current security information to
try to authenticate it to the server and obtain authorization from the server
for access to the file. If the file server does not accept the program's
security credentials, the program cannot open the file. These credentials
include user login information (the equivalent of a username and password) and
other technical details including whether the credentials can be used for
network access. If an interactive user runs a program from the desktop or
command line, that process runs with the user's credentials. When the program
attempts to open a file on a file server, the user's credentials are checked
for access.
When a drive letter is mapped to a network share and used to open a
file, Windows uses the same mechanism as for UNC paths. However, a drive letter
mapping generally applies only to a specific user. A different user on the same
computer can have that drive letter mapped to a different share or not mapped
at all.
This means that UNC paths represent the same file for every program,
no matter which user account the program is running under but that drive letter
mappings can vary and are less likely to work when a program is run by
different users. In general, UNC paths are more suitable for filenames that are
stored in programs or saved somewhere and drive letter mappings are more
suitable for interactive use.
For further advice see the chapter Configuration in
your Enterprise Server Configuration and Administration
book
- 1052982
- If you browse an OO application that uses ISO 2002 multiple
inheritance, only one of the inheritance links is shown.
- 529575
- You cannot use an inline invoke for a method defined after it. For
example, you cannot write:
method-id. "method1".
procedure division.
move objref::"method2"(a,b,c) to d
end method "method1"
method-id. "method2".
linkage section.
...
procedure division using a b c returning d.
...
exit method
end method "method2"
To avoid this problem, use an INVOKE statement instead.
- A class cannot use property syntax on a property it has itself
defined.
- See also
Deploying to Enterprise
Server for errors and restrictions concerning the deployment of
Object-oriented COBOL.
- When using Oracle's ODBC driver, array fetches and some scrolling
fetches might produce inconsistent behavior if you change the array size
between fetches. To overcome this, build your application with
SQL(NORESULTARRAY). When this is set, OpenESQL performs single row fetches
under the covers, bypassing this limitation.
- At the time of release, we are aware of some issues with local
transaction support with Oracle 9.0.4. If you use Oracle and need local
transaction support, please contact Support for the hot fix that resolves these
issues.
- If you open a project that was closed with compilation errors in your
source programs, and you have breakpoints set in the source, you get RTS error
114 in CDI2.gnt. To fix this, delete the
.idy file.
- 529974
-
Projects in the IDE that build type libraries
(.tlb files) from .idl or
.odl files always report that they need rebuilding.
This is because the .tlb file is built in the
project directory instead of the Release or
Debug directory. When running an application, so long as the
type library has been built and is up to date, you can either ignore the
request to rebuild or copy the .tlb file into the
appropriate directory.
If you make any changes that cause the type library to be updated,
you should delete any copy made before rebuilding.
This applies to COM and ActiveX control projects.
-508417
-
In a project, the dependency checking for a copyfile in a
program does not work correctly for a copyfile in the Class-Control
paragraph.-NWB42724
-
The Image Editor accepts bitmaps in Windows 3.0 bitmap format
only, and accepts no more than 16 colors.
-NWB42974
-
If, after editing a menu file referenced in a
.rc file, you close the .rc file
before rebuilding, the resource .dll file doesn't get
rebuilt. You should rebuild after closing the menu file but before closing the
.rc file.
-
Net Express does not support environment variables with
names containing embedded spaces.
-
When running .int code, you get incorrect
results when you query data items in the Thread-Local-Storage Section if the
program has not yet accessed Thread-Local-Storage.
-
The use of EXTERNAL data or files in the STATIC (or FACTORY)
area of class programs will produce either compile-time or run-time
errors.
- In mainframe emulation of DFSORT, the run-time system error COBRT252
"Memory corruption detected (Fatal)”, might occur when performing a SORT
FIELDS=COPY on a file with a record format of VB.
- In mainframe sort emulation, under certain circumstances when sorting
records using RECORD TYPE = VB, records are truncated by 4 characters.
- If you want to run the XDB server as a Windows NT service on a PC
running Net Express that was installed as a client lite installation from
a server, you need to specify a user account to be able to access resources on
the server machine. To do this, perform the following steps:
- Click Settings > Control Panel on the
Windows Start menu.
- Double-click Services.
- Select Micro Focus XDB server for NX 5.1, and
click Startup.
- Click This Account.
- Click the Browse button
next to the
This Account field.
- Double-click your user account, and click OK.
- Specify the password in the Password field,
and again in the Confirm Password field.
- Click OK.
You can now successfully run the XDB server as a service.
- If you are using Windows NT and have installed SQL Option for DB2
from Net Express 5.1 or Mainframe Express 3.0, the XDB server is installed
as an NT service. Only one XDB server can run at the same time, so if you are
using SQL Option for DB2 with Net Express and Mainframe Express, you need
to manage your XDB server services depending on which product you are using.
For example, if you need to use the XDB server with
Net Express, you need to ensure that the Mainframe Express XDB server
service is not started automatically. To do this, perform the following
operations:
- Click Settings > Control Panel on the
Windows Start menu.
- Double-click Services.
- Select Micro Focus XDB Server for NX 5.1 and
click Startup.
- Click Manual, then click
OK.
- Click Close.
When you have done this, the XDB server service for Mainframe
Express is not started as a service, enabling you to use the XDB server for Net
Express. (If the Mainframe Express XDB server is already running, you will need
to shut it down before you can start the Net Express XDB server. See your
Mainframe Express documentation for information on how to do this.)
- Programs in .exe or .dll
format that have been compiled with the TESTCOVER directive set, and have been
run under the TESTCOVER environment, might find that at the reporting stage the
.idy or .cbl/.cpy files cannot be
found when creating reports from the results file(s). To work around this, run
the tcreport utility from the directory containing the
.idy/.cbl/.cpy files.
- 530281
- If you install Workflow Capture Server, the system creates the
registry key HKEY_LOCAL_MACHINE \SOFTWARE\MicroQuill. This key is not removed
when you uninstall.
- When using the following format in the .mfenv
file to specify environment variables to be used on the target UNIX system:
env-var1=$(env-var2)/setting
you cannot specify more than one environment variable on the
right-hand side of the equals sign.
-
If you create an application using Character Dialog System and
link it on the PC, then, when you publish it to UNIX, Publisher will try to
link it on UNIX. This link will fail because the run-time support module DSRUN
is supplied on UNIX only as a .gnt file, not as an
.o file.
To automatically link the DSRUN module on UNIX, select
Settings on Net Expresss UNIX menu and click
Additional Build Options. Add -d DSRUN or
-U to each line that has an executable module as the target.
-
If you have installed the UNIX Option in a directory whose
path is longer than 52 characters, Character Dialog System may produce
unpredictable results.
-
Net Express only supports the creation of ISAPI Extension
DLLs. It does not support the creation of ISAPI Filter DLLs. Any references in
the documentation to ISAPI DLLs should be taken as referring to ISAPI Extension
DLLs.
-
If your Web browser is configured to use a proxy server, Solo
and Form Designer cannot function properly until you make some configuration
changes. You must reconfigure your browser either not to use the proxy server
for the Solo Web address, or not to use the proxy server at all.
To reconfigure your browser not to use the proxy server for the Solo
Web address:
- On Internet Explorer, click Options on the
View menu, then click the Connection tab
on the Options dialog box. Click the
Settings button, and type 127.0.0.1 in the Do not
use proxy server for addresses beginning with field. Then close all
the dialogs.
- On Netscape Navigator Communicator, click
Preferences on the Edit menu, then on the
Category tree view expand the entries under
Advanced and click Proxies.
- If manual proxy configuration is selected click the
View button, and type 127.0.0.1 in the Do not use
proxy server for domains beginning with field.
- If automatic proxy configuration is selected, speak to your
network administrator about getting this domain excluded from the proxy.
- On other browsers, consult your browser documentation to find out
how to exclude specific domains from proxy look up.
To reconfigure your browser not to use the proxy server at all:
- On Internet Explorer, click Options on the
View menu, then click the Connection tab
on the Options dialog box. Uncheck the Connect
through a Proxy Server checkbox.
- On Netscape Navigator Communicator, click
Preferences on the Edit menu, then on the
Category tree view expand the entries under
Advanced and click Proxies. Click the
No proxies radio button.
- For other Web browsers, consult your Web browser documentation.
Consult your network administrator for information about the
implications of reconfiguring the browser not to use a proxy server. After you
have reconfigured your browser, run the Solo troubleshooter again to see if
Solo is now operating.
-
On some computers, the Netscape Navigator browser does not
become visible when Net Express starts it. You should load Netscape
Navigator yourself before trying to use it to test your CGI program.
-NWB47496
- If a transaction start fails, WebLogic will hang.
-543022
- On 64-bit Windows platforms, the current version of XML support
reads/ writes only local XML documents. Support for remote XML documents will
be added in a future release.
- If you use the ODOSLIDE directive when compiling your program, no XD
records may contain an OCCURS DEPENDING ON clause.
- 1051500
64-bit - Unsupported
Features