| RPC Protocol(1) | Feature(2) | EntireX | EntireX Adapter for Integration Server | PI Adapter for EntireX | Natural | More Information | ||
|---|---|---|---|---|---|---|---|---|
| Mainframe | ONE | Open Systems | ||||||
| 2000 | IDL unbounded arrays | 5.4 | 7.1 | 4.1.0 | 4.1.3 | 8.1 | 6.1.1 PL13 | Unbounded arrays are arrays with variable upper bounds, see array-definition under Software AG IDL Grammar in the IDL Editor documentation.
For the programming language COBOL they can be defined with an upper maximum and mapped to COBOL data items with the DEPENDING ON clause.
See COBOL Tables with Variable Size - DEPENDING ON Clause.If a server is wrapped with the COBOL Wrapper or extracted with the IDL Extractor for COBOL a server mapping file (3) is automatically created for IDL unbounded arrays. |
| IDL types PU, NU | 5.4 | 7.1 | 4.1.0 | 4.1.3 | 8.1 | 6.1.1 PL13 | The data types packed and unpacked decimal unsigned support the programming languages COBOL and PL/I. See IDL Data Types in the IDL Editor documentation. | |
| IDL structs | 5.4 | 7.1 | 4.1.0 | 4.1.3 | 8.1 | 6.1.1 PL13 | An IDL struct describes a user-defined type for reusability. For RPC server with a CICS channel
container interface, it describes the layout of container. See structure-definition under Software AG IDL Grammar in the IDL Editor documentation.
|
|
| IDL aligned attribute | 5.4 | 7.1 | 4.1.0 | n/a | n/a | n/a | The aligned attribute is relevant for the programming languages COBOL and PL/I and the server side.
For other languages it is not relevant. See attribute-list under Software AG IDL Grammar in the IDL Editor documentation.
|
|
| IDL parameters with more than 3 indices (all indices up to the parent on level 1 counted) | 5.4 | 7.1 | 4.1.0 | n/a | n/a | n/a | See array-definition under Software AG IDL Grammar in the IDL Editor documentation.
|
|
| IDL library or IDL program longer than 8 characters for COBOL | 5.4 | 7.1 | 4.1.0 | 4.2.6 | 8.1 | 6.3.7 | If a server is wrapped with COBOL Wrapper or extracted with IDL Extractor for COBOL with a long IDL program name (longer than 8 characters) or extracted with the or extracted with IDL Extractor for COBOL and renamed to a different IDL program name, a server mapping file (3) is created automatically. | |
| Reliable RPC | 8.0 | 7.2 | 4.1.1 | 4.2.5 | 8.1 | 6.3.6 | Reliable RPC. | |
| CICS Channel Container | 8.2.2 | 7.1 | 4.1.0 | n/a | n/a | n/a | If a COBOL server with interface type CICS with Channel Container Calling Convention is wrapped with the COBOL Wrapper or extracted with the IDL Extractor for COBOL, a server mapping file 3 is automatically created. | |
| Mixed case RPC passwords | 8.2.2 | 8.2.2 | no | 4.1.4 | 8.1 | 6.1.1 PL21 | Allow RPC passwords with lowercase characters. See Natural Security under Common Features of Wrappers and RPC-based Components in the RPC Programming documentation. | |
| 2010 | Natural optional parameters | n/a | n/a | n/a | 4.1.3 | 8.1 | 6.1.1 PL13 | Optional parameters are a special Natural feature. See Natural documentation. |
| 2020 | IDL types U, UV | 7.3 | 7.1 | 4.1.1 | 4.2.1 | 8.1 | 6.2.1 | The Unicode data types support all programming languages with separate Unicode and character types such as COBOL, Natural and C. See IDL Data Types in the IDL Editor documentation. |
| Up to 99 IDL Levels | 7.3 | 7.1 | 4.1.1 | 4.2.1 | 8.1 | 6.2.1 | IDL levels are used in conjunction with parameter grouping. Parameters are either scalar or a member of the immediately preceding
group that has been assigned a lower level number. See simple-parameter-definition under Software AG IDL Grammar in the IDL Editor documentation.
|
|
| 2030 | Natural Redefine, IDL program name longer than 8 characters for Natural, server mapping file for Natural (Designer file with extension .cvm), and other features | 8.2 | 8.2 | 4.1.2 | 4.2.7 and 8.2.2 | 8.2.4 | 6.3.9 | REDEFINEs are supported by IDL Extractor for Natural on the server side and force a server mapping file (4) to be created. See When is a Server Mapping File Required? in the Designer documentation for full list of features.
|
| Server mapping file (Designer file with extension .cvm) for COBOL | 9.7 | 9.7 | 4.1.2 | n/a | n/a | n/a | If a server is wrapped with the COBOL Wrapper or extracted with the IDL Extractor for COBOL, a server mapping file (3) is automatically created if one is required. See When is a Server Mapping File Required? under Server Mapping Files for COBOL in the Designer documentation. |
|
| 2040 | Increased precision for IDL types N, NU, P, PU | 9.7 | 9.7 | no | 8.2.2 | 8.4.1 | 8.4.1 | If more than 7 digits after the decimal point or more than 29 digits in total (before and after the decimal point) are used.
For EntireX, the maximum number of supported digits depends on language and operating system. See notes for data types N, NU, P and PU in document Mapping IDL Data Types to target language environment C | COBOL | DCOM | .NET | Java | Natural | PL/I | XML. |
| 2050 | Long RPC user ID and RPC password | 10.3 | 10.3 | no | 9.1.1 | 9.1.1 | 9.1.1 |
The RPC user ID/password pair is designed to be used by the receiving RPC server. This component's configuration determines whether the pair is considered or not. Useful scenarios are:
There is no limitation on the length of the RPC user ID and RPC password sent by an RPC client. A length restriction may come into account by the receiving RPC server when the RPC server validates the credentials from the calling RPC client against a security system. |
| n/a | = not applicable |
| no | = not supported |
Notes:
Server mapping files with extension .svm are no longer supported at design time by the Designer.
You can still use them at runtime in a server-side mapping container.
All special COBOL syntax and features supported by server mapping files with extension .svm are also covered by server mapping
files with extension .cvm.
See When is a Server Mapping File Required?
We recommend migrating .svm files to .cvm files. See Migrating Server Mapping Files under Server Mapping Files for COBOL in the Designer documentation.