08B

Explanation
An error occurred while the system processed a
data-in-virtual service request. Either a parameter on the DIV macro
or another condition that existed when the DIV macro was issued caused
the error.  The 2 low-order bytes in register 15 contain a hexadecimal
reason code that explains the error: Code
Explanation
0001
The caller requested an unknown service.
0002
Data-in-virtual does not recognize the parameter list format.
0003
The input parameter list cannot be addressed.
0004
The parameter list specifies storage that data-in-virtual cannot
address.
0005
The parameter list contains a reserved field that does not contain
binary zeroes.
0006
The caller is not running in task mode.
0007
The primary and home address spaces are not equal.
0008
The macro specified an incorrect TYPE parameter.
0009
The ID parameter is either incorrect or an ID that the caller
cannot use.
000A
Data-in-virtual is processing another data-in-virtual request
with the specified ID.
000B
The system already accessed an object with the specified ID.
000C
The caller does not have the proper resource access control facility
(RACF®) authorization to the
requested object. (Or, the caller is attempting to use a password-protected
data set for an object. Data-in-virtual does not support passwords.)
000D
The specified range exceeds the maximum allowable size for the
object.
000E
The system does not have access to an object for the specified
ID.
000F
The specified range overlaps with a range already mapped for the
ID.
0010
The specified virtual range overlaps with an already mapped virtual
range in the current address space or the specified data space.
0011
An undetermined system or caller error occurred while data-in-virtual
was attempting to access data from the object; all data was not retained.
0012
The virtual storage specified does not begin on a 4-kilobyte boundary.
0013
The virtual storage specified is not in a pageable private area
subpool.
0014
The system cannot use the virtual storage specified to map an
object. For example, the virtual storage may contain storage assigned
to virtual input output (VIO).
0015
The specified range of virtual storage contains at least one page
that was not in a virtual range obtained by a GETMAIN macro.
0016
The specified virtual storage contains at least one page in a
range that is specified on a current PAGE FIX request; however, RETAIN=YES
was not specified.
0017
Portions of virtual storage that mapped the object were not addressable,
and could not be saved.  Either a paging error occurred or data occupied
a bad central storage frame.
0018
The caller does not have UPDATE ACCESS to the object.
0019
Data-in-virtual marked as non-pageable a page in a range to be
saved or reset. That is, a PAGE FIX was outstanding against the page.
001A
The specified range is not in any mapped area of the object.
001B
The virtual storage area specified to be unmapped is not currently
mapped.
001C
Data-in-virtual cannot access the object at the current time;
the object data set is in use.
001D
The accessed object is not a virtual storage access method (VSAM)
linear data set, and thus does not have the correct control interval
size that is implicit for a VSAM linear data set.
001E
The length of the DDNAME parameter value exceeds the maximum size
allowed.
001F
The caller's storage key is not the same as when data-in-virtual
issued the IDENTIFY.
0020
A task that does not own the specified ID issued a DIV macro with
an ACCESS parameter.
0021
Data-in-virtual could not access portions of the object on permanent
storage; therefore, all data was not retained.
0022
A task issued a DIV macro with an IDENTIFY parameter for an object.
The task does not own the virtual storage specified to be mapped.
For authorized programs, that task or one of its subtasks does not
own the storage.
0023
The caller's storage key does not permit access to part or all
of the specified storage to be mapped.
0024
The caller issued a DIV macro while holding the local lock.
0025
The caller issued a DIV macro while in an environment that precludes
the use of Supervisor Call (SVC) instructions.
0026
The caller issued a DIV macro, but was not in 31-bit addressing
mode.
0027
The specified OFFSET and SPAN parameters describe a range that
exceeds the maximum supported object size.
0028
Data-in-virtual attempted to access an empty data set for a DIV
macro with MODE=READ.
0029
Data-in-virtual attempted to map into a disabled reference (DREF)
data space.
002A
Data-in-virtual attempted to establish a mapped local view into
a data space.  LOCVIEW=MAP was specified on a previous DIV macro with
an ACCESS parameter.
002B
The specified virtual range exceeds the bounds of the specified
data space.
002C
The caller requested either: A data space map while one or more address space maps were still
active under a given ID
An address space map while one or more data space maps were still
active under a given ID

