Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-18 Thread Paul Gilmartin 
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; we both had it wrong. From z/OS TSO/E REXX Reference,
>SA22-7790-08:
>
> 2.5.9.2  The LINKMVS and ATTCHMVS host command environments
>
>   For the LINKMVS and ATTCHMVS environments, you can pass multiple
>   parameters to the program.
> 
C 'the' 'each' first

-- gil

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-18 Thread Shmuel Metz (Seymour J.) 
In <2445830881854866.wa.paulgboulderaim@listserv.ua.edu>, 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; we both had it wrong. From z/OS TSO/E REXX Reference,
SA22-7790-08:

 2.5.9.2  The LINKMVS and ATTCHMVS host command environments

   For the LINKMVS and ATTCHMVS environments, you can pass multiple
   parameters to the program.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-17 Thread Paul Gilmartin 
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 a halfword length field and passes the result as a single parameter
to the called program.  LINKPGM passes the programmer-supplied
parameter as-is to the called program (of course, nothing prevents
the programmer's supplying a halfword length field), and passes
that to the called program as a single parameter.  Neither passes
the length as a separate parameter.  "Address LINK" is entirely
different; I am not sure what "address LINK" would do for me.

SYS1.SAMPLIB contains an ICSF sample using LINKPGM.

-- gil

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-17 Thread Shmuel Metz (Seymour J.) 
In
,
on 03/14/2014
   at 09:01 PM, "Hansen, Dave L - Eagan, MN" 
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 environment; it should have been LINKMVS rather
than LINK. Sorry.

>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.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-14 Thread Hansen, Dave L - Eagan, MN 
Gil,

   Sorry for the delay.  We don't have ISRSUPC in the SYS1.LPALIB.  LINK 
worked, but I didn't figure out the error.

   LINKMVS has not failed in either of the two EXECs I used them in.

 

   ISRSUPC will work with a LINK:

   49 *-* address LINK ISRSUPC 'FILECMP,DELTAL'
   >L>   "ISRSUPC"
   >L>   "FILECMP,DELTAL"
   >O>   "ISRSUPC FILECMP,DELTAL"
  ISRSUPC   -   MVS/PDF FILE/LINE/WORD/BYTE/SFOR COMPARE UTILITY- ISPF FOR z/OS
2014/03/07  11.02PAGE 1

   Right now I don’t know why I’m getting this warning.  Perhaps SYSIN needs 
something in it? 

   ISRS010W "::  " PROCESS OPTION PARAMETER IS NOT A VALID PROCESS OPTION. 
IT
IS IGNORED.

+++ RC(4) +++


   The examples from Sri work great!  They use LINKMVS.  I am not sure what 
LINKPGM would do for me.


  Thanks,  Dave



-Original Message-
From: IBM Mainframe Discussion List [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)"   */
>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.  CALL will just hang.
> 
Were they right?  Does LINKMVS succeed in cases where CALL * fails?

"Just hang"?  No message?  No ABEND?  ...

I had thought that CALL* uses the same TASKLIB/STEPLIB(/ISPLLIB) search order 
as LINKMVS.

Did it at least get you to just hang up the phone for a while?

-- 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: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-10 Thread Shmuel Metz (Seymour J.) 
In <7695529832117020.wa.paulgboulderaim@listserv.ua.edu>, on
03/10/2014
   at 10:04 AM, Paul Gilmartin  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 parameter strings that I can pass
with EXEC that % disallows."
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-10 Thread Paul Gilmartin 
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 was "just REXX and TSO issues",
merely that there was a context in which EXEC worked but '%'
didn't.  And I was wishing for "EXEC *(MEMBER) ..." to avoid the
need to fully qualify the path.

And, yes, I'd also wish for more permissive ISPF syntax.  A
scheme for escaping metacharacters would go a long way.

-- gil

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-10 Thread Shmuel Metz (Seymour J.) 
In <6209480351328263.wa.paulgboulderaim@listserv.ua.edu>, on
03/09/2014
   at 06:51 PM, Paul Gilmartin  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 just REXX and TSO issues; it
has nothing to do with what % allows. Try, at the command line,

%rexx say arg(1); exit; '

assuming that user.clist(rexx) doesn't use any ISPF services.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-09 Thread Paul Gilmartin 
On Sun, 9 Mar 2014 08:52:02 -0400, Shmuel Metz (Seymour J.) 
 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 unmatched apostrophe.  It's been a long time;
I can only re-create with a pointless example.  Here's my REXX exec:

/* REXX Useful! */ interpret arg(1)

And it was in an ISPSTART context; something like:

ispstart cmd( exec 'user.clist(rexx)' 'say arg( 1 ); exit; ''' )

which prints:

READY
ispstart cmd( exec 'user.clist(rexx)' 'say arg( 1 ); exit; ''' )
 say arg( 1 ); exit; '
 ***

Note the single apostrophe in the output.  I don't remember why I
needed that apostrophe (or something similar), but I can get it with
EXEC, not with '%'

-- gil

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-09 Thread Shmuel Metz (Seymour J.) 
In <2098713607740788.wa.paulgboulderaim@listserv.ua.edu>, 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?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-08 Thread Paul Gilmartin 
On Sat, 8 Mar 2014 20:50:37 -0500, Shmuel Metz (Seymour J.) wrote:
>
>>(On occasion, I've wished for an analogous "EXEC *(MEMBER)".)
>
>%MEMBER
> 
No.  The syntactic restrictions are different.  There are parameter
strings that I can pass with EXEC that % disallows.

-- gil

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-08 Thread Shmuel Metz (Seymour J.) 
In <3530218517098767.wa.paulgboulderaim@listserv.ua.edu>, on
03/08/2014
   at 10:28 AM, Paul Gilmartin  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 consisting of a single
>apostrophe; I don't know how to do this with CALL.  (Perhaps 
>"call *(IEFBR14) "?). 

That looks right.

>But you can use the magic SVC, if you've installed it, to twiddle 
>the AUTH bit.

It's not my dog!

>Isn't LPA always in LINKLIST?

No.

>(On occasion, I've wished for an analogous "EXEC *(MEMBER)".)

%MEMBER
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-08 Thread Shmuel Metz (Seymour J.) 
In
,
on 03/07/2014
   at 10:41 PM, "Hansen, Dave L - Eagan, MN" 
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:

   *
   specifies that CALL should use the standard load module
   search sequence for the member name.

>From z/OS MVS Programming: Assembler Services Guide, SA22-7605-1,
1.4.6.1.2  The Search for the Load Module:

   In response to your request for a copy of a load module, the
   control program searches the task's load list and the job pack
   area . If a copy of the load module is found, the control
   program determines whether that copy can be used (see "Using an
   Existing Copy").  If an existing copy can be used, the search
   stops. If it cannot be used, the search continues until the
   module is located in a library or the link pack area . The load
   module is then brought into the job pack area or placed into the
   load list.

--
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-08 Thread Paul Gilmartin 
On Sat, 8 Mar 2014 05:42:47 -0600, Walt Farrell wrote:
>
>It does seem odd that the CALL command would simply hang. But yes, I believe 
>that LINKMVS will work in cases where CALL won't. 
> 
Of course, LINKMVS supports multiple parameters, such as alternate DDNAME
lists; I don't know that CALL does this.  And there are syntactic limitations.  
I
know that with LINKMVS I can pass a parameter consisting of a single apostrophe;
I don't know how to do this with CALL.  (Perhaps "call *(IEFBR14) "?).  And
CALL limits me to 100 bytes in the parameter; LINKMVS allows 32767.  (With
LINKPGM, I can craft longer parameters -- I've tested with 65535 with BPXBATCH,
which appears to treat the count as unsigned.  Don't try this with ASMA90!)

And there's the APF concern.  IIRC, I've been compelled to use CALL because
CALL will ATTCH a module authorized (subject to restrictions discussed earlier
in this thread; LINKMVS always ATTACHes unauthorized.  But you can use
the magic SVC, if you've installed it, to twiddle the AUTH bit.

>I also believe that Dave meant "I was told by IBM that I _have_ ISRSUPC in 
>SYS1.LPALIB, rather than _don't have_.  CALL expects to find its target in the 
>standard library search order (Tasklib (including STEPLIB/JOBLIB), Linklist) 
>and I do not think it will find a module that is only in LPA. LINKMVS (also 
>LINK, LINKPGM, and probably the ATTACH variants) will find things that are 
>only in LPA, and I believe that explains why LINKMVS worked for him.
> 
I had (mis-)understood that "CALL DATA.SET.NAME(MODULE)" simply
allocates DATA.SET.NAME as a tasklib and performs a conventional
ATTACH.  "CALL *(MODULE)" performs no additional allocation,but uses
the existing search order.  Isn't LPA always in LINKLIST?  Is there any
way to exclude modules in LPA?

What have I misunderstood?

(On occasion, I've wished for an analogous "EXEC *(MEMBER)".)

-- gil

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-08 Thread Walt Farrell 
On Fri, 7 Mar 2014 17:56:05 -0600, Paul Gilmartin  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 don't have ISRSUPC in the SYS1.LPALIB.  I had to use 
>> LINKMVS to get it to work.  CALL will just hang.
>> 
>Were they right?  Does LINKMVS succeed in cases where CALL * fails?
>
>"Just hang"?  No message?  No ABEND?  ...
>
>I had thought that CALL* uses the same TASKLIB/STEPLIB(/ISPLLIB) search
>order as LINKMVS.
>
>Did it at least get you to just hang up the phone for a while?

It does seem odd that the CALL command would simply hang. But yes, I believe 
that LINKMVS will work in cases where CALL won't. 

I also believe that Dave meant "I was told by IBM that I _have_ ISRSUPC in 
SYS1.LPALIB, rather than _don't have_.  CALL expects to find its target in the 
standard library search order (Tasklib (including STEPLIB/JOBLIB), Linklist) 
and I do not think it will find a module that is only in LPA. LINKMVS (also 
LINK, LINKPGM, and probably the ATTACH variants) will find things that are only 
in LPA, and I believe that explains why LINKMVS worked for him.

-- 
Walt

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-07 Thread Paul Gilmartin 
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.  CALL will just hang.
> 
Were they right?  Does LINKMVS succeed in cases where CALL * fails?

"Just hang"?  No message?  No ABEND?  ...

I had thought that CALL* uses the same TASKLIB/STEPLIB(/ISPLLIB) search
order as LINKMVS.

Did it at least get you to just hang up the phone for a while?

-- gil

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-07 Thread Hansen, Dave L - Eagan, MN 
Seymour,

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.  CALL will just hang.


  Thank you and have a good 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)

In
,
on 03/07/2014
   at 03:35 PM, "Hansen, Dave L - Eagan, MN" 
said:

>I don't know why CALL isn't working for me.

You seem to be missing a space. Try

"CALL *(ISRSUPC) 'FILECMP,DELTAL'"
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
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: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-07 Thread Shmuel Metz (Seymour J.) 
In
,
on 03/07/2014
   at 03:35 PM, "Hansen, Dave L - Eagan, MN" 
said:

>I don't know why CALL isn't working for me.

You seem to be missing a space. Try

"CALL *(ISRSUPC) 'FILECMP,DELTAL'"
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-07 Thread Hansen, Dave L - Eagan, MN 
Mr. Metz,

   Thank you for suggesting LINK.  I don't know why CALL isn't working for me.  
I have ADDRESS TSO at the start of my EXEC.

 48 *-* "CALL *(ISRSUPC)'FILECMP,DELTAL'"
>L>   "CALL *(ISRSUPC)'FILECMP,DELTAL'"
 INVALID DATA SET NAME, *(ISRSUPC)'FILECMP
 INVALID KEYWORD, DELTAL'
+++ RC(12) +++



   Kolusu, 

   I tried your link and it took me to appendix A in the ISPF Users Guide.  I 
tried searching for FILECMP and DELTAL.  I didn't find any information on these.

   I looked at the samples and the JCL has PARM=(DELTAL,LINECMP,'','').  I 
searched the whole users guide for LINECMP and only found this "//COMPARE EXEC 
PGM=ISRSUPC,PARM=('LINECMP,CHNGL,UPDCNTL')".  

Q).  Where can I find information on DELTAL and FILECMP?  I tried using 
CYTPE(FILE) but I get INVALID KEYWORD, CTYPE(FILE).  SUPERC offers four compare 
levels.  What book am I missing?



address LINK ISRSUPC 'FILECMP,DELTAL'
ISRS010W "::  " PROCESS OPTION PARAMETER IS NOT A VALID PROCESS OPTION. IT 
IS IGNORED.
+++ RC(4) +++

Q).  RC 4 is a warning.  Erroneous input detected.  I looked at Table 24. 
Summary of process options.  I didn't see any that stood out.  Do I need a 
Process Option?  What do I need to do to get past the RC 4?


  At least it's Friday,  Dave



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Shmuel Metz (Seymour J.)
Sent: Thursday, March 06, 2014 8:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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  said:

>So, in Rexx:
>address TSO "call *(ISRSUPC) 'FILE'"

That will work, but it's overkill. Why not use

   address LINK ISRSUPC 'FILE'

instead?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
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: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-06 Thread Paul Gilmartin 
On Thu, 6 Mar 2014 21:42:39 -0500, Shmuel Metz (Seymour J.) wrote:

> on 03/06/2014  at 04:20 PM, Paul Gilmartin said:
>
>>So, in Rexx:
>>address TSO "call *(ISRSUPC) 'FILE'"
>
>That will work, but it's overkill. Why not use
>
>   address LINK ISRSUPC 'FILE'
>
>instead?
> 
Indeed.  I was trying not to stray too far from the OP's paradigm.
But what you suggest avoids the TSO prerequisite.

There are:
address LINK
address LINKPGM
address LINKMVS

The last is compatible with JCL "EXEC PGM=...".
The last two are compatible with Assembler CALL macro.

I'd use LINKMVS.

-- gil

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-06 Thread Shmuel Metz (Seymour J.) 
In <9380636879776208.wa.paulgboulderaim@listserv.ua.edu>, on
03/06/2014
   at 04:20 PM, Paul Gilmartin  said:

>So, in Rexx:
>address TSO "call *(ISRSUPC) 'FILE'"

That will work, but it's overkill. Why not use

   address LINK ISRSUPC 'FILE'

instead?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-06 Thread Shmuel Metz (Seymour J.) 
In
,
on 03/06/2014
   at 10:01 PM, "Hansen, Dave L - Eagan, MN" 
said:

> address TSO "alloc fi(newdd) da('A3ZP.PROD.CICS("pgm")') shr reu"

> address TSO "alloc fi(olddd) da('A3WD.APPROD3.CICS("pgm")') shr reu"  

What about the rest of the allocations?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: 0C4 from TSOEXEC IEBCOMPR

2014-03-06 Thread Shmuel Metz (Seymour J.) 
In
,
on 03/06/2014
   at 03:43 PM, "Hansen, Dave L - Eagan, MN" 
said:

>I would like to automate comparing a bunch of FONT libs.

 1. the SuperC panels have an option to generate a batch job.
Use it and look at the generated JCL

 2. What did you allocate before invoking ISRSUPC?

 3. What is in your EXEC? You only gave the failing line.

>I tried "TSOEXEC ISRSUPC" in my EXEC. 

Why? It's for commands.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-06 Thread Farley, Peter x23353 
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 [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Hansen, Dave L - Eagan, MN
Sent: Thursday, March 06, 2014 5:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

Dear Group,

   Ok, I got IEBCOMPR to work:

"ALLOC FI(SYSUT1) DA('PMSBDH.VPS.LRS.AFP.V2R10.FDEFLIB') SHR"
"ALLOC FI(SYSUT2) DA('VPS.LRS.VPS.V2R10.FDEFLIB') SHR"
"ALLOC DD(SYSPRINT) DA(*) REU"
"ALLOC DD(SYSIN) RECFM(F B) LRECL(80) NEW REU"
QUEUE " COMPARE TYPORG=PO"
"EXECIO" queued() "DISKW SYSIN (FINIS"
"CALL *(IEBCOMPR)"
CC=RC
if cc <> 0 Then Do
SAY "IEBCOMPR FAILED FOR AFP.V2R10.FDEFLIB"
...
"FREE FI(SYSUT1 SYSUT2 SYSIN SYSPRINT)"

   With IEBCOMPR I look for a RC of 0.



   I found this site:  
http://computer-programming-forum.com/38-rexx/35af2e8f164fb280.htm and this 
EXEC:

/*   test si version prod et approd identique  */ 
say "Test si version PROD et APPROD identique "   
 address TSO "alloc fi(newdd) da('A3ZP.PROD.CICS("pgm")') shr reu" 
 address TSO "alloc fi(olddd) da('A3WD.APPROD3.CICS("pgm")') shr reu" 
 address tso "call *(isrsupc)" 
 if rc =  0 then   
   do 
 say "version identique." 
   end 
   else   
   do 
 say "! VERSION PROD APPROD DIFFERENTES !" 
 exit 
   end

   Mostly this just hangs for me, but once I did get an RC of 24. In the 
ISPF User's Guide it says RC 24 is ERROR.  I/O Error writing to the output 
listing file.  

Q).  Does this Example need some more work?  

  


   I found some doc that said ISRSUPC was documented in the ISPF User guide. 
Vol 2.  I have been looking for where the KEYWORDS are listed for ISRSSUPC.  In 
appendix A they list some stuff.

   It says: "The keywords and parameters are:"
  "CTYPE Specifies the compare type.  The parameter can be one 
of the SuperC compare types (File, Line, Word, or Byte).  To call the 
Search-For program, use CTYPE(SRCH)".
  "PROCESS  Specifies the process options"
   OK, I want ISRSUPC to use a CTYPE of FILE to do a file level compare.


   I tried:

  "CALL *(ISRSUPC)" "FILE"
INVALID KEYWORD, FILE

  "CALL *(ISRSUPC)" "CTYPE(FILE)"
INVALID KEYWORD, CTYPE(FILE)FILE

   I saw PGM=ISRSUPC),PARM=(DELTAL,LINECMP,'','').  So I tried:

 "CALL *(ISRSUPC) FILECMP"
INVALID KEYWORD, FILECMP


Q).  Where are the Keyword and Parameters for SUPERC (aka ISRSUPC) found?


   Thanks again,  Dave

  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sri h Kolusu
Sent: Thursday, March 06, 2014 12:29 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: 0C4 from TSOEXEC IEBCOMPR

Q. Do IEBCOMPR and ISRSUPC both support alternate DDName lists?)

