On Thu, 7 Mar 1996 14:18:34 -0800 Stan Sieler said:
>Jeff [Vance] writes:
>> This is accomplished via a new parameter: job=job_id, where job_id can be:
>>    [#]Jnnn
>...
>>I would like to extend job_id to include all jobs for a user.acct. I imagine
>> some of you already have developed a syntax to accomplish this.  My idea
>> is:
>>    [@J | @S:]user.acct
>>   "[@J | @S:]jobname,user.acct"   <-- quotes needed for same reason
>
>What about the obvious:
>
>   #J@:user.acct
>
>The next enhancement is to allow any MPE pattern.  For example, I want to
>wait for all (or is it *any one of*?) jobs in the range 120..129:
>
>   #J12?:@.@
                 [...snip...]
 
Or even better still, given that the code is now there for the calling, why
don't we allow regular expressions?  egrep rules would be fine, perl even
better still.  Maybe some escape code that allowed a regular expression in
anyplace the MPE wildcards can now appear - then we enhance a boatload of
commands in one swipe (assuming the wildcard expansion code is common).
 
I'll admit to some bias here (having finally just leared what that cryptic
pattern matching regular expression stuff is all about) but the payoffs are
great and the hard part (the code to do the matching) is already done and
part of the Posix library.
 
Jeff Kell <[log in to unmask]>