Configuring the Adapter for DATACOM

In this section:

You configure the Adapter for DATACOM from the Web Console.


Top of page

x
Declaring Connection Attributes

How to:

Reference:

Users accessing the DATACOM DBMS are authenticated by the Operating System security package, as well as any authentication performed by the DBMS itself.

Note: The Adapter for DATACOM uses the connection attributes declaration only for synonym creation purposes.



x
Procedure: How to Declare Connection Attributes

You can configure the adapter from either the Web Console or the Data Management Console.

  1. From the Web Console menu bar, click Adapters.

    or

    From the Data Management Console, expand the Adapters folder.

    The Adapters folder opens.

  2. Expand the Available folder, if it is not already expanded.
  3. Expand the appropriate group folder and the specific adapter folder. The group folder is described in the connection attributes reference.
  4. Right-click the adapter name and/or version and select Configure.

    The Add Adapter to Configuration pane opens.

  5. Enter values for the parameters required by the adapter, as described in the connection attributes reference.
  6. Click Configure. The configured adapter is added to the Adapters list in the navigation pane.


x
Reference: Connection Attributes for DATACOM

The DATACOM adapter is under the DBMS group folder.

The following list describes the connection attributes for which you can supply values. To complete the attribute declaration, click the Configure button.

Connection Name

Is the logical name used to identify this particular set of attributes.

You can establish multiple connections to a Datacom data source. However, the first connection_name must define the DBID of the Datacom data dictionary, which is required as the source for Create Synonym processing.

DBID

Database ID.

For the first connection, you must specify the Data Dictionary ID.

User Table

A User Requirements Table contains all tables that an application can access. Enter a valid User Table name for access to the Datacom database with the current DBID.

For the Datacom data dictionary, this is AUTOURT.

Note that sample JCL is shipped with the product for your use in preparing the DATACOM Environment. This JCL generates the User Requirements Table, AUTOURT.

Trace

Select from the drop-down list:

CBS

Sets the accumulation of Compound Boolean Selection (CBS) diagnostics to the DATACOM diagnostics file (PXX) by making "$$$" the first 3 bytes of the User Information Block for each Datacom command.

NO

Indicates no trace. NO is the default value.

The parameter is optional.

Skipselect

Select from the drop-down list:

NO

Provides access to the root segment as stipulated in the request. This value is the default.

YES

Provides sequential access to the root segment in the Access File even if logical criteria exist for the segment.

However, if a join connection has been defined to the root segment, a selection command is used.

The parameter is optional.

Select profile

Select a profile from the drop-down list to indicate the level of profile in which to store the CONNECTION_ATTRIBUTES command. The global profile, edasprof.prf, is the default.

If you wish to create a new profile, either a user profile (user.prf) or a group profile if available on your platform (using the appropriate naming convention), choose New Profile from the drop-down list and enter a name in the Profile Name input box. (The extension is added automatically).



x
Syntax: How to Declare Connection Attributes Manually
ENGINE DATACOM SET CONNECTION_ATTRIBUTES connection_name /, ; 
dbid: "USERTABLE urt_name [TRACE {CBS|NO}] [SKIPSELECT {YES|NO}]"

where:

connection_name

Is the logical name used to identify as particular set of attributes.

The connection_name that defines the DBID of the DATACOM data dictionary must be used as the source for Create Synonym processing.

dbid

Database ID.

For the first connection, you must specify the Data Dictionary ID.

urt_name

A User Requirements Table contains all tables that an application can access. Enter a valid User Table name for access to the DATACOM database with the current DBID. For related information, see Controlling Data Access With a User Requirements Table.

TRACE

Valid values are:

CBS sets the accumulation of Compound Boolean Selection (CBS) diagnostics to the DATACOM diagnostics file (PXX) by making "$$$" the first 3 bytes of the User Information Block for each DATACOM command.

NO indicates no trace. NO is the default value.

The parameter is optional.

SKIPSELECT

Valid values are:

NO provides access to the root segment as stipulated in the request. This value is the default.

