Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

KDCINF - Syntax description

KDCINF      type

           [ ,LIST={ KDCNAMES | (name_1,...,name_10) | KDCALL | KDCCON } ]

           [ ,OUT={ KDCDISP | KDCPRINT | KDCBOTH | ltermname | tacname } ]

           [ ,CONT={ name | (name,proname) | (name,proname,bcamname) } ]

           [ ,PRONAM=proname]

           [ ,LPAP=lpapname ]                    (only for type = LSES)

           [ ,OSI-LPAP=osilpapname ]             (only for type = OSI-ASSOCIATIONS)

Only on BS2000 systems

[ ,OPTION=MONITORING ]               (only for type = MUX)

For administration using message queuing, you must enter KDCINFA.

type 


Type of objects or application parameters about which UTM is to provide information. For type you can enter the following values:

ALL
KSET
LTERM
PAGEPOOL
POOL

PROG
PTERM
STATISTICS
SYSLOG
SYSPARM

TAC
TACCLASS
TAC-PROG
USER

To query information about objects in a distributed processing environment you can enter the following values for type:

CON
LPAP
LSES
LTAC

OSI-ASSOCIATIONS
OSI-CON
OSI-LPAP


In UTM applications on BS2000 systems you can also enter the following for type:

LOAD-MODULE

MUX


In UTM applications on Unix, Linux or Windows systems you can also enter the following for type:

SHARED-OBJECT





These entries for type have the following meanings:

ALL


Calls for all information about all objects, statistics and application parameters.

The result of KDCINF ALL is always output to the standard system printer (the default printer in the operating system). Control of output using the OUT operand is not possible: entries for OUT are ignored. 
For the LIST operand, only the operand values KDCNAMES (default) and KDCALL are considered.

In the combination ALL and LIST=KDCNAMES, the names of all objects are output but no application parameters and no statistical information are displayed.

In the combination ALL and LIST=KDCALL, all application parameters, statistical information and the properties of all objects are displayed.

In UTM applications on BS2000 systems , no information is displayed about load modules in response to KDCINF ALL, LIST=KDCALL.

In KDCINF ALL, data relating to the CONT, OUT and PRONAM operands has no effect.

KSET


Informs you about the key sets in the application. You can output information about a specific key set (use of LIST=kset_name) at an administrator terminal. If you wish to obtain information about several or all key sets, this information is always output to the standard system printer. 
Data relating to the OUT operand has no effect.

Exception

If a value greater than 255 was entered for the KEYVALUE operand in the MAX statement during KDCDEF generation, you cannot query any information about key sets with the KDCINF call (type = KSET). In this case, the KDCINF command is rejected and the message ”KEYVALUE > 255 NOT SUPPORTED“ is displayed. 
However, you can create your own administration program for querying this information with the help of the administration program interface (KC_GET_OBJECT call with object type KC_KSET).

LOAD-MODULE (only on BS2000 systems)



Informs you about load modules. The scope of output can be controlled using the CONT and LIST operands. For LIST, you are only allowed to enter KDCNAMES or an individual load module name. With LIST=KDCNAMES a list of all load module names is issued. 
You are provided with information about a specific load module if you enter the name of that load module in LIST.

When you enter the name of a load module in LIST, the entry is interpreted as a program name in CONT. This entry in CONT determines the program unit name with which the list of program units in the load module should begin.

LTERM


Informs you about LTERM partners, i.e. about the logical names and properties of clients and printers. The scope of this output can be controlled using operands CONT and LIST.

If an LTERM partner is assigned to a printer pool (several printers, i.e. PTERMs), then you can display the list of printers assigned to the LTERM (PTERMs) with the following command:

KDCINF LTERM, LIST=ltermname

If the specified LTERM is the primary LTERM of an LTERM group, the primary and group LTERMs of the LTERM group are output (see openUTM manual “Generating Applications”). The sequence is as follows:

  • The first line contains the primary LTERM.

  • The subsequent lines contain the group LTERMs.

If the specified LTERM is both the master LTERM of an LTERM bundle and the primary LTERM of an LTERM group, all master, primary, slave and group LTERMs are output. The sequence is as follows:

  • The first line contains the master/primary LTERM.

  • This is followed by all the group LTERMs.

  • The subsequent lines contain the all the slave LTERMs. The first slave LTERM listed is the one to which the messages are delivered.

