OPS/MVS Invalid variable on HWSHWCOMER API event in BCPii

book

Article ID: 185508

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation

Issue/Introduction

14:18:36,API,HWSHWCOMER HARDWARE COMMUNICATION EVENT - AVAILABLE  CPC IBM390PS.RTP4

14:18:36,MSG,OPFHWS001I HWSHWCOMER HARDWARE COMMUNICATION EVENT - AVAILABLE  CPC

14:18:36,MSG, IBM390PS.RTP4

14:18:36,MSG,OPM9999T OPAOEV RC= 46 FOR ENVIRONMENTAL VARIABLE API.NUMENTRIES

14:18:36,MSG,OPM1046O ERROR 46 RUNNING MISC.HWSEVENT, LINE 67: INVALID VARIABLE REFERENCE

14:18:36,MSG,OPFINFO OPM1046O ERROR 46 RUNNING MISC.HWSEVENT, LINE 67: INVALID VARIABLE REFERENCE

14:18:36,MSG,OPBCP067I - Permanent commerr/BCPii shutdown ECB posted...


My generic rule is intercepting all HWS API events and trying to see if API.NUMENTRIES is > 0.  According to the manual, this variable is always used but does not appear to be used in this case.

Environment

Release : 13.5   Pre-complete (0000) release 

Component : OPS/MVS BCPII INTERFACE

Resolution

api.numentries does not apply to BCPii status events. It's a documentation oversight on our part.

In the past, HISRV created these and other variables in all cases. Variables that did not apply to specific events were created with a value of 0. It generated overhead which we wanted to avoid with the new server. That said, api.numentries does not apply to BCPii up/down status and any of the commerr events.


Additional Information

Documentation updates were submitted to correct this as of March 4, 2020.