Presentation Outline

Size: px

Start display at page:

Download "Presentation Outline"

Katherine Scott
6 years ago
Views:

1 Wilfried Van Hecke IBM Certified IT Specialist IBM Sales & Distribution, Software Sales Europe PanIMT PD Tools Community Leader System z Software Technical Sales Hans Emrich (emrich@de.ibm.com) ADTools + Rational on System z Technical Sales and Solutions IBM Sales & Distribution, Software Sales Enterprise Modernization Enterprise COBOL V5 What's new! Presentation Outline New functions in Enterprise COBOL V5 Key prerequisites New and recent news 2 1

2 Enterprise COBOL V5.1 Generally available June 21, W32 Incorporates new optimization and code-generation technology into z/os COBOL Exploits latest z/architecture instructions Foundation for support of new hardware features and future System z processors Positioning for future 64-bit exploitation New function for creating new applications and modernizing existing applications New usability and problem determination capabilities Goal is to maintain source and object code compatibility, except for dropping selected obsolete language features 3 New Functions 4 2

Raise compiler limits Enterprise COBOL V4: Limit for each data division section: 128 MB (aggregate size of all data items) Limit for individual data item: 128 MB Enterprise COBOL V5: No aggregate

improvement - initialization overhead significantly reduced for programs containing very large data items 5 Optimization options New compiler options for optimization and processor exploitation:

3 Raise compiler limits Enterprise COBOL V4: Limit for each data division section: 128 MB (aggregate size of all data items) Limit for individual data item: 128 MB Enterprise COBOL V5: No aggregate data division limit - up to address space capacity Limit for individual data item: 999,999,999 bytes (1 Gigabyte) LENGTH OF special register implicit definition: PICTURE 9(9) USAGE BINARY Performance improvement - initialization overhead significantly reduced for programs containing very large data items 5 Optimization options New compiler options for optimization and processor exploitation: OPTIMIZE( ) Optimization level ARCH( ) Processor architecture ARCH(6): z990, z890 ARCH(7): System z9 ARCH(8): System z10 ARCH(9): zenterprise 196 ARCH(10): zenterprise EC12 STGOPT / NOSTGOPT Storage optimization - like OPT(FULL) in Enterprise COBOL V4 HGPR(PRESERVE NOPRESERVE) AFP(VOLATILE NOVOLATILE) 6 3

4 ARCH(n): new benefits for COBOL ARCH(6) z990, z890 (and above) Relative instructions: branches, data references relative to executing instruction Half word immediate instructions Long displacement instructions 64-bit binary operations (more than 9 digit picture) in 64-bit register ARCH(7) z9 Extended immediate data up to 32 bits within instruction ARCH(8) z10 Decimal Floating Point can be used internally for packed decimal multiplication and division Wider immediate instructions with 2, 4, and 8 byte versions ARCH(9) z196 Distinct operand: arithmetic instructions that update a register in place now allow a third (target) register and leave contents of the sources unchanged. Conditional load: register can be conditionally loaded (without surrounding branching logic). ARCH(10) EC12 High word instructions: the top half of each GPR not used to hold a 64-bit value is available for register allocation More Decimal Floating Point instructions, e.g. conversion between Zoned Decimal and Decimal Floating Point. 7 New Unicode Intrinsic Functions New intrinsic functions improve usability for programming with UTF-8 Unicode Complements support for UTF-16 Unicode that is built into the language with native data types (USAGE NATIONAL) UTF-8 data is stored in alphanumeric (PIC X) items Note UTF-8 characters vary in size, from 1 to 4 bytes direct manipulation with native COBOL verbs (INSPECT, UNSTRING, ) is difficult and error prone 8 4

5 Unicode Intrinsic Functions FUNCTION ULENGTH(utf8-argument) Returns number of logical UTF-8 characters in argument FUNCTION UPOS(utf8-argument, n) Returns index of byte where the nth logical UTF-8 character starts FUNCTION USUBSTR(utf8-argument, n, len) Returns substring starting at nth logical UTF-8 character, for length len logical UTF-8 characters FUNCTION UWIDTH(utf8-argument, n) Return width in bytes of the nth logical UTF-8 character in utf8-argument 9 Unicode Intrinsic Functions FUNCTION UVALID(argument) Return index of first byte in alphanumeric argument containing an invalid UTF-8 byte sequence, or zero if all are valid - or - Return index of first UTF-16 encoding unit in national argument containing an invalid UTF-16 character, or zero if all are valid FUNCTION USUPPLEMENTARY(argument) Argument may be alphanumeric (UTF-8) or national (UTF-16) Return index of the first Unicode supplementary character in argument (or zero, if none) Note: a supplementary character is: - A Unicode character above U+FFFF - A character outside the Basic Multilingual Plane (BMP) - Encoded in UTF-16 using a surrogate pair - Encoded in UTF-8 with a 4 byte representation 10 5

