search cancel

SOLVE NetMaster &SMFWRITE problem

book

Article ID: 187744

calendar_today

Updated On:

Products

SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS SOLVE MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME

Issue/Introduction

I have a log exit in MAI that traps various message ID's. When a message ID is trapped, it calls another proc to write the SMF record via the &SMFWRITE verb.
When the log exit calls the second proc via an &APPC START, the following is returned

10.58.47.52  LOG-PROC  MAIMLOGP   @IFLOGX1-999 APPC START rc=0 sysmsg=         
10.58.47.52  LOG-PROC  MAIMLOGP   N25B02 USER NOT AUTHORIZED FOR &SMFWRITE REQUEST
10.58.47.52  LOG-PROC  MAIMLOGP   @ADSMF-999 SMFWRITE RC=16 FDBK=0 SYSMSG=  

When the log calls the second proc via a &CALL PROC=, the following is returned
11.13.29.72  LOG-PROC  MAIMLOGP   @ADSMF-999 SMFWRITE RC=8 FDBK=56 SYSMSG=    
11.13.29.72  LOG-PROC  MAIMLOGP   @IFLOGX1-999 CALL rc=8 sysmsg=              

 

Environment

Release : 5.0

Component : CA SOLVE:Access Session Management

Resolution

There's no way to pass an MDO on a SUBMIT.

We recommend that the LOGPROC issues an &EVENT with the MDO and there is a long running proc under BSYS that listens (PROFILE EDS ENABLE) for these events.