StopX37/II functions and zFS
MainView SRM StopX37/II 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 StopX37/II functions affected by processing zFS allocation table lists StopX37/II functions that are affected by processing zFS allocation.
StopX37/II functions affected by processing zFS allocation
Function | Description |
|---|---|
SPACSECA | Add a secondary allocation quantity |
SPACSECB | Reduce the secondary allocation to the best fit |
SPACSECR | Reduce the secondary allocation to the largest extent |
SPACSWIR | Reduce the initial allocation on a volume addition |
SPACVOLA | Add a volume during allocation |
The StopX37/II functions affected by processing zFS allocation 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 StopX37/II product in the following ways:
- Instead of appearing in the user address space, StopX37/II messages appear in the zFS address space and in the operator log.
- The FLST/RLST parameters in the zFS Started Task 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 |
RACFRACFGRP | 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 |