| Fixed By |
Op. Sys. |
Query Ref. |
Description |
| S202z20 |
All |
(SQ11852 - 2010/03/01) |
0C6 occurs on a SELCOPY statement in error that
contains a FROM position and an LRECL value which
is an unresolved numeric expression involving "+"
and/or "-" operators.
Same problem in previous release. |
| S202z19 |
MVS |
(SQ11850 - 2010/02/18) |
0C6 and other potential failures on multiple CALL
statements to a mixture of COBOL II and Enterprise
COBOL compiled routines.
Same problem in previous release. |
| S202z18 |
VSE |
(SQ11817 - 2010/02/18) |
ERROR 505 and failure to decrypt CA-EPIC encryted
input TAPE file. This zap introduces the option
to allow SELCOPY to perform standard LIOCS for
input tapes so bypassing SELCOPY's additional error
checking for input BLKSIZE.
To do this, CBLSUSR2 x'04' bit flag must be set on
(STapeInpLIOC=YES for CBLNAME assembly).
Note that DEV=TAPE must be specified on the tape
input READ statement if fname (TLBL/CA-EPIC DDNAME)
is not of the format TAPEnn.
Latest CBLNAME macro supporting option STapeInpLIOC
is available at:
ftp://ftp.cbl.com/Mainframe/ALL/CBLNAME
|
| S202z17 |
MVS |
(SQ11814 - 2009/01/20) |
With ZAP 12 (Ref: s202z12) applied, ERROR 077 -
VSAM OPEN FAILURE is given for empty VSAM input
even with CBLNAME option SVsamRc160=Empty in
effect. |
| S202z16 |
MVS |
(SQ11805 - 2008/11/13) |
With ZAP 04 (Ref: s202z04) or ZAP 05 (Ref: s202z05)
applied, 0C1 Abend may occur at SELCOPY+10ED2 on
input of a SAM file, as a result of SELCOPY's free
storage management. |
| S202z15 |
MVS |
(SQ11784 - 2008/08/20) |
With ZAP 09 (Ref: s202z09) applied, 0C1 Abend
may occur at SELCOPY+1DDAC on input of a ddname
which is a JCL concatenation of data sets, one of
which resides on an LBI capable device (e.g. TAPE).
Zap 09 is a pre-requisite.
|
| S202z14 |
MVS |
(SQ11780 - 2008/08/20) |
ERROR 585 (with text "ZAP 64") introduced by fix
S200z64 (for Rel 2.00) avoided potential 0C4
(or garbage input) for files with input buffers
above the 16MB line. (e.g. Using RMODE31=BUFF, or
ACCBIAS=SYSTEM). S202z14 sophisticates S200z64
by handling above the line buffers properly,
provided a WORKLEN is in use.
This fix also modifies the text accompanying
ERROR 585 to "202z14".
|
| S202z13 |
MVS |
(SQ11764 - 2008/08/20) |
S878 REASON CODE 10 - Error during GETMAIN
at EOJ of a DB/2 job.
Error introduced by SELCOPY 2.00 Zap 81 (Ref: s200z81).
|
| S202z12 |
MVS |
(SQ11758 - 2008/08/20) |
0C6 abend at SELCOPY+101D9 when reading a VSAM
file with RLS=xx specified on the DD card. |
| S202z11 |
MVS |
(SQ11757 - 2008/03/25) |
With ZAP 09 (Ref: s202z09) applied, 0C1 Abend
occurs on a VSAM open of DDNAME allocated to DUMMY.
Zap 09 is a pre-requisite.
|
| S202z10 |
All |
(SQ11756 - 2008/03/20) |
0C4 Abend during SYSIN/SYSIPT SELCOPY control
statement analysis when all the following are true:
- "*" (asterisk) comment indicator is in the
first column of the control statement.
- The cotrol statement begins on a storage page boundary.
- Storage page immediately before is protected
i.e. not allocated by SELCOPY.
Same problem in previous release.
|
| S202z09 |
MVS |
(SQ11740 - 2008/02/22) |
IEC141I 013-E1 abend when SELCOPY attempts to OPEN
a data set defined with BLKSIZE>32K. Primarily
occurs on z/OS 1.7 and later, or on previous
releases with IBM tolerance APAR OA09869 applied,
where block size information is recorded in tape
HDR2 labels.
Where BLKSIZE>32K is supported (for Tape devices
and DUMMY), this zap allows use of BLKSIZE>32K for
data set Input/Output by employing the system
Large Blocksize Interface (LBI).
** Important **
Zap s202z09 will fail to Verify if the special zap
(Ref: SQ11647) which disables ERROR 582 is applied.
See SELCOPY 2.02 Install FAQ 05 at:
http://www.cbl.com/selcfaq.html#x5
FAQ 05 contains links to a SQ11647 zap roll back
job and an amended version of the SQ11647 zap.
Same problem in previous release.
|
| S202z08 |
MVS |
(SQ11708 - 2008/02/22) |
ERROR 584 - OUTPUT DSN ALREADY OPEN should always
and immediately be issued, regardless of program
logic, if an attempt is made to open an output
file where the DSN matches the DSN on any other
file, and the open has not been (explicitly or
implicitly) deferred. |
| S202z07 |
MVS |
(SQ11691 - 2008/02/22) |
ERROR 581 - ZAP 43 incorrectly returned on input
of JCL concatenated, RECFM=V data sets where the
allocated LRECL of the 2nd or subsequent data set
in the concatenation is greater than the LRECL of
the first data set. |
| S202z06 |
MVS |
(SQ11658 - 2007/07/03) |
ERROR 572 - DD/DLBL EXISTS WITH DIFF NAME on a
re-open of a DIRDATA input stream, previously
dynamically allocated to the same FName using a
different dsn, following an explicit OPEN/CLOSE. |
| S202z05 |
MVS |
(SQ11630 - 2007/05/23) |
## IMPORTANT ZAP for MVS ##
Due to customer pressure, a change introduced in
SELCOPY 2.02 has been reversed following problems
with legacy code, thus
WRITE ABC VSAM LRECL=80
will therefore revert to being interpreted as
treating the VSAM file, ABC, as RECFM=F, which
causes all records written to that file to be of
fixed length 80.
Without Zap 05 applied, SELCOPY 2.02 treats the
above WRITE statement as defining the maximum
output LRECL as 80 and will write records of length
equal to the current LRECL value.
Possible problems were:
- RC=05:
Truncation due to current LRECL being greater
than the LRECL value specified on the WRITE.
- No Error:
Records written could be shorter than intended
due to current LRECL being less than the LRECL
value specified on the WRITE, which of course
is a serious error.
Please apply Zap 05 and accept our sincere
apologies.
|
| S202z04 |
All |
(SQ11641 - 2007/05/14) |
Input of empty VSE/VSAM file under CMS causes a
loop on file OPEN (VSAM Error 160).
Same problem in Release 2.00 with Zap 80 applied. |
| S202z03 |
MVS |
(SQ11635 - 2007/05/14) |
IEA705I ERROR DURING GETMAIN SYS CODE = 878-10 is
possible on input where BLKSIZE is unknown.
(e.g. DD DUMMY.) Default set back to LRECL instead
32K-8 maximum.
Same problem in Release 2.00 with Zap 46 applied. |
| S202z02 |
MVS |
(SQ11633 - 2007/05/04) |
S0C1 at offset 1B8E4 on READ DIR of PDS/PDSE
Load Library or any RECFM=U data set.
Same problem in Release 2.01 with Zap 01 applied. |
| S202z01 |
VSE |
(SQ11623 - 2007/05/04) |
ERR641 or ERR642 may occur on CA-EPIC
managed file I/O. Caused by SELCOPY file label
SYS/volser checking prior to OPEN, thus avoiding
4883I abend.
Same problem in Release 2.00 with Zap 16 applied. |