XML Processing Enhancements 11 XML Generate with suppression - example 01 G. 02 Aarray value spaces. 03 A pic AAA occurs 5. 02 Barray value spaces. 03 B pic XXX occurs 5.

6 XML Processing Enhancements 11 XML Generate with suppression - example 01 G. 02 Aarray value spaces. 03 A pic AAA occurs Barray value spaces. 03 B pic XXX occurs Carray value zeros. 03 C pic 999 occurs Doc pic X(500). Move "abc" to A(3) Move 123 to C(3) XML Generate Doc from G Count in tally End-XML Display Doc(1:tally) 12 6

7 XML Generate with suppression example... Default output: lots of blank and zero entries! <G> <Aarray><A> </A><A> </A><A>abc</A><A> </A><A> </A> </Aarray> <Barray> </Barray> <Carray><C>0</C><C>0</C><C>123</C><C>0</C><C>0</C> </Carray> </G> Output with suppression requested: <G> <Aarray><A>abc</A></Aarray> <Carray><C>123</C></Carray> </G> 13 XML GENERATE with suppression XML Generate Doc from G Suppress every nonnumeric element when space every numeric element when zero End-XML Or equivalently: XML Generate Doc from G Suppress A when space B when space C when zero End-XML Or equivalently: XML Generate Doc from G Suppress when space or zero End-XML 14 7

XML GENERATE with user-supplied names 01 Msg. 02 Msg-Severity pic 9 value 1. 02 Msg-Date pic 9999/99/99 value "2

8 XML GENERATE with user-supplied names 01 Msg. 02 Msg-Severity pic 9 value Msg-Date pic 9999/99/99 value "2013/05/09". 02 Msg-Text pic X(50) value "Sell everything!". XML Generate Doc from Msg With attributes Name of Msg is "Message" Name of Msg-Severity is "Severity" Name of Msg-Date is "Date" Name of Msg-Text is "Text"... End-XML <Message Severity="1" Date="2013/05/09" Text="Sell everything!"></message> 15 User control of attributes and element generation Two choices in V4, either all elements or all attributes: 01 Msg. 02 Msg-Severity pic 9 value Msg-Date pic 9999/99/99 value "2013/05/09". 02 Msg-Text pic X(50) value "Sell everything!". XML Generate Doc from Msg <Msg><Msg-Severity>1</Msg-Severity> <Msg-Date>2013/05/09</Msg-Date> <Msg-Text>Sell everything!</msg-text> </Msg> XML Generate Doc from Msg with attributes <Msg Msg-Severity="1" Msg-Date="2013/05/09" Msg-Text="Sell everything!">... </Msg> 16 8

9 V5: Choice of element, element content, or attribute 01 Msg. 02 Msg-Severity pic 9 value Msg-Date pic 9999/99/99 value "2013/05/09". 02 Msg-Text pic X(50) value "Sell everything!". XML Generate Doc from Msg Type of Msg-Severity is attribute Msg-Date is element Msg-Text is content End-XML <Msg Msg-Severity="1"> <Msg-Date>2013/05/09</Msg-Date> Sell everything! </Msg> 17 XML Parse toleration of undeclared namespace prefix Example: <pfx:msg>hello</pfx:msg> XML Parse statement now has new warning-level exception codes (800, 801) for use of undeclared namespace prefix In the EXCEPTION event, set XML-CODE to ZERO to ignore warning-level exception and continue parse Typical usage: parse SOAP message Body without the containing SOAP Envelope that has the namespace definitions Requires z/os 2.1 with LE APAR PM

