Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Alan Altmark
Use DVHSAPI to issue DIRMAINT commands and get the output back to your program. Alan Sent from my iPhone using IBM Verse On Jan 11, 2018, 5:54:08 PM, jphartm...@gmail.com wrote: From: jphartm...@gmail.com To: CMS-PIPELINES@VM.MARIST.EDU Cc: Date: Jan 11, 2018, 5:54:08 PM Subject: Re:

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread John P. Hartmann
Whether the OP really needs to include asynchronous messages from a service machine or not in the command output, this is a valid scenario that should be addressed in general and examples in the relevant book; think, e.g., DIRMAINT.

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Rob van der Heij
On 11 January 2018 at 22:57, Hobart Spitz wrote: > Would I be wrong to say a sipping CALLPIPE in a loop might be a good > generalized solution for issuing multiple commands, and keeping the return > codes and messages properly timed? You could, but it probably does not give

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Rob van der Heij
On 11 January 2018 at 23:34, Michael Harding wrote: > No, the command and cms stages are documented to write all command output > before writing the return code to the secondary stream, which is easily > verified. > The stall occurs because command was stuck writing the

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Michael Harding
No, the command and cms stages are documented to write all command output before writing the return code to the secondary stream, which is easily verified. The stall occurs because command was stuck writing the return code before it posted eof on its primary. A simple elastic stage on the second

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Rob van der Heij
On 11 January 2018 at 20:29, Miguel Soltero Diaz wrote: > Most of the code is REXX. I thought we could use PIPES to do the work. > Yes, you could. I most certainly would. Maybe a bit ambitious as your first real project with CMS Pipelines. What the trivial examples did not

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Miguel Soltero Diaz
Thanks Glen, the last one is at least getting me the rc. I just need to add it now to the REPT Thank you ...

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Miguel Soltero Diaz
thanks Alan, my reticence to follow your advice is because I see it only for one command only. Here is what we need. We want to verify access for a number of users. ranging from just a few to all users with access to the LPAR. that include service IDs too.. Access will be verified in a number

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Miguel Soltero Diaz
Forgot to append the DUMP that is showing every time I execute it.. These are the ones for the last two times I have executed it Pipeline stall 11 Jan 2018 09:40:46 5785-RAC CMS Pipelines level 1.1.12 sublevel 14 ("000E"x) From z/VM

Re: [CMS-PIPELINES] getting the RC from third party commands

2018-01-11 Thread Miguel Soltero Diaz
Thank you guys for your efforts. Alan, I tried using !STARMSG *MSG', and the response was sent to console. That is why I used STARTMSG *MSGALL. That way at least the response is sent to the REPT. Michael, I am following your advice, and I am not able to past SPECS. Here is VMSECURE when I