IBM Enterprise COBOL for z/OS

https://www.ibm.com/docs/en/cobol-zos/6.4.0
Admin
IBM Enterprise COBOL for z/OS is a compiler that enables the development, compilation, and execution...
Tokens:1,514,097
Snippets:11,307
Trust Score:10
Update:1 day ago
Show doc for...
Tokens:
Raw
### Batch compilation example with LANGUAGE option

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=compilation-example-language-option-in-batch

Shows the behavior of the LANGUAGE compiler option in a batch environment. The default installation option is ENGLISH (EN), and the invocation option is XX, a nonexistent language. The example includes multiple CBL statements and programs to illustrate how the language in effect changes.

```plaintext
CBL LANG(JP),FLAG(I,I),APOST  (1)
    IDENTIFICATION DIVISION.            (2)
    PROGRAM-ID.  COMPILE1.
    .  .  .
    END PROGRAM  COMPILE1. 
CBL LANGUAGE(YY)                        (3)
CBL LANGUAGE(JP),LANG(!!)   (4)
    IDENTIFICATION DIVISION.            (2)
    PROGRAM-ID.  COMPILE2.
    .  .  .
    END PROGRAM  COMPILE2.
    IDENTIFICATION DIVISION.
    PROGRAM-ID.  COMPILE3.
    .  .  .
    END PROGRAM  COMPILE3.
CBL LANGUAGE(JP),LANGUAGE(YY)           (5)
    .  .  . 
```

--------------------------------

### Example PDS path for --dlloutdir

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=java-cjbuild-command-reference

Example of a PDS path for the --dlloutdir option.

```plaintext
//COBOL.LOAD or //'USER.COBOL.LOAD'
```

--------------------------------

### IDENTIFICATION DIVISION example

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=program-identifying

Example of an IDENTIFICATION DIVISION with PROGRAM-ID, AUTHOR, INSTALLATION, DATE-WRITTEN, and DATE-COMPILED paragraphs. The DATE-COMPILED data is replaced with the latest compilation date.

```cobol
IDENTIFICATION DIVISION.
Program-ID.    Helloprog.
Author.        A. Programmer.
Installation.  Computing Laboratories.
Date-Written.  09/04/2019.
Date-Compiled. 09/08/2019.
```

--------------------------------

### Example INPUT-OUTPUT SECTION for a class instance method

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=method-input-output-section-defining-class-instance

Shows how to code the INPUT-OUTPUT SECTION in the ENVIRONMENT DIVISION of a class instance method, using a SELECT statement to associate a file-name with an external file. The syntax is the same as for a program.

```plaintext-ibm
Environment Division.
Input-Output Section.
File-Control.
    Select account-file Assign AcctFile.
```

--------------------------------

### Comment line example

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=structure-characters

Shows a comment line in COBOL, starting with an asterisk (*) in column 7.

```plaintext-ibm
* THIS IS COMMENT LINE. 
```

--------------------------------

### Compile with SOURCE and LIST options

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=cbrca6a-compiling-binding-amode-64-programs-under-zos-unix

Shows how to pass additional compiler options using -q with -q64.

```plaintext-ibm
cob2  -q64  -q"SOURCE,LIST"  hello.cbl
```

--------------------------------

### SET for procedure-pointer and function-pointer data items example

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=ss-format-6-set-procedure-pointer-function-pointer-data-items

Example showing how to assign entry points to a function-pointer (FP) and a procedure-pointer (PP) using the SET statement, then dynamically call the referenced subprograms. The example uses 'subp1' and 'subp2' as program names.

```plaintext-ibm
IDENTIFICATION DIVISION.
PROGRAM-ID DEMO.
DATA DIVISION.
WORKING-STORAGE SECTION.
01 FP USAGE FUNCTION-POINTER.
01 PP USAGE PROCEDURE-POINTER.

PROCEDURE DIVISION.
    SET FP to Entry "subp1"
    CALL FP
    SET PP to Entry "subp2"
    CALL PP
```

--------------------------------

### START statement for sequential reading

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=files-reading-records-from-vsam-file

Use this START statement to set the file position indicator to a specific record before reading sequentially with READ NEXT. The example uses KEY IS EQUAL TO ALTERNATE-RECORD-KEY.

```COBOL
START file-name KEY IS EQUAL TO ALTERNATE-RECORD-KEY
```

--------------------------------

### Example of listing header with build level

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=6-changes-in-compiling-enterprise-cobol-5

Shows the format of the compiler listing header, which includes the build level information (PYYMMDD) starting in Enterprise COBOL V6.1. The example shows the header for Enterprise COBOL 6.4.0.

```plaintext
PP 5655-EC6 IBM Enterprise COBOL for z/OS 6.4.0 PXXXXXX
```

--------------------------------

### Flexible input examples for NUMVAL

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=functions-converting-numbers-numval-numval-c-numval-f

Shows example input values that can be accepted when using NUMVAL, demonstrating the flexible format allowed.

```plaintext
1.23
-300
```

--------------------------------

### Shell script to run COBOL/Java interoperability demo

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=java-example-cobol-calls-application-building-running

