It seems like this is a never-ending source of
confusion. I thought I had it all figured out, but
I'm getting box:vol parameter problems again.
Here is what taskman monitor is saying:
--------------------------------
Checking Taskman. Current $H=59886,61383 (Dec 17,
[EMAIL PROTECTED]:03:03)
RUN NODE=ROU:poweredge is the
wrong type in taskman site parameters. (ROU:poweredge
is the wrong type in taskman site parameters.)
Taskman is late by 5174211768 seconds. not running..
Checking the Status List:
Node weight status time $J
The Status List is empty.
Checking the Schedule List:
Taskman has 296 tasks scheduled.
All of them are overdue. First task is 24025673
seconds late.
Checking the IO Lists:
There are no tasks waiting for devices.
Checking the Job List:
There are no tasks waiting for partitions.
Checking the Task List:
There are no tasks currently running.
On node ROU:poweredge there are no free
Sub-Manager(s). Status: Run
Enter monitor action: UPDATE//
-------------------------
Specifically, it has ROU:poweredge in there, when ROU
should have been deleted during my install. Here is
what my taskman site parameters look like:
-------------------------
Select Taskman Management Utilities Option: edit
Taskman Parameters
Site Parameters Edit
UCI Association Table Edit
Volume Set Edit
Select Edit Taskman Parameters Option: site Parameters
Edit
Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: ??
VOL:poweredge
You may enter a new TASKMAN SITE PARAMETERS, if
you wish
The value for the current account is ROU:poweredge
Your answer should be the
volume set name concatenated with ":"
concatenated with the name of the CPU.
The value for the current process can be found
by doing GETENV^%ZOSV and
checking the fourth ^-piece of Y. This allows
the TaskMan site paramete
rs
to be applied extremely precisely, depending
both upon which volume set
and cpu which is affected.
Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR:
vol:poweredge
BOX-VOLUME PAIR: VOL:poweredge//
LOG TASKS?: NO//
DEFAULT TASK PRIORITY:
TASK PARTITION SIZE:
SUBMANAGER RETENTION TIME: 2//
TASKMAN JOB LIMIT: 990//
TASKMAN HANG BETWEEN NEW JOBS: 0//
MODE OF TASKMAN: GENERAL PROCESSOR//
VAX DSM ENVIROMENT FOR DCL:
OUT OF SERVICE: NO//
MIN SUBMANAGER CNT:
TM MASTER:
Balance Interval:
LOAD BALANCE ROUTINE:
Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR:
-----------------------------
And here is my volume set entry:
-----------------------------
Site Parameters Edit
UCI Association Table Edit
Volume Set Edit
Select Edit Taskman Parameters Option: volume Set Edit
Select VOLUME SET: ??
VOL
You may enter a new VOLUME SET, if you wish
Answer should be the name of a volume set.
When each cpu can have only one volume set,
this is also the cpu name.
Answer will be used in extended global
references to reach this volume.
Select VOLUME SET: vol
VOLUME SET: VOL//
TYPE: GENERAL PURPOSE VOLUME SET//
INHIBIT LOGONS?: NO//
LINK ACCESS?: YES//
OUT OF SERVICE?: NO//
REQUIRED VOLUME SET?: YES//
TASKMAN FILES UCI: UCI//
TASKMAN FILES VOLUME SET: VOL//
REPLACEMENT VOLUME SET: VOL//
DAYS TO KEEP OLD TASKS: 4//
SIGNON/PRODUCTION VOLUME SET: Yes//
Select VOLUME SET:
-----------------------------
So where is Taskman getting the ROU:... from, and how
can I get it to start?
Thanks
Kevin
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Hardhats-members mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
