A UPIC client can run on BS2000, Unix, Linux and Windows systems. If the platform you select is Windows system, you have the advantage of being able to generate a friendly graphical user interface for the administration program.
A client can also be restarted in that it can request the latest output message and continue the interrupted service; see the manual „openUTM-Client for the UPIC Carrier System”.
Please note that a UPIC client
can only communicate with one application at any one time, if it is running under a BS2000 system
cannot itself send any asynchronous jobs to openUTM
always has to take the initiative, i.e. it cannot be started from the application to be administered.
UPIC clients for Unix, Linux and Windows systems are available for the products WinAdmin and WebAdmin.
WinAdmin and WebAdmin offer the full function scope of the KDCADMI program interface (see the section "Administration using WinAdmin and WebAdmin").
UTM on BS2000 systems is supplied with a UPIC client program complete with an SDF command interface in the form of a fully compiled object code. You can adapt the configuration for this program to the needs of your own configuration. For more details, see section "CALLUTM - Tool for administration and client/server communication (BS2000 systems)" of the appendix.
Programming
What you program is a UPIC program which sends the data required for administration (the administration command or input for the administration command) to the remote application and receives the corresponding output from the application being administered. The diagram below gives a rough outline of a UPIC program for Unix, Linux or Windows systems.
#include <upic.h>
Enable_UTM_UPIC /* Sign on to UPIC carrier system */
Initialize_Conversation /* Initialize conversation; */
/* sym_dest_name addresses the */
/* application to be administered. */
Set_TP_Name /* TAC for administration program */
/* or KDC.... administration TAC. */
Set_Conversation_Security_Type=CM_SECURITY_PROGRAM
/* Use UTM user concept */
Set_Conversation_Security_User_ID /* Set UTM user ID which must have */
/* administration privileges. */
Set_Conversation_Security_Password /* Password for user ID */
...
Allocate /* Set up conversation. */
memcpy (buffer, ) /* Supply data area with */
/* command or program input */
Send_Data /* Send command/program input to */
/* the administered application. */
Receive /* Message returned by UTM appli- */
/* cation and then evaluated by */
/* the program. */
Disable_UTM_UPIC /* Sign off UPIC carrier system */
How the UPIC program can send and receive data is described in section "Central Administration using commands" and section "Central Administration using programs".
Generation example (standalone UTM application)
The UPIC program on a Unix or Linux system UNIX0001 is to administer three UTM applications. One application is running on a BS2000 system D123ZE45, the second on a Unix system D234S012 and the third on a Windows system WSERV01. The UTM applications are to be able to shut down with the administration TAC KDCSHUT and to call the administration program with the TAC TPADMIN.
Entries in the UPIC client’s upicfile
upicfile:
* Local name of the CPI-C application LNADMIN001 UPIC0001; * UTM application on a BS2000 system HDUTMAW001 APPLIBS2.D123ZE45 TPADMIN; * UTM application on a Unix or Linux system SDUTMAW002 APPLUnix.D234S012 TPADMIN PORT=30000; * UTM application on a Windows system SDUTMAW003 APPLIWIN.WSERV01 TPADMIN PORT=30000;
UTM generation on the BS2000 system:
BCAMAPPL APPLIBS2,T-PROT=ISO PTERM UPIC0001,PTYPE=UPIC-R,LTERM=UPICLTRM, ,BCAMAPPL=APPLIBS2,PRONAM=UNIX0001,... LTERM UPICLTRM,KSET=ALLKEYS,USER=REMADMIN,RESTART=N USER REMADMIN,PERMIT=ADMIN,RESTART=NO *) TAC KDCSHUT, PROGRAM=KDCADM,ADMIN=Y **) TAC TPADMIN,PROGRAM=ADMINPRG,ADMIN=Y,... PROGRAM ADMINPRG,... PROGRAM KDCADMThe processor name UNIX0001 must be generated in BCAM (by means of a BCIN or CREATE-PROCESSOR command or in the RDF). BCMAP entries are not required for RFC1006 via port 102.
UTM generation on Unix and Linux systems:
BCAMAPPL APPLUnix,LISTENER-PORT=30000,TSEL-FORMAT=T,T-PROT=RFC1006 PTERM UPIC0001,PRONAM=UNIX0001,TSEL-FORMAT=T,PTYPE=UPIC-R,LTERM=UPICLTRM, ,BCAMAPPL=APPLUnix LTERM UPICLTRM,KSET=ALLKEYS,USER=REMADMIN,RESTART=N USER REMADMIN,PERMIT=ADMIN,RESTART=NO *) TAC KDCSHUT, PROGRAM=KDCADM,ADMIN=Y **) TAC TPADMIN,PROGRAM=ADMINPRG,ADMIN=Y,... PROGRAM ADMINPRG,... PROGRAM KDCADMUTM generation on WIndows systems:
BCAMAPPL APPLIWIN,LISTENER-PORT=30000,TSEL-FORMAT=T,T-PROT=RFC1006 PTERM UPIC0001,PRONAM=UNIX0001,TSEL-FORMAT=T PTYPE=UPIC-R,LTERM=UPICLTRM,BCAMAPPL=APPLIWIN LTERM UPICLTRM,KSET=ALLKEYS,USER=REMADMIN,RESTART=N USER REMADMIN,PERMIT=ADMIN,RESTART=NO *) TAC KDCSHUT, PROGRAM=KDCADM,ADMIN=Y **) TAC TPADMIN,PROGRAM=ADMINPRG,ADMIN=Y,... PROGRAM ADMINPRG,... PROGRAM KDCADM*)
The connection user ID is used here, for which no password protection applies. If you require greater security, the UPIC client has to pass on a “genuine” user ID to openUTM using the CPI-C calls Set_Conversation_Security_Type/_User_ID/_Password. In this case the user ID must have administrator privileges and be password protected.
**)
You should generate all the relevant TACs. KDCSHUT must always be generated. In the UPIC, program, the TAC can be set via the program (the default is TPADMIN).
Generation example for a UTM cluster application (Unix, Linux and Windows systems)
The UPIC program on Unix or Linux system UNIX0002 is to administer a UTM cluster application on the Linux systems C123DE10, C123DE11 and C123DE12. The UTM cluster application APPLLINC consists of three nodes and the administration program should be able to call it by means of the TAC REMADMIN.
Entries in the UPIC client’s upicfile:
The UPIC client is configured in a way that requires a separate Symbolic Destination Name to be specified for each node.
* Local name of the CPI-C application LNADMIN001 UPIC0001; * UTM cluster application on the Linux system CDclnode01 APPLLINC.C123DE10 REMADMIN CDclnode02 APPLLINC.C123DE11 REMADMIN CDclnode03 APPLLINC.C123DE12 REMADMIN
In this case, the UPIC program must explicitly address the relevant node (clnode01
,clnode02 or clnode03).UTM generation on the Linux system (initial KDCFILE):
BCAMAPPL APPLLINC,T-PROT=ISO PTERM UPIC0001,PTYPE=UPIC-R,LTERM=UPICLTRM, ,BCAMAPPL=APPLLINC,PRONAM=UNIX0002,... LTERM UPICLTRM,KSET=ALLKEYS,USER=REMADMIN,RESTART=N USER ADMUSR01,PERMIT=ADMIN,RESTART=NO *) USER ADMUSR02,PERMIT=ADMIN,RESTART=NO *) USER ADMUSR03,PERMIT=ADMIN,RESTART=NO *) TAC KDCSHUT, PROGRAM=KDCADM,ADMIN=Y **) TAC REMADMIN,PROGRAM=ADMINPRG,ADMIN=Y,... PROGRAM ADMINPRG,... PROGRAM KDCADM*)
For each node, you should generate a user ID with administration authorizations since, by default, a user in a UTM cluster application continues to be signed on when the conversation terminates. The UPIC program must assign the user ID.
**)
You should generate all the relevant administration TACs. In the UPIC, program, the TAC can be set via the program (the default is REMADMIN).