5770-WDS IBM Rational Development Studio for i V7.4

IBM Europe Sales Manual
Revised:  September 10, 2019.

 
Table of contents
TOC Link Product life cycle dates TOC Link Description
TOC Link Program number TOC Link Operating environment
TOC Link Abstract TOC Link Planning Information
TOC Link Highlights TOC Link Security, Auditability, and Control

 

Product life cycle dates

Program NumberVRM Announced Available Marketing Withdrawn Service Discontinued
5770-WDS07.04.002019/04/232019/06/21 - -
5770-WDS07.02.002014/04/282014/05/02 2020/04/302021/04/30
5770-WDS07.01.002010/04/132010/04/23 2017/09/302018/04/30

Back to topBack to top

Program number

  • IBM Rational Development Studio for i V7.4.0 (5770-WDS)

Back to topBack to top

Abstract

IBM Rational Development Studio for i 7.2 delivers significant enhancements to the IBM i Integrated Language Environment (ILE) compilers.



Back to topBack to top

Highlights

Key 7.1 Enhancements

ILE RPG

  • Sort and search data structure arrays
  • Support for ALIAS names
  • Built-in functions
  • Prototypes are now optional
  • Performance improvement for returning large values
  • Options for XML-INTO
  • Implicit parameter conversion between alphanumeric, UCS-2 and Graphic
  • The listing debug view can be encrypted
  • Support for the teraspace storage model
  • Support for Open Access: RPG Edition

ILE COBOL

  • Support for true integers and unsigned integers
  • Improved performance for XML GENERATE
  • OPTIMIZE(*NEVER) supports compiling very large programs
  • Greater ease in specifying the VALUE clause for a national data item
  • The listing debug view can be encrypted
  • Support for the teraspace storage model
  • PROCESS statement options

ILE C

  • Support for encryption of debug data

ILE C++

  • Decimal floating-point support
  • Support for C99 features
  • Support for encryption of debug data

Application Development ToolSet (ADTS)

  • An exit point to allow customers to monitor or disable changing source files using Source entry utility (SEU), Screen design aid (SDA), and Report Layout Utility (RLU)
  • Features introduced to ILE RPG and ILE COBOL following the 6.1 release are not recognized by the syntax-checkers used by SEU

Key 7.2 Enhancements

ILE RPG

  • Support for free-form Control, File, Definition, and Procedure statements
  • Several enhancements related to Coded Character Set Identifiers (CCSIDs)
  • Increased precision for timestamp data
  • Ability to control the length of the value returned by %SUBDT
  • XML-INTO options to support XML namespaces
  • An optimization option to improve the performance of date, time, and timestamp operations by skipping the validation step
  • Program Call Markup Language (PCML) support for date, time, timestamp, and 8-byte unsigned integers

ILE COBOL

  • Increased precision for timestamp data
  • XML PARSE support for XML files greater than 16MB in size
  • Improved support for PCML generation of OCCURS DEPENDING ON items and filler items
  • Several enhancements for National data (Unicode)
  • Options to help improve the accuracy of some numeric operations
  • PROCESS options NOCHGFLTRND and ALWCHGFLTRND to specify how COBOL will use the floating-point rounding mode specified by the SETCA machine interface (MI) instruction

The Heritage compilers are stabilized as of V5R4. It is recommended that their use be discontinued and ILE compilers be adopted.

ADTS is stabilized as of Version 6.1. In particular, ADTS does not support the language capabilities that were introduced in the ILE Compilers as of Version 6.1. It is recommended that use of ADTS be discontinued and that Rational Developer for i, a modern graphical Integrated Development Environment (IDE), be adopted.



Back to topBack to top

Description

