Cobol Evaluate True Also True

Cobol Evaluate True Also True
1Chapter: 1Supported Platforms .

1Chapter: 2Cobol Technical Metrics .

.5ol : 3SQL Technical Reference

.

1 17Complexity Metrics .

18L .

20Chapter: 4JCL Technical Reference

23Complexity Metrics .

25L : 5CICS Technical Reference .

.

31 31Complexity Metrics .

34ts .

37 2 FCT, and PCT Statements .<: 6IDMS Technical Reference

.

49IDMS Support Complexity Metrics .

51m IDMS Schema Statements

.

53m IDMS DML : 7IMS Technical Reference

.

5IMS Support Notes

.

59IMS Complexity Metrics .

63PSB Statements

.

71 1This document describes Modernization Workbench (MW) support for Cobol and related platforms:COBOL for OS/390, Version 2 Release 2.See CICS Transaction Server for For CICS commands, see CICS Application Programming Reference, For Basic Mapping -ming Reference, CICS Transaction Server for OS/390, Release 3, Publication No.SC33-1688-35, IBM, 2000.For resource definition, see Transaction Server fo, Publication No.

IDMS, Release 15.0For DML statements, see For database definition, see CA-IDMS Database AdministrationIMS, Version 7For DL/I calls, see For Exec DLI commands, see , Publication No.

For PSB and DBD files, see Utilities Reference: System, Publication UPPORTEDFor MFS files, see JCL, OS/390 Version 2 Release 10For JCL files, see For sort cards, DFSORT Application ProgrSQL.DB2 Universal Database for z/OS, Version 8.See DB2 UDB for z/OS

3Cobol Technical ReferenceThis section describes MW support for Cobol files and copybooks:Support Notes on page 3 describes MW limitations, caveats, and special usage for Cobol applications.Complexity Metrics on page 5 describes the supported complexity metrics for objects in the Cobol model.Relationship Projections from Cobol Statements on page 13 describes support files.Support NotesThese notes describe MW limitations, caveats, and special usage for Cobol applications.Make sure to check the Release Notes on the installation CD for any late-breaking support information.Object-Oriented StatementsObject-oriented Cobol statements are not supported.Program IDs Program IDs must be unique.ECHNICALUPPORTwed by a blank, , the parser may treat

as a numeric literal, espe-cially when the program was compiled with the DECIMAL POINT IS COMMA ary, and the library is referenced in a COPY statement with the format COPY text-name IN
or exist, for a copybook named text-name.

If It is your responsibility filepaths and dot (.) separators: dir1.dir2.member.cpy represents the copybook NOTEwith a short name, the referencing source file will not be invalidated.Its up to you source needs to be reverified.OBOLOMPLEXITYfficult it is to maintain, The table below describes MetricDescriptionBlank LinesNumber of blank lines of source (sequence number area content is ignored).Include StatementsNumber of include statements: COPY, ++INCLUDE, INC, EXEC SQL INCLUDE.Lines with CommentsNumber of lines of source containing comments, including inline comments placed on lines with statements.Source LinesNumber of lines of source, including blank lines and comments.Total Include StatementsNumber of include statements in the file and any used include files.MetricDescriptionBlank LinesNumber of blank lines of source (sequence number area content is ignored).Data ElementsNumber of declared data items (elementary structures and their table below describes object.

For more information on dead code statistics, see How MW Calculates Abbreviated conditions are expanded before calculations.DECLARATIVEs content and other exHandling of EVALUATE formats:
EVALUATE

[ALSO ] Conditional ] Binary Decision, Conditional Statement

WHEN OTHER Conditional Statement
END-EVALUATEHandling of SEARCH formats:
SEARCH

AT END

Binary Decision, Conditional Statement

