I was testing running from Rexx z/OS 1.13 IEBCOPY, which doesn't
require authorization:
0IEB1021E OMVS,*,SYSIN ,GET ,WRONG LEN RECRD,00000000000000,QSAM
17.52.11 STC09793 +IEB1021E OMVS,*,SYSIN ,GET ,WRONG LEN
RECRD,00000000000000,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
-STEP1 COPY 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:
-STEP1 COPY 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 [email protected] with the message: INFO IBM-MAIN
