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:[email protected]]
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.02 PAGE 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 [email protected] with the message: INFO IBM-MAIN
