What causes abend ADSTH944+001ED2 and error message: ADSTH944 4587
Article ID: 16076
Updated On:
Products
Issue/Introduction
What causes this error message:
ADSTH944 4587 CARTRIDGE SIZE ( 40,960MB) DOES NOT MATCH SYSPARM DLMVSIZ1, DLMVSIZ2, DLMVSIZ3 OR DLMVSIZ4
Environment
Component:
Resolution
PTF RO91662 changes the format of the DLMVSIZx SYSPARMs and provides support to interpret
DLMVSIZ1-4 values in MB, GB, and TB as well as to enforce a maximum of 32TB.
These Sysparm updates have been added to support EMC DLm VTE's and are required
for the cartridge(s) defined in your DLm volume size definition.
NOTE: The DLMVSIZx SYSPARMs must now be supplied via the SYSPARMS member in CCUWPARM
and cannot be overridden through the " //SYSPARMS DD * ".
DLMVSIZxnnnnnnnnyy
This SYSPARM is required for the cartridge(s) defined in your DLM volume size definition.
Valid for ARCHIVE, BACKUP, BACKUPCC, RESTORE, RECOVER, VRECOVER, IXMAINT, MERGE, and XCOPY.
They define the cartridge size(s) being used in your shop.
x - Specify a 1 character value starting with 1, in sequence with a maximum of 4,
to define a cartridge to be used.
nnnnnnnn - This is the numeric size value.
yy - is the type value where MB is megabytes, GB is gigabytes and TB is terabytes.
If yy is not specified, GB is used. These values must match your DLM volume size definition.
Additional Information
Example for a shop using a single cartridge size of 200GB:
DLMVSIZ100200 (pseudo device type would be D3481, D3491 or D3591)
Examples for a shop using multiple cartridges with sizes of 220GB and 300GB:
DLMVSIZ100220 (pseudo device type would be D3481, D3491 or D3591)
DLMVSIZ200300 (pseudo device type would be D3482, D3492 or D3592)
Examples for a shop using multiple cartridges of 10GB, 800MB, 32TB and 500GB:
DLMVSIZ100000010GB (pseudo device type would be D3481, D3491 or D3591)
DLMVSIZ200000800MB (pseudo device type would be D3482, D3492 or D3592)
DLMVSIZ300000032TB (pseudo device type would be D3483, D3493 or D3593)
DLMVSIZ400000500GB (pseudo device type would be D3484, D3494 or D3594)
**CAUTION** Changing the size of the same DLMVSIZx Sysparm from one value to another
should not be done without considering existing ARCHVOL records.
For example, if DLMVSIZ2 has been defined as 280GB, changing this value to 300GB
could cause problems for any existing ARCHVOL record(s) that used that value.
It would be safer to define a new Sysparm with the desired size.
In this example, defining DLMVSIZ3 with a value of 300GB would be the safest thing to do.
To verify if a DLMVSIZx Sysparm is in use, a second line has been added to the LISTV report
showing the applicable Sysparm.
Caution: If this PTF is RESTORED from your CA Disk CCUWLOAD Target Library,
you must revert back to the DLMVSIZ1-4 that were used prior to applying this PTF.
NOTE: PTF RO91662 is PE, corrected by PTF RO95205 for a problem in Merge.
New Messages:
4611 - SYSPARM DLMVSIZX VALUE OF nnnnnn EXCEEDS MAXIMUM OF 32TB
Reason: SYSPARM DLMVSIZx supports a maximum value of 32 terabytes.
Action: Correct SYSPARM DLMVSIZx value and then resubmit the request.
4612 - SYSPARM DLMVSIZX nnnnnn IS INVALID
Reason: SYSPARM DLMVSIZx values can be entered with up to 8 digits and a suffix of
MB, GB or TB and up to a maximum of 32 terabytes.
Action: Correct SYSPARM DLMVSIZx value and then resubmit the request.
4613 - DEVICE CAPACITY nnnnnnnn EXCEEDS 32TB
Reason: The calculated EMC DLM VTE media capacity exceeded the maximum value of 32 terabytes.
Action: Contact CA Technical Support for assistance.
Feedback