10 XML Parse with continued data With z/os XML Services parser: Element content or attribute characters might not all be delivered on a single XML event Content might be split across multiple events Application program logic must concatenate pieces of content together 19 XML PARSE example, with continued content XML document in data item Doc: <pfx:greeting xmlns:pfx=" <pfx:msg type="brief">hello, world!</pfx:msg> </pfx:greeting> COBOL program logic: XML Parse Doc processing procedure P P. Display XML-event XML-text XML-namespace-prefix XML-namespace. XML-Event START-OF-DOCUMENT XML-Text XML-namespace-prefix XML-namespace START-OF-ELEMENT Greeting pfx NAMESPACE-DECLARATION pfx START-OF-ELEMENT msg pfx ATTRIBUTE-NAME type ATTRIBUTE-CHARACTERS brief CONTENT-CHARACTERS Hello, CONTENT-CHARACTERS world! END-OF-ELEMENT msg pfx END-OF-ELEMENT Greeting pfx END-OF-DOCUMENT 20 10

11 XML parse with continued data... New COBOL syntax to aid programming when split element content or attribute value occurs New special register XML-INFORMATION Implicit definition: 01 XML-INFORMATION PIC S9(9) BINARY VALUE ZERO. Processing procedure can determine if element content or attribute value is complete, or is continued on next event XML-INFORMATION = 1 if value in XML-TEXT or XML-NTEXT is complete XML-INFORMATION = 2 if value is incomplete Now also available in V4.2, delivered via service stream 21 COBOL enhancement for unbounded arrays New COBOL syntax extension for OCCURS clause: UNBOUNDED keyword Linkage Section. 01 G. 02 A pic X(5). 02 B pic 9(2) occurs 1 to unbounded depending on NB. 02 C pic 9(2) occurs 1 to unbounded depending on NC. 01 NB pic S9(9) binary. 01 NC pic S9(9) binary. Facilitates mapping of XML Schema containing unbounded constructs, to COBOL data structure 22 11

Additional enhancements 23 Debugging enhancements TEST compiler option simplified Debug information: Stored in a binder "No Load" class within module Only loaded into memory if requested

12 Additional enhancements 23 Debugging enhancements TEST compiler option simplified Debug information: Stored in a binder "No Load" class within module Only loaded into memory if requested Represented in industry-standard DWARF format, accessed via Common Debug Architecture services SEPARATE/NOSEPARATE suboptions of TEST no longer needed New function: STEP OVER a PERFORM statement 24 12

TEST( EJPD NOEJPD, SOURCE NOSOURCE) EJPD: enables JUMPTO and GOTO commands when debugging optimized

13 TEST option syntax NOTEST( DWARF NODWARF) DWARF: include basic diagnostic DWARF info in module for use in CEEDUMP, Fault/ABEND analysis, etc. TEST( EJPD NOEJPD, SOURCE NOSOURCE) EJPD: enables JUMPTO and GOTO commands when debugging optimized code SOURCE: expanded source code included in DWARF info for debugging NOSOURCE: debugger uses compiler listing to get expanded source 25 IBM Debug Tool 26 13

14 IBM Fault Analyzer 27 Application Performance Analyser 28 14

Inline comments New floating comment indicator *> Specify anywhere in program text area (Area A or Area B, columns 8 72) Indicates a comment line if used as first character string in program text

15 Inline comments New floating comment indicator *> Specify anywhere in program text area (Area A or Area B, columns 8 72) Indicates a comment line if used as first character string in program text area Indicates an inline comment if it follows other strings in program text area Procedure division. Add 1 to X *> Increment bitcoin count 29 MAXPCF(n) option Specify a Maximum Program Complexity Factor n for optimization Complexity factor includes more than statements, e.g. Expansion of EXEC SQL, EXEC CICS Data initialization Processing for variable length items If exceeded, OPT(n) option automatically reduced to OPT(0) Use to avoid excessive compilation time or storage when compiling a suite of COBOL programs 30 15

16 Goal: DISPSIGN(SEP COMPAT) option Improve usability of DISPLAY output for numeric fields Print sign values as leading + or -% Avoid unreadable output for numbers with overpunch signs COMPAT suboption to preserve exact compatibility Example DISPLAY output with DISPSIGN(COMPAT) negative packed-decimal 22K positive zoned-decimal 33C Example DISPLAY output with DISPSIGN(SEP) negative packed-decimal -222 positive zoned-decimal LVLINFO installation option Now 8 bytes instead of 4, you can put APAR, PTF, or your own numbers Example: LVLINFO=PN Listing header: PP 5655-W32 IBM Enterprise COBOL for z/os PN Date 05/20/2013 Time 10:45:03 Signature bytes: 00088E (+40) =X' ' INFO. BYTES (+44) D7D5F1F2F3F4F5F6 =C'PN123456' USER LEVEL INFO (LVLINFO) 32 16

