Subject: | |
From: | |
Reply To: | |
Date: | Thu, 18 Jan 2001 10:00:17 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
MPE's assumption is correct: the wildcard would lead to a nine character
long filename which is not allowed in MPE.
Try
LISTFILE /!HPACCOUNT/@/@QPLIMIT@,2
and this will work as supposed!
Best regards, Andreas Schmidt, CSC, GERMANY
"James B. Byrne" <[log in to unmask]>@RAVEN.UTC.EDU> on 17/01/2001
06:25:38 PM
Please respond to "James B. Byrne" <[log in to unmask]>
Sent by: HP-3000 Systems Discussion <[log in to unmask]>
To: [log in to unmask]
cc:
Subject: [HP3000-L] Wild card parsing in LISTF
LISTF @[log in to unmask]@,2;$STDLIST
^
File name is more than eight characters long. (CIERR 532)
I ran across this today. I also remember running into this a
long time ago on MPE. Would this not be considered an
implementation flaw? After all, does not @ match nothing as
well? Should not the above yield the same result as the
combined output of:
LISTF @QPLIMIT.@,2;$STDLIST
LISTF [log in to unmask]@,2;$STDLIST
Its not a big thing I admit, it just strikes me as odd. I seem to
recall that something similar used to happen if you tried to
back reference an eight character file name in a FILE equate.
I tested this just to see and it works fine.
:file abcdefgh=qptxrunj
:file ijklmnop=*abcdefgh
Is this an old problem that isn't worth fixing or is this behaviour
intended? If so, for what reason? Just wondering.
Regards,
Jim
--- *** e-mail is not a secure channel ***
James B. Byrne Harte & Lyne Limited
vox: +1 905 561 1241 9 Brockley Drive
fax: +1 905 561 0757 Hamilton, Ontario
mailto:[log in to unmask] Canada L8E 3C3
|
|
|