YES provides sequential access to the root segment in the Access File even if logical criteria exist for the segment.

However, if a join connection has been defined to the root segment, a selection command is used.

The parameter is optional.



Example: Sample Attribute Declaration
ENGINE DATACOM SET CONNECTION_ATTRIBUTES DATC /,;2: "USERTABLE AUTOURT"
ENGINE DATACOM SET CONNECTION_ATTRIBUTES ALX /,;905: "USERTABLE ALXURT"

Top of page

x
Using the Default Connection

How to:

The Adapter for DATACOM uses the default connection name if the USERTABLE keyword is omitted from the Access File on the file level and the CONNECTION keyword is omitted on the segment level. For related information, see Access Files for DATACOM.



x
Syntax: How to Use the Default Connection
ENGINE DATACOM SET DEFAULT_CONNECTION [connection_name]

where:

DATACOM

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

connection_name

Is the connection defined in a previously issued SET CONNECTION_ATTRIBUTES command.



Example: Using the Default Connection

The following SET DEFAULT_CONNECTION command selects the DATACOM database server named CON01 as the default server:

ENGINE DATACOM SET DEFAULT_CONNECTION CON01

Top of page

x
Controlling Data Access With a User Requirements Table

First-level access to DATACOM data sources and fields is controlled by the DATACOM User Requirements Table (URT). DATACOM uses the URT to provide file and database-level security, and password protection for element-level security. The URT used for the server structure must include all the DATACOM database IDs contained in the Access File. At run time, the adapter dynamically loads the URT's load module.

The DATACOM Data Driver (like any other DATACOM application) uses a DATACOM User Requirements Table to access the appropriate DATACOM tables. A User Requirements Table contains all tables that an application can access.

One DATACOM URT containing many DATACOM tables can be described by one or many Master Files. The Access File contains the name of URT that dynamically calls the DATACOM URT.

An example of JCL that creates a DATACOM URT is located in HOME.DATA in the member GENURT1 and GENURT2. For your convenience, the sample code is provided in this documentation.

Note: To ensure the most efficient loading of URT tables, you can specify connection pooled deployment in the edaserve.cfg file from the Workspace, Configuration, Data Services option on the Web Console. For details, see Configuring Deployment Modes in Running and Monitoring Your Server.



Example: Sample JCL for User Requirements Table (GENURT1 and GENURT2)

Run GENURT1 followed by GENURT2.

//GENURT1 JOB 'PROG',MSGCLASS=X,CLASS=S  
//*************************************************************
//* NAME:     GENURT1
//*
//* FUNCTION: STEP1 IN CREATING THE DATACOM URT
//*
//* SUBSTITUTIONS:-CHANGE "DATACOM.CAIMAC" TO THE NAME OF YOUR
//*                DATACOM MACRO LIBRARY.
//*               -CHANGE MACRO DBURTBL ENTRIES:
//*                TBLNAME   DATACOM-NAME OF TABLE  (EX PMF)
//*                DBID      DATACOM-ID OF DATABASE (EX 001)
//*               -CHANGE MACRO DBUREND ENTRIES:
//*                USRINFO   1-16 BYTES OF USER INFO TO BE PLACED
//*                          IN URT.
//*               -CHANGE SYSLMOD TO LIBRARY WHERE YOU ARE GOING
//*                KEEP URTS.
//*************************************************************
//ASMBL    EXEC  PGM=ASMA90,PARM='OBJECT,NODECK,LIST',REGION=1024K
//SYSLIB   DD DSN=DATACOM.CAIMAC,DISP=SHR       <==CHANGE
//         DD DSN=SYS1.MACLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSLIN   DD DSN=&&OBJPASS,UNIT=SYSDA,
//         SPACE=(TRK,10),DISP=(NEW,PASS)
//SYSUT1   DD DSN=&&SYSUT1,UNIT=SYSDA,SPACE=(1700,(600,100))
//SYSUT2   DD DSN=&&SYSUT2,UNIT=SYSDA,SPACE=(1700,(300,50))
//SYSUT3   DD DSN=&&SYSUT3,UNIT=SYSDA,SPACE=(1700,(300,50))
//SYSPUNCH DD DUMMY
//SYSIN    DD *
         DBURSTR MULTUSE=YES
         DBURTBL TBLNAM=XXX,DBID=XXX,SEQBUFS=2,UPDATE=YES
         DBURTBL TBLNAM=XXX,DBID=XXX,SEQBUFS=2,UPDATE=YES
         DBURTBL TBLNAM=XXX,DBID=XXX,SEQBUFS=2,UPDATE=YES
         DBUREND USRINFO=*USER COMMENTS *
         END
