|Skip Navigation Links|
|Exit Print View|
|Oracle Java CAPS COBOL Copybook Encoder User's Guide Java CAPS Documentation|
The COBOL Copybook Encoder converts copybook descriptions, and creates schema definitions designed to encapsulate data conforming to the description. The encoder can generate the schema definition based on a copybook file.
Copybooks are common fragments of code that are typically distributed throughout a software application. They are functionally similar to the #include file of a C or C++ application, and mainframes reference these books and call structures as needed. They are usually stored in a source library file. When integrating mainframe applications with other platforms, it is necessary to retrieve and generate the data structure of the copybook. Without the copybook's data structure, disparate applications cannot communicate with each other and data cannot be transferred between applications and platforms. Copybook documents use a fixed-length field encoding mechanism.
The COBOL Copybook Encoder allows you to handle data encoded in COBOL copybook format in a JBI application. With the encoder, you can create JBI applications that can read or send data in copybook format, connecting mainframe applications to applications running on other platforms. The COBOL Copybook Encoder definition is represented by an XSD file and is used in the WSDL document to define the encoding. The encoding style is specified in the WSDL document's binding element. The encoding style for COBOL copybook is cocoencoder-1.0.
The COBOL Copybook Encoder is part of a larger framework of custom encoders provided with Java CAPS. A standard encoder is a bidirectional software component that transforms an XML message into a non-XML message, or the other way around. In this case, it encodes data from XML to copybook, and from copybook to XML. For more information about custom encoders, see the Oracle Java CAPS Custom Encoders User’s Guide.
The content of the COBOL copybook, compliant with the IBM COBOL Reference standard, does not go past column 72. To process a copybook that contains data beyond column 72 (that is, content that is not line numbering or comments, which should be ignored), you need to specify not to ignore the content when you create the XSD file for the copybook document.
Caution - It is still possible for a copybook with data beyond the 72nd column to process successfully if you choose to ignore the extra content. However, the data may not be process correctly.