| CA |
2.0 Operating System Support
2.1 CA Aion BRE
3.0 System Requirements
3.1 Hardware Requirements
3.2 Pre-Installation Requirements
3.3 Third-Party Software Compatibility
3.3.1 Databases
3.3.2 Compliers for CA Aion BRE
3.3.3 z/OS Requirements for CA Aion BRE
3.3.4 Linux x86_64 Requirements for CA Aion BRE
3.3.5 Web Application Servers
3.3.6 WebSphere application server for CA Aion BRE
4.0 Installation Considerations for Windows
4.1 Installation Drive Must Be Mapped and Not Attached
4.2 Requirements for Installing CA Aion BRE
4.3 Post-Installation Considerations for UNIX/Linux
4.3.1 AionBuilder
5.0 Installation Considerations for Mainframes
6.0 General Considerations
6.1 Compatibility Between CA Aion BRE r11 and Previous Releases
6.2 CA Aion BRE UNIX/Linux-Specific Information
6.3 CA Aion BRE Mainframe Specific Information
6.4 Running Ant Scripts That Deploy CA Aion as a Web Service
6.5 CA Aion BRE Java Interface Layer
6.6 CA Aion BRE Dynamic Rule Repository
6.7 Source Code Control Program Installation
6.8 Environmental Requirements for UNIX/Linux Installations
6.8.1 Oracle
6.8.2 Sybase
6.8.3 DB2 UDB
6.8.4 IBM WebSphere MQ
6.8.5 Servlet Containers and Web Servers
6.8.6 Access remote Rule Manager
6.9 MAES Secure Socket Layer (SSL) Communications Setup
6.9.1 Define SSL self-signed certificate
6.9.2 FTP exported MAES SSL certificate to Java environment
6.9.3 Java key store setup
6.9.4 Prepare MAES SSL configuration information (MAESSSLX)
6.9.5 Java SSL Client Program
6.10 Administrative Privilege Requirements for Windows
6.11 Getting Additional Information Out of the Maes Logs
6.12 Disabling Static SQL Multiple Row Fetch in DB2 v8 Environments that Lack NFM Capabilities
6.13 Setting Size Value for Binary Parameter Values in COBOL or PL/1 Programs
6.14 Uninstallation Consideration
7.0 Known Issues
7.1 Aion BRE installation log file
7.2 Directories with Special Characters
7.3 Uninstall Process on HP-UX
7.4 Incorrect Product Qualifier in Translated PDF Tables of Contents
7.5 Unicode Version of Aion BRE on Windows
7.6 MAES Shutdown with Low SSL Activity
7.7 MAES Health Checker is for VTAM And TCPIP Only
7.8 Not Enough Memory to Compile Application with AIX IBM XL C/C++ Compiler
7.9 DB2 Static SQL does not Work on the Windows Platform
7.10 Obtaining CA Health Checker Common Service
7.11 Additional Information out of the MAES LOG File
7.12 <aionhlq>MAES.JCL(CEEUOPT)
7.13 BIND DB2 8 Compatibility Mode
10.0 Documentation
10.1 Release Numbers on Documentation
12.0 Contact Technical Support
Welcome to CA Aion® Business Rules Expert r11. This document contains installation considerations, operating system support, and known issues for CA Aion Business Rules Expert (Aion BRE). For documentation updates, contact Customer Support at http://ca.com/support. Use the Support link to access the latest documentation.
Note: Throughout this document, the directory in which CA Aion BRE r11 is installed is referred to as <aion_install_dir>. When files and commands are discussed, all file separators are presented as backward slashes (\); however, these symbols should be read as forward slashes (/) for all UNIX and Linux platforms. For example, the installation directory may be C:\Program Files\CA\Aion on Microsoft Windows platforms or /opt/CA/AionBRE on UNIX and Linux platforms.
This section describes operating system support for CA Aion BRE r11.
The following operating systems are supported for compiling and deploying components written using Aion BRE:
The Aion Interactive Development Environment (IDE) and Debugger are only supported on those Microsoft Windows platforms listed above.
CA Aion BRE r11 is a 32bit application that can run on a 64bit operating system. Aion requires the 32bit version of database drivers and others modules that it may call. Aion will not work with the 64 bit version of these drivers or other modules.
For CA Aion BRE, the system requirements for the Microsoft Windows-based development environment are:
CA Aion BRE requires a license file in order to be fully functional. If you are downloading CA Aion BRE and need to obtain a license file, contact your local CA Total License Care group or visit http://ca.com/support for information about how to contact TLC.
System requirements for CA Aion BRE on z/OS can be found in the Mainframe Installation Guide.
Note: On the Windows platform, 240 MB free disk space is required for a full product installation of CA Aion BRE r11. On Linux or UNIX, 430 MB free disk space is required during installation for a full product installation while 280 MB of disk space is used after the installation.
The following are the pre-installation requirements:
To be accessible the path environment variable must contain $JAVA_HOME/bin where $JAVA_HOME/bin is the directory where the Java runtime executable is installed. If the JRE is not accessible to the installation package or $JAVA_HOME/bin points to the version that is lower than version 1.5, the installation will fail with a message similar to "No Java virtual machine could be found from your PATH environment variable. You must install a VM prior to running this program." or a message indicating that there is an error loading the Java VM.
The following section lists the third-party software that is compatible with CA Aion BRE r11.
The following databases are supported by CA Aion BRE:
| Operating System | Compiler |
|---|---|
| Microsoft Windows | Microsoft Visual Studio 2005 SP1 or 2008 |
| Sun Solaris: 9, 10 | SUN Studio 11, 12 or GCC 3.4.6 |
| IBM AIX 5L: 5.3 | IBM XL C/C++ 7.0 through 10 or GCC 3.3.2 |
| HP-UX PA-RISC: 11i | HP aC++ A.03.55 or GCC 4.1.2 |
| HP-UX Itanium: 11i | HP aC++ A.05.55, A.06, or GCC 3.4.4 |
| SuSE 10 (Intel) | GCC 4.1.0 |
| RedHat Linux 4, 5 AS (Intel) | GCC 4.1.2 |
| Suse 9 on zSeries S390 31bit | GCC 3.3.3 |
| IBM z/OS and z/OS.e | CCNDRVR |
Note:
For information on z/OS requirements for CA Aion BRE, see the Mainframe Installation Guide.
The following web application servers are supported by CA Aion BRE:
The software is delivered electronically as an iso file. An iso file is a CD image. The iso file contains the non-mainframe software installation. The file can be burnt to a CD or a third party tool such as IOBuster can be used to read the file as if it were a CD.
After a successful installation AionBRE, the system variable PATH has been updated with required AionBRE paths, but it has not yet been activated. To activate updated System Variables you must reboot or relogin to Windows.
If you are installing from a network drive, the drive must be mapped to a letter instead of using the \\ designation to access the drive. Users should not launch the CA Aion installer from a mapped drive on Microsoft Windows 2003. It is recommended to copy the build locally.
To install CA Aion BRE on Microsoft Windows Vista or Microsoft Windows 2008, you must log onto Microsoft Windows as a user with administrator privileges. On Linux/UNIX, you must log on as a user with root privileges if installing into system directory that is,. /opt/CA
After a Linux or UNIX installation, several environment variables must be set before running CA Aion BRE r11 for UNIX/Linux. The CA Aion r11 installer places Bourne (aion.sh) and C-Shell (aion.cshrc) setup files in the installation directory. These files contain the default system settings necessary to run CA Aion BRE r11 for UNIX/Linux. After installation, these files should be reviewed. It is necessary to run one of these files (depending on the shell that is being used) prior to running CA Aion BRE r11 for UNIX/Linux.
To run the Aion Builder, the $JAVA_HOME environment variable must be set in either aion.chsrc or aion.sh to point to the directory in which Java is installed.
Installation procedures for this release of CA Aion are in the Mainframe Installation Guide.
CA Aion BRE r11 and CA Aion BRE 10.2 can co-exist as long as each is installed in separate libraries and only the r11 libraries are used for execution. R10.2 applications can be used in a MAES environment, by concatenating the CA Aion BRE 10.2 libraries to the MAES STEPLIB and MAESHPO files. Otherwise, it is important to never mix pre-r11 and r11 items.
The Volume Serial number for the mainframe tape is EF9B00.
The PAX file name is EF9B00.pax.Z
CA Aion BRE r11 for z/OS has been placed under SMP/E control. The EF9B00.pax.Z file is formatted as an enhanced ESD pax file image. Its RELFILEs, SMPMCS and SAMPJCL can be transferred directly to disk datasets via GIMUNZIP. There is no need to reconstitute a tape image. The EF9B00.pax.Z file can also be directly used as input to MSM (Mainframe Software Manager), CA's highly automated mainframe software installation and maintenance tool. The EF9B00.pax.Z file can be obtained from CA Support Online, via CA MSM's Product Acquisition Service
The Microsoft Windows environment is the principal development environment for CA Aion BRE r11. Development of CA Aion BRE applications should take place on the Microsoft Windows platform using the CA Aion BRE Integrated Development Environment (IDE). The Microsoft Windows-based IDE provides remote deployment facilities to other platforms, for example, UNIX and the mainframe (zSeries platforms).
If you have r10.2 and r11 installed simultaneously on one PC it is necessary to start each application from this folder where it was installed.
Note: All existing CA Aion applications must be restored and rebuilt within CA Aion BRE r11 to be used.
CA Aion BRE r11 for UNIX and Linux environments offers the same operating functionality as CA Aion BRE r11 for Microsoft Windows, except for those features that are unique to the Microsoft Windows platforms (for example, support for the Aion IDE, COM, .NET, and the Dynamic Rule Manager).
CA Aion 10.2, 9.5 applications that have been developed for UNIX/Linux must be converted to CA Aion BRE r11 in the Microsoft Windows environment before being compiled using CA Aion BRE r11 for UNIX/Linux.
Aion applications built for UNIX environments are generally upwardly compatible, that is, applications built on a lower version of the operating system can generally run successfully on a higher version, but not the reverse.
Note: Most CA Aion r10.2 Linux and UNIX applications can be successfully compiled by CA Aion BRE r11 for Linux and UNIX without modification. However, if any difficulties are encountered, it is recommended that the application be restored using the primary development environment, CA Aion BRE r11E for Microsoft Windows, where the problem can be investigated using a more intuitive graphical facility IDE capabilities.
The Aion Debugger is not supported on UNIX/Linux platforms.
Sybase is not supported on Linux zSeries S390
CA Aion BRE r11 for the mainframe offers the same basic functionality as CA Aion BRE r10.2, r11 for Microsoft Windows, except for those features that are unique to the Microsoft Windows platforms (for example, support for the Aion IDE, support for COM, and the Dynamic Rule Manager).
CA Aion 10.2 applications that have been developed for the mainframe should be converted to CA Aion BRE r11 in the Microsoft Windows environment before being compiled under CA Aion BRE r11 for the mainframe.
Most CA Aion r10.2 mainframe applications can be successfully compiled by CA Aion BRE r11 without modification. However, if any difficulties are encountered, it is recommended that the application be restored using the primary development environment, CA Aion BRE r11 for Microsoft Windows, where the problem can be investigated using a more intuitive graphical facility IDE capabilities.
If you want to run Ant scripts that deploy a CA Aion application as a web service, you must first run the Web Service Wizard in the IDE. The wizard prompts for the values to AXIS_HOME and ANT_HOME. Setting these values enables the Ant scripts to deploy CA Aion applications as web services.
Apache Ant 1.7.0 or is recommended. Apache AXIS 1.4 is recommended.
Java Development Kit (JDK) version 1.5 is recommended for CA Aion BRE r11.
Building the examples for the Java Interface layer requires Apache Ant 1.7. Ant 1.7 is freely downloadable from http://www.apache.org
Depending on the facilities used in a Java application to call a CA Aion server, there may be additional environmental requirements. For example, using servlet technology to support servers in a web environment requires a J2EE compatible environment.
The Dynamic Rule Repository requires a source code control program that conforms to the Microsoft Source Code Control Interface. CA's Harvest and Microsoft's Visual SourceSafe complies with this API.
For more information about installing a particular source control program, see the documentation provided by the program's supplier.
To use a source code control program with CA Aion BRE on Microsoft Windows, the Source Code Control (SCC) Interface must be installed locally. Some programs (for example, PVCS) have separated the SCC Interface installation from the main program installation. CA Harvest Change Manager and Microsoft Visual SourceSafe install the SCC Interface as part of the main program installation.
CA Harvest Change Manager VCI Integration feature must be selected during its installation.
The following installation notes explain specific environmental requirements for UNIX/Linux installations of CA Aion BRE r11.
For a 64-bit version of Oracle, you must use ORACLE_HOME/lib32.
For Oracle 11g on Solaris and Linux:
cd $AION_Home/lib ln –s $ORACLE_HOME/lib/libclntsh.so.11.1 libclntsh.so.10.1
For Oracle 11g on HP-UX (PA-RISC):
cd $AION_HOME/lib ln –s $ORACLE_HOME/lib/libclntsh.sl.11.1 libclntsh.sl.10.1
For Oracle 11g on HP-UX (IA64 Itanium):
cd $AION_HOME/lib ln –s $ORACLE_HOME/lib/libclntsh.so.11.1 libclntsh.so.10.1
Note: If you are using a 64-bit version of Oracle, you must use ORACLE_HOME/lib32.
Note: Sybase 12.5 on Solaris uses a versioned name for the libtli library. Instead of being named libtli.so, the library is named libtli.so.12.5.0. To access the 12.5 library with CA Aion, you must create a symbolic link to this version of the library. You can create the symbolic link in $AION_HOME/lib or in the Sybase 12.5 directory OCS-12_5/lib.
cd $AION_HOME/lib (or cd <Sybase 12.5 installation directory>/OCS-12_5/lib)
ln –s <Sybase 12.5 installation directory>/OCS-12_5/lib/libtli.so.12.5.0 libtli.so
Before running the Aion application, define the SYBASE environment variable and system library path, such as:
setenv SYBASE <Sybase 12.5 installation directory>\ setenv LD_LIBRARY_PATH $SYBASE/OCS-12_5/lib:$LD_LIBRARY_PATH
Make sure that the database /sqllib/lib directory is included in the LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH environment variable.
Make sure that the IBM WebSphere MQ /lib directory is included in the LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH environment variable.
Servlet containers and Web server environments require that the directories $AION_HOME/lib and $AION_HOME/userlibs are included in the LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH environment variable (as appropriate for your environment).
Make sure that the libz and libxml2 library files are installed on currently UNIX/Linux machine.
This section describes how to establish MAES Secure Socket Layer (SSL) communication capabilities.
Use IBM's gskkyman program to define an SSL keyring HFS path name that contains a self-signed certificate. This process is documented in Chapter 9 of IBM's publication (SC24-5901): z/OSCryptographic Services System Secure Sockets Layer Programming.
PATH=$PATH:/usr/lpp/gskssl/bin export NLSPATH=$NLSPATH:/usr/lpp/gskssl/lib/nls/msg/%L/%N export NLSPATH=/usr/lpp/gskssl/lib/nls/msg/En_US.IBM-1047/%N:$NLSPATH export STEPLIB=$STEPLIB:SYS1.SIEALNKE su gskkyman
Note: The common name could be same as label.
1 - <certificate-label> from above
10 - Create a signed certificate and key
6 - User or server certificate with 2048-bit RSA key
below: <maes_ssl_certificate_name>
7 - Export certificate and key to a file
3 - Binary PKCS #12 Version 3
<exported_maes_ssl_certificate_name>
Use standard FTP capabilities to transfer the exported MAES SSL certificate to the Java environment that will be communicating with MAES.
Make sure the "binary" FTP option is used.
First you need to use the standard Java "keytool" program to prepare a keystore.
keytool -genkey -alias aionbre_keystore -keyalg RSA -keystore keystore.jks
The PKCS #12 certificate can be imported into a Java key store, but the traditional "keytool" can't be used. You need to obtain the pkcs12import program from Sun. It is part of the jwsdwp 2.0 package. Then use the pkcs12import.bat utility to import the PKCS#12 certificate into the Java keystore.
Set session.properties to locate the Java keystore.
Make the keystore available on the classpath.
The MAESSSLX REXX program prepares MAES SSL configuration information. The MAESSSLX program is in the <aionhlq>.CLIST library. This library needs to be allocated to the SYSEXEC DD before ISPF/PDF is activated.
The program uses panels that are in <aionhlq>.ISPPLIB and JCL skeletons that are in <aionhlq>.ISPTLIB. These libraries need to be concatenated to the ISPPLIB and ISPSLIB DD's before ISPF/PDF is activated.
MAESSSLX prepares JCL for submission. The jobcard must be established before the program is executed. The jobcard is defined using the standard ISPF/PDF technique. It is specified in the Log/List options of the ISPF Settings panel.
To set up the jobcard
+--------------------------------------------------------------------------+ | Log/List Function keys Colors Environ Workstation Identifier Help | | | | ISPF Settings | |Command ===> | | | |Options Print Graphics | | Enter "/" to select option Family printer type 2 | | Command line at bottom Device name . . . . | | / Panel display CUA mode Aspect ratio . . . 0 | | . | | . etc. | | . | +--------------------------------------------------------------------------+
Log/List Function keys Colors Environ +----------------------------------+ | 1. Log Data set defaults | | 2. List Data set defaults | | 3. List Data set characteristics | | 4. JCL... | +----------------------------------+
+----------------------------------------------------------------+ | Log and List JCL | | | |Job statement information: (Required for system printer) | |//<jobcard_line_1> | |//<jobcard_line_2, or spaces> | |//<jobcard_line_3, or spaces> | |//<jobcard_line_4, or spaces> | | | | F1=Help F2=Split F3=Exit F9=Swap F12=Cancel | +----------------------------------------------------------------+
tso %MAESSSLX
+----------------------------------------------------------------------------+ |CA Aion BRE ------------- MAES SSL Configuration ------------- CA Aion BRE| |COMMAND ===> | | | |Press Enter when complete, or END command to cancel | | | | Enter high-level qualifier(s) of Aion BRE load library: | | Aion load library qualifier ===> <aionhlq> | | | | Enter SSL keyring HFS path name below: | | HFS Path ===> <ssl_hfs_path> | | | | Enter SSL keyring password below: | | Password ===> | | | | Verify SSL keyring password below: | | Password ===> | | | | Enter SSL certificate label below: | | Label ===> <maes_ssl_certificate_name> | | Copyright(C) CA, Inc. 2009. All Rights Reserved | | | | F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE| | F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEV| +----------------------------------------------------------------------------+
The generated JCL is displayed.
+----------------------------------------------------------------------------+ | File Edit Edit_Settings Menu Utilities Compilers Test Help | | | |EDIT WATKE08.CA11.SPFTEMP1.CNTL Columns 00001 000| |Command ===> Scroll ===> CS| |****** ***************************** Top of Data ***************************| |==MSG> -Warning- The UNDO command is not available until you change | |==MSG> your edit profile using the command RECOVERY ON. | |000001 //<jobcard lines> | |000003 //* | |000004 //* SUBMIT this job. | |000005 //* | |000006 //* JCL prepared at 3:10pm on Tuesday, 24 Nov 2009 | |000007 //* | |000008 //* This job was generated by CA Aion BRE -- MAESSSLX | |000009 //* | |000010 //* ------------------------------------------- | |000011 //* | |000012 //* CA Aion Business Rules Expert | |000013 //* | |000014 //* Copyright (c) 2009 CA. All rights reserved. | |000015 //* | |000016 //* This software and all information contained | |000017 //* therein is confidential and proprietary and | |000018 //* shall not be duplicated, used, disclosed or | |000019 //* disseminated in any way without the express | |000020 //* written permission of CA. All authorized | |000021 //* reproductions must be marked with this language. | +----------------------------------------------------------------------------+
The submitted job should conclude with a completion code of 0. Afterwards the <aionhlq>.MAES.LOAD library will contain the MAESSSLD member.
If a new certificate is created, or the password of the SSL keyring changes, then you will need to redefine the MAESSSLD member by rerunning the MAESSSLX program.
The Java client that uses SSL to communicate with MAES is programmed as follows:
private SSLContext sslContext;
private SSLSocketFactory sslSocketFactory;
private Socket socket;
private InputStream stream_in;
private OutputStream stream_out;
private ByteArrayOutputStream bout = new ByteArrayOutputStream();
private DataInputStream data_stream_in = null;
System.setProperty("javax.net.ssl.trustStore","");
System.setProperty("javax.net.ssl.trustStorePassword","");
System.setProperty("javax.net.ssl.keyStore","");
System.setProperty("javax.net.ssl.keyStorePassword","");
System.setProperty("javax.net.debug","SSL");
System.out.println( "Providers:");
Provider aProvider[] = Security.getProviders();
int nProviders = aProvider.length;
for( int nProvider=0; nProvider < nProviders; nProvider++ )
{
System.out.println( " " + aProvider[nProvider].getName() );
}
// Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
/*
* Set up a key manager for client authentication
* if asked by the server. Use the implementation's
* default TrustStore and secureRandom routines.
*/
KeyManagerFactory kmf;
KeyStore ks;
char[] passphrase = "".toCharArray();
sslContext = SSLContext.getInstance("TLSv1");
kmf = KeyManagerFactory.getInstance("SunX509");
ks = KeyStore.getInstance("JKS");
ks.load(new FileInputStream(""), passphrase);
kmf.init(ks, passphrase);
sslContext.init(kmf.getKeyManagers(), null, null);
sslSocketFactory = sslContext.getSocketFactory();
if( bIPv6Version )
{
// note: IPv6 must be installed and enabled on the system !!!
host_name = "";
InetAddress inet_addr = InetAddress.getByName( host_name );
byte[] inetAddrBytes = inet_addr.getAddress();
if(debug)
{
System.out.println(
"MAESRPC: host name address" + host_name
+ " #" + Integer.toString( inetAddrBytes.length ) + " bytes" );
printHex( inetAddrBytes, inetAddrBytes.length );
}
InetAddress inet_addr6 = InetAddress.getByAddress( host_name, inetAddrBytes );
socket = (Socket) sslSocketFactory.createSocket( inet_addr6, port_number);
}
else
socket = (Socket) sslSocketFactory.createSocket(host_name, port_number);
On Windows Vista, 2008 and 7, CA Aion BRE must run with the privilege level of administrator. To run CA Aion or any of its components on Vista as an administrator you can right mouse click on the menu shortcut and select Run as administrator. You can also set the privilege level permanently, by using the right mouse click on the menu short cut, select Properties, Compatibility tab, and check Run this program as an administrator checkbox. The instructions for Windows 2008 and Windows 7 are similar. For more information, refer to the Microsoft documentation.
When MAES is terminated, some diagnostic information that is buffered is not written to the DIVLOG dataset. It can cause difficulties resolving problems associated with the absent diagnostic information. In the MAES startup JCL, the following file can be provided for additional MAES diagnostic logging. There will be performance overhead when output is written to the MLOGOUT file. This should only be added in special circumstances, when insufficient information is recorded in DIVLOG output. A workaround is to perform a few additional MAES application requests before stopping MAES. //MLOGOUT DD SYSOUT=<sysout_dest>
CA Aion BRE uses multi-row fetch by default within static SQL queries. If your environment is not DB2 v8 New Function Mode (NFM), or DB2 v9, then multi-row fetch cannot be used for Static SQL requests. An SQL error -4700 will occur if a multi-row fetch is performed in an environment that does not support this capability.
To disable the use of multi-row fetch with Static SQL, in the BABUILD step SYSIN file specify the following new parameter:
DB2-STATIC-MULTIROW-FETCH=NO
This causes the generated Static SQL code to perform single row fetch activities instead.
If the value of the DB2-STATIC-MULTIROW-FETCH parameter is any other value, or unspecified, then static SQL multi-row fetch capabilities will be generated.
Note: You may execute your Static SQL applications on different machines. In this case, you may need to build one version of the application with static SQL multi-row fetch disabled, and another with it enabled. If so, you should devise a method for differentiating these versions.
Previously, the size of an Aion binary value that statically resides in a COBOL or PL/1 program was unknown if the value is initialized by the xb_Open function and then passed as an input parameter to an Aion application method. Prior to r11.0 a crash occurred if Aion logic referenced beyond the extent of the binary value. This was corrected by ensuring that references to the binary value are confined to the value's extent. Now when binary values that are created the size of the value is established, with the exception of the xb_Open calls in COBOL or PL/1 programs. In these programs an additional call is required to a new xb_SetDataBufferSize function. Programs that use the xb_Open function, but do not use the xb_SetDataBufferSize function will encur various execution problems.
The following shows how the new xb_SetDataBufferSize function is used in a COBOL program.
* USE THE xb_Open FUNCTION TO LET AION KNOW WHERE THE * BINARY BUFFER IS. CALL 'xb_Open' USING BY VALUE XB-OPEN-READ BY VALUE ADDRESS OF L0588-DECISION-REQUEST RETURNING BINARYIN-IN OF SENDL0588-METHOD END-CALL * NOTICE THAT THE xb_SetDataBufferSize FUNCTION MUST BE * CALLED AFTER THE xb_Open REQUEST. CALL 'xb_SetDataBufferSize' USING BY VALUE BINARYIN-IN OF SENDL0588-METHOD BY VALUE LENGTH OF L0588-DECISION-REQUEST
The uninstallation process only removes directories and files that were installed by the Aion BRE installer. Directories and files that were prepared after installation, such as user applications, will not be automatically removed. When you uninstall the product, please make sure to remove any residual files that remain. In particular, the directory named userlibs must be removed before a new install can be performed with the same installation path.
Problem:
The aionbre_install.log log file does not get created if the install is run remotely.
Circumvention:
Run the install locally.
Problem:
The build process will not work if Aion is installed into a directory that contains special characters in its name.
Circumvention:
When Aion BRE is installed in a directory that contains special characters like Program Files (x86), a virtual drive should be created for the BRE installation path in order to run the examples from the installation path.
For Example assume that Aion BRE is installed in "C:\Program Files (x86)\CA\AionBRE". Define a virtual drive for that BRE installation path using command prompt as follows
subst X: "C:\Program Files (x86)\CA\AionBRE"
Start REDEV from the command Prompt and reference the virtual directory X: instead of the paths that contains the special character.
After following the above process, examples can be run without any problem. The virtual drive must be re-created whenever the computer is re-booted.
Problem:
On HP UX, the Uninstall process may not remove the Uninstall_AionBRE and examples directories.
Circumvention:
Manually delete the directories after the Uninstall is complete.
Problem:
In the translated PDF Tables of Contents, the CA Aion BRE Release Notes is still labeled Business Rules Expert (BRE) Release Summary.
Circumvention:
None
Problem:
The unicode version of Aion BRE on the Windows platforms is not working properly. Various abends can occur.
Circumvention:
Install the non-unicode version of Aion BRE on a Windows platform. The non-unicode version is the default.
Problem:
If MAES is supporting SSL communications with little SSL activity a WTOR termination request may not be effective. This is because the SSL server task is waiting for a client request, and can't respond to the shutdown request. The shutdown will proceed if a remote client request arrives.
Circumvention:
You need to cancel MAES to proceed with shutdown.
Problem:
Health Checks are not currently implemented for SSL capabilities.
Circumvention:
None.
Problem:
The compile option "-qmaxmem" is set to 16000KB. If the amount of memory required, exceeds this amount during code optimization, the following message will be displayed "1500-030: (I) INFORMATION: Mxxx: Additional optimization may be attained by recompiling and specifying MAXMEM option with a value greater than 16000"
Circumvention:
To remove the memory limitation on the compiler set "-qmaxmem=-1" in the file $AION_HOME/build/unxmkenv.bat
Problem:
Static SQL for DB2 on the Windows platform is not working as documented in the BRE product guide in section Dynamic versus Static SQL
Circumvention:
Use Dynamic SQL.
Problem:
MAES Health Checker capabilities are based on the CA Health Checker Common Service. The CA Health Checker Common Service will be integrated in CA Common Services in the future. However, it is currently an optional feature of CA Common Services. If the CA Health Checker Common Service is absent, then MAES Health Checker capabilities will be unavailable.
Circumvention:
The CA Health Checker Common Service needs to be separately obtained from CA.
Phase I of CA Health Checker Common Service r12.0 is being delivered as an optional feature for CCS r11.
The common services feature must be installed before individual product checks will activate.
Problem:
In section 6 of this README, information is provided regarding additional information that is now available in the new MAES MLOGOUT DD statement. If used, the last statement written to this file should indicate 'SHUTDOWN Compete'. However, the 'SHUTDOWN complete' message may not always appear at the end of the MLOGOUT DD's output.
Circumvention:
None.
Problem:
Attempts to execute the CEEUOPT JCL as provided will result in a cc of 12 in the LINK step with messages: IEW2303E 1030 MEMBER OAES OF THE DATA SET SPECIFIED BY LOADIN COULD NOT BE FOUND.
Circumvention:
Update the parameters on the LINK step to include a CASE=MIXED parameter and change reference to the INCLUDE LOADIN in the SYSLIN from OAES to OAESB0. The entire corrections are as follows:
The PARM statement will be:
PARM='DYNAM=DLL,CASE=MIXED,XREF,LIST,MAP,AMODE=31,RMODE=ANY,RENT' SYSLIN DD * INCLUDE LOADIN(OAESB0)
Problem:
The BIND step of the <aionhlq>.SAMPLES.BATCHBLD(DATSTAT) or (DATSTATX) using DB2 R8 in Compatibility mode results in receipt of a cc of 8 with -180 when DB2-STATIC-MULTIROW-FETCH=NO is specified in the BABUILD steps.
Circumvention:
Edit the <userhlq>.DATATEST.APP file and issue a find on 'DB2_STATIC_TEST.ITIME' then find the string statement that proceeds it and modify the statement from 'string' to 'string(8)'. An example of the statements before and after the change are provided for your review.
Save the <userhlq>.DATATEST.APP file.
Rerun the respective job either DATSTAT or DATSTATX. The Bind step will now end with a cc of 0.
Example Before Change:
000755 #Attribute 000756 ITIME QueryDB2_Static 000757 #Type 000758 string 000759 #Initial Value 000760 NULL 000761 #Field 000762 True 000763 #Alias 000764 DB2_STATIC_TEST.ITIME
Example After change:
000755 #Attribute 000756 ITIME QueryDB2_Static 000757 #Type 000758 string(8) 000759 #Initial Value 000760 NULL 000761 #Field 000762 True 000763 #Alias 000764 DB2_STATIC_TEST.ITIME
The complete list of published bug fixes since the GA version of CA Aion Business Rules Expert, and any updated documentation, including updates to this readme can be found through Published Solutions on Support Online at http://ca.com/support.The following Solution have been published and should be applied to the product after the GAl installation:
| PTF number | Problem number | Platform | Description |
|---|---|---|---|
| RO16979 | AIONBR 799 | z/OS | DO NOT ADD BACKSLASH WHEN TRUNCATING STATIC SQL |
A translated product (sometimes referred to as a localized product) is an internationalized product that includes local language support for the product's user interface, online help and other documentation, as well as local language default settings for date, time, currency, and number formats.
The CA Aion BRE product is not localized.
Each PDF guide in a documentation set has a unique Document ID (DID) that appears on the title page of the guide. The DID uses the first six characters to identify the guide, a hyphen, then two characters at the end to identify the edition and language in which it is written. For example, L00088-1E identifies the first edition of the English version of a user guide. When the second edition of this guide is published, the DID will be incremented to L00088-2E. The DID is used without the hyphen for the .PDF file on the product media and on SupportConnect as shown in File Name column of the following table.
The DIDs and file names for this product's guides are:
| Guide Name | DID | File Name |
|---|---|---|
| CA Aion BRE Product Guide | L001131E | CA_Aion_BRE_Product_ENU.pdf |
| CA Aion BRE Mainframe User Guide | L001181E | CA_Aion_BRE_Mainframe_User_ENU.pdf |
| CA Aion BRE Mainframe Installation Guide | L001141E | CA_Aion_BRE_Mainframe_Install_ENU.pdf |
| CA Aion BRE Rules Guide | L001151E | CA_Aion_BRE_Rules_ENU.pdf |
| CA Aion BRE Developers Overview | L001171E | CA_Aion_BRE_Developers_Overview_ENU.pdf |
| CA Aion BRE Release Notes | L001161E | CA_Aion_BRE_Release_ENU.pdf |
| CA Aion BRE Best Practices Guide | L002301E | CA_Aion_BRE_BestPractices_ENU.pdf |
The DID for this readme file appears under the readme title; the same DID without the hyphen is used for the readme file name on SupportConnect.
The release number on the title page of a document might not correspond to the current product release number; however, all documentation delivered with the product, regardless of release number on the title page, does support your use of the current product release. The release number changes only when a significant portion of a document changes to support a new or updated product release. If no substantive changes are made to a document, the release number does not change. For example, a document for r2.4 can still be valid for r2.4 SP3 or even r3. Documentation bookshelves always reflect the current product release number.
Occasionally, we must update documentation outside of a new or updated release. To indicate a minor change to the documentation that does not invalidate it for any releases that it supports, we update the edition number on the cover page. First editions do not have an edition number.
Updated guides will be available at http://ca.com/support.
Contact Technical Support
For your convenience, CA provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA products. At http://ca.com/support, you can access the following:
Provide Feedback
If you have comments or questions about CA product documentation, you can send a message to techpubs@ca.com.
If you would like to provide feedback about CA product documentation, complete our short customer survey, which is also available on the CA Support website, found at http://ca.com/docs.