I wouldn't be surprised if CMS Pipelines were just the innocent bystander running some CMS program that program checked.
The ideal would have been to get a VMDUMP at the point where the program check occurred, but since we're probably past that opportunity, another idea would be to look what's at that location when the program is running again (but even if that is in PIPMOD it could still be someone else stepping on things). Rob On Tue, 6 Dec 2022 at 22:28, DeWayne Thomas <[email protected]> wrote: > Greetings, > > We just received the following in a REXX PIPE stage: > > 20:04:01.329108 PARSCALL SocketSetStatus rc=0 PARSEM Connected Free 1099 > Used 1 > 20:04:25.569707 IADEDIRB STORE IADEDIR1 FLEXCNTL > DMSABE141T Data exception occurred at 8114620A in routine PIPE > CMS > > Any helpful hints on how we even begin to debug this? > > Thanks, > DeWayne >
