Re: SysRexx and WAIT program not working (resolved)

2018-01-21 Thread Tony Thigpen
> I am still curious what program is supposed to be executed: MPFZWAIT > or JOBZWAIT? Because I am stupid? :-) That was the problem. I am currently working on two major systems. One is related to MPF, the other to a system called 'JOBZ'. I actually have the same program, with different name,

Re: SysRexx and WAIT program not working

2018-01-21 Thread Seymour J Metz
No, with LINKMVS you pass variable names for the parameters, not the actual parameters. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua

Re: SysRexx and WAIT program not working

2018-01-21 Thread Paul Gilmartin
On Sun, 21 Jan 2018 08:29:26 -0500, Don Poitras wrote: >And you were correct when you first wrote it. You want "JOBZWAIT 120", >not "JOBZWAIT wait_value". It looks as though LINKMVS isn't available >in your environment. > I think not. 'address LINK "JOBZWAIT 120"' is correct, but not 'addres

Re: SysRexx and WAIT program not working

2018-01-21 Thread Paul Gilmartin
On Sun, 21 Jan 2018 19:47:59 +, Seymour J Metz wrote: >Slight clarification; appropriate in the sense that if the LINK and LINKMVS >environments are available in SysRexx and if JOBZWAIT handles the documented >parameter lists for those environments then those are the correct forms. >__

Re: Writing SMF 89 records

2018-01-21 Thread Peter Relson
Reading the documentation for each of the SMF 89 subtypes, it would appear that (in somewhat informal terms) subtype 1 reports CPU and zIIP time for a product, while subtype 2 reports the number of times that a product was run (registered itself as running). Is that a fair summary? I'd say "no"

Re: SysRexx and WAIT program not working

2018-01-21 Thread Steve Horein
I am still curious what program is supposed to be executed: MPFZWAIT or JOBZWAIT? Am I missing something? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message:

Re: SysRexx and WAIT program not working

2018-01-21 Thread Peter Relson
>The wait program is in the LLA and does work works with what invocation? And I doubt you meant "in the LLA". Perhaps "in the LNKLST" or "in the LPA"? It does appear that LINKMVS passes to the target a parameter list in the same way that EXEC PGM=xxx does, each parameter being a 2-byte length

Re: SysRexx and WAIT program not working

2018-01-21 Thread Seymour J Metz
Slight clarification; appropriate in the sense that if the LINK and LINKMVS environments are available in SysRexx and if JOBZWAIT handles the documented parameter lists for those environments then those are the correct forms. From: IBM Mainframe Discussi

Re: SysRexx and WAIT program not working

2018-01-21 Thread Seymour J Metz
No. address LINKMVS "JOBZWAIT wait_value", address LINK "JOBZWAIT" 120 and address LINK "JOBZWAIT" wait_value are appropriate, but not address LINKMVS "JOBZWAIT" wait_value. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainfra

CBT Tape URL is www.cbttape.org

2018-01-21 Thread Sam Golob
Hi Folks,     Most people know the URL for the CBT Tape, but in case somebody doesn't know it, it's www.cbttape.org.  There may be some people who are new to this list, and who don't (yet) know that they can get many marvelous tools for z/OS there (all for free).  (Of course, all disclaimers

Re: SysRexx and WAIT program not working

2018-01-21 Thread Paul Gilmartin
On Sun, 21 Jan 2018 09:48:22 -0600, Paul Gilmartin wrote: >> >I've used LINKMVS lots, but in plain Rexx, not SysRexx. I'd use: > >wait_value = 120 >address LINKMVS "JOBZWAIT" "wait_value" > >The first argument is the name of the program. Additional arguments are >*names* of Rexx variable

The Arcati Mainframe Yearbook 2018 – Now Available

2018-01-21 Thread Mark Regan
https://it.toolbox.com/blogs/trevoreddolls/the-arcati-mainframe-yearbook-2018-now-available-012018 -- Regards, Mark T. Regan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.

Re: SysRexx and WAIT program not working

2018-01-21 Thread Paul Gilmartin
On Sat, 20 Jan 2018 20:34:33 -0500, Tony Thigpen wrote: > >When I try to call it from a SysRexx program, it fails: > > 22 *-* wait_value = 120 >>L> "120" > 23 *-* address LINKMVS "JOBZWAIT wait_value" >>L> "JOBZWAIT wait_value" >+++ RC(-3) +++ > >While I write a

Re: SysRexx and WAIT program not working

2018-01-21 Thread Steve Horein
If you call PGM=MPFZWAIT in batch, why are you attempting to LINKMVS to program JOBZWAIT? On Sat, Jan 20, 2018 at 7:34 PM, Tony Thigpen wrote: > I am trying to get a SysRexx command to wait between several steps. I am > using the TSO=YES option on the AXREXX macro. The wait program is in the >

Re: SysRexx and WAIT program not working

2018-01-21 Thread Don Poitras
And you were correct when you first wrote it. You want "JOBZWAIT 120", not "JOBZWAIT wait_value". It looks as though LINKMVS isn't available in your environment. --- If the REXX exec uses the ADDRESS name instruction, and the value name in not in the table, no error is detected. However, when t

Re: SysRexx and WAIT program not working

2018-01-21 Thread Tony Thigpen
Actually, that is how I first wrote it. 25 *-* address LINKMVS "JOBZWAIT" wait_value >L> "JOBZWAIT" >V> "120" >O> "JOBZWAIT 120" +++ RC(-3) +++ I changed it to the "variable name in the quotes" based on examples in the manual. Tony Thigpen Don Poitras wr