COBOL Clause |
Allowed as Input to Transaction Designer? |
Comments |
BLANK WHEN ZERO |
Yes |
-- |
COPY |
No |
Insert referenced files manually. |
DATE FORMAT |
Yes |
Two particular formats, DATE FORMAT YYYYXXXX, and DATE FORMAT XXXXYYYY, are converted to the built-in datatype xsd:date as defined in W3C XML Schema Datatypes. In this year-2000 COBOL enhancement, YYYY is the year; XXXX is the month and day-of-the-month. All other COBOL date formats are converted to an integer representation, not datatype xsd:date. |
EXTERNAL |
No |
Cannot be used in the linkage area. |
GLOBAL |
No |
Not relevant to Transaction Designer for CICS. |
JUSTIFIED |
Yes |
-- |
OCCURS |
Yes |
Supported for fixed-length tables. ASCENDING and INDEXED BY phrases are ignored. Also supported for variable-length tables, as indicated by the OCCURS DEPENDING ON phrase. See Using an OCCURS DEPENDING ON Clause. |
PICTURE |
Yes |
G and N picture symbols are not supported. B picture symbol is supported only for non-DBCS (Double-Byte Character Set) data. |
REDEFINES |
Yes |
See Using a REDEFINES Clause. |
RENAMES |
No |
Level 66 items. |
SIGN |
Yes |
-- |
SYNCHRONIZED |
No |
-- |
USAGE |
Yes |
Supported data types are BINARY, COMP, COMP-1, COMP-2, COMP-3, COMP-4, DISPLAY (the default), and PACKED. The machine-dependent DISPLAY-1 and COMP-5 data types are not supported, nor are POINTER, PROCEDURE-POINTER, NATIONAL, OBJECT REFERENCE, nor INDEX. |
VALUE |
Yes |
When coded on host transaction input elementary data items, the associated value of this clause is used as the "Default" value during runtime. Client operation fields mapped to the item will send the value to the host if the client does not specify a non-null input value for the field during runtime. When coded on a level 88 statement, the value specified is associated with the "Condition Name" of the level 88 statement as indicator values. This information is available in the Javadocs when a resulting client operation is exposed with the task bean interface. |