ILE RPG 7.1 Enhancements

  • Sort and search data structure arrays: To sort or search a data structure array, one subfield is identified as the "key" for the array, using the syntax ARRAY(*).KEYSUBFIELD. The following examples sort the INFO array by the SALARY subfield and search for the name 'Jack' in the NAME subfield of the INFO array.
            SORTA INFO(*).SALARY;
            i = %LOOKUP('Jack' : INFO(*).NAME);
    
  • Support for ALIAS names
    • The ALIAS keyword can be specified on the File specification for an externally described file that will not have Input or Output specifications generated by the compiler. These are files specified with the QUALIFIED keyword, or files specified within subprocedures. When the LIKEREC keyword is used to define a data structure from one of the record formats of the file, the RPG subfield names will be taken from the alternate names of the fields rather than the short names.
    • The ALIAS keyword can be specified on the Definition specification for an externally described data structure. The RPG subfield names will be taken from the alternate names of the fields rather than the short names.
              A        R CUSTREC
              A        CUSTNM        25A         ALIAS(CUSTOMER_NAME)
              A        CUSTAD        25A         ALIAS(CUSTOMER_ADDRESS)
              A        ID            10P 0
       
              D custDs    e ds                   ALIAS
              D                                  QUALIFIED EXTNAME(custFile)
               /free
                custDs.customer_name = 'John Smith';
                custDs.customer_address = '123 Mockingbird Lane';
                custDs.id = 12345;
       
      
  • Updated built-in functions
      The %SCANRPL built-in function scans for all occurrences of a value
      within a string and replaces them with another value.
       // Replace NAME with 'Tom'
       string1 = 'See NAME. See NAME run. Run NAME run.';
       string2 = %ScanRpl('NAME' : 'Tom' : string1);
       // string2 = 'See Tom. See Tom run. Run Tom run.'
      The built-in function %PARMNUM can be used within a procedure to
      soft-code the number of a parameter.
            D                     pi
            D    name                       100a   const varying
            D    id                          10i 0 value
            D    errorInfo                         likeds(errs_t)
            D                                      options(*nopass)
             /free
              // Check if the "errorInfo" parameter was passed
              if %parms >= %parmnum(errorInfo);
    

    Enhanced built-in function %LEN can now be used to obtain the maximum number of characters in a varying-length alphanumeric, UCS-2 or DBCS variable.

  • Optional prototypes: If a program or procedure is not called by another RPG module, it is optional to specify the prototype. The prototype may be omitted for the following types of programs and procedures:
    • A program that is only intended to be used as an exit program or as the command-processing program for a command
    • A program that is only intended to be called from a different programming language
    • A procedure that is not exported from the module
    • A procedure that is exported from the module but only intended to be called from a different programming language
  • Performance improvement for returning large values: A procedure defined with the RTNPARM keyword handles the return value as a hidden parameter. When a procedure is prototyped to return a very large value, especially a very large varying value, the performance for calling the procedure can be significantly improved by defining the procedure with the RTNPARM keyword.
            D getFileData     pr              a   varying len(1000000)
            D                                     rtnparm
            D   file                          a   const varying len(500)
            D data            S               a   varying len(1000)
             /free
                data = getFileData ('/home/mydir/myfile.txt');
     
    
  • Options for XML-INTO
    • The datasubf option allows you to name a subfield that will receive the text data for an XML element that also has attributes.
    • The countprefix option reduces the need for you to specify the allowmissing=yes option. It specifies the prefix for the names of the additional subfields that receive the number of RPG array elements or non-array subfields set by the XML-INTO operation.

    These options are also available through PTF SI34983 for 6.1.

  • Pass any type of string parameter: Implicit conversion will be done for string parameters passed by value or by read-only reference. For example, a procedure can be prototyped to have a CONST UCS-2 parameter, and character expression can be passed as a parameter on a call to the procedure. This enables you to write a single procedure with the parameters and return value prototyped with the UCS-2 type. To call that procedure, you can pass any type of string parameter, and assign the return value to any type of string variable.
         // The makeTitle procedure upper-cases the value
         // and centers it within the provided length
         alphaTitle = makeTitle(alphaValue : 50);
         ucs2Title = makeTitle(ucs2Value : 50);
         dbcsTitle = makeTitle(dbcsValue : 50);
     
    
  • Support for encryption of debug data: A debug encryption key compiler option, DBGENCKEY, is supported in the ILE RPG compiler. This option specifies the key to be used to encrypt source code that is embedded in debug views of a module (for example, the Listing View debug view created by specifying the DBGVIEW(*LIST) compile option). An equivalent option is available on the start debug command, STRDBG, to specify the key for decryption of the encrypted debug views.
  • Support for the teraspace storage model
    • RPG modules and programs can be created to use the teraspace storage model or to inherit the storage model of their caller. With the teraspace storage model, the system limits regarding automatic storage are significantly higher than for the single-level storage model. There are limits for the amount of automatic storage for a single procedure and for the total automatic storage of all the procedures on the call stack.
    • Use the storage model (STGMDL) parameter on the CRTRPGMOD or CRTBNDRPG command, or use the STGMDL keyword on the Control specification.
      • *TERASPACE: The program or module uses the teraspace storage model.
      • *SNGLVL: The program or module uses the single-level storage model.
      • *INHERIT: The program or module inherits the storage model of its caller.
    • The default value of the ACTGRP parameter and Control specification keyword is changed from QILE to *STGMDL. ACTGRP (*STGMDL) specifies that the activation group depends on the storage model of the program. When the storage model is *TERASPACE, ACTGRP(*STGMDL) is the same as ACTGRP(QILETS). Otherwise, ACTGRP (*STGMDL) is the same as ACTGRP(QILE).
    • Ability to allocate teraspace storage. Use the ALLOC keyword on the Control specification to specify whether the RPG storage- management operations in the module will use teraspace storage or single-level storage. The maximum size of a teraspace storage allocation is significantly larger than the maximum size of a single- level storage allocation.
  • Support for Open Access: RPG Edition