This script sets up the environment for running the COBOL/Java interoperability demo. It requires STEPLIB and JAVA_HOME to be set, and it adds the user's COBOL.LOAD dataset to STEPLIB. It sets CLASSPATH, IBM_JAVA_OPTIONS, _CEE_RUNOPTS, and LIBPATH, then runs './prog1'. For Java 25.0 and above, uncomment the COBJVMINITOPTIONS line.

```shell
#!/bin/sh
###############################################################################
#
#  IBM Enterprise COBOL for z/OS                    
#               Version 6 Release 4 Modification 0
#
#  LICENSED MATERIALS - PROPERTY OF IBM.
#
#  5655-EC6 COPYRIGHT IBM CORP. 2022, 2026
#
#  US GOVERNMENT USERS RESTRICTED RIGHTS - USE,
#  DUPLICATION OR DISCLOSURE RESTRICTED BY GSA
#  ADP SCHEDULE CONTRACT WITH IBM CORP.
#
###############################################################################
###############################################################################
# Run script for the COBOL/Java interoperability demo
###############################################################################
#
# NOTE:
# -----
#
# 1) Make sure your STEPLIB includes an Enterprise COBOL runtime
#    that is sufficient to run programs compiled with the Enterprise
#    COBOL V6.4 or later compiler.
#
#    The dataset <USER>.COBOL.LOAD that received the program objects
#    and DLL for your interoperable application during the build
#    step must also be included in your STEPLIB.  We have added this
#    in automatically for you below.
#
# 2) Set JAVA_HOME to an appropriate 64-bit Java SDK:
#
#    e.g., JAVA_HOME=/usr/lpp/java/IBM/J8.0_64  or
#          JAVA_HOME=/usr/lpp/java/IBM/J11.0_64
#
###############################################################################

if [ -z $STEPLIB ]; then
  echo "STEPLIB environment variable must be set"
  exit 1
fi

if [ -z $JAVA_HOME ]; then
  echo "JAVA_HOME environment variable must be set"
  exit 1
fi

# ATTN: ensure the STEPLIB environment variable is set appropriately
export STEPLIB=${USER}.COBOL.LOAD:$STEPLIB
export CLASSPATH=.:./class:$CLASSPATH
export IBM_JAVA_OPTIONS="-XX:+Enable3164Interoperability"
export _CEE_RUNOPTS="POSIX(ON)"
export LIBPATH=.:${JAVA_HOME}/lib/s390x/j9vm:${JAVA_HOME}/lib/s390x/:${JAVA_HOME}/lib:${JAVA_HOME}/lib/j9vm:${LIBPATH}

# Java 25.0 and above only
#export COBJVMINITOPTIONS="--enable-native-access=ALL-UNNAMED ${COBJVMINITOPTIONS}"

./prog1

```

--------------------------------

### Example 2: Reference modification with all single-byte characters

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=cobol-reference-modifiers-utf-8-data-items

Shows that u1(3:2) starts at character position 3, which is the 3rd byte because all characters have 1-byte encodings.

```COBOL
01 u1 pic u(10) value u'ecran'.
:
display u1(3:2)
```

--------------------------------

### Example: Partitioning SQLIMS suboptions across multiple CBL statements

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=options-sqlims

Shows how to specify SQLIMS suboptions in multiple CBL statements, which are concatenated in order. The example uses a JCL step and two CBL statements with suboption strings.

```plaintext
//STEP1 EXEC IGYWC, . . .
// PARM.COBOL=’SQLIMS("string1")’
//COBOL.SYSIN DD *
       CBL SQLIMS("string2")
       CBL SQLIMS(’string3’)
       IDENTIFICATION DIVISION.
       PROGRAM-ID. DRIVER1.
       . . .
```

--------------------------------

### COBOL get method example: getBalance in Account class

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=methods-example-coding-get-method

Defines the getBalance instance method in the Account class to return the AccountBalance instance variable. The method uses a linkage section to return the balance to the client. The example shows the class structure with the OBJECT paragraph and the method definition.

```plaintext-ibm
 Identification Division.
 Class-id. Account inherits Base.
*  (ENVIRONMENT DIVISION not shown)
*  (FACTORY paragraph not shown)
*
 Identification division.
 Object.
  Data division.
  WORKING-STORAGE SECTION.
  01 AccountBalance pic S9(9) value zero.
*   (Other instance data not shown) 
*
  Procedure Division.
*
   Identification Division.
   Method-id. "getBalance".
   Data division.
   Linkage section.
   01 outBalance pic S9(9) binary.
*
   Procedure Division returning outBalance.
     Move AccountBalance to outBalance.
   End method "getBalance".
*
*  (Other instance methods not shown)
 End Object.
*
 End class Account.
```

--------------------------------

### Example: Concatenated suboption string passed to IMS SQL coprocessor

Source: https://www.ibm.com/docs/en/cobol-zos/6.4.0?topic=options-sqlims

Shows the resulting concatenated suboption string from the previous example, with single spaces between suboptions.

```plaintext
"string1 string2 string3"
```
Tokens:
Raw