SMF-89 records Compiler now instrumented to work with the z/os System Management Facilities (SMF) Generates SMF-89 records Processed by Sub-Capacity Reporting Tool (SCRT) - requires SCRT V21

17 SMF-89 records Compiler now instrumented to work with the z/os System Management Facilities (SMF) Generates SMF-89 records Processed by Sub-Capacity Reporting Tool (SCRT) - requires SCRT V or later Reduces administrative overhead for implementation of subcapacity pricing 33 Enterprise COBOL V5: key prerequisites z/os V1R13 or V2R1 Hardware processor model: 2084-xxx (z990), 2086-xxx (z890), or later Note z900, z800 no longer supported CICS Transaction Server for z/os V3 IMS V11 Problem Determination Tools V12 Rational Developer for System z V9 Use FIXCAT to find prerequisite service PTFs to LE, Binder, DB2, Debug Tool, CCCA,

New and recent news 35 Enterprise COBOL V5.

the value that could be gained from upgrading to Enterprise COBOL V5.1 Same function as Enterprise COBOL V5.

18 New and recent news 35 Enterprise COBOL V5.1 Developer Trial Trial product generally available October 4, TRY Zero-cost evaluation license for 90 days Assess the value that could be gained from upgrading to Enterprise COBOL V5.1 Same function as Enterprise COBOL V5.1 (except generation of SMF-89 records for subcapacity pricing) Same pre-requisites as Enterprise COBOL V5.1 (e.g. runs on z/os V1.13 and z/os V2.1) Code compiled with Developer Trial cannot be used for production Developer Trial is supported by IBM Service: questions, problem reports, but not fixes APAR/PTF fixes delivered in normal V5 product and future refreshes of the trial product

19 IMS SQL Coprocessor Enterprise COBOL V5 and IMS 13 now support EXEC SQLIMS statements embedded in COBOL programs Access IMS databases from COBOL using SQL, similar to relational database access Coprocessor enabled by compiler option: SQLIMS("IMS-suboption-string") Analogous to coprocessors for EXEC SQL and EXEC CICS statements COBOL support shipped: - via V5 service stream, APAR PM and in Enterprise COBOL Developer Trial product Caveat: first release requires codepage 1140 or Recent Enterprise COBOL V5 updates via service Dynamic storage (WSA) allocation design updated With V5, WORKING-STORAGE, file record areas, etc. are allocated in the Writable Static Area (WSA), managed by LE and DFSMS After service update, COBOL dynamic storage now allocated on LE Heap (in most cases), as with V4 LE options for heap tuning, reporting, and initialization apply Improves initialization performance for short transactions Some cases still allocate dynamic storage via Program Management loader service, in Subpool 1: DLL applications Mixed language modules, e.g. COBOL + C 38 19

20 Enterprise COBOL V5 Run Time Language Environment Program Object CODE WSA = Working Storage Eventually DWARF (Debug Tool) COBOL 5 Run Time Other Language (including older COBOL) Run Times Stack (local Storage, etc ) Heap (WSA, etc ) 39 Thank you! Any Questions or Comments? 40 20

21 Thank you! Any Questions or Comments? 41 New function in Enterprise COBOL V4.2 XML-INFORMATION special register Facilitate migration from XMLPARSE(COMPAT) to XMLPARSE(XMLSS) Migration to XMLSS parser can be done with V4, prior to Enterprise COBOL V5 migration FLAGMIG4 compiler option Generates warning diagnostic for use of obsolete language syntax not supported by V5 Delivered via V4 service stream PM85428, PM85035 (V4.2 compiler) PM87347 (LE) 42 21

22 Design Partner Program for Enterprise COBOL Program Mission: To involve clients early in the design and development process of our products to improve quality, deliver the right strategy and features, and increase client satisfaction. Benefits to participants Direct input on design of new COBOL features Visibility into product strategy and roadmaps Early experience with pre-release drivers Nomination: Program contacts: Marie Bradford Roland Koo Input from the European perspective is needed, and would be especially valuable! 43 Recent Enterprise COBOL V5 updates via service... IMS SQL Coprocessor XML Parse toleration of undeclared namespace prefix Performance tuning Various corrections for issues reported late in the Beta, or from early users 44 22

S16150: What s New in COBOL Version 5 since GA

S16150: What s New in COBOL Version 5 since GA Tom Ross IBM Aug 4, 2014 1 Title: What's new in COBOL v5 since GA Refresher about COBOL V5 requirements Service updates Improved compatibility New Function