RE: [Hardhats-members] Taskman problems
Nancy, That fixed it! Thanks, thurman > -Original Message- > From: [EMAIL PROTECTED] [mailto:hardhats- > [EMAIL PROTECTED] On Behalf Of Nancy Anthracite > Sent: Thursday, March 24, 2005 8:35 PM > To: hardhats-members@lists.sourceforge.net > Subject: Re: [Hardhats-members] Taskman problems > > I think I know what your problem is. Your parameter in the Taskman site > parameters file for "Mode of Taskman" should be general. See if that > fixes > it. > > On Thursday 24 March 2005 09:05 pm, Thurman Pedigo wrote: > > It appears I am having problems with Taskman and box volume pair. Anyone > > know what I am missing or what else I should check, given the data > below? > > > > Thanks, > > > > Thurman > > > > > > D ^ZTMB > > > > D GETENV^%ZOSV W Y > > VISTA^VISTA^W2K3^VISTA:CACHEMAW > > > > Checking Taskman. Current $H=59983,71375 (Mar 24, [EMAIL > > PROTECTED]:49:35) > > RUN NODE=VISTA:CACHEMAW is the wrong type in > taskman > > site > > parameters. (VISTA:CACHEMAW is the wrong type in taskman site > parameters.) > > Taskman is late by 5182602560 seconds. not running.. > > Checking the Status List: > > Node weight status time $J > > The Status List is empty. > > > > Checking the Schedule List: > > Taskman has 134 tasks scheduled. > > All of them are overdue. First task is 24513941 seconds late. > > > > Checking the IO Lists: > > There are no tasks waiting for devices. > > > > Checking the Job List: > > There are no tasks waiting for partitions. > > For VISTA:NTA there are 0 tasks. > > For VISTA:NTB there are 0 tasks. > > > > Checking the Task List: > > There are no tasks currently running. > > On node VISTA:CACHEMAW there are no free Sub-Manager(s). Status: > Run > > > > > > > > --- > > 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > ___ > > Hardhats-members mailing list > > Hardhats-members@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > -- > Nancy Anthracite > > > --- > 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > ___ > Hardhats-members mailing list > Hardhats-members@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hardhats-members --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Taskman problems
I think I know what your problem is. Your parameter in the Taskman site parameters file for "Mode of Taskman" should be general. See if that fixes it. On Thursday 24 March 2005 09:05 pm, Thurman Pedigo wrote: > It appears I am having problems with Taskman and box volume pair. Anyone > know what I am missing or what else I should check, given the data below? > > Thanks, > > Thurman > > > D ^ZTMB > > D GETENV^%ZOSV W Y > VISTA^VISTA^W2K3^VISTA:CACHEMAW > > Checking Taskman. Current $H=59983,71375 (Mar 24, [EMAIL PROTECTED]:49:35) > RUN NODE=VISTA:CACHEMAW is the wrong type in taskman > site > parameters. (VISTA:CACHEMAW is the wrong type in taskman site parameters.) > Taskman is late by 5182602560 seconds. not running.. > Checking the Status List: > Node weight status time $J > The Status List is empty. > > Checking the Schedule List: > Taskman has 134 tasks scheduled. > All of them are overdue. First task is 24513941 seconds late. > > Checking the IO Lists: > There are no tasks waiting for devices. > > Checking the Job List: > There are no tasks waiting for partitions. > For VISTA:NTA there are 0 tasks. > For VISTA:NTB there are 0 tasks. > > Checking the Task List: > There are no tasks currently running. > On node VISTA:CACHEMAW there are no free Sub-Manager(s). Status: Run > > > > --- > 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > ___ > Hardhats-members mailing list > Hardhats-members@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Nancy Anthracite --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
[Hardhats-members] Taskman problems
It appears I am having problems with Taskman and box volume pair. Anyone know what I am missing or what else I should check, given the data below? Thanks, Thurman D ^ZTMB D GETENV^%ZOSV W Y VISTA^VISTA^W2K3^VISTA:CACHEMAW Checking Taskman. Current $H=59983,71375 (Mar 24, [EMAIL PROTECTED]:49:35) RUN NODE=VISTA:CACHEMAW is the wrong type in taskman site parameters. (VISTA:CACHEMAW is the wrong type in taskman site parameters.) Taskman is late by 5182602560 seconds. not running.. Checking the Status List: Node weight status time $J The Status List is empty. Checking the Schedule List: Taskman has 134 tasks scheduled. All of them are overdue. First task is 24513941 seconds late. Checking the IO Lists: There are no tasks waiting for devices. Checking the Job List: There are no tasks waiting for partitions. For VISTA:NTA there are 0 tasks. For VISTA:NTB there are 0 tasks. Checking the Task List: There are no tasks currently running. On node VISTA:CACHEMAW there are no free Sub-Manager(s). Status: Run --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
Re: [Hardhats-members] Taskman problems
Nancy, Thanks for your feedback. It helped me zero in on the problem. In my install script, I had to create a special, non-interactive, version of ZTMGRSET. It is ZTMGRSET that sets up all these parameters correctly. Turned out that I had a bug that caused my customized version to skip the code that set the VOL,UCI parameters. I think I have it fixed now. So it turns out that it is not a bad thing to use something other than ROU... you just have to not have code with a bug in it! :-) Thanks again. Kevin --- "Nancy E. Anthracite" <[EMAIL PROTECTED]> wrote: > Sorry, I am blind. > > Well, I looked at my system where you had partially > run your XML on last > night, and clearly telling VOL that it is VOL is not > enough because > everything is pointing to the Taskman SIte > Parameters box: volume pair and > that is pointed to ROU:localhost despite saying it > is VOL:localhost, and that > must be because it is pointed at that 4th peice of Y > . I think you should > give in and run the GETENV^%ZOSV right from the get > go and don't fight city > hall. Use the ROU for your volume like it said in > the first place and don't > try to change it. However, if you do want to > change it, I have this note to > myself from advice from an old email sent by ??? I > will find it and send you > the reference. > > When moving a system over from another environment > it would be best to just > KILL ^%ZTSCH and ^%ZTSK as start over. To start > rebuilding use the option ... > > > On Friday 17 December 2004 06:12 pm, Kevin > Toppenberg wrote: > > The screen log below shows: > > > > VOL:poweredge > > > > Kevin > > > > --- "Nancy E. Anthracite" > <[EMAIL PROTECTED]> > > > > wrote: > > > If you put ?? here, what do you get? > > > > > > Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: > ?? > > > > > > > > > On Friday 17 December 2004 05:17 pm, Kevin > > > > > > Toppenberg wrote: > > > > 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: > > > >
Re: [Hardhats-members] Taskman problems
Well, here it is from a private email and a benefactor who will remain
nameless until I know if he minds being named. I don't know if it applies.
**
D ^XUP calls ^XQ1 after setting up the variables. I don't know of any
reason it would not offer options.
Any security lock check is done after you select the option.
When moving a system over from another environment it would be best to
just KILL ^%ZTSCH and ^%ZTSK as start over. To start rebuilding use the
option SCHEDULE/UNSCHEDULE tasks to setup the regularly scheduled options.
Things likeXTRMONITOR, XUSCZONK, XU-SPL-PURGE, XQBUILDTREEQUE, XQ XUTL $J
NODES, XUTM QCLEAN, XMCLEAN, XMAUTOPURGE, XWB LISTENER STARTER. There
are others for things that should be running on a regular basis.
^%ZTSK has the data for a task. The who, what, and where. ^%ZTSCH is
taskman work global, it has by time the tasks that are queued to run, in
^%ZTSCH(,task#). When it is time for the task to run the
manager checks the task and puts data into
^%ZTSCH("JOB",,task#) for general tasks or
^%ZTSCH("C",,,task#) for tasks that want a special
node. When the job starts the sub-manager puts an entry in
^%ZTSCH("TASK",task#) to track the jobs that are running.
Here is the code for the timeinseconds, The input is a $H value
H3(%) ;Convert $H to seconds.
Q 86400*%+$P(%,",",2)
Hope that gives some insight into what is in these globals.
-Original Message-
From: Anthracite, Nancy
Sent: Tuesday, August 31, 2004 7:59 AM
To: Fort, Wally
Subject: RE: Thank you!
I want to get together a set of instructions about how to do this port and
eventually how to do a FOIA port, which is why I wanted the log, not to
mention that they teach me a lot.
Do I do that with literally doing K ^%ZTSCH("C") etc.? And then do I need
to replace them? If so, with what or where do I set them? I need to be
able to repeat the process as a way of proofing my instructions. What
does the ZTSCH global have to do with in general - Taskman I assume.
Also, do you have any idea why when I use D ^XUP I am not offered options?
Chris made a new user and got them. I modified an old user who had all of
the XU keys, and it doesn't give me options.
Thanks so much for fixing it. Now I HOPE it will hook up and go!
-Original Message-
From: Fort, Wally
Sent: Tuesday, August 31, 2004 10:50 AM
To: Anthracite, Nancy
Subject: RE: Thank you!
Glad to help.
I was almost done when Chris said you wanted a log, sorry I didn't know in
time.
The problem was old data in the ^%ZTSCH global. I killed off these nodes
^%ZTSCH("C"),^%ZTSCH("LINK"),^%ZTSCH("ER"),^%ZTSCH("DEVTRY"),^%ZTSCH("MON"
),
^%ZTSCH("TASK")
and TaskMan was happy again.
On Friday 17 December 2004 07:56 pm, Nancy E. Anthracite wrote:
> Sorry, I am blind.
>
> Well, I looked at my system where you had partially run your XML on last
> night, and clearly telling VOL that it is VOL is not enough because
> everything is pointing to the Taskman SIte Parameters box: volume pair and
> that is pointed to ROU:localhost despite saying it is VOL:localhost, and
> that must be because it is pointed at that 4th peice of Y . I think you
> should give in and run the GETENV^%ZOSV right from the get go and don't
> fight city hall. Use the ROU for your volume like it said in the first
> place and don't try to change it. However, if you do want to change it, I
> have this note to myself from advice from an old email sent by ??? I will
> find it and send you the reference.
>
> When moving a system over from another environment it would be best to just
> KILL ^%ZTSCH and ^%ZTSK as start over. To start rebuilding use the option
> ...
>
> On Friday 17 December 2004 06:12 pm, Kevin Toppenberg wrote:
> > The screen log below shows:
> >
> > VOL:poweredge
> >
> > Kevin
> >
> > --- "Nancy E. Anthracite" <[EMAIL PROTECTED]>
> >
> > wrote:
> > > If you put ?? here, what do you get?
> > >
> > > Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: ??
> > >
> > >
> > > On Friday 17 December 2004 05:17 pm, Kevin
> > >
> > > Toppenberg wrote:
> > > > 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:
> > > > Taskm
Re: [Hardhats-members] Taskman problems
Sorry, I am blind. Well, I looked at my system where you had partially run your XML on last night, and clearly telling VOL that it is VOL is not enough because everything is pointing to the Taskman SIte Parameters box: volume pair and that is pointed to ROU:localhost despite saying it is VOL:localhost, and that must be because it is pointed at that 4th peice of Y . I think you should give in and run the GETENV^%ZOSV right from the get go and don't fight city hall. Use the ROU for your volume like it said in the first place and don't try to change it. However, if you do want to change it, I have this note to myself from advice from an old email sent by ??? I will find it and send you the reference. When moving a system over from another environment it would be best to just KILL ^%ZTSCH and ^%ZTSK as start over. To start rebuilding use the option ... On Friday 17 December 2004 06:12 pm, Kevin Toppenberg wrote: > The screen log below shows: > > VOL:poweredge > > Kevin > > --- "Nancy E. Anthracite" <[EMAIL PROTECTED]> > > wrote: > > If you put ?? here, what do you get? > > > > Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: ?? > > > > > > On Friday 17 December 2004 05:17 pm, Kevin > > > > Toppenberg wrote: > > > 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
Re: [Hardhats-members] Taskman problems
The screen log below shows: VOL:poweredge Kevin --- "Nancy E. Anthracite" <[EMAIL PROTECTED]> wrote: > If you put ?? here, what do you get? > > Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: ?? > > > On Friday 17 December 2004 05:17 pm, Kevin > Toppenberg wrote: > > 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
Re: [Hardhats-members] Taskman problems
If you put ?? here, what do you get? Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: ?? On Friday 17 December 2004 05:17 pm, Kevin Toppenberg wrote: > 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 -- Nancy Anthracite --- 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/har
[Hardhats-members] Taskman problems
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
