Re: [CMS-PIPELINES] Question about starsys *vmevent handling......
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 wrote on 04/15/2021 07:34:18 AM: > From: Rob van der Heij > 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 > > On Thu, 15 Apr 2021 at 16:32, Rob van der Heij wrote: > > > On Thu, 15 Apr 2021 at 16:16, John P. Hartmann 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 >
Re: [CMS-PIPELINES] Question about starsys *vmevent handling......
On Thu, 15 Apr 2021 at 16:32, Rob van der Heij wrote: > On Thu, 15 Apr 2021 at 16:16, John P. Hartmann 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
Re: [CMS-PIPELINES] Question about starsys *vmevent handling......
On Thu, 15 Apr 2021 at 16:16, John P. Hartmann 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... Rob
Re: [CMS-PIPELINES] Question about starsys *vmevent handling......
Please trace IUCV to see the interrupt parameter and message number. Also check for message in parameter list. The target class is supposed to identify the data; without that, STARMSG *VMEVENT is useless. Perhaps STARMSG could/should be enhanced to write the IPARML in front of the data (or some part of the IPARML). On 4/15/21 15:07, Dave Jones wrote: Hello, gang. I'm trying to use the starsys *VMEVENT stage to capture logon/logoff messages in a z/VM user id. The user id has this in it's definition. priv classes: ABCDG IUCV statement: IUCV *VMEVENT MSGLIMIT 65535 but when I run this simple text case, I see this: pipe starsys *vmevent | cons MONWRITE FPLIUS346E No message found (id 44767) FPLMSG003I ... Issued from stage 1 of pipeline 1 FPLMSG001I ... Running "starsys *vmevent" RSCSAUTH FPLIUS346E No message found (id 44768) FPLMSG003I ... Issued from stage 1 of pipeline 1 FPLMSG001I ... Running "starsys *vmevent" Does anyone know what's going on here? Many thanks, and stay safe. DJ -- DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and Cloud 703.237.7370 (Office) | 281.578.7544 (CELL) INFORMATION TECHNOLOGY COMPANY
[CMS-PIPELINES] Question about starsys *vmevent handling......
Hello, gang. I'm trying to use the starsys *VMEVENT stage to capture logon/logoff messages in a z/VM user id. The user id has this in it's definition. priv classes: ABCDG IUCV statement: IUCV *VMEVENT MSGLIMIT 65535 but when I run this simple text case, I see this: pipe starsys *vmevent | cons MONWRITE FPLIUS346E No message found (id 44767) FPLMSG003I ... Issued from stage 1 of pipeline 1 FPLMSG001I ... Running "starsys *vmevent" RSCSAUTH FPLIUS346E No message found (id 44768) FPLMSG003I ... Issued from stage 1 of pipeline 1 FPLMSG001I ... Running "starsys *vmevent" Does anyone know what's going on here? Many thanks, and stay safe. DJ -- DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and Cloud 703.237.7370 (Office) | 281.578.7544 (CELL) INFORMATION TECHNOLOGY COMPANY
