RCCLVIEW
RCCLVIEW lists the views on the distributed system.
Syntax
RCCLVIEW(platform,CCtype,viewType,host,port,TSCdirectory,distributedUserName,client_codepage,server_codepage,client_rt_codepage,timeout,cq_id,cq_passwd,cq_dbset,verbose_option)
Arguments
You can use the following arguments when you run the RCCLVIEW function:
- The name of the platform that contains the DevOps Code ClearCase® VOB. Allowable values: WINDOWS or UNIX®.
- The type of DevOps Code ClearCase environment. Allowable values: UCM or NONUCM.
- The type of DevOps Code ClearCase view. Allowable values: SNAPSHOT or DYNAMIC.
- The TCP/IP address or DNS name of the machine that contains the DevOps Code ClearCase VOB. This address must be a valid TCP/IP address or DNS name.
- The TCP/IP port number used to contact the host specified by the host argument. Allowable values: 0-65535.
- The name of the directory on the host machine from which the server component of TSO Client was started.
- The user ID on the distributed system on which you are running DevOps Code ClearCase and the server component of TSO Client.
- The code page for the input, output, and build script files on the client. Code page conversion occurs only on text files. This argument is optional.
- The code page used on the server. This argument is optional.
- The code page for the distributed system's locale. This option defaults to the same value as is specified with the client codepage client_codepage argument. This argument is optional.
- The number of minutes that the server waits for an invoked build script to return before stopping the build event. This argument is optional.
- A ClearQuest® user ID. This argument is optional.
- The password for the ClearQuest user ID. This argument is optional.
- The name of the schema repository to be used by ClearQuest. This argument is optional.
- The message verbosity. The value for this argument can be -V, -V -V, or -V -V -V. This argument is optional.
Result
The following table lists the return and reason codes that result from running the RCCLVIEW function; it also provides a description of the meaning of the codes.
Return code | Reason code | Description |
---|---|---|
0 | 600 | Processing successful. |
8 | 611 | Required argument missing. |
612 | Invalid argument value. | |
614 | Distributed command failure. | |
616 | Improper number of arguments. | |
12 | 698 | Internal error. |
699 | Internal error. |
Example
List the views on a computer running Windows® with an IP address of 9.48.114.54.
The server component of TSO Client is installed in the C:\Program Files\IBM Rational\ClearCase\bin\ directory and is running with auth mode 0, using port 4000.
The server component of TSO Client is installed in the var/tmp/samples/ directory and is running with auth mode 0, using port 4000.
The following REXX™ commands could be used to invoke the RCCLVIEW API function:
pltf = ‘WINDOWS'
cctype = ‘NONUCM'
vtype = ‘DYNAMIC'
host = ‘9.48.114.54'
port = ‘4000'
dir = ‘C:\Program Files\IBM Rational\ClearCase\bin\userID'
disuser = ‘userone'
Parse Value RCCLVIEW(pltf,cctype,vtype,host,port,dir,disuser)
With rccret rccrsn rccmsg
Output
For a list of the output data sets corresponding to the RCCLOG1, RCCOUT, and RCCERR file names, see RCCUALOC.
For a description of the log entries in RCCLOG1, see RCCULOG.
For an example listing of the log, see Example of a log entry.
RCCOUT contains a list of the view registry entries.
RCCOUT example
After a successful completion of the API call in the previous example, RCCOUT contains the following message:
testview1
testview2
testview3