Materialize Dump Space (MATDMPS)

Instruction Syntax

Op Code (Hex) Operand 1 Operand 2
04DA Receiver Dump space
Operand 1: Space pointer.

Operand 2: System pointer.

Bound Program Access 
Built-in number for MATDMPS is 83.
MATDMPS (
         receiver     : address
         dump_space   : address of system pointer
)

Description:

The current attributes of the dump space specified by operand 2 are materialized into the receiver specified by operand 1.

The template identified by operand 1 must be 16-byte aligned in the space. The format of the materialization is as follows:

Offset  
Dec Hex Field Name Data Type and Length
0 0 Materialization size specification Char(8)
0 0
  • Number of bytes provided for materialization
  • Bin(4)

4

4

  • Number of bytes available for materialization
    (always 128 for this instruction)

  • Bin(4)
8 8 Object identification Char(32)
8 8
  • Object type
  • Char(1)
9 9
  • Object subtype
  • Char(1)
10 A
  • Object name
  • Char(30)
40 28 Object creation options Char(4)

40

28

  • Existence attributes

    0 =
    Temporary
    1 =
    Permanent

  • Bit 0

40

28

  • Space attribute

    0 =
    Fixed length
    1 =
    Variable length

  • Bit 1

40

28

  • Context

    0 =
    Addressability not in context
    1 =
    Addressability in context

  • Bit 2
40 28
  • Reserved (binary 0)
  • Bits 3-12
40 28
  • Initialize space
  • Bit 13
40 28
  • Reserved (binary 0)
  • Bits 14-31
44 2C Recovery options Char(4)
48 30 Size of space Bin(4)
52 34 Initial value of space Char(1)
53 35 Performance class Char(4)
57 39 Reserved Char(7)
64 40 Context System pointer
80 50 Reserved Char(16)
96 60 Dump space size Char(4)
100 64 Dump data size Char(4)
104 68 Dump data size limit Char(4)
108 6C Reserved Char(20)

128

80

--- End ---

 

The first 4 bytes of the materialization identify the total number of bytes provided for use by the instruction. This value is supplied as input to the instruction and is not modified by the instruction. A value of less than eight causes the materialization length invalid (hex 3803) exception to be signaled.

The second 4 bytes of the materialization identify the total number of bytes available to be materialized. The instruction materializes as many bytes as can be contained in the area specified as the receiver. If the byte area identified by the receiver is greater than that required to contain the information requested, then the excess bytes are unchanged. No exceptions are signaled in the event that the receiver contains insufficient area for the materialization, other than the materialization length invalid (hex 3803) exception described previously.

The dump space size field is set with the current size value for the number of 512-byte blocks of space allocated for storage of dump data within the dump space.

The dump data size field is set with the current size value for the number of 512-byte blocks of dump data contained in the dump space. This value specifies the number of blocks from the start of the dump space through the block of dump data which has been placed into the dump space at the largest dump space offset value. A value of zero indicates that the dump space currently contains no dump data.

The dump data size limit field is set with the current size limit for the number of 512-byte blocks of dump data which may be stored in the dump space. A value of zero indicates that no explicit limitation is placed on the amount of dump data which may be stored in the dump space. The machine implicitly places a limit on the maximum size of a dump space. This value of this limitation is dependent upon the specific implementation of the machine.

Authorization Required

  • Operational
    • Operand 2
  • Execute
    • Contexts referenced for address resolution

Lock Enforcement

  • Materialize
    • Operand 2
    • Contexts referenced for address resolution

Exceptions

  • 06 Addressing
    • 0601 Space Addressing Violation
    • 0602 Boundary Alignment
    • 0603 Range
  • 08 Argument/Parameter
    • 0801 Parameter Reference Violation
  • 0A Authorization
    • 0A01 Unauthorized for Operation
  • 10 Damage Encountered
    • 1004 System Object Damage State
    • 1005 Authority Verification Terminated Due to Damaged Object
    • 1044 Partial System Object Damage
  • 1A Lock State
    • 1A01 Invalid Lock State
  • 1C Machine-Dependent
    • 1C03 Machine Storage Limit Exceeded
  • 20 Machine Support
    • 2002 Machine Check
    • 2003 Function Check
  • 22 Object Access
    • 2201 Object Not Found
    • 2202 Object Destroyed
    • 2203 Object Suspended
    • 2207 Authority Verification Terminated Due to Destroyed Object
    • 2208 Object Compressed
    • 220B Object Not Available
  • 24 Pointer Specification
    • 2401 Pointer Does Not Exist
    • 2402 Pointer Type Invalid
    • 2403 Pointer Addressing Invalid Object Type
  • 2E Resource Control Limit
    • 2E01 User Profile Storage Limit Exceeded
  • 32 Scalar Specification
    • 3201 Scalar Type Invalid
  • 36 Space Management
    • 3601 Space Extension/Truncation
  • 38 Template Specification
    • 3801 Template Value Invalid
    • 3803 Materialization Length Invalid
  • 44 Protection Violation
    • 4401 Object Domain or Hardware Storage Protection Violation
    • 4402 Literal Values Cannot Be Changed
Parent topic: Dump Space Management