z/OS MVS Programming: Callable Services for High-Level Languages
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


FPZ4RZV — Rendezvous compression service

z/OS MVS Programming: Callable Services for High-Level Languages
SA23-1377-02

Parent topic: System z authorized compression services

Description

The FPZ4RZV service performs the required setup and initialization of the compression services for an exploiter. The scope is the address space of the application and it is valid for the life of the Cross Memory Resource Owner Task (CMRO).

Notes:
  1. A maximum of 32 rendezvous tokens are supported per each address space. This allows multiple applications to exploit the compression driver so each can maintain their own rendezvous scope.
  2. All 64-bit storage is obtained with the MEMLIMIT=NO option.
Table 1. Environment for the FPZ4RZV service
Environmental factor Requirement
Minimum authorization: Supervisor State with Key 0
Dispatchable unit mode: Task
Cross memory mode: PASN=HASN=SASN
AMODE: 64-bit
Interrupt status: Enabled for I/O and external interrupts
Locks: No locks held
Table 2. Parameters for the FPZ4RZV service
Name Type Input/Output Description
ApplicationId Fixed(32) Input The application type to use. 0x01 is the application type for zEDC.
FPZ4RZV_options Bit(64) Input Options for the FPZ4RZV service:
SoftwareInflate (X'80000000 00000000')
Allows compression requests to fall back to software inflation when no compression devices are available.
EnableABCScatter (X'40000000 00000000')
Allows compression requests to use the FPZ4ABC compression service to submit work with scatter/gather lists.
FailOnNoDevices (X'20000000 00000000')
If specified, compression requests fail when no compression devices are available. If FailOnNoDevices is not specified, a valid rendezvous token is returned even if no compression devices are currently available. This returned rendezvous token is used for all other services.
Start of changeStart of changePlusOne (X'08000000 00000000')End of changeEnd of change
Start of changeIf specified, compression requests will only use zEDC Express Adapters with the March 31, 2014 Firmware MCL release, or later.End of change
userid Char(8) Input An eight character EBCDIC string identifying the user.
rmr_entries Fixed(32) Input The estimated number of FPZ4RMR compression service calls to be performed that helps to size the tables used until the maximum number of registrations is reached. This is an optional parameter. rmr_entries can be anywhere between 1 and 64K. The default is 128.

Define rmr_entries as integer data of length 32.
Rendezvous token Char(16) Output This is the token that must be passed to all FPZ services.
Return code Fixed(31) Output The return code for the service.
Reason code Fixed(32) Output The reason code for the service.
Table 3. Return and Reason Codes for the FPZ4RZV service
Hexadecimal Return Code Reason Code Meaning and Action
00 0000 Meaning: The call completed successfully.

Action: None.
04 0000 Meaning: No zEDC devices are available. zEDC support is active so it is possible that zEDC devices might become available in the future.

Action: If zEDC devices are available to this system, perform diagnostics to determine the reason for the failure.
04 0102 Meaning: No zEDC devices are available because the system requirements for zEDC were not met. See Requirements for zEnterprise Data Compression for the details. A 'thin' rendezvous was created.

Action: None.
08 0000 Meaning: No zEDC devices are available because the system requirements for zEDC were not met. This is the result of RvzFailOnNoDev being ON or SoftwareInflate being OFF when on downlevel hardware or software. See Requirements for zEnterprise Data Compression for the details. No rendezvous token is returned.

Action: None.
0C 0201 Meaning: Invalid parameter combination.

Action: Check the calling program for a probable coding error. Correct the program and rerun it.
0C 0207 Meaning: The calling environment is invalid.

Action: Check the calling program for a probable coding error. Correct the program and rerun it.
0C 0210 Meaning: rmr_entries specified an invalid value.

Action: Check the calling program for a probable coding error. Correct the program and rerun it.
0C 0226 Meaning: Invalid application specified.

Action: Check the calling program for a probable coding error. Correct the program and rerun it.
10 0301 Meaning: An internal error caused recovery to be entered.

Action: Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.
10 0303 Meaning: The maximum number of rendezvous tokens have been reached for the address space.

Action: Determine if the calling program is at fault because of a coding error. If there is no coding error, another program might be consuming all the rendezvous tokens for the address space. Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center.

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014