Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

RESERVE - reserve table locations for UTM objects

If you use the functions of the program interface KDCADMI for dynamic configuration during application operation, or want to add dynamic objects using the WinAdmin or WebAdmin administration workstation, then you must use the RESERVE statement to reserve table spaces in the object tables of openUTM at the KDCDEF generation.

Further information on dynamic configuration can be found in section "Changing theconfiguration of an application dynamically".

The RESERVE statement can only be issued once for each object type. The following is valid for a RESERVE statement with OBJECT=ALL:

  • After RESERVE OBJECT=ALL is specified, it is not possible to enter any additional RESERVE statements.

  • Before RESERVE OBJECT=ALL all object-specific RESERVE statements are permitted. These object-specific RESERVE statements take priority.

Due to internal dependencies, the KDCDEF generation tool may reserve more objects than specified in RESERVE statements. The exact number of objects of the reserved entries for an object type is output in a message.

RESERVE

OBJECT={ ALL [ ,CARDS=percent11 ] [ ,PRINCIPALS=percent2 1 ] |
         CON     |
         KSET    | 
         LSES    |
         LTAC    |
         LTERM   | 
         PROGRAM |
         PTERM   |
         TAC     | 
         USER [ ,CARDS=percent11 ] [ ,PRINCIPALS=percent21 ] }
[ { ,NUMBER=number | ,PERCENT=percent3 } ]

1only permitted on BS2000 systems

OBJECT=

Table locations are reserved for objects of the specified type. These objects can then be entered in the configuration dynamically as required.

    ALL [ ,CARDS=percent1 ] [ ,PRINCIPALS=percent2 ]


(CARDS= and PRINCIPALS= are only permitted on BS2000 systems)
Table locations can be reserved for objects of type CON, KSET, LSES, LTAC, LTERM, PROGRAM, PTERM, TAC and USER, which are then entered dynamically.

With objects of type USER, CARDS=percent1 means that up to percent1% of users entered dynamically can be defined with an ID card.
PRINCIPALS=percent2 means that up to percent2% of users entered dynamically can be defined with a Kerberos authentication.

Default for percent1/percent2: 0%, i.e. no users can be entered dynamically with an identity card or Kerberos authentication.
Maximum value for percent1/percent2: 100%

    CON

Table entries are reserved for the transport connections to LU6.1 partner applications, for example, for objects of type CON.

    KSET

Table entries are reserved for the key sets, for example, for objects of type KSET.

    LSES

Table entries are reserved for the LU6.1 session names, for example, for objects of type LSES.

    LTAC

Table entries are reserved for the local service names via which the service programs in partner applications can be started. These are objects of the type LTAC.

    LTERM

Table locations are reserved for objects of type LTERM

Please note that the following object components must be generated statically and cannot be entered dynamically:

  • A client with PTYPE=APPLI cannot be assigned dynamically to an LTERM partner without an autosign USER with the name of a statically generated USER.

  • A client with PTYPE=APPLI cannot be assigned dynamically to an LTERM partner without an autosign USER defined with the name of a statically generated user.

  • the format handling system when using formats

  • the sign-on procedure with #formats.

       PROGRAM

Table locations are reserved for objects of type PROGRAM
Objects of type PROGRAM can only be entered dynamically in applications generated with load modules (BS2000 systems), shared objects (Unix and Linux systems) or DLLs (Windows systems).

Please note that the following object components must be generated statically and cannot be entered dynamically:

  • Programming languages (PROGRAM ...,COMP=) must be generated statically using the PROGRAM statement.

  • With ILCS-compatible languages (COMP=ILCS), the static generation of an ILCS program is sufficient.

  • LOAD-MODULEs in PROGRAM must be generated statically using the LOAD-MODULE statement.

  • For applications generated without load modules on BS2000 systems, the PROGRAM names specified when entering a new TAC must be generated statically.

  • For applications generated without shared objects/DLLs, the program names specified when entering a TAC must be generated statically.

    PTERM