Paul,

I do believe IEBCOMPR can be invoked using alternate DDname list(example shown 
below), but with ISRSUPC I get RC of 24

/* REXX - Invoke IEBCOMPR With alternate DDnames.   */ 
"ALLOC FI(PDS1) DA('KOLUSU.PMR66403.JCL') SHR" 
"ALLOC FI(PDS2) DA('KOLUSU.PMR66403.JCL') SHR" 
"ALLOC DD(REP) DA(*) REU" 
"ALLOC DD(CTL) NEW REU RECFM(F B) LRECL(80)" 
QUEUE "  COMPARE TYPORG=PO " 
"EXECIO "QUEUED()" DISKW CTL (FINIS" 
PROG   = 'IEBCOMPR' 
PARM   = ''   /* STANDARD PARM, AS FROM JCL   */
DDLIST = COPIES('00'X,8) ||,  /* DDNAME  1 OVERRIDE: SYSLIN   */
 COPIES('00'X,8) ||,  /* DDNAME  2 OVERRIDE:  N/A */
 COPIES('00'X,8) ||,  /* DDNAME  3 OVERRIDE: SYSLMOD  */
 COPIES('00'X,8) ||,  /* DDNAME  4 OVERRIDE: SYSLIB   */
 LEFT('CTL',  8) ||,  /* DDNAME  5 OVERRIDE: SYSIN*/
 LEFT('REP',  8) ||,  /* DDNAME  6 OVERRIDE: SYSPRINT */
 COPIES('

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-06 Thread Sri h Kolusu 
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 OLDDD SYSIN OUTDD)" 