WHEN AND Binary Decision, Conditional Statement
END-SEARCHInclude StatementsNumber of include statements: COPY, ++INCLUDE, INC, EXEC SQL INCLUDE.Lines with CommentsNumber of lines of source containing comments, including inline comments placed on lines with statements.Source LinesNumber of lines of source, including blank lines and ComplexityBinary Decisions divided by the number of statements.Asynchronous CallsNumber of asynchronous calls, such as Cobol INITIATE statements.OBOLOMPLEXITYBinary DecisionsNumber of branching conditions in the flow graph with two possible outcomes.Includes statements with implicit condition evaluation (loops, AT END, and so on): IF, EVALUATE (number of WHEN except WHEN OTHER), PERFORMTIMES, PERFORMUNTIL, PERFORMVARYING, PERFORMVARYINGAFTER (number of AFTER phrases + 1), statements with ON/NOT ON, AT END/NOT AT END, INVALID/NOT INVALID (one decision per statement), GOTODEPENDING ON (number of alternatives), SEARCH (number of WHEN, AT END).IDMS: IF.Computational StatementsNumber of statements performing arithmetic calculations: ADD, SUBTRACT, DIVIDE, MULTIPLY, COMPUTE.Conditional ComplexityBinary Decisions plus Unique Operands in Conditions.Conditional StatementsNumber of branching statements with nested statements executed under certain conditions, not including conditional GOTOs.IF, EVALUATE, SEARCH, PERFORMUNTIL, PERFORMVARYINGUNTIL, statements with ON/NOT ON, AT END/NOT AT END, INVALID/NOT INVALID.IDMS: IF.Cyclomatic Complexityv(G) = e - n + 2, where v(G) is the cyclomatic complexity of the flow graph (G) for the program in question, e is the number of edges in G, and n is the number of nodes.

Quantity of decision logic.The number of linearly independent paths (minimum number of paths to be tested).

v(G) = DE + 1, where DE is the number of binary decisions made in the program.Data ElementsNumber of declared data items (elementary structures and their fields).Dead Data ElementsNumber of dead data elements in programs and used include files.

Dead data elements are unused structures at any data level, all of whose parents and children are Data Elements from IncludesNumber of dead data elements in include files.Dead data elements are unused structures at any data level, all of whose parents and children are unused.Dead LinesNumber of dead lines in programs and used include files.Dead lines are source lines containing Dead Data Elements or Dead Statements.

Also, source lines containing dead constructs.

If an include file is included multiple times, it is counted each time.Dead Lines from IncludesNumber of dead lines in include files and used include files.Dead lines are source lines containing Dead Data Elements from Includes or Dead Statements from Includes.Also, source lines containing dead constructs.If an include file is included multiple times, it is counted each time.Dead StatementsNumber of dead statements in programs and used include files.A dead statement is a procedural statement that can never be reached during program execution.Dead Statements from IncludesNumber of dead statements in include files.

