Why the MSG.JOBNM environmental variable is populated when SSIMSG Parameter is set to YES ?

book

Article ID: 14879

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation

Issue/Introduction

The CA OPS/MVS Event Management and Automation Parameter Reference Guide explains that the SSIMSG Parameter determines whether CA OPS/MVS processes messages before or after JES2 processes them.

This parameter has 2 possible values, NO and YES.

When SSIMSG Parameter is set to YES CA OPS/MVS processes messages before JES2 does so CA OPS/MVS MSG.JOBNM environmental variable  is not populated .



What could be the reason to have information in the MSG.JOBNM environmental variable when SSIMSG Parameter is set to YES ?

Environment

Release: PVLA2.00200-12.2-OPS/MVS-Event Management & Automation-for JES2
Component:

Resolution

With OPS/MVS parameter SSIMSG set to YES, there will be some messages that do not have msg.jobnm populated. This depends on if the asid/job has requested and received a Job number from JES when the message was issued.

This depends whether the GETJOBID subsystem call was done before the message was issued or not.

Additional Information

The definition of SSIMSG Parameter can be found at the following link:

https://docops.ca.com/ca-opsmvs/122-EN/reference-information/parameter-reference/parameters-in-ca-ops-mvs/message-related-parameters#Message-RelatedParameters-SSIMSGParameter