Open Access is a full-featured version of the limited support provided by RPG SPECIAL files. It provides a way for RPG programmers to use the simple and well-understood RPG I/O model to access devices that are not directly supported by RPG.

When the HANDLER keyword is specified on a File specification, the RPG compiler will generate code to use the specified handling procedure for I/O operations to the file rather than generating code to call the system's data management functions.

The HANDLER keyword can be used for any RPG device, DISK, PRINTER, or WORKSTN. The provider of the handling procedure can choose the RPG device-type that best fits the function that the handler provides. For example, a user-interface application could map to a WORKSTN file, an Excel document could map to a PRINTER file, and a Web service could map to a keyed DISK file.

To obtain the runtime enablement for these capabilities, customers should order IBM Rational Open Access: RPG Edition (5733-OAR).

ILE COBOL 7.1 Enhancements

  • COMPUTATIONAL-5 (native binary) data type: COMPUTATIONAL-5 or COMP-5 is a native binary data type now supported by the USAGE clause. COMP-5 data items are represented in storage as binary data, and can contain values up to the capacity of the native binary representation (2, 4, or 8 bytes). When numeric data is moved or stored into a COMP-5 item, truncation occurs at the binary field size rather than at the COBOL picture size limit. When a COMP-5 item is referenced, the full binary field size is used in the operation. This support will enhance portability to or from COBOL on other IBM platforms and operating systems.
  • Improved performance for XML GENERATE
    • Performance improvements have been made for XML GENERATE when the APPEND option is specified. Users who have a large number of data records to be appended into a data structure or into a stream file will benefit from these changes. The improvements include the addition of PROCESS statement parameter XMLGEN with option values
      • NOKEEPFILEOPEN / KEEPFILEOPEN Specify KEEPFILEOPEN to indicate that the XML stream file is to be left open and not closed when the XML GENERATE statement is complete, so that subsequent XML GENERATE FILE-STREAM APPEND statements can quickly append data to the stream file.
      • NOASSUMEVALIDCHARS / ASSUMEVALIDCHARS Specify ASSUMEVALIDCHARS to have XML GENERATE bypass the checking for special characters (less-than, greater-than, ampersand, and the single and double-quote symbols), and for characters not supported by XML that would require being generated as hexadecimal. Otherwise normal checking will be done with the default NOASSUMEVALIDCHARS.
    • Performance is improved for cases where the same COBOL data item is repeatedly output using XML GENERATE
  • Greater ease in specifying the VALUE clause for a national data item: A non-numeric literal can be specified on the VALUE clause for a national data item.
  • 77 NATIONAL-VAR PIC N(10) USAGE NATIONAL VALUE "HELLO".
  • Compile very large programs by disabling optimization: When programs fail to compile due to reaching system limits, specifying OPTIMIZE(*NEVER)or NEVEROPTIMIZE will cause the COBOL compiler to omit generating optimization code for the program, which may allow the program to compile.
  • Support for encryption of debug data: A debug encryption key compiler option, DBGENCKEY, is supported in the ILE COBOL compiler. This option specifies the key to be used to encrypt source code that is embedded in debug views of a module (for example, the Listing View debug view created by specifying the DBGVIEW(*LIST) compile option). An equivalent option is available on the start debug command, STRDBG, to specify the key for decryption of the encrypted debug views.
  • Support for the teraspace storage model
    • COBOL modules and programs can be created to use the teraspace storage model or to inherit the storage model of their caller. With the teraspace storage model, the system limits regarding automatic storage are significantly higher that for the single-level storage model. There are limits for the amount of automatic storage for a single procedure and for the total automatic storage of all the procedures on the call stack.
    • Use the storage model (STGMDL) parameter on the CRTCBLMOD or CRTBNDCBL command, or use the STGMDL PROCESS option.
      • TERASPACE: The program or module uses the teraspace storage model.
      • SNGLVL: The program or module uses the single-level storage model.
      • INHERIT: The program or module inherits the storage model of its caller.
    • The default value of the ACTGRP command parameter is changed from QILE to *STGMDL. ACTGRP(*STGMDL) specifies that the activation group depends on the storage model of the program. When the storage model is *TERASPACE, ACTGRP(*STGMDL) is the same as ACTGRP (QILETS). Otherwise, ACTGRP(*STGMDL) is the same as ACTGRP(QILE).
  • PROCESS statement options
    • ACTGRP is now available as a PROCESS statement parameter with option values
      • STGMDL
      • NEW
      • CALLER.
    • NEVEROPTIMIZE is now available as a PROCESS statement option
    • STGMDL is now available as a PROCESS statement parameter with option values
      • INHERIT
      • SNGLVL
      • TERASPACE
    • XMLGEN is now available as a PROCESS statement parameter with option values
      • NOKEEPFILEOPEN / KEEPFILEOPEN
      • NOASSUMEVALIDCHARS / ASSUMEVALIDCHARS