A dead statement is a procedural statement that can never be reached during program execution.DifficultyD = (n1 / 2) * (N2 / n2), where n1 is Unique Operators, N2 is Operands, and n2 is Unique Operands.Entry PointsNumber of program entry points: PROCEDURE DIVISION, ENTRY.Error EstimateB = E**(2/3) / 3000, where E is Programming Effort.Essential ComplexityQuantity of unstructured logic (a loop with an exiting GOTO statement, for example).v(G) for reduced graph without D-structured primes.Executable StatementsAll Procedure Division statements, plus CONTINUE and NEXT STATEMENT.Extended Cyclomatic ComplexityCyclomatic Complexity plus Logical Operators in Conditions.Number of all paths in the PointsLines of Code/K, where K=77.Estimate of the number of end-user business functions implemented by the program.GoTo StatementsNumber of GOTO statements, including conditional GOTOs: GOTO, GOTO...DEPENDING ON.Inner Call StatementsNumber of statements that invoke Inner Procedures: PERFORM procedure-name.Inner ProceduresNumber of structured pieces of code that cannot be invoked from external programs: Cobol paragraphs (including nameless).Intelligent ContentI = L * V, where L is Program Level and V is Program Volume.Complexity of a given algorithm independent of the language used to express the algorithm.IO StatementsNumber of statements performing input/output operations: OPEN, CLOSE, READ, WRITE, REWRITE, DELETE, START, SORT, MERGE, RETURN, RELEASE, ACCEPT, DISPLAY, STOP literal.SQL: INSERT, FETCH, SELECT, UPDATE, DELETE, EXECUTE.CICSCONVERSE, SEND, SEND MAP, SEND TEXT, RECEIVE, RECEIVE MAP, RECEIVE TEXT, READQ, WRITEQ, DELETEQ, READ, READNEXT, READPREV, WRITE, REWRITE, DELETE.IDMS: ERASE, OBTAIN, GET, MODIFY, STORE
Ibm Enterprise Cobol For Z/os, Version 4
Enterprise COBOL for z/OS also includes a high-speed parser that enables your COBOL programs to: ... IF or EVALUATE. Debug object-oriented COBOL syntax (publib.boulder.ibm.com)
The Cobol Programming Language
switch-like statements known from C. COBOL offers programmers the EVALUATE verb. The format is: ... EVALUATE { expression-1 } ALSO { expression-2 } (publib.boulder.ibm.com)
Chapter 8 Decision Making Using The If And Evaluate Statements
Decision Making Using the IF and EVALUATE Statements COBOL Statements Two categories ... • May also use DeMorgan's Rule to negate compound conditions (publib.boulder.ibm.com)
.Lines of CodeNumber of lines of code, including include files, but not including comments and blank lines.If an include file is included multiple times, it is counted each time.Logical Operators in ConditionsNumber of binary logical operators used in conditions: AND, OR.Loop StatementsNumber of repetitively executing statements: PERFORMTIMES, PERFORMUNTIL, PERFORMVARYING PERFORMVARYINGAFTER (# of AFTER + IndexMI = 171 - 5.2 * ln (PgmVolume) - 0.23 * ExtCycComp - 16.2 * ln (LOC) + 50 * sin (sqrt (2.46 * CommentLines/SourceLines)), where PgmVolume is Program Volume, ExtCycComp is Extended Cyclomatic Complexity, LOC is Lines of Code, CommentLines is Comment Lines, and SourceLines is Source Lines.Nesting LevelMaximum nesting of conditional statements within conditional statements (0 if no conditional statements, 1 if no nesting).Non-returning CallsNumber of non-returning calls, such as CICS XCTL statements.OperandsNumber of operand occurrences (N2).Operands are variables and literals used in operators.

Compare Unique Operands.OperatorsNumber of operator occurrences (N1).Operators are executable statements and unary and binary operations: +, -, *, /, **, NOT, AND, OR&#x=,00;&#x=,00;, , =, , =, =, IS, (subscript), (reference:modification), FUNCTION.Compare Unique Operators.ParametersNumber of Cobol Procedure Division USING...RETURNING parameters.PointersNumber of data elements declared as pointers.Data items with USAGE IS POINTER, PROCEDURE-POINTER.Program LengthN = N1 + N2, where N1 is Operators and N2 is Operands.Program LevelL = 1 / D, where D is Difficulty.Program VolumeV = N * log2(n), where N is Program Length and n is Vocabulary.Minimum number of bits required to code the program.Programming EffortE = V / L, where V is Program Volume and L is Program Level.Estimated mental effort required to develop the program.Programming TimeT = E / 18, where E is the Programming Effort and 18 is Strouds Number.Estimated amount of time required to implement the algorithm, in section provides details on how MW calculates Cobol dead code statistics.Dead Statements reached during program dead.

For instance, EXEC CICS HANDLE

when all EXEC Dead Data ElementsDead data elements are unused structures at any data level, all of whose parents Returning CallsNumber of returning calls, such as CALL or LINK statements.Unique OperandsNumber of distinct operands (n2).Operands are variables and literals used in operators.Uniqueness of literals is determined by their notation.Compare Operands.Unique Operands in ConditionsNumber of distinct operands used in conditions.Unique OperatorsNumber of distinct operators (n1).

Operators are executable statements and unary and binary operations: +, -, *, /, **, NOT, AND, OR&#x=,00;&#x=,00;, , =, , =, =, IS, (subscript), (reference:modification), FUNCTION.Compare Operators.Vocabularyn = n1 + n2, where n1 is the number of Unique Operators and n2 is the number of Unique paragraph consisting solely of dead statements is a dead paragraph.A section consisting solely of dead dead constructs (statements or data elements) in the Configuration Section, this A file description entry (FD) containing ription.

A file section containing only dead file descriptions is a dead section.A SELECT statement referring to a dead file description is a dead construct.A file-control paragraph consisting solely of dead SELECT statements is a dead paragraph.An input-output section consistigraphs is a dead section.ta Elements from InclIncludes metrics.If a copybook is included multiple times, then each instance of the copybook is le, and all dead constructs and dead dead.

For instance, if a copybook is included twice and both inclusions result in Dead Lines from Includes=2 (assuming eachone line of the included copybook).If the same copybook is included twice but only one instance results in a dead data element, then Dead Data Elements from Includes=1 and Dead Lines from Includes=1.declarations, dead files, and instances ofOBOLROJECTIONSTATEMENTSNOTENot all language syntax phrases are represented in the HyperView model, contributing to dead lines can be identified using Clipper searches.In other words, Clipper can identify all dead data elements and application that represents the objects it uses and how they interact.This section The Cobol File object represents the source file for a Cobol program.The table member [OF library]Cobol File Includes Copybook FileFor resolved files: Copybook.Name = unresolved files: Copybook.Name = [ (Panvalet)++INCLUDE memberCobol File Includes Copybook FileFor resolved files: Copybook.Name = ; For unresolved files: Copybook.Name = [ memberCobol File Includes Copybook FileFor resolved files: Copybook.Name = ; For unresolved files: Copybook.Name = [ File Relationship ProjectionsThe Copybook File object represents a Cobol copybook.The table below describes the relationships generated from Cobol statements in the copybook.PROGRAM- PROGRAM-ID.nameCobol File Defines ProgramProgram.Name = nam&#x.300;&#x.700;e member [OF library]Copybook File Includes Copybook FileFor resolved files: Copybook.Name = ; For unresolved files: Copybook.Name = [ (Panvalet)++INCLUDE memberCopybook File Includes Copybook FileFor resolved files: Copybook.Name = ; For unresolved files: Copybook.Name = [ memberCopybook File Includes Copybook FileFor resolved files: Copybook.Name = ; For unresolved files: Copybook.Name = [ Program object represents a Cobol program.The table below describes the [FROM mnemonic-name]Program.OnlineFlag.= TrueCALLCALL

nameProgram Calls Program Entry PointProgramEntry.Name = Calls Program Entry Decision Decision attributes: Name = Known As = Type = PROGRAMENTRYENTRYENTRY nameProgram Has Program Entry PointProgramEntry.Name = nam.00;.00;e ProgramEntry.MainEntry = TruePROGRAM-IDPROGRAM-ID.name Program Has Program Entry PointProgramEntry.Name = nam.00;.00;e ProgramEntry.MainEntry = DescriptionSELECT file-name ASSIGN TO [label-][org-] nam.00;.00;e1 [assignment- name2]FD file-name.01 file-record-nameSee CRUD statements below.external-name = nam.00;.00;e1File attributes: Name = Name = external-file-nameFile Type = FILEA File object is generated only when the first CRUD statement for the file is encoun-tered.

File attributes do not depend on the CRUD statement itself.DELETEDELETE file-nameProgram Deletes From FileSee File Description for File attributes.READREAD file-nameProgram Reads FileSee File Description for File attributes.REWRITEREWRITE file-record-nameProgram Updates FileSee File Description for File attributes.WRITEWRITE file-record-nameProgram Inserts Into FileSee File Description for File This section describes MW support for EXEC SQL statements in programs and Support Notes on page 17 describes MW limitations, caveats, and special usage for SQL.Complexity Metrics on page 18 describes the supported complexity metrics for objects in the SQL model.Relationship Projections from EXEC SQL Statements on page 19 describes the relationships generated from EXEC SQL statements in programs.Relationship Projections from SQL DDL Statements on page 20 describes the relationships generated from SQL DDL statements in DDL files.These notes describe MW limitations, caveats, and special usage for SQL.Make support information.use DCLGEN include include files should rename the DCLGEN includes with a DCLGEN prefix and dot (.) separator, so that both types of file can be registered: ATTR.valid exten-, it first searches for OMPLEXITYETRICSNOTEwith a short name, the referencing source file will not be invalidated.

Its up to you source needs to be reverified.fficult it is to maintain, for objects in the SQL model.The table below describes object.MetricDescriptionBlank LinesNumber of blank lines of source (sequence number area content is ignored).ColumnsNumber of columns.Foreign KeysNumber of foreign keys.Lines with CommentsNumber of lines of source containing comments, including inline comments placed on lines with statements.Primary KeysNumber of primary keys.Source LinesNumber of lines of source, including blank lines and comments.TablesNumber of tables.ELATIONSHIP EXEC SQL STATEMENTSapplication that represents the objects it uses and how they interact.This section for SQL model objects from the EXEC SQL statements in programs.The Program object represents a Cobol program.

The table below describes the relationships generated from EXEC TABLEALTER TABLE Program Manipulates TableTable.Name = ;.
Rad14002 usen 00 cobol v41
\f""#?## @## =?## .=="(## ## ,! '#.;16?20A## +2/@2?C602@\t!60?0B@## ## ## 12C29=:2;A2;C6?;:2;A/.@21;)",.;1 6;BE3?.==960.A6;@12=9F21;)",.;1 ## .; "8'8+4,8.+68??425/1+6!60?0B@## @;## ## ## =?@@?)", ## 6;09B16;4'#'F;A.E.;1## ;@ !60?0B@## ?:## 6;BE\t!60?0B@## 0:/6;2@@B==?A3?:B9A6=92## ## !.
Tags: evaluate true in cobol,cobol write statement,cobol thru statement,cobol case statement,cobol evaluate or,
© 2013 Avenida classifieds             Sitemap   Privacy Policy - Contact