#Managing Storage in HDISV

#Quick reference

• Understanding storage
  • Default storage allocation
  • What counts toward storage?
• Monitoring storage usage
  • Using ISPF (Option 3.4)
  • Using TSO commands
  • Using USS commands
  • Storage ssage tips
• When to request additional storage
  • Signs more storage is needed
  • Planning for additional storage
• Requesting & mounting additional storage
  • What happens during storage mount
  • After storage is mounted
• Managing storage efficiently
  • Best practices
  • Storage monitoring schedule
• Troubleshooting storage issues

---

This guide explains how to manage storage in an HDISV instance, including understanding storage allocation, monitoring usage, and requesting additional storage when needed.

#Understanding storage

#Default storage allocation

Every HDISV instance includes:

User Volume Storage:

• Default Size: 100 GB (approximately two 3390 mod 54 volumes)
• Purpose: Store z/OS datasets and applications
• Volumes: USER01 and USMS01 (if SMS configured)
• Persistence: Data persists during recreate operations (MSI mode only)

System Storage:

• Purpose: z/OS operating system and middleware
• Management: Managed by IBM, not user-accessible
• Updates: Refreshed during recreate operations

↑ Return to Quick reference

#What counts toward storage?

Included in your 100 GB:

• Your datasets (ZOSADMN.*)
• Application data
• USS files in /u/zosadmn
• Custom libraries and programs

Not counted (managed separately, not persistent through recreate):

• z/OS system datasets
• Middleware (Db2, CICS, IMS)
• Temporary work files
• JES spool

↑ Return to Quick reference

#Monitoring storage usage

#Using ISPF (Option 3.4)

Check Dataset Space:

ISPF → 3 (Utilities) → 4 (Dslist)

DSLIST - DATA SETS MATCHING ZOSADMN.*

Enter "I" next to dataset for information:

I ZOSADMN.SOURCE.COBOL

Dataset Information:
  Tracks Used: 15
  Tracks Allocated: 20
  % Used: 75%

View All Your Datasets:

ISPF → 3.4

Enter: ZOSADMN.*

Review space usage for each dataset

↑ Return to Quick reference

#Using TSO commands

List Dataset Information:

LISTDS 'ZOSADMN.MY.DATA' ALL

Shows:
- Space allocated
- Space used
- Extents
- Volume serial

Check Volume Space:

LISTCAT ENTRIES('USER01') ALL

Shows total volume capacity and usage

↑ Return to Quick reference

#Using USS commands

Check USS File System:

# Check disk space
df -k /u/zosadmn