The call KDCINF LTERM, LIST=master-lterm outputs the master and slave LTERMs of an LTERM bundle. Output is the same as with the KDCINF LTERM, LIST=KDCALL call:

  • The first line contains the master LTERM.

  • The subsequent lines contain the slave LTERMs.

MUX (only on BS2000 systems)



Informs you about the properties and current status of multiplex connections. If MUX is entered together with the operand OPTION=MONITORING, UTM also supplies event values for the multiplex connections. 
However, OPTION=MONITORING has no effect if you enter LIST= KDCNAMES.

PAGEPOOL

Informs you about the current utilization of the page pool.

Only the OUT operand is valid in conjunction with PAGEPOOL. 
Specifications for the LIST, CONT, and PRONAM operands are ignored by openUTM.

POOL

Informs you about LTERM pools. The scope of output can be controlled with the operands CONT and LIST.

PROG

This is only permitted if the application was generated using load modules/shared objects (the LOAD-MODULE statement (BS2000 systems) and the SHARED-OBJECT statement (Unix, Linux and Windows systems). openUTM informs you about the program units in the application. 
In each program unit, the name of the relevant load module/shared object/DLL is displayed together with its load mode and a statement about how readily it can be replaced. 
The scope of output can be controlled using the operands CONT and LIST.

PTERM

Informs you about the physical properties of clients and printers. The scope of output can be controlled using the operands CONT, LIST and PRONAM.

SHARED-OBJECT (only on Unix, Linux and Windows systems)



This is only permitted if the application is generated using SHARED-OBJECT statements. 
openUTM informs you about shared objects/DLLs.

The scope of output can be controlled using the operands CONT and LIST. With LIST, the only entries permitted are KDCNAMES or an individual shared object name/DLL name. When LIST=KDCNAMES is entered, a list of all share object names or DLL names is issued.

STATISTICS

Displays general statistical information. 
Together with STATISTICS, only the operand OUT has any effect. Entries for the operands LIST, CONT and PRONAM are ignored by openUTM.

Some statistical data is written to the system log file SYSLOG once an hour via the K081 message and subsequently reset to 0. For this to be possible, the application must have been generated with MAX STATISTICS-MSG=FULL-HOUR .The statistical values supplied by openUTM and their period of validity are described as of section type=STATISTICS in chapter "Output from KDCINF (examples)".

SYSLOG

Informs you about the SYSLOG file for the UTM application. Together with SYSLOG only the OUT operand has any effect. Entries for the operands LIST, CONT and PRONAM are ignored by openUTM. 
KDCINF SYSLOG acts like KDCSLOG INFO (see chapter "KDCSLOG - Administer the SYSLOG file" ).

SYSPARM

Informs you about application parameters (system parameters) and timer settings which were defined during generation in the MAX statement and which can be changed using the administration functions. Using SYSPARM you can, for example, check parameter values which were changed using KDCAPPL. 
Together with SYSPARM, only the operand OUT has any effect. Entries for the operands LIST, CONT and PRONAM are ignored by openUTM.

TAC


Informs you about transaction codes or TAC queues in the application. 
The scope of output can be controlled with the help of operands CONT and LIST.

TAC-PROG

This is only permitted if the application was generated using load modules/shared objects (the LOAD-MODULE statement (BS2000 systems) or the SHARED-OBJECT statement (Unix, Linux and Windows systems) respectively. 
openUTM informs you about which program units are assigned to the transaction codes and the load modules/shared objects/DLLs to which the program units are assigned. The transaction codes are specified in the LIST operand.

TACCLASS

Informs you about TAC classes in the application. 
openUTM displays how many messages in each TAC class are waiting to be processed, how long the average wait time is for each TAC class and whether priority control is generated for a TAC class. If priority control is not generated for a TAC class, i.e. the TAC-PROPERTIES statement was not issued during KDCDEF generation, openUTM displays how many processes are assigned to each TAC class.

USER


Informs you about the user IDs in the application. 
openUTM informs you about security violations for the user ID, CPU time used since the user signed on, and the LTERM partner used to sign on the user ID.

The scope of output can be controlled using the operands CONT and LIST.


The following values are only useful for applications that use distributed processing:

CON             

Only for distributed processing using the LU6.1 log. 
openUTM informs you about connections that were created with KC_CREATE_OBJECT for the object type KC_CON or generated using the KDCDEF control statement CON. openUTM displays names, generated properties, current status and statistical values relating to the level of capacity utilization for the connection. The scope of output can be controlled using the operands CONT, LIST and PRONAM.

LPAP

Only for distributed processing using the LU6.1 log. 
openUTM informs you about the names and properties of the LPAP partners. Depending on the entries in LIST, open UTM will either display the names only, or these names together with the properties of the LPAP partners. The scope of output can be controlled using the operands CONT and LIST.

You can issue the call KDCINF LPAP, LIST=master-lpap to output the master and slave LPAPs of an LU6.1-LPAP bundle (see openUTM manual “Generating Applications”). The output has exactly the same form as for the call KDCINF LPAP, LIST=KDCALL:

  • The first line contains the master LPAP.

  • The following lines contain the slave LPAPs.

LSES

Only for distributed processing using the LU6.1 log. 
openUTM informs you about local sessions that were created with KC_CREATE_OBJECT for the object type KC_LSES or generated using the KDCDEF control statement LSES. If you specify LSES together with the operand LPAP= lpapname (KDCINF LSES,LPAP= lpapname ), openUTM restricts output to information about sessions generated for the LPAP partner specified in lpapname . The scope of output can also be controlled with the aid of the operands CONT and LIST.

LTAC

Informs you about the names and properties assigned to remote service programs within local applications (LTAC properties).
The scope of output can be controlled with the aid of the operands CONT and LIST.

OSI-CON

Only for distributed processing using the OSI TP log. 
openUTM informs you about names generated with the KDCDEF control statement OSI-CON for logical connections to partner applications. 
Depending on the entries in LIST, the properties generated in OSI-CON for related connections are displayed. 
The scope of output can be restricted with the help of the operands CONT and LIST.

OSI-LPAP

 Only for distributed processing using the OSI TP log.
openUTM informs you about OSI-LPAP partners that were generated for the OSI TP partner applications in the local application. Depending on the specifications made for the LIST operand, openUTM will either display the names only, or these names together with the logical properties of their partner applications. 
The scope of output can be controlled with the aid of the operands CONT and LIST.

The KDCINF OSI-LPAP, LIST=master-lpap-name call outputs the master and slave LPAPs of an OSI-LPAP bundle (see openUTM manual “Generating Applications”). The output is the same as for the call KDCINF OSI-LPAP, LIST=KDCALL:

  • The first line contains the master LPAP.

  • The subsequent lines contain the slave LPAPs.

OSI-ASSOCIATIONS


Only with distributed processing using the OSI TP log. 
openUTM informs you about OSI TP associations. Information about the job submitter assigning an association together with statistical information.

KDCINF...,L=KDCNAMES 
outputs the name of generated OSI associations.

KDCINF...,L=KDCALL,OSI-LPAP=osilpapname 
only outputs the currently associated OSI associations, sorted by the association ID assigned by XAPTP. 
The operand OSI-LPAP=osilpapname is mandatory!

KDCINF...,L=(name_1...name_10),OSI-LPAP=osilpapname 
In this case, the association ID assigned by XAPTP must be entered for name_n rather than the OSI association name generated. 
The operand OSI-LPAP=osilpapname is mandatory!
The scope of output can be controlled with the help of operands CONT and LIST.

openUTM restricts itself to information about OSI associations that have been set up in connection with the specified OSI-LPAP partners.


The following operands control output

LPAP=lpapname



is only permitted for type = LSES:
This operand restricts output of session properties to sessions that were generated for a partner application specified in lpapname.

OPTION=MONITORING (only on BS2000 systems)



is only permitted for type = MUX and only works where LIST != KDCNAMES. openUTM informs you about event values in multiplex connections.

With KDCINF ALL, these event values are not issued at the same time as the other values.

CONT=

Continue/start the output list at a specific point. List output occurs in alphabetical order of object names. CONT=name causes the output list to start with the object name and to contain only objects whose name occurs following the one specified in name in alphabetical order.

With UTM applications on BS2000 systems, the operand CONT, when specified in conjunction with LIST=name, only takes effect if the name of a program unit is entered for type LOAD-MODULE and for name.

In UTM applications running on Unix, Linux or Windows systems the operand CONT has no effect if specified together with LIST=(name_1,...,name_10).


name

The list starts with the object name. For name, specify the name of an object in the application. You can enter any one of the following names:

  • for type = KSET: KSET name of a key set.

  • for type = LTERM: logical name of a client/printer (name of an LTERM partner)

  • for type =PTERM: (PTERM-)name of a client or printer

  • for type =POOL: the LTERM prefix defined for an LTERM pool

  • for type = PROG: name of a program unit

  • for type =TAC: TAC name of a local transaction code/queue

  • for type = USER: user ID (USER name)

  • for type = CON/OSI-CON: a logical connection name generated in a CON or OSI-CON statement

  • for type = LPAP/OSI-LPAP: name of an LPAP or OSI-LPAP partner

  • for type = LTAC: local TAC name of a remote service program

  • for type=OSI-ASSOCIATION: association ID, assigned to the association when establishing an OSI TP connection

In UTM applications on BS2000 systems you can also enter the following names:

  • for type = LOAD-MODULE: name of a load module or a program unit

  • for type = MUX: name of a multiplex connection


(name,proname)



The list should begin with the object (name,proname). proname is the name of the processor on which the object name is located. There is no point entering proname unless type = PTERM / CON / MUX objects of the same name exist, as a result of which unique identification is only possible using the different processor names.


(name,proname,bcamappl)



The list should start with the object (name,proname,bcamappl). bcamappl is the name of the transport access point that is used by the object (name,proname) to connect to the application. It is only of use to specify bcamappl if objects with type=PTERM / CON / MUX exist with the same name and processor and unique identification is therefore only possible if the name of the transport access point is different.

Output starts with the object (name,proname) to which the local transport access point name indicated in bcamappl is assigned.

LIST=

Controls the type and scope of information.


KDCNAMES



Outputs a list of names of all objects of the type specified in type. LIST=KDCNAMES has no effect on type=PAGEPOOL, STATISTICS, SYSLOG, SYSPARM, TACCLASS.


(name_1,..., name_10)



The properties of objects with the names name_1,..., name_10 are displayed. You can specify a maximum of 10 names. Parentheses are not required if only one name is specified.


KDCCON  

Only appropriate for type = PTERM, USER, LSES and CON.

Also for UTM applications on BS2000 systems and for type=MUX.

Only the properties of objects currently connected to the application are displayed in response to this command.

Exceptions with type=USER: 
If the application is generated with SIGNON MULTI-SIGNON=NO, then the user IDs through which only OSI TP partners are signed on to start asynchronous services are not displayed.

If the application is generated with SIGNON MULTI-SIGNON=YES, then the following user IDs are not displayed:

  • user IDs with RESTART=NO that are not signed on through a terminal

  • user IDs through which only OSI TP partners are signed on that have selected the functional unit “COMMIT” or that intend to start an asynchronous service.


KDCALL

The properties of all objects of the type specified in type are displayed.

Default: KDCNAMES

OSI-LPAP=osilpapname



Only permitted for type = OSI-ASSOCIATIONS. The operand restricts the output of information to the OSI associations that have been established for the specified OSI-LPAP partner.

The operand must be specified for: 
KDCINF OSI-ASSOCIATION...,L=(name_1...name_10) 
KDCINF OSI-ASSOCIATION...,L=KDCALL

OUT= 

Indicates where UTM is to output the information requested.


KDCDISP

Output to the administrator terminal, i.e. the terminal at which KDCINF was entered.


KDCPRINT

On Unix and Linux systems, the shell script admlp is used for output. admlp is located in $UTMPATH/shsc and calls the lp command. Users can modify admlp or create their own script with the name admlp and store it under a separate directory. This directory must then be included in the path variable $PATH (prior to $UTMPATH/shsc).

Windows systems do not as yet support output to a printer from the UTM application, i.e. no file is generated or printed out.


KDCBOTH

Output to the administrator terminal and (Unix and Linux systems) to the standard system printer.

On Unix and Linux systems, the shell script admlp is used for output (see above).


ltermname

Output to the printer with the logical name ltermname.


tacname

Name of the transaction code to which UTM is to transfer the result of the information query. The transaction code must be assigned to a program unit which runs in an asynchronous service.

Default: KDCDISP

PRONAM=proname



Only effective for type = PTERM, CON and MUX. 
openUTM only supplies information about the clients and partner applications running on or connected to the computer proname.

Default value for openUTM for systems: Blanks for local devices

Powered by Atlassian Confluence and Scroll Viewport.