That's correct. it is branch around constant, which is you MPFREXX module namee. It's your own rexx, isn't it? Just enter trace all at the beginning of the code you think that is malfunctioning. the output will be printed on the console. you can always start the exec from the consoe as well (f axr,exec_name ief404i jobname1
ITschak On Wed, Jan 10, 2018 at 7:18 PM, Tony Thigpen <[email protected]> wrote: > Yet, the DIAG1-4 values don't look like valid information. They look like > code. > > Tony Thigpen > > ITschak Mugzach wrote on 01/10/2018 11:59 AM: > >> System rexx is complex ;-( the cmplete list of return ode are here: >> https://www.ibm.com/support/knowledgecenter/en/ >> SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaa100/axrexxmac.htm >> ITschak >> >> The four leftmost characters from the reason code 0c0f >> C xxxx0C0F *Equate Symbol:* AXRBadIWMECREA >> >> *Meaning:* A bad return code was returned from IWMECREA. The return code >> and reason codes from IWMESQRY and the return and reason codes from >> IWMECREA are placed in AXRDIAG1, AXRDIAG2, AXRDIAG3 and AXRDIAG4 >> respectively of the RexxDiag parameter. >> >> *Action:* Inspect the return and reason codes from IWMESQRY and IWMECREA >> by >> looking it up in the z/OS MVS Programming: Workload Management Services >> <https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/co >> m.ibm.zos.v2r1.ieaw200/toc.htm?view=kc>. >> If the problem cannot be resolved, contact IBM Service. >> >> >> On Wed, Jan 10, 2018 at 6:42 PM, Tony Thigpen <[email protected]> wrote: >> >> I have something strange happening using the MPF exit MPF2REXX. >>> >>> We are trying to trap when specific subsystems shutdown during the day >>> shift. I am intercepting the IEF404I message, examining it for the job >>> name, then if the job name matches a table, I send a message. >>> >>> If the exit is driven by a test job I submit, then everything works as >>> expected. But when the exit is driven by the shutdown of a started task, >>> I >>> get a failure message on the consoe: >>> >>> MPFTREXX INVOKED >>> MPFTREXX AXREXX RC 0000000C RSN 041E0C0F RTN: IEF404I >>> MPFTREXX DIAG1 47F0C024 DIAG2 D4D7C6E3 DIAG3 D9C5E7E7 DIAG4 40F0F161 >>> >>> Also, I have the trace output turned on. The trace file is built when >>> when >>> the the exit is driven by a submitted job terminating. But, the trace >>> file >>> is not written to, or even cleared, when the exit is driven by the >>> shutdown >>> of a started task. >>> >>> -- >>> Tony Thigpen >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >>> >>> >> >> >> > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