ILE C 7.1 Enhancements

Support for encryption of debug data: A debug encryption key compiler option, DBGENCKEY, is supported in the ILE C compiler. This option specifies the key to be used to encrypt source code that is embedded in debug views of a module (for example, the Listing View debug view created by specifying the DBGVIEW (*LIST) compile option). An equivalent option is available on the start debug command, STRDBG, to specify the key for decryption of the encrypted debug views.

ILE C++ 7.1 Enhancements

  • Decimal floating-point support
    • Allows floating-point computations to be performed using decimal arithmetic (base 10)
    • Avoids potential rounding errors converting binary floating-point data to/from human readable formats
    • Conforms to the decimal formats and arithmetic described in the IEEE 754-2008 Standard for Floating-Point Arithmetic
    • Adds support to ILE C++ compiler, based on Draft Technical Report 24732 submitted to the ISO/IEC JTC1/SC22/WG14 Programming Language C committee
    • Data types
      • _Decimal32, 4 bytes, 7 digits precision, -95/+96 exponent
      • _Decimal64, 8 bytes, 16 digits precision, -383/+384 exponent
      • _Decimal128, 16 bytes, 34 digits precision, -6143/+6144 exponent
    • Includes decimal floating-point literals: 1.0df, 1.0dd, and 1.0dl
    • Conversions to/from C++ built-in data types, such as integers and binary floating-point types
    • Includes DECFLTRND option on C++ compiler commands (CRTCPPMOD, CRTBNDCPP)to control compile-time decimal floating-point rounding mode
  • Support for C99 features: The ILE C++ compiler has been enhanced to support many of the C99 features defined in the ISO/IEC 9899:1999 C language standard. Some of the C99 features now supported include:
    • _Pragma operator
    • __func__ predefined identifier
    • hexadecimal floating-point literals
    • variable length arrays
    • empty arguments for function-like macros
    • variable number of arguments for function-like macros
  • Support for encryption of debug data: A debug encryption key compiler option, DBGENCKEY, is supported in the ILE C++ compiler. This option specifies the key to be used to encrypt source code that is embedded in debug views of a module (for example, the Listing View debug view created by specifying the DBGVIEW(*LIST) compile option). An equivalent option is available on the start debug command, STRDBG, to specify the key for decryption of the encrypted debug views.

ADTS 7.1 Enhancements

  • Anexit point to allow customers to monitor or disable changing source files using SEU, SDA, RLU

    Exit point QIBM_QSU_ALW_EDIT is added for SEU, SDA and RLU. The exit program associated with the exit point will receive parameters indicating the library, file, and member of the source file. The exit program can then determine if the current job should be allowed to continue with the operation that will change the source file and set the "Allow" parameter to '2' to indicate that the operation should not be allowed to continue, and to any other value to indicate that the operation should be allowed to continue.

  • The exit point format is EXTP0100.

    The parameters for the exit program are LIBRARY, FILE, MEMBER, ALLOW:

    • LIBRARY CHAR(10)
    • FILE CHAR(10)
    • MEMBER CHAR(10)
    • ALLOW CHAR(1)
  • SEU syntax checking is frozen at the 6.1 level for RPG and COBOL: Features introduced to ILE RPG and ILE COBOL following the 6.1 release are not recognized by the syntax-checkers used by SEU.

ILE RPG 7.2 Enhancements

