Smart RRSAF JES MESSAGES FOR USAGE/VERSION

Products

• Smart RRSAF

Issue/Introduction

When doing an (smart/rrsaf) run -- is there an option to cause version to be written in jes messages (message srsi035i) ?

U11-010 CA-11 - 'F' PROCESSING COMPLETE FOR JOB DXP5048A     
XACT# FOCUCC   RMS      U11RMS       0     0:00.05    0:00.01
+SRSI035I - Smart/RESTART r20.1.00 initialization in progress
+SRSC122I - Smart/RESTART abends will be issued via User ABEN
+SRSI039I - Subsequent messages will be directed to the SRSPR
+SRSI039I - (as specified by the MSGDD parameter)            
XACT# RUNCAF            DBSR001V     0     0:02.05    0:01.63
+SRSI035I - Smart/RESTART r20.1.00 initialization in progress
+SRSC122I - Smart/RESTART abends will be issued via User ABEN
+SRSI039I - Subsequent messages will be directed to the SRSPR
+SRSI039I - (as specified by the MSGDD parameter)            
XACT# RUNRRSAF          DBSR001V     0     0:01.99    0:01.60

 

vs 

U11-010 CA-11 - 'P' PROCESSING COMPLETE FOR JOB DXP50
XACT# FOCUCC   RMS      U11RMS       0     0:00.02   
XACT# RUNCAF            DBSR001A     0     0:00.52   
XACT# RUNRRSAF          DBSR001A     0     0:00.52   

Environment

Release : 20.1

Resolution

The issue described is due to a built-in difference between Smart/RRSAF running without Smart/RESTART versus Smart/RESTART. Smart/RESTART generates a few messages before it has completed processing the runtime options, and these messages always go to the JES joblog. The first of these messages is the version message:SRSI035I. Once the options have been read then if the MSGDD() option is coded with a DDNAME then you get the message: SRSI039I-Subsequent messages will be directed to the <ddname> file. On the other hand, Smart/RRSAF has much less work to do during initialization and so does not begin issuing messages until after the options have been read.
Then if MSGDD() was coded with a DDNAME all the messages are written to that file, including message: A080I - Smart/RRSAF r20.1.00.   Now if you were to code MSGDD(WTO) then the version message would appear in the joblog, along with all the other Smart/RRSAF messages.
If you were running with MSG_DISPLAY(TERSE) this might be ok.
Even if you were running with MSG_DISPLAY(VERBOSE) it might be OK as long as you weren't doing anything that produces a lot of output
(like tracing).  However MSG_DISLPAY(DEBUG) would probably send too much output to the joblog most of the time.   Otherwise a product code change would be required to make the Smart/RRSAF version message write to the JES joblog when MSGDD(<ddname>) is specified.