bpxmtext 0D070200  gives
BPXNSMSS 09/17/18
JRPswKeyNotValid: The PSW key of the caller is not a valid key

Action: A service was requested that requires the invoker to be in the same
key that the process was dubbed under.

On Wed, 14 Jan 2026 at 14:39, Paul Gilmartin <
[email protected]> wrote:

> On Wed, 14 Jan 2026 14:12:58 +0400, Peter  wrote:
> >
> >After upgrading zos 2.4 to zos 3.1 I get these error while invoking OMVS
> >from ISPF.
> >
> Partition the problem.
>
> What happens if you issue OMVS from the TSO READY prompt?
> What happens if you ssh to z/OS UNIX?
>
>
> >Has anyone encountered this problem?
> >
> >CEE5101C During initialization, the callable service BPX1MSS failed. The
> >system
> >
> >return code was 0000000156 , the
> >
> >
> >         reason code was 0D070200 . The application will be terminated.
> >
> >
> > CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4093 TO DATA SET:
> >PXXXXXX.D014.T0
> >
> >942436.XXXZZZ
> >
> >
> > IGD101I SMS ALLOCATED TO DDNAME (SYS00021)
> >
> >
> >         DSN (PXXXXX.D014.T0942436.XXXXX )
> >
> >         STORCLAS (STANDARD) MGMTCLAS (STANDARD) DATACLAS ( )
> >
> >         VOL SER NOS= XXXB10
> >
> >
> > IGD104I XXXXX.D014.T0942436.XXXXZZ RETAINED, DDNAME=SYS00021
> >
> >IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO P3XXX3.D014.T0942436.P3XXX3
> >
> > CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP.
> >
> >
> > FSUM2088I The OMVS command ended unexpectedly. The recovery routine was
> >invoke
> >
> >d. OMVS control block address = 00000000, C control block address =
> >00000000
> >
> > FSUM2089I First OMVS module address = 0C49E250, second OMVS module
> address
> >= 00
> >
> >000000, PSW = 078D1000 8005E3FE
> >
> >
> > IEA995I SYMPTOM DUMP OUTPUT
> >
> >
> >   USER COMPLETION CODE=4093 REASON CODE=00000090
> >
> >
> >  TIME=09.42.43 SEQ=00410 CPU=0000 ASID=0048
> >
> >  PSW AT TIME OF ERROR 078D1000 8005E3FE ILC 2 INTC 0D
> >
> >    ACTIVE MODULE ADDRESS=00000000_0005CB30 OFFSET=000018CE
> >
> >    NAME=CEEBINIT
> >
> >
> >    DATA AT PSW 0005E3F8 - 00181610 0A0DA7F4 001C1811
> >
> >    AR/GR 0: 006E8B74/84000000 1: 00000000/84000FFD
> >
> >
> >          2: 00000000/00000090 3: 00000000/0D070200
> >
> >
> >          4: 00000000/0C4648B0 5: 00000000/80067EB0
> >
> >
> >         6: 00000000/0C4648B0 7: 00000000/0005E3C2
> >
> >         8: 00000000/80000000 9: 00000000/07378136
> >
> >         A: 00000000/00000001 B: 00000000/8005E320
> >
> >         C: 00000000/0C4661D8 D: 00000000/0C51B030
> >
> >         E: 00000000/8737685C F: 00000001/00000090
> >
> > END OF SYMPTOM DUMP
> >
> >
> >BPXP018I THREAD 0CC3900000000003, IN PROCESS 33555114, ENDED
> >
> >
> >WITHOUT BEING UNDUBBED WITH COMPLETION CODE 84000FFD
> >
> >
> >, AND REASON CODE 00000090.
>
> --
> gil
>
> ----------------------------------------------------------------------
> 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

Reply via email to