Allocation functions and zFS
MainView SRM Allocation generally supports the IBM zSeries File System (zFS).
However, the product's behavior varies slightly when processing zFS allocations instead of non-zFS data sets. The following table lists Allocation functions that are affected by processing zFS allocation.
Allocation functions affected by processing zFS allocation
Function | Description |
|---|---|
SPACSECA 1 | Add a secondary allocation quantity |
SPACSECB 1 | Reduce the secondary allocation to the best fit |
SPACSECR 1 | Reduce the secondary allocation to the largest extent |
SPACSWIR 1 | Reduce the initial allocation on a volume addition |
SPACVOLA 1 | Add a volume during allocation |
VSAMCNTL 2 | Enforce VSAM allocation standards |
- Space extension takes place in zFS address space (called by the IBM colony).
- Specifying a CISIZE other than 4096 causes zFS formatting to fail.
With the exception of the VSAMCNTL function, the previous table shows that the functions that are affected by zFS allocation are those that apply to the data set extensions. All zFS allocation and I/O activity is performed within the zFS-dedicated address space (colony). This address space affects the Allocation product in the following ways:
- Instead of appearing in the user address space, Allocation messages appear in the zFS address space and in the operator log.
The following table lists the filtering FLST/RLST parameters that reflect the zFS Started Task, not the user's job.
FLST/RLST parameters in the zFS Started Task
FLST/RLST parameter
Description
JOB
Job, TSO, or STC name
JOBACCTn
Job account field, where n is 1, 2, or 3
JOBCLASS
Job class
JOBSDAY
Job start day
JOBSTIME
Job start time
JOBTYPE
Type of job STC|TSO|JOB
PGM
Program name
PGMRNAME
Programmer name job card field
PROCSTEP
Procedure step name
RACF
RACFGRP
IBM RACF group
RACFUID
Value of the RACF user ID on a JOB card
STEP
Job step name
STEPACCTn
Step account field, where n is 1, 2, or 3