Check this link for SUPERC reference

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ISPZU290/A.0?


Kolusu

IBM Mainframe Discussion List  wrote on 
03/06/2014 02:01:36 PM:

> From: "Hansen, Dave L - Eagan, MN" 
> To: IBM-MAIN@listserv.ua.edu, 
> Date: 03/06/2014 02:02 PM
> Subject: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
> Sent by: IBM Mainframe Discussion List 
> 
> Dear Group,
> 
>Ok, I got IEBCOMPR to work:
> 
> "ALLOC FI(SYSUT1) DA('PMSBDH.VPS.LRS.AFP.V2R10.FDEFLIB') SHR"
> "ALLOC FI(SYSUT2) DA('VPS.LRS.VPS.V2R10.FDEFLIB') SHR"
> "ALLOC DD(SYSPRINT) DA(*) REU"
> "ALLOC DD(SYSIN) RECFM(F B) LRECL(80) NEW REU"
> QUEUE " COMPARE TYPORG=PO"
> "EXECIO" queued() "DISKW SYSIN (FINIS"
> "CALL *(IEBCOMPR)"
> CC=RC
> if cc <> 0 Then Do
> SAY "IEBCOMPR FAILED FOR AFP.V2R10.FDEFLIB"
> ...
> "FREE FI(SYSUT1 SYSUT2 SYSIN SYSPRINT)"
> 
>With IEBCOMPR I look for a RC of 0.
> 
> 
> 
>I found this site:  http://computer-programming-forum.com/38-
> rexx/35af2e8f164fb280.htm and this EXEC:
> 
> /*   test si version prod et approd identique  */  
> say "Test si version PROD et APPROD identique "  
>  address TSO "alloc fi(newdd) da('A3ZP.PROD.CICS("pgm")') shr reu"  
>  address TSO "alloc fi(olddd) da('A3WD.APPROD3.CICS("pgm")') shr reu"  
>  address tso "call *(isrsupc)"  
>  if rc =  0 then  
>do  
>  say "version identique."  
>end  
>else  
>do  
>  say "! VERSION PROD APPROD DIFFERENTES !"  
>  exit  
>end
> 
>Mostly this just hangs for me, but once I did get an RC of 24. 
> In the ISPF User's Guide it says RC 24 is ERROR.  I/O Error writing 
> to the output listing file. 
> 
> Q).  Does this Example need some more work? 
> 
> 
> 
> 
>I found some doc that said ISRSUPC was documented in the ISPF 
> User guide. Vol 2.  I have been looking for where the KEYWORDS are 
> listed for ISRSSUPC.  In appendix A they list some stuff.
> 
>It says: "The keywords and parameters are:"
>   "CTYPE Specifies the compare type.  The parameter 
> can be one of the SuperC compare types (File, Line, Word, or Byte). 
> To call the Search-For program, use CTYPE(SRCH)".
>   "PROCESS  Specifies the process options"
>OK, I want ISRSUPC to use a CTYPE of FILE to do a file level compare.
> 
> 
>I tried:
> 
>   "CALL *(ISRSUPC)" "FILE"
> INVALID KEYWORD, FILE
> 
>   "CALL *(ISRSUPC)" "CTYPE(FILE)"
> INVALID KEYWORD, CTYPE(FILE)FILE
> 
>I saw PGM=ISRSUPC),PARM=(DELTAL,LINECMP,'','').  So I tried:
> 
>  "CALL *(ISRSUPC) FILECMP"
> INVALID KEYWORD, FILECMP
> 
> 
> Q).  Where are the Keyword and Parameters for SUPERC (aka ISRSUPC) 
found?
> 
> 
>Thanks again,  Dave
> 
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU
> ] On Behalf Of Sri h Kolusu
> Sent: Thursday, March 06, 2014 12:29 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: 0C4 from TSOEXEC IEBCOMPR
> 
> Q. Do IEBCOMPR and ISRSUPC both support alternate DDName lists?)
> 
> Paul,
> 
> I do believe IEBCOMPR can be invoked using alternate DDname list
> (example shown below), but with ISRSUPC I get RC of 24
> 
> /* REXX - Invoke IEBCOMPR With alternate DDnames.   */ 
> "ALLOC FI(PDS1) DA('KOLUSU.PMR66403.JCL') SHR" 
> "ALLOC FI(PDS2) DA('KOLUSU.PMR66403.JCL') SHR" 
> "ALLOC DD(REP) DA(*) REU" 
> "ALLOC DD(CTL) NEW REU RECFM(F B) LRECL(80)" 
> QUEUE "  COMPARE TYPORG=PO " 
> "EXECIO "QUEUED()" DISKW CTL (FINIS" 
> PROG   = 'IEBCOMPR' 
> PARM   = ''   /* STANDARD PARM, AS FROM JCL   */
> DDLIST = COPIES('00'X,8) ||,  /* DDNAME  1 OVERRIDE: SYSLIN   */
>  COPIES('00'X,8) ||,  /* DDNAME  2 OVERRIDE:  N/A *

Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-06 Thread Paul Gilmartin 
On Thu, 6 Mar 2014 22:01:36 +, Hansen, Dave L - Eagan wrote:
>
>   I found this site:  
> http://computer-programming-forum.com/38-rexx/35af2e8f164fb280.htm and this 
> EXEC:
>  
> address tso "call *(isrsupc)" 
> if rc =  0 then   
>   do 
> say "version identique." 
>   end 
>   else   
>   do 
> say "! VERSION PROD APPROD DIFFERENTES !" 
> exit 
>   end


>   I found some doc that said ISRSUPC was documented in the ISPF User guide. 
> Vol 2.  I have been looking for where the KEYWORDS are listed for ISRSSUPC.  
> In appendix A they list some stuff.
>
>   It says: "The keywords and parameters are:"
>  "CTYPE Specifies the compare type.  The parameter can be one 
> of the SuperC compare types (File, Line, Word, or Byte).  To call the 
> Search-For program, use CTYPE(SRCH)".
>  "PROCESS  Specifies the process options"
>   OK, I want ISRSUPC to use a CTYPE of FILE to do a file level compare.
>
>
>   I tried:
>
>  "CALL *(ISRSUPC)" "FILE"
>INVALID KEYWORD, FILE
>
I suspect that's a TSO message.  For example:

 READY 
call *(IEFBR14)  whatever 
 IKJ56712I INVALID KEYWORD, WHATEVE
 IKJ56703A REENTER THIS OPERAND -

but:

 READY 
call *(IEFBR14) 'whatever'
 READY 

(You really should PROFILE MSGID to get more information.)

So, in Rexx:
address TSO "call *(ISRSUPC) 'FILE'"

(I think.)

-- gil

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

RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)

2014-03-06 Thread Hansen, Dave L - Eagan, MN 
Dear Group,

   Ok, I got IEBCOMPR to work:

"ALLOC FI(SYSUT1) DA('PMSBDH.VPS.LRS.AFP.V2R10.FDEFLIB') SHR"
"ALLOC FI(SYSUT2) DA('VPS.LRS.VPS.V2R10.FDEFLIB') SHR"
"ALLOC DD(SYSPRINT) DA(*) REU"
"ALLOC DD(SYSIN) RECFM(F B) LRECL(80) NEW REU"
QUEUE " COMPARE TYPORG=PO"
"EXECIO" queued() "DISKW SYSIN (FINIS"
"CALL *(IEBCOMPR)"
CC=RC
if cc <> 0 Then Do
SAY "IEBCOMPR FAILED FOR AFP.V2R10.FDEFLIB"
...
"FREE FI(SYSUT1 SYSUT2 SYSIN SYSPRINT)"

   With IEBCOMPR I look for a RC of 0.



   I found this site:  
http://computer-programming-forum.com/38-rexx/35af2e8f164fb280.htm and this 
EXEC:

/*   test si version prod et approd identique  */ 
say "Test si version PROD et APPROD identique "   
 address TSO "alloc fi(newdd) da('A3ZP.PROD.CICS("pgm")') shr reu" 
 address TSO "alloc fi(olddd) da('A3WD.APPROD3.CICS("pgm")') shr reu" 
 address tso "call *(isrsupc)" 
 if rc =  0 then   
   do 
 say "version identique." 
   end 
   else   
   do 
 say "! VERSION PROD APPROD DIFFERENTES !" 
 exit 
   end

   Mostly this just hangs for me, but once I did get an RC of 24. In the 