Support for free-form Control, File, Definition, and Procedure statements. An ILE RPG program can now be written entirely in free form. File definitions and data definitions can be intermixed. The /FREE and /END-FREE directives are no longer required to separate free-form statements and fixed-form statements. Here is an example of free-form code:

        CTL-OPT OPTION(*SRCSTMT : *NODEBUGIO);
        DCL-S total PACKED(7:2);
        DCL-F orders USAGE(*UPDATE);
        DCL-DS orderData LIKEREC(orderFmt);
 
        READ orders orderData;
        DOW NOT %EOF;
           READ orders orderData;
           total += processOrder(orderData);
        ENDDO;
        *INLR = '1';
 
        DCL-PROC processOrder;
           DCL-PI *N PACKED(7:2);
              data LIKEREC(orderData);
           END-PI;
           IF data.quantity > 1000;
              data.price *= data.discount;
             UPDATE orderFmt data;
           ENDIF;
           RETURN data.price * data.quantity;
        END-PROC;

Several CCSID enhancements include:

  • The default alphanumeric CCSID for the module can be set to a CCSID other than the job CCSID.
  • Alphanumeric data can be defined with a CCSID. Supported CCSIDs include:
    • Single-byte and mixed-byte EBCDIC CCSIDs
    • Single-byte and mixed-byte ASCII CCSIDs
    • UTF-8
    • Hexadecimal
  • CCSID conversion is not performed for hexadecimal data, which includes:
    • Hexadecimal literals
    • Alphanumeric and graphic data defined with CCSID(*HEX)
    • Alphanumeric and graphic data in I/O buffers for externally- described files when the DATA keyword is in effect for the file and the CCSID of the field in the file is 65535
    • Alphanumeric and graphic data in externally-described data structures that are defined with CCSID(*EXACT) when the CCSID of the field in the file is 65535
  • Open database files without conversion to the job CCSID. Use Control keyword OPENOPT(*NOCVTDATA) or File keyword DATA(*NOCVT) to specify that a database file will be opened so that alphanumeric and graphic data will not be converted to and from the job CCSID for input and output operations.
  • Use the /SET and /RESTORE directives to set defaults for definitions that do not explicitly specify date formats, time formats, and CCSIDs.
  • Support for implicit conversion between alphanumeric, graphic, and UCS-2 data for concatenation expressions.
  • Support for CCSID conversions that causes a loss of data when a source character does not exist in the target character set
    • Use CCSIDCVT(*EXCP) to get an exception, if a CCSID conversion loses data due to the source character not having a match in the target character set.
    • Use CCSIDCVT(*LIST) to obtain a listing of every CCSID conversion in the module, with a diagnostic message that indicates whether the conversion has the potential of losing data.

Increased precision for timestamp data: timestamp data can have between 0 and 12 fractional seconds.

Control the length that is returned by %SUBDT:

  • An optional third parameter for %SUBDT allows you to specify the number of digits in the result. For example, you can return the value of the years as a four-digit value: %SUBDT(MyDate : *YEARS : 4).
  • An optional fourth parameter allows you to specify the number of decimal places when returning the number of seconds from a timestamp. For example, you can return the number of seconds as a five-digit value with three decimal places: %SUBDT(MyTimestamp : *SECONDS : 5 : 3);.

Additional data types are supported for PCML generation:

  • Date, time, and timestamp
  • 8-byte unsigned integers

XML-INTO options

  • XML namespaces are supported by the "ns" and "nsprefix" options.
  • XML names with characters that are not supported by RPG for subfield names are supported by the case=convert option.

Option to skip the validation step of date, time, and timestamp operations, which may improve performance

  • Use Control-specification keyword VALIDATE(*NODATETIME) to allow the RPG compiler to treat date, time, and timestamp data as character data, without performing the checks for validity.

ILE COBOL 7.2 Enhancements

A timestamp item can now have between 0 and 12 fractional seconds.

  • The following intrinsic functions now allow PICOSECONDS as a duration when specified for a timestamp item: ADD-DURATION, EXTRACT-DATE-TIME, FIND-DURATION, and SUBTRACT-DURATION.
  • The SIZE keyword is allowed with FORMAT TIMESTAMP. The size can be 19 indicating zero fractional seconds or a value between 21 and 32, which indicates between 1 and 12 fractional seconds.

XML PARSE now has the capability to parse XML files that are greater than 16MB in size

  • No individual document piece passed to the processing procedure is greater than 16 MB. The following XML-CODE values are associated with this change:
    • XML-CODE 62 indicates that the XML document exceeds 16,000,000 bytes.
    • XML-CODE 170 indicates that an XML event exceeds 16,000,000 bytes.

