Starting an Event-Driven UEM Server - zOS

Starting an Event-Driven UEM Server

There are two ways start an event-driven UEM Server (uems) component:

  1. Recycle the ubroker daemon (Universal Broker service under Windows).
  2. Use Universal Control to start the uems, either locally on the server or from the mainframe.

In this example, uems is started from the mainframe.

(This job will fail if uems is running at the time of submit; uems usually is started by the Universal Broker when it is started.)


//STUEMS   JOB CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID 
//         JCLLIB ORDER=SBI.UNV.SUNVSAMP 
//* 
//STEP1    EXEC UCTLPRC 
//LOGONDD  DD  DISP=SHR,DSN=MFC1A.JCL.CNTRL(WINUSER) 
//SYSIN    DD  * 
-host 172.16.30.30 -encryptedfile LOGONDD -port 7887 -start uems 
/* 


Note

There is only one different command (-start) between this example and Refreshing an Event-Driven UEM Server.

SYSIN Options

The SYSIN options used in this example are:

Option

Description

-host

TCP/IP host name of the remote computer on which Universal Broker is running and accepting connections.

-encrypted

Encrypted command file.

-port

TCP/IP port number of the remote computer on which Universal Broker is running and accepting connections.

-start

Instruction to a Universal Broker to start the UEM Server.

Components

Universal Control

Universal Event Monitor Server for Windows

Universal Event Monitor Server for UNIX