Oppolzer - Informatik / Blog


Blog-Hauptseite      Neuester Artikel      Älterer Artikel      Neuerer Artikel      Älterer gleiche Kategorie      Neuerer gleiche Kategorie

IBM-MAIN - Merkwürdige Probleme mit PDSEs, IEBGENER, IEBCOPY

Subject:

Re: Intermittent, not consistently reproducible problems with PDSEs on z/OS V2R1 (incl. infrequent S0F4-20 RSN 1C0752EE ABENDs)

From:

Bernd Oppolzer <bernd.oppolzer@T-ONLINE.DE>

Reply-To:

IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>

Date:

2015.03.20 17:09:50


Am 20.03.2015 um 17:02 schrieb K.H.:
>> Have you tried with - directly after each IEBGENER step - do an IEBGENER
>> from the member to SYSOUT ?
> Yes. Makes no difference. Same problem
>
>> Have you tried with only non-empty members?
> Yes. No empty members - no problem.
>
>> Have tried with DD * instead of DD DATA ?
> Yes. Makes no difference. Same problem.
>
>> Have you tried with something other than NULLFILE for empty members?
>> (E g an IEBCOPY from a third dataset with empty members.)
> Yes. Makes no difference. Same problem.

that is:

the problem is not limited to IEBGENER ... if you build the empty member with
other tools, the problem remains?

So this is a PDSE problem ... from your posts I'm almost sure that you don't
have this problem with normal PDSs.

PDSEs are supported by a special address space, AFAIK. Is there a possibility to
have site-specific exits installed in the PDSE supporting subsystem; do you have
any?

> Thanks.
>
> K.
>

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

Blog-Hauptseite      Neuester Artikel      Älterer Artikel      Neuerer Artikel      Älterer gleiche Kategorie      Neuerer gleiche Kategorie