On 2017-02-02, at 08:32, Sri h Kolusu wrote:
>>> I don't know if IEBCOMPR works fine selecting a member. This sample
> cancels with IEC036I 002-B0.
>
> When you specify a member name from a PDS , it essentially is a sequential
> file and your SYSIN TYPORG=PO is no longer valid. You need to su
gt; To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 02/02/2017 01:19 AM
> Subject: Re: Limit RACF access to ISRSUPC (compare mode)
> Sent by: IBM Mainframe Discussion List
>
> Hi Kolusu,
>
> I don't know if IEBCOMPR works fine selecting a member. This
> sample cancels
Just get rid of "develop team". Evidently they only cause trouble.
sas
On Thu, Feb 2, 2017 at 3:19 AM, Jorge Garcia wrote:
> Hi Kolusu,
>
> I don't know if IEBCOMPR works fine selecting a member. This sample
> cancels with IEC036I 002-B0. It compares two members in a PDSE.
>
> //IEBCOMPR JOB
Hi Kolusu,
I don't know if IEBCOMPR works fine selecting a member. This sample cancels
with IEC036I 002-B0. It compares two members in a PDSE.
//IEBCOMPR JOB (32),'SISTEMAS',CLASS=S,MSGCLASS=X,NOTIFY=&SYSUID
//STEP1EXEC PGM=IEBCOMPR
//SYSPRINT DD SY
Jorge Garcia wrote:
> I know It's a question about a RACF topic, but we need a workaround to solve
> a problem access. We've limited the ISRSUPC program access to the devolpment
> teams to avoid searchs in long PDS with many elapsed and cpu time. The
> problem that we have It's ISPF use the sam
And an answer to the OP's original performance problem could be to adjust his
WLM for TSO sessions to have a 3rd period (or 2nd or 4th) where the long
running SupreC drops to discretionary.
--
For IBM-MAIN subscribe / signoff /
On 2017-02-01, at 14:01, Sri h Kolusu wrote:
And that gives me:Bad Request
>
> Paul,
>
> I have no idea as to how to fix your Bad request error from your browser.
> Either way that is besides the point, since you found a working link.
>
As I follow this list, I observe reports of KC
ion based on his requirements. It was
merely a suggestion.
Thanks,
Kolusu
IBM Mainframe Discussion List wrote on
02/01/2017 01:41:14 PM:
> From: Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 02/01/2017 01:41 PM
> Subject:
On 2017-02-01, at 10:02, Sri h Kolusu wrote:
> Jorge,
>
> If you just want your developers to only use compare function, they can
> use IEBCOMPR. The output is not as fancy as SuperC , but it lists the
> differences.
>
> https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r
On Wed, 1 Feb 2017 10:49:10 -0600 Jorge Garcia wrote:
:> I know It's a question about a RACF topic, but we need a workaround to solve
a problem access. We've limited the ISRSUPC program access to the devolpment
teams to avoid searchs in long PDS with many elapsed and cpu time. The problem
that
List wrote on
02/01/2017 09:49:10 AM:
> From: Jorge Garcia
> To: IBM-MAIN@LISTSERV.UA.EDU
> Date: 02/01/2017 09:50 AM
> Subject: Limit RACF access to ISRSUPC (compare mode)
> Sent by: IBM Mainframe Discussion List
>
> Hi all,
>
> I know It's a question a
W dniu 2017-02-01 o 17:49, Jorge Garcia pisze:
Hi all,
I know It's a question about a RACF topic, but we need a workaround to solve
a problem access. We've limited the ISRSUPC program access to the devolpment
teams to avoid searchs in long PDS with many elapsed and cpu time. The problem
tha
Hi all,
I know It's a question about a RACF topic, but we need a workaround to solve a
problem access. We've limited the ISRSUPC program access to the devolpment
teams to avoid searchs in long PDS with many elapsed and cpu time. The problem
that we have It's ISPF use the same program to search
13 matches
Mail list logo
