IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

REXX Access to VSAM Files
Accessing VSAM Files Using Alternate Keys
The following example code fragments are written in REXX:
v To access the VSAM information using alternate keys, perform the VSAM I/O
requests using the PATH cluster. For example:
– VSAMC320.BASE is the base cluster.
– VSAMC320.AIX is the Alternate Index cluster.
– VSAMC320.PATH is the PATH.
v To access the VSAM information using the primary keys, ALLOC the BASE
cluster, then attempt VSAM I/O requests using DSIVSMX.
’ALLOC FILE(BASE) DSN(VSAMC320.BASE)’
’DSIVSMX vsmx_func BASE ’
v To access the VSAM information using the alternate keys, ALLOC the PATH,
then attempt VSAM I/O requests using DSIVSMX.
’ALLOC FILE(PATH) DSN(VSAMC320.PATH)’
’DSIVSMX vsmx_func PATH
Where vsmx_func is one of the following DSIVSMX functions:
OPEN or CLOSE
GET or GETREV
PUT
DEL
INQUIRE
Deleting an Alternate Index File
To delete the base and Alternate Index clusters, delete the base using DSIVSMX
IDCAMS with the DELETE CLUSTER parameters. If you delete the base, the
alternate index and the path will also be deleted.
Using the AUTOTOKE Value Provided by DSIVSMX
An AUTOTOKE value is set by DSIVSMX whenever the VSAM file is opened or
closed. This value is provided in all messages issued by DSIVSMX, and can be
retrieved using the AUTOTOKE() REXX function, or in the output of the DSIVSMX
INQUIRE command. To determine that the VSAM file has not been opened or
closed since the last I/O, do the following:
1. Save the AUTOTOKE value when the data set is opened. The DSI633I message
has the AUTOTOKE() value. Alternately, use DSIVSMX INQUIRE after the
DSIVSMX OPEN to retrieve and save the value from the INQUIRE message
text.
2. Check the AUTOTOKE value after you issue the DSIVSMX commands. If the
value is the same as the saved value, the data set was neither opened nor
closed since the last access.
DSIVSAM: Access to Keyed VSAM Files Defined by NetView DSTs
342 Programming: Pipes
The DSIVSAM command processor can access VSAM keyed files that are defined
by NetView data services tasks such as DSILOG. This allows for implementation of
all kinds of VSAM applications, including end-use application development in
REXX (in conjunction with the pipeline facility) and intensive VSAM diagnostics.
For more information about DSIVSAM, see the NetView online help.
The DSIVSAM command provides REXX access to any keyed VSAM file on any
data services task.