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
