PK
$Aoa, mimetypeapplication/epub+zipPK $A iTunesMetadata.plistn
Before performing any of the tasks described in this part, you should read Part I, "Getting Started with Oracle Database Gateways" to get an overview of the technology, the architecture, and the process involved in installing and configuring a database gateway.
To be able to access legacy data, you need to perform the tasks described in the following list, in the specified order. Each step in the list directs you to the relevant manual or chapter.
By now, you should have completed tasks 1 and2. This part describes how to perform task 3.
Install Oracle Connect for IMS, VSAM, and Adabas Gateways
See Oracle Connect for IMS, VSAM, and Adabas Gateways Installation and Configuration Guide for IBM z/OS for information on installing Oracle Connect for IMS, VSAM, and Adabas Gateways.
Install Oracle Studio for IMS, VSAM, and Adabas Gateways
See Chapter 11, "Installing Oracle Studio for IMS, VSAM, and Adabas Gateways" for information on installing Oracle Studio for IMS, VSAM, and Adabas Gateways.
Configure Oracle Connect for IMS, VSAM, and Adabas Gateways
See Chapter 13, "Configuring Oracle Connect through Oracle Studio for IMS, VSAM, and Adabas Gateways" for information on configuring Oracle Connect for IMS, VSAM, and Adabas Gateways.
Set up the connection to Oracle Connect for IMS, VSAM, and Adabas Gateways
See the relevant topic in any of the following chapters:
Set up the VSAM, IMS, or Adabas data source
See the relevant topic in any of the following chapters:
Set up the data source metadata
See the following chapters for additional information:
Install Oracle Database Gateway for VSAM, IMS, or Adabas
See the following chapters for additional information:
Configure Oracle Database Gateway for IMS
See the following chapters for additional information:
Part V, "Installing Oracle Studio for IMS, VSAM, and Adabas Gateways," describes how to install Oracle Studio for IMS, VSAM, and Adabas Gateways and use it to configure and manage Oracle Connect for IMS, VSAM, and Adabas Gateways.
It contains the following chapters:
Chapter 11, "Installing Oracle Studio for IMS, VSAM, and Adabas Gateways"
Chapter 12, "Working with the Oracle Studio for IMS, VSAM, and Adabas Gateways Workbench"
Chapter 13, "Configuring Oracle Connect through Oracle Studio for IMS, VSAM, and Adabas Gateways"
Chapter 14, "Managing Security for Oracle Connect for IMS, VSAM, and Adabas Gateways"
This chapter contains the following sections:
Heterogeneous data access is a problem that affects a lot of companies. A lot of companies run several different database systems. Each of these systems stores data and has a set of applications that run against it. Consolidation of this data in one database system is often hard—in large part because many of the applications that run against one database may not have an equivalent that runs against another. Until such time as migration to one consolidated database system is made feasible, it is necessary for the various heterogeneous database systems to interoperate.
Oracle Database Gateways provide the ability to transparently access data located in a non-Oracle system from an Oracle environment. This transparency eliminates the need for application developers to customize their applications to access data from different non-Oracle systems, thus decreasing development efforts and increasing the mobility of the application. Applications can be developed using a consistent Oracle interface for both Oracle and VSAM, IMS, or Adabas.
Gateway technology is composed of two parts: a component that has the generic technology to connect to a non-Oracle system, which is common to all the non-Oracle systems, called Heterogeneous Services, and a component that is specific to the non-Oracle system that the gateway connects to. Heterogeneous Services, in conjunction with the Database Gateway agent and Oracle Connect for IMS, VSAM, and Adabas Gateways, enables transparent access to non-Oracle systems from an Oracle environment.
Heterogeneous Services provides the generic technology for connecting to non-Oracle systems. As an integrated component of the database, Heterogeneous Services can exploit features of the database, such as the powerful SQL parsing and distributed optimization capabilities.
Heterogeneous Services extends the Oracle SQL engine to recognize the SQL and procedural capabilities of the remote non-Oracle system and the mappings required to obtain necessary data dictionary information. Heterogeneous Services provides two types of translations: the ability to translate Oracle SQL into the proper dialect of the non-Oracle system and the ability to handle data dictionary translations so that the metadata of the non-Oracle system is displayed in the local format. For situations where no translations are available, native SQL can be issued to the non-Oracle system using the pass-through feature of Heterogeneous Services.
Heterogeneous Services also maintains the transaction coordination between Oracle and the remote non-Oracle system, such as providing the global transaction protocol to ensure distributed transaction integrity, even for non-Oracle systems that do not natively support global transactions.
See Also: Oracle Database Heterogeneous Connectivity User's Guide for more information about Heterogeneous Services. |
Oracle Database Gateways for IMS, VSAM, and Adabas allow Oracle client applications to access IMS, VSAM, and Adabas data through Structured Query Language (SQL). The gateway, with the Oracle database server, creates the appearance that all data resides on a local Oracle database server, even though data might be widely distributed. If data is moved from these data sources to an Oracle database, no changes in the client application's design or function are needed because the gateway handles all differences in data types or SQL functions between the applications and the database.
Using Oracle SQL, Oracle client applications can access data sources such as IMS, VSAM, and Adabas as if the data was stored in an Oracle table. A single SQL statement can access data residing in Oracle and VSAM, IMS, or Adabas data sources, performing heterogeneous joins and subselects. This means that you can develop one set of portable applications to use against Oracle and these non-relational data sources. You can continue to develop new information systems without losing your investment in existing data and applications.
Transactions updating Oracle and these non-relational data sources are automatically protected by the Oracle global transactions feature. Use of synonyms is another Oracle feature. By setting up synonyms in the Oracle database server that point to database links to VSAM, IMS, or Adabas files, the physical location of the data is transparent to the client application. This allows future migration of data from the VSAM, IMS, or Adabas data source to Oracle to be transparent to the client applications.
The gateway requires the Oracle database server, Oracle Connect for IMS, VSAM, and Adabas Gateways, and Oracle Studio for IMS, VSAM, and Adabas Gateways. All other Oracle products are optional. However, using other Oracle products with the gateway can greatly extend the gateway's capabilities.
The gateway can be installed on a computer where the Oracle database is installed, or on a second, standalone system. Each configuration has its advantages and disadvantages. The issues to consider when you determine where to install the gateway are network traffic, availability of the operating system platform, hardware resources, and storage.
Oracle Connect for IMS, VSAM, and Adabas Gateways must be installed on the z/OS system where the VSAM, IMS, or Adabas data source is installed. To be able to configure and manage Oracle Connect for IMS, VSAM, and Adabas Gateways, you need to install Oracle Studio for IMS, VSAM, and Adabas Gateways on a computer running Windows or Linux.
The gateway is invoked by the listener. The gateway is not multi-threaded and cannot support shared database links. Each gateway session spawns a separate gateway process, and connections cannot be shared.
The gateway is located on a Windows or UNIX computer. The non-relational data source resides on a computer running IBM z/OS. The Oracle database server can reside on the same system as the gateway or on another system.
The gateway interacts with the Oracle database server to interface between client applications and the VSAM, IMS, or Adabas data source, as shown in Figure 1-1.
Note: The non-Oracle system in Figure 1-1 and Figure 1-2 represents the VSAM, IMS, or Adabas data source. |
Client applications, such as Developer, connect to the Oracle database server by using Oracle Net.
The Oracle database server, which includes Heterogeneous Services and the database itself, resides on a single system. This Oracle database server also stores definitions of database links for the non-Oracle system.
The gateway to VSAM, IMS, and Adabas resides on a second system.
The VSAM, IMS, or Adabas data source, together with Oracle Connect for IMS, VSAM, and Adabas Gateways, resides on a third system, which is an IBM z/OS platform.
Oracle Studio for IMS, VSAM, and Adabas Gateways, which is used to configure Oracle Connect for IMS, VSAM, and Adabas Gateways, resides on a fourth system, which can be running a Windows or Linux operating system.
The Oracle database server on the first system uses Oracle Net to connect directly to the VSAM, IMS, or Adabas gateway on the second system. The gateway itself uses the Oracle Connect for IMS, VSAM, and Adabas Gateways protocol to connect to Oracle Connect for IMS, VSAM, and Adabas Gateways, which then connects to the non-Oracle system using the same protocol.
The Oracle database server and the gateway work together to present the appearance of a single Oracle database to the client. All data accessed by the client appears to reside in a single Oracle database. The client application sends a request to the Oracle database server, and the Oracle database server sends the request to the gateway.
For the first transaction in a session, the gateway logs into the VSAM, IMS, or Adabas data source using a username and password that is valid in the respective data source. The gateway converts the SQL statement to a native VSAM, IMS, or Adabas statement, and the VSAM, IMS, or Adabas data source performs the request. The gateway converts the retrieved data to a format compatible with the Oracle database server and returns the results to the Oracle database server, which returns the results to the client application.
Figure 1-2 shows a typical gateway process flow. The steps explain the sequence of the events that occurs when a client application queries the VSAM, IMS, or Adabas data source through the gateway.
The client application sends a query over Oracle Net to the Oracle database server.
The Oracle database server sends the query over to the gateway, again using Oracle Net.
The gateway passes the query on to Oracle Connect for IMS, VSAM, and Adabas Gateways.
For the first transaction in a session, Oracle Connect for IMS, VSAM, and Adabas Gateways logs into the VSAM, IMS, or Adabas data source using a user name and password that is valid in the respective data source.
Oracle Connect for IMS, VSAM, and Adabas Gateways converts the Oracle SQL statement into a data access operation understood by the data source.
Oracle Connect for IMS, VSAM, and Adabas Gateways retrieves the data.
Oracle Connect for IMS, VSAM, and Adabas Gateways converts the retrieved data into a format compatible with the Oracle database server.
Oracle Connect for IMS, VSAM, and Adabas Gateways passes the data to the gateway using the Oracle Connect for IMS, VSAM, and Adabas Gateways protocol.
The gateway returns the query results to the Oracle database server, again using Oracle Net.
The Oracle database server passes the query results to the client application by using Oracle Net. The database link remains open until the gateway session is finished or the database link is explicitly closed.
To be able to access VSAM, IMS, or Adabas data, you need to perform the tasks described in the following list, in the specified order. Each step in the list directs you to the relevant manual or chapter.
Install Oracle Connect for IMS, VSAM, and Adabas Gateways
See: Oracle Connect for IMS, VSAM, and Adabas Gateways Installation and Configuration Guide for IBM z/OS for information on installing Oracle Connect for IMS, VSAM, and Adabas Gateways |
Install Oracle Studio for IMS, VSAM, and Adabas Gateways
See: Chapter 11, "Installing Oracle Studio for IMS, VSAM, and Adabas Gateways" for information on installing Oracle Studio for IMS, VSAM, and Adabas Gateways |
Configure Oracle Connect for IMS, VSAM, and Adabas Gateways
See: Chapter 13, "Configuring Oracle Connect through Oracle Studio for IMS, VSAM, and Adabas Gateways" for information on configuring Oracle Connect for IMS, VSAM, and Adabas Gateways |
Set up the connection to Oracle Connect for IMS, VSAM, and Adabas Gateways
See: Relevant topic in any of the following chapters: |
Set up the VSAM, IMS, or Adabas data source
See: Relevant topic in any of the following chapters: |
Set up the data source metadata
Install Oracle Database Gateway for VSAM, IMS, or Adabas
Configure Oracle Database Gateway for VSAM, IMS, or Adabas
This chapter explains how to configure access to VSAM data by using Oracle Studio for IMS, VSAM, and Adabas Gateways. It contains the following sections:
To be able to access VSAM data, you must have a working connection to Oracle Connect for IMS, VSAM, and Adabas Gateways, which is installed on the IBM z/OS computer where your VSAM files are located. You establish this connection by using Oracle Studio for IMS, VSAM, and Adabas Gateways.
Whenever needed, you can also use Oracle Studio for IMS, VSAM, and Adabas Gateways to configure Oracle Connect for IMS, VSAM, and Adabas Gateways.
Note: The following task assumes that you have permission to access the IBM z/OS platform and that the Oracle Connect for IMS, VSAM, and Adabas Gateways daemon is running on this computer. Check with the system administrator to ensure these requirements are fulfilled. |
Perform the following steps to set up access to a computer that runs Oracle Connect for IMS, VSAM, and Adabas Gateways.
From the Start menu, select Programs, point to Oracle, and select Studio. Oracle Studio for IMS, VSAM, and Adabas Gateways opens.
In the Design perspective's Configuration view, right-click the Machines folder and select Add Machines.
The Add machine screen opens, as shown in Figure 2-1.
Enter the following information in each field:
Host name/IP address: Enter the name of the computer on the network or click Browse, to browse all the systems running a daemon listener on the specified port currently accessible over the network.
Port: Enter the port number where the daemon is running. The default port is 2551.
Display name: Enter an alias used to identify the system when different from the host name (optional).
User name: Enter the system administrator's user name.
Note: You indicate the system administrator when the system is installed or by using the NAV_UTIL utility ADD_ADMIN operation. For details, see Oracle Connect for IMS, VSAM, and Adabas Gateways Installation and Configuration Guide for IBM z/OS. |
Password: Enter the system administrator's password. This is the password for the user entered in the User name field. If no password is necessary to access this system, do not enter anything.
Connect via NAT with fixed IP address: Select this if the system uses the NAT (Network Address Translation) firewall protocol, with a fixed configuration, mapping each external IP to one internal IP, regardless of the port specified.
Click Finish.
The computer is displayed in the Configuration view, in the Machine folder. You can edit the system's login information, or configure bindings, daemons, and users for each system.
Oracle Connect for IMS, VSAM, and Adabas Gateways supports the following types of VSAM data sources:
VSAM (CICS): The VSAM under CICS data source accesses VSAM by making calls from the external CICS interface (EXCI) to a CICS program that is provided as part of the Oracle Connect for IMS, VSAM, and Adabas Gateways installation. This CICS program does the actual VSAM reads and writes from within CICS.
When you access VSAM data using this data source, the following restrictions apply:
SQL DELETE operations are not supported for ESDS files.
Using an alternate index to access an entry sequenced data set (ESDS) file is not supported.
A non-unique alternate index for a key sequenced data set (KSDS) file is not supported.
VSAM/Batch: This data source connects directly to the VSAM data and is limited if the VSAM files are managed by CICS. In this case, it is recommended to use this data source for read-only access to VSAM files. However, this may not give you adequate read integrity if some changes are buffered by CICS. Another alternative is to use the VSAM under CICS data source.
When you access VSAM data using the VSAM data source, the following restrictions apply:
Transactions are not supported when you access VSAM directly. When you access VSAM under CICS, global transactions are supported.
Locking is not supported.
You cannot update an array value (a child record in a hierarchical table) when the parent record is included in the SQL in a subquery.
SQL DELETE operations are not supported for ESDS files.
A relative record data set (RRDS) file cannot have an alternate index.
The primary key of a KSDS file must be one segment only (however, it can be several consecutive fields). You cannot modify the primary key value of a KSDS file.
This section describes how to set up a VSAM data source using Oracle Studio for IMS, VSAM, and Adabas Gateways. It includes the following tasks:
Perform the following steps to define the connection to the VSAM data source.
In Oracle Studio for IMS, VSAM, and Adabas Gateways, in the Configuration view of the Design perspective, open the binding of the system where the data is located.
Right-click Data Source and select New Data Source.
The New Data Source screen opens, as shown in Figure 2-2.
Specify a name for the data source in the Name field.
Note: The name you assign to each data source that you define must be noted and used consistently throughout all phases of the gateway configuration. |
From the Type list, select VSAM and click Next.
Click Next.
Specify the connect string as follows:
Data HLQ
: The high-level qualifier where the data files are located.
Disk Volume Name
: The high-level qualifier (volume) where the data is located.
The values specified are used in the Data File field in the Oracle Studio for IMS, VSAM, and Adabas Gateways Design Perspective Metadata tab. For tables created using the CREATE TABLE
statement, the values specified are used to create the data files. If values are not specified, then data files are written to the DEF high-level qualifier under the high-level qualifier where Oracle Connect for IMS, VSAM, and Adabas Gateways is installed.
When SMS is used to manage the volumes, leave this value empty and set the newFileSMSStorageClass
and newFileSMSDataClass
properties as described in VSAM Data Source Parameters.
Click Finish.
Perform the following steps to define the connection to the VSAM (CICS) data source:
In Oracle Studio for IMS, VSAM, and Adabas Gateways, in the Configuration view of the Design perspective, open the binding of the system where the data is located.
Right-click Data Source and select New Data Source.
The New Data Source screen opens, as shown in Figure 2-3.
Specify a name for the data source in the Name field.
From the Type list, select VSAM (CICS) and click Next.
The Data Source Connect String screen is displayed.
Specify the connect string as follows:
CICS Application ID
: VTAM applID of the CICS target system. The default value is CICS. This parameter is used when updating VSAM data. You can determine this value by activating the CEMT transaction on the target CICS system. In the bottom right corner of the screen appears the legend APPLID=target_system
.
Transaction ID
: The mirror transaction within CICS that receives control through MRO, which transfers the transaction from the Oracle Connect for IMS, VSAM, and Adabas Gateways environment to CICS. The default value is EXCI.
VTAM Netname
: The VTAM netname of the specific connection being used by EXCI (and MRO) to relay the program call to the CICS target system. For example, if you issue the following command to CEMT:
CEMT INQ CONN
Then you see on the display screen that the netname is BATCHCLI (this is the default connection supplied by IBM upon the installation of CICS). The default value is ATYCLIEN.
If you plan to use the IBM defaults, specify BATCHCLI as the VTAM_netname
parameter, otherwise define a specific connection (with EXCI protocol) and use the netname you provided there for this parameter.
Oracle provides a netname, ATYCLIEN that can be used after the following procedure is followed:
Either, use the JCL in the NAVROOT.USERLIB(CICSCONF)
member to submit the DFHCSDUP
batch utility program to add the resource definitions to the DFHCSD dataset (see the IBM CICS Resource Definition Guide for further details).
or:
Use the instream SYSIN control statements in the NAVROOT.USERLIB(CICSCONF)
member as a guide to defining the resources online using the CEDA facility.
After the definitions have been added (through batch or using the CEDA facility), logon to CICS and issue the following command to install the resource definitions under CICS:
CEDA INST GROUP(ATYI)
Henceforth, specify ATYCLIEN
as the NETNAME.
Program Name
: The UPDTRNS program that is supplied with Oracle Connect for IMS, VSAM, and Adabas Gateways to enable updating VSAM data. To use the UPDTRNS program, copy the program from NAVROOT.LOAD
to a CICS DFHRPL library (such as CICS.USER.LOAD
) and then define the UPDTRNS
program under CICS using any available group:
CEDA DEF PROG(UPDTRNS) G(group_name) LANG(C) DA(ANY) DE(ATTUNITY VSAM UPDATE PROG)
NAVROOT is the high-level qualifier where Oracle Connect for IMS, VSAM, and Adabas Gateways is installed.
After defining the UPDTRNS program, install it as follows:
CEDA IN G(group_name)
Trace Queue
: The name of the queue for output that is defined under CICS when tracing the output of the UPDTRNS
program. When not defined, the default CICS queue is used.
Click Finish.
After defining the connection to the VSAM (CICS) data source, perform the following steps to configure the data source properties.
In Oracle Studio for IMS, VSAM, and Adabas Gateways, in the Configuration view of the Design perspective, right-click the data source and select Edit Data Source.
In the editor, on the Properties tab, configure the data source parameters as required. For a description of the available parameters, see "VSAM Data Source Parameters" or "VSAM (CICS) Data Source Parameters".
If you want to configure VSAM (CICS) to support rollback, on the Advanced tab, from the Transaction type list, select 1PC or 2PC, depending on the data source usage.
If you do not use 2PC, see the Oracle Database Heterogeneous Connectivity User's Guide for configuration information.
On the Advanced tab, configure how arrays will be handled by selecting the relevant check boxes in the Virtual View Policy section. The following options are available:
Generate sequential view: Select this option if you want to map a non-relational file to a single table.
Generate virtual views: Select this option if you want to have an individual table created for every array in the non-relational file.
Include row number column: Select this option if you want to include a column that specifies the row number in the virtual or sequential view.
Inherit all parent columns: Select this option if you want the virtual views to include all the columns of the parent record.
Save your settings.
The following parameters can be configured for VSAM data sources in the Properties tab of the Configuration Properties screen:
disableExplicitSelect=true|false
: When set to true
, this parameter disables the ExplicitSelect ADD
attribute; every field is returned by a SELECT * FROM...
statement.
filepoolCloseOnTransaction=true|false
: This parameter specifies that all files in the file pool for this data source close at the end of each transaction (commit or rollback).
filepoolSize=n
: This parameter specifies how many instances of a file from the file pool may be open concurrently.
newFileLocation=string
: This parameter is the Data HLQ in the connect string that specifies the high-level qualifier for the file.
newFileSMSStorageClass=string
: This parameter specifies the storage class when SMS is used to manage volumes.
newFileSMSDataClass=string
: This parameter specifies the data class when SMS is used to manage volumes.
newFileVolume=string
: This parameter specifies the file volume where the file is catalogued (data disk in the connect string).
useGlobalFilepool=true|false
: This parameter specifies whether or not a global file pool that can span more than one session is used.
The following parameters can be configured for VSAM (CICS) data sources in the Properties tab of the Configuration Properties screen:
allowUpdateKey=true|false
: When set to true
, this parameter specifies that the key is updatable.
cicsProgname=string
: The ProgramName
in the connect string, this parameter specifies the UPDTRNS program that is supplied with Oracle Connect for IMS, VSAM, and Adabas Gateways to enable updating VSAM data.
cicsTraceQueue=string
: The TraceQueue
in the connect string, this parameter indicates the name of queue for output that is defined under CICS when tracing the output of the UPDTRNS program. When not defined, the default CICS queue is used.
disableExplicitSelect=true|false
: When set to true
, this parameter disables the ExplicitSelect ADD
attribute; every field is returned by a SELECT * FROM...
statement.
exciTransid=string
: The Transaction ID in the connect string, this parameter indicates the CICS TRANSID
. This value must be EXCI or a copy of this transaction.
targetSystemApplid=string
: The CICS Application ID in the connect string, this parameter specifies the VTAM applid
of the CICS target system.
TransactionType=true|false
: When set to true
, this parameter specifies that the key is updatable.
vtamNetname=string
: The VTAM Netname in the connect string, this parameter specifies the connection being used by EXCI (and MRO) to relay the program call to the CICS target system.
Defining VSAM metadata by using the Import Manager of Oracle Studio for IMS, VSAM, and Adabas Gateways requires a COBOL copybook that contains the COBOL definition of the VSAM records.
If the metadata is provided in a number of COBOL copybooks with different filter settings, such as whether the first 6 columns are ignored or not (see Apply Filters), first import the metadata from copybooks with the same settings, and then import the metadata from the other copybooks.
The import process includes the following tasks:
This section describes the steps required to import the COBOL copybooks that will be used to generate the metadata. You can import new copybooks or use copybooks that you already imported earlier.
To import new copybooks, perform the following procedure.
In the Configuration view, right-click the data source and select Edit Metadata.
The Metadata tab is displayed with the data source displayed in the Metadata view.
Right-click the Imports node under the data source and select New Import.
The Metadata Import screen opens, as shown in Figure 2-4:
Enter a name for the import. The name can contain letters, numbers and the underscore character.
Select VSAM Import Manager or VSAM Under CICS Import Manager as the import type as required.
Click Finish.
The Metadata import wizard opens with the Get Input Files screen, as shown in Figure 2-5:
Click Add.
The Add Resource screen opens, as shown in Figure 2-6:
If the files are located on another computer, do any of the following:
Right-click My FTP Sites and select Add.
The Add FTP Site screen opens, as shown in the following figure.
Enter the server name where the COBOL copybooks are located and, if not using an anonymous connection, enter a valid username and password to access the computer. The username is then used as the high-level qualifier.
Click OK. After accessing the remote computer, you can change the high-level qualifier by right-clicking the system in the Add Resource screen and selecting Change Root Directory.
Select the files to import and click Finish to start the file transfer. When complete, the selected files are displayed in the Get Input Files screen.
To remove any of these files, select the required file and click Remove.
Click Next.
The Apply Filters screen opens (see Apply Filters).
To use copybooks that you imported earlier, perform the following procedure.
In the Configuration view, right-click the data source and select Edit Metadata.
The Metadata tab is displayed with the data source displayed in the Metadata view.
Expand the Imports node under the data source, right-click the existing import, and select Open.
The Metadata import wizard opens with the Get Input Files screen, showing the copybooks that you imported.
Click Next.
The Apply Filters screen opens (see Apply Filters).
This section describes the steps required to apply filters on the COBOL copybooks used to generate the Metadata. It continues the Import the COBOL Copybooks procedure. Perform the following procedure.
Expand all nodes in the Apply Filters screen.
Apply the required filter attributes to the COBOL copybooks.
The following table describes the available filters.
Filter | Description |
---|---|
COMP_6 switch |
The MicroFocus COMP-6 compiler directive. Specify either COMP-6'1' to treat COMP-6 as a COMP data type or COMP-6'2' to treat COMP-6 as a COMP-3 data type. |
Compiler source |
z/OS |
Storage mode |
The MicroFocus Integer Storage Mode. Specify one of the following:
|
Ignore after column 72 |
When set to |
IgnoreFirst6 |
When set to |
Replace hyphens (-) in record and field names with underscores (_) |
When set to |
Prefix nested columns |
When set to |