Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

OPTION - manage the KDCDEF run

The OPTION control statement allows you to manage the KDCDEF run.

The control statements for KDCDEF can be distributed in such a manner that only the OPTION statements are contained in a procedure file/shell script, but the actual generation statements are read from other files (on BS2000 systems from SAM or ISAM files or from LMS library elements).

openUTM only processes OPTION statements if they have been read in by SYSDTA or stdin.

OPTION statements are ignored by KDCDEF, if is read from a file that is assigned using OPTION DATA=.

If you issue more than one OPTION statement, the values last specified are taken as valid.

If the OPTION statement is not specified, only the KDCFILE is generated, i.e. the default setting GEN=KDCFILE applies.

OPTION

[ ,DATA= { filename |
           *LIBRARY-ELEMENT 1 (LIBRARY=lib-name 
                    ,ELEMENT=element 
                  [ ,VERSION=C'version' | 
                             *HIGH EST-EXISTING |
                             *UPPER-LIMIT ] 
                  [ ,TYPE=element-type ]) } ]
[ ,GEN= { KDCFILE | ROOTSRC | NO | ALL |  CLUSTER2 | 
         (KDCFILE,ROOTSRC)         | 
         (CLUSTER,KDCFILE)2        | 
         (CLUSTER,ROOTSRC)2        | 
         (CLUSTER,KDCFILE,ROOTSRC)2 } ]
[ ,GEN-RSA-KEYS={ YES | NO } ]

additional opernan on BS2000 systems

[ ,ROOTSRC=filename ]

 additional operand on Unix, Linux and Windows systems
[ ,CHECK-RFC1006={ NO | YES } ]

1 only on BS2000 systems
2 only on Unix, Linux and Windows systems

CHECK-RFC1006=

This parameter is only supported on Unix, Linux and Windows systems.

Extended check of the UTM generation for the communication via TCP/IP connections with RFC1006.

    YES

KDCDEF checks the specifications of transport addresses for all communication partners and local transport system end points that are generated with T-PROT= RFC1006 for completeness and plausibility.
When OPTION CHECK-RFC1006=YES, a port number must be specified in the LISTENER-PORT parameters of the ACCESS-POINT, BCAMAPPL, CON, OSI-CON, and PTERM statements.

Default: YES

    NO 

KDCDEF does not execute any extended checks.

DATA=

Specifies the source from which the subsequent KDCDEF control statements are to be read. The source can also have been generated by inverse KDCDEF by means of the statement CREATE-CONTROL-STATEMENTS.

For information on the inverse KDCDEF function, see section "Inverse KDCDEF".

    filename

The KDCDEF control statements are read from the file specified here (on BS2000 systems, from a SAM or ISAM file). If the end-of-file is reached then the next KDCDEF control statements are read from SYSDTA or stdin again.

    *LIBRARY-ELEMENT(...) 

This parameter value is only supported on BS2000 systems.

The KDCDEF control statements are read from the LMS library element specified here. If the end of the file is reached then the next KDCDEF control statements are again read from SYSDTA.
If the specified library element does not exist then KDCDEF cancels the generation run with an error message

        LIBRARY= 

lib-name

Name of an LMS library. The file name can be up to 54 characters in length. LIBRARY is a mandatory parameter.

       ELEMENT=

element

Name of an LMS element.
The element name may be up to 64 characters in length and consists of an alphanumeric string which can be subdivided into multiple substrings separated by periods or hyphens.
ELEMENT is a mandatory parameter.

       VERSION =

Version of the LMS element.

           C'version'

The element version is specified as an alphanumeric string of up to 24 characters in length which can be subdivided into multiple substrings separated by periods or hyphens.

            *HIGHEST-EXISTING 

The highest version of the specified element present in the library is read.

Default: *HIGHEST-EXISTING

           *UPPER-LIMIT

The highest possible version of the specified element is read. LMS indicates this version by means of an "@".

       TYPE=

element-type

Type of LMS element. An alphanumeric string of up to 8 characters in length can be specified for the type. Default value: S

For further information on the syntax rules for the names of LMS elements and a specification of version and type, see the manual "LMS SDF Format".

GEN=

Specifies what objects are to be generated.

    KDCFILE

The KDCFILE is generated.

Default: KDCFILE

    ROOTSRC

The ROOT table source is generated.

    (KDCFILE,ROOTSRC)

The KDCFILE and the ROOT table source are generated.

    CLUSTER 

This parameter value is only supported on Unix, Linux and Windows systems.

The following UTM cluster files are generated:

  • the cluster configuration file

  • the cluster user file

  • the cluster page pool files

  • the cluster GSSB file

  • the cluster ULS file

These files must not already exist.

If you have specified OPTION GEN=CLUSTER or (CLUSTER,...), you must also specify a CLUSTER statement and at least two CLUSTER-NODE statements.

    (CLUSTER,KDCFILE)

This parameter value is only supported on Unix, Linux and Windows systems.

The UTM cluster files listed above are generated together with the KDCFILE.

    (CLUSTER,ROOTSRC)

This parameter value is only supported on Unix, Linux and Windows systems.

The UTM cluster files listed above are generated together with the ROOT table source.

    (CLUSTER,KDCFILE,ROOTSRC)

This parameter value is only supported on Unix, Linux and Windows systems.

The UTM cluster files listed above are generated together with the KDCFILE and the ROOT table source.

    NO

The parameters are only checked.

    ALL

The KDCFILE and the ROOT table source are generated.

If a ROOT table source is generated, the ROOT statement must be specified. This is the case with the following specifications:

  • ROOTSRC

  • (KDCFILE,ROOTSRC)

  • ALL

  • (CLUSTER,ROOTSRC)

  • (CLUSTER,KDCFILE,ROOTSRC)


The following must further be noted for Unix, Linux and Windows systems:

  • KDCDEF generates the ROOT table source as a C/C++ program under the name rootname .c (see the ROOT statement) in the directory filebase (see the MAX ...,KDCFILE=filebase... statement).

  • If a KDCFILE is generated for a UTM cluster application, then the cluster user file must already exist. This file is evaluated and extended if required.

GEN-RSA-KEYS =

Specifies whether RSA keys are to be created.

    YES

KDCDEF is to generate RSA keys.

RSA keys are required by applications in which objects (TAC, PTERM or TPOOL) are generated with an encryption level.

If GEN-RSA-KEYS=YES then KDCDEF always generates RSA keys for password encryption irrespective of the type of objects generated.

If GEN-RSA-KEYS=YES is set but the encryption functions are not available then KDCDEF issues the warning message K508. However, the KDCFILE is still generated and the application can be operated (without encryption).

Default: YES

    NO

KDCDEF is not to generate RSA keys.

GEN-RSA-KEYS=NO should not be used unless

  • openUTM is being run without the encryption functionality ,

  • or, after the KDCDEF run, the RSA keys are transferred from an old KDCFILE to the new KDCFILE using KDCUPD. For more information on transferring RSA keys with KDCUPD see "The tool KDCUPD - updating the KDCFILE".

If objects with encryption are generated in an application and if no RSA keys are available, the application can run but with certain restrictions, i.e.:

  • TACs with encryption level cannot be called,

  • no connection can be established to PTERMs or TPOOLs generated with encryption level.

ROOTSRC= 

filename

This parameter is only supported on BS2000 systems.

This parameter is significant only when generating the ROOT table source.

filename can be up to 54 characters in length.

A ROOT source with the CSECT name rootname is generated and stored in the KDCROOT file filename. rootname is defined in the ROOT statement.

Default: ROOT.SRC.ASSEMB.rootname



Powered by Atlassian Confluence and Scroll Viewport.