z/OS Using REXX and z/OS UNIX System Services
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


v_write

z/OS Using REXX and z/OS UNIX System Services
SA23-2283-00

Read syntax diagramSkip visual syntax diagram
>>-v_write--vntoken--variable--length--position--stem----------->

>--+--------------+--+-----------+-----------------------------><
   '-access_check-'  '-opentoken-'   

Function

v_rdwr invokes the v_rdwr callable service to accept a vnode token representing a file and to write data to the file. The number of bytes written and the file attributes are returned in RETVAL when the write completes.

Parameters

vntoken
A variable name that contains the vnode token for the file to be written.
variable
The name of the buffer from which data is to be written.
length
The number of characters to write.
position
The file offset where the write is to start from, specified in bytes.
stem
The name of a stem variable used to return the file attributes. Upon return, stem.0 contains the number of attribute variables returned. The same information is returned in stem as if a v_getattr was used on the file. To access the file attributes, you can use a numeric value or the predefined variables beginning with ST_ used to derive the numeric value. See stat for more information about the ST_ predefined variables; see REXX predefined variables for the numeric values.
access_check
Specify 0 for no access check, or 1 for the system to check the user for read access to the file. The user is defined by the effective UID and GID. Setting the effective GID does not affect supplemental groups. Also, there is no support for altering the MVS™ user identity of the task using the ACEE.
opentoken
A variable name that contains the open token as returned from the v_open service. If the opentoken parameter is specified, the access_check parameter must also be specified.

Example

In the following example, assume that filetok, buf, and pos were assigned values earlier in the exec:
"v_write filetok buf" length(buf) pos

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014