z/OS MVS System Codes
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


18A

z/OS MVS System Codes
SA38-0665-00

18A

Explanation

A PGSER macro requested a paging service (FIX, FREE, LOAD, RELEASE, ANYWHER, PROTECT, or UNPROTECT). The request was not valid. The caller used 31-bit addressing.

The registers contain the following:
  • Register 0: A hexadecimal reason code, which is one of the following:
    Code
    Explanation
    08000101
    On a branch request, the start address is greater than the end address. The request was a register-format input.
    0B000101
    On an SVC request, the start address is greater than the end address. The request was a register-format input.
    2A000301
    Partial megabyte pagefree is prohibited against an already page fixed large page segment.
    35000201
    The page is part of a virtual I/O (VIO) window.
    35000301
    The page had not been obtained by a GETMAIN macro.
    35000B01
    Partial megabyte pagefix is prohibited against an already page fixed large page segment.
    36000101
    The page had not been obtained by a GETMAIN macro.
    36000201
    Permanent error.
    3AF20101
    A program check occurred when the paging services was accessing the caller's service list (SL) entry. The entry point whose ID is equal to the second byte of the reason code issued the reason code.
    3B000401
    The starting address in a virtual subarea list (VSL)/page service list (PSL) entry is greater than the ending address.
    3B000501
    The caller's page service list (PSL) entry contains the reserved flag.
    3B000601
    The starting address in a VSL/PSL entry is greater than the ending address.
    3BF20101
    A program check occurred when the paging services was accessing the caller's service list (SL) entry.
    55000101
    The caller is not in key 0. The key for the page did not match the caller's.
    55000201
    The caller requested that a permanently resident page be released.
    6A000101
    The caller specified a nonzero event control block (ECB) address with a cross memory page services request.
    6A000201
    The caller specified a nonzero ECB address with a PGOUT, PGRLSE or PGANY request.
    6A000301
    An ECB address contained a negative number. The request was a PGFIX, PGFREE or PGLOAD.
    6A000401
    An ECB was not on a word boundary. The request was a PGFIX, PGFREE or PGLOAD.
    6A000601
    The caller is not authorized to perform the page service function requested. The request was a PGFIX or PGFREE.
    6A000701
    The caller specified a cross memory mode request and a nonzero task control block (TCB) address with a page service function to which the TCB address was applicable.
    6A000801
    The caller specified an incorrect TCB. The request was a PGFIX, PGFREE, PGLOAD or PGOUT.
    6A000901 through 6A000906
    The caller specified incorrect options with the page services request.
    6A000A01
    The caller did not specify a valid function in the VSL/PSL entry.
    6A000B01
    The caller specified an ECB address, and the page containing it had not been obtained by a GETMAIN macro.
    6A000B02
    The caller specified an ECB address, and the page containing it had not been obtained by a GETMAIN macro.
    6A000C01
    A caller that is not in key 0 specified an ECB address. The key of the page containing it did not match the caller's key.
    6FF20101
    A program check occurred when the paging services was accessing the caller's service list (SL) entry.
    xx0008xx
    The caller tried to release a page of protected storage.
    xx000907
    The caller issued a PGSER macro with the PROTECT parameter, but one of the other parameters specified was either incorrect or incompatible.
    xx000908
    The caller issued a PGSER macro with the UNPROTECT parameter, but one of the other parameters specified was either incorrect or incompatible.
    xx0701xx
    The caller issued a PGSER macro with the PROTECT parameter for storage with a key that does not match the PSW key under which the program runs. The program issuing the PGSER macro with the PROTECT parameter must be either key zero or else run under a PSW key that matches the key of the storage being protected.
    xx0702xx
    The caller tried to issue the PGSER macro with the PROTECT parameter for virtual storage in either the PSA or any VIO window. Neither storage area can be specified with the PROTECT keyword.
    xx0704xx
    The caller issued a PGSER macro with the PROTECT parameter for virtual storage in the read/only nucleus that is backed by 1 megabyte pages. This storage area cannot be specified with the PROTECT keyword.
    xx0801xx
    The caller issued a PGSER macro with the UNPROTECT parameter with a key that does not match the PSW key under which the program runs. The program issuing the PGSER UNPROTECT macro must be either key zero or else run under a PSW key that matches the key of the storage being unprotected.
    xx0802xx
    The caller tried to issue the PGSER macro with the UNPROTECT parameter for virtual storage in either the PSA or any VIO window. Neither storage area can be specified with the UNPROTECT keyword.
    xx0804xx
    The caller issued a PGSER macro with the UNPROTECT parameter for virtual storage in the read/only nucleus that is backed by 1 megabyte pages. This storage area cannot be specified with the UNPROTECT keyword.
  • Register 3: If branch entry, caller's return address.
  • Register 4: If LIST-FORMAT entry, address of the caller's erroneous page service list entry (PSL)/short page service list (SSL). If REGISTER-FORMAT entry, register 4 contains zero.
  • Registers 5-7: If SSL format entry, registers 5-7 contain the caller's input registers.

    If PSL format SVC entry, registers 5-7 contain zero.

    If PSL format branch entry, registers 5-7 are irrelevant.

  • Register 8: If SSL format entry, register 8 is the same as the caller's input register.

    If PSL format SVC entry, register 8 contains zero.

    If PSL format branch entry, register 8 contains the caller's input TCB address, or, if no TCB address was supplied, register 8 contains zero.

  • Register 9: If PSL format entry, address of the input ECB. If no ECB address was supplied, register 9 contains zero.

    If SSL format entry, register 9 is the same as the caller's input register.

  • Register 10: If the error is related to paging, the address of the page in error. If the error is not related to paging, register 10 contains zero.
  • Register 11: If LIST-FORMAT entry, address of the caller's first PSL/SSL entry. If REGISTER-FORMAT entry, register 11 contains 0.
  • Registers 12-14: If PSL format entry, the PSL entry in error. If the PSL was in pageable storage or if the PSL storage key did not match a nonzero caller's storage key, registers 12-14 contain zero.

    If SSL format entry, register 12 contains zero. Registers 13-14 contain the SSL entry in error, or, if the SSL was in pageable storage, registers 13-14 contain zero.

  • Register 15: Hexadecimal reason code, as follows:
    Code
    Explanation
    04
    A caller issued a PGFIX request but did not obtain the PSL storage using a GETMAIN macro, or a page release operation failed because either the caller attempted to release permanently backed storage or a non-system key caller attempted to release storage in a different key.
    10
    The input ECB, TCB, or PSL/SSL failed validity checks.

System action

The system issues an abend to the current task.

System programmer response

Correct the problem in the request and run the job again. If PGFIX or PGFREE was requested and the caller was not authorized, obtain proper authorization and run the job again.

Source

Real storage manager (RSM)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014