Define PFA cache area for pubset
Component: | BS2000 |
Functional area: | Caching media control |
Domain: | MULTI-CATALOG-AND-PUBSET-MGMT |
Privileges: | TSOS |
Function
Systems support staff can use this command during a session to set up a cache area for high-speed temporary storage of data in a cache medium (main memory or global storage) for an imported SF pubset or for a volume set in an imported SM pubset. This activates PFA caching for the pubset/volume set.
The preconditions for setting up the cache area are that:
no cache has yet been activated
a cache configuration has previously been defined in the MRSCAT entry for the pubset or volume set concerned, using the MODIFY-PUBSET-CACHE-ATTRIBUTES command.
The START-PUBSET-CACHING command makes caching available to all hiperfiles in the pubset/volume set (files with the performance attribute HIGH or VERY-HIGH) which are opened from then on. Files which are already open cannot take advantage of caching until a START-FILE-CACHING command has been issued or until they are closed and reopened.
After a cache area has been removed using the STOP-PUBSET-CACHING command, the same cache medium must be used when it is set up again. The same applies to the VOLATILITY parameter specified in the MODIFY-PUBSET-CACHE-ATTRIBUTES command for the global storage (GS) cache medium. Changes are accepted only after the pubset has been re-imported.
The SHOW-PUBSET-CACHE-ATTRIBUTES (and also SHOW-PUBSET-PARAMETERS) command provides details of the cache configuration which is currently valid.
The command is not supported for the home pubset.
The command is also supported for shared pubset networks.
In a shared pubset network, the command can be issued on the master system or on a slave. A system message refers to the system which is issuing the command, unless it is preceded by message DMS136D, which then includes the name of the system (master or slave) on which the error has occurred. If the command is issued on a slave system, the system name may also be the local host name.
Format
START-PUBSET-CACHING | ||||||||||||||||
| ||||||||||||||||
Operands
PUBSET = <cat-id 1..4>
ID of the pubset for which the cache area is to be activated.
PUBSET-TYPE = *SINGLE-FEATURE / *SYSTEM-MANAGED(...)
Indicates whether the pubset is an SF pubset (cache directly assigned to the pubset) or an SM pubset (cache assigned to one of the volume sets of the pubset).
PUBSET-TYPE = *SINGLE-FEATURE
Default. The pubset is an SF pubset. The cache is directly assigned to the SF pubset.
PUBSET-TYPE = *SYSTEM-MANAGED(...)
The pubset is an SM pubset. The cache is assigned to a single volume set.
VOLUME-SET = <cat-id 1..4>
Identifies the volume set to which the cache is assigned.
Return codes
(SC2) | SC1 | Maincode | Meaning |
|---|---|---|---|
0 | CMD0001 | No errors | |
1 | 0 | DMS1356 | Cache area already active |
32 | DMS1351 | Pubset management parameter error | |
32 | DMS135F | Internal system error | |
32 | DMS1398 | Reconfiguration no longer possible | |
64 | DMS1352 | Not authorized to use command | |
64 | DMS1353 | MRSCAT entry not found | |
64 | DMS1354 | Pubset not locally imported | |
64 | DMS1355 | Invalid cache configuration | |
64 | DMS1358 | Function is not supported | |
64 | DMS135A | No cache for shared pubsets | |
64 | DMS135B | Cache memory allocation full | |
64 | DMS135D | Cache cannot be connected | |
64 | DMS135E | Cache handler not available | |
64 | DMS1362 | No cache for home pubset | |
64 | DMS1381 | Volume set conflict | |
64 | DMS138D | Pubset type conflict | |
64 | DMS1390 | Earlier reconfiguration job not yet completed | |
64 | DMS1397 | Reconfiguration by partner system not supported | |
64 | DMS139D | Volume not accessible | |
128 | DMS1363 | Class 4/5 memory shortage | |
128 | DMS1389 | Error in transmission to partner system | |
128 | DMS139A | Other pubset reconfiguration job still active | |
128 | DMS139B | Volume or volume set is reserved | |
128 | DMS139C | Pubset configuration file still locked |