Use the Map CICS® VSAM Table wizard to map information from an existing
copybook to a new table for CICS VSAM.
The copybook from which you want to create a table must be listed
in the COBOL Copybooks folder in your data project.
You
can use each table that you create for queries on and updates to a VSAM file,
queries only, or for publishing changes that are mad to the file. You cannot
use one table for more than one of these functions.
Specify Location and COBOL Copybook page
Use this
page to select the database model and the schema that you want to create the
table in. Also, select the copybook on which to base the table.
- Database model
- Type the path and name of the database model in
which you want to create the table. For example, if your project is named
MyProject and your database model is named MyModel, type \MyProject\MyModel.
You can click Browse to select a database model.
- Copybook
- Type the path and name of the copybook on which
you want to base your table. For example, if your project is named MyProject
and your copybook is named copybook1, type \MyProject\copybook1.
You can click Browse to select a copybook that is located
on your filesystem.
- Schema name
- Select the schema in which you want to create
the table, or type a new schema.
- Select table usage
- Specify how the table will be used.
- Query
- Specifies that the table will be used for retrieving
data by Classic Federation.
- Update
- Specifies that the table will be used for updates
of data by Classic Federation.
- Change capture
- Specifies that the table will be used as a source
table for a publication or a subscription.
- Create view
- Use these controls to indicate whether you want to create a view on the
table.
- No
- Specifies that you do not want to create a view.
- Yes
- Specifies that you want to create a view on the table. This option allows
you to create a view for Classic federation. You can use the view to filter
record types and to filter rows and columns.
- Yes with change capture
- Specifies that you want to create a view on the table. This option allows
you to create a view for change capture. You can use the view to filter record
types and to filter rows. The view must reference all of the columns that
are in the table.
Specify CICS VSAM Information page
Use this page to
select an 01 level, to name the table, and to specify where to locate the
VSAM file.
- Select 01 level
- If the copybook has more than one 01 level, select
the 01 level that contains the elements that you want to map as columns in
the table.
- Table name
- Type a name for the table that you want to create.
By default, the wizard uses the name of the 01 level that you specify. You
can change this default.
- File control table (FCT)
- Type the name of the CICS table that contains the information
that is used by CICS file
control for accessing the VSAM file.
- Data server LUNAME
- Type an identifier of 1 to 8 characters for the
name of a local LU (logical unit) VTAM® LU 6.2 definition that is used by
the server to communicate with a CICS partner LU name (identified by CICS APPLID).
The data server LUNAME corresponds to either the ACBNAME or the name (label)
that is specified on the VTAM APPL definition. The data server LUNAME must be
active on the image where the data server is running. The data server LUNAME
follows VTAM naming
conventions. The LUNAME must also be defined to CICS as a CONNECTION definition.
- Sample local LU definitions are provided in SASCSAMP member CACCAPPL.
The sample data server LUNAME values are CACCICS1 and CACCICS2 and can be
modified.
- CICS APPLID
- Type an identifier of 1 to 8 characters for the VTAM LU
6.2 definition that a CICS region is listening on for connection requests.
This identifer corresponds to the value of the APPLID parameter that is specified
in the system initialization definition (DFHSIT macro) of the target CICS subsystem
where the VSAM file is located. This identifier follows VTAM naming conventions.
- Logmode
- Type a short identifier of 1 to 8 characters for
the name of the VTAM logon
mode table that is used to control the session parameters for the conversation
that is established between the local LU and the CICS LU. The logon mode table name corresponds
to a z/OS® load
module that is accessible to VTAM. The definition for a Classic supplied logon mode
table is supplied in SASCSAMP member CACCMODE.
- Transaction ID
- Type a short identifier of 1 to 4 characters for
the name of the supplied CICS transaction that is used for data access and validation
purposes. The CICS transaction
ID corresponds to the CICS TRANSACTION definition. Sample CICS transaction,
connection, program, and session definitions are supplied in SCACSAMP member
CACCDEF. The sample CICS transaction ID is EXV1 and can be modified.
- Network name
- Type a short identifier of 1 to 8 characters for
the name of the network where the CICS LUNAME resides, which corresponds
to the CICS subsystem
that is used to access a VSAM file. The network name is identified on the
NETWORK VTAM macro
definition on the local image to identify the remote SNA network where the CICS subsystem
resides. The network name follows VTAM naming conventions.
- Record exit
- Optional: Use these controls to pass control to a record exit for decompressing
sequential records. You can use record exits only for Classic federation.
- Exit name
- Type a short native identifier for the name of
a record processing exit to invoke to decompress sequential records when the
file is accessed. The exit must either exist in a data set that is referenced
by the server's STEPLIB DD statement or reside in the link pack area. The
exit name follows z/OS load module naming conventions.
- Maximum length
- Type the maximum length (in bytes) of the buffer
that is needed by the record exit to decompress a record.
Summary page
Use this page to verify the columns
of the table that will be created when you generate and run the DDL.
If
you are creating a view on the table, you can view the SELECT statement that
Classic Data Architect will base the view on.
You can click Finish to
generate the model for the table.