Service and support

• UD53142
• UD53104

• UD53329

// JOB UD53329
// OPTION CATAL
// EXEC MSHP
APPLY   5686-CF8-06-91G:UD53329
REQUIRES PRE=(CF891G);
RESOLVES APARS=(DY46863);
AFFECTS MACROS=(MAPSCBLK) TYPE=A;
DATA;
/$
/*
/&

F2 0114 DFHSO0106 DBDCCICS 17/04/08 09:50:44 
DBDCCICS A Language Environment Callable 
Service error (code X'0226') has occurred in 
module DFHSOCK.
F2 0114 DFHME0116 DBDCCICS (Module:DFHMEME) 
CICS symptom string for message DFHSO0106 is
PIDS/564805400 LVLS/411 MS/DFHSO0106 
RIDS/DFHSOCK PTFS/UK20279 PRCS/00000226.

// EXEC MSHP                           
   REMOVE  5648-054-00-B0P PTF=UK25490 
/*

ARI0866E Input record data field error:
        Column = ITEM Input Record Count = 26473
(000001):4040F1F5C3F0F740F2F5F040404040404040968
(000056):40404040404040404040404040404040E2F0F0F

• PTFs enabling IBM System Storage TS1120 encrypting tape drives
• DB2 Server for VSE & VM V7.5
• accumulated service

// EXEC MSHP
CORRECT 5686-CF-706-81C : DY46780
AFFECTS PHASE=$IJJGTOP
ALTER  4B2A  A79A0001 : 0700D201
ALTER  4B2E  40903024  : 3024803C
RESOLVES 'MESSAGE 4331D VOLUME SEQUNCE'
/*

Up to 10 datasets for DL/I HD databases

With APAR PK48347 (PTF UK26815) the maximum number of datasets that can be allocated for HD databases with DL/I 1.11 has been increased from 5 to 10 datasets allowing a maximum database size of 10 * 4 = 40 GB. Users, who are already working with 5 datasets at some database and who are approaching capacity limits with the current maximum of 20 GB may now be able to extend this database by allocating more datasets.

Additional datasets can be defined through the following procedure:

• Unload database with the existing DBD/PSB definitions
• Add new dataset(s) in the DBD, run DBDgen and create new DMB and PSB execution blocks (ACBgen)
• Reload database with new DBD/PSB definitions, when necessary including runs of the pre-reorganization, prefix resolution and prefix update utilities

It is also required to provide DLBL statements for the additional datasets in all jobs that are accessing a database with the extended DBD and add the according control statements for the new datasets in all affected DL/I backup and recovery jobs.

For more information, please see the documentation included in PK48347 or contact your DL/I support.

• z/VSE V4.1: DY46682 (UD53141 and UD53142)
• z/VSE V3.1: DY46685 (UD53143,UD53144, UD53146) and PK43473 (UK24398)
• z/VM:  VM64062  (UM32012)
• DITTO: PK44172  - With this Apar, DITTO/ESA for VSE supports tape encryption interactively and via standard VSE JCL in BATCH mode

For a detailed description please see the updated chapter Implementing Hardware-Based Tape Encryption (PDF, 231KB) in the z/VSE V4R1 Administration guide.

'IDC2950I INVALID FORMAT STRUCTURE' on MASTERCATALOG LISTCAT

For a detailed description please see IDC2950I INVALID FORMAT STRUCTURE (PDF, 24KB)

1S40I SYSTEM ERROR, LABEL 
          RET.CODE=0E REASON CODE=06
1S40D SYSTEM ERROR, LABEL 
          RET.CODE=0E REASON CODE=04

CATALOG $0JCL.PROC DATA=YES REPLACE=YES 
STDOPT ACANCEL=NO,DECK=NO,DUMP=PART,... 
SYSDEF DSPACE,DSIZE=12M 
// EXEC PROC=STDLABEL (remove this statement)
// VDISK UNIT=FDF,BLKS=2880,VOLID=VDIDLA,...
* VDISK UNIT=CUU,BLKS=81920,VOLID=VDIWRK 
// EXEC PROC=STDLABEL   CALLS STDLABUP AND ... 
// EXEC PROC=SETSDL     SET SDL

TCP/IP for VSE Service Pack E (APAR PQ87041) is now available.
For VSE/ESA 2.7 the PTF number is UK19329.
For z/VSE 3.1 the PTF number is UK19330.
For VSE/ESA 2.6 we are no longer providing PTFs because this CLC 1OQ is out of service since 03/31/2006.

Note: Before installing Service Level E, be sure to read the  Problem Summary, especially the Security section and perform the required actions.

New ACF/VTAM V4.2  31-bit I/O Buffer support for z/VSE V3.1:
In the current ACF/VTAM implementation, VTAM I/O buffers use 24-Bit System Getvis storage. For some customers, this restriction creates a storage constraint. Customer requiremens (e.g. WAVV200414, WAVV200311, WAVV200242, WAVV200224) have requested that IBM allows to move these I/O buffers 'above the line' (into 31-Bit System Getvis storage).

IBM's response is the VTAM 31-Bit I/O Buffer Support in z/VSE 3.1. With this new function, ACF/VTAM can move I/O buffers (IOBUF pool) and all I/O CTC packing buffers in 31-Bit System Getvis storage (VTAM startup option IOBUF31=YES). This enhancement allows z/VSE customers to grow their communication workloads.

To use this support PTF UD52873 and PTF UD53035 (AF Base) or UD52874 and UD53060(Generation Feature) must be applied to z/VSE V3.1. In addition PTF UD52964 and PTF  UD53054 must be applied to ACF/VTAM V4.2.

z/VSE VTAM 31bit I/O Buffer Support (20KB)

With z/VSE 3.1.1, initial installation may fail, first IPL goes into a loop:
A few users experienced problems with the initial installation of z/VSE V3.1.1. For technical details and a local fix see  here (PDF, 8KB). As a result, we developed a solution (APAR  DY46515). We applied the APAR and replaced the z/VSE V3.1.1 tapes at the distribution centers as of February 8. 

z/VSE V3 customers fall into three groups:

1. If you ordered z/VSE V3.1.1 before February 8, and successfully installed the system, the fix does not apply to you.
2. When you order z/VSE V3.1.1 anytime after February 8, you'll get an updated system with the fix applied.
3. If you ordered z/VSE V3.1.1 before February 8, but have not yet installed it, we suggest you reorder the system.  

In summary, the z/VSE V3.1,1 system you order now includes an important fix.  We recommend that all customers with z/VSE V3.1.1 'on the shelf' (but who have not yet installed it for whatever reason), reorder z/VSE V3.1.1 before trying to install the system. 

Large Dasd (3390 model F) Exploitation in VSE/ESA 2.6 and VSE/ESA 2.7:
In order to exploit the Large DASD Support in VSE/VSAM, it is vital and essential to install the PTF for  APAR DY46113.

Migration to Large DASD without changing old (legacy) definitions for files, may result in the definition of a VSE/VSAM cluster that is allocated less than 1 CYLINDER in size. This will result in overlapping EXTENTS.

Installation of VSE/ESA 2.5 and 2.6 on zSeries systems with HiperSockets defined in the IOCDS:
This information is intended for customers who are planning to install a VSE/ESA 2.5.x or VSE/ESA 2.6.x system natively on a zSeries system where HiperSockets are defined in the IOCDS.

If the zSeries hardware has HiperSockets defined the native (means: not under VM) installation of a VSE/ESA 2.5 or 2.6 system will fail with hardwait during initial installation from tape.

To successfully proceed with the VSE/ESA installation the HiperSockets devices have to be disabled. This can be done by setting the HiperSockets devices or their related CHPIDs 'offline' at the hardware console.

If planning to install VSE/ESA under z/VM it is recommended that you define no HiperSockets devices to this guest system. HiperSockets are not supported by VSE/ESA 2.5.x or 2.6.x.

This problem will not occur with VSE/ESA 2.7.

See Info APAR  II13511.

• This only applies to BACKUPs that contain REUSE ESDS files that have been reset (i.e., contain a single initialization record).
• No data is lost or corrupted.
• Explicit RESTORE of individual files is still possible.
• Problem files can be skipped via the EXCLUDE parameter.
• A patch is available from the IBM Support Center if there are so many files that use of the EXCLUDE parameter is prohibitive. Please refer to Informational APAR II13501.

VSE/ESA VSAM APAR:

With PTFs UD52124 (VSE/ESA 2.4), UD52125 (VSE/ESA 2.5) and UD52126 (VSE/ESA 2.6) bogus compression error messages may occur. These PTFs have been superceded by UD52127 (VSE/ESA 2.4), UD52128 (VSE/ESA 2.5) and UD52129 (VSE/ESA 2.6).

VSE/ESA Supervisor APAR:

On level DY45817 a Program Check loop may occur right after MSG0I20I. Therefore DY45817 has been superseded by DY45921.

VSE/ESA 2.6 Virtual Tape Support:

In general, the Virtual Tape Support included in VSE/ESA 2.6 is intended to be transparent to applications and to provide the customer with the ability to read from or write to a virtual tape in the same way as if it were a physical tape.

For technical and performance reasons, the full range of the capabilities of a physical tape has not been implemented. Before you use the VSE/ESA 2.6 Virtual Tape Support, you must first install the PTF UD52009 (APAR DY45789). This is required to ensure correct operation in different environments. A list of supported functions and usage recommendations can be found here.

Important Note for Users Performing a FSU to VSE/ESA 2.6.0:

This problem only affects Users that have the Generation Feature installed.

Users that do not have the Generation Feature installed are not affected by this problem.

Performing a release upgrade to VSE/ESA 2.6.0 via FSU, a user with the Generation Feature installed must follow the appended recommondation in order to avoid errors during FSU:

On panel SRV$FS03 (that is presented on selection 1433 - FSU Installation) there is a selection for GEN-LIB refresh. The selection here should always be 2 (NO) to ensure a sucessful FSU.

The generation library is deleted and removed from the system history file during the FSU but can easily be reinstalled later.

With this option, the created job DTRFSU will run without problems.

If you already selected 1 (YES) on SRV$FS03 the following Error will occur:

Step 16, Job DTRFSU16
* STEP 16: REFRESH GENERATION FEATURE
will show the following error message:

1F33D PARAMETER XLAST NOT DEFINED .

To recover from this Error, abort the FSU jobs sequence, delete all FSU-Jobs from the reader queue (L RDR,DTR*) and recreate the job sequence using selection 1433 as described above).