ISPF User's Guide it says RC 24 is ERROR.  I/O Error writing to the output 
listing file.  

Q).  Does this Example need some more work?  

  


   I found some doc that said ISRSUPC was documented in the ISPF User guide. 
Vol 2.  I have been looking for where the KEYWORDS are listed for ISRSSUPC.  In 
appendix A they list some stuff.

   It says: "The keywords and parameters are:"
  "CTYPE Specifies the compare type.  The parameter can be one 
of the SuperC compare types (File, Line, Word, or Byte).  To call the 
Search-For program, use CTYPE(SRCH)".
  "PROCESS  Specifies the process options"
   OK, I want ISRSUPC to use a CTYPE of FILE to do a file level compare.


   I tried:

  "CALL *(ISRSUPC)" "FILE"
INVALID KEYWORD, FILE

  "CALL *(ISRSUPC)" "CTYPE(FILE)"
INVALID KEYWORD, CTYPE(FILE)FILE

   I saw PGM=ISRSUPC),PARM=(DELTAL,LINECMP,'','').  So I tried:

 "CALL *(ISRSUPC) FILECMP"
INVALID KEYWORD, FILECMP


Q).  Where are the Keyword and Parameters for SUPERC (aka ISRSUPC) found?


   Thanks again,  Dave

  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Sri h Kolusu