002D
Data-in-virtual deleted the data space. However, the requested
operation completed successfully.
002E
Data-in-virtual deleted the data space. The requested operation
cannot be performed.
002F
A page to be saved was in the define I/O on (IOON) state.
0030
The virtual range specified contained at least one define I/O
on (IOON) page and RETAIN=YES was not specified.
0031
The caller specified an incorrect TTOKEN.
0032
The caller is not authorized.
0036
The DIV macro supplied an STOKEN value that does not represent
a valid data space that the requester can use.
0037
The caller accessed an object that was defined with SHAREOPTIONS
other than (1,3), and LOCVIEW=YES was not specified.
0038
The caller attempted to access a non-linear data set.
0039
The DIV macro requested a SAVE or RESET on a data space range
with DREF pages.
003A
Data-in-virtual attempted to MAP the virtual storage of a ESO
type Hiperspace™.
003B
Data-in-virtual attempted to UNMAP Hiperspace storage, but RETAIN=YES was
not specified.
003C
Data-in-virtual attempted to UNMAP virtual storage that maps a Hiperspace data object, but
RETAIN=YES was specified.
003D
The STOKEN for the object associated with the specified ID does
not represent a valid Hiperspace that
may be used with this request.
003E
The Hiperspace object
may not be accessed at this time.  Either the maximum for READs has
been reached, or there is a violation of SHARE options.
003F
The DIV macro specified LOCVIEW=MAP for an ID associated with
a Hiperspace object.
0040
The specified MAP range would cause the Hiperspace object to be extended such
that the installation data space limits for the address space would
be exceeded.
0041
The DIV macro specified an STOKEN with an ID that represents a Hiperspace data-in-virtual
object.  Data space virtual storage cannot be mapped into a Hiperspace.
0042
The DIV macro tried to access a Hiperspace, but the ALESERV ADD command
already had been entered for this Hiperspace.
0046
The caller issued the DIV macro with the SAVE or the SAVELIST
parameter and specified an incorrect LISTSIZE value.
0047
The caller issued a DIV macro with the SAVE parameter with one
of the required keywords missing. The missing keyword is either LISTADDR
or LISTSIZE.
0048
The caller issued a DIV macro with the SAVE parameter and LISTADDR
and LISTSIZE keywords to specify a user list. One of the following
problems occurred: The ranges specified for the user list do not intersect with a
mapped range.
The user list contains incorrect data.

0049
The caller issued a DIV macro with the SAVE parameter using incorrect
keywords. One of the following is true: The caller used keyword LISTADDR and LISTSIZE to specify a user
list, but also used one or both of the OFFSET or SPAN keywords. The
LISTSIZE and LISTADDR keywords are not compatible with the OFFSET
and SPAN keywords.
The caller specified the STOKEN keyword with either the OFFSET
or SPAN keywords. The STOKEN keyword is incompatible with the OFFSET
and SPAN keywords.

004A
The caller issued a DIV macro with the SAVE parameter but specified
incorrect addresses in the user list. Either an address was not on
a page boundary or the start address was higher than the end address.
004B
The caller issued the DIV macro with SAVE parameter but specified
a range in the user list that spans multiple data spaces or Hiperspaces.
004C
The caller issued the DIV macro with the SAVE parameter for a
data space or Hiperspace but
did not specify the STOKEN keyword.
004D
The user is not authorized to ACCESS the requested data.
004E
The caller issued the DIV macro with the MAP parameter for a shared
data page that does not meet the requirement that it reside in non-swappable
storage and have a SHAREDWRITE view mode.
004F
The caller issued the DIV macro with the MAP parameter for another
member of the same sharing group.
0050
The caller issued the DIV macro with the MAP parameter for a Hiperspace object into shared
storage.
0051
The caller issued the DIV macro with the MAP parameter for one
member of a sharing group, but this sharing group contains a member
that is currently fixed.
0052
The virtual storage specified contains at least one protected
page and RETAIN=YES was not specified.
0053
The caller attempted to DIV MAP a page that is part of an address
space view of a shared segment.
0054
The caller attempted to DIV ACCESS an object that is an extended
format linear dataset for which the size is greater than 4GB.
0801
The storage available was insufficient for building the necessary
data-in-virtual control block structure.
0802
An I/O driver failure occurred.
0803
The system could not read a required page table into central storage.
0804
The catalog update failed.
0805
An undetermined system error occurred.
0806
An I/O error occurred.
0807
Data may be damaged in the allocated space on a direct access
storage device (DASD). The space is currently beyond the saved portion
of the object.
0808
The system has not completed I/O from a previous request.

System action
The system abends the program that issued the
DIV macro. The system writes a logrec data set error record, and it
may write a dump.  If the reason code is X'0805', data-in-virtual
requested an SVC dump with the title COMPON=DATA-IN-VIRTUAL.

System programmer response
For reason code 0052, remove the protection
status from the protected pages in the specified virtual range.  Then
issue the DIV macro again. If you want to invoke MAP or UNMAP and
want to preserve the protection status, specify RETAIN=YES when you
issue the macro.
For reason code 0054, change the DDNAME to
point to a different dataset, because the current DDNAME points to
an extended format linear dataset with a size that is greater than
4GB, which is not support.
For other reason codes, look in the
system trace for the first PC entry with 00307 in the UNIQUE-1
column above the SVC 0D entry for the X'08B' abend.  The
address column contains the address of the program that issued the
DIV macro. Identify this program.
If the program is installation-provided,
continue diagnosis with the program.  If it is IBM-provided, search
the problem reporting data bases for a fix for the problem.  If no
fix exists, contact the data-in-virtual component at the IBM® support center.

Source
Data-in-virtual