IBM OS/390 Time Clock User Manual


 
13.2.4.2 RELPAG Macro
The MVS PGRLSE and PGSER RELEASE macros have functions similar to the
VSE RELPAG macro.
┌─────┬────────┬─────────────────────────────┐
│ VSE │ RELPAG │begin addr , end addr,777
│ (2-12) (2-12)
│lis─name
│ (1)
├─────┼────────┼─────────────────────────────┤
│ MVS │ PGRLSE │ LA=addrl ,HA=addr2
(2-12) (2-12)
(0) (1)
└─────┴────────┴─────────────────────────────┘
When you issue the PGRLSE macro, all complete pages of virtual storage
between the low and high addresses specified are released. You can help
reduce system overhead by releasing virtual storage when you no longer need
it.
Unlike VSE, you must issue a separate instruction for each area of storage you
want to release.
13.2.4.3 PFIX and PFREE Macros
The MVS PGFIX and PGFREE macros correspond to VSE PFIX and PFREE. Use of
the MVS instructions is restricted, however, to system functions and authorized
users (key-0 and supervisor state). Further information about PFIX and PFREE
appears in MVS SRL library publications.
13.2.4.4 SETPFA Macro
In MVS, only system functions and authorized users (key-0 and supervisor state)
are permitted to handle their own page faults.
13.2.4.5 PAGEIN Macro
The MVS PGLOAD macro is similar to PAGEIN, but its use is restricted to system
functions and authorized users (key-0 and supervisor state).
13.2.4.6 FCEPGOUT, RUNMODE, VIRTAD and REALAD Macros
These instructions have no equivalent in MVS.
13.2.5 VSAM Macros
Detailed information on the coding of MVS VSAM macros can be found in the
publication
DFSMS/MVS Macro Instructions For Data Sets
, SC26-4913.
13.2.5.1 ACB Macro
The ACB macro is source-compatible except for the parameter PARMS=
which was introduced by VSE VSAM Release 2 to support VSE VSAM Space
Managed files. MVS VSAM does not support this type of file. Programs using this
VSE feature should be converted to use MVS Sequential Access Method (SAM),
or VSAM ESDS files.
Additional MVS VSAM ACB Parameters
290 VSE to OS/390 Migration Workbook