Sent: Thursday, March 06, 2014 12:29 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: 0C4 from TSOEXEC IEBCOMPR

Q. Do IEBCOMPR and ISRSUPC both support alternate DDName lists?)

Paul,

I do believe IEBCOMPR can be invoked using alternate DDname list(example shown 
below), but with ISRSUPC I get RC of 24

/* REXX - Invoke IEBCOMPR With alternate DDnames.   */ 
"ALLOC FI(PDS1) DA('KOLUSU.PMR66403.JCL') SHR" 
"ALLOC FI(PDS2) DA('KOLUSU.PMR66403.JCL') SHR" 
"ALLOC DD(REP) DA(*) REU" 
"ALLOC DD(CTL) NEW REU RECFM(F B) LRECL(80)" 
QUEUE "  COMPARE TYPORG=PO " 
"EXECIO "QUEUED()" DISKW CTL (FINIS" 
PROG   = 'IEBCOMPR' 
PARM   = ''   /* STANDARD PARM, AS FROM JCL   */
DDLIST = COPIES('00'X,8) ||,  /* DDNAME  1 OVERRIDE: SYSLIN   */
 COPIES('00'X,8) ||,  /* DDNAME  2 OVERRIDE:  N/A */
 COPIES('00'X,8) ||,  /* DDNAME  3 OVERRIDE: SYSLMOD  */
 COPIES('00'X,8) ||,  /* DDNAME  4 OVERRIDE: SYSLIB   */
 LEFT('CTL',  8) ||,  /* DDNAME  5 OVERRIDE: SYSIN*/
 LEFT('REP',  8) ||,  /* DDNAME  6 OVERRIDE: SYSPRINT */
 COPIES('00'X,8) ||,  /* DDNAME  7 OVERRIDE: SYSPUNCH */
 LEFT('PDS1', 8) ||,  /* DDNAME  8 OVERRIDE: SYSUT1   */
 LEFT('PDS2', 8) ||,  /* DDNAME  9 OVERRIDE: SYSUT2   */
 COPIES('00'X,8) ||,  /* DDNAME 10 OVERRIDE: SYSUT3   */
 COPIES('00'X,8) ||,  /* DDNAME 11 OVERRIDE: SYSUT4   */
         COPIES('00'X,8) ||,  /* DDNAME 12 OVERRIDE: SYSTERM  */
 COPIES('00'X,8) ||,  /* DDNAME 13 OVERRIDE:  N/A

Re: 0C4 from TSOEXEC IEBCOMPR

2014-03-06 Thread Sri h Kolusu 
Q. Do IEBCOMPR and ISRSUPC both support alternate DDName lists?)

Paul,

I do believe IEBCOMPR can be invoked using alternate DDname list(example 
shown below), but with ISRSUPC I get RC of 24

/* REXX - Invoke IEBCOMPR With alternate DDnames.   */ 
"ALLOC FI(PDS1) DA('KOLUSU.PMR66403.JCL') SHR" 
"ALLOC FI(PDS2) DA('KOLUSU.PMR66403.JCL') SHR" 
"ALLOC DD(REP) DA(*) REU" 
"ALLOC DD(CTL) NEW REU RECFM(F B) LRECL(80)" 
QUEUE "  COMPARE TYPORG=PO " 
"EXECIO "QUEUED()" DISKW CTL (FINIS" 
PROG   = 'IEBCOMPR' 
PARM   = ''   /* STANDARD PARM, AS FROM JCL   */
DDLIST = COPIES('00'X,8) ||,  /* DDNAME  1 OVERRIDE: SYSLIN   */
 COPIES('00'X,8) ||,  /* DDNAME  2 OVERRIDE:  N/A */
 COPIES('00'X,8) ||,  /* DDNAME  3 OVERRIDE: SYSLMOD  */
 COPIES('00'X,8) ||,  /* DDNAME  4 OVERRIDE: SYSLIB   */
 LEFT('CTL',  8) ||,  /* DDNAME  5 OVERRIDE: SYSIN*/
 LEFT('REP',  8) ||,  /* DDNAME  6 OVERRIDE: SYSPRINT */
 COPIES('00'X,8) ||,  /* DDNAME  7 OVERRIDE: SYSPUNCH */
 LEFT('PDS1', 8) ||,  /* DDNAME  8 OVERRIDE: SYSUT1   */
 LEFT('PDS2', 8) ||,  /* DDNAME  9 OVERRIDE: SYSUT2   */
 COPIES('00'X,8) ||,  /* DDNAME 10 OVERRIDE: SYSUT3   */
 COPIES('00'X,8) ||,  /* DDNAME 11 OVERRIDE: SYSUT4   */
 COPIES('00'X,8) ||,  /* DDNAME 12 OVERRIDE: SYSTERM  */
 COPIES('00'X,8) ||,  /* DDNAME 13 OVERRIDE:  N/A */
 COPIES('00'X,8)  /* DDNAME 14 OVERRIDE: SYSCIN   */