Table locations are reserved for objects of type PTERM.

For each client with PTYPE=APPLI, SOCKET, UPIC-R or UPIC-L, openUTM implicitly creates a USER. If such clients generated dynamically, this must be taken into consideration in the NUMBER= or PERCENT= operand for OBJECT=USER.

Please note that BCAMAPPL names must be generated statically and cannot be entered dynamically.

    TAC

Table locations are reserved for objects of type TAC.

Please note that the following object components must be generated statically and cannot be entered dynamically:

  • TAC classes

  • If TACs are to be created dynamically for X/Open program units, at least one X/Open TAC must be generated statically.

    USER [ ,CARDS=percent1 ] [ ,PRINCIPALS=percent2 ]


(CARDS= and PRINCIPALS= are only permitted on BS2000 systems) Table locations are reserved for objects of type USER.

If user IDs have not been generated for an application, i.e. the generation does not contain any USER statements, table locations cannot be reserved for objects of type USER. This is because KDCDEF already reserves an

object of type USER internally for each reserved object of type LTERM. The number of users reserved by KDCDEF in this way is output in a UTM message.

BS2000 systems:
On BS2000 systems CARDS=percent1 means that up to percent1% of users entered dynamically can be defined with an ID card. PRINCIPALS=percent2 means that up to percent2% of users entered dynamically can be defined with a Kerberos authentication.

Default for percent1/percent2: 0%, i.e. no users can be entered dynamically with an identity card or Kerberos authentication. Maximum value for percent1/percent2: 100%

Please note that the following object components must be generated statically and cannot be entered dynamically:

  • the format handling system when using formats

  • the sign-on procedure with #-formats

UTM creates an internal user ID for all TS applications (PTYPE=APPLI/ SOCKET) and UPIC clients (PTYPE=UPIC-R). The NUMBER or PERCENT specification must be increased appropriately if these PTERMs are to be entered dynamically.

NUMBER= 

number

Maximum number of objects of the specified type which can be entered dynamically.

If OBJECTS=ALL, up to number objects of the types listed in the syntax diagram can be entered dynamically.

  • NUMBER=0 The number of objects of the specified type can be increased dynamically to the maximum value, i.e. the maximum number of names that can be generated as specified in section "Number of names ".

  • NUMBER!=0 This reduces the storage space occupied by the UTM application. If the number of objects to be reserved is greater than the maximum number of names that can be generated (see "Number of names "), then this statement has the same effect as NUMBER=0.

Minimum value: 0
Maximum value:

  • 32 000 for LTAC, KSET, TAC and PROGRAM

  • 65 000 for CON, LSES, LTERM, PTERM

  • 500 000 for USER, LTERM, PTERM

The following also apply:

  • The sum of the reserved entries for an object type and the number of statically generated names of the associated name classes must not exceed the maximum number of permitted entries for these name classes (see "Number of names").

  • The sum of the reserved CONs and PTERMs must not be greater than 500 000.

  • The sum of the reserved LSES and USER must not be greater than 500 000.

At the end of the KDCDEF run, the number of entries reserved for each object type is output with message K502.

PERCENT=

percent3

Number of objects of the specified type which can be entered dynamically, expressed as a percentage of the total number of objects of this type which have been generated statically.

The advantage of a percentage specification is that the number of objects that can be entered dynamically automatically increases at the same rate as the number of statically generated objects of the respective type in each generation (assuming the RESERVE statements are not modified).

PERCENT=percent3 has the same effect as the equivalent
NUMBER=number, i.e. PERCENT=0 has the same effect as NUMBER=0.

PERCENT!=0 reduces the storage space occupied by the UTM application. If the number of objects to be reserved is greater than the maximum number of names that can be generated (see "Number of names"), this statement has the same effect as PERCENT=0.

Default: 10
Minimum value: 0
Maximum value: Number of names that can be generated

Powered by Atlassian Confluence and Scroll Viewport.