I made a mistake.  I imagined the processes columns in the output from "select 
* from syscat.columns" would sort into tables by default; they didn't.
When I tried "select * from processes" using Servergraph, I didn't notice that 
the titles stretched way off my screen.
I think I'll just go back to lurking...
 - Margaret

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Howard Coles
Sent: Thursday, March 17, 2011 8:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Scripts Doubling up

I'm not sure how you're pulling that "syscat columns" information.  
However, Here's a sample from the select statement that David offered:

PROCESS_NUM: 1810
        PROCESS: Migration
     START_TIME: 2011-03-17 10:09:45.000000
FILES_PROCESSED: 40
BYTES_PROCESSED: 33943646208
         STATUS: Disk Storage Pool ORADSKPOOL, Moved Files: 43, Moved
Bytes: 33,945,214,976,
                  Unreadable Files: 0, Unreadable Bytes: 0. Current
Physical File (bytes):
                  27,689,148,416 Current output volume(s): B00404L4.

See Ya'
Howard Coles Jr., RHCE, CNE, CDE
John 3:16!

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Clark, Margaret
Sent: Wednesday, March 16, 2011 6:03 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Scripts Doubling up

Not on our 6.2.2.0 server, it doesn't!  - Margaret

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David E Ehresman
Sent: Wednesday, March 16, 2011 12:04 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Scripts Doubling up

But at v6.2.2.0, a "select * from processes" does show a STATUS field.

David

>>> "Clark, Margaret" <MClark AT SDDPC DOT ORG> 3/16/2011 2:52 PM >>>
Syscat columns doesn't show a STATUS in the PROCESSES table any more.
- Margaret Clark

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of Howard Coles
Sent: Tuesday, March 15, 2011 6:51 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Scripts Doubling up

Ladies and Gents, got another weird issue.  TSM 6.2.2.1



Running the following script works when I preview it in the ISC:



select process_num from processes where process='Backup Storage Pool'
and status LIKE '%Pool AIXDSKPOOL%'

if (rc_ok) goto reschedule

backup stg aixpripool aixcppool maxproc=2 wait=no

update sched daily_aix_proc type=admin cmd='RUN DAILY03_AIX_MIGSTG'
starttime=now+00:30 active=yes

exit

reschedule:

update schedule daily_aix_proc type=admin starttime=now+00:05
active=yes

exit



However, when it runs on its own apparently the select and if
statement
are no longer working.  I have found the backup process running on the
primary tape pool at the same time the diskpool backup is running.  I
haven't had time to redo all the scripts, but this should still
function
from all the tests I ran.

My question is, what is wrong with the above script that it wouldn't
work, at least for now, as written?



Oh, here's the part of the previous script that kicks off the disk
pool
backup:



backup stg aixdskpool aixcppool maxproc=2 wait=no

update sched daily_aix_proc type=admin cmd='RUN DAILY02_AIX_BAKPRI'
starttime=now+00:30 active=yes



This process has worked very well, as we have 5 storage pools, that
vary
in length for each of the processes that run against them, (backup
disk,
backup primary tape, reclaim offsite, reclaim onsite, etc).



See Ya'

Howard Coles Jr.

John 3:16!