Mainframe connection

Define the MVS Servers (Mainframes)

In order to connect to your z/OS mainframe LPARs, you need to create a TCP definition through the MVS Server menu option. In the DataLoader program, select on the Options menu the select MVS Servers. 

The connection refers the IP and port of mainframe task DXPLTCP. Please look at ZETALY Streaming Agent Installation and Operations Guide for more details.  

After completing the parameters click the Save button and then click the Test connection to check if the parameters you configured are correct.  

Create a DinoMessaging Service

You can create a DinoMessaging service for each z/OS LPAR to automatically download the events from the mainframe. A windows service runs even if there is no one logged on the server. 

Use this following command line to install a service (Substitute MVS1 by the SID of your LPAR.) 

sc create DinoMVS1 binPath= "C:\Program Files (x86)\ZETALY Explorer\DinoMessaging.exe MVS1" start= Auto DisplayName="Dino Messaging (MVS1)"

Setting a better description to the service :

sc description DinoMVS1 "Dino Messaging service collects event messages from IBM z/OS Lpar MVS1" 

The name of the service cataloged in the windows will be "Dino" + Name, in this example DinoMVS1. 

We suggest you use our supplied script “CreateDinoService.cmd”. You just type:

CreateDinoService.cmd MVS1

Description will be automatically generated.

Service Recovery

The communication to the mainframe is initiated by the DinoMessaging service. So, the service is the client side of the connection. The service stops if any problem occurs such as: 

• DXPLTCP task in the mainframe is not running 
• Network problems 
• Database connection problem 
• Database errors, such as a lack of space

You should add “Restart service” recovery to automatically restart your services. The configuration is done in the “Services” Administrative tools.  You can also run the services.msc program.  

To add restart feature, on the Services interface, click properties and Recovery: 

Service Parameters

During the service installation process, some entries were created in the a configuration “.json” file.  

These files will be located at “C:\ProgramData\Dino Explorer\” and they will be called DinoMVS1.json. 

 At first time, when the configura “.json” does not exists, it will be created with default parameters. 

You can change any value of these keys by editing the corresponding “.json”  file. 

See the list of values created in the “. Json” below: 

{
"MvsServer": "S0W1",
"BatchSize": 1000,
"FlushTime": 180,
"MsgSize": 100,
"PoolTime": 30,
"Connections": 1,
"AscData": 1,    
"CacheData": 1,
"CatData": 1,
"CecData": 1,
"ChpData": 1,
"CicsData": 1,
"CpuData": 1,
"DbaData": 1,
"DevData": 1,
"DsData": 1,
"ExecData": 1,
"HisData": 1,
"ImsData": 1,
"InvData": 1,
"IoData": 1,
"JobData": 1,
"LcuData": 1,
"LparData": 1,
"MsuData": 1,
"PavData": 1,
"RacfData": 1,
"SmsData": 1,
"SyslogData": 1,
"SyslogdData": 1,
"TrgData": 1,
"VolData": 1,
"VsData": 1,
"WlmData": 1,
"TcpData": 1,
"PageData": 1,
"SwData": 1,
"RmsData": 1,
"VstData": 1,
"CfnData": 1,
"MqData": 1,
"WspData": 1,
"Count": 1
} 

MvsServer is the name of the MVS Server connection used; 

BatchSize is the number of records inserted at each database bulk insert; 

FlushTime is the time in seconds that the buffers will wait to be disposed at DB; 

MsgSize it the number of records that will be retrieved from z/OS at each message; 

PoolTme is the time in seconds that the thread will wait before ask for new incomplete message; 

Connections is the number of concurrent thread executing at same time; 

xxxData are the flags related to the type of SMF. Put “0” (false) or (1) true.