OPS/MVS: MSG Rule variable to trap the correct message issuer

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Why sometimes the CA OPS/MVS variable MSG.JOBNAME does not return the original jobname of the message issuer?

 

 

Environment

Release:  
Component: OPSMVS 

Resolution

When the message is issued asynchronously from the CONSOLE address space or is being reissued for some other reason, the value of MSG.JOBNAME can be different from the name of the task that originally issued it. In this case, in order to code a correct MSG rule, it is better to use the variable MSG.OJOBNAME to trap the correct message issuer as it always contains the original job name associated with the message.

Here a sample situation from ADABAS task message ADAN01 :

TIME     Job Name OJobname ----+----1----+----2----+----3----+----4----+-
04:00:04 ADDPDESS ADDPDESS ADAN01 00053 A D A B A S  V8.3.5  is active   
04:00:04 ADDPDESS ADDPDESS ADAN01 00053 MODE = MULTI                     
04:00:04 ADDPDESS ADDPDESS ADAN01 00053 Running without recovery log     
04:00:05 CONSOLE  ADDMASTR ADAN01 00221 A D A B A S  V8.3.5  is active   
04:00:05 CONSOLE  ADDMASTR ADAN01 00221 MODE = MULTI                     
04:00:05 CONSOLE  ADDMASTR ADAN01 00221 Running without recovery log     
04:00:05 CONSOLE  ADDVISD1 ADAN01 00041 A D A B A S  V8.3.5  is active   
04:00:05 CONSOLE  ADDVISD1 ADAN01 00041 MODE = MULTI                     
04:00:05 CONSOLE  ADDVISD1 ADAN01 00041 Running without recovery log     
04:00:05 CONSOLE  ADDVISD2 ADAN01 00042 A D A B A S  V8.3.5  is active   
04:00:05 CONSOLE  ADDVISD2 ADAN01 00042 MODE = MULTI                     
04:00:05 CONSOLE  ADDVISD2 ADAN01 00042 Running without recovery log     
04:00:05 ADSMASTR ADSMASTR ADAN01 00222 A D A B A S  V8.3.5  is active   
04:00:05 ADSMASTR ADSMASTR ADAN01 00222 MODE = MULTI                     
04:00:05 ADSMASTR ADSMASTR ADAN01 00222 Running without recovery log     

Some of the different  ADABAS regions have the jobname and the ojobname both set to the region task name (ADSMASTR - DDPDESS) but others have jobname set to CONSOLE and ojobname always set to the correct ADABAS task name (ADDMASTR - ADDVISD1 - ADDVISD2). 

Additional Information

A reference for the variables available in message rules can be found at the following link for OPSMVS 14.0 (but valid for all the supported releases) 

AOF Variables Available in MSG Rules