HP3000-L Archives

October 1995, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Per Ostberg <[log in to unmask]>
Reply To:
Date:
Thu, 26 Oct 1995 17:31:54 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (125 lines)
     After a bit of humble research of MPEX it seems to me that the =
 
     'lockword' variable doesn't mean anything if you don't have =
 
     AM-capabilities. (If this is the case maybe you can use =
 
     GOD.PUB.VESOFT?)
     =
 
     On the other hand, this behavior doesn't seem right to me. Some fun=
ny =
 
     output:
     =
 
     as one user:
     :mpex.pub.vesoft
     =
 
     MPEX/3000  25N50418  (c) VESOFT Inc, 1980  5.0  03:00361  For help =
=
 
     type 'HELP'
     <snip>
     <23 NATTJOB  4:19 PM> rename test1, test1/test1 =
 
     -----Renaming TEST1.NATT.NATTJOB         =3D> TEST1 =
 
     <24 NATTJOB  4:19 PM> listf test#
     <snip>
     TEST1       TEST2       TEST3       =
 
     =
 
     <25 NATTJOB  4:19 PM> listf test#(lockword=3D"") =
 
     <snip>
     TEST1       TEST2       TEST3       =
 
     #(^^^^, just renamed it)
     =
 
     <26 NATTJOB  4:20 PM> showvar hpusercap@ =
 
     HPUSERCAP =3D 196992
     HPUSERCAPF =3D ND,SF,BA,IA
     <27 NATTJOB  4:54 PM> =
 
     ......
     =
 
     and as another user:
     KEM/PER (1):mpex.pub.vesoft
     MPEX/3000  25N50418  (c) VESOFT Inc, 1980  5.0  03:00361  For help =
type =
 
     'HELP'
     <snip>
     <17 KEM  4:24 PM> rename test1,test1/test1
     -----Renaming TEST1.PER.KEM              =3D> TEST1
     <18 KEM  4:25 PM> listf test#             =
 
     <snip>
     TEST1       TEST2       TEST3       =
 
     =
 
     <19 KEM  4:25 PM> listf test#(lockword=3D"")
     <snip>
     TEST2       TEST3       =
 
     #(no TEST1)
     =
 
     <20 KEM  4:25 PM> showvar hpusercap@
     HPUSERCAP =3D 1887633867
     HPUSERCAPF =3D AM,AL,GL,LG,ND,SF,BA,IA,PM,MR,DS,PH
     =
 
So, if I don't have AM-cap (at least that's what LISTF ,-3 hinted: 'LIST=
F ,-1 or
=2D3 requires AM capability. (CIERR 423)') the 'lockword' variable is ig=
nored. Is =
 
there an explanation out there? Is this a bug or a feature?
 
/per
 
______________________________ Reply Separator _________________________=
________
Subject: Re: Mpex filesets and lockwords
Author:  HP3000-L at shar/dd.RFC-822=3DHP3000-L\@utcvm\.utc\.edu Date:  =
  =
 
1995-10-26 3.34
 
 
Per Ostberg <[log in to unmask]> Wrote: | | Item Subject: Mpex=
 =
 
filesets and lockwords |
| What you're looking for might be something like: | :print =
 
<fileset>(lockword=3D"");search=3D.....
 
Hello Per,
 
I already tried it, but.....
 
%PRINT [log in to unmask](LOCKWORD=3D"");SEARCH=3D"HELLO" LOCKWORD: =
 
G0000746.FSUBS.ASK60?
 
Also tried many permutations of VEFINFO with no luck.
 
Am on MPE
RELEASE: C.50.00   MPE/iX HP31900 B.79.06   USER VERSION: C.50.00
 
Mpex
MPEX/3000  25N50418  (c) VESOFT Inc, 1980  4.0  02:00303
     =
 
Regards,
Henryk.

ATOM RSS1 RSS2