/*
//LINKEDIT EXEC  PGM=IEWL,PARM='LET,NORENT,NCAL,LIST,MAP,SIZE=1024K'
//SYSPRINT DD SYSOUT=*
//SYSUT1   DD UNIT=SYSDA,SPACE=(CYL,(10,1))
//DBNTRY   DD DISP=(OLD,DELETE),DSN=&&OBJPASS
//SYSLMOD DD DSN=HLQ.URTLIB,DISP=SHR            <==CHANGE
//SYSLIN    DD *
  INCLUDE DBNTRY
  NAME TESTURT1(R)
/*
//
//GENURT2 JOB 'PROG',MSGCLASS=X,CLASS=S 
//*************************************************************
//* NAME:     GENURT2
//*
//* FUNCTION: STEP2 IN CREATING THE DATACOM URT
//*
//* SUBSTITUTIONS:-CHANGE "DATACOM.CAIMAC" TO THE NAME OF YOUR
//*                DATACOM MACRO LIBRARY.
//*               -CHANGE MACRO DBURINF ENTRIES:
//*                LOADNAM OBJECT MODULE CREATED FROM STEP1
//*               -CHANGE MACRO DBUREND ENTRIES:
//*                USRINFO   1-16 BYTES OF USER INFO TO BE PLACED
//*                          IN URT.
//*               -CHANGE //DATAMOD TO HLQ.HOME.DATA LIBRARY
//*               -CHANGE SYSLMOD TO LIBRARY WHERE YOU ARE GOING
//*                KEEP URTS.
//*************************************************************
//ASMBL    EXEC  PGM=ASMA90,PARM='OBJECT,NODECK,LIST',REGION=1024K
//SYSLIB   DD DSN=DATACOM.CAIMAC,DISP=SHR          <==CHANGE
//                 DD DSN=SYS1.MACLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSLIN   DD DSN=&&OBJPASS,UNIT=SYSDA,
//                 SPACE=(TRK,10),DISP=(NEW,PASS)
//SYSUT1   DD DSN=&&SYSUT1,UNIT=SYSDA,SPACE=(1700,(600,100))
//SYSUT2   DD DSN=&&SYSUT2,UNIT=SYSDA,SPACE=(1700,(300,50))
//SYSUT3   DD DSN=&&SYSUT3,UNIT=SYSDA,SPACE=(1700,(300,50))
//SYSPUNCH DD DUMMY
//SYSIN    DD *
         DBURINF URTABLE=LOAD,OPEN=USER,USRNTRY=USNTRY,                X
                 LOADNAM=ALXURT1                   <==CHANGE
         DBUREND USRINFO=*USER COMMENTS*           <==CHANGE
         END
/*
//LINKEDIT EXEC  PGM=IEWL,PARM='LET,NORENT,NCAL,LIST,MAP,SIZE=1024K'
//SYSPRINT DD SYSOUT=*
//SYSUT1   DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//DATAMOD  DD DSN=HLQ.HOME.DATA,DISP=SHR           <==CHANGE
 //DBNTRY   DD DISP=(OLD,DELETE),DSN=&&OBJPASS
//SYSLMOD  DD DSN=PMSAEP.DATACOM.URTLIB,DISP=SHR   <==CHANGE
//SYSLIN    DD *
 INCLUDE DATMOD(USNTRY)
 INCLUDE DBNTRY
 ENTRY USNTRY
 NAME ALXURT(R)
/*
//

iWay Software