ADDRESS 'LINKMVS' PROG 'PARM DDLIST' 
"FREE FI(PDS1 PDS2 CTL REP)" 
EXIT RC 

Sri Hari Kolusu
DFSORT Development
IBM Corporation
Email: skol...@us.ibm.com
Phone: 408-927-2187 Tie Line: 457-2187

IBM Mainframe Discussion List  wrote on 
03/06/2014 09:34:58 AM:

> From: Paul Gilmartin 
> To: IBM-MAIN@listserv.ua.edu, 
> Date: 03/06/2014 09:35 AM
> Subject: Re: 0C4 from TSOEXEC IEBCOMPR
> Sent by: IBM Mainframe Discussion List 
> 
> On Thu, 6 Mar 2014 09:20:56 -0800, Sri h Kolusu wrote:
> 
> >Hansen,
> >
> >The following REXX will invoke IEBCOMPR
> >
> >/* REXX */
> >ADDRESS TSO
> >"ALLOC FI(SYSUT1) DA('Your.PDS1.To.Compare') SHR"
> >"ALLOC FI(SYSUT2) DA('Your.PDS2.To.Compare') SHR"
> >"ALLOC DD(SYSPRINT) DA(*) REU"
> >"ALLOC DD(SYSIN) NEW REU RECFM(F B) LRECL(80)"
> >QUEUE "  COMPARE TYPORG=PO "
> >"EXECIO "QUEUED()" DISKW SYSIN (FINIS"
> >"CALL *(IEBCOMPR)"
> >"FREE FI(SYSUT1 SYSUT2 SYSIN SYSPRINT)"
> > 
> (I use BPXWDYN() and "address LINKMVS" to avoid a TSO prerequisite.
> Often, I use RTDDN(name) and an alternate DDName list to avoid
> collision with existing allocations.  Do IEBCOMPR and ISRSUPC both
> support alternate DDName lists?)
> 
> -- 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: 0C4 from TSOEXEC IEBCOMPR

