Tony,
I ran in to that same problem back when I was implementing this program. At
the time I opened a PMR asking what was going on. I don't remember the exact
details, but that particular environment wasn't valid to create and call a
System REXX. At the time I had inserted code to test for it, the test is
still in my copy, although I have a branch around it as I think I decided
against using it for some reason, don't remember exactly why..
BNZ MinorLine Yes-> Go process minor line
* Check for valid environment @DM10222010
B EnvOK **** Don't check Environment ****
USING PSA,R0 Point to PSA @DM10222010
L R6,PSAAOLD Point to Current ASCB @DM10222010
USING ASCB,R6 Use pointer to ASCB @DM10222010
L R6,ASCBOUCB Point to OUCB @DM10222010
Drop R6 Reg is now pointing to OU@DM10222010
USING OUCB,R6 Tell assembler @DM10222010
CLI OUCBIAC,x'00' Is OUCBIAC>0? @DM10222010
BH EnvOK Yes-> Continue @DM10222010
WTO 'MPF2REXX Invalid environment for System REXX'
B Return @DM10222010
Drop R6 @DM10222010
* Getmain workarea
Dana
On Wed, 10 Jan 2018 11:42:00 -0500, 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.
>
>
>MPFTREXX INVOKED
>MPFTREXX AXREXX RC 0000000C RSN 041E0C0F RTN: IEF404I
>MPFTREXX DIAG1 47F0C024 DIAG2 D4D7C6E3 DIAG3 D9C5E7E7 DIAG4 40F0F161
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
