Re: IEBCOPY with I/O error on SYSIN

2012-02-17 Thread J R 
I would have thought that the effect of a dummy, empty or omitted SYSIN 
is perfectly well known.  Moreover, its "shortcut" functionality is not limited 
to compress operations.  

More to the point, a malfunctioning SYSIN dataset is "none of the above" 
and it makes no sense to interpret it as such.  

 > Date: Thu, 16 Feb 2012 16:27:17 +
> From: mike.wawio...@barclays.com
> Subject: Re: IEBCOPY with I/O error on SYSIN
> To: IBM-MAIN@bama.ua.edu
> 
> This behaviour gives a simple, and little known/used, method of running a 
> compress without control cards.
> 
> 1. Allocate SYSUT1 to your PDS
> 2. SYSUT2 DSN=*.SYSUT1
> 3. Omit SYSIN
> 
> Runs a compress of SYSUT1
> 
> Regards, 
> Mike 
> Mike Wawiorko
> Global z Connectivity and Automation Engineering
> Global Technology Infrastructure and Services
> Barclays Bank
> Ground Floor (B4), Turing House, Radbroke Hall, WA16 9EU (Mail Van 49)
> Tel: +44(0)1565 615415 or internal 7-2000-5415
> Mobile:  07824527120
> Email: mailto:mike.wawio...@barclays.com
> P Please consider the environment before printing this e-mail
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf 
> Of Mary Anne Matyaz
> Sent: 16 February 2012 12:12
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: IEBCOPY with I/O error on SYSIN
> 
> Paul,
> IEBCOPY is documented (and functions) as generating a SYSIN if none exists, 
> if it's dummied, or if it's an empty file. Not sure what category a 'bad' 
> file fits into, but I would guess it's essentially 'omitted'. 
> 
> If you feel strongly about it you could open a Share requirement. 
> 
> 
> From DFP Utilities: 
> 
> "When the SYSIN DD statement is a DD DUMMY, points to an empty file, or is 
> omitted, IEBCOPY will generate a COPY statement that allows you to run 
> IEBCOPY without supplying a control statement data set for SYSIN."
> 
> MA
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@bama.ua.edu with the message: INFO IBM-MAIN
> This e-mail and any attachments are confidential and intended
> solely for the addressee and may also be privileged or exempt from
> disclosure under applicable law. If you are not the addressee, or
> have received this e-mail in error, please notify the sender
> immediately, delete it from your system and do not copy, disclose
> or otherwise act upon any part of this e-mail or its attachments.
> 
> Internet communications are not guaranteed to be secure or
> virus-free.
> The Barclays Group does not accept responsibility for any loss
> arising from unauthorised access to, or interference with, any
> Internet communications by any third party, or from the
> transmission of any viruses. Replies to this e-mail may be
> monitored by the Barclays Group for operational or business
> reasons.
> 
> Any opinion or other information in this e-mail or its attachments
> that does not relate to the business of the Barclays Group is
> personal to the sender and is not given or endorsed by the Barclays
> Group.
> 
> Barclays Bank PLC. Registered in England and Wales (registered no.
> 1026167).
> Registered Office: 1 Churchill Place, London, E14 5HP, United
> Kingdom.
> 
> Barclays Bank PLC is authorised and regulated by the Financial
> Services Authority.
> 
> --
  
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: IEBCOPY with I/O error on SYSIN

2012-02-17 Thread Shmuel Metz (Seymour J.) 
In <9289112425599854.wa.maryanne4psugmail@bama.ua.edu>, on
02/16/2012
   at 06:12 AM, Mary Anne Matyaz  said:

>Not sure what category a 'bad' file fits into, but I would guess 
>it's essentially 'omitted'. 

That would be broken behavior.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: IEBCOPY with I/O error on SYSIN

2012-02-17 Thread Shmuel Metz (Seymour J.) 
In
,
on 02/16/2012
   at 04:27 PM, Mike Wawiorko  said:

>This behaviour

What behavior? The bevior Paul described, or the behavior in your
example? They're not the same.

>"When the SYSIN DD statement is a DD DUMMY, points to an empty file,
>or is omitted, IEBCOPY will generate a COPY statement that allows
>you to run IEBCOPY without supplying a control statement data set
>for SYSIN."

Paul had a SYSIN and it was neither empty nor a DUMMY.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

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

Re: IEBCOPY with I/O error on SYSIN

2012-02-16 Thread Mike Wawiorko 
This behaviour gives a simple, and little known/used, method of running a 
compress without control cards.

1. Allocate SYSUT1 to your PDS
2. SYSUT2 DSN=*.SYSUT1
3. Omit SYSIN

Runs a compress of SYSUT1

Regards, 
Mike 
Mike Wawiorko
Global z Connectivity and Automation Engineering
Global Technology Infrastructure and Services
Barclays Bank
Ground Floor (B4), Turing House, Radbroke Hall, WA16 9EU (Mail Van 49)
Tel: +44(0)1565 615415 or internal 7-2000-5415
Mobile:  07824527120
Email: mailto:mike.wawio...@barclays.com
P Please consider the environment before printing this e-mail
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Mary Anne Matyaz
Sent: 16 February 2012 12:12
To: IBM-MAIN@bama.ua.edu
Subject: Re: IEBCOPY with I/O error on SYSIN

Paul,
IEBCOPY is documented (and functions) as generating a SYSIN if none exists, if 
it's dummied, or if it's an empty file. Not sure what category a 'bad' file 
fits into, but I would guess it's essentially 'omitted'. 

