The consequences of setting up VM:Schedule as a SECUSER in VM:Operator

Document ID : KB000054839
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

VM:Schedule is set up as a SECUSER in VM:Operator. VM:Operator reroutes messages to a OPVMCL client, which will pass the message to OPSMVS via IP sockets.

When a User id gets autologged to run a VM:Schedule job (scheduled request) VM:Operator routes that message to this monitor, however, hex characters 0C0D0E0F000000, are tagged on to autolog message.

Solution:

These hex characters do not appear in Operator's open console or syslog and only show up in Operator's closed console. They also cause the next message to be routed to the monitor to not be filtered correctly.

Example of series of messages sent to Operator

00:15:00 AUTO LOGON *** VMTLIBR USERS = 52 BY VMSCHED
VMSCHED : AUTO LOGON *** VMTLIBR USERS = 52
VMSCHED : 00:15:00 VMTLIBR 00 VMDAUT060I Request 'DLYRPTS' started normal
VMTLIBR : VMSCHED MON START VMTLIBR DLYRPTS 00000038 """"

Following is the EXEC that routes the messages to the OPVMCL client:

OPVMMSG  EXEC     W1  V 130  Trunc=72 Size=24 Line=0 Col=1 Alt=0        
                                                                         
* * * Top of File * * *                                                  
/*********************************************************************/  
/*  OPVMMSG  EXEC A                                                  */  
/*                                                                   */  
/*  This exec will build SMSG command and route the message to       */  
/*  OPVMCL client, which will pass the message to OPSMVS via         */  
/*  IP sockets.                                                      */  
/*  To activate it, code the following entry in the LOGTABLE file:   */  
/*                                                                   */  
/*  EXEC OPVMMSG MSG * *                                             */   
/*                                                                   */  
/*********************************************************************/  
                                                                         
'EXECIO * CP (SKIP STRING QUERY OPVMCL'                                  
if rc \='0' then do                                                      
 Exit -1                                                                 
 end                                                                     
                                                                         
Parse Arg 1 time 10 userid  19 class 22 msg_text                         
                                                                         
'CP SMSG OPVMCL 'time''userid''class''msg_text                           
                                                                         
Exit -1                                                                  
                                                                         
/*********************************************************************/  
* * * End of File * * *

The reason for the hex characters on the Autolog message, is due to the Monitor process in VM:Schedule. VM:Operator is capturing the internal MON START command that is given to the autologged user getting ready to run a VM:Schedule request. This would not be seen normally, except for the SECUSER set up. There isn't any
way to get around this unless the VM:Schedule job monitor process is not used. Turning this off would allow VM:Schedule to end up with other problems (run away VM:Schedule requests and users not logged off after request completion to name a couple)

To resolve this on the VM:Operator side, the following Rexx code was added in the above exec after the Parse Arg:

/* Alters char x'00 to x'0f to ques. marks. Command post problem */
msg_text = translate(msg_text,'????????????????',xrange('00'x,'of''x))