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, in both systems. But, MPFZWAIT does not require a 
STEPLIB while JOBZWAIT requires a STEPLIB.


I put the wrong name in the test SysRexx.

(To answer another question asked)
MPFZWAIT is in a LNKLST library. When I typed LLF, I was tired and 
thinking about the F LLA,REFRESH command I use for this program.


Tony Thigpen

Steve Horein wrote on 01/21/2018 03:59 PM:

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: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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.edu>
Sent: Sunday, January 21, 2018 4:41 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: SysRexx and WAIT program not working

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 'address LINKMVS "JOBZWAIT 120"'.  The OP correctly coded:
>> >>  22 *-* wait_value = 120
>> >>  23 *-* address LINKMVS "JOBZWAIT wait_value"
... and Rexx echoes the command as:
>> >> >L>   "JOBZWAIT wait_value"

The question of MPFZWAIT versus JOBZWAIT remains unanswered.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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 'address LINKMVS "JOBZWAIT 120"'.  The OP correctly coded:
>> >>  22 *-* wait_value = 120
>> >>  23 *-* address LINKMVS "JOBZWAIT wait_value"
... and Rexx echoes the command as:
>> >> >L>   "JOBZWAIT wait_value"

The question of MPFZWAIT versus JOBZWAIT remains unanswered.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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.
>
>From:  Seymour J Metz
>Sent: Sunday, January 21, 2018 2:21 PM
>
>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.
>
Note that LINKMVS provides the parameter list most similar to the classic OS 
CALL.

Grrr.  SUBCOM is supposed to help here, but I read:
z/OSIBM TSO/E REXX Reference Version 2 Release 3
SA32-0972-30
Chapter 10. TSO/E REXX commands
►► SUBCOM envname   ►◄
queries the existence of a specified host command environment. ...
You can use the SUBCOM command in REXX execs that run in both the TSO/E 
address space and non-TSO/E address spaces.

English usage:  While this suggests that I can use the SUBCOM command in REXX 
execs
that run in both the TSO/E address space and non-TSO/E address spaces, it 
doesn't say
that I can use SUBCOM in execs that run in only one of the two but not the 
other.

I'll submit an RCF.

And SUBCOM is itself a command, which means it must be issued to a command
environment.  Do all non TSO/E command environments support SUBCOM?
In a Rexx exec running in an OMVS address space, can I:
address SH 'SUBCOM MVS'
address SH 'SUBCOM SH'
???

It's dismaying that RC==-3 is issued both for invalid environment and for 
invalid
command within invalid environment.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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". What IFAUSAGE reports is, in general, up to the exploiter. 
And for IFAEDREG there is no necessary relationship between the number of 
invocations of IFAEDREG and the number of times that a product was run.


Would I be correct in inferring from that that subtype 1 might be more
appropriate for a "long-running service" product like CICS, while subtype 
2
would be more appropriate for a "batch" type product like, for example, a
compiler or utility?

I'd say "no". "Appropriateness" is not relevant to these cases. The choice 
is a business decision.

Your questions make me fear that you want to do something beyond what is 
documented with these records. I hope my fear is misplaced. You do know 
that SCRT pays attention to these records. If there is something specific 
that is not documented, we could consider documenting it.

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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: INFO IBM-MAIN

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 
followed by the parameter.. 

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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 Mainframe Discussion List  on behalf of Don 
Poitras 
Sent: Sunday, January 21, 2018 8:29 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: SysRexx and WAIT program not working

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 the language processor tries to locate the
entry in the table to pass a command and no corresponding entry is
found, the language processor returns with a return code of -3, which
indicates an error condition.
---

It says to use IRXSUBCM to query the host command name, but since you
would normally run that with LINKMVS, I don't see how you can. Are you
sure that JOBZWAIT is in your tasklib?

In article <5a647d33.8030...@vse2pdf.com> you wrote:
> 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 wrote on 01/20/2018 10:14 PM:
> > In article <5a63ee29.7020...@vse2pdf.com> you 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
> >> LLA and does work. In batch, the program is used as:
> >> //WAIT1EXEC PGM=MPFZWAIT,PARM='120'
> >> //SYSUDUMP DD   SYSOUT=*
> >> //*
> >> 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 lot of Rexx on VM, my expereance with Rexx on z/OS is
> >> minimal, so I might be doing something really stupid.
> >> Thoughts?
> >> --
> >> Tony Thigpen
> >
> > Try:
> >
> > address LINKMVS "JOBZWAIT" wait_value
> >

--
Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
sas...@sas.com   (919) 531-5637Cary, NC 27513

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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 apply, but we try and keep things as reliable as we can.  We 
work very hard at it.)


    All the best

Sam G

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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 variables containing parameter values.
>
I stand corrected.  In working code I have:
address 'ATTCHMVS' 'IEBGENER PARM1 PARM2'
(... but concatenation by abutment makes that equivalent.)

So, the OP seems correct.  Does SysRexx support LINKMVS?  Is the needed
object in LNKLIST (or TASKLIB/STEPLIB)?  What happens with:
address LINKMVS "IEFBR14"?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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.edu with the message: INFO IBM-MAIN

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
> LLA and does work. In batch, the program is used as:
>
> //WAIT1EXEC PGM=MPFZWAIT,PARM='120'
> //SYSUDUMP DD   SYSOUT=*
> //*
>
> 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 lot of Rexx on VM, my expereance with Rexx on z/OS is
> minimal, so I might be doing something really stupid.
>
> Thoughts?
>
> --
> Tony Thigpen
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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 the language processor tries to locate the
entry in the table to pass a command and no corresponding entry is
found, the language processor returns with a return code of -3, which
indicates an error condition.  
---

It says to use IRXSUBCM to query the host command name, but since you
would normally run that with LINKMVS, I don't see how you can. Are you
sure that JOBZWAIT is in your tasklib?

In article <5a647d33.8030...@vse2pdf.com> you wrote:
> 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 wrote on 01/20/2018 10:14 PM:
> > In article <5a63ee29.7020...@vse2pdf.com> you 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
> >> LLA and does work. In batch, the program is used as:
> >> //WAIT1EXEC PGM=MPFZWAIT,PARM='120'
> >> //SYSUDUMP DD   SYSOUT=*
> >> //*
> >> 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 lot of Rexx on VM, my expereance with Rexx on z/OS is
> >> minimal, so I might be doing something really stupid.
> >> Thoughts?
> >> --
> >> Tony Thigpen
> >
> > Try:
> >
> > address LINKMVS "JOBZWAIT" wait_value
> >

-- 
Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
sas...@sas.com   (919) 531-5637Cary, NC 27513

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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 wrote on 01/20/2018 10:14 PM:

In article <5a63ee29.7020...@vse2pdf.com> you 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
LLA and does work. In batch, the program is used as:
//WAIT1EXEC PGM=MPFZWAIT,PARM='120'
//SYSUDUMP DD   SYSOUT=*
//*
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 lot of Rexx on VM, my expereance with Rexx on z/OS is
minimal, so I might be doing something really stupid.
Thoughts?
--
Tony Thigpen


Try:

address LINKMVS "JOBZWAIT" wait_value



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN