To All,
We have an HP3000 967/RX running MPE/iX 5.0 PP5
RELEASE: C.50.02 MPE/iX HP31900 B.79.06 USER VERSION: C.50.02
I was trying to use the 'listuser' command when the following odd behavior was
observed:
1. First get the correct syntax
:help listuser
LISTUSER
Displays information for one or more users.
SYNTAX
LISTUSER [userset][,listfile][;PASS]
[;FORMAT={SUMMARY|BRIEF|DETAIL}]
KEYWORDS: PARAMETER,OPERATION,EXAMPLE
2. Now build the needed file and issue file equation to capture the data:
:build tf;rec=-80,,f,ascii;temp
:file t=tf,oldtemp
:listuser mgr.vxl,*t;pass
:
:listuser mgr.vxl,*t;pass;format=detail
^
Only two parameters allowed, PASS and FORMAT. (CIERR 870)
3. This is strange!!. I cannot use the listfile when I specify 'pass' and
'format'. Let us see if 'listacct' behaves the same way:
listuser mgr.vxl,*t;pass;format=detail
dddddddddiacct
listacct vxl,*t;pass;format=detail
:listacct vxl,*t;pass;format=detail
EXCLUSIVE VIOLATION: FILE ACCESSED EXCLUSIVELY (FSERR 91)
File system error 91 encountered on list file. (CIERR 425)
4. This is even more strange!! The temp file is being accessed?
:listftemp,2
TEMPORARY FILES FOR MANAGER.SYS,SUPUTIL
ACCOUNT= SYS GROUP= SUPUTIL
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
TF * 80B FA 0 1023 3 256 1 * (TEMP)
5. Well, lets use a different temp file for the listacct:
:build tf2;rec=-80,,f,ascii;temp
:file t2=tf2,oldtemp
:listacct vxl,*t2;pass;format=detail
^
Only two parameters allowed, PASS and FORMAT. (CIERR 870)
:listftemp ,2
TEMPORARY FILES FOR MANAGER.SYS,SUPUTIL
ACCOUNT= SYS GROUP= SUPUTIL
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
TF * 80B FA 0 1023 3 256 1 * (TEMP)
TF2 * 80B FA 0 1023 3 0 0 * (TEMP)
6. This is even worse. Both commands behave the same, consistency is good,
and now I have two temp files that are being accessed by my session.
I guess I can use command redirection to place the needed data into a file
but it would sure have been nice if the documentation mentioned that.
On the other hand it could just be an error on HP's part?
Any ideas??
Regards
Paul H. Christidis
|