Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
UNACCESS—Ending the OSREQ interface z/OS DFSMS OAM Application Programmer's Reference SC23-6865-00 |
|
The UNACCESS function ends the connection between the application program and OAM. When the calling program no longer requires OSREQ services, it must issue OSREQ UNACCESS. When invoking UNACCESS, the caller supplies an eight-byte token that has been set by a successful issuance of OSREQ ACCESS. UNACCESS should not be requested unless the corresponding ACCESS was successful. An initialized token is required by all OSREQ calls, except ACCESS. The syntax diagram for the OSREQ UNACCESS function follows. Syntax for OSREQ UNACCESS >>-OSREQ UNACCESS--MF=-+-L---------------------------------+----> +-(M,parameter_list-+-----------+-)-+ | '-,COMPLETE-' | '-(E,parameter_list-+-----------+-)-' '-,COMPLETE-' >--+-------------------------------------+----------------------> | (1) | '-TOKEN----=-+-token_area-----------+-' '-(token_area_pointer)-' >--+-------------------------------------+----------------------> '-MSGAREA=-+-message_area-----------+-' '-(message_area_pointer)-' >--+------------------------------------+-----------------------> '-RETCODE=-+-return_code-----------+-' '-(return_code_pointer)-' >--+------------------------------------+-----------------------> '-REACODE=-+-reason_code-----------+-' '-(reason_code_pointer)-' >--+--------------------------------------+-------------------->< '-TTOKEN=-+-tracking_token-----------+-' '-(tracking_token_pointer)-' Notes:
OSREQ UNACCESS does not attempt to end any active requests that are using the same token, but returns control to the UNACCESS caller with a warning return code and reason code. When each of the outstanding requests completes, any further OSREQ requests using that token receive return and reason codes indicating that the token is no longer valid. |
Copyright IBM Corporation 1990, 2014
|