Re: Highest address "below the bar

[Rob Schramm]

Any region size in excess of 16m gives you that amount above the line plus
everything that is available below the line.  REGION=64M is 64M above and
(assuming you have a 10M below the line YBTLRMV) gives you the 10M below as
well.  Been that way for as long as I remember. This also assumes there are
no exits messing with the REGION.

YBTLRMV - Your below the line region may vary 

Rob Schramm

On Sun, Jun 19, 2016, 6:17 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Sun, 19 Jun 2016 15:32:07 -0400, Peter Relson wrote:
> >
> >The maximum region size is entertaining, but if you ever granted it, you
> >would probably cause the address space to fail.  There isn't room for
> >x'7FF0' bytes of user storage above the 16M line (and when you specify
> >a region size that big, it applies to the area above 16M),
> >
> Really?  I had expected it would apply to both.  What happens if a (legacy)
> program explicitly requests 24-bit storage?  Does that mean that if I
> specify REGION=16385K, I can use that amount above the line *plus*
> whatever scraps are available below the line?  (I understand I'll never
> get 16383K.)
>
>
> On Fri, 17 Jun 2016 11:21:44 -0400, Jim Mulder wrote:
>
> >> >>For diagnostic purposes, then 4K page at 7000 is always
> >> >>left invalid in z/OS.
> >> >
> >> That might be due to a requirement of ANSI C that there always be an
> address
> >> algebraically greater than that of any accessible object, for loop
> >> termination conditions.
> >
> >  Not likely.  It has been that way since the first release of MVS/XA,
> >circa 1982. That was a time when MVS still ruled with arrogance, and it
> >would takes some doses of marketplace reality changes a few years later
> >before MVS became interested in accommodating C and Unix.
> >
> So it's fortuitous that the design meets both requirements.  Or,
> the designers might have had similar motivaions in both cases.
>
> -- gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
-- 

Rob Schramm
The Art of Mainframe, Inc

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

Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

[Paul Gilmartin]

On Sun, 19 Jun 2016 17:54:24 +, J R wrote:

>The PDS gotchas described in this thread have existed since Christ was a 
>cowboy.  Yes, something should have been done about it since the first cha was 
>got.  However, given that that eventuality never came to pass, what amazes me 
>most is that it's still such a hot topic fifty years later!  
> 
It shall remain a hot topic as long as unwitting programmers continue to fall
into the pit.

>Does PDSE avert at least the directory integrity weakness?  
>  
I hope.  I suppose I need to test.  It's plausible even that for (FSVO)
compatibility the operation will succeed as a no-op, much like an
attempt to compress a PDSE with IEBCOPY.  RC=??

This was most often done as a shortcut to empty a PDS: write a
terminator at the beginning of the directory and reset DS1LSTAR.

-- gil

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

Re: Highest address "below the bar

[Paul Gilmartin]

On Sun, 19 Jun 2016 15:32:07 -0400, Peter Relson wrote:
>
>The maximum region size is entertaining, but if you ever granted it, you 
>would probably cause the address space to fail.  There isn't room for 
>x'7FF0' bytes of user storage above the 16M line (and when you specify 
>a region size that big, it applies to the area above 16M), 
> 
Really?  I had expected it would apply to both.  What happens if a (legacy)
program explicitly requests 24-bit storage?  Does that mean that if I
specify REGION=16385K, I can use that amount above the line *plus*
whatever scraps are available below the line?  (I understand I'll never
get 16383K.)


On Fri, 17 Jun 2016 11:21:44 -0400, Jim Mulder wrote:

>> >>For diagnostic purposes, then 4K page at 7000 is always
>> >>left invalid in z/OS.
>> > 
>> That might be due to a requirement of ANSI C that there always be an  address
>> algebraically greater than that of any accessible object, for loop 
>> termination conditions.
>
>  Not likely.  It has been that way since the first release of MVS/XA, 
>circa 1982. That was a time when MVS still ruled with arrogance, and it 
>would takes some doses of marketplace reality changes a few years later 
>before MVS became interested in accommodating C and Unix. 
> 
So it's fortuitous that the design meets both requirements.  Or,
the designers might have had similar motivaions in both cases.

-- gil

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

Re: TIOT exceeded

[Greg Dyck]

On 6/18/2016 11:03 AM, Jake Anderson wrote:

