Administration via a TS application

The application can be any TS application such as a CMX application (PTYPE=APPLI) or a socket USP application (PTYPE=SOCKET), for example. However, you can also use a UTM application, which you generate as a TS application. The administration application is linked to the administered UTM applications by means of an LTERM/PTERM or TPOOL statement.

In all cases, the application can:

• simultaneously administer several UTM applications

• be started by the administered applications

How the application can be programmed depends on the type of TS application used. If you are using a UTM application, you can also use DPUT to send time-driven jobs to the administered applications.

In order to carry out administration by means of a TS application, one of the following cases must apply:

• The connection user ID must have administration authorization, e.g.:

  LTERM ADMINLTM,KSET=ALLKEYS,RESTART=N, USER=ADMINUS
USER ADMINUS, PERMIT=ADMIN, RESTART=N

  or

• A genuine user ID with administration authorization must be signed on during the signon process for the TS application.

Generation

For the generation of an administered UTM application on a BS2000 system, it should be possible to call the command KDCSHUT and to call the administration program with the TAC TPADMIN.

To achieve this, the following statements will be required in the decentralized application for LTERM, TAC and PROGRAM, irrespective of whether the central application is a socket, CMX or DCAM application:

*********************************************************************
*** LTERM, TAC and PROGRAM
*********************************************************************
LTERM ADMINLTM,KSET=ALLKEYS,RESTART=N
USER ADMINLTM, PERMIT=ADMIN,RESTART=N
TAC KDCSHUT, PROGRAM=KDCADM,ADMIN=Y
TAC TPADMIN,PROGRAM=ADMINPRG,ADMIN=Y,...
PROGRAM ADMINPRG,...
PROGRAM KDCADM

To address the central application you must write the following statements depending on which type of application (DCAM or CMX) you are using. If you are using a UTM application, the same applies depending on whether the application is linked via NEA or via TCP/IP.

*********************************************************************
*** DCAM application which communicates via
*** NEA protocols with openUTM applications: on BS2000 systems
*********************************************************************
BCAMAPPL APPLIBS2,T-PROT=NEA
PTERM dcam-name,PTYPE=APPLI,LTERM=ADMINLTM,
BCAMAPPL=APPLIBS2,PRONAM=dcam-computer
*********************************************************************
*** CMX application on Unix or Linux system via TCP/IP-RFC1006
*********************************************************************
BCAMAPPL APPLUnix,T-PROT=RFC1006
PTERM t-selector,PTYPE=APPLI,LTERM=ADMINLTM,BCAMAPPL=APPLUnix,
        LISTENER-PORT=port-number, PRONAM=unix-computer
*********************************************************************
*** Socket application on Unix or Linux system
*********************************************************************
BCAMAPPL SOCKETBS,LISTENER-PORT=12000,T-PROT=SOCKET
PTERM SOCKPTRM,PTYPE=SOCKET,LTERM=ADMINLTM, BCAMAPPL=SOCKETBS,
               LISTENER-PORT=port-number, PRONAM=unix-computer

dcam-name and dcam-computer are the respective names of the DCAM application and computer on which the DCAM application is running. t-selector is the T selector for the remote CMX application. unix-computer is the name of the computer on which the CMX or socket application runs. port-number is the port number at which the central CMX or socket application waits for connection setup requests.