2014-03-06 Thread Paul Gilmartin 
On Thu, 6 Mar 2014 09:20:56 -0800, Sri h Kolusu wrote:

>Hansen,
>
>The following REXX will invoke IEBCOMPR
>
>/* REXX */
>ADDRESS TSO
>"ALLOC FI(SYSUT1) DA('Your.PDS1.To.Compare') SHR"
>"ALLOC FI(SYSUT2) DA('Your.PDS2.To.Compare') SHR"
>"ALLOC DD(SYSPRINT) DA(*) REU"
>"ALLOC DD(SYSIN) NEW REU RECFM(F B) LRECL(80)"
>QUEUE "  COMPARE TYPORG=PO "
>"EXECIO "QUEUED()" DISKW SYSIN (FINIS"
>"CALL *(IEBCOMPR)"
>"FREE FI(SYSUT1 SYSUT2 SYSIN SYSPRINT)"
> 
(I use BPXWDYN() and "address LINKMVS" to avoid a TSO prerequisite.
Often, I use RTDDN(name) and an alternate DDName list to avoid
collision with existing allocations.  Do IEBCOMPR and ISRSUPC both
support alternate DDName lists?)

-- gil

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

Re: 0C4 from TSOEXEC IEBCOMPR

2014-03-06 Thread Paul Gilmartin 
On Thu, 6 Mar 2014 15:43:22 +, Hansen, Dave L - Eagan, MN wrote:
>
>  My trace ===> 30 *-* "ISPEXEC SELECT PGM(ISRSUPC)"
>>L>   "ISPEXEC SELECT PGM(ISRSUPC)"
> 
Eek!

I've always just ALLOCATEd a couple DDNames and done "address LINKMVS ISRSUPC".
(It may need a control file).  Works outside ISPF environment.

Caution:  RC indicates failure if the data sets match; success if they don't 
match
(it's all subjective).

-- gil

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

Re: 0C4 from TSOEXEC IEBCOMPR

2014-03-06 Thread Sri h Kolusu 
Hansen,

The following REXX will invoke IEBCOMPR

/* REXX */ 
ADDRESS TSO 
"ALLOC FI(SYSUT1) DA('Your.PDS1.To.Compare') SHR" 
"ALLOC FI(SYSUT2) DA('Your.PDS2.To.Compare') SHR" 
"ALLOC DD(SYSPRINT) DA(*) REU" 
"ALLOC DD(SYSIN) NEW REU RECFM(F B) LRECL(80)" 
QUEUE "  COMPARE TYPORG=PO " 
"EXECIO "QUEUED()" DISKW SYSIN (FINIS" 
"CALL *(IEBCOMPR)" 
"FREE FI(SYSUT1 SYSUT2 SYSIN SYSPRINT)" 

Thanks,
Kolusu

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

Re: 0C4 from TSOEXEC IEBCOMPR

2014-03-06 Thread Hansen, Dave L - Eagan, MN 
Terry,

   Thank you for your update.  I am changing course away from IEBCOMPR and 
moving towards ISRSUPC.  I found our ISPF SAMPLIB that has ISRSCLST and 
ISRSPROC.  I would like to automate comparing a bunch of FONT libs.

   Our ISPF LOAD lib has ISRSUPC.  I tried "TSOEXEC ISRSUPC" in my EXEC.  It 
just hung.  I looked at what was required and I thought with the defaults that 
maybe something would complete.

   OK, I can do this.  I'll just call ISPF from my EXEC.  I tried "ISPEXEC 
SELECT PGM(ISRSUPC)".  I've done some panels, but I have not done much with 
calling ISPF programs.  This also just hung.

  My trace ===> 30 *-* "ISPEXEC SELECT PGM(ISRSUPC)"
>L>   "ISPEXEC SELECT PGM(ISRSUPC)"

   It looks like the example ISRSCLST.  But I didn't pass LISTING, CTYPE, or 
PROCESS.  They should default.


Q).  Both calls to ISRSUPC just hang.  Is there something in the environment I 
have not taken into consideration I need to setup?  Can ISRSUPC be called from 
either TSOEXEC and ISPEXEC?


  Thanks again for your insight,  Dave 



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Terry Sambrooks
Sent: Thursday, March 06, 2014 2:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: 0C4 from TSOEXEC IEBCOMPR

Hi Dave,

Acknowledging that an example for comparing two PDSEs may existing in the z/OS 
V1R12.0 DFSMSdfp Utilities (SC26-7414-07) manual.

When I last looked at IEBCOMPR in the utilities manual, I notice the very first 
paragraph is "Recommendation: Use the SuperC utility instead of IEBCOMPR. 
SuperC is part of ISPF/PDF and the High Level Assembler Toolkit Feature. SuperC 
can be processed in the foreground as well as in batch and its report is more 
useful."

IEBCOMPR was never brilliant as it would stop after 10 consecutive errors, 
which is easily induced if a record is deleted from a file.

Kind Regards - Terry
 
Director
KMS-IT Limited
228 Abbeydale Road South
Dore
Sheffield
S17 3LA
UK
 
Reg : 3767263
 
Outgoing e-mails have been scanned, but it is the recipients responsibility to 
ensure their anti-virus software is up to date.
 
 


--
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: 0C4 from TSOEXEC IEBCOMPR

2014-03-06 Thread Terry Sambrooks 
Hi Dave,