Is there a way to know if the DD chain has approached the end or it has
approached the end of Chain. Is there a way to tweak the JCL to overcome
TIOT exceeded values ?


The TIOT is a fixed sized array of entries, not a chain.  The size is 
defined in PARMLIB member ALLOCxx, with a maximum allowed size of 64K. 
Only when an allocation request fails due to insufficient TIOT space do 
you know it is full.


The primary 'tweak' for SMS managed datasets that can reduce the space 
used for each DD in the TIOT is to reduce the dynamic volume count 
(DYNVOL) specification defined for the data class 
(http://www-01.ibm.com/support/docview.wss?uid=isg3T165).


It is possible to dynamically allocated datasets using the extended TIOT 
(aka, XTIOT).  This requires the application be updated appropriately 
(http://publibz.boulder.ibm.com/zoslib/pdf/oa34634.pdf).  For non-VSAM 
datasets you must also change PARMLIB member DEVSUPxx to specify 
NON_VSAM_XTIOT=YES.  VSAM datasets may be allocated using the XTIOT 
without any changes to PARMLIB.


Greg

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

Re: owner-ibm-main

[Campbell Jay]

Thanks much.

Jay Campbell
IBM OS Support Section

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@listserv.ua.edu] On Behalf 
Of Edward Finnell
Sent: Sunday, June 19, 2016 3:05 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: owner-ibm-main

Definitely you are. The List is not seeing them and as a List member I'm not 
getting them. Get your Network folks to look at full headers and see if they  
can block at a node point or add the 'owner' to your white board list in your  
mailer.
 
 
In a message dated 6/19/2016 1:08:01 P.M. Central Daylight Time, 
james.l.campb...@irs.gov writes:

Am I  being SPAMed ?
They're getting  annoying.

--
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: Highest address "below the bar

[Peter Relson]

-- The highest address below the bar is of course 7FFF.
-- The highest non-data space address that will not definitely blow up 
when you reference it is 7FFFEFFF. The high page in 31-bit storage was 
made non-addressable for RAS/quality reasons (Bob Rogers, I believe, drove 
it, possibly with the advent of MVS/XA).
-- The highest data space address is 7FFF.

The maximum region size is entertaining, but if you ever granted it, you 
would probably cause the address space to fail.  There isn't room for 
x'7FF0' bytes of user storage above the 16M line (and when you specify 
a region size that big, it applies to the area above 16M), 


Peter Relson
z/OS Core Technology Design


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

Re: owner-ibm-main

[Edward Finnell]

Definitely you are. The List is not seeing them and as a List member I'm  
not getting them. Get your Network folks to look at full headers and see if 
they  can block at a node point or add the 'owner' to your white board list 
in your  mailer.
 
 
In a message dated 6/19/2016 1:08:01 P.M. Central Daylight Time,  
james.l.campb...@irs.gov writes:

Am I  being SPAMed ?
They're getting  annoying.

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

Re: Where is format of Job ID documented?

[Mark Zelden]

On Sat, 18 Jun 2016 21:00:38 +, Jesse 1 Robinson  
wrote:

>How could I determine if APPC output is clogging my spool? I don't see any at 
>the moment. 

Set PREFIX=* ,  DEST= (null)  and OWNER=* in SDSF.

Issue "H ALL"  and sort on JOBID and look for Annn
Issue "O" and sort on JOBID and look for Annn

This assumes you don't have any SDSF parms or SDSF SAF security rules preventing
you from seeing the output.  

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Where is format of Job ID documented?

[Mark Zelden]

On Sat, 18 Jun 2016 08:05:02 -0500, Joel C. Ewing  wrote:

>We always auto-purged older held output known to be past its usefulness
>and for some categories of output that usefulness was a matter of hours
>not days.
>
>My recollection is that after APPC came upon the scene we had to modify
>the held-output purge command sequences or APPC output wasn't touched.
>Makes me wonder if the folks seeing terrible performance when SDSF shows
>APPC output could be unintentionally retaining APPC junk in their output
>queue that has no useful function and which would be better to purge in
>a more timely fashion.
>Joel C Ewing


From what I recall, having APPC ON desegregated performance whether you had
APPC output or not.   Testing with "APPC ON" right now in a fairly large 
spool environment doesn't seem to hurt performance at all.   I recall doing
the same test some years ago with the same results.  So that leads me
to believe the original problem was fixed in either SDSF or maybe it was 
fixed as a result of a change in JES2.   However, "this ain't 1992" either. 
The processors are so much faster, I have no way of knowing for sure
if the original problem was really "fixed" or not.

 
Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: WAIT >1 (Friday type question, a day late)

[Stevet]

Try EVENTS. I've not used this for a few years, but I think it does what you 
want. Sorry, but I'm doing electrical work and can't get to manuals right now. 

Sent from iPhone - small keyboard fat fingers - expect spellinf errots.

> On Jun 19, 2016, at 12:52 PM, Charles Mills  wrote:
> 
> Oh sure. The basic "wait for one of many." My code waits for an any one of
> an operator command, a timer expiration, or "real work." 
> 
> My question was does anyone issue a wait with a completion count of more
> than one? "Wake me when two of these five ECBs have been posted"?
> 
> Charles
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Peter Hunkeler
> Sent: Sunday, June 19, 2016 9:03 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: AW: WAIT >1 (Friday type question, a day late)
> 
> 
> 
> 
>> I just had occasion to RTFM on WAIT. I'm sure WAIT with an event count 
>> greater than one seemed like a terrific idea at the time, but has 
>> anyone ever used it? What's an application for "wait for any two of 
>> these five events to occur"?
> 
> 
> 
> 
> I once wrote a utility that waits for either an MVS STOP command or until a
> specified time interval has expired. It sets up the timer and the CIB, then
> WAITs for one of the two events to happen.
> 
> --
> 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

owner-ibm-main

[Campbell Jay]

Am I being SPAMed ?
They're getting annoying.

Supposedly from  owner-ibm-m...@listserv.ua.edu   sometimes with no From:

Text...

X-Brightmail-Tracker: 
H4sIA+NgFlrNLMWRWlGSWpSXmKPExsXCdV5DVffPnbRwg4nfTCxev023WPm/mdHi
4qc9jA7MHkfWHmQOYIzisklJzcksSy3St0vgyujZfYGtgKECRDUwMkxgZFjAyLCKUTYswCjY
19XXMSAg2NfdwEgvpVgvs6g4L7VELz2/bBMjyK7bgbE7GNd8dDzEKMDBqMTD27kiLVyINbGs
uDL3EKMkB5OSKO+e7tRwIb6k/JTKjMTijPii0pzU4kOMEhzMSiK8x28DlfOmJFZWpRblw6Sk
OViUxHk/TXweIiSQnliSmp2aWpBaBJOV4eBQkuCdCtIoWJSanlqRlplTgpBm4uAEGc4DNPw8
2PDigsTc4sx0iPwpRkOOfYtvrGXiuPDsAZC8AiKFWPLy81KlxHkzQBoEQBoySvPgZl5iFJUS
5mVkYGAQ4gG6IzezBCL+ilEc6GVhXgVgUAvxZOaVwG15BXQAE9ABmvOSQQ4oSURISTUwcva0
/D49q2btxbqy0iMKH98kP9qzzmHfzxmPhHKc1V81F7rdqv/AZO1p43tbYp1uYnbjwkpZh73Z
811VFB3OHPtx7fqJjKWybfULRV+vkWuXC/jCE6dgcSBo+ZfnHo75U24eKsg+tZ5XKTrzemfX
JZPZC9vm9W99w5r98r2/Vr8d09zHXnVPlFiKMxINtZiLihMBA4pxRz4CAAA=
Date: Sun Jun 19 12:57:16 2016

Jay Campbell
IBM OS Support Section

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

Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

[J R]

The PDS gotchas described in this thread have existed since Christ was a 
cowboy.  Yes, something should have been done about it since the first cha was 
got.  However, given that that eventuality never came to pass, what amazes me 
most is that it's still such a hot topic fifty years later!  

Does PDSE avert at least the directory integrity weakness?  

Sent from my iPhone

> 

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

Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

[retired mainframer]

The other members became " unreadable" as soon as the DCB values were
changed in the DSCB.  This probably happened when the SYSPRINT was closed.
Any subsequent editing of that member did not change the situation, not for
better and not for worse.

The PDS directory was not corrupted by either action.

Any of the members in the PDS can be read as long as the DCB used to access
the member contains the correct values.  Under normal conditions those
values come from the following sources, if they exist (in order of highest
priority to lowest): the OPEN exit, the DCB statement in the program, the DD
statement, and the DSCB.  If you are using a standard utility such as
IEBGENER or IEBCOPY, the first two are not an option for you.  But you do
have complete control over the DD statement.

Regardless of the current DSCB values, if you specify in the DD statement
the values used when a member was written to the PDS, you will be able to
read that member back.  Specifying the original values will allow you to
copy all the original members to another PDS.  Specifying the SYSPRINT
values will let you copy the print output to a third PDS.  Then you can
discard the original PDS, rename the two new ones, and proceed on as if this
never happened.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of ? ?
> Sent: Sunday, June 19, 2016 8:42 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> Yes - definitely - but I think I went wrong when I edited the output .
> 
> .
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jesse 1 Robinson
> Sent: Sunday, June 19, 2016 6:35 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> Please answer one burning question. When SYSPRINT went to the PDS, was a
member
> name specified?
> 
> .
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-302-7535 Office
> robin...@sce.com
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of ? ?
> Sent: Sunday, June 19, 2016 2:31 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: [EXTERNAL] RFE opened on IEBGENER and PDS
Corruption
> 
> Thanks so much Lizette and Lionel.  In my case, it was SYSPRINT of IDCAMS
that
> 'reconfigured' the PDS file, followed by edit of the sysprint output
members. Believe me ,
> the 'sandbox' is now backed up daily.
> 
> .
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lizette Koehler
> Sent: Friday, June 17, 2016 7:05 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> Cool.
> 
> I will see if I can append to the RFE.
> 
> Lizette
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Dyck, Lionel B. (TRA)
> > Sent: Friday, June 17, 2016 9:02 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> >
> > I like the idea of the RFE but could I suggest broadening it to all
> > BSAM/QSAM since any program that writes output could do the same
> > thing.  Put the test in the access method to prevent writing a
> > sequential dataset on top of a partitioned dataset.
> >
> > --
> > 
> > Lionel B. Dyck (TRA Contractor)
> > Mainframe Systems Programmer
> > Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI
> > Service Delivery & Engineering
> >
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Lizette Koehler
> > Sent: Friday, June 17, 2016 10:59 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> >
> > After the discussion this week on recovering a PDS after IEBGENER was
> > used without a member on SYSUT2, I went ahead and opened the following
> > RFE (I did not find any currently in RFE on this)
> >
> > If you like it, please vote for it
> >
> > It is asking IBM to put a test into IEBGENER to see if SYSUT2 is a PDS
> > or PDSE.
> > And if it is, and no member is specified on the SYSUT2, to terminate
> > the step with an RC12 and message about a PDS and no member name
supplied.
> >
> > http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=9
> > 0179
> >
> >
> > Lizette Koehler
> > statistics: A precise and logical method for stating a half-truth
> > inaccurately
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
to
> 

Re: RFE opened on IEBGENER and PDS Corruption

[Paul Gilmartin]

On Sun, 19 Jun 2016 17:25:45 +0100, Rupert Reynolds wrote:

>I can see an obvious need to avoid corruption of the directory. Yet there
>is (or was) valid code (using BLKSIZE=256 from memory) to access a PDS
>directly. And wasn't IEBGENER with a dummy SYSUT1 used to repair the
>DSORG=PO of a PDS damaged in this way?  So I think it would be difficult to
>make sensible changes to the access methods.
> 
The user should be allowed any desired overrides to RECFM, LRECL,
BLKSIZE, and DSORG opening a data set for INPUT.  The data set
remains intact.  Access methods or DFSMS should prohibit opening
for OUTPUT or UPDATE that would modify existing attributes.

If such rules had originally been in force, there would have been no
damage, and no need to repair.

>I'd suggest making sure there are checks in all the IBM utilities, as in
>the RFE, as a practical answer.
> 
I consider it less practical to make changes in *ALL* IBM utilities, past,
present, and future, than in one central place in DFSMS.

Suggestion to OP. Use:

//STEP EXEC PGM=IEBGENER
//SYSPRINT  DD  SYSOUT=(,)
//SYSIN DD  *
//SYSUT2DD  SYSOUT=(,)
//SYSUT1DD  DISP=SHR,DSN=data.set.name(member1),
//  RECFM=FB,LRECL=80,BLKSIZE=32720

... to recover any member.

-- gil

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

Re: WAIT >1 (Friday type question, a day late)

[Charles Mills]

Oh sure. The basic "wait for one of many." My code waits for an any one of
an operator command, a timer expiration, or "real work." 

My question was does anyone issue a wait with a completion count of more
than one? "Wake me when two of these five ECBs have been posted"?

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Peter Hunkeler
Sent: Sunday, June 19, 2016 9:03 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: WAIT >1 (Friday type question, a day late)

 

 
>I just had occasion to RTFM on WAIT. I'm sure WAIT with an event count 
>greater than one seemed like a terrific idea at the time, but has 
>anyone ever used it? What's an application for "wait for any two of 
>these five events to occur"?




I once wrote a utility that waits for either an MVS STOP command or until a
specified time interval has expired. It sets up the timer and the CIB, then
WAITs for one of the two events to happen.

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

Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

[Rupert Reynolds]

I can see an obvious need to avoid corruption of the directory. Yet there
is (or was) valid code (using BLKSIZE=256 from memory) to access a PDS
directly. And wasn't IEBGENER with a dummy SYSUT1 used to repair the
DSORG=PO of a PDS damaged in this way?  So I think it would be difficult to
make sensible changes to the access methods.

I'd suggest making sure there are checks in all the IBM utilities, as in
the RFE, as a practical answer.

Rupert

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

Re: RFE opened on IEBGENER and PDS Corruption

[פנינה קוניגסברג]

Oh， how I wish that was true. Tried many of the suggestions posted both before 
and after I submitted the problem. Iebgener to different size pds`s 80 & 124. 
Today， Printds looked good but same results. Xmit/receive today really made me 
hopeful but alas the output file still remained with io errors. Last week used 
z/os ditto disk browse to copy one important member， so the data still exists 
on the hardware. Just the control info is corrupted.

Sent from my LG Mobile

-- Original message--
From: Jesse 1 Robinson
Date: Sun, Jun 19, 2016 19:16
To: IBM-MAIN@LISTSERV.UA.EDU;
Cc:
Subject:Re: RFE opened on IEBGENER and PDS Corruption

The reason I ask about member name is that having one in the IDCAMS JCL should 
have preserved the PDS directory. This means that old data should still be 
intact. Only the oddball SYSPRINT member should be unusable once the externa 
DCB attributes are restored to FB-80. In fact it can be deleted without harming 
the other data.

Confession: I have not actually tried any of this.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ? ?
Sent: Sunday, June 19, 2016 8:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Yes - definitely - but I think I went wrong when I edited the output .

.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Sunday, June 19, 2016 6:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Please answer one burning question. When SYSPRINT went to the PDS, was a member 
name specified?

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ? ?
Sent: Sunday, June 19, 2016 2:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Thanks so much Lizette and Lionel.  In my case, it was SYSPRINT of IDCAMS that 
'reconfigured' the PDS file, followed by edit of the sysprint output members. 
Believe me , the 'sandbox' is now backed up daily.

.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, June 17, 2016 7:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Cool.

I will see if I can append to the RFE.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Dyck, Lionel B. (TRA)
> Sent: Friday, June 17, 2016 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
>
> I like the idea of the RFE but could I suggest broadening it to all
> BSAM/QSAM since any program that writes output could do the same
> thing.  Put the test in the access method to prevent writing a
> sequential dataset on top of a partitioned dataset.
>
> --
> 
> Lionel B. Dyck (TRA Contractor)
> Mainframe Systems Programmer
> Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI
> Service Delivery & Engineering
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Lizette Koehler
> Sent: Friday, June 17, 2016 10:59 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
>
> After the discussion this week on recovering a PDS after IEBGENER was
> used without a member on SYSUT2, I went ahead and opened the following
> RFE (I did not find any currently in RFE on this)
>
> If you like it, please vote for it
>
> It is asking IBM to put a test into IEBGENER to see if SYSUT2 is a PDS
> or PDSE.
> And if it is, and no member is specified on the SYSUT2, to terminate
> the step with an RC12 and message about a PDS and no member name supplied.
>
> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=9
> 0179
>
>
> Lizette Koehler
> statistics: A precise and logical method for stating a half-truth
> inaccurately

--
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: 

Re: RFE opened on IEBGENER and PDS Corruption

[Jesse 1 Robinson]

The reason I ask about member name is that having one in the IDCAMS JCL should 
have preserved the PDS directory. This means that old data should still be 
intact. Only the oddball SYSPRINT member should be unusable once the externa 
DCB attributes are restored to FB-80. In fact it can be deleted without harming 
the other data. 

Confession: I have not actually tried any of this. 

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ? ?
Sent: Sunday, June 19, 2016 8:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Yes - definitely - but I think I went wrong when I edited the output . 

.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Sunday, June 19, 2016 6:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Please answer one burning question. When SYSPRINT went to the PDS, was a member 
name specified?

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ? ?
Sent: Sunday, June 19, 2016 2:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Thanks so much Lizette and Lionel.  In my case, it was SYSPRINT of IDCAMS that 
'reconfigured' the PDS file, followed by edit of the sysprint output members. 
Believe me , the 'sandbox' is now backed up daily.   

.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, June 17, 2016 7:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Cool.

I will see if I can append to the RFE.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Dyck, Lionel B. (TRA)
> Sent: Friday, June 17, 2016 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> I like the idea of the RFE but could I suggest broadening it to all 
> BSAM/QSAM since any program that writes output could do the same 
> thing.  Put the test in the access method to prevent writing a 
> sequential dataset on top of a partitioned dataset.
> 
> --
> 
> Lionel B. Dyck (TRA Contractor)
> Mainframe Systems Programmer
> Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI 
> Service Delivery & Engineering
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Friday, June 17, 2016 10:59 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> After the discussion this week on recovering a PDS after IEBGENER was 
> used without a member on SYSUT2, I went ahead and opened the following 
> RFE (I did not find any currently in RFE on this)
> 
> If you like it, please vote for it
> 
> It is asking IBM to put a test into IEBGENER to see if SYSUT2 is a PDS 
> or PDSE.
> And if it is, and no member is specified on the SYSUT2, to terminate 
> the step with an RC12 and message about a PDS and no member name supplied.
> 
> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=9
> 0179
> 
> 
> Lizette Koehler
> statistics: A precise and logical method for stating a half-truth 
> inaccurately

--
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

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

AW: WAIT >1 (Friday type question, a day late)

[Peter Hunkeler]

>I just had occasion to RTFM on WAIT. I'm sure WAIT with an event count
>greater than one seemed like a terrific idea at the time, but has anyone
>ever used it? What's an application for "wait for any two of these five
>events to occur"?




I once wrote a utility that waits for either an MVS STOP command or until a 
specified time interval has expired. It sets up the timer and the CIB, then 
WAITs for one of the two events to happen.


--
Peter Hunkeler



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

Re: WAIT >1 (Friday type question, a day late)

[Rupert Reynolds]

I think I used WAIT with a handful of ECBs in a started task. But it was
many years ago and I don't remember details.
At 14:41 -0700 on 06/18/2016, Charles Mills wrote about WAIT >1 (Friday
type question, a day late):

I just had occasion to RTFM on WAIT. I'm sure WAIT with an event count
> greater than one seemed like a terrific idea at the time, but has anyone
> ever used it? What's an application for "wait for any two of these five
> events to occur"?
>
> I suppose one reasonable application for an event count greater than one
> would be "WAIT for _all_ of these events to occur."
>
> Charles
>

I think the EVENTS call is designed for the "Wait Until X ECBs have been
Posted" situation. OTOH, I may be wrong.

--
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: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

[פנינה קוניגסברג]

Yes - definitely - but I think I went wrong when I edited the output . 

.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Sunday, June 19, 2016 6:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Please answer one burning question. When SYSPRINT went to the PDS, was a member 
name specified?

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ? ?
Sent: Sunday, June 19, 2016 2:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Thanks so much Lizette and Lionel.  In my case, it was SYSPRINT of IDCAMS that 
'reconfigured' the PDS file, followed by edit of the sysprint output members. 
Believe me , the 'sandbox' is now backed up daily.   

.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, June 17, 2016 7:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Cool.

I will see if I can append to the RFE.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Dyck, Lionel B. (TRA)
> Sent: Friday, June 17, 2016 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> I like the idea of the RFE but could I suggest broadening it to all 
> BSAM/QSAM since any program that writes output could do the same 
> thing.  Put the test in the access method to prevent writing a 
> sequential dataset on top of a partitioned dataset.
> 
> --
> 
> Lionel B. Dyck (TRA Contractor)
> Mainframe Systems Programmer
> Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI 
> Service Delivery & Engineering
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Friday, June 17, 2016 10:59 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> After the discussion this week on recovering a PDS after IEBGENER was 
> used without a member on SYSUT2, I went ahead and opened the following 
> RFE (I did not find any currently in RFE on this)
> 
> If you like it, please vote for it
> 
> It is asking IBM to put a test into IEBGENER to see if SYSUT2 is a PDS 
> or PDSE.
> And if it is, and no member is specified on the SYSUT2, to terminate 
> the step with an RC12 and message about a PDS and no member name supplied.
> 
> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=9
> 0179
> 
> 
> Lizette Koehler
> statistics: A precise and logical method for stating a half-truth 
> inaccurately

--
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: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

[Jesse 1 Robinson]

Please answer one burning question. When SYSPRINT went to the PDS, was a member 
name specified?

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of ? ?
Sent: Sunday, June 19, 2016 2:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Thanks so much Lizette and Lionel.  In my case, it was SYSPRINT of IDCAMS that 
'reconfigured' the PDS file, followed by edit of the sysprint output members. 
Believe me , the 'sandbox' is now backed up daily.   

.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, June 17, 2016 7:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Cool.

I will see if I can append to the RFE.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Dyck, Lionel B. (TRA)
> Sent: Friday, June 17, 2016 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> I like the idea of the RFE but could I suggest broadening it to all 
> BSAM/QSAM since any program that writes output could do the same 
> thing.  Put the test in the access method to prevent writing a 
> sequential dataset on top of a partitioned dataset.
> 
> --
> 
> Lionel B. Dyck (TRA Contractor)
> Mainframe Systems Programmer
> Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI 
> Service Delivery & Engineering
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Friday, June 17, 2016 10:59 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> After the discussion this week on recovering a PDS after IEBGENER was 
> used without a member on SYSUT2, I went ahead and opened the following 
> RFE (I did not find any currently in RFE on this)
> 
> If you like it, please vote for it
> 
> It is asking IBM to put a test into IEBGENER to see if SYSUT2 is a PDS 
> or PDSE.
> And if it is, and no member is specified on the SYSUT2, to terminate 
> the step with an RC12 and message about a PDS and no member name supplied.
> 
> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=9
> 0179
> 
> 
> Lizette Koehler
> statistics: A precise and logical method for stating a half-truth 
> inaccurately

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

Re: WAIT >1 (Friday type question, a day late)

[Robert A. Rosenberg]

At 14:41 -0700 on 06/18/2016, Charles Mills wrote about WAIT >1 
(Friday type question, a day late):



I just had occasion to RTFM on WAIT. I'm sure WAIT with an event count
greater than one seemed like a terrific idea at the time, but has anyone
ever used it? What's an application for "wait for any two of these five
events to occur"?

I suppose one reasonable application for an event count greater than one
would be "WAIT for _all_ of these events to occur."

Charles


I think the EVENTS call is designed for the "Wait Until X ECBs have 
been Posted" situation. OTOH, I may be wrong.


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

Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

[פנינה קוניגסברג]

Thanks so much Lizette and Lionel.  In my case, it was SYSPRINT of IDCAMS that 
'reconfigured' the PDS file, followed by edit of the sysprint output members. 
Believe me , the 'sandbox' is now backed up daily.   

.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Friday, June 17, 2016 7:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption

Cool.

I will see if I can append to the RFE.

Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Dyck, Lionel B. (TRA)
> Sent: Friday, June 17, 2016 9:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> I like the idea of the RFE but could I suggest broadening it to all 
> BSAM/QSAM since any program that writes output could do the same 
> thing.  Put the test in the access method to prevent writing a 
> sequential dataset on top of a partitioned dataset.
> 
> --
> 
> Lionel B. Dyck (TRA Contractor)
> Mainframe Systems Programmer
> Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI 
> Service Delivery & Engineering
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Friday, June 17, 2016 10:59 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] RFE opened on IEBGENER and PDS Corruption
> 
> After the discussion this week on recovering a PDS after IEBGENER was 
> used without a member on SYSUT2, I went ahead and opened the following 
> RFE (I did not find any currently in RFE on this)
> 
> If you like it, please vote for it
> 
> It is asking IBM to put a test into IEBGENER to see if SYSUT2 is a PDS 
> or PDSE.
> And if it is, and no member is specified on the SYSUT2, to terminate 
> the step with an RC12 and message about a PDS and no member name supplied.
> 
> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=9
> 0179
> 
> 
> Lizette Koehler
> statistics: A precise and logical method for stating a half-truth 
> inaccurately
> 
> --
> 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

--
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