In 2445830881854866.wa.paulgboulderaim@listserv.ua.edu, on
03/17/2014
at 11:03 AM, Paul Gilmartin paulgboul...@aim.com said:
No, and no. LINKMVS prefixes the programmer-supplied parameter
with a halfword length field and passes the result as a single
parameter to the called program.
On Mon, 17 Mar 2014 18:49:15 -0400, Shmuel Metz (Seymour J.) wrote:
on 03/17/2014 at 11:03 AM, Paul Gilmartin said:
No, and no. LINKMVS prefixes the programmer-supplied parameter
with a halfword length field and passes the result as a single
parameter to the called program.
Still not right;
In
cc42e2f56d60f24fb8a6bcc639d1d9632c665...@samtcasxmb13.usa.dce.usps.gov,
on 03/14/2014
at 09:01 PM, Hansen, Dave L - Eagan, MN dave.l.han...@usps.gov
said:
Sorry for the delay. We don't have ISRSUPC in the SYS1.LPALIB. LINK
worked, but I didn't figure out the error.
I gave you the wrong
On Mon, 17 Mar 2014 10:34:05 -0400, Shmuel Metz (Seymour J.) wrote:
I am not sure what LINKPGM would do for me.
It would start the parameter with a halfword length field instead of
passing the length as a separate parameter.
No, and no. LINKMVS prefixes the programmer-supplied parameter
with
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Friday, March 07, 2014 5:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
On Fri, 7 Mar 2014 22:41:44 +, Hansen, Dave L - Eagan, MN wrote:
44 *-* /* CALL *(ISRSUPC
In 6209480351328263.wa.paulgboulderaim@listserv.ua.edu, on
03/09/2014
at 06:51 PM, Paul Gilmartin paulgboul...@aim.com said:
A string containing an unmatched apostrophe.
%member 'foo
should work just fine.
And it was in an ISPSTART context;
Then you're dealing with ISPF issues, not
On Sun, 9 Mar 2014 23:41:12 -0400, Shmuel Metz (Seymour J.) wrote:
And it was in an ISPSTART context;
Then you're dealing with ISPF issues, not just REXX and TSO issues; it
has nothing to do with what % allows. Try, at the command line,
%rexx say arg(1); exit; '
Yes, but I never claimed it
In 7695529832117020.wa.paulgboulderaim@listserv.ua.edu, on
03/10/2014
at 10:04 AM, Paul Gilmartin paulgboul...@aim.com said:
Yes, but I never claimed it was just REXX and TSO issues, merely
that there was a context in which EXEC worked but '%' didn't.
No, what you claimed was There are
On Sun, 9 Mar 2014 08:52:02 -0400, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
on 03/08/2014 at 09:07 PM, Paul Gilmartin said:
The syntactic restrictions are different. There are parameter
strings that I can pass with EXEC that % disallows.
Such as?
A string containing an
On Fri, 7 Mar 2014 17:56:05 -0600, Paul Gilmartin paulgboul...@aim.com wrote:
On Fri, 7 Mar 2014 22:41:44 +, Hansen, Dave L - Eagan, MN wrote:
44 *-* /* CALL *(ISRSUPC) */
45 *-* CALL *(ISRSUPC) 'FILECMP,DELTAL'
L CALL *(ISRSUPC) 'FILECMP,DELTAL'
I was told by IBM I
In
cc42e2f56d60f24fb8a6bcc639d1d9632c658...@samtcasxmb13.usa.dce.usps.gov,
on 03/07/2014
at 10:41 PM, Hansen, Dave L - Eagan, MN dave.l.han...@usps.gov
said:
I was told by IBM I don't have ISRSUPC in the SYS1.LPALIB.
That shouldn't matter. From z/OS TSO/E Command Reference,
SA22-7782-11:
In 3530218517098767.wa.paulgboulderaim@listserv.ua.edu, on
03/08/2014
at 10:28 AM, Paul Gilmartin paulgboul...@aim.com said:
Of course, LINKMVS supports multiple parameters, such as alternate
DDNAME lists; I don't know that CALL does this.
It does not.
with LINKMVS I can pass a parameter
: Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
In 9380636879776208.wa.paulgboulderaim@listserv.ua.edu, on
03/06/2014
at 04:20 PM, Paul Gilmartin paulgboul...@aim.com said:
So, in Rexx:
address TSO call *(ISRSUPC) 'FILE'
That will work, but it's overkill. Why not use
weekend, Dave
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Shmuel Metz (Seymour J.)
Sent: Friday, March 07, 2014 2:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR
On Fri, 7 Mar 2014 22:41:44 +, Hansen, Dave L - Eagan, MN wrote:
44 *-* /* CALL *(ISRSUPC) */
45 *-* CALL *(ISRSUPC) 'FILECMP,DELTAL'
L CALL *(ISRSUPC) 'FILECMP,DELTAL'
I was told by IBM I don't have ISRSUPC in the SYS1.LPALIB. I had to use
LINKMVS to get it to work.
Dave,
Here is a rexx exec to invoke ISRSUPC in rexx
/* REXX */
ADDRESS TSO
ALLOC FI(NEWDD) DA('PMSBDH.VPS.LRS.AFP.V2R10.FDEFLIB') SHR
ALLOC FI(OLDDD) DA('VPS.LRS.VPS.V2R10.FDEFLIB') SHR
ALLOC DD(OUTDD) DA(*) REU
ALLOC F(SYSIN) DUMMY REUSE
CALL *(ISRSUPC) 'FILECMP,DELTAL'
FREE FI(NEWDD
Dave, I don't see an ALLOC for DD SYSPRINT in the ISRSUPC code. Note the text
of the error for that RC=24 seems to agree:
RC 24 is ERROR. I/O Error writing to the **output listing file**
(emphasis mine)
HTH
Peter
-Original Message-
From: IBM Mainframe Discussion List
In
cc42e2f56d60f24fb8a6bcc639d1d9632c657...@samtcasxmb13.usa.dce.usps.gov,
on 03/06/2014
at 10:01 PM, Hansen, Dave L - Eagan, MN dave.l.han...@usps.gov
said:
address TSO alloc fi(newdd) da('A3ZP.PROD.CICS(pgm)') shr reu
address TSO alloc fi(olddd) da('A3WD.APPROD3.CICS(pgm)') shr
18 matches
Mail list logo
