On Thu, 17 Jan 2008 16:17:09 -0800, Frank Yaeger [EMAIL PROTECTED] wrote:
Mark Zelden wrote on 01/17/2008 03:33:11 PM:
I used SORTGENR for years (in the old days) at shops that didn't
have ICEGENER or SYNCGENR installed:
//STEP1EXEC PGM=SORT
//SORTIN DD DISP=SHR,DSN=input
//SORTOUT
Date:Tue, 15 Jan 2008 17:06:04 -0600
From:Paul Gilmartin [EMAIL PROTECTED]
Subject: Re: IEBGENER is BROKEN
And I might mention that DUMMY is __required__. We had some jobs that
ran with SYSIN being a DD *, but with no control cards. This is,
technically, equivalent to DUMMY
Tom Russell wrote on 01/17/2008 02:42:06 PM:
A DD DUMMY, or DSN=NULLFILE, or no //SYSIN allows DFSORT to know that
ICEGENER is OK to go. Anything else requires them to OPEN and READ the
file. Much easier just to XCTL to IEBGENER and let it work it out. Why
would they OPEN the file?
Yes,
Mark Zelden wrote on 01/17/2008 03:33:11 PM:
I used SORTGENR for years (in the old days) at shops that didn't
have ICEGENER or SYNCGENR installed:
//STEP1EXEC PGM=SORT
//SORTIN DD DISP=SHR,DSN=input
//SORTOUT DD DISP=SHR,DSN=output
//SYSOUT DD SYSOUT=*
//SYSINDD *
SORT
On Thu, 17 Jan 2008 15:02:53 -0800, Frank Yaeger [EMAIL PROTECTED]
Yes, that's correct. ICEGENER is just a front-end for calling DFSORT
copy
or IEBGENER so we don't do any I/O processing in ICEGENER itself. I was
trying to avoid discussing how ICEGENER works internally, but since you
figured
Paul Gilmartin wrote:
On Tue, 15 Jan 2008 15:01:58 -0700, Steve Comstock wrote:
And I might mention that DUMMY is __required__. We had some jobs that
ran with SYSIN being a DD *, but with no control cards. This is,
technically, equivalent to DUMMY, but not by ICEGENER. The same applies
to an
In [EMAIL PROTECTED], on 01/14/2008
at 04:38 PM, Paul Gilmartin [EMAIL PROTECTED] said:
Historically, many programs have had RECFM, LRECL, and sometimes BLKSIZE
hard coded in DCB macros.
And not documented :-(
(Usually the troublemaker would remember to specify a member name.)
Ah, yes.
In [EMAIL PROTECTED], on 01/15/2008
at 05:46 PM, Ed Gould [EMAIL PROTECTED] said:
as the TMP has no other way to signify EOF to the program.
The TMP isn't involved; it's handled in the access method.
BTW, if you allocate a DASD data set for SYSIN, *DON'T* put a /* at the
end.
--
On Mon, 14 Jan 2008 21:17:15 -0600, Walt Farrell ... wrote:
snip
If I have a VB (or even an FB) with a larger LRECL, it shouldn't take
handstands to copy!
For VB, I agree.
For FB, how would you like the output padded? Blanks? Binary zeros?
One of those will be incorrect for some
IMHO ICEGENER does it right IEBGENER does it wrong. Most sites have
an alternative copy utility by way of the SORT utility and it should provide
better performance than IEBGENER... so vote with your feet and avoid
IEBGENER whenever you can.
Bill
On Tue, 15 Jan 2008 03:12:48 -0600, Zaromil
Zaromil Tisler wrote on 01/15/2008 01:12:48 AM:
The argumentation above was apparently not used in ICEGENER design,
the ICEGENER (as a replacement for IEBGENER SYSUT1 DD DUMMY
combination) takes another approach:
Copying PS V shorter to PS V larger brings RC=0.
Copying PS F shorter to PS FB
On Tue, 15 Jan 2008 08:01:40 -0800, Frank Yaeger
[EMAIL PROTECTED] wrote:
...
as a replacement for IEBGENER SYSUT1 DD DUMMY combination
That's SYSIN DD DUMMY, not SYSUT1 DD DUMMY.
...
Actually, SYSUT1 DD DUMMY simplifies things a bit.
It really speeds up the processing time. :-)
Pat O'Keefe
Patrick O'Keefe wrote on 01/15/2008 01:21:56 PM:
...
as a replacement for IEBGENER SYSUT1 DD DUMMY combination
That's SYSIN DD DUMMY, not SYSUT1 DD DUMMY.
...
Actually, SYSUT1 DD DUMMY simplifies things a bit.
It really speeds up the processing time. :-)
Right :-) To clarify, I
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Frank Yaeger
Sent: Tuesday, January 15, 2008 3:54 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: IEBGENER is BROKEN
Patrick O'Keefe wrote on 01/15/2008 01:21:56 PM:
...
as a replacement
McKown, John wrote:
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Frank Yaeger
Sent: Tuesday, January 15, 2008 3:54 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: IEBGENER is BROKEN
Patrick O'Keefe wrote on 01/15/2008 01:21:56 PM
John McKown wrote on 01/15/2008 02:01:10 PM:
And I might mention that DUMMY is __required__. We had some jobs that
ran with SYSIN being a DD *, but with no control cards. This is,
technically, equivalent to DUMMY, but not by ICEGENER. The same applies
to an empty dataset with no control cards.
On Tue, 15 Jan 2008 15:01:58 -0700, Steve Comstock wrote:
And I might mention that DUMMY is __required__. We had some jobs that
ran with SYSIN being a DD *, but with no control cards. This is,
technically, equivalent to DUMMY, but not by ICEGENER. The same applies
to an empty dataset with no
On Jan 15, 2008, at 5:06 PM, Paul Gilmartin wrote:
--SNIP
Can you expand on this (or am I requesting too much
a freebie)?
But (open message to designers): No! KISS dammit!
OPEN SYSIN; QSAM GET until you come to the end; then
CLOSE. Treat all empty data
On Tue, 15 Jan 2008 17:46:20 -0600, Ed Gould wrote:
On Jan 15, 2008, at 5:06 PM, Paul Gilmartin wrote:
--SNIP
Can you expand on this (or am I requesting too much
a freebie)?
But (open message to designers): No! KISS dammit!
OPEN SYSIN; QSAM GET until
On Jan 15, 2008, at 8:59 PM, Bill Godfrey wrote:
--
SNIP--
Ed
The utility never sees the /* from the terminal. The GET or READ-
and-CHECK
will take the EODAD exit. See the TSO/E Programming Services
manual, in the
chapter
Try to copy a VB 125 to a VB 140 and see what happens.
Then go read APAR OZ72277. Make sure you do not have a mouth full of
some beverage.
Regards,
Steve Thompson
-- All opinions expressed by me are my own and may not necessarily
reflect those of my employer. --
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Thompson, Steve
Try to copy a VB 125 to a VB 140 and see what happens.
Then go read APAR OZ72277. Make sure you do not have a mouth
full of some beverage.
The resulting torrent of illogic [is] most amusing.
Why
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Thompson, Steve
Try to copy a VB 125 to a VB 140 and see what happens.
Then go read APAR OZ72277. Make sure you do not have a mouth
full of some beverage.
The resulting torrent of illogic [is] most
John Chase wrote on 01/14/2008 11:23:41 AM:
-Original Message-
Try to copy a VB 125 to a VB 140 and see what happens.
Then go read APAR OZ72277. Make sure you do not have a mouth
full of some beverage.
The resulting torrent of illogic [is] most amusing.
Why would one expect
: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Kelman, Tom
Sent: Monday, January 14, 2008 3:08 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: IEBGENER is BROKEN
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Thompson, Steve
Try to copy a VB 125
Steve, are you really concerned about a 24-year-old APAR?
On Mon, 14 Jan 2008 13:53:52 -0500, Thompson, Steve
[EMAIL PROTECTED] wrote:
Try to copy a VB 125 to a VB 140 and see what happens.
Then go read APAR OZ72277. Make sure you do not have a mouth full of
some beverage.
Regards,
Steve
I tried to copy a VB/125 file to a VB/140 file using IEBGENER and got a RC=12:
So, why does IEBGENER care?
It should work.
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Peter X. DeFabritus
Sent: Monday, January 14, 2008 2:47 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: IEBGENER is BROKEN
Steve, are you really concerned about a 24-year-old APAR?
SNIP
I'm concerned
Discussion List IBM-MAIN@BAMA.UA.EDU
15/01/2008 09:59 a.m.
Please respond to
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
Re: IEBGENER is BROKEN
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
of
some beverage.
Steve, are you really concerned about a 24-year-old APAR?
It's documentation of how long IEBGENER has been broken (and apparently
nobody had noticed until now). Apparently it had been working correctly
before this APAR, which concluded in effect that it is improper to
move letter
Steve, are you really concerned about a 24-year-old APAR?
I agree. This is AFH. Discussing it just adds more noise to this list.
Bob Shannon
Rocket Software
--
For IBM-MAIN subscribe / signoff / archive access instructions,
If you use IEBGENER in straight copy mode, it does check and enforce that the
LRECLs match.
I think that violates the principle of least astonishment.
If I have a VB (or even an FB) with a larger LRECL, it shouldn't take
handstands to copy!
-
Too busy driving to stop for gas!
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Anthony Fletcher
If you use IEBGENER in straight copy mode, it does check and
enforce that the LRECLs match.
All well and good -- for FIXED-length records. Irrelevant for
VARIABLE-length records.
When you hang
On Mon, 14 Jan 2008 21:34:06 +, Ted MacNEIL wrote:
If you use IEBGENER in straight copy mode, it does check and enforce that the
LRECLs match.
I think that violates the principle of least astonishment.
Historically, many programs have had RECFM, LRECL, and sometimes BLKSIZE
hard coded in
At 15:31 -0600 on 01/14/2008, Chase, John wrote about Re: IEBGENER is BROKEN:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Anthony Fletcher
If you use IEBGENER in straight copy mode, it does check and
enforce that the LRECLs match.
All well and good
On Mon, 14 Jan 2008 17:28:28 -0500, Robert A. Rosenberg wrote:
At 15:31 -0600 on 01/14/2008, Chase, John wrote about Re: IEBGENER is
BROKEN:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Anthony Fletcher
If you use IEBGENER in straight copy mode, it does
On Mon, 14 Jan 2008 18:04:05 -0600, Dave Kopischke wrote:
Another oddity:
Not at all odd; merely BAD.
We had an issue with a PDS where a PDS was reblocked. A subsequent batch
JOB came along and reblocked it back to it's original smaller block size. I
believe it was an IEBCOPY compress with DD
On Jan 14, 2008, at 3:31 PM, Chase, John wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Anthony Fletcher
If you use IEBGENER in straight copy mode, it does check and
enforce that the LRECLs match.
All well and good -- for FIXED-length records. Irrelevant
-snip
When you hang your shirt in a different-size closet, does the shirt size
change?
-unsnip--
If you hang it in a smaller closet, that may make a difference. Will the
same size hangar fit?
On Mon, 14 Jan 2008 21:34:06 +, Ted MacNEIL [EMAIL PROTECTED] wrote:
If I have a VB (or even an FB) with a larger LRECL, it shouldn't take
handstands to copy!
For VB, I agree.
For FB, how would you like the output padded? Blanks? Binary zeros?
One of those will be incorrect for some
On Jan 14, 2008, at 6:47 PM, Paul Gilmartin wrote:
-SNIP---
IEBGENER's approach of only allowing matching parameters is
safest ???
Corruptions are very bad.
Shouldn't be utilities' responsibility; should be right in
OPEN -- Sx13 if someone tries to change
If you hang it in a smaller closet, that may make a difference. Will the same
size hangar fit?
Poor analogy.
The whole argument is about a larger DSN.
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff /
On Jan 14, 2008, at 10:10 PM, Paul Gilmartin wrote:
On Mon, 14 Jan 2008 21:41:12 -0600, Ed Gould wrote:
That is a problem which IBM should have fixed early on but I think
they kept it this way for compatibility reasons. Don't rant or rave
IBM has done other such items for compatibility
44 matches
Mail list logo