# Check directory sizes
du -sk /u/zosadmn/*

# Find large files
find /u/zosadmn -type f -size +10M -exec ls -lh {} \;

↑ Return to Quick reference

#Storage usage tips

Identify Space Hogs:

1. List all your datasets by size
2. Check for unused datasets
3. Look for duplicate data
4. Review temporary datasets

Common Space Issues:

• Old test datasets not deleted
• Duplicate copies of data
• Oversized allocations
• Unused libraries

↑ Return to Quick reference

#When to request additional storage

#Signs more storage is needed

Dataset Allocation Failures:

IKJ56247I SPACE REQUESTED NOT AVAILABLE

Volume Full Messages:

IEC030I B37-04 VOLUME FULL

USS File System Full:

No space left on device

↑ Return to Quick reference

#Planning for additional storage

Before Requesting:

1. Clean Up First

   • Delete unused datasets
   • Remove old test data
   • Compress or archive old files

2. Estimate Needs

   • Calculate current usage
   • Project future growth
   • Add buffer (20-30%)

3. Consider Alternatives

   • Archive old data off-system
   • Use more efficient storage formats
   • Compress large datasets

Storage Increments:

• Storage is ordered in 50 GB increments up to a maximum of 18 additional units (1 TB total user storage)

↑ Return to Quick reference

#Requesting & mounting additional storage

Step 1: Order storage

1. Navigate to the ZLPN Dashboard.
2. In the Actions menu to the right of the instance row for which you would like to order additional storage, select Order additional storage.
3. Enter the number of 50 GB units to be added and submit the form. NOTE: Storage orders are permanent; storage cannot be reduced after purchase.

Step 2: Mount storage

1. Navigate to the ZLPN Dashboard.
2. In the Actions menu to the right of the instance, select Mount storage.
3. The window shows the units of storage which have been ordered. Click Mount next to an ordered unit to mount that unit.
   • Each unit needs to be mounted individually.
   • Mounting storage can take up to ten minutes per 50 GB unit.
   • Status will update to Mounted when the process completes for each unit.
4. Repeat as necessary until all purchased units are mounted.

↑ Return to Quick reference

#What happens during storage mount

For Managed Service Mode:

1. The instance remains running
2. A new emulated mod54 CKD file is created and added to the zADE devmap on one of the available device numbers. The new devices are added in order starting with AA00 and ending with AA11.
3. The volume is not visible to z/OS until the instance is stopped and started

For Linux Access Mode:

1. The instance remains running
2. The block device mounted in Linux at /zos/user-ckd is grown automatically to consume the new storage

↑ Return to Quick reference

#After storage is mounted

#For Managed Service Mode:

1. Restart the instance through ZLPN dashboard

2. Logon to z/OS TN3270

3. Format the new DASD device. Here's some sample JCL to do this:

   DSSINIT.JCL

   //D#INTSMS JOB (D999),'INIT VOL',MSGCLASS=O,CLASS=A,
   //         NOTIFY=&SYSUID,REGION=0M  TYPRUN=HOLD
   //*
   //*  INITIALIZE DASD VOLUME WITH VTOC INDEX FOR SYSTEM DUMPS
   //*  VOLUMES MUST BE OFFLINE FOR INITIALIZATION
   //*
   //STEP1   EXEC PGM=ICKDSF
   //SYSPRINT DD  SYSOUT=*
   //SYSIN    DD  *
   INIT UNIT(AA00) VTOC(1,0,30) NOVAL VERIFY(*NONE*) -
   VOLID(xxxx) INDEX(3,0,15) NOPURGE NOVERIFYOFFLINE 
   

4. From SDSF there will be a WTOR Reply U to WTOR

   RESPONSE=LTE1                                                  
   IEE112I 22.20.54 PENDING REQUESTS 107                         
   RM=1    IM=0     CEM=0     EM=0     RU=0    IR=0    AMRF      
   ID:R/K     T SYSNAME  MESSAGE TEXT                            
            02 R LTE1     *02 ICK003D REPLY U TO ALTER VOLUME AA00
                        CONTENTS, ELSE T
   

   Reply: R xx,U

5. From SDSF, vary online the new DASD device

   /v aa00,online
   

#For Linux Access Mode:

1. Grow the filesystem to consume the new space:

   xfs_growfs /zos/user-ckd

2. Create new CKD files to represent 3390 DASD devices in zADE. Be sure to use the /zos/user-ckd directory to store CKD files.

   Example:

   $ alcckd /zos/user-ckd/my-volume.ckd -d3380-1
   AWSCKE035I Creating file '/zos/user-ckd/my-volume.ckd', 3380, 885 cylinders
   
   AWSCKE072I 100 percent complete ...
   AWSCKE005I Processing file '/zos/user-ckd/my-volume.ckd' ...
   AWSCKE006I    Device type: 3380-1
   AWSCKE009I      Cylinders: 885, heads 15
   AWSCKE010I     Track size: 47616
   AWSCKE011I   File version: 0
   AWSCKE014I   Version pend: No
   AWSCKE017I       IPL text: No
   AWSCKE018I  Volume serial: <None>
   

   For more information see section 4.2.3 The alcckd command in https://www.redbooks.ibm.com/redbooks/pdfs/sg248205.pdf

3. Update your zADE devmap to include the new CKD file in the awsckd manager stanza.

   For more information see section 3.6.1 The awsckd device manager in https://www.redbooks.ibm.com/redbooks/pdfs/sg248205.pdf

↑ Return to Quick reference

#Managing storage efficiently

#Best practices

#1. Regular cleanup

Monthly Tasks:

• Delete old test datasets
• Remove temporary files
• Archive completed projects
• Review USS directories

Cleanup Commands:

# Delete dataset
DELETE 'ZOSADMN.OLD.DATA'

# Delete USS files
rm /u/zosadmn/old_file.txt

# Remove empty directories
rmdir /u/zosadmn/empty_dir

#2. Efficient dataset allocation

Right-Size Datasets:

# Instead of over-allocating:
SPACE(100,50) TRACKS  (Bad)

# Allocate what you need:
SPACE(10,5) TRACKS    (Good)

Use Secondary Extents:

• Allow datasets to grow as needed
• Prevents wasted space
• Automatic expansion

#3. Compress data

For Sequential Datasets:

• Use compression utilities
• Archive old data
• Export to workstation if not needed

For USS Files:

# Compress files
gzip large_file.txt

# Create archives
tar -czf archive.tar.gz directory/

#4. Archive old data

Options for Archiving:

To the Workstation:

# Download via SFTP
sftp zosadmn@<zos-ip>
get /u/zosadmn/old_data.txt

To USS Archive:

# Create archive directory
mkdir /u/zosadmn/archive

# Move old files
mv old_project/* /u/zosadmn/archive/

Export Datasets:

# Use DFSMSdss to create portable copies
# See dataset-migrate.md for details

#Storage monitoring schedule

Weekly:

• Check for failed jobs due to space
• Review largest datasets
• Delete temporary test data

Monthly:

• Full storage audit
• Archive completed projects
• Plan for future needs

Quarterly:

• Review overall usage trends
• Optimize dataset allocations
• Consider storage request if needed

↑ Return to Quick reference

#Troubleshooting storage issues

#Issue: "Space Not Available" error

Symptoms:

IKJ56247I SPACE REQUESTED NOT AVAILABLE

Solutions:

1. Check Current Usage:

   ISPF → 3.4
   Review dataset list
   

2. Delete Unused Datasets:

   D next to dataset in 3.4
   

3. Request Additional Storage:

   • Via ZLPN portal
   • Follow request process above

#Issue: cannot create new datasets

Symptoms:

• Dataset allocation fails
• "Volume full" messages

Solutions:

1. Free Up Space:

   • Delete old datasets
   • Compress large files
   • Archive old data

2. Use Different Volume:

   • Try USMS01 if available
   • Contact support for options

3. Request More Storage:

   • Submit request via ZLPN

#Issue: USS file system full

Symptoms:

No space left on device

Solutions:

1. Find Large Files:

   du -sk /u/zosadmn/* | sort -n
   

2. Delete Unnecessary Files:

   rm large_file.txt
   

3. Compress Files:

   gzip *.log
   

4. Request Additional Storage

#Issue: Storage request not processed

If storage request is delayed:

1. Check Request Status:

   • Log in to ZLPN portal
   • View request history
   • Check for error messages

2. Verify Instance is Running:

   • Storage can only be added to running instances
   • Start instance if stopped
   • Mount any available storage

3. Contact Support:

   • Via ZLPN portal
   • Provide request ID
   • Describe the issue

↑ Return to Quick reference