I think Rob hit the nail on the head. STARSYS tries a 2-way IUCV connection but *VMEVENT is 1-way. You should be using STARMSG instead as it's also 1-way.
-- Mike Harding z/VM System Support mhard...@us.ibm.com mikehard...@mindless.com (925) 672-4403 (o) (925) 323-2070 (m) (925) 672-3922 (h) /sp CMSTSO Pipelines Discussion List <CMS-PIPELINES@VM.MARIST.EDU> wrote on 04/15/2021 07:34:18 AM: > From: Rob van der Heij <rvdh...@gmail.com> > To: CMS-PIPELINES@VM.MARIST.EDU > Date: 04/15/2021 07:34 AM > Subject: [EXTERNAL] Re: Question about starsys *vmevent handling...... > Sent by: CMSTSO Pipelines Discussion List <CMS-PIPELINES@VM.MARIST.EDU> > > On Thu, 15 Apr 2021 at 16:32, Rob van der Heij <rvdh...@gmail.com> wrote: > > > On Thu, 15 Apr 2021 at 16:16, John P. Hartmann <m...@jphartmann.eu> wrote: > > > >> Please trace IUCV to see the interrupt parameter and message number. > >> > > > > I see it as well, and I'm trying to remember what I'm doing wrong, since > > folks are using CMS Pipelines to catch VMEVENT stuff... > > > > And I know, you use STARMSG to catch them! > > Sir Rob the Plumber >
