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 Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of 
Seymour J Metz <sme...@gmu.edu>
Sent: Sunday, January 21, 2018 2:21 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: SysRexx and WAIT program not working

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 <IBM-MAIN@listserv.ua.edu> on behalf of Don 
Poitras <poit...@pobox.com>
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:
> >> //WAIT1    EXEC 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-5637                Cary, 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

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

Reply via email to