Re: Determining a 'process id'

[Evan Harris <spanner@xxxxxxxxxx>]

Rob

It wouldn't surprise me if TSM happened to be referring to its own process 
ID's. It also wouldn't surprise me if the kill command it is referring to 
is its own kill command rather than an OS kill command. My experience with 
TSM suggests that this is a fair possibility.

I can tell you from painful experience that TSM did not like jobs being 
ended from other than the approved (read TSM/ADSM) interfaces.

If you can't find the green screen TSM administration console - or it no 
longer exists on your version - then the browser interface will allow you 
to get a TSM command line.

I wasn't aware that the new version of TSM (5.2 now is it ?) was actually 
shipping for the AS/400 yet but I have thankfully escaped from using it so 
it may well have slipped under my guard.

Regards
Evan Harris

> At 12:40 01/08/2003, Rob Berendt wrote:
> > I had a coworker here working on an iSeries PASE based Tivoli solution.
> > She asked me a question.  She has to issue a 'kill' command to stop a
> > 'process id'.  She knows that it is a particular job, like
> > number/user/jobname, however ENDJOB is not the appropriate command.  Is
> > there a way to determine the process id?
> ps will show you the process ID for your own jobs. ps -A will show you the 
> process ID for all jobs. Within a job, the $$ shell variable expands to 
> the job's process ID.
> Pete Hall