|
|
| |
|
Multiple Information Retrieval,
Manipulation & Update for
IBM Mainframe, iSeries, UNIX & PC Platforms
|
Maintenance to SELCOPY and answers to frequently
asked questions may be found on this Technical Support page
and the FAQs
page respectively.
Users should refer
to these pages prior to contacting CBL directly.
As well as answers to general questions,
the FAQ lists may include solutions or work
arounds for problems that are not attributable
to an error in the repective program, or problems
for which a zap has not yet been published.
If you cannot find the answer to your query
on these web pages site, then please contact
the CBL query desk via the following:
CBL provides a 24 x 7 technical support service to all customers via telephone.
During normal office hours (09:30-17:30),
every endeavour is made to supply immediate
technical support via the telephone. At
all other times, including weekends and
Bank Holidays, a recorded telephone message
provides relevant telephone number(s) for
technical emergencies only.
|
| |
SELCOPY 2.02 Zap Summary
Please see end of product maintenance notification for
releases of SELCOPY prior to 2.02.
Please download and install the latest CBL product bundle for the
relevant operating system.
SELCOPY 2.00 zaps applied at source in SELCOPY 2.01 and SELCOPY 2.01 zaps applied at source in SELCOPY 2.02
are documented in the
SELCOPY 2.01 New Features document and
SELCOPY 2.02 New Features document respectively.
Zaps correct known errors in the above release and are all independent, unless specifically stated otherwise.
You may apply all of them, or only those applicable to your system. "All" indicates applicable to MVS, CMS and VSE.
(xQnnnnn - yyyy/mm/dd) indicates the CBL query reference and the date the zap was first published.
Once published, a zap will not be changed, except by a further zap. However its description may change to
indicate the further requirement.
Zap references are in the format Srelznn where:
- rel indicates the release of SELCOPY to which the zap applies.
- nn denotes the Zap number.
You can download all available zaps by clicking on the following link:
|
| Program Release |
ZIP File Size |
Last Update |
| SELCOPY Rel 2.02 |
14,971 bytes |
2008/03/25 14:10 |
|
Zap descriptions for SELCOPY Rel 2.02 follow. For details of zaps for other CBL programs
please refer to
the CBLi
and CBLVCAT
Technical Support pages.
|
| |
| Fixed By |
Op. Sys. |
Query Ref. |
Description |
| 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. |
|
|
|
|
|
|