If you feel strongly about it you could open a Share requirement. 


>From DFP Utilities: 

"When the SYSIN DD statement is a DD DUMMY, points to an empty file, or is 
omitted, IEBCOPY will generate a COPY statement that allows you to run IEBCOPY 
without supplying a control statement data set for SYSIN."

MA

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
This e-mail and any attachments are confidential and intended
solely for the addressee and may also be privileged or exempt from
disclosure under applicable law. If you are not the addressee, or
have received this e-mail in error, please notify the sender
immediately, delete it from your system and do not copy, disclose
or otherwise act upon any part of this e-mail or its attachments.

Internet communications are not guaranteed to be secure or
virus-free.
The Barclays Group does not accept responsibility for any loss
arising from unauthorised access to, or interference with, any
Internet communications by any third party, or from the
transmission of any viruses. Replies to this e-mail may be
monitored by the Barclays Group for operational or business
reasons.

Any opinion or other information in this e-mail or its attachments
that does not relate to the business of the Barclays Group is
personal to the sender and is not given or endorsed by the Barclays
Group.

Barclays Bank PLC. Registered in England and Wales (registered no.
1026167).
Registered Office: 1 Churchill Place, London, E14 5HP, United
Kingdom.

Barclays Bank PLC is authorised and regulated by the Financial
Services Authority.

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

Re: IEBCOPY with I/O error on SYSIN

2012-02-16 Thread Mary Anne Matyaz 
Paul, 
IEBCOPY is documented (and functions) as generating a SYSIN if none exists, if 
it's dummied, or if
it's an empty file. Not sure what category a 'bad' file fits into, but I would 
guess it's
essentially 'omitted'. 

If you feel strongly about it you could open a Share requirement. 


>From DFP Utilities: 

"When the SYSIN DD statement is a DD DUMMY, points to an empty file, or is
omitted, IEBCOPY will generate a COPY statement that allows you to run
IEBCOPY without supplying a control statement data set for SYSIN."

MA

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

IEBCOPY with I/O error on SYSIN

2012-02-15 Thread Paul Gilmartin 
I was testing running from Rexx z/OS 1.13 IEBCOPY, which doesn't
require authorization:

0IEB1021E OMVS,*,SYSIN   ,GET   ,WRONG LEN RECRD,00,QSAM
17.52.11 STC09793  +IEB1021E OMVS,*,SYSIN   ,GET   ,WRONG LEN 
RECRD,00,QSAM
  
\216^A\220÷Ù¯ç"\2370"\2370"\2370"\2370"\2370"\2370"\2370"\2370Ù¯ç\216^A 
÷\216^A&÷
  -÷\216^Aø÷\216^AØ÷^B^P  ^B^A\234^B^A øåÖ*\200
â^A^A 
5\227åÔè^A\234^A^A¶C\213Ì\210Û7\237ÛÜ\237\227^BÌ
  LEN=X'0050' SENSE=A338-00
  
\216^A\220÷Ù¯ç"\2370"\2370"\2370"\2370"\2370"\2370"\2370"\2370Ù¯ç\216^A ÷
  -÷\216^Aø÷\216^AØ÷^B^P  ^B^A\234^B^A øåÖ*\200
â^A^A 
5\227åÔè^A\234^A^A¶C\213Ì\210Û7\237ÛÜ\237\227^BÌ
  LEN=X'0050' SENSE=A338-00
  
\216^A\220÷Ù¯ç"\2370"\2370"\2370"\2370"\2370"\2370"\2370"\2370Ù¯ç\216^A ÷
  -÷\216^Aø÷\216^AØ÷^B^P  ^B^A\234^B^A øåÖ*\200
â^A^A 
5\227åÔè^A\234^A^A¶C\213Ì\210Û7\237ÛÜ\237\227^BÌ
  LEN=X'0050' SENSE=A338-00
  
\216^A\220÷Ù¯ç"\2370"\2370"\2370"\2370"\2370"\2370"\2370"\2370Ù¯ç\216^A ÷
  -÷\216^Aø÷\216^AØ÷^B^P  ^B^A\234^B^A øåÖ*\200
â^A^A 
5\227åÔè^A\234^A^A¶C\213Ì\210Û7\237ÛÜ\237\227^BÌ
  LEN=X'0050' SENSE=A338-00
-STEP1COPY  INDD=SYSUT1,OUTDD=SYSUT2 GENERATED STATEMENT
0IEB1013I COPYING FROM PDS   INDD=SYSUT1   VOL=M20RES DSN=SYS1.MACLIB
 IEB1014I   TO PDSE OUTDD=SYSUT2   VOL=WORK01 
DSN=SYS12046.T175200.RA000.user9.R0F32424
17.52.45 STC09793  IEC032I 
E37-04,IGC0005E,user9,STEP1,SYSUT2,4158,WORK01,SYS12046.T175200.RA000.user9.R0F32424

The I/O error is somewhat intentional, and correctly reported by IEBCOPY.
Yet I have a complaint:

-STEP1COPY  INDD=SYSUT1,OUTDD=SYSUT2 GENERATED STATEMENT

... seems imprudent.  On encountering an I/O error and reading nothing
legible on SYSIN, IEBCOPY ought to quietly quit rather than attempting
to DWIM.

What if I had intended SYSUT2 as an input data set?  (I know, bad practice,
but still ...)

-- gil

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