> 
> That's not ALWAYS the case. I haven't fully investigated but I've 
noticed that
> whenever a job has a "long" or "not standard" name it cannot be 
removed by rjob
> using it's job no. (eg. ProWesS, QD). Others (eg  QPAC jobs say 
"Files") can be
> removed.
>
Well, looks like I have another little assembler project to occupy my 
rationed QL time! :O)

Ian.

> -----Original Message-----
> From: webmaster 
> Sent: 28 January 2002 14:22
> To: ql-users
> Cc: webmaster
> Subject: RE: [ql-users] A foible ...
> 
> 
> At 02:13 μμ 28/1/2002 +0000, you wrote:
> 
> > > ... In other words, I think the ability to supply -1 as the job
> > > id to this trap is a bit silly :o)
> >Probably listed for completeness as the -1 argument value is accepted
> >by the trap and therefore technically valid, even though its use is
> >illogical in that context.
> >
> >On the subject of removing jobs, from SBASIC the RJOB command seems
> >only to accept the name of a job, not its number (which to me would
> >seem more useful).  What if I have more than one job with the same
> >name?  RJOB removes the first listed.  I saw NXJOB in the Toolkit II
> >manual and thought it might be relevant but can't figure out how to
> >make it do anything except "invalid parameter".
> >
> >Ian.
> 
> That's not ALWAYS the case. I haven't fully investigated but 
> I've noticed 
> that whenever a job has a "long" or "not standard" name it cannot be 
> removed by rjob using it's job no. (eg. ProWesS, QD). Others 
> (eg  QPAC jobs 
> say "Files") can be removed.
> 
> Good point Ian, I always wanted to ask that...  :-)
> 
> 
> Phoebus
> 


Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.

Reply via email to