Question & Answer
Question
After z/OS Encryption maintenance is applied (OA50569 and it's co-reqs), DCOLLECT may fail with the following error:
IDC3302I ACTION ERROR ON [dsname]
IDC3309I ** RECORD X'xxxxxxxx' NOT WRITTEN. LENGTH INVALID IDC21809I FAILURE ATTEMPTING TO WRITE D-TYPE RECORD FOR IDC21809I [dsname] ON VOLUME [volser]
Or when MIGRATEDATA is specified:
IDC21804I FAILURE DURING MIGRATION DATA COLLECTION SERVICE PROCESSING -
IDC21804I RETURN CODE WAS X'14' REASON CODE WAS X'040C4000
IDC01811I NUMBER OF 'M ' RECORDS PROCESSED WAS 1
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
IDC21804I FAILURE DURING MIGRATION DATA COLLECTION SERVICE PROCESSING -
IDC21804I RETURN CODE WAS X'14' REASON CODE WAS X'040C4000
IDC01811I NUMBER OF 'M ' RECORDS PROCESSED WAS 1
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
Answer
As part of encryption support, APAR OA51067 added several fields to the DCOLLECT 'D' and 'M' type record output (see below). This may require that the DCOLLECT output LRECL or primary/secondary allocation be increased, which is not uncommon when new features are introduced. It is generally recommended that the largest LRECL size, which is 32756 , be used to avoid having to increase it again in the future. If an OUTPUT LRECL is specified that is too small to fit a output record, the above IDC3302I error will be issued. Also if the primary & secondary allocation amount is small enough during MIGRATEDATA processing to cause an Abend B37 condition, the above IDC21804I may be issued, which indicates that an internal 0C4 was issued (addressed in OA56791).
| New DCOLLECT "D" type record fields: | ||||
| Offset | Type | Length | Name | Description |
| 386(X'182') | CHARACTER | 66 | DCDENCR | ENCRYPTION INFORMATION |
| 386(X'182') | UNASSIGNED | 2 | DCDTYPE | ENCRYPTION TYPE |
| 388(X'184') | CHARACTER | 64 | DCDKLBL | ENCRYPTION KEY LABEL |
| 452(X'1C4') | CHARACTER | 16 | * | RESERVED |
| 468(X'1D4') | CHARACTER | DCDADSIE | END OF DOCUMENT Note: DCDDCLAS, DCDSCLAS, DCDMCLAS, DCDSTOGP, AND DCDACCT ARE NOT RETURNED FOR ALTERNATE INDEXES. |
|
| New DCOLLECT "M" type record fields: | ||||
| 184(x'B8') |
BITSTRING
1... .... .1.. .... ..1. .... ...1 .... .... 1... .... .1.. .... ..1. .... ...1
|
1
|
UMFLAG2
UMRACFD UMGDS UMREBLK UMPDSE UMSMSM UMCOMPR UMLFS UMENCRP |
INFORMATION FLAG 2 RACF-INDICATED DATA SET IF SET TO 1, GENERATION GROUP DATA SET¹ IF SET TO 1, SYSTEM-REBLOCKABLE DATA SET¹ IF SET TO 1, PARTITIONED DATA SET EXTENDED¹ IF SET TO 1, SMS-MANAGED DATA SET. IF SET TO 1, COMPRESSED DATA SET. IF SET TO 1, DATA SET IS LARGE FORMAT SEQ. IF SET TO 1, DATA SET IS ENCRYPTED Note: ¹Only valid when the dataset is SMS-managed |
| 238(x'EE') |
BITSTRING
1... ....
1... ....
..1. ....
.... .xxx
|
1 |
UMFLAG3
UMEMPTY
UMEMPTY
UMZFS
*
|
INFORMATION FLAG3
ON, IF DATA SET WAS EMPTY AT THE TIME OF
MIGRATION ON, IF DATA SET WAS EMPTY AT THE TIME OF
MIGRATION ON - VSAM LINEAR data set for ZFS usage
RESERVED
|
| 239(x'EF') |
BITSTRING
1... ....
.1.. ....
...1 ....
.... 1...
.... .1..
.... .xxx
|
1 |
UMFLAG4
UMALLSP_FMB
UMUSESP_FMB
UMRECSP_FMB
UMDSIZE_FMB
UM_FMB
*
|
INFORMATION FLAG 4
MBYTE FLAG FOR UMALLSP
MBYTE FLAG FOR UMUSESP
MBYTE FLAG FOR UMRECSP
MBYTE FLAG FOR UMDSIZE
When set to 1, UM_USER_DATASIZE and
UM_COMP_DATASIZE are in megabytes RESERVED
|
[{"Product":{"code":"SWG90","label":"z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"5695DF103 - DFSMS\/MVS ACCESS METHOD SERVICES","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"2.1;2.2;2.3","Edition":"","Line of Business":{"code":"LOB56","label":"Z HW"}}]
Was this topic helpful?
Document Information
Modified date:
03 September 2021
UID
isg3T1027127