Parameter Descriptions
- REQUEST=READ_STGSTATS
- Use this input parameter to specify that statistical information for the specified storage class (STGCLASS) be returned in the storage area specified by STGSTATS.
- ,ANSAREA=NO_ANSAREA
- ,ANSAREA=ansarea
- Use this output parameter to specify an answer area to contain information returned from the
request. The format of the answer area is described by the IXLYCAA mapping macro.
To Code: Specify the RS-type name or address (using a register from 2 to 12) of an area (with a length of ANSLEN) where the information returned by the request will be put.
- ,ANSLEN=anslen
- Use this inppaameter to specify the size of the storage area specified by ANSAREA. Use either CAALEVEL0LEN, CAALEVEL1LEN or CAALEVEL2LEN of the IXLYCAA mapping macro to determine the minimum size of the answer area. The answer area length must be at least large enough to accommodate the level of the IXLYCAA mapping appropriate to the requested function.
- When the connection specified ASYNCXI=1 on the IXLCONN invocation and AXIOVERRIDE=0 was specified or defaulted to for the IXLCACHE request, the answer area length is a required parameter and must be a minimum value of CAALEVEL2LEN to contain a returned asynchronous cross-invalidation sequence number (CAAASYNCXISEQNUM).
- When the value of PLISTVER is 4 or above, the minimum answer area length is CAALEVEL1LEN.
- When the value of PLISTVER is 0 - 3, the minimum answer area length is CAALEVEL0LEN.
To Code: Specify the RS-type name or address (by using a register 2 - 12 2 to ) of a 2-byte field that contains the length of the answer area (ANSAREA).
- ,CONTO=conken
- Use this input parameter to specify the connect token that was returned by the IXLCONN service
in the IXLCONN answer area, which is mapped which is by IXLYCONA. The connect token uniquely
identifies your connection to the cache structure, and must be specified on each IXLCACHE
invocation.
To Code: Specify the RS-type name or address (by using a register from 2 to 12) of a 16-byte field that contains the connect token.
- ,MF=S
- ,MF=(L,mfctrl)
- ,MF=(L,mfctrl,mfattr)
- ,MF=(L,mfctrl,0D)
- ,MF=(M,mfctrl)
- ,MF=(M,mfctrl,COMPLETE)
- ,MF=(M,mfctrl,NOCHECK)
- ,MF=(E,mfctrl)
- ,MF=(E,mfctrl,COMPLETE)
- ,MF=(E,mfctrl,NOCHECK)
- Use MF=S to specify the standard form of the macro, which builds an inline parameter list and
generates the macro invocation to transfer control to the service.
Use MF=L to specify the list form of the macro. Use the list form together with the execute form of the macro for applications that require reentrant code. The list form defines an area of storage that the execute form uses to store the parameters. Only the PLISTVER parameter can be coded with the list form of the macro.
Use MF=M to specify the modify form of the macro. Use the modify form to generate code to put the parameters into the parameter list.
Use MF=E to specify the execute form of the macro. Use the execute form together with the list form of the macro for applications that require reentrant code. The execute form stores the parameters into the storage area defined by the list form, and generates the macro invocation to transfer control to the service.- ,mfctrl
- Use this output parameter to specify a storage area to contain the parameters.
To Code: Specify the RS-type name or address (by using a register 2 - 12) of the parameter list.
- ,mfattr
- Use this input parameter to specify the name of a 1- to 60-character string that can contain any value that is valid on an assembly language Data Studio pseudo-op. You can use this parameter to force boundary alignment of the parameter list. If you do not code mfattr, the system provides a value of 0D, which forces the parameter list to a doubleword boundary.
- ,COMPLETE
- ,NOCHECK
- Use this input parameter to specify the degree of macro parameter syntax checking the system is
to do.
- COMPLETE
- Use this input parameter to require that the system check for required parameters and supply
defaults for omitted optional parameters. Note: In the macro expansion you might see some defaults for optional parameters that are not documented here. The ones that are not documented do not have any effect on the macro. For example, if SMILE=var were an optional parameter and the default is SMILE=NO_SMILE then it would not be documented. However, if the default was SMILE=:-), then it would be documented because a value would be the default.
- NOCHECK
- Use this parameter to specify that the system is not to check for required parameters nor to supply defaults for omitted optional parameters.
- ,MODE=SYNCSUSPEND
- ,MODE=SYNCECB
- ,MODE=SYNCEXIT
- ,MODE=SYNCTOKEN
- ,MODE=ASYNCECB
- ,MODE=ASYNCEXIT
- ,MODE=ASYNCTOKEN
- Use this input parameter to specify:
- Whether the request is to be performed synchronously or asynchronously
- How you want to be notified of request completion if the request is processed asynchronously.
- SYNCSUSPEND
- The request processes synchronously. If necessary, the request is suspended until it can complete synchronously. To use this option, your program must be enabled for I/O and external interrupts.
- SYNCECB
- The request processes synchronously if possible. If the request processes asynchronously, the ECB specified by REQECB is posted when the request completes.
- SYNCEXIT
- The request processes synchronously if possible. If the request processes asynchronously, your complete exit is given control when the request completes.
- SYNCTOKEN
- The request processes synchronously if possible. If the request processes asynchronously, an
asynchronous request token is returned to the area specified by REQTOKEN. Use the returned request
token on the IXLFCOMP macro to determine whether your request has completed. Note: ANSAREA is a required parameter when MODE=SYNCTOKEN is specified.
- ASYNCECB
- The request processes asynchronously. The ECB specified by REQECB is posted when the request completes.
- ASYNCEXIT
- The request processes asynchronously. Your complete exit is given control when the request completes.
- ASYNCTOKEN
- The request processes asynchronously. An asynchronous request token is returned to the area
specified by REQTOKEN. Use the returned request token on the IXLFCOMP macro to determine whether
your request has completed. Note: ANSAREA is a required parameter when MODE=ASYNCTOKEN is specified.
- ,PLISTVER=IMPLIED_VERSION
- ,PLISTVER=MAX
- ,PLISTVER=plistver
- Use this input parameter to specify the version of the macro. See Understanding IXLCACHE Version Support for a description of the options available with PLISTVER.
- ,REQDATA=NO_REQDATA
- ,REQDATA=reqdata
- Use this input parameter with MODE=SYNCEXIT or MODE=ASYNCEXIT to pass any data you choose to the
complete exit. The exit will get control only if the request is processed asynchronously.
To Code: Specify the RS-type name or address (by using a register from 2 to 12) of an 8-byte field that contains the data to be passed to the complete exit.
- ,REQECB=reqecb
- Use this output parameter with either MODE=SYNCECB or MODE=ASYNCECB to specify the address of an
ECB, which is to be posted when the request completes if the request was processed asynchronously.
Before coding REQECB, you must ensure that:
- You initialize the ECB before you issue the request.
- The ECB resides in either common storage or the home address space where IXLCONN was issued.
- Any tasks that wait for the ECB to be posted reside in the home address space where IXLCONN was issued.
To Code: Specify the RS-type name or address (by using a register from 2 to 12) of a 4-byte field that contains the address of the ECB to be posted when the request completes. The ECB must be aligned on a fullword boundary.
- ,REQID=NO_REQID
- ,REQID=reqid
- Use this input parameter to specify a user-defined request identifier to be associated with the
request. You can specify this request identifier on the IXLPURGE macro to cancel a request that has
not yet been processed.
To Code: Specify the RS-type name or address (by using a register from 2 to 12) of an 8-byte field that contains the user-defined request identifier.
- ,REQTOKEN=reqtoken
- Use this output parameter with either MODE=SYNCTOKEN or MODE=ASYNCTOKEN to specify the address
of a storage area to receive the request token that is returned when the request will be processed
asynchronously. This token, which uniquely identifies the request, must be used as input to the
IXLFCOMP macro, which you use to determine if the request has completed.
To Code: Specify the RS-type name or address (by using a register from 2 to 12) of a 16-byte field where the system will put the request token.
- ,RETCODE=retcode
- Use this output parameter to specify a field to contain the return code. (The return code is
also returned in register 15.)
To Code: Specify the RS-type name or address (by using a register from 2 to 12) of a 4-byte field that will contain the return code when the request has completed.
- ,RSNCODE=rsncode
- Use this output parameter to specify a field to contain the reason code returned, if applicable.
(The reason code is also returned in register 0.)
To Code: Specify the RS-type name or address (by using a register from 2 to 12) of a 4-byte field that will contain the reason code (if any) when the request has completed.
- ,STGCLASS=stgclass
- Use this input parameter to specify the storage class for which statistical information will be
returned.
To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 1-byte field that contains the storage class.
- ,STGSTATS=stgstats
- Use this output parameter to specify a storage area to contain the storage class statistics
returned from the request. The format of the STGSTATS area is described by mapping macro IXLYCSCS.
For more information about the data returned by this request, see z/OS MVS Programming: Sysplex Services Guide.
To Code: Specify the RS-type name or address (using a register from 2 to 12) of a 256-byte area where the storage statistics information will be placed.