Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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. 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 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
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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)
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 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 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
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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
I haven't seen anything more on this yet but I'm digested daily causing
delays...
Dave - re ISRS010W: I haven't tested or researched but is it, perhaps, a
positional parm problem? In my SuperC batch step, I use
PARM=('DELTAL','FILECMP','',''). Hmmm... perhaps it's a lack of parms ie. 4
are generated by the ISPF batch panel. (That's where I got the sample above.)
signature = 6 lines follows
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585 fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
“How *do* you plan for something like that?” Guardian Bob, Reboot
“For every action, there is an equal and opposite criticism.”
“Systems Programming: Guilty, until proven innocent” John Norgauer 2004
-Original Message-
From: Hansen, Dave L - Eagan, MN [mailto:dav...l...ha...@usp...gov]
Sent: March 14, 2014 17:02
Subject: Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
[snip]
49 *-* address LINK ISRSUPC '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.
[snip]
--
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)
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)
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 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 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
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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)
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 parameter strings that I can pass with EXEC that % disallows. -- 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
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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 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)
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 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)
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: * 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 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
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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 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 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
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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 paulgboul...@aim.com 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)
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 cc42e2f56d60f24fb8a6bcc639d1d9632c657...@samtcasxmb13.usa.dce.usps.gov, on 03/07/2014 at 03:35 PM, Hansen, Dave L - Eagan, MN dave.l.han...@usps.gov 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)
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
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('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 IBM-MAIN@listserv.ua.edu wrote on
03/06/2014 09:34:58 AM:
From: Paul Gilmartin paulgboul...@aim.com
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 IBM-MAIN@listserv.ua.edu
On Thu, 6 Mar 2014 09:20:56 -0800, Sri h Kolusu wrote:
Hansen,
The following
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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 IBM-MAIN@listserv.ua.edu wrote on
03/06/2014 02:01:36 PM:
From: Hansen, Dave L - Eagan, MN dave.l.han...@usps.gov
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 IBM-MAIN@listserv.ua.edu
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 */
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
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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('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
Re: RC 24 from ISRSUPC (Was 0C4 from TSOEXEC IEBCOMPR)
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 reu
What about the rest of the allocations?
--
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
