1 / 22

V6R1 – RPG enhancements

V6R1 – RPG enhancements. THREAD(*CONCURRENT) Ability to define a main procedure which does not use the RPG cycle Files defined in subprocedures Qualified record formats Files defined like other files Files passed as parameters. V6R1 – RPG enhancements. EXTDESC keyword and EXTFILE(*EXTDESC)

tahlia
Download Presentation

V6R1 – RPG enhancements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. V6R1 – RPG enhancements • THREAD(*CONCURRENT) • Ability to define a main procedure which does not use the RPG cycle • Files defined in subprocedures • Qualified record formats • Files defined like other files • Files passed as parameters

  2. V6R1 – RPG enhancements • EXTDESC keyword and EXTFILE(*EXTDESC) • EXTNAME to specify the library for the externally-described data structure • EXFMT allows a result data structure

  3. V6R1 – RPG enhancements • Larger limits for data structures, and character, UCS-2 and graphic variables • %ADDR(varying : *DATA) • Larger limit for DIM and OCCURS • Larger limits for character, UCS-2 and DBCS literals

  4. V6R1 – RPG enhancements • TEMPLATE keyword for files and definitions • Relaxation of some UCS-2 rules • Eliminate unused variables from the compiled object • PCML can now be stored in the module

  5. THREAD(*CONCURRENT) When THREAD(*CONCURRENT) is specified on the Control specification of a module, it provides ability to run concurrently in multiple threads.

  6. Ability to define a main procedure which does not use the RPG cycle When THREAD(*CONCURRENT) is specified on the Control specification of a module, it provides ability to run concurrently in multiple threads. * The prototype for the linear-main procedure must have * the EXTPGM keyword with the name of the actual program. D DisplayCurTime PR EXTPGM(’DSPCURTIME’)

  7. Ability to define a main procedure which does not use the RPG cycle * The program is named DSPCURTIME, and the module has * a linear-main procedure called DisplayCurTime. * The Control specification MAIN keyword signifies that this is * a linear-main module, and identifies which procedure is the * special subprocedure which serves as the linear-main procedure, * which will act as the program-entry procedure. H MAIN(DisplayCurTime) * Copy in the prototype for the program /COPY DSPCURTIME *-------------------------------------------------- * Procedure name: DisplayCurTime *-------------------------------------------------- P DisplayCurTime B D DisplayCurTime PI /FREE dsply (’It is now ’ + %char(%time())); /END-FREE P DisplayCurTime E

  8. Files defined in subprocedures NameHeading=GetCompanyName(); P GetCompanyNameB D GetCompanyNamePIlike(coname) FParmFile IFEKDISK /free chain'CONAME'ParmFile; return coname; /end-free P GetCompanyName E

  9. Qualified Record Formats * file1 has formats HDR, INFO, ERR. * file2 has format INFO. * The QUALIFIED keyword is used for both files, making it * unnecessary to rename one of the "INFO" formats. * Note that the record format names are not qualified when * specified in keywords of the File specification. Ffile1 ifedisk qualified Fignore(hdr) Frename(err:errorRec) Ffile2 oedisk qualified * The record formats must be qualified on all specifications * other than the File specification for the file.

  10. Qualified Record Formats D ds1 dslikerec(file1.info : *input) D errDs ds likerec(file1.errorRec : *input) D ds2 dslikerec(file2.info : *output) /free read file1.info ds1; eval-corr ds2 = ds1; writefile2.info ds2; read file1.errorRec errDs;

  11. Files defined like other files FFILE1 IFEDISK EXTMBR(extmbrVariable) FFILE2 LIKEFILE(FILE1) F EXTFILE(extfileVariable) Useful for opening the same file twice in one program without having to OVRDBF to get the compile to work.

  12. EXTDESC keyword and EXTFILE(*EXTDESC) The EXTDESC keyword can be specified to indicate which file the compiler should use at compile time to obtain the external descriptions for the file. The file specified by the EXTDESC keyword is used only at compile time. At runtime, the file is found using the same rules as would be applied if the EXTDESC keyword was not specified. You can use additional keyword EXTFILE(*EXTDESC) if you also want the file specified by the EXTDESC keyword to be used at runtime. Useful to avoid OVRDBF just to compile.

  13. EXTNAME to specify the library for the externally-described data structure The EXTNAME keyword is enhanced to allow a literal to specify the library for the external file. EXTNAME(’LIBNAME/FILENAME’) or EXTNAME(’FILENAME’) are supported. This removes the need to provide a compile-time override for the file.

  14. EXFMT allows a result data structure The EXFMT operation is enhanced to allow a data structure to be specified in the result field. The data structure must be defined with usage type *ALL, either as an externally-described data structure for the record format (EXTNAME(file:fmt:*ALL), or using LIKEREC of the record format (LIKEREC(fmt:*ALL).

  15. Larger Limits • Larger limits for data structures, and character, UCS-2 and graphic variables • Data structures can have a size up to 16,773,104. • Character definitions can have a length up to 16,773,104. (The limit is 4 less for variable length character definitions.) • Character definitions can have a length up to 16,773,104. (The limit is 4 less for variable length character definitions.) • UCS-2 definitions can have a length up to 8,386,552 UCS-2 characters. (The limit is 2 less for variable length UCS-2 definitions.) • Graphic definitions can have a length up to 8,386,552 DBCS characters. (The limit is 2 less for variable length graphic definitions.) • The VARYING keyword allows a parameter of either 2 or 4 indicating the number of bytes used to hold the length prefix. %ADDR(varying : *DATA) The %ADDR built-in function is enhanced to allow *DATA as the second parameter to obtain the address of the data part of a variable length field.

  16. Larger Limits Larger limit for DIM and OCCURS • An array or multiple-occurrence data structure can have up to 16,773,104 elements, provided that the total size is not greater than 16,773,104. Larger limits for character, UCS-2 and DBCS literals • Character literals can now have a length up to 16380 characters. • UCS-2 literals can now have a length up to 8190 UCS-2 characters. • Graphic literals can now have a length up to 16379 DBCS characters.

  17. TEMPLATE keyword for files and definitions The TEMPLATE keyword can be coded for file and variable definitions to indicate that the name will only be used with the LIKEFILE, LIKE, or LIKEDS keyword to define other files or variables. Template definitions are useful when defining types for prototyped calls, since the compiler only uses them at compile time to help define other files and variables, and does not generate any code related to them. Template data structures can have the INZ keyword coded for the data structure and its subfields, which will ease the use of INZ(*LIKEDS).

  18. Eliminate unused variables from the compiled object New values *UNREF and *NOUNREF are added to the OPTION keyword for the CRTBNDRPG and CRTRPGMOD commands, and for the OPTION keyword on the Control specification. The default is *UNREF. *NOUNREF indicates that unreferenced variables should not be generated into the RPG module. This can reduce program size, and if imported variables are not referenced, it can reduce the time taken to bind a module to a program or service program.

  19. Relaxation of some UCS-2 rules The compiler will perform some implicit conversion between character, UCS-2 and graphic values, making it unnecessary to code %CHAR, %UCS2 or %GRAPH in many cases. This enhancement is also available through PTFs for V5R3 and V5R4. Implicit conversion is now supported for • Assignment using EVAL and EVALR. • Comparison operations in expressions. • Comparison using fixed form operations IFxx, DOUxx, DOWxx, WHxx, CASxx, CABxx, COMP. • Note that implicit conversion was already supported for the conversion operations MOVE and MOVEL. UCS-2 variables can now be initialized with character or graphic literals without using the %UCS2 built-in function.

  20. PCML can now be stored in the module Program Call Markup Language (PCML) can now be stored in the module as well as in a stream file. By using combinations of the PGMINFO command parameter and/or the new PGMINFO keyword for the Control specification, the RPG programmer can choose where the PCML information should go. If the PCML information is placed in the module, it can later be retrieved using the QBNRPII API. This enhancement is also available through PTFs for V5R4, but only through the Control specification keyword.

  21. Briefly… • Files passed as parameters

  22. Bibliography What’s new http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/topic/rzasd/sc09250807.htm?tocNode=int_230543 ILE RPG Language Reference http://publib.boulder.ibm.com/infocenter/systems/scope/i5os/topic/rzasd/sc092508.pdf System i Technical Overviews http://www-304.ibm.com/jct01004c/systems/support/i/library/techoverviews/ Presentations http://www.statususer.org/html/newsletterArchive.html

More Related