1 10/07/88 get_information, gi
 2 
 3 Syntax as a command:
 4 gi arguments {-control_args}
 5 
 6 
 7 Function:
 8 The  get_information  request   lets  you  obtain  information
 9 about  a file on a remote host.  You  can obtain any or all of
10 the following information about a file on a remote host:
11   file name
12   history
13   logical attributes
14   physical attributes
15 
16 
17 Arguments:
18 file
19   file   is  the  name  of  the  file  about  which  you  want
20   information  and must  be specified in a form acceptable  to
21   host  on  which  the  file resides.   It must be preceded by
22   -name (or -nm)  if the file  name  begins  with  a  "-".  It
23   must be followed by "-at CORRESPONDENT"  where CORRESPONDENT
24   must be  the  name  given  in  the  NIT (Network Information
25   Table) to the remote  UFT application.   It must be enclosed
26   in quotes if it contains spaces or  special  characters.  If
27   the  CORRESPONDENT is  running  on  a  Multics  system, then
28   file  can be  a  "star"  name, and information on all of the
29   files that match the "star" name will be returned.
30 
31 
32 Control arguments:
33 -at CORRESPONDENT
34   CORRESPONDENT  must be  the  name given  in the NIT (Network
35   Information Table) to the remote UFT application.    The NIT
36   associates  to  the  UFT correspondent name  its DSA network
37   address (session_id and mailbox).
38 -attributes ATTRIBUTES, -att ATTRIBUTES
39   ATTRIBUTES   specifies  the  type   of  information  desired.
40   ATTRIBUTES  are:   history,   logical,  physical,  space, or
41   all.  You can specify several attributes.
42 -billing STR
43   specifies the  accounting identification used by  the remote
44   host (not Multics); there is no default.
45 -catalogue <file_name>, -cat <file_name>
46   for a non-Multics system,  <file_name> specifies a catalogue
47   file.  The -catalogue control argument is required only when
48   the  catalogue   file  for  the  file   description  is  not
49   implicitly known.  <file_name> must be specified in a syntax
50   acceptable to  the host on  which the file  will resides; it
51   must be enclosed  in quotes if it contain  spaces or special
52   characters.
53 -no_password, -npw
54   if  the -no_password  control argument  is present  the user
55   will  not  be  prompted  for  a  password  with a mask.  The
56   password will not be used by the remote host to authenticate
57   the submitter.
58 -password, -pw
59   if the  -password control argument is present  the user will
60   be prompted for a password with a mask.  The password may be
61   used by the remote host  to authenticate the submitter.  For
62   a remote  Multics system, the -password  control argument is
63   mandatory.  (Default)
64 -person STR, -user STR
65   STR  specifies the  remote user  identification used  by the
66   remote host  on whose behalf  the delete is  to be executed.
67   This may  be used by  the remote host  for authentication of
68   the job  submitter.  The default  is the Multics  user_id of
69   the user who submitted the request.
70 -project STR, -pj STR
71   STR specifies the project  identification used by the remote
72   host on whose behalf the delete is to be executed.
73 
74 
75 Examples:
76   The following  is an example  of the get_information  request
77   which will return all pertinent information about the segment
78   cr_1.
79 
80      gi uft_dest>cr_1 -at dsa.MUL1.FILETRAN