Thanks Greg, I found an earlier post in the archives that suggested
someone rerun ZTMGRSET when they were getting the WSAEINTR error when
attempting to start CPRS.  That has obviously caused the problem with
my errors.  Upon restarting Taskman, my D ^%SS output is as below, but
CPRS still gives me the same interrupted system call error (WSAEINTR).
 Again, I'm just trying to start CPRS with Cache and Vista configured
on the same machine, and I'm trying to connect to my localhost.  Is
there some other common mistake that I am making?


VISTA 5f3>D ^%SS

                 Cache System Status: 12:58 pm 28 Jul 2005
 
Process  Devices      KB Namespace      Routine     CPU,Glob  Pri  UIC  Location
   624                   %SYS                         0,0      7   0,0  CONTROL
   880                   %SYS                      1252,3425   8   0,0  WRTDMN
   892                   %SYS                         0,0      7   0,0  GARCOL
   872                   %SYS                      8453,6364   7   0,0  JRNDMN
   928                   %SYS                         0,0      7   0,0  EXPDMN
  2036   //./nul      64 %SYS           TASKMGR   69523,13020  7   0,0
  3012*  |TRM|:|3012 126 VISTA          %SS     1348233,675654  7  0,0
  1472   |TCP|1972    45 %SYS           %cmtP        45,11     7   0,0
  1876   |TCP|9210    80 VISTA          XWBTCPL    3484,451    7   0,0
  2180   //./nul      52 VISTA          %ZTM       2432,399    7   0,0
  3324   //./nul      61 VISTA          XMKPLQ    43384,11987  7   0,0
  3336   //./nul      66 VISTA          XMTDT     24770,4681   7   0,0
  3764   //./nul      49 VISTA          %ZTMS1   293823,71824  7   0,0




On 7/28/05, Greg Woodhouse <[EMAIL PROTECTED]> wrote:
> It looks as if someone ran ZTMGRSET while Taskman was running. This
> causes a fatal error which you see reported here). All that you need to
> do is restart Taskman.
> 
> In general...Infrastructure is something that needs to be updated or
> patched more carefully than normal applications. You usually need to
> place Taskman in a wait state  or, in some cases, stop it completely
> when updating these routines. In case you're interested %ZTM is the
> manager routine -- it runs in the backgound handling scheduling and
> assignment of tasks to submanagers which, in turn, actually run them.
> The routine %ZTMS1 is part of the submanager code.
> 
> --- Kevin Adams <[EMAIL PROTECTED]> wrote:
> 
> > I am trying to configure Vista for the first time on Windows.  I am
> > able to log into the RPC BROKER test program just fine, but when I
> > try
> > to start up the CPRSChart.exe file, I get a WSAEINTR error.  As I was
> > following the trouble shooting tips on the instruction page, I came
> > across these taskman-related errors occuring
> >
> > VISTA>D ^XTER
> >
> >
> > In response to the DATE prompt you can enter:
> >     'S' to specify text to be matched in error or routine name
> >
> >
> > 2 errors logged on 7/28/2005
> >  2)  <EDITED>^%ZTMS1                 17:12:40  VISTA,VISTA     3352
> > //./nul:3
> >  1)  <EDITED>^%ZTM                   17:10:12  VISTA,VISTA      108
> > //./nul:1
> >
> > No screened error
> >
> >     Enter '^' to quit listing, <RETURN> to continue...:
> >
> > Which error? >  1
> >
> >
> > Process ID:  108  (108)
> >                                                          JUL 28, 2005
> > 17:10:12
> >
> > Username:                               Process Name:
> >
> > UCI/VOL: [VISTA,VISTA]                  :
> >
> > $ZA:   0                                $ZB:
> >
> > Current $IO: //./nul:108                Current $ZIO: ^0^0
> >
> > CPU time:                               Page Faults:
> >
> > Direct I/O:                             Buffered I/O:
> >
> > $ZE= <EDITED>^%ZTM
> >
> > Last Global Ref: ^%ZTSCH("LINK")
> >
> > Which symbol? >
> >
> > Which error? >  2
> >
> >
> > Process ID:  3352  (3352)
> >                                                          JUL 28, 2005
> > 17:12:40
> >
> > Username:                               Process Name:
> >
> > UCI/VOL: [VISTA,VISTA]                  :
> >
> > $ZA:   0                                $ZB:
> >
> > Current $IO: //./nul:3352               Current $ZIO: ^0^0
> >
> > CPU time:                               Page Faults:
> >
> > Direct I/O:                             Buffered I/O:
> >
> > $ZE= <EDITED>^%ZTMS1
> >
> > Last Global Ref: ^%ZOSF("OS")
> >
> > Since a lot of problems seem to be related to box:volume pairs, this
> > output may be helpful to someone too:
> >
> > VISTA>D GETENV^%ZOSV W Y
> > VISTA^VISTA^LUCETIA-2DAFC0E^VISTA:CACHEWEB
> >
> > Here is my D ^ZTMON output:
> > VISTA>D ^ZTMON
> >
> > Checking Taskman.   Current $H=60109,40197  (Jul 28, [EMAIL 
> > PROTECTED]:09:57)
> >                      RUN NODE=60109,40195  (Jul 28, [EMAIL PROTECTED]:09:55)
> > Taskman is current..
> > Checking the Status List:
> >  Node      weight  status      time       $J
> >  VISTA:CACHEWEB     RUN      [EMAIL PROTECTED]:09:55   108       Main Loop
> >
> > Checking the Schedule List:
> >     Taskman has no tasks scheduled.
> >
> > 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.  Out Of Service
> >     For VISTA:NTB there are 0 tasks.  Out Of Service
> >
> > Checking the Task List:
> >     There are 2 tasks currently running.
> >     On node VISTA:CACHEWEB there are  2 free Sub-Manager(s). Status:
> > Run
> >
> > I hope I have provided enough info for someone to help me track down
> > the problem.  Since I am totally new to this, any help is
> > appreciated.
> >  Thank you!
> >
> >
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September
> > 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> > Agile & Plan-Driven Development * Managing Projects & Teams * Testing
> > & QA
> > Security * Process Improvement & Measurement *
> > http://www.sqe.com/bsce5sf
> > _______________________________________________
> > Hardhats-members mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >
> 
> 
> 
> ===
> Gregory Woodhouse  <[EMAIL PROTECTED]>
> 
> "Design quality doesn't ensure success, but design failure can ensure 
> failure."
> 
> --Kent Beck
> 
> 
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO September
> 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Hardhats-members mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
>


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to