Acknowledging that an example for comparing two PDSEs may existing in the
z/OS V1R12.0 DFSMSdfp Utilities (SC26-7414-07) manual.

When I last looked at IEBCOMPR in the utilities manual, I notice the very
first paragraph is "Recommendation: Use the SuperC utility instead of
IEBCOMPR. SuperC is part of
ISPF/PDF and the High Level Assembler Toolkit Feature. SuperC can be
processed in the foreground as well as in batch and its report is more
useful."

IEBCOMPR was never brilliant as it would stop after 10 consecutive errors,
which is easily induced if a record is deleted from a file.

Kind Regards - Terry
 
Director
KMS-IT Limited
228 Abbeydale Road South
Dore
Sheffield
S17 3LA
UK
 
Reg : 3767263
 
Outgoing e-mails have been scanned, but it is the recipients responsibility
to ensure their anti-virus software is up to date.
 
 


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

Re: 0C4 from TSOEXEC IEBCOMPR

2014-03-05 Thread Jim Mulder 
>I am trying to compare two PDSEs.  I found Example 8: Compare Two
> PDSEs in the z/OS V1R12.0 DFSMSdfp Utilities (SC26-7414-07).  I am 
> trying to get IEBCOMPR to work from REXX like I got IEBCOPY to work.
> We are running z/OS V1R13.
> 
> "ALLOC FI(SYSUT1) DA('PMSBDH.VPS.LRS.AFP.V2R10.FDEFLIB') SHR"
> "ALLOC FI(SYSUT2) DA('VPS.LRS.VPS.V2R10.FDEFLIB') SHR"
> "ALLOC FI(SYSIN) UNIT(VIO) SPACE(15) BLKSIZE(80) LRECL(80) RECFM(F B)
> DSORG(PS) NEW DELETE REUSE"
> "NEWSTACK"
> V1 = " COMPARE TYPORG=PO"
> QUEUE V1
> "EXECIO" queued() "DISKW SYSIN (FINIS"
> "DELSTACK"
> "TSOEXEC IEBCOMPR"
> "FREE FI(SYSUT1 SYSUT2 SYSIN)"

  For one thing, you are invoking IEBCOMPR as a command processor,
and it may not be designed to deal with that interface.

  What happens if you do "CALL *(IEBCOMPR)" instead of
"TSOEXEC IEBCOMPR"  ?

Jim Mulder   z/OS System Test   IBM Corp.  Poughkeepsie,  NY

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

0C4 from TSOEXEC IEBCOMPR

2014-03-05 Thread Hansen, Dave L - Eagan, MN 
Dear Group,

   I am trying to compare two PDSEs.  I found Example 8: Compare Two PDSEs in 
the z/OS V1R12.0 DFSMSdfp Utilities (SC26-7414-07).  I am trying to get 
IEBCOMPR to work from REXX like I got IEBCOPY to work.  We are running z/OS 
V1R13.

"ALLOC FI(SYSUT1) DA('PMSBDH.VPS.LRS.AFP.V2R10.FDEFLIB') SHR"
"ALLOC FI(SYSUT2) DA('VPS.LRS.VPS.V2R10.FDEFLIB') SHR"
"ALLOC FI(SYSIN) UNIT(VIO) SPACE(15) BLKSIZE(80) LRECL(80) RECFM(F B)
DSORG(PS) NEW DELETE REUSE"
"NEWSTACK"
V1 = " COMPARE TYPORG=PO"
QUEUE V1
"EXECIO" queued() "DISKW SYSIN (FINIS"
"DELSTACK"
"TSOEXEC IEBCOMPR"
"FREE FI(SYSUT1 SYSUT2 SYSIN)"



>From the trace:

36 *-* "TSOEXEC IEBCOMPR"
   >L>   "TSOEXEC IEBCOMPR"
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=0C4  REASON CODE=0011
TIME=15.14.49  SEQ=63831  CPU=  ASID=018E
PSW AT TIME OF ERROR  078D1000   0006E474  ILC 6  INTC 11
   ACTIVE LOAD MODULE   ADDRESS=00069A38  OFFSET=4A3C
   NAME=IEBCOMPR
   DATA AT PSW  0006E46E - B25A4270  B09BD2D3  60005002
   GR 0:    1: 00066AC0
  2:    3: 00066820
  4: 8A2B202C   5: 6F80
  6: 00070EE6   7: D7D3
  8: 00979AB8   9: 00D3C130
  A: 0006E918   B: 4006E3DA
  C: 000674A0   D: 0006E924
  E: 80FD8D78   F: 0006E3B8
END OF SYMPTOM DUMP
IEBCOMPR ENDED DUE TO ERROR+
SYSTEM ABEND CODE 0C4 REASON CODE 



   With IEBCOPY I could stack my input commands.  With IEBCOMPR all I need is 
"COMPARE TYPEORG=PO".

Q).  Should this work stacking the "COMPARE"?



I tried passing "TSOEXEC IEBCOMPR" "COMPARE TYPEORG=PO"  Blew up at the same 
address and offset.

 29 *-* "TSOEXEC IEBCOMPR" "COMPARE TYPORG=PO"
>L>   "TSOEXEC IEBCOMPR"
>L>   "COMPARE TYPORG=PO"
>O>   "TSOEXEC IEBCOMPR COMPARE TYPORG=PO"
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=0C4  REASON CODE=0011
  TIME=15.20.29  SEQ=63836  CPU=  ASID=018E
  PSW AT TIME OF ERROR  078D1000   0006E474  ILC 6  INTC 11
ACTIVE LOAD MODULE   ADDRESS=00069A38  OFFSET=4A3C
NAME=IEBCOMPR
DATA AT PSW  0006E46E - B25A4270  B09BD2D3  60005002

Q).  Should this work passing the "COMPARE"?



   This is part of my IEBCOPY REXX that works:

QUEUE VJ
"EXECIO" queued() "DISKW SYSIN (FINIS"
"DELSTACK"
"TSOEXEC IEBCOPY"
"FREE FI(INDD1 OUTDD1 SYSIN)"


   Thank you,  Dave

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