PCML generation enhancements

  • PCML generation provides improved handling for an OCCURS DEPENDING ON array with the addition of an "init" keyword set to the maximum size of the array.
  • PCML generation provides automatic data-item naming in generated PCML for filler data items and unnamed items in a data structure, helping to enable web services to use generated PCML without first modifying it. The names for these data items will be _filler_1, _filler_2, and so on.

National data (Unicode) enhancements

  • Numeric national datatype is supported
  • A numeric literal can be specified on the VALUE clause for a numeric national data item
  • The figurative constant ZERO/ZEROS/ZEROES represents one or more national zero digits when used with national data items
  • National 'N' literals are supported when the PROCESS option NATIONALPICNLIT is specified

Options to help improve the accuracy of some numeric operations:

  • Compiler option ARITHMETIC(*EXTEND31) or PROCESS option EXTEND31 can increase the accuracy of NUMVAL and NUMVAL-C to 31 digits.
  • Compiler option ARITHMETHC(*EXTEND31FULL) or PROCESS option EXTEND31FULL can increase floating-point accuracy for several numeric intrinsic functions and can increase fixed-point accuracy for fixed- point intermediate results.

Floating point rounding mode

  • Use NOCHGFLTRND / ALWCHGFLTRND to control whether or not COBOL will use the floating point rounding mode computational attribute specified by MI instruction SETCA. SETCA allows you to set the rounding mode of the result of a floating-point calculation to either round or truncate.

Back to topBack to top

Operating environment

Hardware requirements

The 7.1 product supports all the hardware models that support IBM i 6.1, and 7.1.

Memory and disk space:

     ---------------------------------+----------------------- 
     Option                            Auxiliary storage       
     ---------------------------------+----------------------- 
     Base                                35 MB                 
     ---------------------------------+----------------------- 
     Option 60 Workstation Tools          3 MB                 
     ---------------------------------+----------------------- 
     ILE compilers                                             
     ---------------------------------+----------------------- 
       ILE RPG                           14 MB                 
       ILE RPG *PRV Compiler             25 MB                 
       ILE COBOL                         27 MB                 
       ILE COBOL *PRV Compiler           47 MB                 
       ILE C                             96 MB                 
       ILE C++                           64 MB                 
       IXLC for C/C++                    .5 MB                 
                                                               
                                        The C++ compiler       
                                        requires a machine     
                                        capable of running     
                                        the Portable           
                                        Application Solutions  
                                        Environment or PASE    
                                        (option 33 of the IBM  
                                        i Operating System).   
                                                               
     ---------------------------------+----------------------- 
     Heritage compilers                                        
     ---------------------------------+----------------------- 
       S/36 Compatible RPG II             7 MB                 
       S/38 Compatible RPG III            4 MB                 
       RPG/400                            5 MB                 
       S/36 Compatible COBOL              6 MB                 
       S/38 Compatible COBOL              5 MB                 
       OPM COBOL                          7 MB                 
     ---------------------------------+----------------------- 
     Application Development ToolSet     22 MB                 
     ---------------------------------+----------------------- 
 

The 7.2 product supports all the hardware models that support IBM i 6.1, 7.1, and 7.2.

Software requirements

  • IBM Rational Development Studio for i 7.1 requires IBM i 7.1 (5770-SS1).
  • IBM Rational Development Studio for i 7.2 requires IBM i 7.2 (5770-SS1).
  • The C and C++ compilers in the product require the "System Openness Includes" (option 13 of 5770-SS1). Installing the "System Openness Includes" is optional for RPG and COBOL. The C++ compiler requires the Portable Application Solutions Environment or PASE (option 33 of 5770-SS1). To use the ixlc shell command, the Qshell interpreter (option 30 of 5770-SS1) must be installed.

Back to topBack to top

Planning Information

Customer responsibilities

The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.

Publications

No publications are shipped with this program.



Back to topBack to top

Security, Auditability, and Control

IBM Rational Development Studio for i uses the security and auditability features of the IBM i.
 

Back to topBack to top

Trademarks

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation. ** Company, product, or service name may be a trademark or service mark of others.

Terms of use

IBM products and services which are announced and available in your country can be ordered under the applicable standard agreements, terms, conditions, and prices in effect at the time. IBM reserves the right to modify or withdraw this Sales Manual at any time without notice. This Sales Manual is provided for your information only. Additional terms of use are located at

Terms of use

© IBM Corporation 2019.